[pkg-cryptsetup-devel] Bug#952703: [cryptsetup] needs breaks on old cryptsetup-bin

[Guilhem Moulin]

Control: retitle -1 unsupported upgrade from <buster to bullseye
Control: severity -1 minor

On Thu, 27 Feb 2020 at 20:33:54 +0000, jnqnfe at gmail.com wrote:
> ```
> dpkg: error processing archive
> /var/cache/apt/archives/cryptsetup_2%3a2.2.2-3_deb (--unpack):
> trying to overwrite '/usr/sbin/luksformat', which is also in package
> cryptsetup-bin 2:1.7.0-2
> ```

That seems to be an upgrade from a package version even older that
stretch's (stretch has 2:1.7.3-4) all the way to bullseye's.  That's not
a supported upgrade path.  The only supported one is stable → stable+1
(for which we have suitable Breaks relations in place),
https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian .

> I expect you forgot to place a suitable breaks on the older packages
> after the reorganisation.
> […]
> Clearly what should be expected from a targetted upgrade specifying
> just `cryptsetup` and not `cryptsetup cryptsetup-bin
> cryptsetup-initramfs` should be that it either pulls in all three as
> necessary upgrades or at least complains about version conflicts. It
> should never just fail like this.

I suppose adding Breaks on pre-Buster packages won't hurt so I'm keeping
that open (with a lower severity) but you're very much on your own once
you start mixing releases like this :-P

-- 
Guilhem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20200227/ab5949b8/attachment.sig>