!!! Invalid or corrupt dependency specification: invalid atom: '>=sys-libs/glibc-2.7*' ('ebuild', '/', 'sys-apps/iproute2-2.6.25.20080417', 'merge') !minimal? ( berkdb? ( sys-libs/db ) ) atm? ( net-dialup/linux-atm ) elibc_glibc? ( >=sys-libs/glibc-2.7* ) >=virtual/os-headers-2.6.25 This package can not be installed. Please notify the 'sys-apps/iproute2-2.6.25.20080417' package maintainer about this problem. ... done! Just remove the * and everything works fine here.
This causes a traceback on portage-2.2_rc1: Calculating dependencies \Traceback (most recent call last): File "/usr/bin/emerge", line 18, in <module> retval = _emerge.emerge_main() File "/usr/lib64/portage/pym/_emerge/__init__.py", line 9434, in emerge_main myopts, myaction, myfiles, spinner) File "/usr/lib64/portage/pym/_emerge/__init__.py", line 8611, in action_build retval, favorites = mydepgraph.select_files(myfiles) File "/usr/lib64/portage/pym/_emerge/__init__.py", line 2880, in select_files if not self._create_graph(): File "/usr/lib64/portage/pym/_emerge/__init__.py", line 2155, in _create_graph allow_unsatisfied=allow_unsatisfied): File "/usr/lib64/portage/pym/_emerge/__init__.py", line 2433, in _add_pkg_deps if not blocker and vardb.match(atom): File "/usr/lib64/portage/pym/_emerge/__init__.py", line 1062, in _match_wrapper matches = self._match(cpv, use_cache=use_cache) File "/usr/lib64/portage/pym/_emerge/__init__.py", line 1808, in match result = portage.dbapi.match(self, origdep, use_cache=use_cache) File "/usr/lib64/portage/pym/portage/dbapi/__init__.py", line 124, in match mydep = dep_expand(origdep, mydb=self, settings=self.settings) File "/usr/lib64/portage/pym/portage/__init__.py", line 5998, in dep_expand return portage.dep.Atom(prefix + expanded + postfix) File "/usr/lib64/portage/pym/portage/dep.py", line 400, in __init__ raise InvalidAtom(s) portage.exception.InvalidAtom: >=sys-libs/glibc-2.7* Portage didn't tell me it was iproute2 that was causing the problem. I had to go grepping through /usr/portage. After I figured out it was iproute2, I found this bug.
(In reply to comment #1) > This causes a traceback on portage-2.2_rc1: I got this same traceback doing "emerge -DNuva world". Just for the hell of it, I decided to switch options and tried "emerge -va world" which then reported the invalid glibc atom as in the description. I played around some more: emerge -uva world, emerge -Nuva world, emerge -Nva world ----> dep calc succeeded and portage let the emerge proceed emerge -Dva world ----> same as description emerge -Duva world ----> traceback This behavior seems...odd.
thx, downgrading to iproute2-2.6.24.20080108 solves the problem with "emerge --depclean" for me
Traceback with portage-2.1.5.6: Calculating dependencies -Traceback (most recent call last): File "/usr/bin/emerge", line 9277, in <module> retval = emerge_main() File "/usr/bin/emerge", line 9271, in emerge_main myopts, myaction, myfiles, spinner) File "/usr/bin/emerge", line 8530, in action_build retval, favorites = mydepgraph.select_files(myfiles) File "/usr/bin/emerge", line 3006, in select_files if not self._create_graph(): File "/usr/bin/emerge", line 2289, in _create_graph allow_unsatisfied=allow_unsatisfied): File "/usr/bin/emerge", line 2567, in _add_pkg_deps if not blocker and vardb.match(atom): File "/usr/bin/emerge", line 1233, in _match_wrapper matches = self._match(cpv, use_cache=use_cache) File "/usr/bin/emerge", line 1942, in match result = portage.dbapi.match(self, origdep, use_cache=use_cache) File "/usr/lib64/portage/pym/portage.py", line 6579, in match mydep = dep_expand(origdep, mydb=self, settings=self.settings) File "/usr/lib64/portage/pym/portage.py", line 5987, in dep_expand return portage_dep.Atom(prefix + expanded + postfix) File "/usr/lib64/portage/pym/portage_dep.py", line 289, in __init__ raise InvalidAtom(s) portage_exception.InvalidAtom: >=sys-libs/glibc-2.7*
I think it is not useful to post portage's logs and failures. We just need to wait until someone reassigned this bug and/or some dev correct this minor typo. As a workaround, you can remove this star from sys-libs/glibc-2.7* and put a modified ebuild in your personal overlay.
29 Jun 2008; Zac Medico <zmedico@gentoo.org> iproute2-2.6.25.20080417.ebuild: Change invalid >=sys-libs/glibc-2.7* atom to >=sys-libs/glibc-2.7. There is a bug in repoman that allowed this atom to slip through. The repoman bug is fixed in svn. 28 Jun 2008; Mike Frysinger <vapier@gentoo.org> iproute2-2.6.25.20080417.ebuild: Force newer glibc #229357. emerge --sync and try again, y'all.
