your recent upload of tor to trixie-backports / aliased files
Michael Biebl <[email protected]> Sat, 3 Jan 2026 16:38:44 +0100
| Newsgroups | gmane.linux.debian.backports.general |
|---|---|
| Message-ID | <[email protected]> |
Hi Peter, you recently made an upload of tor to trixie-backports: https://tracker.debian.org/news/1703357/accepted-tor-04821-1bpo131-source-amd64-all-into-stable-backports/ The relevant part is * Keep systemd files in /lib (as opposed to /usr/lib) In trixie (that includes trixie-backports) all files *must* be installed into /usr. Moving the files back to the aliased location is a policy violation from trixie onwards (and can lead to file loss). For bookworm/bookworm-backports, the file move moratorium was still in place, which means, if your package in trixie shipped files in /bin, /sbin or /lib and you make a bookworm-backport, moving the files back / is correct. This means, you need to differentiate between bookworm-backports and trixie-backports. CCed the backports mailing list to raise awareness of this issue. Regards, Michael
OpenPGP_signature.asc
(application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEECbOsLssWnJBDRcxUauHfDWCPItwFAmlZOAQFAwAAAAAACgkQauHfDWCPItzp 3A//USgx1hH9fNiegU62m4TR5B9dLvffG15ALDtwP32Mwb+YjV1PouOS35z9/mZs2xc+HqQAodBh 6X8A41sMLo2Ql0WI/wdhRjvPKnLqKBpHM+T7x98YrCt7DyEOJKrsfGZ1VL3fzOMbixWapW0oY+jj yDz2L8LI0Omq7TWRJO+PSchGCds5qqzcOPHCBuzSKcoB0ixldOVwKegC/PoMtQg/ej9UGT+1tlx9 bo5alH7VdUhp1JlkMBrNHpWw4Rsb6YdtmOCXbWZoDqzAr022IJQ1ZmAxVz22t09XMsfQGWctf5OM 5nM816IeG8T5jVfafg4s+L86ObJf4miXCfhgtIHT2v6zN3ZMfcExX8646IU601Wu5J4loJsNkwFI S0mYQwYU50BahcBTXdmB6Ln4hHSElKDzR+A/U/tvGANzjsBAHytjzDILI4aIz76JNa01OlYu3F0z Ei9AaZChXz9cFoLs3C8PBRcZuD0vgVmkHrT1a9QyCTyPRY5q40m9Mo7MTPHavV9FzCz4TuIcnDnN 4HMbf8axxnWmdmrwAxUyXH9w8L40dDAzh1zszOfuDqfIZtF2yZD7l5MAZohTGqEQpGBh6j5qeLgS NtiNl8JXFiPYRHeNZ1B1t+ZZd+VeJTL41Q3WMob3vSHmVQIhnWHDmnUHhsGYEF+JkvwtYwLzKO0R HBc= =bnkV -----END PGP SIGNATURE-----