Control: reassign 791917 initscripts
Control: found 791917 2.88dsf-59.1
Control: fixed 791917 2.88dsf-59.2
On Sun, 02 Aug 2015 at 00:41:23 +0100, Simon McVittie wrote:
> This means you had this as the broken situation:
>
> initscripts 2.88dsf-59.1
> sysvinit-utils 2.88dsf-59
> util-linux 2.25.2-6
>
> initscripts 2.88dsf-59.2 has a Breaks on util-linux (<< 2.26.2-4~), and
> has now replaced 2.88dsf-59.1 in testing, so this shouldn't happen again.
>
> > Can we get the depends/breaks between them so that you can't install a
> > combination that doesn't work?
>
> My understanding is that this was a bug in initscripts 2.88dsf-59.1 and
> was fixed in 2.88dsf-59.2: namely, it dropped mountpoint from the
> Essential set, but did not ensure that a sufficiently new util-linux to
> provide mountpoint was installed. Now that initscripts 2.88dsf-59.1 is
> no longer available in any suite, upgrades from stable shouldn't run
> into this.
In the absence of any feedback to the contrary, I'm going to consider this
to be a bug in initscripts, which was present in 2.88dsf-59.1
but fixed in 2.88dsf-59.2. Without a time machine to go back and
fix this before it happened, I don't think we can fix these partial
upgrades.
There doesn't seem to be much I can or should do about this in dbus;
partly because it affects other packages, not just dbus (e.g. uswsusp,
#793886), and partly because if people are doing partial upgrades that
pick up the latest initscripts without the latest util-linux,
there doesn't seem to be anything to guarantee that they'll
upgrade to the latest dbus either.
S
