Re: Dropping upstart jobs (or not)
On 4 June 2016 at 00:31, Michael Biebl <email@example.com> wrote:
> I just became aware recently that upstart has been removed from the
> archive (unstable/testing) .
> Now I'm wondering what to do about the upstart job files that were added
> to various packages. Do we
> - continue to ship them, assuming we have users that keep upstart
> installed when upgrading to stretch.
> - drop them from the package but don't remove the obsolete conffiles.
> This would mean we keep the upstart jobs on upgrades. (probably makes
> our debian qa people unhappy though, who run adequate)
> - drop them from the package and remove them on upgrades.
> - ?
There are still a few downstream distributions from debian using
upstart, with a mix of packages across releases. I am trying to
migrate all of those major users off upstart but progress is going
steady but slow.
It is an adequate thing to do, but may ask to postpone "drop them from
the package and remove them on upgrades." until Buster. Because
otherwise people who run backports and/or packages from testing (and
derived distros) might end up patching those jobs back in, only to
drop the lot a year or two later, resulting in triple total effort
involved in mucking with these conf-files. They are small, inert and
mostly harmless. If one really dislikes them, one can always dpkg
filter them out on current systems.