#1122746 btrfsmaintenance: Please remove/replace usage of dh_movetousr

#1122746#5
Date:
2025-12-12 13:52:17 UTC
From:
To:
Hi,

your package btrfsmaintenance 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

#1122746#10
Date:
2026-07-04 20:56:18 UTC
From:
To:
Hi Nicholas

Please find attached a patch which implements this change.

Regards,
Michael

#1122746#17
Date:
2026-07-04 23:52:10 UTC
From:
To:
control: tag -1 pending

biebl@debian.org writes:

The plan, as you stated, is to drop dh_movetousr in 2027.  Why are you
pushing this now?  NACK to the NMU you intend but didn't propose.  I've
updated my branch in git with this change and it will be in the upload I
make later this summer.

Regards,
Nicholas

#1122746#24
Date:
2026-07-05 13:47:49 UTC
From:
To:
Hi Nicholas

Am 05.07.26 um 01:52 schrieb Nicholas D Steeves:

I didn't intend to NMU the package, otherwise I would have said so.
Sorry if it came across this way. I created the patch mainly for your
convenience.

That said, thanks a lot for applying it to your Git branch.

Michael