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).
On Wed, 2006-11-22 at 11:23 -0600, John Goerzen wrote: > Package: xfsprogs > Version: 2.8.11-1 > Severity: critical > Justification: causes serious data loss Sorry, but you've not given any evidence of that here. > This may be "only" grave instead of critical, but it looks to me like it > is a Big Deal and unquestionably RC in any case. These are actually all relatively minor problems, and have all been there for a long time in xfsprogs. > http://lists.debian.org/debian-devel/2006/11/msg00630.html > mentions that the latest versions contain fixes for kernel bugs 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 ;) > 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. 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. thanks. -- Nathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
