Bug 96679 – emerge -aUDN causes portage traceback with vmware-workstation-5.0.0.13124-r1

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Jules Colding 2005-06-21 02:39:56 UTC]

I did:

    emerge -vaUDN world

and got:

omc-1 ~ # emerge -vaUDN world

*** Warning: --upgradeonly is a deprecated option in portage-2.0.51.19
***          and will likely be removed in a future version.

>>> --upgradeonly implies --update... adding --update to options.

These are the packages that I would merge, in order:

Calculating world dependencies |!!! aux_get(): ebuild path for
'app-emulation/vmware-workstation-5.0.0.13124' not specified:
!!!            None
Traceback (most recent call last):
  File "/usr/bin/emerge", line 2986, in ?
    if not mydepgraph.xcreate(myaction):
  File "/usr/bin/emerge", line 1360, in xcreate
    if not self.create(myk,myuse=binpkguseflags):
  File "/usr/bin/emerge", line 916, in create
    iuses=string.split(portage.portdb.aux_get(mykey, ["IUSE"])[0])
  File "/usr/lib/portage/pym/portage.py", line 5162, in aux_get
    raise KeyError, "'%(cpv)s' at %(path)s" % {"cpv":mycpv,"path":myebuild}
KeyError: "'app-emulation/vmware-workstation-5.0.0.13124' at None"


Reproducible: Always
Steps to Reproduce:
1. emerge --sync
2. emerge -vaUDN world
3.

Actual Results:  
As described in "Details".

Expected Results:  
vmware, and all other due packages, should have been updated.

I am unsure whether this is an RTFM-kind of bug or a real one...

[Comment 1 Jason Stubbs (RETIRED) 2005-06-21 05:40:06 UTC]

Does it happen every time? Does it happen if you use -u instead of -U? 

[Comment 2 Jules Colding 2005-06-21 05:56:08 UTC]

It happens everytime, yes. I can s/U/u but then it wants me to downgrade to
4.5.2.8848-r6.

[Comment 3 Jakub Moc (RETIRED) 2005-06-21 06:01:55 UTC]

(In reply to comment #2)
> It happens everytime, yes. I can s/U/u but then it wants me to downgrade to
> 4.5.2.8848-r6.

Then put it into /etc/portage/package.keywords and/or package.unmask as
appropriate. Don't use deprecated and broken features like --upgradeonly, it's
evil! See man emerge and man portage.

[Comment 4 Jason Stubbs (RETIRED) 2005-06-21 06:09:01 UTC]

Does that mean you don't get any traceback if you use -u? 

[Comment 5 Jules Colding 2005-06-21 06:13:54 UTC]

(In reply to comment #4)
> Does that mean you don't get any traceback if you use -u? 

Yes.

[Comment 6 Zac Medico 2005-08-08 04:01:51 UTC]

(In reply to comment #2)
> I can s/U/u but then it wants me to downgrade to 4.5.2.8848-r6.

You should mask the lower version in order to prevent downgrade (like Jakub said
in comment #3).  Here's an example:

echo "<app-emulation/vmware-workstation-5.0.0.13124" >> /etc/portage/package.mask

[Comment 7 Zac Medico 2005-08-08 04:13:23 UTC]

(In reply to comment #0)
>   File "/usr/lib/portage/pym/portage.py", line 5162, in aux_get
>     raise KeyError, "'%(cpv)s' at %(path)s" % {"cpv":mycpv,"path":myebuild}
> KeyError: "'app-emulation/vmware-workstation-5.0.0.13124' at None"

This traceback is very similar to bug 85796 and bug 97969.

[Comment 8 Brian Harring (RETIRED) 2005-08-09 02:43:12 UTC]

able to hit it with .22?

[Comment 9 Jules Colding 2005-08-09 02:56:38 UTC]

Pardon my ignorance, but ".22" what?

[Comment 10 Zac Medico 2005-08-09 03:01:20 UTC]

LOL, portage-2.0.51.22

[Comment 11 Jules Colding 2005-08-10 02:06:38 UTC]

portage-2.0.51.22 does indeed seem to fix the problem. 

[Comment 12 Chris Gianelloni (RETIRED) 2005-08-10 17:20:24 UTC]

Fixed in latest stable portage...