On Sat, Dec 02, 2006 at 10:51:57AM +0100, Sven Luther wrote: > The -k7 issue, i don't know, can it be a flavour that was dropped or > something ?
linux-latest-2.6 is not a candidate because not yet uploaded on sparc. That's the easy part; linux-modules-extra-2.6 is the harder part, currently failing to build on both arm and s390 (c.f. bug #400220). > > > - What are our plans for 2.6.19 ? Will we have it enter unstable, and > > > maintain the etch kernel through testing-proposed-updates ? I heard > > > this > > > mentioned some time back. Will we fork a linux-2.6.19 package in > > > unstable > > > ? Will we keep 2.6.19 in experimental for now ? > > I hope you can keep 2.6.19 in experimental for now - it doesn't take so > > long to release Etch anymore. > Bah, we where told this for sarge, and it took over a year back then. I don't > see us releaseing etch anytime soon, since we don't have had a single release > candidate of d-i with the 2.6.18 kernels in it yet, so moving 2.6.19 to > unstable (maybe with a linux-2.6.19 source package) should be nice enough. We > did this already for 2.6.16, so, we know how to do this. Frankly, 2.6.16 was a total cock-up. Aside from all the extra work it made for the release team, I even found patches I had to reapply for alpha because they were dropped on the floor when 2.6.16 was merged to trunk. I am very much opposed to having two kernel versions in unstable at the same time. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
