On Wed, Dec 15, 2004 at 01:28:50PM +0900, Horms wrote:
<snip>
> As it stands it seems whe have two choices.
>
> 1. Back out the CAN-2004-081 patch.
> This is trivial and would resolve the symbol problem.
> 2. Bump the SO name
> i.e. kernel-{build,headers,image,pcmcia-modiles}-2.4.27-1*
> -> kernel-{build,headers,image,pcmcia-modiles}-2.4.27-2*
> This is not fun, but is probably my prefered option at this point.
>
> Theroretically we might be able to do 1+2 but it looks painful at best.
> We may also be able to find a way to fix CAN-2004-081 and avoid
> introducing this symbol problem, but I am skeptical.
I have built packages that implement each of these plans.
Please take a look if you are interested.
I am still in favour of option 2.
Message-ID: <email address hidden>
Date: Thu, 16 Dec 2004 13:35:23 +0900
From: Horms <email address hidden>
To: Thomas Hood <email address hidden>, <email address hidden>
Cc: <email address hidden>,
<email address hidden>, <email address hidden>,
<email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: New release changed symbols thus rendering modules unloadable
On Wed, Dec 15, 2004 at 01:28:50PM +0900, Horms wrote:
<snip>
> As it stands it seems whe have two choices. {build, headers, image,pcmcia- modiles} -2.4.27- 1* {build, headers, image,pcmcia- modiles} -2.4.27- 2*
>
> 1. Back out the CAN-2004-081 patch.
> This is trivial and would resolve the symbol problem.
> 2. Bump the SO name
> i.e. kernel-
> -> kernel-
> This is not fun, but is probably my prefered option at this point.
>
> Theroretically we might be able to do 1+2 but it looks painful at best.
> We may also be able to find a way to fix CAN-2004-081 and avoid
> introducing this symbol problem, but I am skeptical.
I have built packages that implement each of these plans.
Please take a look if you are interested.
I am still in favour of option 2.
http:// debian. vergenet. net/testing/ kernel- 2.4.27/
--
Horms