After execution of "emerge --sync", I get the following output: >>> Updating Portage cache: 88%!!! Cannot resolve a virtual package name to an ebuild. !!! This is a bug, please report it. (virtual/libintl-0) beryl root # emerge --info Portage 2.0.51.19 (default-linux/mips/cobalt/2005.0, gcc-3.4.3,glibc-2.3.4.20050125-r1,glibc-2.3.4.20040619-r2,2.4.31-mipscvs-20050606 mips) ================================================================= System uname: 2.4.31-mipscvs-20050606 mips Nevada V10.0 FPU V10.0 Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Apr 30 2005, 02:31:05)] dev-lang/python: 2.3.4-r1 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.91.0.2-r1 sys-devel/libtool: 1.5.14 virtual/os-headers: 2.4.21-r3 ACCEPT_KEYWORDS="mips" AUTOCLEAN="yes" CFLAGS="-O2 -mips4 -mabi=32 -fomit-frame-pointer" CHOST="mipsel-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mips4 -mabi=32 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sfperms strict" GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://distro.ibiblio.org/pub/linux/distributions/gentoo/ http://www.gtlib.gatech.edu/pub/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="mips berkdb bitmap-fonts bzip2 cobalt expat fortran gdbm gpm libwww ncurses nls nomultilib pam perl python readline sdl ssl tcpd truetype-fonts type1-fonts zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY Platform is a Cobalt RaQ2.
this is a dupe of many other bugs. solution: update your portage first.
*** This bug has been marked as a duplicate of 114798 ***
Perhaps you didn't notice the "emerge --sync"? Is there something else you mean by "update your portage first"? Perhaps you could point me at the FM for me to R? If you don't want the bugs reported, then perhaps you shouldn't have it spit out "This is a bug, please report it."
Implicit in 'please report it' is 'please check whether anyone has reported it, and if not then do so'.
(In reply to comment #3) > Is there something else you > mean by "update your portage first"? That means `emerge portage` (update sys-apps/portage).
Zac, thanks for the pointer. What mistake am I making here? beryl root # emerge portage Calculating dependencies ...done! >>> emerge (1 of 1) sys-apps/portage-2.0.51.22-r3 to / !!! Security Violation: A file exists that is not in the manifest. !!! File: files/2.1_pre4-r1.patch
(In reply to comment #6) > !!! Security Violation: A file exists that is not in the manifest. > !!! File: files/2.1_pre4-r1.patch Well, that file is in the manifest, so it seems like your portage is too old to parse the current manifest format. You can disable the security check with `env FEATURES=-strict emerge portage` (at your own risk, of course).
Hmm... this could be preemptively worked around at a global level. FEATURES="strict" was never set in make.globals for any of the releases that will have problems. If it is removed from make.defaults in the profiles and added to make.globals (if it's not there already) in forthcoming releases, the transition should be a little bit smoother...
Zac, that seemed to resolve the issue for me...thanks!
