Your message dated Mon, 31 Mar 2025 23:05:16 +0000
with message-id <[email protected]>
and subject line Bug#1099444: fixed in incus 6.0.3-5
has caused the Debian Bug report #1099444,
regarding incus-base: ineffective Replaces for incus due to /usr-move (DEP17 P1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1099444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099444
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: incus-base
Version: 6.0.3-4
Severity: serious
Justification: file loss in upgrade
Control: affects -1 + incus
User: [email protected]
Usertags: dep17p1
Hi,
you moved the systemd units formerly present in incus to the incus-base
package. The way this is done is normally correct and works for trixie
-> sid upgrades. Unfortunately, the earlier version has also been
backported to bookworm-backports and there the systemd units are
installed into the aliased location. Therefore and upgrade from
bookworm-backports to sid may presently loose the systemd units. This
bug serves as a migration blocker. For more information refer to
https://subdivi.de/~helmut/dep17.html section P1.
The failing scenario is rare. People upgrading from trixie to sid will
be unaffected as there is no aliasing in trixie. People running
bookworm-backports will most likely upgrade to some eventual
6.0.3-4~bpo12+1 which will also have working Replaces and from there
they may be upgrading to trixie at a later time. It is the rare
situation from the aliased + previous package organization to the
canonicalized + reorganized packages that is prone to loss.
Given this rarity, I suggest going with a rather weak mitigation that
will only work reliably when upgrading with an apt-based package manager
(and can leave failing scenarios behind when doing upgrades with dpkg
directly). It is (DEP17 M7):
-Replaces: incus (<< 6.0.3-3~)
-Breaks: incus (<< 6.0.3-3~)
+Conflicts: incus (<< 6.0.3-3~)
Then apt will prefer to unpack the updated incus (releasing the systemd
units) before unpacking incus-base and thus avert the file loss
situation. In other cases, I've suggested stronger mitigations, but here
my expectation is that the scenario is mostly artificial (assuming that
you do another bookworm-backports upload and people upgrade to it).
Do you agree with the reasoning? If yes, please move forward and include
"DEP17 P1 M7" in debian/changelog.
Helmut
--- End Message ---
--- Begin Message ---
Source: incus
Source-Version: 6.0.3-5
Done: Mathias Gibbens <[email protected]>
We believe that the bug you reported is fixed in the latest version of
incus, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mathias Gibbens <[email protected]> (supplier of updated incus package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 31 Mar 2025 22:36:28 +0000
Source: incus
Architecture: source
Version: 6.0.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team <[email protected]>
Changed-By: Mathias Gibbens <[email protected]>
Closes: 1084990 1099444
Changes:
incus (6.0.3-5) unstable; urgency=medium
.
[ Martin Steigerwald ]
* Runit support for Incus (Closes: #1084990)
.
[ Mathias Gibbens ]
* d/control:
- Apply hack for /usr-move (Closes: #1099444; DEP17 P1 M7)
- Update minimum required version of lxcfs to ensure its runit scripts
will be available
- Set minimum version of apparmor
- Replace Built-Using with Static-Built-Using
* Add apparmor 4.x userns patch
* Cherry-pick upstream commit for selecting SecureBoot capable OVMF
* Cherry-pick upstream fix for qemu 10
* Update d/README.Debian to reflect addition of runit scripts
* Fix lintian warning old-fsf-address-in-copyright-file in d/copyright
Checksums-Sha1:
181894a8147a2f6aae26817ee204a28c05e9cc46 4559 incus_6.0.3-5.dsc
5bdf0d9e3cecc8c8de6eed61d60949251b9363f0 4384011 incus_6.0.3.orig.tar.gz
63599fda65569d4ebb9776cce85deaf78c666bf0 24360 incus_6.0.3-5.debian.tar.xz
25732f2f56faf0c2958b8f81395ed21f2668018c 21405 incus_6.0.3-5_amd64.buildinfo
Checksums-Sha256:
0699067466b66b18b81dc7474272cc0f139fd216defa1e02ec4d4eee95a6f799 4559
incus_6.0.3-5.dsc
0286ba9f0a1c25260e74e81c621746c3de152dee7fa8f5c663b301a52c8ce16e 4384011
incus_6.0.3.orig.tar.gz
7a4f8bea99ce86ecc47f2aa9c9035531d345e112a00cb17288cc6a816f09e708 24360
incus_6.0.3-5.debian.tar.xz
d3476cdcd169d2c76570ba5a5d6bb571a1e00bc5aeb659263ba22b104333a870 21405
incus_6.0.3-5_amd64.buildinfo
Files:
518f1431fe0c01401e667cc1b3123e04 4559 admin optional incus_6.0.3-5.dsc
d1bd8d2c2c98b8ccc112c58fa24b0bdb 4384011 admin optional incus_6.0.3.orig.tar.gz
b52fb4a3d1a914e90df8bc0ed6f23b9f 24360 admin optional
incus_6.0.3-5.debian.tar.xz
c67b825d8ab79c1ca0b7a6c59d1d376d 21405 admin optional
incus_6.0.3-5_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEE1Bp60H32xfynSJ8cKe7i1uz0QvkFAmfrGu4SHGdpYm1hdEBk
ZWJpYW4ub3JnAAoJECnu4tbs9EL5QjcP/2k0QzOVFekmpIIQ0UivcUTN5w3KgoZP
pwzzmE6+LKLqsI8S71otAMtEjoSQ0VhEiLoYmI6uiidi7WAU7yhcldT76cNOQZmP
A4K+PVmTsep/kleii9r35l8t+OPTr5ePkR47amhzcQDyMnt1MDkCd5jWiJ7sf1Od
8JvyKJstadMXEasnPQzyW0Q5U4CwhtPSGcnKuWojVr4ltL+n55gG886HW0Ouz1cj
/3aaoW8nV2txvF8WL1UyLbjlv59qmMe4MO9Gc+XKrR5bDu0IiaSAx/eUWafeHRqS
tuimbAw/DiTlfimLoyP+a9SltEmT6OU1nMG1eaFWBbR1Qb+DHFsCht9LLm81djq1
B5nzRZ0QSSPzTEZujJfI+jVrlhn0D8aitnQRj8BER6bT/zE5nMd2ldPj3BcFv5RS
XZJ+VLG8ktSgEcTsFoX4N/kyyWBVIczG4A3LYZAl4ZNfpGgvbSJwjp9j+4W3zxQF
Dp/R86Q6fMV5qnY4+jrQQ5XDAGn44vpeMkWwnIRzqr8wQpt6JBPtscqdycHrjbL4
Lh5qjN0PV2GbVIBrqsyIYQxcjNWl55WGIdm+tII65JNlI7Bd+QI5wdKd9cOpi9Qm
wMcMLkJAvi4lIHADmfU2Eark1sz73NmBk+bUilILxPk6p6/H6XulKfjvcxL6wyeo
SjDbPceT3za+
=JDAD
-----END PGP SIGNATURE-----
pgpHPKvvrCL4K.pgp
Description: PGP signature
--- End Message ---
