On Thu, Sep 08, 2016 at 07:11:31AM +0200, Adam Borowski wrote: > On Thu, Sep 08, 2016 at 12:57:32AM -0400, Nicholas D Steeves wrote: > > Package: sponsorship-requests > > Severity: grave > > > > I am looking for a sponsor for an urgent NMU of "btrfs-progs". Upstream > > has marked this as an "urgent fix" < > > https://btrfs.wiki.kernel.org/index.php/Changelog#btrfs-progs-4.7.2_.28Sep_2016.29 > > > Package name : btrfs-progs > > Version : 4.7.1-1~bpo8+1 > > Except, you see, it's 4.7 and 4.7.1 which are the buggy versions, 4.6.1 is > unaffected. So you demand, with a grave severity, to overwrite a known-good > version with one with a data loss bug. > > -- > Second "wet cat laying down on a powered on box-less SoC on the desk" close > shave in a week. Protect your ARMs, folks! I hit "r" instead of "g", so my last reply didn't make it to the bug-tracker. This is an error in my bug submission, and I am embarassed I made that mistake (too late here, I'm going to sleep). It should read: Package name : btrfs-progs Version : 4.7.2-0.1 5 Sept (I think, it might have been earlier) I asked Gianfranco to cancel my bpo in the deferred queue because of this issue. Thank you, Nicholas
Attachment:
signature.asc
Description: Digital signature