Hi.
I think that this bug should be closed since they re-enable utmp support in
systemd.
systemd (256.6-1) unstable; urgency=medium
[ Helmut Grohne ]
* salsa-ci: test the stage1 build profile
[ Simon Chopin ]
* Filter out zdev rules in the initramfs hook (LP: #2044104). s390-tools
has its own initramfs customization logic that deals with those files.
[ Luca Boccassi ]
* Re-enable utmp support, tmux's autopkgtests require it. This will
break as logind writing into utmp will wrap around, so Trixie won't be
y2038 ready after all
* New upstream version 256.6
* Note systemd-cryptsetup package split in NEWS (Closes: #1079644)
-- Luca Boccassi <[email protected]> Tue, 10 Sep 2024 18:28:21 +0200
I got this same who problem with systemd 256.5-2 and it fixed downgrading
to 256.5-1. But it's working now after upgrading to 256.6-1.
On Wed, 4 Sep 2024 07:47:05 -0400 Michael Stone <[email protected]> wrote:
> On Wed, Sep 04, 2024 at 12:28:35PM +0200, Vincent Lefevre wrote:
> >On 2024-09-04 11:15:26 +0200, Chris Hofstaedtler wrote:
> >> On Mon, Sep 02, 2024 at 11:15:19AM -0400, Michael Stone wrote:
> >> > On Mon, Sep 02, 2024 at 01:07:59PM +0200, Vincent Lefevre wrote:
> >> > > Severity: grave
> >> > > Justification: renders package unusable
> >> >
> >> > That's a ridiculous severity/rationale
> >
> >I completely disagree. "who" is a standard POSIX utility:
> >
> >https://pubs.opengroup.org/onlinepubs/9799919799/utilities/who.html
> >
> >So, in addition to prevent the use in an interactive shell (without
> >any workaround), you are also likely to break existing scripts.
> >This is a major regression for users of this utility; the current
> >workaround is to stick to systemd 256.5-1.
>
> who is a very minor (and relatively little used) part of the coreutils
> package. Furthermore, it's systemd that broke the standard posix utility
> and the interface that's been in use for literally decades, not who. If
> you'd like to reassign to systemd at a higher priority, go for it.
>
>
