Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 62889 - emerge fails with "object doesn't support item deletion"
Summary: emerge fails with "object doesn't support item deletion"
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High blocker (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
: 62945 69203 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-09-05 00:01 UTC by Joerg Plate
Modified: 2004-10-28 06:18 UTC (History)
8 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Plate 2004-09-05 00:01:20 UTC
Reproducible: Always
Steps to Reproduce:
1. emerge py-rrdtool

Actual Results:  
!!! object doesn't support item deletion 
!!! '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) 
 

Expected Results:  
emerge py-rrdtool 
 

"emerge info" doesn't work
Comment 1 Sebastian Bergmann (RETIRED) gentoo-dev 2004-09-05 00:17:45 UTC
I get the same error after I did an "emerge sync" this morning.
Comment 2 alex f 2004-09-05 05:15:07 UTC
Same here Comment #2. Deleting the profiles dir and re-sync does not help. Error stays the same
Comment 3 Sebastian Bergmann (RETIRED) gentoo-dev 2004-09-05 06:43:52 UTC
Update: I am experiencing this issue with portage-2.0.50-r10.
Comment 4 Jason Stubbs (RETIRED) gentoo-dev 2004-09-05 07:34:05 UTC
What does the following give?

ls -l /etc | grep make.profile
Comment 5 Sebastian Bergmann (RETIRED) gentoo-dev 2004-09-05 08:02:24 UTC
make.profile -> /usr/portage/profiles/default-linux/x86/2004.2/gcc34/2.6
Comment 6 Marc Hildebrand (RETIRED) gentoo-dev 2004-09-05 11:00:38 UTC
Ok, this did the trick for me:
Switch the symlink (/etc/make.profile) back to '/usr/portage/default-x86-2004.2'.
Upgrade to newest (masked) portage which is 2.0.51_pre20 atm.
Link /etc/make.profile to '/usr/portage/profiles/default-linux/x86/2004.2/gcc34/2.6' again.
Portage Team: please confirm this, ymmv
Cheers,
Marc.
Comment 7 Jason Stubbs (RETIRED) gentoo-dev 2004-09-05 16:10:04 UTC
*** Bug 62945 has been marked as a duplicate of this bug. ***
Comment 8 Disenchanted (RETIRED) gentoo-dev 2004-09-06 01:29:21 UTC
ok, seems there is a bug in 2.0.50 parsing cascaded profiles, the make.defaults files are adjusted to this, thanks to jstubbs
please sync 35 mins after reading this comment and test with your portage 2.0.50-r10
thank you

Daniel
Comment 9 Pete Plank 2004-09-06 15:13:57 UTC
Problem persists - tried again just five minutes ago.
Comment 10 Disenchanted (RETIRED) gentoo-dev 2004-09-06 22:09:45 UTC
the problem is in the CFLAGS in make.defaults
2.0.50 reacts to them differently than 2.0.51
i took out CFLAGS for now until i get a chance to get some longer talk with carpaski in regards to cascading profiles
Comment 11 Nicholas Jones (RETIRED) gentoo-dev 2004-09-07 16:51:28 UTC
It may be quicker for 2.0.51 to come out than to fix this "broken"
(read: historically incorrect) CFLAGS. The backport would be fairly
sizable to update the cascade functions.

I recommend using 51, unless -r12 happens to have the backport.
Comment 12 Nicholas Jones (RETIRED) gentoo-dev 2004-09-21 17:58:20 UTC
Use 51 for cascades.
Comment 13 Jason Stubbs (RETIRED) gentoo-dev 2004-10-28 06:18:16 UTC
*** Bug 69203 has been marked as a duplicate of this bug. ***