On Sun, 2018-02-25 at 13:01 +0100, intrigeri wrote: > here's the updated debdiff; I've bumped the version in order to > avoid confusion.
Well you can't upload another +deb9u1 as that version is already in the archive, so it's required in any case. > This will now work fine except for Linux 4.14 to 4.14.12 that have > the > bug which prevented us from including apparmor 2.11.0-3+deb9u1 in the > previous point release. The kernel fix has been in sid since > 2018-01-15, in stretch-backports since 2018-01-16, and in testing > since 2018-01-20. So IMO the benefit (repairing stuff for Stretch > users running an up-to-date backported kernel) is worth the risk > (breaking stuff for Stretch users running an outdated Linux 4.14.x). > > May I upload (with s/UNRELEASED/stretch/ of course)? What's the difference between this and +deb9u1? Is it simply this change: -++features-file=/etc/apparmor/features +++features-file=/usr/share/apparmor-features/features and the equivalent in debian/install? The changelog going from -3 to -3+deb9u2 is confusing, particularly given that +deb9u1 has been available to users of proposed-updates for some time. If the above is correct, please keep the previous changelog stanza for +deb9u1 as-is and add a new entry for +deb9u2 describing the path change. Regards, Adam