Dimitri John Ledkov: > On 22 September 2017 at 19:24, Michael Biebl <[email protected]> wrote: >> [...] >> >> Niels mentioned on IRC, that in compat 11, debhelper could make it an >> error to have an upstart file and use the opportunity to remind people >> to remove the conffile. >> >> I like that idea. >> > > I'm not sure about the timing though. Many people maintain backports > for their packages, and do backport them "unmodified" sometimes by > means of backporting debhelper first to keep things building > unmodified. > > Under such conditions, having upstart support in debhelper makes some > marginal sense. >
Just to clarify: If I understand you correctly, you are happy with the change itself but would not like it to be a part of a compat level being released in buster? I.e. we are only debating /when/ to apply/enable this change? I believe it would be a non-issue to postpone it until compat 12. There is no other helper/part of debhelper relying on this change that it need to synchronize with; the only "issue" is that we (Debian) keep the upstart jobs longer. > What is the timing of the compat 11? is this something for buster or bullseye? > Compat 11 is targeted for buster. Postponing compat 11 itself for bullseye is not really an option as there are several changes in compat 11 that are needed or makes it easier for people to comply with "recent" policy changes (like the doc change 3.9.7 and DEB_BUILD_OPTIONS="nodoc") > Btw, are debhelper major version numbers going to synchronise with the > debian release numbers? =)))) it would be cute. > No. At times, I need the flexibility of doing != 1 compat levels in a given Debian release. Thanks, ~Niels
