Just did an emerge sync and here is what i get: !!! 'str' object has no attribute 'insert' !!! 'rm -Rf /usr/portage/profiles; emerge sync' may fix this. If it does !!! not then please report this to bugs.gentoo.org and, if possible, a dev !!! on #gentoo (irc.freenode.org) Several other people on #gentoo are reporting the same problem. Of course I removed my profiles dir, but that didn't had any effect. Any ideas? Reproducible: Always Steps to Reproduce: * emerge sync (you get the error) * emerge -s test (you get the error)
BTW, my portage version (can only be asked after deleting the profiled dir) is: $ emerge -V --- 'profiles/arch.list' is empty or not available. Empty portage tree? Portage 2.0.50-r11 (gcc34-2004.2, gcc-3.4.1, glibc-2.3.4.20040808-r0, 2.6.7-gentoo-r14)
OK, i kinda "fixed" the problem (although "workarounded" describes it better). I manually upgraded my portage to version .51_pre2. Seems like my profile (default-linux/amd64/gcc34-2004.2) have some problem with my "old" (newest in ~amd64) portage version. Things seems to work alright now.
*** Bug 63404 has been marked as a duplicate of this bug. ***
*** Bug 63410 has been marked as a duplicate of this bug. ***
same prob here, using portage-2.0.50-r11 and profile default-linux/amd64/gcc34-2004.2 emerge -d just produces the error as above.
The problem was incompatible entries in some of the profile files.
same Problem here but I use /etc/make.profile -> /usr/portage/profiles/default-linux/x86/2004.2
emerge -d procudes the error-message. My profile is default-linux/amd64/gcc34-2004.2
Same thing here, with profile default-linux/amd64/gcc34-2004.2
It appears that emerge refuses to work, even to the extent of 'emerge --version' performing the rm -Rf /usr/portage/profiles makes 'emerge --version' work once more. Performing an 'strace emerge --version' shows that immediately after reading the "/usr/portage/profiles/default-linux/x86/2004.2/make.defaults" file, the message is generated (no intervening system calls) 'emerge -d' generates nothing but the error message. /etc/make.conf =-=-=- # These settings were set by the catalyst build script that automatically built this stage # Please consult /etc/make.conf.example for a more detailed example CFLAGS="-O3 -mcpu=i686 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CXXFLAGS="${CFLAGS}" MAKEOPTS="-j3" # This one uses Internode - which appears to be slightly out of sync GENTOO_MIRRORS="ftp://mirror.internode.on.net/pub/gentoo ftp://mirror.pacific.net.au/linux/Gentoo http://mymirror.asiaosc.org/gentoo/ http://www.zentek-international.com/mirrors/gentoo/ http://open-systems.ufl.edu/mirrors/gentoo http://www.ibiblio.org/pub/Linux/distributions/gentoo" # this one uses the official mirrors - just not free to me. #GENTOO_MIRRORS="ftp://mirror.pacific.net.au/linux/Gentoo http://mirror.internode.on.net/pub/gentoo ftp://mirror.aarnet.edu.au/pub/gentoo http://mymirror.asiaosc.org/gentoo/ http://www.zentek-international.com/mirrors/gentoo/ http://open-systems.ufl.edu/mirrors/gentoo http://www.ibiblio.org/pub/Linux/distributions/gentoo" SYNC="rsync://mirror.internode.on.net/gentoo-portage" #SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" AUTOCLEAN="yes" FEATURES="sandbox userpriv usersandbox" # PORT_LOGDIR=/var/log/emerge =-=-=- /usr/portage/profiles/default-linux/x86/2004.2/make.defaults =-=-=- # Copyright 1999-2004 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/profiles/default-linux/x86/2004.2/make.defaults,v 1.3 2004/08/25 13:58:05 vapier Exp $ # # System-wide defaults for the Portage system # See portage(5) manpage GRP_STAGE23_USE="ipv6 pam tcpd readline nls ssl gpm perl python berkdb acl ncurses" # Please avoid enabling things by default in here if possible. Understand any # implications with core packages. For example, if "java" is in USE and db # has a conditional dependency on java (which it does,) then a JDK will be # pulled in during *emerge system*! USE="x86 oss apm arts avi berkdb crypt cups encode foomaticdb gdbm gif gpm gtk gtk2 imlib jpeg kde gnome libg++ libwww mad mikmod motif mpeg ncurses nls oggvorbis opengl pam pdflib png python qt quicktime readline sdl slang spell ssl svga tcpd truetype X xml2 xmms xv zlib" ARCH="x86" ACCEPT_KEYWORDS="x86" FEATURES="sandbox sfperms" =-=-=-
It seems there are incompatible USE flags in the profiles, as commenting out the USE line makes emerge work again !
*** Bug 63422 has been marked as a duplicate of this bug. ***
*** Bug 63426 has been marked as a duplicate of this bug. ***
for most people, just remove /usr/portage/profiles/base/make.defaults and this should go away for amd64 users, make sure you only have 1 make.defaults in your stacking profile path i'll fix this up in cvs
I switched from /etc/make.profile -> /usr/portage/profiles/default-linux/x86/2004.2 to make.profile -> /usr/portage/profiles/default-x86-2004.2 that fixed it.
is it fixed already? i did an emerge sync and now it works...
Yes, it seems to be also fixed for me, thanks for the work !
Fixed here too, marked as FIXED.
Not fixed... :( Just synced (Duron - ~x86): >>> Updating Portage cache... ...done! !!! 'str' object has no attribute 'insert' !!! 'rm -Rf /usr/portage/profiles; emerge sync' may fix this. If it does !!! not then please report this to bugs.gentoo.org and, if possible, a dev !!! on #gentoo (irc.freenode.org) ls -l /etc/make.profile: /etc/make.profile -> ../usr/portage/profiles/hardened/x86
I just synced the tree and got this error. I removed /usr/portage/profile and resynced. That didn't work /etc/make.profile -> /usr/portage/profiles/default-linux/x86/2004.2 my ACCEPT_KEYWORDS is set to "x86".
changing /etc/make.profile -> /usr/portage/profiles/default-linux/x86/2004.2 to /etc/make.profile -> /usr/portage/profiles/default-x86-2004.2 solved the problem
it's very simple if you're going to use cascading profiles, use 2.0.51 or better we're not going to hold back cascading profiles for users who refuse to upgrade
*** Bug 69357 has been marked as a duplicate of this bug. ***
Additional Comment #21 of this bug solved my problem.
*** Bug 69401 has been marked as a duplicate of this bug. ***
*** Bug 69733 has been marked as a duplicate of this bug. ***
*** Bug 70173 has been marked as a duplicate of this bug. ***
*** Bug 70181 has been marked as a duplicate of this bug. ***
*** Bug 70823 has been marked as a duplicate of this bug. ***
Fwiw, simply changinng the symlink didn't fix it for me. I had to remove the symlink to the new version, run emerge -up world (or anything that touched emerge) and *then* make the symlink back to the old default-x86- version. (Without running emerge, I continued to get the same error message, even when the symlink was pointing to a compatible version).
So the moral of the story is: When portage told us to upgrade to >=2.0.51 *first* and *then* change the symlink, we should have followed those directions. The /usr/portage/profiles/default-linux/x86/2004.3 profile works great *if* you first upgrade portage!!
*** Bug 71824 has been marked as a duplicate of this bug. ***
When I originally got the message to update my make.profile to 2004.3, there was not any message about updating portage first. I got the message on three different computers and definately didn't see it on any of them.
*** Bug 72544 has been marked as a duplicate of this bug. ***
*** Bug 72980 has been marked as a duplicate of this bug. ***
For those of you that are having this problem with SELINUX, the solution is a little bit less straightforward. There is no flat SELINUX profile any more. To get an SELINUX system's portage upgraded to 2.0.51: # export ARCH="$(portageq envvar ARCH)" # export ACCEPT_KEYWORDS="$(portageq envvar ACCEPT_KEYWORDS)" # MYPROFILE="$(readlink -f /etc/make.profile)" # rm /etc/make.profile # emerge -u portage # ln -s "$MYPROFILE" /etc/make.profile Actually, that process should work for anybody.
Sorry, Jason, your suggestion failed. # export ARCH="$(portageq envvar ARCH)" # export ACCEPT_KEYWORDS="$(portageq envvar ACCEPT_KEYWORDS)" produced null strings since portageq is returning the same error that emerge is returning. I did manage to figure out what they should be set to by reading /etc/make.profile/make.defaults. Once I set the variables according to what was there. . . # emerge -u portage produced the following output: !!! /etc/make.profile is not a symlink and will probably prevent most merges. !!! It should point into a profile within /usr/portage/profiles/ !!! (You can safely ignore this message when syncing. It's harmless.) Calculating dependencies / emerge: there are no masked or unmasked ebuilds to satisfy virtual/libc !!! Error calculating dependencies. Please correct. --- BUT --- Setting /etc/make.profile as a link to /usr/portage/profiles/hardened/x86 appears to work (at least at this point, it's in the process of downloading a bunch of stuff. . .)
Yes, you're right. Well, for those that can't figure it out, ARCH and ACCEPT_KEYWORDS should be your architecture's keyword, as per $PORTDIR/profiles/arch.list. The dependency problems can be bypassed with --nodeps, but selinux people should also make sure dev-python/python-selinux is installed.
You don't suppose this may be related to copying the /etc directory from one installation to another, do you? In my case I hozed a perfectly updated and smooth system and the solution was to reinstall - which I did. I then put in my original /etc components. This is the first trouble I noticed. The other was the strange circumstance of missing man pages.... notably: # man emerge gave me an empty page. Ok (sez I), I'll just emerge emerge. Got the error. I changed the link to make.profile and "emerge emerge" seems to be working now; but! after the first dependency, emerge repointed the make.profile to the original location. We'll see. I can not run emerge --sync from here. Firewall. emerge-webrsync functions but didn't help.
*** Bug 76934 has been marked as a duplicate of this bug. ***
*** Bug 78318 has been marked as a duplicate of this bug. ***
*** Bug 82094 has been marked as a duplicate of this bug. ***
*** Bug 84899 has been marked as a duplicate of this bug. ***
*** Bug 94166 has been marked as a duplicate of this bug. ***
*** Bug 96316 has been marked as a duplicate of this bug. ***
For SELinux users during bootstrap: rm /etc/make.profile ln -s /usr/portage/profiles/hardened/x86/2.6 /etc/make.profile export ARCH="x86" export ACCEPT_KEYWORDS="x86" cd /usr/portage scripts/bootstrap.sh And it worked :)
*** Bug 102614 has been marked as a duplicate of this bug. ***
the only upgrade people have now is to set their profile to one of the obsolete ones, upgrade portage, and then continue on their way: rm -f /etc/make.profile ln -s /usr/portage/profiles/obsolete/<ARCH> /etc/make.profile
*** Bug 102696 has been marked as a duplicate of this bug. ***
*** Bug 103532 has been marked as a duplicate of this bug. ***
*** Bug 104755 has been marked as a duplicate of this bug. ***
*** Bug 104803 has been marked as a duplicate of this bug. ***
*** Bug 107591 has been marked as a duplicate of this bug. ***
*** Bug 112340 has been marked as a duplicate of this bug. ***
*** Bug 118498 has been marked as a duplicate of this bug. ***
*** Bug 123768 has been marked as a duplicate of this bug. ***
*** Bug 129303 has been marked as a duplicate of this bug. ***
could not emerge portage or fix anything because /bin/sed got deleted during the initial update (that failed) copied sed from another 2004.2 gentoo box to /bin then followed #49
*** Bug 147105 has been marked as a duplicate of this bug. ***
*** Bug 183930 has been marked as a duplicate of this bug. ***
