On Mon, 2011-10-24 at 01:40 +0200, Hartmut Figge wrote:
> Greetings,
>
> emerge --sync was successfull till 'Performing Global Updates' which
> leaded to an error. After waiting for perhaps 1 to 2 hours i tried
> another 'emerge --sync' in the hope that would fix the issue. No luck.
>
> ---------------
> i5 hafi # emerge --sync
>
> Performing Global Updates:
> (Could take a couple of minutes if you have a lot of binary packages.)
> .='update pass' *='binary update' #='/var/db update' @='/var/db move'
> s='/var/db SLOT move' %='binary move' S='binary SLOT move'
> p='update /etc/portage/package.*'
> /usr/portage/profiles/updates/3Q-2011..........................
> /usr/portage/profiles/updates/4Q-2011......
> ERROR: Malformed update entry 'move dev-php5/dev-php5/pecl-ssh2
> dev-php/dev-php5/pecl-ssh2'
> Traceback (most recent call last):
> File "/usr/bin/emerge", line 43, in <module>
> retval = emerge_main()
> File "/usr/lib/portage/pym/_emerge/main.py", line 1531, in emerge_main
> _global_updates(trees, mtimedb["updates"], quiet=("--quiet" in myopts)):
> File "/usr/lib/portage/pym/portage/_global_updates.py", line 160, in
> _global_updates
> moves = vardb.move_ent(update_cmd, repo_match=repo_match)
> File "/usr/lib/portage/pym/portage/dbapi/vartree.py", line 300, in move_ent
> origmatches = self.match(origcp, use_cache=0)
> File "/usr/lib/portage/pym/portage/dbapi/vartree.py", line 474, in match
> origdep, mydb=self, use_cache=use_cache, settings=self.settings)
> File "/usr/lib/portage/pym/portage/dbapi/dep_expand.py", line 33, in
> dep_expand
> mydep = Atom(mydep, allow_repo=True)
> File "/usr/lib/portage/pym/portage/dep/__init__.py", line 1097, in __init__
> raise InvalidAtom(self)
> InvalidAtom: dev-php5/dev-php5/pecl-ssh2
> ---------------
I'm seeing this chatter now. It looks like someone made a typo. And
some mirrors are still picking it up.
You should be able to delete /usr/portage/profiles/updates/4Q-2011 (or
edit the file and fix it... it's pretty straighforward) and continue
from there.
-a
