Your message dated Sun, 12 Dec 2021 09:52:27 -0500 with message-id <[email protected]> and subject line Close bug #67964 has caused the Debian Bug report #67964, regarding Request for an "ensureuser" command for preinst scripts 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 [email protected] immediately.) -- 67964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=67964 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: fetchmail Version: 5.9.5-1 Severity: important I get an error after today's upgrade: Setting up fetchmail (5.9.5-1) ... chmod: getting attributes of `/var/run/fetchmail': No such file or directory dpkg: error processing fetchmail (--configure): subprocess post-installation script returned error exit status 1 Setting up cvs (1.11.1p1-1) ... Errors were encountered while processing: fetchmail E: Sub-process /usr/bin/dpkg returned an error code (1) If I just touch the file, it works fine: ~-root@aenima>touch /var/run/fetchmail Setting up fetchmail (5.9.5-1) ... Starting mail retrieval agent: fetchmail. Thank you _very_much_ for your time. -- System Information Debian Release: testing/unstable Kernel Version: Linux aenima 2.4.9 #13 Sun Sep 2 23:39:28 CEST 2001 i686 unknown Versions of the packages fetchmail depends on: ii adduser 3.42 Add and remove users and groups to resp. fro ii base-files 2.2.14 Debian base system miscellaneous files ii debconf 1.0.18 Debian configuration management system ii debianutils 1.15 Miscellaneous utilities specific to Debian. ii libc6 2.2.4-5 GNU C Library: Shared libraries and Timezone
--- End Message ---
--- Begin Message ---Greetings: This bug has been tagged as "wontfix" since 2005. I think that a sufficient amount of time has passed to justify us going ahead and marking it as closed. It may help to note that the functions requested here to support maintainer scripts are already suitably provided by other tools, at least on any modern Debian installation. First, if you want to verify that user "mysql" exists on the system, you would invoke something like... if ! getent passwd mysql >/dev/null 2>&1; then # actions for when user does not exist ... fi Second, to verify a user's shell, you would simply receive the output of the "getent passwd" command and parse out the corresponding field in the passwd entry with the utility or shell feature of your choosing. This would apply to groups as well with the "getent group" command. Finally, as Marc Haber noted, overwriting local configuration in a maintainer script is usually a policy violation. So, there should seldom be a need for these types of checks. They are generally only useful when initially creating a system user or group in a maintainer script. I hope sufficient justification has been given for closing this. Let me know if there are any problems I failed to address. Thanks! -- Jason Franklin
--- End Message ---
