Luca Bruno [EMAIL PROTECTED] writes:
I know, this was basically an unfortunate timing, my bad. Given that
there isn't a solution, and the status quo is not safe, the only
conclusion is to not release with 0.8.7-1.
Should I explicitely request a removal of 0.8.7-1 from Lenny or are you
already
Marc 'HE' Brockschmidt scrisse:
Luca Bruno [EMAIL PROTECTED] writes:
So I'm asking what you suggest to do:
- unblock 0.9.0-1 for lenny as is
- upload the new 0.9.1-1 to sid and then unblock it for lenny
I think it's too late for both of these options. Sorry, but accepting
a few
Luca Bruno [EMAIL PROTECTED] writes:
So I'm asking what you suggest to do:
- unblock 0.9.0-1 for lenny as is
- upload the new 0.9.1-1 to sid and then unblock it for lenny
I think it's too late for both of these options. Sorry, but accepting a
few thousand new lines of code just a few weeks
Adeodato Simó scrisse:
* Marc 'HE' Brockschmidt [Tue, 14 Oct 2008 22:11:18 +0200]:
- upload 0.9.0-1lenny0 to t-p-u with the backported offset patch
Could you give a rough estimate how big this patch would be?
AFAICT, this option was about accepting 0.9.0 in its entirety, plus a
Hi,
sorry if this mail comes a bit late in the release cycle, but I've
recently got a mail exchange with ksplice upstream, and our actual
situation isn't optimal.
Basically ksplice 0.8.7 pre-dates 2.6.26 kernel and has various serious
safety issues which can crash the whole kernel:
- race
5 matches
Mail list logo