Hi Gianfranco, > > >I also just uploaded 4.7.1 to Debian mentors. > > >Will the deferred queue automatically drop the proposed 4.7.1 bpo in case a > >major regression prevents the sid package from migrating to testing? > > > no, it won't prevent the drop, this is something I have to remember to check > in today+4days > (I usually sponsor one day after the testing migration, because of this > reason) > (I did the upload in deferred/6, I would appreciate you to ping me when the > current one migrates, and I'll reschedule it)
Please remove this backport from the deferred queue asap! Chris Murphy found "I'm getting some weird unexplained errors that only progs 4.7 complains about (clean scrubs, clean mounts, completely working file system, but a buncha backref complaints from 4.7's btrfs check)" < http://www.spinics.net/lists/linux-btrfs/msg58325.html >. Furthermore, from what I gather from that email (and a fuzzy analysis of other recent posts to linux-btrfs), btrfs-progs-4.5.3 and 4.6.1 (and of course 4.4.1) are the "known good" userspace for users who have chosen to run linux-4.4.x LTS. In light of this, I definitely don't think that 4.7.x is appropriate for backports. I believe the current bpo version 4.6.1 is our best option for supporting users using linux-4.4.x-to-4.6.x, and I've noticed that there's quite a spread in linux-image bpo bug reports. Thank you! Nicholas
signature.asc
Description: Digital signature
