Your message dated Tue, 28 Jan 2025 20:57:41 +0000 with message-id <e1tcset-0045fw...@fasolo.debian.org> and subject line Bug#981937: fixed in dh-sysuser 1.6.0 has caused the Debian Bug report #981937, regarding dh-sysuser: Reduce negative impact and assess overall utility 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.) -- 981937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: dh-sysuser Version: 1.3.5 Severity: wishlist X-Debbugs-Cc: plore...@disroot.org Note: CC Helmut Grohne as he started the discussion, CC Niels Thykier as he might want to say something here Helmut Grohne <hel...@subdivi.de>, from #981683: > Further development seems like a good idea. The package uses useradd > instead of the policy-recommended adduser. Is there a good reason for > doing so? The approach taken here entirely sidesteps the established and > declarative sysusers.d format. Is there a reason for not cooperating > with it? Niels Thykier is working a lot on removing maintainer scripts > and turning them into declarative alternatives such as triggers. > dh-sysusers works towards the opposite. Why? As far as I can tell, > project consensus is that system users should not be removed on purge, > but dh-sysuser does so. From my subjectively skewed perception, > dh-sysuser has only created problems, not solved any. I acknowledge that > this is not the whole picture. Short answer: Given that this is an alternative implementation for creating system users related to an alternitive init system, and given the last GR results, it make sense to drive the development of this package in a way that shift the burden from Debian infrastructure and contributors to this package maintainance, whenever this is possible. If dh-sysuser creates problem, then people affected need to report bugs about that. There is nothing i can and i will do if i'm not even aware of the existence of an issue [ this package had 0 bug reported until the beginning of 2021]. I've already opened bugs for the 'adduser'and the 'remove on purge' issues, but that's not the kind of bugs we are talking about. Long answer: Following the last GR, the overall state of 'creating system users' in Debian is getting messy, currently we have * systemd-sysusers [systemd package]: this is destructive on systems with an alternative init system, as installing systemd package will likely remove your Desktop Environment (due to conflict with elogind). This was one of the reason for the existence of dh-sysuser at least at the beginning * opensysusers: in Debian only since 2020; i'm doing some QA maintainance on it to allow it's inclusion in Bullseye. Supposed to work fine with alternative init systems, possibly also with systemd although this setup is not tested (and not sure someone is interested in this) * dh-sysuser: alternative declarative interface to handle creation and removal of users; known to work both with systemd and alternative init systems. It's part of the runit infrastructure. * systemd-standalone-sysusers [ future package ] currently does not exists, not sure when it will, but has been discussed in TC list and some other bug too. Will work fine for alternative init systems. Not sure if it will work on BSD port, wich is relevant for runit As of my personal efforts: I plan to stop doing QA on opensysusers if the standalone package from systemd proves to works fine on all cases that I care (including BDS port). At that point someone else steps in for opensysusers or the package will end up removed (or limited to BDS port). I don't plan to drop dh-sysuser soon as I may need it for runit future development. More about dh-sysuser: > doing so? The approach taken here entirely sidesteps the established and > declarative sysusers.d format. Is there a reason for not cooperating > with it? Niels Thykier is working a lot on removing maintainer scripts > and turning them into declarative alternatives such as triggers. > dh-sysusers works towards the opposite. I don't see it that way, maybe I'm missing something? It's declarative and it parses a file in the source. It allows me to fix things uploading a new version of sysuser-helper, without the need to rebuild the affected package from source. It's probably able to handle many kind of transition without requiring coordination form others maintainers (I guess I will find out soon if it works as expected with the Merged-usr transition). Also (looking at the patch from #981799) I don't see a clear advantage of systemd-sysusers in simlpifying syntax of rules or other files in the /debian directory. One notable difference is that dh-sysuser parses on buildtime while systemd-sysusers parses on runtime, but for Debian I'm not sure what can be the advantage of one approach versus the other. I plan to keep this bug open for the next release cycle so there is time for people to highlight bug or other problems with this package. Regards, Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages dh-sysuser depends on: ii perl 5.32.0-6 dh-sysuser recommends no packages. dh-sysuser suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: dh-sysuser Source-Version: 1.6.0 Done: Lorenzo Puliti <plore...@disroot.org> We believe that the bug you reported is fixed in the latest version of dh-sysuser, 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 981...@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 dh-sysuser 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: Wed, 22 Jan 2025 19:32:31 +0100 Source: dh-sysuser Architecture: source Version: 1.6.0 Distribution: unstable Urgency: medium Maintainer: Lorenzo Puliti <plore...@disroot.org> Changed-By: Lorenzo Puliti <plore...@disroot.org> Closes: 981937 Changes: dh-sysuser (1.6.0) unstable; urgency=medium . * switch to sysusers.d format, deprecate our sysuser format (Closes: #981937) * update dh_sysuser manpage * update sequence, run after installsysusers * postinstall snippet: use minsysusers as fallback * NEWS for dh_sysuser * sysuser-helper: - add minsysusers fallback parser - add manpage for minsysuser * d/copyright: update * d/control: update package description Checksums-Sha1: 0cd026623eff183f28f37fcf15cec3376020a60a 1546 dh-sysuser_1.6.0.dsc da880a6428ad4d408cfe3c5d50280cda2df03aa1 14892 dh-sysuser_1.6.0.tar.xz a5b9c876417927d85af5d06f0b79f65db1de403d 5293 dh-sysuser_1.6.0_source.buildinfo Checksums-Sha256: 247a3e0a599a6a316e19dd954a850e71819a238656833ebdf587c3ff6d4f1984 1546 dh-sysuser_1.6.0.dsc c11f350279c9d7e3c730f664c79cbd8c65a22255349f1ad2b1f9dc70afbf3f60 14892 dh-sysuser_1.6.0.tar.xz 31ce05014e0a318555face6d8ee7138c6df809a2e3b911ebaf82d6362c88fa1e 5293 dh-sysuser_1.6.0_source.buildinfo Files: 321427d2b5f963e9d485d9da8f6538ce 1546 admin optional dh-sysuser_1.6.0.dsc 71bedff25c3993f2605611b191bb01b5 14892 admin optional dh-sysuser_1.6.0.tar.xz 3bd916bab24311cb288443386ed43ffc 5293 admin optional dh-sysuser_1.6.0_source.buildinfo -----BEGIN PGP SIGNATURE----- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmeZOZgQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFFI5C/9Xh7ZV+YKCojv/eDJw3VsEMpBu6Wvn6yR9 Tk8hzn8BAEqLku2AY+//5yTxVDeaPtbo56gRWknfzeP7kMSXtXovcotLnKnUJ4tb FFHcdMWi5zI1NPYrSYtzfcRGq891hRMbPqWlsPfgpZfqL0g/B1U8j8sOctrPzNBh jiI7Koptp75iR9webExZoYpuk7ODS+CrztJDR8fM79OPuEAXqi4RezBfcC05edLY f398TAdxDCx3oaOs2zqRdAQh3k+JA2hhoEdpo1/OS7tU3hdsfOF2wEyT9ifZ5SoW w0+By+zR2bimTpQ2CDiyEaMKSxZRO6UKv1M569aT7CLmywGHDUy8aZmyvTv7gPY5 ku/vynG+setcxduAEFEktl/mrhmD62t2wO5bFkqgIR7UP6C7w5XGBa7WrNyiVqBY R90zYYGjHN12/P2K9jU1TRM2nQpZEqlDPNRM5plGuknGglQUOhNV2+Ffs1UOzzK2 8OEE0OJoPA8lNfb/QNIv2iCRMhpugEQ= =SCfA -----END PGP SIGNATURE-----
pgpWkdolrBgXE.pgp
Description: PGP signature
--- End Message ---
