Hi Thorsten,
On Tue, Jun 18, 2024 at 11:29:34PM +0000, Thorsten Glaser wrote:
> close 1073608
> close 1073622
> thanks
>
> Helmut Grohne dixit:
>
> >This package is part of the /usr-move (DEP17) transition, because it
> >contains files in aliased locations and should have those files moved to
>
> No. The files in both packages are in their canonical location.
> And if you use a usrmerged system, it does not make any practical
> difference anyway.
There is a significant difference here. mksh has an undeclared directory
vs symlink conflict with base-files about /bin. This is known to cause
problems. In principle, what happens with the location is dependent on
the unpack order though all practical installations will unpack
base-files before mksh. For another dpkg-deb -x mksh.deb / will break a
/usr-merged system. At present, most issues are mitigated with
maintainer scripts, but we want to drop those mitigations, which is why
we require that all packages release aliased locations by trixie. I hope
we can agree that there are practical differences and then resume to
disagree about their severity.
In any case, this was discussed on d-devel extensively and we have wide
consensus on this approach. These bug reports will become release
critical on August 6th and I will take care of ensuring that trixie does
not release with aliasing conflicts even if that amounts to removing
offending packages from trixie.
If you truly believe that your package has to continue using the aliased
paths, please provide an alternative plan for dealing with the problems
listed in DEP17. Failing that, we will continue with what was planned.
I request that you reopen these bugs even if the solution ends up being
a different one than the one I requested, but the status quo is not
something we can continue using as is.
> For mksh, this is even worse as I regularily backport to before
> bookworm so newer version numbers must be able to stay in their
> current canonical (i.e. /bin/) location.
Thanks for letting us know about your backporting plans. I concur that
bookworm and earlier must not move files to /usr as the file move
moratorium still is in effect there. If you were only backporting to
bookworm, dh-sequence-movetousr would achieve that. For bullseye and
earlier, please use a different rune:
override_dh_installdeb:
! command -v dh_movetousr >/dev/null || dh_movetousr
dh_installdeb
This will work on all known releases and do the right thing for
backports. Caveats about restructuring changes still apply and I note
that we are not monitoring bullseye and earlier about such issues. That
seems like a minor issue as these shells are not frequently
restructured.
Helmut
