Your message dated Thu, 10 Apr 2025 10:35:18 +0000
with message-id <[email protected]>
and subject line Bug#1102101: fixed in wtmpdb 0.73.0-1
has caused the Debian Bug report #1102101,
regarding wtmpdb: Argument `last -p <TIME>` not working (UTC / local-time?)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1102101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102101
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wtmpdb
Version: 0.72.0-1
Severity: normal
Dear Maintainer,
for the command-line argument `last -p <TIME>` there are existing at
least 4 issues:
1. last -p now
Works on the older util-linux version and shows all current
"still ..." active sessions. But the wtmpdb version, which I am
reporting here outputs
$> last -p now
Invalid time value 'now'
2. last -p <TIME>
The <TIME> is neither interpreted as UTC nor as local time. My
current system is using time zone (+0100) plus summer time, which
results in (CEST, +0200).
$> timedatectl
Local time: Sat 2025-04-05 04:08:45 CEST
Universal time: Sat 2025-04-05 02:08:45 UTC
RTC time: Sat 2025-04-05 02:08:45
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
In the following example a su(1) session starts at 03:39 local
time. To request it using -p argument I need to substract 1h,
i.e. 02:39. Don't know why 1h.
$> wtmpdb last -p '2025-04-05 02:40:00'
root pts/0 Sat Apr 5 03:39 - 03:47 (00:07)
dirk tty7 :0 Sat Apr 5 01:48 - still logged in
reboot system boot 6.12.20-amd64 Sat Apr 5 01:27 - still running
wtmpdb begins Fri Apr 4 19:01:21 2025
$> wtmpdb last -p '2025-04-05 02:38:00'
dirk tty7 :0 Sat Apr 5 01:48 - still logged in
reboot system boot 6.12.20-amd64 Sat Apr 5 01:27 - still running
wtmpdb begins Fri Apr 4 19:01:21 2025
3. last -p <RFC 3339 TIME>
Wishlist: Would be nice if <TIME> accepts fully the RFC 3339
format. Then the following example should work, which is
equivalent to `last -p now`:
$> last -p "$(date --rfc-3339=seconds)"
Invalid time value '2025-04-05 04:26:47+02:00'
4. last -p
Wishlist: Would be nice to make the <TIME> optional, like
[<TIME>]. This should be equivalent to `last -p now`.
Greets,
Dirk =)
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.20-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages wtmpdb depends on:
ii init-system-helpers 1.68
ii libaudit1 1:4.0.2-2+b2
ii libc6 2.41-6
ii libsystemd0 257.4-3
ii libwtmpdb0 0.72.0-1
Versions of packages wtmpdb recommends:
ii libpam-wtmpdb 0.72.0-1
wtmpdb suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: wtmpdb
Source-Version: 0.73.0-1
Done: Andrew Bower <[email protected]>
We believe that the bug you reported is fixed in the latest version of
wtmpdb, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrew Bower <[email protected]> (supplier of updated wtmpdb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 09 Apr 2025 19:29:42 +0100
Source: wtmpdb
Architecture: source
Version: 0.73.0-1
Distribution: unstable
Urgency: medium
Maintainer: Andrew Bower <[email protected]>
Changed-By: Andrew Bower <[email protected]>
Closes: 1083228 1102101
Changes:
wtmpdb (0.73.0-1) unstable; urgency=medium
.
[ Andrew Bower ]
* New upstream version
- drop patches adopted upstream
- fixes time specifications (Closes: #1102101)
* patch to fix import of logins recorded by some wtmp writers
* refine man page for debian, appeasing lintian
* d/control:
- further extend package descriptions (Closes: #1083228)
- mark libwtmpdb-dev as Multi-Arch: same
* d/copyright: set missing Upstream-Contact field
Checksums-Sha1:
036ae28ba218919e6d5d3cbd23f55a5a9b060d21 2282 wtmpdb_0.73.0-1.dsc
e9f7bf7566b2b4273792d8f94c238cb938273664 41082 wtmpdb_0.73.0.orig.tar.gz
0b75e2b3c4a68b5514c4447bcc375b5ef13b9466 8824 wtmpdb_0.73.0-1.debian.tar.xz
2d7c57e744dbd0fc2357b6ba9363e2cf76d26408 8720 wtmpdb_0.73.0-1_arm64.buildinfo
Checksums-Sha256:
35534a5e2a4605a4c0db669e48e4393bf303e7e15b410b70343173f06eb9309d 2282
wtmpdb_0.73.0-1.dsc
6d77454bf196e07fa3b43c1b4346ce608af147c22486889d61bc1c74fc1a8f5e 41082
wtmpdb_0.73.0.orig.tar.gz
f08caf20681748ffda420e3e676a1c9e875db5fd1b8dead44fb7ac64c1c9826a 8824
wtmpdb_0.73.0-1.debian.tar.xz
e2f9cec289235825bf653e1bfa7d108d15ede2355756e2a54183f413f460a19d 8720
wtmpdb_0.73.0-1_arm64.buildinfo
Files:
3954bc22598ab7de588b11453b719d9b 2282 admin optional wtmpdb_0.73.0-1.dsc
b38a987fde377484af0302aef1a0c28d 41082 admin optional wtmpdb_0.73.0.orig.tar.gz
c2f32c6f86511995f42c21207e0be643 8824 admin optional
wtmpdb_0.73.0-1.debian.tar.xz
fcd38f9609f36fca990801ea788c39e2 8720 admin optional
wtmpdb_0.73.0-1_arm64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmf3nWkACgkQXBPW25MF
LgOEJA//XWJSzjRtOjqgj/k31vp9ZrOu8Ri+vqgkzQHIPNQUUNq0J3uwUmh2EcVo
YFb3LQ1IoAFoXGMpF109NLzC/tPLfwvdx1Mdtmn63ovOFa/9j/izoGbXefZDh8uM
90trrbTsn/fJX8wMXrKdQyhGNe97XMluAWo9AZfTkiWe8Aii/o/n/HDJja13vMy0
4D4S3Ao3CNGX8VfoDn6lnga9APpAGOxbGfRECPMUPauQNh8lv+8GAF5OFPLfgknd
Rsj2GsQRN6r2vjSr+bA1B4ZyUUtu8upCDrfxzgJN8WSMqGd6hwgzFWQa5mX8gN1a
EbcRsBVCjyD+dyzZ3+9f+GrsdMV4tEWHhRzqSqeNw8kuqOZKW5i/xseyTj5usflD
PaH8TvhC8FWeEDGGNN9pGD2het41H8UDdYZoalaq2+bRGCQ7pFYzqRzYNVfYAtj2
6eVmoF+qIzXI5Bkx+JiUZQ12Sam1+jxKbYcW5jY9XnoQEr7zvCv9L8nu/uVukwlH
Q4uKZ93V9xEdVCW/PK8rUej2wHNf83cKUMPfC73RHdT/kHUH3n94WYJntUrzlkVt
oMzuLmg27QGez0At7HzYc9gQ1iVWaBR3A3TcMRHlvPcJYctUllod5Xv/JsLc6+jC
Pqug4KrlXe+/EJqLazefHzt8pVCHSgZgglf1bIGCzQYdi6BB0vA=
=LrOY
-----END PGP SIGNATURE-----
pgpPAnau0E0PH.pgp
Description: PGP signature
--- End Message ---
