| 1 |
On Thursday 10 February 2011 18:24:51 Neil Bothwick wrote: |
| 2 |
> On Thu, 10 Feb 2011 09:10:06 -0800 (PST), Volker Armin Hemmann wrote: |
| 3 |
> > > The trouble is that binpkgs keep a copy of the ebuild in them, so |
| 4 |
> > > even if you remove the downgrade check fro the in-tree ebuild, it |
| 5 |
> > > still fails. That one had me scratching my head for a few minutes. |
| 6 |
> > |
| 7 |
> > what happens if you remove the entry in /var/db? |
| 8 |
> > From gentoo's point of view, glibc suddenly is not installed. You are |
| 9 |
> > free to choose a version. |
| 10 |
> |
| 11 |
> That's a good question, I had assumed it was getting the info from the |
| 12 |
> binpkg, but a grep of the entry in /var/db shows no sign of the warning |
| 13 |
> message (it's not in the ebuild but in an eblit file) so removing |
| 14 |
> the db entry would appear to be fruitless. |
| 15 |
|
| 16 |
wtf? |
| 17 |
|
| 18 |
no, the 2.12.1 binpackage does not know which versions are installed. It just |
| 19 |
includes a version check. |
| 20 |
If no glibc is installed (and removing the /var/db/pkg/sys-libs/glibc-2.13 |
| 21 |
directory = no glibc installed) then you are free to install any binpkg you |
| 22 |
want. |
| 23 |
|
| 24 |
Or, you know, just extract ld.so from a tarball, copy it into /lib, and un- |
| 25 |
prelink your system. Then re-install 2.13. Problem solved. |
Archives