Bug 40864

Summary:	Portage rescue leads to access violation in attempt emerge any portage
Product:	Portage Development	Reporter:	Whit Blauvelt <whit>
Component:	Unclassified	Assignee:	Portage team <dev-portage>
Status:	RESOLVED FIXED
Severity:	critical
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Whit Blauvelt 2004-02-08 11:08:01 UTC

See bug 40659 - but this is something different. After portage being hosed by 2.0.50 any attempt after following README.RESCUE to reinstall an earlier portage results in:

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-portage-2.0.50_pre22-24938.log"

open_wr:   /etc/group
open_wr:   /etc/passwd
--------------------------------------------------------------------------------

This happens with every version available. I haven't done anything to change the perms on /etc/group or /etc/passwd, if that's what this is about, which are:

# ls -l passwd
-rw-r--r--    1 root     root         2209 Dec 29 10:21 passwd
free /etc # ls -l group
-rw-r--r--    1 root     root          751 Jan 12 11:19 group


Reproducible: Always
Steps to Reproduce:
1. install bad portage-2.0.50
2. run portage-rescue-2.0.47-r10-x86.tbz2
3. emergy sync then attempt to emerge any portage




# emerge info
Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r9)
=================================================================
System uname: 2.6.2-rc1-gentoo i686 AMD Athlon(tm) XP 2500+
GENTOO_MIRRORS="http://gentoo.oregonstate.edu/
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /var/bind
/usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/share/config
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 oss apm avi crypt cups encode foomaticdb gif gtk2 jpeg kde gnome libg++
mad mikmod mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv
zlib gdbm berkdb slang readline arts tetex svga tcltk java guile mysql X sdl gpm
tcpd pam libwww ssl perl python esd imlib oggvorbis gtk qt motif opengl mozilla cdr"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-O2 -mcpu=i686 -pipe"
CXXFLAGS="-O2 -mcpu=i686 -pipe"
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"

Comment 1 Whit Blauvelt 2004-02-09 11:18:19 UTC

Can get around this with FEATURES="-sandbox" in make.conf. I assume that the sandbox is actually a Really Good Thing, so hope this will be fixed.

Comment 2 ferret 2004-02-10 15:24:09 UTC

carpaski has some new portage rescue tarballs on his dev.gentoo.org site, which
if I'm not mistaken replace those in /usr/portage/sys-apps/portage/files/.

Comment 3 Nicholas Jones (RETIRED) gentoo-dev

2004-02-10 23:30:31 UTC

There is a portage-2.0.50-r1 rescue tarball available.
See the readme.