Bug 262485 – sys-apps/portage-2.{1.6.7,2_rc25} - quickpkg: traceback on invalid package atoms

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Lars Wendler (Polynomial-C) (RETIRED) 2009-03-14 22:32:21 UTC]

After I mistyped a package's atom, I got the following traceback on quickpkg from either portage-2.1.6.7 or portage-2.2_rc25:

zeromancer:~ # quickpkg --include-config=y =db:4.7
Traceback (most recent call last):
  File "/usr/sbin/quickpkg", line 227, in <module>
    retval = quickpkg_main(options, args, eout)
  File "/usr/sbin/quickpkg", line 38, in quickpkg_main
    atom = dep_expand(arg, mydb=vardb, settings=vartree.settings)
  File "//usr/lib64/portage/pym/portage/__init__.py", line 6903, in dep_expand
    return portage.dep.Atom(prefix + expanded + postfix)
  File "//usr/lib64/portage/pym/portage/dep.py", line 496, in __call__
    instance = super(_AtomCache, cls).__call__(s)
  File "//usr/lib64/portage/pym/portage/dep.py", line 527, in __init__
    raise InvalidAtom(s)
portage.exception.InvalidAtom: =sys-libs/db:4.7
zeromancer:~ #

Since the package atoms are invalid anyway, I marked this bug as trivial.

Reproducible: Always

[Comment 1 Zac Medico 2009-03-17 05:36:07 UTC]

Thanks, this is fixed in svn r13116.

[Comment 2 Zac Medico 2009-03-17 20:49:04 UTC]

This is fixed in 2.1.6.9 and 2.2_rc26.