On Thu, Oct 02, 2025 at 02:31:15PM +0100, Matthew Vernon wrote:
1) This change to systemd must persist until a satisfactory migration of impacted software has occurred and Policy updated accordingly. 2) This change to systemd must persist until Policy has been updated to allow otherwise. 3) This change to systemd must persist until the TC allows otherwise, which the TC expects to do once a suitable transition plan has been agreed.
The /var/lock change is a good change for us to target. We can't do it without coordinating a transition[1]. I look forward to this change to the distro, and think it's a good thing for the ecosystem to move to. I'm happy to see this change in general.
Because I don't like the idea of TC being involved on an ongoing basis with implementation *and* transition, so i'd rather be clear on the acceptable end-state and let the project work it out - I vote:
A > C > B > N[1]: The Release Team considers everything a transition where the upload of a package requires changes (rebuilds or actual patches) to reverse dependencies. (from https://wiki.debian.org/Teams/ReleaseTeam/Transitions)
-- ⢀⣴⠾⠻⢶⣦⠀ Paul Tagliamonte <paultag> ⣾⠁⢠⠒⠀⣿⡁ https://people.debian.org/~paultag | https://pault.ag/ ⢿⡄⠘⠷⠚⠋ Debian, the universal operating system. ⠈⠳⣄⠀⠀ 4096R / FEF2 EB20 16E6 A856 B98C E820 2DCD 6B5D E858 ADF3
Attachment:
signature.asc
Description: PGP signature