Re: [gentoo-user] Re: What's wrong with emerge
On Wednesday 03 June 2009 09:23:51 Arttu V. wrote: > ... I wonder why isn't your profiles directory updated by the sync ... It gets in the way of portage. As soon as it finds a profile update it can't handle it aborts whatever it's about to do, even if that's syncing. I got out of this on one box by copying over the profiles from another box that wasn't affected. Then a --sync brought it all back into line. -- Rgds Peter
Re: [gentoo-user] Re: What's wrong with emerge
On 6/3/09, alain.didierj...@free.fr wrote: > > After three days, emerge --sync still returns the same error message. Is > there > anything I can do on my computer to fix it ? I don't know the portage internals well enough even to know if my following suggestion is good or bad (and I wonder why isn't your profiles directory updated by the sync?), but the troublemaking change is probably the one unmade by this: http://sources.gentoo.org/viewcvs.py/gentoo-x86/profiles/updates/2Q-2009?r1=1.24&r2=1.25 So, if you're feeling lucky (and nothing else works nor you get any better advice), you can try removing the reddened line out of your /usr/portage/profiles/updates/2Q-2009 (I'd make a backup copy before editing). -- Arttu V.
Re: [gentoo-user] Re: What's wrong with emerge
Selon Nikos Chantziaras : > alain.didierj...@free.fr wrote: > > #emerge --sync returns the following error: > > > > > > Performing Global Updates: /usr/portage/profiles/updates/2Q-2009 > > (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.*' > > . > > ERROR: Malformed update entry 'move >=kde-base/konq-plugins-4 > > kde-misc/konq-plugins' > > Traceback (most recent call last): > > File "/usr/bin/emerge", line 40, in > > retval = _emerge.emerge_main() > > File "//usr/lib64/portage/pym/_emerge/__init__.py", line 14830, in > emerge_main > > if portage._global_updates(trees, mtimedb["updates"]): > > File "//usr/lib64/portage/pym/portage/__init__.py", line 7914, in > > _global_updates > > moves = vardb.move_ent(update_cmd) > > File "//usr/lib64/portage/pym/portage/dbapi/vartree.py", line 165, in > move_ent > > raise InvalidPackageName(cp) > > InvalidPackageName: >=kde-base/konq-plugins-4 > > > > Where does it come from ? > > How can I fix it ? > > Thanks for the help to come... > > It's been fixed already. Resync to get the bugfix. > After three days, emerge --sync still returns the same error message. Is there anything I can do on my computer to fix it ? -- ~adj~
Re: [gentoo-user] Re: What's wrong with emerge
Selon Nikos Chantziaras : > alain.didierj...@free.fr wrote: > > #emerge --sync returns the following error: > > > > It's been fixed already. Resync to get the bugfix. > Thanks. I'll have to wait till the fix reaches my mirror.
[gentoo-user] Re: What's wrong with emerge
alain.didierj...@free.fr wrote: #emerge --sync returns the following error: Performing Global Updates: /usr/portage/profiles/updates/2Q-2009 (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.*' . ERROR: Malformed update entry 'move >=kde-base/konq-plugins-4 kde-misc/konq-plugins' Traceback (most recent call last): File "/usr/bin/emerge", line 40, in retval = _emerge.emerge_main() File "//usr/lib64/portage/pym/_emerge/__init__.py", line 14830, in emerge_main if portage._global_updates(trees, mtimedb["updates"]): File "//usr/lib64/portage/pym/portage/__init__.py", line 7914, in _global_updates moves = vardb.move_ent(update_cmd) File "//usr/lib64/portage/pym/portage/dbapi/vartree.py", line 165, in move_ent raise InvalidPackageName(cp) InvalidPackageName: >=kde-base/konq-plugins-4 Where does it come from ? How can I fix it ? Thanks for the help to come... It's been fixed already. Resync to get the bugfix.
