Hi
Version 13.17 of debhelper has just been updated to unstable with the
following compat 14 related changes:
* Reorder default sequence around dh_fixperms and nearby tools in
compat 14. (Closes: #981783, #982457). This should also avoid
future issues like LP#1928381 where Ubuntu's modifications to
`dh_strip` cause differences not visible in Debian.
- Most importantly, `dh_fixperms`, `dh_compress`, and
`dh_strip_nondeterminism` are now run later and in a different
order with `dh_fixperms` now running before the other two.
This may expose bugs in `dh_compress`, `dh_strip_nondeterminism`,
or third-party tools added (now) after `dh_fixperms` because they
used one of the other commands as "anchor" point. This will mostly
be visible in the form of ownership or mode and will require you
to file bugs against the relevant tools. (Feel free to CC me on
bugs to third-party packages and add them as blockers for this
bug)
* The `Dh_Lib.pm` function `pkgfile` (used to detect files like
"debian/foo.install") no longer allows `named` and architecture
restricted files by default in compat 14. Instead, tools have to
explicitly declare that they support multiple files via `--name`
or/and architecture restricted files (like `debian/symbols.amd64`).
This is only about `debian/foo.named.install` no longer being
accepted as a valid source file for `dh_install -pfoo --name named`
(etc.). Note that `--name` (the parameter) is still accepted by most
helpers by default and may still change the destination name in some
cases.
All of `debhelper`'s commands should have been updated correctly. If
not, please do not hesitate to file bugs.
Third-party tools may need updating here as well though I expect to
be rare, since few helpers need these features. If it happens, they
will need a versioned dependency on `debhelper/13.17` (or a runtime
check) and a slightly altered call to `pkgfile` to (re-)enable these
special cases.
* The `dh_auto_install --destdir debian/tmp` change has now become a
`compat 14` rather than a `compat 15` change at request in #1074322.
At the time of analysis, only two packages were affected and were
maintained by the reported, who was ok with the change (everyone else
added an explicit `--destdir` with a compat 14 change and should
therefore be unaffected by this change). Please see #1074322 for the
rationale.
Please let me know if you run into issues with any of these changes or
the changes have unexpected side-effects. As always, please file bugs
and add them as blockers of this bug. :)
Best regards,
Niels
