I am new to portage-prefix, but not to gentoo. I followed the instructions for installing prefix portage to the letter and I get this after I've finished bootstrapping: Following this manual: http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml At code listing: 1.6 emerge --oneshot "=sys-apps/sed-4.1.4*" returns: <snip> Calculating dependencies !!! All ebuilds that could satisfy "=sys-apps/sed-4.1.5*" have been masked. !!! One of the following masked packages is required to complete your request: - sys-apps/sed-4.1.5 (masked by: required EAPI -0, supported EAPI prefix) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. </snip> I have not modified anything from the original instructions. All defaults are left as they were.
Oops... I tried both versions of sed and pasted the wrong one from my terminal.
Sorry, I slack for not having made that new snapshot, sorry. Please watch bug #187839. I'm really sorry for this. *** This bug has been marked as a duplicate of bug 187839 ***
Calculating dependencies !!! All ebuilds that could satisfy "sed" have been masked. !!! One of the following masked packages is required to complete your request: - sys-apps/sed-4.1.5 (masked by: required EAPI -0, supported EAPI prefix) - sys-apps/sed-4.1.4-r1 (masked by: required EAPI -0, supported EAPI prefix) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. % emerge --info !!! Problem with sandbox binary. Disabling... Portage 2.2.00.7571-prefix (default-prefix/linux/x86, gcc-3.4.3, unavailable, 2.6.9-11.ELsmp i686) ================================================================= System uname: 2.6.9-11.ELsmp i686 unknown Unknown Host Operating System Timestamp of tree: Unknown ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf" DISTDIR="/home/dlamotte/portage/linux-32-brazil/usr/portage/distfiles" EPREFIX="/home/dlamotte/portage/linux-32-brazil" FEATURES="collision-protect distlocks metadata-transfer sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LC_ALL="C" LDFLAGS="-Wl,-search_paths_first -L/home/dlamotte/portage/linux-32-brazil/usr/lib -L/home/dlamotte/portage/linux-32-brazil/ lib" PKGDIR="/home/dlamotte/portage/linux-32-brazil/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-afte r --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/home/dlamotte/portage/linux-32-brazil/var/tmp" PORTDIR="/home/dlamotte/portage/linux-32-brazil/usr/portage" SYNC="svn+http://overlays.gentoo.org/svn/proj/alt/trunk/prefix-overlay" USE="cracklib iconv midi mudflap ncurses openmp prefix readline ssl x86 zlib" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix d share dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm s oftvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" Unset: CFLAGS, CTARGET, CXXFLAGS, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LINGUAS, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_CO MPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
(In reply to comment #3) > - sys-apps/sed-4.1.5 (masked by: required EAPI -0, supported EAPI prefix) > - sys-apps/sed-4.1.4-r1 (masked by: required EAPI -0, supported EAPI prefix) It seems like the EAPI="-0" is being generated in ebuild.sh when it shouldn't be. Try adding 'set -x' at the top of ${PREFIX}/usr/lib/portage/bin/ebuild.sh and then run this command: ebuild $(equery which =sys-apps/sed-4.1.5) depend Post the bash trace that is produced and also the file that is generated at "${PREFIX}/var/cache/edb/dep/aux_db_key_temp".
Created attachment 128109 [details] trace log with "set -x" on here is the trace log but there was no other file that got generated: % find var/cache/ var/cache/ var/cache/edb var/cache/edb/dep var/cache/edb/dep/home var/cache/edb/dep/home/dlamotte var/cache/edb/dep/home/dlamotte/portage var/cache/edb/dep/home/dlamotte/portage/linux-32-brazil var/cache/edb/dep/home/dlamotte/portage/linux-32-brazil/usr var/cache/edb/dep/home/dlamotte/portage/linux-32-brazil/usr/portage var/cache/edb/dep/home/dlamotte/portage/linux-32-brazil/usr/portage/sys-apps var/cache/edb/dep/home/dlamotte/portage/linux-32-brazil/usr/portage/sys-apps/sed-4.1.5 var/cache/edb/dep/home/dlamotte/portage/linux-32-brazil/usr/portage/sys-apps/sed-4.1.4-r1 var/cache/edb/mtimedb contents of the sed files: <sed-4.1.5> _eclasses_= LICENSE= RESTRICT= SRC_URI= KEYWORDS= RDEPEND= SLOT= DEPEND= IUSE= HOMEPAGE= PROVIDE= PDEPEND= EAPI=-0 DESCRIPTION= CDEPEND= </sed-4.1.5> <sed-4.1.4-r1> _eclasses_= LICENSE= RESTRICT= SRC_URI= KEYWORDS= RDEPEND= SLOT= DEPEND= IUSE= HOMEPAGE= PROVIDE= PDEPEND= EAPI=-0 DESCRIPTION= CDEPEND= </sed-4.1.4-r1>
The trace shows that EBUILD_PHASE is unset and that variable is required for proper behavior of ebuild.sh. That variable is supposed to be set inside portage.doebuild_environment() but apparently it's getting lost somehow before ebuild.sh is called from portage.doebuild() (relevant functions are located in ${PREFIX}/usr/lib/portage/pym/portage/__init__.py). Maybe FEATURES=python-trace will show what went wrong: env FEATURES=python-trace ebuild --debug $(equery which =sys-apps/sed-4.1.5) \ depend &> debug.log
Created attachment 128191 [details] debug log the debug log from your ebuild command
Something in my environment that I had messed up the entire bootstrap as now I am able to emerge sed with no issues. I guess, a nice suggestion would be to do something to this regard before installing. % exec -c bash --norc --noprofile This fixed it for me. Then setup a very small PATH and go along with the install. Just a suggestion I guess. Any opinions?
(In reply to comment #8) > Just a suggestion I guess. Any opinions? Not really... without a cause, I can't fix this. Closing for now.