Bug#960638: [Pkg-shadow-devel] Bug#960638: Bug#960638: login no longer needs to be essential
* Josh Triplett [200517 22:39]: > On Fri, May 15, 2020 at 01:33:42AM +0200, Chris Hofstaedtler wrote: > > * Josh Triplett [200515 00:21]: > > > It should still have priority "required", and > > > perhaps "Important: yes" so that apt makes sure the user doesn't remove > > > it by accident, but it doesn't need "Essential: yes" anymore. > > > > However, if you keep Important: yes, you'll discover that the Debian > > tooling doesn't deal with this properly, and your package won't > > migrate to testing. So ... I'd recommend avoiding Important: yes. > > I was not aware of that. > > Any reference to a bug report about that? https://alioth-lists.debian.net/pipermail/piuparts-devel/2020-May/009116.html That's the only info I have about that. Chris
Bug#960638: [Pkg-shadow-devel] Bug#960638: login no longer needs to be essential
On Fri, May 15, 2020 at 01:33:42AM +0200, Chris Hofstaedtler wrote: > * Josh Triplett [200515 00:21]: > > It should still have priority "required", and > > perhaps "Important: yes" so that apt makes sure the user doesn't remove > > it by accident, but it doesn't need "Essential: yes" anymore. > > However, if you keep Important: yes, you'll discover that the Debian > tooling doesn't deal with this properly, and your package won't > migrate to testing. So ... I'd recommend avoiding Important: yes. I was not aware of that. Any reference to a bug report about that?
Bug#960638: [Pkg-shadow-devel] Bug#960638: login no longer needs to be essential
* Josh Triplett [200515 00:21]: > It should still have priority "required", and > perhaps "Important: yes" so that apt makes sure the user doesn't remove > it by accident, but it doesn't need "Essential: yes" anymore. However, if you keep Important: yes, you'll discover that the Debian tooling doesn't deal with this properly, and your package won't migrate to testing. So ... I'd recommend avoiding Important: yes. Chris
Bug#960638: login no longer needs to be essential
Package: login Version: 1:4.8.1-1 Severity: wishlist Now that login no longer contains "su", it no longer needs to be an essential package. A system that doesn't run any getty processes or other means of logging in (such as a system using only ssh, or a chroot, or a system with no interactive users at all) may not need to have the login package installed. It should still have priority "required", and perhaps "Important: yes" so that apt makes sure the user doesn't remove it by accident, but it doesn't need "Essential: yes" anymore. - Josh Triplett -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages login depends on: ii libaudit1 1:2.8.5-3+b1 ii libc6 2.30-8 ii libcrypt1 1:4.4.16-1 ii libpam-modules 1.3.1-5 ii libpam-runtime 1.3.1-5 ii libpam0g1.3.1-5 login recommends no packages. login suggests no packages. -- no debconf information
