This is a request for different handling of a particular crash. I personally experienced this crash with portage version 2.1.6.13 that is in a recent stage3, but have subsequently lost the traceback after fixing the source of the problem. There is, however, a nearly identical crash that was caused by portage 2.2-r14. The invalid atom in my system was caused by a system crash while merging sys-power/acpid-1.0.10_p3. The resultant flawed atom was "sys-power/acpid:[". After much guesswork and log-reading I deleted /var/db/pkg/sys-power/acpid-1.0.10_p3/ and remerged it. Is it possible to have portage display the offending file in /var/db/pkg/, rather than giving vague clues to what's wrong? A better, more complicated solution would be displaying which package(s) has erroneous data in the pkg database and allowing those packages to be rebuilt, but that seem impractical. Reproducible: Always Steps to Reproduce: 1. Bork pkg/db 2. Try "emerge" or "emerge -p" 3. ????? 4. Profit Calculating dependencies Traceback (most recent call last): File "/usr/bin/emerge", line 40, in <module> retval = _emerge.emerge_main() File "//usr/lib/portage/pym/_emerge/__init__.py", line 15670, in emerge_main myopts, myaction, myfiles, spinner) File "//usr/lib/portage/pym/_emerge/__init__.py", line 14466, in action_build mydepgraph = depgraph(settings, trees, myopts, myparams, spinner) File "//usr/lib/portage/pym/_emerge/__init__.py", line 4549, in __init__ pkg_cache=self._pkg_cache) File "//usr/lib/portage/pym/_emerge/__init__.py", line 1217, in __init__ root_config=root_config, type_name="installed") File "//usr/lib/portage/pym/_emerge/__init__.py", line 1571, in __init__ self.slot_atom = portage.dep.Atom("%s:%s" % (self.cp, self.slot)) File "//usr/lib/portage/pym/portage/dep.py", line 496, in __call__ instance = super(_AtomCache, cls).__call__(s) File "//usr/lib/portage/pym/portage/dep.py", line 527, in __init__ raise InvalidAtom(s) InvalidAtom: net-libs/librpcsecgss: This someone posted at http://forums.gentoo.org/viewtopic-t-745058-highlight-invalidatom.html.
Are you able to reproduce this bug with sys-apps/portage-2.2_rc42?
*** This bug has been marked as a duplicate of bug 262211 ***
(In reply to comment #1) > Are you able to reproduce this bug with sys-apps/portage-2.2_rc42? > After re-installing sys-power/acpid, I couldn't reproduce the error in 2.1.6.13 even when trying to modify files in /var/db/pkg/. I did find that files in /var/db/pkg/dev-libs/libIDL-0.8.12 were loaded with what looked like logs from installing acpid, which makes me think that the invalid was from something in one of those files.
