bug#64954: GNU 'uptime' on OpenBSD always prints "0 users"

Thanks, I propagated that into Coreutils and installed the simplified patch I mentioned yesterday. Closing the coreutils bug report.

bug#64954: GNU 'uptime' on OpenBSD always prints "0 users"

I wrote in : > - Gnulib modules should better provide .h files that can be #included > on any platform. Thus, it's Gnulib's task to provide a readutmp.h > and a read_utmp() function that can also be used on native Windows. Done as

bug#64937: "who" reports funny dates

Hi, On Sun, Jul 30, Paul Eggert wrote: > Thorsten's draft coreutils patches > are a bit > long, and I'm hoping we can simplify this by packaging the fix inside > Gnulib (much as we already packaged the fix for not working on >

bug#64954: GNU 'uptime' on OpenBSD always prints "0 users"

Paul Eggert wrote: > > I'm fine with the change, but we'll also need to adjust > > the sc_prohibit_always_true_header_tests syntax check in gnulib > > I looked into that but it's such a hassle that I came up with the > attached simpler patch to Coreutils. How about installing it instead? Yes,

bug#64954: GNU 'uptime' on OpenBSD always prints "0 users"

On 30/07/2023 20:43, Paul Eggert wrote: On 2023-07-30 11:41, Pádraig Brady wrote: I'm fine with the change, but we'll also need to adjust the sc_prohibit_always_true_header_tests syntax check in gnulib I looked into that but it's such a hassle that I came up with the attached simpler patch to

bug#64937: "who" reports funny dates

On 2023-07-31 00:08, Thorsten Kukuk wrote: 1. you need to extend ut_tv from 32bit time_t to 64bit time_t, or your patch will not survive 2038. Yes, that's the plan. Gnulib's readutmp module already does this, in apps that also use the year2038 or year2038-recommended modules (which most do).