When doing a emerge -u -p world, I got the answer saying that there was no ebuild that could satisfy gnome-base/libgnomeui-2.0.6 (a dependency inherited from gnome 2.0.3). I checked in the portage tree and libgnomeui-2.0.6-r1 not only was not masked, but also contained the keyword "x86" (I don t accept keyword ~x86). What is strange is that, in the libgnomeui-2.0.6-r1, I added a space char between " and x86 in the KEYWORDS section. It worked ! More strange is that to be complete I edited back the ebuild and deleted the space I just added... I still worked, no more complaints about failed dependencies for libgnomeui-2.0.6. Same problem with Orbi2-2.4.4, nautilus-2.0.8,... and always the same solution: opening the file with nano and then editing it then back (just to have nano save it). Could it be a problem with some locale ? I had a working 1.2 gentoo that I up'ed to 1.4rc1 some 2 months ago I think. But everything worked fine till last sunday (01/12).
emerge info
Created attachment 6209 [details] Output from emerge info Did emerge info redirected into this file 'emerge info > emerge_info'.
Wanted to check that also : a simple 'touch' on the ebuild works also... Could it be locale/codepage problem ?I don t change anything in the ebuild, just 'touch' and they work...
Strangest : if I do an emerge rsync (then wiping out all the ebuilds I 'touch'ed), portage complains about the same file than before doing emerge rsync. Then it has nothing to do with the ebuilds : I ll try to wipe out /var/tmp/portgae to see if it was somehow corrupted.
Bug disappeared with portage 2.0.45-r1. Should we close the bug report ?
