Allan McRae, le Mon 11 Jan 2010 10:55:56 +1000, a écrit :
> As Lenny was released about the same time that patch
> hit cvs/git, I am guessing that a patch was never needed for this
> particular issue.
Yes it was: unstable saw an upgrade to 2.9 first, and then to 2.10
Samuel
Samuel Thibault wrote:
Allan McRae, le Mon 11 Jan 2010 09:15:51 +1000, a écrit :
Samuel Thibault wrote:
Allan McRae, le Sun 10 Jan 2010 19:59:01 +1000, a écrit :
Is there another patch for glibc-2.7 to fix this or, even better, a
patch-set for a newer glibc version?
You can peek debian's patc
Allan McRae, le Mon 11 Jan 2010 09:15:51 +1000, a écrit :
> Samuel Thibault wrote:
> >Allan McRae, le Sun 10 Jan 2010 19:59:01 +1000, a écrit :
> >> Is there another patch for glibc-2.7 to fix this or, even better, a
> >>patch-set for a newer glibc version?
> >
> >You can peek debian's patchset.
>
Samuel Thibault wrote:
Allan McRae, le Sun 10 Jan 2010 19:59:01 +1000, a écrit :
Is there another patch for glibc-2.7 to fix this or, even better, a
patch-set for a newer glibc version?
You can peek debian's patchset.
Thanks. I guess this is an answer for the latter part of that question,
Allan McRae, le Sun 10 Jan 2010 19:59:01 +1000, a écrit :
> Is there another patch for glibc-2.7 to fix this or, even better, a
> patch-set for a newer glibc version?
You can peek debian's patchset.
Samuel
