[Pkg-sysvinit-devel] Bug#791917: dbus: Missing dependency on mountpoint from util-linux package

[Simon McVittie]

On 01/08/15 21:45, Kurt Roeckx wrote:
> So I just ran into this myself.  The history file showed that I
> just did this to fix it:
> Install: libfdisk1:amd64 (2.26.2-9, automatic)
> Upgrade: initscripts:amd64 (2.88dsf-59.1, 2.88dsf-59.2),
> sysvinit-utils:amd64 (2.88dsf-59, 2.88dsf-59.2), util-linux:amd64 (2.25.2-6, 2.26.2-9)

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.

I could add a versioned Depends on util-linux (>= 2.26.2-4~) in dbus,
but this seems like something that packages depending on the Essential
set shouldn't need to do; and if you do partial upgrades that don't pick
up the newer initscripts, I don't see any way to guarantee that you
don't do partial upgrades that don't pick up the newer dbus either,
leaving you with a version that does not have that workaround. So it
seems to me that this would just make the dependency graph more
complicated, for little real gain.

Does this match the initscripts maintainers' understanding of the situation?

    S