On Thu, Nov 23, 2006 at 09:33:31AM +1100, Nathan Scott wrote: > John, > > Take a deep breath. Please start a discussion with the maintainer > before attempting an NMU, its generally considered courteous to > give more than 45 mins notice (which was the time between this > bug and your NMU problem report).
Hi Nathan, It appears there was some misinformation about debian-devel about your level of activity wrt this package. I have prepared an NMU, but I uploaded it to delayed/4-day, so feel free to remove it. > The XFS experts do not hang out on debian-devel, so I'd take most > of those comments with a pinch of salt (except for the one that said > talk to the maintainer before attempting an NMU ;) Hey, that's why I sent in this bug report ;-) > > I *personally* encountered trouble today, which looks like remnants from > > when I was running a kernel before 2.6.18. I will likely prepare an NMU > > for this in short order. > > You've given no details. I can only guess that you're refering to > the dir2 corruption problem of 2.6.17.[0-7] - that particular problem > was resolved in 2.8.11 which was uploaded as soon as a fix was > available. I suspected that at first, but yes I saw that in the changelog too. In any case, XFS crashed spectacularly during a dist-upgrade, forcibly unmounted /usr, and xfs_repair killed /usr/share/man3 entirely and corrupted a few things in /usr/lib in the repair process. I needed to get the machine back up ASAP so I didn't have time to do a lengthy postmortem. > However, I'll look into doing an upload soon. Please do not do an NMU. > As you can see if you read the changelog more carefully, there has been > substantial work done on scaling xfs_repair since .11. Thats relatively > risky change, so I want to let it get some soak time before uploading. Let me know if you want to delete it from delayed or if you want me to. -- John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
