Re: Updating linux-2.6 in testing (to 2.6.17)
Steve Langasek a écrit :
I wouldn't know how to show that it's safe and correct to push linux-2.6
in at this time, so I guess I won't be doing this. Hopefully someone
else does, otherwise Etch won't be how it was announced.
There are currently 4 RC bugs against linux-2.6. #342246 and #242866 are
clearly preexisting. #369517 already affects testing through
linux-2.6.16 and should also be ignored unless removing linux-2.6 from
testing is considered. Finally, #383481 is not reported against any
version and can be considered as either invalid or preexisting.
On Sat, Aug 19, 2006 at 03:04:08AM -0400, Filipus Klutiero wrote:
Since I'm afraid that the Linux team isn't doing anything to update
linux-2.6 in testing and that nothing else feels responsible for doing
so, I'm initiating the discussion. I request the release team to force a
linux-2.6 update (to 2.6.17) in testing in 3 days unless objections are
raised until then.
I certainly won't be doing this; someone needs instead to show me that it's
safe and correct to push linux-2.6 in at this time, and to either address or
account for the RC bugs currently listed as open against linux-2.6.