Quoting Michael Lueck ([EMAIL PROTECTED]): > On Fri, 13 May 2005 22:47:03 +0200, Christian Perrier wrote: > > >Which does not make the bug release critical.... > > In the end it is your call. What, since it involves Samba + XFS it is OK to > allow a copy forever loop into stable? Since we run all XFS it means we have > to > handle Samba in a special way which is an ugly way to have Debian Sarge enter > the deep freeze world of Stable. Long live Debian Testing!
Please keep the bug number CC'ed to answers. The decrease in severity is not a way to judge that your bug report is to be ignored. This is just assigning the bug the correct severity with regard to your description. No ignoring it : indeed, I'm likely to be affected by this bug report, being in the exact situation you describe. Given that this bug is restricted to XFS file systems, it may not IMHO be assigned a RC severity. This does not mean that the maintainers will not fix the bug. Fixing important bug for non base packages is still allowed and, indeed, I think it's worth fixing thios bug (as well as 302771 for which I tried to give maintainers some input). Please note, besides this, that using XFS on testing, if you use it along with 2.6 kernels, is not a recommended situation, if you keep 2.6.8 kernels shipped with sarge. On my own side, I had to upgrade the kernel to 2.6.10 from unstable, because of a grave bug in XFS support for 2.6.8 (no reference, sorry). In conclusion, I'mpretty sure that Steve and Eloy will give this bug the attention it deserves. Guys, I can again give some help here, for instance by building test packages with the fix pointed by Michael for #309003.
