Your message dated Thu, 05 Feb 2026 17:50:38 +0000
with message-id <[email protected]>
and subject line Bug#1122747: fixed in progress-linux-metapackages 20260205-1
has caused the Debian Bug report #1122747,
regarding bfh-metapackages: Please remove/replace usage of dh_movetousr
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.)


-- 
1122747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122747
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: bfh-metapackages
Version: 20211009-38
Severity: normal
User: [email protected]
Usertags: dh_movetousr_removal

Hi,

your package bfh-metapackages either Build-Depends on
dh-sequence-movetousr or uses dh_movetousr conditionally to move
files from aliased locations like /sbin, /bin or /lib to the
canonical location in /usr.

Eventually, we would like to get rid of this debhelper addon.
Packages should use the canonical paths without any postprocessing.

This means, files are installed directly into /usr.

Please note, that such a change must not be backported to bookworm or
older. If you intend to provide such backports, these changes must be
reverted for those releases. If this means an undue burden on your
workflow our recommendation is to postpone this cleanup.

The motivation for this bug report is, to inform maintainers, that
installing files into the canonical location explicitly, is now the
preferred approach and dh_movetousr is now a deprecated tool.

The goal is, to have dh_movetousr removed after forky is released. We
can revise this plan, if needed. Please keep this timeline in mind
and let us know if this doesn't work for you.

For more information see [1].

If you have further questions, there is an IRC channel named
#debian-usrmerge on OFTC.

Regards,

Michael

[1] https://lists.debian.org/debian-devel/2025/11/msg00245.html

--- End Message ---
--- Begin Message ---
Source: progress-linux-metapackages
Source-Version: 20260205-1
Done: Daniel Baumann <[email protected]>

We believe that the bug you reported is fixed in the latest version of
progress-linux-metapackages, 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.
Daniel Baumann <[email protected]> (supplier of updated 
progress-linux-metapackages 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: Thu, 05 Feb 2026 18:26:57 +0100
Source: progress-linux-metapackages
Architecture: source
Version: 20260205-1
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann <[email protected]>
Changed-By: Daniel Baumann <[email protected]>
Closes: 1122747
Changes:
 progress-linux-metapackages (20260205-1) sid; urgency=medium
 .
   * Merging upstream version 20260205.
   * Adding numactl to progress-linux-container-server depends.
   * Harmonizing email addresses.
   * Removing Rules-Requires-Root, not needed anymore.
   * Updating to standards version 4.7.3.
   * Updating vcs fields.
   * Updating copyright file.
   * Updating upstream sigining-key.
   * Removing dh_movetousr and directly using directories in /usr (Closes:
     #1122747).
   * Removing pre-trixie usr-is-merged handling.
   * Removing now unused pm divertions.
   * Updating watch file to version 5.
   * Correcting typo in 20211008-11 changelog entry.
Checksums-Sha1:
 b3ed151def1af0b665d3921f3b9e4f8f94153150 2087 
progress-linux-metapackages_20260205-1.dsc
 9491fc826e701a844a0e2a86e901a57c4f986b46 13804 
progress-linux-metapackages_20260205.orig.tar.xz
 8f96703477fd5827cc68ce13d0021a310da45f82 8080 
progress-linux-metapackages_20260205-1.debian.tar.xz
 36efac8d88dd91519b8d924b95c329018944c148 8090 
progress-linux-metapackages_20260205-1_amd64.buildinfo
Checksums-Sha256:
 7ecd71cf0a44a3788d41fa72b0425d3b4e206f333ba9a7e75e1af498b4a626d8 2087 
progress-linux-metapackages_20260205-1.dsc
 f7a84de98ea1698a39200d8eddd85efe378f70beae42deafae19a402127cfe24 13804 
progress-linux-metapackages_20260205.orig.tar.xz
 f74edfe6421aa9079bc6e436bfb05bdd39f40b888c183fc96088b92724684c45 8080 
progress-linux-metapackages_20260205-1.debian.tar.xz
 b54713d05f65eb6bfe51f71121a1b262eb33ac976569778d23af8aaaedf20567 8090 
progress-linux-metapackages_20260205-1_amd64.buildinfo
Files:
 02c275c2df429265b07cc323b6ebf646 2087 metapackages optional 
progress-linux-metapackages_20260205-1.dsc
 7ebc949c37158e01557bab2e1eb75802 13804 metapackages optional 
progress-linux-metapackages_20260205.orig.tar.xz
 8b9087ecf70bd410716754062a03ad21 8080 metapackages optional 
progress-linux-metapackages_20260205-1.debian.tar.xz
 35bda7c47f12b4a6871a20e024db2c4b 8090 metapackages optional 
progress-linux-metapackages_20260205-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQQmmGg4gLaoSj0ERgL7tPDoCoAiLwUCaYTTswAKCRD7tPDoCoAi
L32LAQDQQSp/ReX6FV9EPjiEec84/O/S2wX2VS5kOUJuJZxphwD/dnwBHRLOU2AE
ZhE+nhQFLDOv+L9qqlL8V8hL+r6zVwo=
=LZ+4
-----END PGP SIGNATURE-----

Attachment: pgp5_VQKmGIFK.pgp
Description: PGP signature


--- End Message ---

Reply via email to