Hi Buchan, On Fri, 21 Apr 2006 11:45:53 +0200 Buchan Milne <[EMAIL PROTECTED]> wrote:
| > Yes, unfortunally #21345 wasn't fixed yet. One reason is that we (the | > kernel team) are still discussing its introduction into 2006.0 because it | > may brake things (it's not totally clear to me which things, but well..); | > other important reason is that I had important security fixes to work on. | > | > The really bad news is that I think it won't be possible to fix #21345 | > for -20mdk because I don't want to hold this kernel for more than 2 weeks. | > I'll update the ticket with this info soon. | | | I would be a lot more willing to test this kernel on my amd64 box if it | *might* fix #21345 ... I see. | AFAICS, this aspect should *really* not be a big impact, and it is easier to | test (as it only impacts installation, upgrading, and installation/upgrading | of other packages). The main problem here is that, in order to fix #21345, we'll need (in the better case) yet another week of testing. But I don't want to hold this kernel for too long, becase important fixes have been queued due to -19mdk community release. That's bad, I know, but we'll have to wait for -21mdk and I'll try to introduce the fix in -21uc1mdk. -- Luiz Fernando N. Capitulino
