Bug#1091315: delgroup did not delete the requested group from other groups

. How to reconstruct? Manualy run vigr and vigr -s to resemble the situation, and delgroup debian afterwards. -- u34

Bug#1014219: Do improve the language of /etc/ca-certificate.conf

-english/2022/07/msg1.html , and improve the language of /etc/ca-certificates.conf. I am sure users of lists.debian.org/debian-l10n-english can, and will, help. Thank you -- u34

Bug#1010455: Should apache2.README.Debian refer to apache-htcacheclean ?

htcacheclean' ? The context is the configuration file for using mod_cache_disk. -- u34

Bug#994020: dpkg-reconfigure debconf db modes (permitions) not as configured

Package: debconf Version: 1.5.77 dpkg-reconfigure debconf sets files in /var/cache/debconf whosemodes (permitions) are not as configured in /etc/debconf.conf. I guess it is also because of the umask setting. How to reproduce? 1. Set the mode of config at /etc/debconf.conf to 0644. 2. Manually c

Bug#991857: /etc/skel/.profile suggests installing non existant package

umask # with pam-umask at /etc/pam.d/common-session{,-noninteractive}. #umask 022 -- u34

Bug#981283: Should the daemon started at postinst?

d. Prevoiusly, I was only looking for messages in systemd journal. Where there was no explicit error, other then stating nsd failed. Or that I erroneously skipped such a message. Right now I was also looking at the syslog files. Indeed, there is a specific message about an address being used. I am not sure a query for a listener shouldn't be done by postinst. I agree that on package upgrade, I would hope the daemon would bestarted without the admin intervention. What is the point of starting the daemon at postinst, after the package is installed for the 1st time, when there might be no domain file set for it? -- u34

Bug#981283: Should the daemon started at postinst?

-i /var/cache/apt/archives/nsd_4.1.26-1_amd64.deb -- u34

Bug#976721: No mailing list with 10.7 announcement?

Package: lists.debian.org Severity: normal Is it deliberate that debian-annou...@lists.debian.org, and most probably any related mailing list, doesn't have a stable 10.7 announcement? I have checked the debian-announce list archive prior to sending this report. -- u34

Bug#967919: kernel panic at boot

Package: linux-image-4.19.0-10-amd64 Version: 4.19.132-1 Severity: critical Causes a kernel panic at boot. I have only managed to capture The bottom lines of the panic message. A screen shot is at https://imgur.com/a/ETtMtT2 . Both linux-image-4.19.0-9-amd64 4.19.118-2+deb10u1 and linux-image-4.