Your message dated Sat, 25 Nov 2023 14:42:26 +0000 with message-id <e1r6trw-00hg4y...@fasolo.debian.org> and subject line Bug#1043419: fixed in runit 2.1.2-54+usrmerge has caused the Debian Bug report #1043419, regarding runit: ineffective trigger interest due to /usr-merge to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1043419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: runit Version: 2.1.2-54 Severity: important Hi Lorenzo, The runit package declares quite broad trigger interest: | interest-noawait /usr/sbin | interest-noawait /usr/bin | interest-noawait /etc/init.d | interest-noawait /lib/systemd/system Would you be able to shed some light on why it does so? In the mean time, let me explain why I am looking at this. I'm working on finalizing the /usr-merge transition for Freexian SARL and triggers are something that is impacted and runit is affected. A trigger on /usr/sbin and /usr/bin misses out on files installed into those locations via /sbin or /bin. Even if those files end up in the same place due to the aliasing symlinks, dpkg knows them by the location used in the data.tar of the .deb and if that happens to not be the /usr one, it will skip a trigger activation, which may be a problem to runit depending on why it declares such a broad trigger interest. In general, such broad trigger interest seems dubious to me. Can you narrow it down maybe? The trigger interest for /etc/init.d is totally unaffected by the /usr-merge, but the one for /lib/systemd/system will get broken. Currently, packages must install their unit files to the aliased location (due to the file move moratorium and the way debhelper implements that) and runit will get properly activated (except for a minority of units that happen to ship in the /usr location already). As packages move their files from / to /usr, this trigger interest will become ineffective and miss activations. This problem is captured in DEP17 section P2 (a draft of this document is available at https://subdivi.de/~helmut/dep17.html). We're in the process of selecting mitigations for the various problems, but it already is clear that the preferred mitigation for this problem is duplicating triggers (M12), because this mitigation is safe regardless of the other mitigations to be selected. So your trigger file should likely look like this: | ... | interest-noawait /usr/lib/systemd/system | # Duplicate trigger interest according to DEP17-M12 until forky is | # released. | interest-noawait /lib/systemd/system Depending on your answers why you activate on /usr/bin and /usr/sbin you may opt for similarly duplicating those triggers. Note that this issue is actionable now. It will become release critical once we lift the file move moratorium. I hope that to happen in two months as the necessary preparations (one of which is this bug) are ready. If you have any questions, don't hesitate to ask. Helmut
--- End Message ---
--- Begin Message ---Source: runit Source-Version: 2.1.2-54+usrmerge Done: Lorenzo Puliti <plore...@disroot.org> We believe that the bug you reported is fixed in the latest version of runit, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1043...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lorenzo Puliti <plore...@disroot.org> (supplier of updated runit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Mon, 20 Nov 2023 01:36:58 +0100 Source: runit Architecture: source Version: 2.1.2-54+usrmerge Distribution: unstable Urgency: medium Maintainer: Lorenzo Puliti <plore...@disroot.org> Changed-By: Lorenzo Puliti <plore...@disroot.org> Closes: 1043419 Changes: runit (2.1.2-54+usrmerge) unstable; urgency=medium . * Backport "Duplicate triggers as mitigation for usrmerge." from experiemental. (Closes: #1043419) + Thanks to Helmut Grohne <hel...@subdivi.de> * runit.preinst: print a message on unmerged systems warning that such configuration is expected to fail to boot very soon. Checksums-Sha1: 5263a3829043968dd4f4ee3054db971c1bb8479a 2330 runit_2.1.2-54+usrmerge.dsc 6e3edb29166fa43c1326e9fe99016a2719882d4a 63328 runit_2.1.2-54+usrmerge.debian.tar.xz 441a5f499dfeb2fec84415a54e737610b35372c8 7427 runit_2.1.2-54+usrmerge_amd64.buildinfo Checksums-Sha256: 76057c0f4367e8b6768271b8893b35348c3e7040c89a3869db9f03f393409b13 2330 runit_2.1.2-54+usrmerge.dsc bb64ed6f295219b839e1bc1936a8c10cdb401d935d543b400b276efad4888b9a 63328 runit_2.1.2-54+usrmerge.debian.tar.xz 7bb737544f230a41d3a0a487be9c14bd0fcbff0d45e5d6c683abe9965af0cec6 7427 runit_2.1.2-54+usrmerge_amd64.buildinfo Files: a05e916bd7048b62d2dc52cac23cc730 2330 admin optional runit_2.1.2-54+usrmerge.dsc aebeada6f45a64ab74426440633a218b 63328 admin optional runit_2.1.2-54+usrmerge.debian.tar.xz d436e22d0d512f2e60fbccd0aa461b3d 7427 admin optional runit_2.1.2-54+usrmerge_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEETMLS2QqNFlTb+HOqLRqqzyREREIFAmViAV4ACgkQLRqqzyRE REIPIA//b6I8snWJH3s6u/GlwxS2YI/A6A7LZ1zZBb/436yHqKighSgBi0Fw6emk bHYFszTuBKmjD00KBs7gs8OhZ2e4ixmfWD7qV1NDcbHb7RQqXSZ6ivfjp29FseKh KXvWCrp+8mZN5EGfQvpExv9WuXxAiRQfOohOeaMjbc+iRjDLU7BlJ/Sb+36aaxnN PO72n6Cw7G90Y27dxlELUrcoFkHAbXJAM4nDrS68cuMrMl472Ec9YuwZ871wmbNU m8jAGSecqtCxJSyiObw1M2WXNtqzxYAmAOBYUqwO2mOFpxsJPdM+TLXIRfJI/W9R Q0KSwJn73bTBA8pBXG2bHdpiCqzHbwvLKVW1GCwgiK7kixXwNCDJ7zW/8RcusvgR o9Wp/jywZaEuw6PY4wy4k/qHMoVrnUyWZdUX6SP1ebhy5kOyEXc3Z/VBd/94pZ6r BR+LOcO1CD/o2RVo0h9A0jsiplp5lDh6tzvQ72zJg+kFET5FkSXIOgAjkoG7y5c+ aI47IquJZJVEYY/AeLzYLule6278xUlyQCRT+eLSswxl3VKmGkG/Di2MuExtBcEe o3l5CXM9fXOVq36zxywq80h+FlR5312kku7zy/cieKRJgmKnsfUX5Xvj02Ixhnor e4Ix8CD36rwopUsVzVmdyD1Awn86EKAVkPDjoNXcpH1A7YU1zy4= =shEv -----END PGP SIGNATURE-----
--- End Message ---
