Your message dated Sat, 10 Aug 2024 12:09:19 +0200
with message-id <7ccbf50e-8690-d16c-8d19-4cc34d703...@debian.org>
and subject line Re: Bug#1073682: nvidia-tesla-470-kernel-support: move aliased
files from / to /usr (DEP17)
has caused the Debian Bug report #1073682,
regarding nvidia-tesla-470-kernel-support: 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 ow...@bugs.debian.org
immediately.)
--
1073682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-tesla-470-kernel-support
Version: 470.256.02-1
Severity: important
Tags: patch trixie sid
User: helm...@debian.org
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.
nvidia-tesla-470-kernel-support contains:
* lib
* lib/firmware
* lib/firmware/nvidia
* lib/firmware/nvidia/470.256.02
* lib/firmware/nvidia/470.256.02/gsp.bin
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 ---
Version: 470.256.02-3
On 19/06/2024 05.19, Andreas Beckmann wrote:
On 18/06/2024 12.50, Helmut Grohne wrote:
override_dh_installdeb:
! command -v dh_movetousr >/dev/null || dh_movetousr
dh_installdeb
Is this good enough for your purpose?
Nice idea. Will take this approach ;-)
Mixed up the bug numbers and closed the corresponding
src:nvidia-graphics-drivers bug in the upload.
Andreas
--- End Message ---
