emerge: KeyError (dev-perl/DateTime-0.2901)

Message

Mad_Jester · Post by **Mad_Jester** » Wed Jan 18, 2006 12:36 am

After doing an emerge sync, I am getting this error everytime I try to run emerge. Can someone tell me what is wrong here?

emerge -V

Performing Global Updates: /usr/portage/profiles/updates/1Q-2006
(Could take a couple of minutes if you have a lot of binary packages.)
.='update pass' *='binary update' @='/var/db move'
s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*'
........Traceback (most recent call last):
File "/usr/bin/emerge", line 10, in ?
import portage
File "/usr/lib/portage/pym/portage.py", line 7480, in ?
do_upgrade(mykey)
File "/usr/lib/portage/pym/portage.py", line 7372, in do_upgrade
db["/"]["vartree"].dbapi.move_ent(mysplit)
File "/usr/lib/portage/pym/portage.py", line 4683, in move_ent
origmatches=self.match(origcp,use_cache=0)
File "/usr/lib/portage/pym/portage.py", line 4829, in match
return match_from_list(mydep,self.cp_list(mykey,use_cache=use_cache))
File "/usr/lib/portage/pym/portage.py", line 4134, in match_from_list
raise KeyError, "Specific key requires an operator (%s) (try adding an '=')" % (mydep)
KeyError: "Specific key requires an operator (dev-perl/DateTime-0.2901) (try adding an '=')"

Edit: Changed title from '"emerge errors" and stuck temporarily. --Maedhros

mattjgalloway · Post by **mattjgalloway** » Wed Jan 18, 2006 12:37 am

Yep I get this too.

Oh dear, something is fooked here! NOT GOOD!

Lol wow we must have literally updated our portage at the same time as I just found your post 1 minute after you posted it! I'm in the process of trying to sort it out. I think I may be onto something and I'll let you know.

By the way, I am AMD64.

m0rpheus13 · Post by **m0rpheus13** » Wed Jan 18, 2006 12:43 am

i just started getting the same errors... anyone know of a fix?

micmac · Post by **micmac** » Wed Jan 18, 2006 12:47 am

Haha, me too

Can't do nothing:

Code: Select all

emerge sync


Performing Global Updates: /usr/portage/profiles/updates/1Q-2006
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  @='/var/db move'
  s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*'
........Traceback (most recent call last):
  File "/usr/bin/emerge", line 10, in ?
    import portage
  File "/usr/lib/portage/pym/portage.py", line 7480, in ?
    do_upgrade(mykey)
  File "/usr/lib/portage/pym/portage.py", line 7372, in do_upgrade
    db["/"]["vartree"].dbapi.move_ent(mysplit)
  File "/usr/lib/portage/pym/portage.py", line 4683, in move_ent
    origmatches=self.match(origcp,use_cache=0)
  File "/usr/lib/portage/pym/portage.py", line 4829, in match
    return match_from_list(mydep,self.cp_list(mykey,use_cache=use_cache))
  File "/usr/lib/portage/pym/portage.py", line 4134, in match_from_list
    raise KeyError, "Specific key requires an operator (%s) (try adding an '=')" % (mydep)
KeyError: "Specific key requires an operator (dev-perl/DateTime-0.2901) (try adding an '=')"

Poeple better not sync tonight until this gets fixed.

mattjgalloway · Post by **mattjgalloway** » Wed Jan 18, 2006 12:48 am

Ok I have a kinda fix.

Do an emerge-webrsync and your portage will now work again as it reverts to one a few days ago. But it's definately NOT a complete fix as if you do an emerge sync again soon it'll mess up.

Gentoo really has made a mess up here as people will have serious problems if their servers 'emerge sync' every night.

Come on devs, this is serious, sort it please!

napgravy · Post by **napgravy** » Wed Jan 18, 2006 12:54 am

Looks to be a problem in /usr/portage/profiles/updates/1Q-2006

I suspect the last line should read

Code: Select all

move =dev-perl/DateTime-0.2901 =dev-perl/DateTime-0.29.01

Instead of

Code: Select all

move dev-perl/DateTime-0.2901 dev-perl/DateTime-0.29.01

Making this change will allow portage to "work" - but until the mirrors get a proper 1Q-2006 file, you'll just be in the same boat after your next sync.

I could be way out to lunch here - I am not a portage guru.

nap

Glorandar · Post by **Glorandar** » Wed Jan 18, 2006 12:56 am

The file /usr/portage/profiles/updates/1Q-2006's last line (about moving perl) is badly formed.

I just deleted that last line, so that 1Q-2006 now contains:

Code: Select all

slotmove dev-util/gambas 0 1
move dev-libs/wefts dev-cpp/libwefts
move dev-libs/mxmlplus dev-cpp/libmxmlplus
slotmove =gnome-extra/libgtkhtml-2* 1 2
slotmove =gnome-extra/gtkhtml-1* 0 1
move gnome-extra/libgtkhtml gnome-extra/gtkhtml
move dev-util/screem app-editors/screem

Now my portage is back to normal.

I suspect there will be an update to that file soon...

tommoyer324 · Post by **tommoyer324** » Wed Jan 18, 2006 1:00 am

I too had the same problem. The post above about adding the equal sign works as a temporary fix. At least until they get things sorted out.

mattjgalloway · Post by **mattjgalloway** » Wed Jan 18, 2006 1:01 am

Seems like they are fixing it as we speak, wow I love Gentoo!

I'm emerge syncing to see if it works now.

Devs you rock.

Genone · Post by **Genone** » Wed Jan 18, 2006 1:02 am

Fixed it in the tree, should hit rsync in the next hour, you'll have to remove /usr/portage/profiles/updates/1Q-2006 manually though before syncing.
Will kick the dev who did that hard

jstubbs · Post by **jstubbs** » Wed Jan 18, 2006 1:02 am

In the file /usr/portage/profiles/updates/1Q-2006 remove the line:

move dev-perl/DateTime-0.2901 dev-perl/DateTime-0.29.01

Forwarding the bug to the person responsible now.

NightMonkey · Post by **NightMonkey** » Wed Jan 18, 2006 1:04 am

Same problem. = sign change appears to work.

dufeu · Post by **dufeu** » Wed Jan 18, 2006 1:08 am

Genone wrote:Fixed it in the tree, should hit rsync in the next hour, you'll have to remove /usr/portage/profiles/updates/1Q-2006 manually though before syncing.
Will kick the dev who did that hard

No need to kick the dev hard. Finding the fix in the Forums within 60 seconds of encountering it makes up for alot. Just kick the responsible dev a little bit. ;-D

derk · Post by **derk** » Wed Jan 18, 2006 1:08 am

yep the "emerge-webrsync" does the trick .

how many people caught by this are running portage-2.1_pre3-r1 does it also effect earlier version.

I filed bug #119352 for this problem. ... but by the time I returned here fixes and work arounds abound ...

mattjgalloway · Post by **mattjgalloway** » Wed Jan 18, 2006 1:09 am

Yes I must say this is a complete testament to the fact that open source software works. This would have taken a closed source OS like Windows about a week to fix. You Gentoo devs updated the mirrors within a few minutes of finding the bug. I'm impressed.

micmac · Post by **micmac** » Wed Jan 18, 2006 1:10 am

jstubbs wrote:In the file /usr/portage/profiles/updates/1Q-2006 remove the line:

move dev-perl/DateTime-0.2901 dev-perl/DateTime-0.29.01

Forwarding the bug to the person responsible now.

Be kind

It's just a typo. portage should be able to handle that. It's not the guys fault that it apparently can't.

Cheers

mic

fraterm · Post by **fraterm** » Wed Jan 18, 2006 1:14 am

dufeu wrote:
Genone wrote:Fixed it in the tree, should hit rsync in the next hour, you'll have to remove /usr/portage/profiles/updates/1Q-2006 manually though before syncing.
Will kick the dev who did that hard

No need to kick the dev hard. Finding the fix in the Forums within 60 seconds of encountering it makes up for alot. Just kick the responsible dev a little bit. ;-D

I agree, only a small tap is necessary.

rsa4046 · Post by **rsa4046** » Wed Jan 18, 2006 1:22 am

mattjgalloway wrote:Yes I must say this is a complete testament to the fact that open source software works. This would have taken a closed source OS like Windows about a week to fix.

Aint that the truth --- make that 3-4 patches from WU within as many weeks just to finally get it right, with 20 reboots each time.

mattjgalloway wrote: You Gentoo devs updated the mirrors within a few minutes of finding the bug. I'm impressed.

Hats off to the devs.

mattjgalloway · Post by **mattjgalloway** » Wed Jan 18, 2006 1:26 am

Yep if I could, I'd buy you all a pint.

Give yourselves a round of applause guys!

Genone · Post by **Genone** » Wed Jan 18, 2006 1:31 am

FYI: It is not a typo, adding a = will make the error message go away, however that entry would still be broken and not work.
The dev simply assumed that something works and didn't do any research while what he intended defintely doesn't work.

agent_jdh · Post by **agent_jdh** » Wed Jan 18, 2006 1:41 am

Genone wrote:FYI: It is not a typo, adding a = will make the error message go away, however that entry would still broken and not work.
The dev simply assumed that something works and didn't do any research while what he intended defintely doesn't work.

So deleting the line is the correct fix? It seems to have worked here.

Genone · Post by **Genone** » Wed Jan 18, 2006 1:42 am

agent_jdh wrote:
Genone wrote:FYI: It is not a typo, adding a = will make the error message go away, however that entry would still broken and not work.
The dev simply assumed that something works and didn't do any research while what he intended defintely doesn't work.
So deleting the line is the correct fix? It seems to have worked here.

Yes. Adding a = in front doesn't break anything, that entry will simply not work as intended (which doesn't have any implications in this case)

dufeu · Post by **dufeu** » Wed Jan 18, 2006 1:43 am

Genone wrote:The dev simply assumed t ...

It did have that kind of feel to it. As a programmer in a dead legacy language, I understand the pitfalls of assumptions. You know: been there, done that, have the T-shirt/scars to prove it.

It took me one day to modify a legacy label printing program to add new functionality to it. It's taken me 8 working days to test it so far. I expect to be done testing tommorrow. Then I have to write some one off reports to show the effected products before and after.

One day of programming labor - Twelve days of testing and impact research. It's not always easy to test one's own work. But the company I work for would rather pay to get it right the first time than to have everyone disrupted. As a result, I'm pretty tolerant of other people's faux pax. Just so long as they don't let it happen again!

Edit: BTW - thank you very, very much for the quick fix. 'Tis sincerely appreciated.

LostSon · Post by **LostSon** » Wed Jan 18, 2006 1:46 am

whew came back today and thought something was seriously messed up, thanks for the quick fix!!

BillyBob-SA1 · Post by **BillyBob-SA1** » Wed Jan 18, 2006 1:46 am

Well I am impressed so I will add another #1 disto vote here!