Your message dated Sun, 14 Jul 2024 22:04:23 +0000
with message-id <[email protected]>
and subject line Bug#1073662: fixed in corosync-qdevice 3.0.3-2
has caused the Debian Bug report #1073662,
regarding src:corosync-qdevice: move aliased files from / to /usr (DEP17)
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.)
--
1073662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073662
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: corosync-qdevice,corosync-qnetd
Version: 3.0.3-1
Severity: important
Tags: patch trixie sid
User: [email protected]
Usertags: dep17m2 dep17dhmovetousr
This package is part of the /usr-move (DEP17) transition, because it
contains files in aliased locations and should have those files moved to
the corresponding /usr location. The goal of this move is eliminating
bugs arising from aliasing, such as file loss during package upgrades.
The following files in the following binary packages are affected.
corosync-qdevice contains:
* lib
* lib/systemd
* lib/systemd/system
* lib/systemd/system/corosync-qdevice.service
corosync-qnetd contains:
* lib
* lib/systemd
* lib/systemd/system
* lib/systemd/system/corosync-qnetd.service
You may add dh-sequence-movetousr to Build-Depends to perform the move.
This is an easy and readily applicable measure that has been verified
for this package using a test build. The main advantage of this method
is the low effort and it just works when backporting to bookworm.
However, it is more of a stop-gap measure as eventually the installation
procedure should refer to the files that are actually used for
installation. This often means updating debian/*.install files but also
changing flags passed to a configure script or similar measures. In case
you do not anticipate your package being uploaded to bookworm-backports,
please prefer a manual move, but generally prefer moving over delaying
any further.
After having done this move, please keep in mind that the relevant
changes need to be reverted for bookworm-backports, with these
exceptions:
 * dh-sequence-movetousr and dh_movetousr cancel themselves.
 * dh_installsystemd and dh_installudev revert to the aliased location.
 * The pkg-config variables systemdsystemunitdir in systemd.pc and
udevdir in udev.pc reverts to aliased.
Please keep in mind that restructuring changes may introduce problems
after moving. A change is considered restructuring if formerly aliased
files formerly owned by one package are later to be owned by a package
with a different name. Such uploads should be done to experimental and
quarantine for three days before moving to unstable. This way, automatic
analysis (https://salsa.debian.org/helmutg/dumat) can detect problems
and file bugs. Such bugs shall include support for resolving the
problems.
The severity of this bug shall be raised to RC on August 6th.
For additional information about refer to
https://wiki.debian.org/UsrMerge and
https://subdivi.de/~helmut/dep17.html.
--- End Message ---
--- Begin Message ---
Source: corosync-qdevice
Source-Version: 3.0.3-2
Done: Valentin Vidic <[email protected]>
We believe that the bug you reported is fixed in the latest version of
corosync-qdevice, 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.
Valentin Vidic <[email protected]> (supplier of updated corosync-qdevice
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: Sun, 14 Jul 2024 23:54:09 +0200
Source: corosync-qdevice
Architecture: source
Version: 3.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers
<[email protected]>
Changed-By: Valentin Vidic <[email protected]>
Closes: 1073662
Changes:
corosync-qdevice (3.0.3-2) unstable; urgency=medium
.
[ Ferenc Wágner ]
* [9cd7087] Fix typo in Vcs-Browser field
.
[ Valentin Vidic ]
* [4120200] Move systemd files to /usr/lib (Closes: #1073662)
* [1199039] Update Standards-Version to 4.7.0
* [0e56cf8] Update Build-Depends for pkgconf
Checksums-Sha1:
b11396dcec0dee6643efa023fa0af1582ff29676 2548 corosync-qdevice_3.0.3-2.dsc
a3825980e2b6c29d706f747a546133cb7502b0e0 8704
corosync-qdevice_3.0.3-2.debian.tar.xz
d84a57595f4dd39d3872142e62f61057c1766ddf 6332
corosync-qdevice_3.0.3-2_source.buildinfo
Checksums-Sha256:
d314cf8364a48adaa3e291cca8a96f3e7d3af7f1bd4865b919d10c56c773423e 2548
corosync-qdevice_3.0.3-2.dsc
fc395589be48a744da5aa1b4613431041bc527a97b9e70b1b48b350dcc80fb7b 8704
corosync-qdevice_3.0.3-2.debian.tar.xz
c37bf11b411e535a16b34e7d78d4fe01ed0d365cfbbad8e0f348baa577f76493 6332
corosync-qdevice_3.0.3-2_source.buildinfo
Files:
9f1392857abdbba74ebaf1a874a687b5 2548 admin optional
corosync-qdevice_3.0.3-2.dsc
08f64b634bfccfd10a1e2ddd67bb7137 8704 admin optional
corosync-qdevice_3.0.3-2.debian.tar.xz
05ae85e3b99d2913ccc1ba261fa96e8e 6332 admin optional
corosync-qdevice_3.0.3-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEExaW53cM9k/u2PWfIMofYmpfNqHsFAmaUSrMSHHZ2aWRpY0Bk
ZWJpYW4ub3JnAAoJEDKH2JqXzah7QDQP/3EA8c6v9MXpiWJiuLfmu3CnZY1TFyLa
uNxGOXSBy/sc7x7gbf4UXGhKcJ3lduNq03hRNbj4yQ1P0JKji6RSWuUOkryY/37n
FBI8WeuP3f6kf7IVS8iBUbVFzNPXrnv2o9UW28xYe9qLs63eJQYyKkFAIUtE+8o5
CbYABXLmz+WmoHGt6uqWf9aj8uv8/V81YR73EHpVqTyBpqzdT6QplYqV0jZ6DbNG
xqoqA4uH8LYNCiuH5GbcaRB/vk0dKpLnOy6DtD3pbLBDvkDjLKz4HhpPbOIPcNSr
FwJebe1WQETyyy3QIAOPXORL3JW8xVRvnNYyBErnmTEgfGpdyAntMDitJ7Hmn/Cf
QtlFqJWbedO7VI4PcRK4FIBtrSypWoiFue18KftVQi8TbAUx+2iZ9usk9qd8RvrG
4bMC3gP0xsvs4XjUy8foC189rZIC832x1GUzSGoXp7OTW0e3SoS40+ZLroiH8YOR
6tU+g2+qK+RGsexOiCziQLzM62gIH1kMMfAqeN8Hjh6b4ewwk2SaM/8evVR1EHmA
FDDF1hgd+lQmgJaIxGzsbMO93/aY/vgyj9Ug/5Pq1T/Tbf0ZQU3n/RYzpWqlkwAJ
lVMBxVZR921UfxwXkd4E//c6cwSXZ531ea3umXIvxJP1XIAWQ0cBTVsRgGZO5vRJ
NEyHClPqSoEj
=yoAL
-----END PGP SIGNATURE-----
pgp3ereKlVbuF.pgp
Description: PGP signature
--- End Message ---
