Bug#788657: libutempter0: doesn't clean up unused/retired utempter group
Hey Felix On Sun, 2015-06-14 at 11:46 +0200, Felix Geyer wrote: You can't be certain that there are no files on the system that have been chgrp to that group. If the group is removed its gid might get reused. Sure,... which is IMHO one of the several general deficiencies of how Debian handles their system users/groups. But the same would apply to many other packages as well, which in fact *do* remove their users/groups at purge, for many of them where it is even much more likely that people actually used it. The cost of having one more entry in /etc/group is really small so I've decided not to remove the group on upgrade. See also https://wiki.debian.org/AccountHandlingInMaintainerScripts for some more discussion about the pros and cons of removing accounts. May I suggest then, that you add an entry to the NEWS file, where you tell that this is no longer used, and people can typically safely remove it if nothing on their system still uses these as owners? Perhaps even giving a example find / -group foo command to look for such files? That way people would have a more likely chance to notice that change and keep their systems consistent with what fresh installations would have. Thanks, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#788657: libutempter0: doesn't clean up unused/retired utempter group
Hi, On Sun, 14 Jun 2015 00:35:31 +0200 Christoph Anton Mitterer cales...@scientia.net wrote: Package: libutempter0 Version: 1.1.6-1 Severity: normal Hi. Apparently with this release the group utempter is no longer used. This doesn't seem to be one of the base groups as defined by the base-passwd package. It is however not properly cleaned up, so legacy installations would keep it forever without any good reason. Could you please clean that up in one of the following uploads? You can't be certain that there are no files on the system that have been chgrp to that group. If the group is removed its gid might get reused. The cost of having one more entry in /etc/group is really small so I've decided not to remove the group on upgrade. See also https://wiki.debian.org/AccountHandlingInMaintainerScripts for some more discussion about the pros and cons of removing accounts. Cheers, Felix -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557d4d6a.7040...@debian.org
Bug#788657: libutempter0: doesn't clean up unused/retired utempter group
Package: libutempter0 Version: 1.1.6-1 Severity: normal Hi. Apparently with this release the group utempter is no longer used. This doesn't seem to be one of the base groups as defined by the base-passwd package. It is however not properly cleaned up, so legacy installations would keep it forever without any good reason. Could you please clean that up in one of the following uploads? Cheers, Chris. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libutempter0 depends on: ii libc6 2.19-18 libutempter0 recommends no packages. libutempter0 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150613223531.25777.29824.report...@heisenberg.scientia.net
