Does somebody know something easy method of upgrading GLIBC to version 2.4
from 2.3.6 without upgrading Etch to Lenny?
thanks,
--
Kum Gabor
www.kumgabor.hu
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
> Does somebody know something easy method of upgrading GLIBC to version 2.4
> from 2.3.6 without upgrading Etch to Lenny?
I don't see it - and likely there would be too many breakages. You're
better off doing a dist-upgrade to lenny.
> On 1/11/08, Kum Gabor <kumg...@mediacenter.hu> wrote:
>
>> Does somebody know something easy method of upgrading GLIBC to version 2.4
>> from 2.3.6 without upgrading Etch to Lenny?
>
> I don't see it - and likely there would be too many breakages.
Um, could you elaborate _what_ is going to break? Upgrading the glibc
requires an update of a few other packages that do not work with newer
versions (locales, tzdata, libc6-dev), but that's it. After all, if you
dist-upgrade to a newer Debian version, libc6 is usually one of the first
packages that are upgraded, and a breakage in the middle of an upgrade
because of the newer libc6 is not something that happens very often.
> You're
> better off doing a dist-upgrade to lenny.
Which involves its own risk of breakages. I would rather suggest apt
pinning, as described in http://wiki.debian.org/AptPinning.
Sven
> On 2008-01-11 23:37 +0100, David Fox wrote:
>
>> On 1/11/08, Kum Gabor <kumg...@mediacenter.hu> wrote:
>>
>>> Does somebody know something easy method of upgrading GLIBC to version 2.4
>>> from 2.3.6 without upgrading Etch to Lenny?
>>
>> I don't see it - and likely there would be too many breakages.
>
> Um, could you elaborate _what_ is going to break? Upgrading the glibc
> requires an update of a few other packages that do not work with newer
> versions (locales, tzdata, libc6-dev), but that's it. After all, if you
> dist-upgrade to a newer Debian version, libc6 is usually one of the first
> packages that are upgraded, and a breakage in the middle of an upgrade
> because of the newer libc6 is not something that happens very often.
>
I've got some answers in IRC from dondelelcaro some time ago. Briefly,
one of the reason for Etch to ship glibc 2.3.6 instead of newer ones
is it's the last glibc that supports 2.4 Linux kernel, which Etch
supports. Lenny won't make that promise, so it got updated.