Hello.
On Tue, May 14, 2024 at 10:44:37PM +0200, Aurelien Jarno wrote:
> On 2024-05-14 21:51, Chris Hofstaedtler wrote:
> > Hi Eugene,
> >
> > could you please try again with:
> > util-linux 2.40.1-1
> > glibc 2.38-7 or newer
> >
> > and report back, if the problem is fixed for you?
> >
Hi,
On 2024-05-14 21:51, Chris Hofstaedtler wrote:
> Hi Eugene,
>
> could you please try again with:
> util-linux 2.40.1-1
> glibc 2.38-7 or newer
>
> and report back, if the problem is fixed for you?
>
> The newer util-linux is rebuilt against the fixed glibc, so it
> hopefully is now fine.
Hi Eugene,
could you please try again with:
util-linux 2.40.1-1
glibc 2.38-7 or newer
and report back, if the problem is fixed for you?
The newer util-linux is rebuilt against the fixed glibc, so it
hopefully is now fine. It might be necessary to delete your old
utmp/lastlog files tho.
Chris
Control: reassign 1070666 glibc
Control: affects 1070666 util-linux
On Mon, May 06, 2024 at 11:51:50PM +0300, Eugene Berdnikov wrote:
> Upgrade of util-linux from 2.39.3-6 to 2.40-8 on i386 systems breaks
> last(1), while the same upgrade on amd64 systems does not break it.
> Examples on my
Package: util-linux
Version: 2.40-8
Severity: normal
Hello.
Upgrade of util-linux from 2.39.3-6 to 2.40-8 on i386 systems breaks
last(1), while the same upgrade on amd64 systems does not break it.
Examples on my hosts running in 32-bit mode:
5 matches
Mail list logo
