Bo Ørsted Andresen writes:
> On Tuesday 06 March 2007 02:17:27 Alex Schuster wrote:
> > > and what is the output of:
> > >
> > > # cat /var/db/pkg/sys-libs/{glibc-2.2.5-r2,glibc-2.5}/SLOT
> >
> > A blank line, and 2.2.
>
> You should definitely fix that. glibc-2.2.5-r2 is supposed to be in SLOT
> 2.2 too which means it should have been cleaned when you upgraded to
> glibc-2.5.
Looking at /var/log/emerge.log, I do not see glibc-2.2.5-r2 anywhere. No
idea where it came from.
> Run either `equery check =sys-libs/glibc-2.5` or `qcheck
> =sys-libs/glibc-2.5` (requires either gentoolkit or portage-utils) to
> verify that no harm will be caused by unmerging glibc-2.2.5-r2. Then
> unmerge glibc-2.2.5-r2.
OK. The check shows no problem, I unmerged it.
> > I grepped in /var/cache/edb, nothing there, and locate binutils|grep
> > text also showed nothing. Just in case this could mean anything.
>
> Hmm... I actually see this on my system too.. I assume you just didn't
> manage to grep the right files...
Well, a grep -r app-text/binutils /var/cache/edb/ should catch all of them.
> # grep app-text/binutils /var/cache/edb/dep/$(portageq
> portdir)/sys-devel/gcc-4.1.1-r3 [...] ppc? ( >=app-text/binutils-2.17 )
> ppc64? ( >=app-text/binutils-2.17 ) >=app-text/binutils-2.15.94 [...]
Nope, no output.
> > Then I tried emerge --metadata, and suddenly the problem is gone.
> > Whatever it was. Wow, now I have 872 packages to emerge.
> >
> > Thanks for your help, Bo!
> > Do you think I should file a bug, so the devs become aware of this
> > potential problem, or should we just hope it never happens again? I
> > still wonder what may have caused this, looks to me like something got
> > corrupted badly.
>
> That `emerge --metadata` fixes it means that it has been fixed on the
> mirrors. So there's not much to report..
Okay, I'll just forget about it then.
Thanks again,
Alex
--
[email protected] mailing list
