On Sat, 2005-01-08 at 02:44 -0800, Steve Langasek wrote: > > 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?
The latter. > 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 Well, as you say, the practical advantages may not be so great, since removing alsa-modules-2.4.27-1* from the archive won't result in these packages being removed from systems that already have the packages installed. However, removing alsa-modules-2.4.27-1* from the archive will result in people not having broken kernel-image+alsa-modules combinations if they are installing sarge afresh. What removing alsa-modules-2.4.27-1* does do is make sarge more consistent with itself than it currently is. All the *2.4.27-1* packages have to be yanked eventually and since alsa-modules-2.4.27-1* are not serving any useful purpose in the archive now (and has the potential to confuse people), I'd say they should be yanked now. > Also... I know why kernel-image-2.4.27-2 isn't in testing yet, but I > don't see alsa-modules-2.4.27-2 anywhere, even in NEW? We haven't done an alsa-modules-2.4.27-2* release yet. That shouldn't affect the decision about whether or not to remove alsa-modules-2.4.27-1, though. -- Thomas Hood <[EMAIL PROTECTED]>
