Your message dated Sat, 27 Jul 2024 15:21:52 +0000
with message-id <[email protected]>
and subject line Bug#1076640: fixed in wtmpdb 0.13.0-1
has caused the Debian Bug report #1076640,
regarding wtmpdb: last gets the dates wrong on i386 architecture
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.)


-- 
1076640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076640
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wtmpdb
Version: 0.12.0-3
Severity: normal
X-Debbugs-Cc: [email protected]

Hello Chris,
thanks for maintaining this package, which ships command 'last' (as a
symlink).

I installed it on a number of amd64 Debian boxes, without any major
issue.

Then I installed it on the i386 Debian box described below:

  # aptitude install wtmpdb
  [...]
  # exit

Right after having installed it, I have again logged in (through ssh) and:

  $ last
  $USER    ssh          $REMOTE_IP       Thu Jan  1 02:11 - still logged in
  reboot   system boot  6.9.9-686        Thu Jan  1 02:11 - still running
  
  /var/lib/wtmpdb/wtmp.db begins Thu Jan  1 02:11:34 1970

Dates and times seem to be completely wrong, but the system clock is OK:

  $ date -R
  Sat, 20 Jul 2024 16:52:00 +0200

What is funny (or maybe not?!?) is that it seems that it reads all timestamp
as a fixed value. If I log out and then back in, I get:

  $ last
  $USER    ssh          $REMOTE_IP       Thu Jan  1 02:11 - still logged in
  $USER    ssh          $REMOTE_IP       Thu Jan  1 02:11 - 02:11  (00:00)
  reboot   system boot  6.9.9-686        Thu Jan  1 02:11 - still running
  
  /var/lib/wtmpdb/wtmp.db begins Thu Jan  1 02:11:34 1970

In other words, wtmpdb seems to think that everything happens "compressed"
in a single instant at 02:11:34 of January, the 1st, 1970, as in some weird
sci-fi story!   ;-)

Other tools seem to be well aware that we are not living in that weird
sci-fi universe:

  $ who
  $USER    pts/0        2024-07-20 17:09 ($REMOTE_IP)

There must be some bug related with the time_t reading, maybe related to
the fact that i386 has been [excluded] from the 64-bit time_t transition,
thus remaining with the 32-bit time_t...

[excluded]: <https://wiki.debian.org/ReleaseGoals/64bit-time#Decision>


Please fix this bug and/or forward the bug report upstream, as
appropriate.
Thanks for your time (or for your time_t !!!).


P.S.: I would like to see this bug fixed before Thu Jan  1 02:11:34 1970
      ;-p


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: i386 (i586)

Kernel: Linux 6.9.9-686 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wtmpdb depends on:
ii  libaudit1    1:3.1.2-4+b1
ii  libc6        2.38-14
ii  libsystemd0  256.2-1
ii  libwtmpdb0   0.12.0-3

Versions of packages wtmpdb recommends:
ii  libpam-wtmpdb  0.12.0-3

wtmpdb suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: wtmpdb
Source-Version: 0.13.0-1
Done: Chris Hofstaedtler <[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.
Chris Hofstaedtler <[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: SHA256

Format: 1.8
Date: Sat, 27 Jul 2024 16:41:22 +0200
Source: wtmpdb
Architecture: source
Version: 0.13.0-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Hofstaedtler <[email protected]>
Changed-By: Chris Hofstaedtler <[email protected]>
Closes: 1076640
Changes:
 wtmpdb (0.13.0-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #1076640).
Checksums-Sha1:
 bd35a962cd37b090abbf9e41ff4930243f886112 2201 wtmpdb_0.13.0-1.dsc
 3e72451a9063943b62d133f6349a6f366dd5bd22 25912 wtmpdb_0.13.0.orig.tar.gz
 6b3775f2f640f4d1816ef6b247acf772ac7c8c82 3304 wtmpdb_0.13.0-1.debian.tar.xz
 58a3cb6267bb9099dead6cbeeb73ff94ba5e535f 8600 wtmpdb_0.13.0-1_arm64.buildinfo
Checksums-Sha256:
 806cac095acb088809e35f04eb40c549a303b26d8a1edceb4c2671d75a9d9db7 2201 
wtmpdb_0.13.0-1.dsc
 81fb1767838631fe50788408c2c86c3bf26af42c6ed2e11d454f7b14a9a648da 25912 
wtmpdb_0.13.0.orig.tar.gz
 46c87fa63b897548cd74592bbe0171929fda4eea48dd6abcd6a4993466c00f70 3304 
wtmpdb_0.13.0-1.debian.tar.xz
 570281c2c4d2d9ec91030935eb373e4e2f15eb3041cc723cd3aed6b28d9368aa 8600 
wtmpdb_0.13.0-1_arm64.buildinfo
Files:
 bcd9eb2da2afc1a716c3801ff7d3a578 2201 admin optional wtmpdb_0.13.0-1.dsc
 0990d9dca73a3c469fd111e9c635011f 25912 admin optional wtmpdb_0.13.0.orig.tar.gz
 0d3f1bc0432735a77514d23587ca2a48 3304 admin optional 
wtmpdb_0.13.0-1.debian.tar.xz
 0f4787d3081d6c7647f656915650b86b 8600 admin optional 
wtmpdb_0.13.0-1_arm64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmalB+cACgkQXBPW25MF
LgOVyhAApkUiczke51jNdbj7sPdWEXpCYmTjLlvzKS1rm/MV6GLL0AMkWLEhhg0v
0yR+8BGz3OOkXRJCc60N9Lr4FlvwdOjvyt4Wp5r9ig10N5fGUjaRPJ8hr9dugcwz
M+l0gsv0J2wNLFs/8sDX9sQmN9QFLjQnaYSO26lEa1I5L1kfltF9SF5unSzWM9up
9DY8qYRjeqzNo5h3mINZHE+8nF27RXPy+r4naPeeTyJPM6XRBASTKKXyCInl8Asd
Xy9rjNSN9hiKxSINFJD25DCslwGv2pPjLa8S/sy0ttGrmyW3m5+rfls1r8ezgW4q
H7xOhmC05rOSqMfVOF1UDbasEx+iwxR8EXpiAiAuvGbenBw0/XHnkMA3dMS3y2AT
xFAT+EUZvnTzNQ5gu94HnEovfhmELq6LpS3K2fZ7ugOIsBtn2fyYb9GH04vZ+LTI
C/QlpoFqfppIx865OwHenswRLgMqD8PWwwUDzb3Xatx4QAA2tjTS4qFVR71a1R7p
MOah4E2uUgtsz3lLjSO6cHwM3N8S9v7Y0od3DBF+r3iscA2i8UuX43xQnolgEwJ1
Xlwu0paaKnQMJzn+r7aO39Hiwt3dVwFDMvMDk7Ewj2PnqTUgAM4InRVJ/erangNV
2HxHyUBIJBY23Sz0zOP2SGM1eyfI5cMlZJkoSmeb3XIyjcx2FEQ=
=fw87
-----END PGP SIGNATURE-----

Attachment: pgpzTEAFuvUBQ.pgp
Description: PGP signature


--- End Message ---

Reply via email to