Your message dated Fri, 10 Jan 2025 16:37:25 +0000
with message-id <e1twi0j-0004eq...@fasolo.debian.org>
and subject line Bug#1092598: fixed in zfs-linux 2.3.0~rc5-1~exp1.1
has caused the Debian Bug report #1092598,
regarding libzfs6linux ineffectively replaces libzfs4linux (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 ow...@bugs.debian.org
immediately.)
--
1092598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libzfs6linux
Version: 2.3.0~rc5-1~exp1
Severity: serious
Justification: file loss in upgrade
User: helm...@debian.org
Usertags: dep17p1
Hi,
the files
- /usr/lib/x86_64-linux-gnu/libzfs_core.so.3
- /usr/lib/x86_64-linux-gnu/libzfs_core.so.3.0.0
are installed by both libzfs6linux and by libzfs4linux. As a result,
libzfs6linux declares Replaces: libzfs4linux. Unfortunately,
libzfs4linux used to install these files below /lib until bookworm. As
such, an upgrade from bookworm to experimental may loose these files.
The issue arises from the /usr-move transition that requested moving
these files from /lib to /usr/lib. For details on the problem category
refer to https://subdivi.de/~helmut/dep17.html section P1.
Until you move libzfs6linux to unstable, this is not a practical
problem, because we consider upgrades from bookworm to experimental
unsupported.
If libzfs6linux is not meant to be part of trixie (but a preparation for
forky), there is no relevant upgrade path as we expect bookworm users to
first upgrade to trixie before upgrading to forky. In that case, please
close this bug report.
Otherwise, libzfs6linux has been added for preparing an update for
trixie. In this case, we must add mitigations. DEP17 suggests multiple
mitigations for this. In order to select a suitable one, I would like to
understand whether this library is potentiall involved in system boot.
In other words whether we risk turning a system unbootable if the
library would go missing. If that is the case, I suggest using a more
elaborate mitigation.
I intend to provide the relevant patches (if any). To provide suitable
patches, I depend on feedback:
* Is libzfs6linux meant to be included in trixie?
* If yes, do you see a risk of rendering a system unbootable if
libzfs_core.so.3 would go missing?
Thanks in advance
Helmut
--- End Message ---
--- Begin Message ---
Source: zfs-linux
Source-Version: 2.3.0~rc5-1~exp1.1
Done: Helmut Grohne <hel...@subdivi.de>
We believe that the bug you reported is fixed in the latest version of
zfs-linux, 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 1092...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Helmut Grohne <hel...@subdivi.de> (supplier of updated zfs-linux 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 10 Jan 2025 09:03:13 +0100
Source: zfs-linux
Architecture: source
Version: 2.3.0~rc5-1~exp1.1
Distribution: experimental
Urgency: medium
Maintainer: Debian ZFS on Linux maintainers
<pkg-zfsonlinux-de...@alioth-lists.debian.net>
Changed-By: Helmut Grohne <hel...@subdivi.de>
Closes: 1092598
Changes:
zfs-linux (2.3.0~rc5-1~exp1.1) experimental; urgency=medium
.
* Non-maintainer upload.
* Add protective diversions for concurrent package rename and aliasing
change of libzfs_core.so.* (DEP17 P1 M8, Closes: #1092598)
Checksums-Sha1:
38a775efbd8cb22acd5f1f9663f0f8a98d28818c 3674 zfs-linux_2.3.0~rc5-1~exp1.1.dsc
aa86e4ca1811379d36919741e7472fa614edb11b 109116
zfs-linux_2.3.0~rc5-1~exp1.1.debian.tar.xz
42161b5f3538ea3f377ee14683a76ca2eadd6638 17894
zfs-linux_2.3.0~rc5-1~exp1.1_amd64.buildinfo
Checksums-Sha256:
1bbe04c7e71ee68c5d43324d79c8a6e511963649ed1e03294941043c71a14981 3674
zfs-linux_2.3.0~rc5-1~exp1.1.dsc
bb3ba3de82293dff03fd3ff22b7ce1390633b3790db2c662cf27fcd8b396f201 109116
zfs-linux_2.3.0~rc5-1~exp1.1.debian.tar.xz
2a22f54c025a0695c1730dfe806bf80e88606cec740ec21190c985a3275156a3 17894
zfs-linux_2.3.0~rc5-1~exp1.1_amd64.buildinfo
Files:
10c00dd0f81c1eeb489b05fd618bbbb9 3674 contrib/kernel optional
zfs-linux_2.3.0~rc5-1~exp1.1.dsc
64326537ffa8bd5a70e260b2dbc1b1b6 109116 contrib/kernel optional
zfs-linux_2.3.0~rc5-1~exp1.1.debian.tar.xz
3019762c531708101ed6b5ea0fd4e0ef 17894 contrib/kernel optional
zfs-linux_2.3.0~rc5-1~exp1.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE+Fg++qmpHzqjSzySzhGnsHs6uUYFAmeBSysACgkQzhGnsHs6
uUY/yg/+Js5xYy1cRixrojRpvhIMZUMi6UDbPjlUXTb1ZheEYOG5O6XZQ5FZnnkw
RJFhSDaz1nRKk8EaCFMABpPcnoJP1HcQ+7wJ7kA6Lss3aDsbRbr8b/QveS+Wts0/
8EwyiiZ+6zw2TKbfA+a3A+M/sBZwCV288uiNUT0+uriFVzXspHAQCmQpgiK/wDr2
sRyowX0o8Icb1YF1uAV4PZZZ0h9d6vN5XnDBGcBAE/FutKon+fYMG3NfYN/uVbpk
SeQnKNOYqcj/Qa/6U9wLSkE9GZM3PXxvxVM6RI9VqV/2PMohCjDAVNcANRJ8hLyf
MQIbQKnDVWi0qZCSnE0fHjIR7Vl70Ho8XAb0cDecg0wpr/B7mRT/teTdpXWhG5xy
4iJg438W8psR9V55IzyBnlxbZ4fgiL3p+e8nGOc2QCcRZyfGYnTmGGUeq1EpoH1U
ykBsE1BU0mopE3+jK2Qr1VWlqoIp3WjEe9PGK+eV/7jeMUbHpGFrEsIjjS6dr0aZ
qLJooZAnsxeIJrQ/uHyDU/kltNCkjWJ2A7Ep9LSnpKdMSdPRued8VBdeUoD8GMLe
QAYrN6695PkjB9ETuHxBQw+HgopOwfo6gKLKWX9QEKh6gqvru2Sa9yczU2omVbga
TGwC1DpzrvbMr1+K5RQuh1vU6BT/93dSwonHEkfKmKsF2g8QlAk=
=1oft
-----END PGP SIGNATURE-----
pgpVFBpPDWGpK.pgp
Description: PGP signature
--- End Message ---
