On Wed, Jan 05, 2005 at 06:41:08AM +0100, Thomas Hood wrote: > You may know all of this already but in case you don't ... > Because of bug #284356 and the fact that kernel-image-2.4.27-1 packages > affected by this bug were allowed into sarge, users of sarge and kernel > 2.4.27-1 can't load modules that were built for their kernel prior to > the symbol change. E.g., the modules in alsa-modules-2.4.27-1* won't > load because of unresolved symbols. The result of this is that people > who have kernel 2.4.27-1 and upgrade to current testing discover to > their dismay that they no longer have sound. > The solution to #284356 was to abandon 2.4.27-1 and release 2.4.27-2 > kernels instead. However, the combinations of 2.4.27-1 kernels with > 2.4.27-1 module packages are still available in sarge and are still > causing headaches. > To alleviate this problem, I request that alsa-modules-2.4.27-1* be > removed from sarge. Is this an issue with the current version of alsa-modules-2.4.27-1 being broken wrt the original 2.4.27-1 ABI, or is it just an issue of the current kernel-image-2.4.27-1 packages in testing not conforming to that ABI? This isn't clear from your message. If the problem is the first of these, then removing alsa-modules-2.4.27-1 from testing is of course a reasonable solution. If it's the second, I don't see what good removing the binaries will do anybody, and I think the RC bugs should probably be closed anyway in that case since the bug is not actually in this package. (In that case, kicking kernel-image-2.4.27-1 out of testing would be more useful, but that's obviously not an option yet.) -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature