| 1 |
On Tuesday 06 March 2007 02:17:27 Alex Schuster wrote: |
| 2 |
> > and what is the output of: |
| 3 |
> > |
| 4 |
> > # cat /var/db/pkg/sys-libs/{glibc-2.2.5-r2,glibc-2.5}/SLOT |
| 5 |
> |
| 6 |
> A blank line, and 2.2. |
| 7 |
|
| 8 |
You should definitely fix that. glibc-2.2.5-r2 is supposed to be in SLOT 2.2 |
| 9 |
too which means it should have been cleaned when you upgraded to glibc-2.5. |
| 10 |
|
| 11 |
Run either `equery check =sys-libs/glibc-2.5` or `qcheck =sys-libs/glibc-2.5` |
| 12 |
(requires either gentoolkit or portage-utils) to verify that no harm will be |
| 13 |
caused by unmerging glibc-2.2.5-r2. Then unmerge glibc-2.2.5-r2. |
| 14 |
|
| 15 |
> I grepped in /var/cache/edb, nothing there, and locate binutils|grep text |
| 16 |
> also showed nothing. Just in case this could mean anything. |
| 17 |
|
| 18 |
Hmm... I actually see this on my system too.. I assume you just didn't manage |
| 19 |
to grep the right files... |
| 20 |
|
| 21 |
# grep app-text/binutils /var/cache/edb/dep/$(portageq portdir)/sys-devel/gcc-4.1.1-r3 |
| 22 |
[...] ppc? ( >=app-text/binutils-2.17 ) ppc64? ( >=app-text/binutils-2.17 ) >=app-text/binutils-2.15.94 [...] |
| 23 |
|
| 24 |
> Then I tried emerge --metadata, and suddenly the problem is gone. Whatever |
| 25 |
> it was. Wow, now I have 872 packages to emerge. |
| 26 |
> |
| 27 |
> Thanks for your help, Bo! |
| 28 |
> Do you think I should file a bug, so the devs become aware of this |
| 29 |
> potential problem, or should we just hope it never happens again? I still |
| 30 |
> wonder what may have caused this, looks to me like something got corrupted |
| 31 |
> badly. |
| 32 |
|
| 33 |
That `emerge --metadata` fixes it means that it has been fixed on the mirrors. |
| 34 |
So there's not much to report.. |
| 35 |
|
| 36 |
-- |
| 37 |
Bo Andresen |
Archives