On Tue, 2006-06-27 at 23:02 +0200, Adeodato Simó wrote: > * Ian Campbell [Tue, 27 Jun 2006 20:07:59 +0100]: > > I have unfortunately allowed the 0.6.x package to propagate into Etch, > > which currently has a 2.6.15 kernel that the IVTV packages cannot work > > with[0]. It seems that 2.6.16 will not be going into Etch anytime soon > > due to the freeze[1], is that correct? > > Not really, which should be good news for you. :) The kernel team has > put work in coordination with the release team to ensure that 2.6.16 > images enter testing as soon as possible. Now, there are in sid two > source packages, linux-2.6 (providing .17) and linux-2.6.16, which is > expected to enter testing soon: > > http://bjorn.haxx.se/debian/testing.pl?package=linux-2.6.16 Excellent news! Thanks for the info. > > However, does anyone know a more elegant way than filing > > an RC bug to stop the 0.6.x package propagating again (and the same > > problem occurring in the 2.6.17/0.7.x time-frame)? I don't think there > > is a kernel package I can sensibly depend on since people may build from > > upstream source. Would a build-depends make sense, even though it isn't > > strictly true? > > The RC bug is the way to go. As you say, you can't add a dependency, and > build-depends would not do it, since propagation to testing does not > take them into account, only dependencies. I didn't know build-depends didn't count. RC bug it is then, thanks. Ian. -- Ian Campbell (null cookie; hope that's ok)
Attachment:
signature.asc
Description: This is a digitally signed message part