Your message dated Thu, 06 Feb 2025 11:35:15 +0000
with message-id <e1tg0a7-00bweu...@fasolo.debian.org>
and subject line Bug#1094921: fixed in wtmpdb 0.13.0-6
has caused the Debian Bug report #1094921,
regarding sysvinit-core: does not write entries to wtmpdb
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 ow...@bugs.debian.org
immediately.)
--
1094921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysvinit-core
Version: 3.13-1
Severity: normal
sysvinit-core does not write entries to the new wtmpdb.
I fully understand how deeply unattractive the idea would be of any of
the following approaches to doing this:
- linking with libwtmpdb
- spawning wtmpdb
- doing anything more direct with the wtmpdb sqlite database
But the user experience is obviously not going to be ideal as things
stand. I don't think there's even a decoder tool left in the archive
although old ones still work of course.
runit manages this by spawning wtmpdb asymmetrically: on boot through
stage 1 scripts and on shutdown in the shutdown command.
So I thought it would be best to have a bug to stash considerations
around this from a sysvinit-centric perspective. I did a while back
browse the old threads where wtmpdb was introduced but I can't remember
any input from non-systemd users and rather than go back to the thread I
think we should focus on what we can do from where we are now.
Any thoughts on:
- install an initscript with wtmpdb that imports the missing real wtmp
entries into wtmpdb at boot.
- install an initscript with wtmpdb independently to record startup and
shutdown, but less reliably than init itself would.
- reinstate a classic wtmp toolset and compat for wtmpdb?
Thanks,
Andrew
--- End Message ---
--- Begin Message ---
Source: wtmpdb
Source-Version: 0.13.0-6
Done: Andrew Bower <and...@bower.uk>
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 1094...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrew Bower <and...@bower.uk> (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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2025 06:44:16 +0000
Source: wtmpdb
Architecture: source
Version: 0.13.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Andrew Bower <and...@bower.uk>
Closes: 1094921
Changes:
wtmpdb (0.13.0-6) unstable; urgency=medium
.
* QA upload.
* Patch erratic command line time parsing (LP: #2088387)
* Add initscript to write boot and shutdown entries.
Thanks to Mark Hindley <m...@hindley.org.uk> (Closes: #1094921)
* Minor changes to appease Lintian and lrc
- d/lrc.config: exclude false positive for test code
- d/rules: whitespace change
- pam: remove surplus lintian override following section move
- Override lintian false positive for pam module man page
Checksums-Sha1:
e25c8e7b6ac5a76af4d0a8208ddf341f79e0a0aa 2205 wtmpdb_0.13.0-6.dsc
2c900ea45fc5277b81af10239322dcc007066c91 6416 wtmpdb_0.13.0-6.debian.tar.xz
71ea2f6c6deb8376c23cab0e5d6b81913b0659ce 8748 wtmpdb_0.13.0-6_arm64.buildinfo
Checksums-Sha256:
d1da19935a931f754666a63750056b751f4b3a4dcec9e55cd09b3c22dbc489bf 2205
wtmpdb_0.13.0-6.dsc
2c5dceb887508939715c1a70d36b8998284062786d0c45f8bc75d36bde02118e 6416
wtmpdb_0.13.0-6.debian.tar.xz
5913536adbb70e35b12963183a42fcc6b0fcdc0f8c3b6f9ea9068f97d65951ff 8748
wtmpdb_0.13.0-6_arm64.buildinfo
Files:
ff7df6e8250ecda7afc1d6b2f02fa2f0 2205 admin optional wtmpdb_0.13.0-6.dsc
ac4f6c1f0f4f3a0016cf5e32e9d12ffb 6416 admin optional
wtmpdb_0.13.0-6.debian.tar.xz
d0c0bc578f079d2db31d7b39135def5c 8748 admin optional
wtmpdb_0.13.0-6_arm64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmekmbUACgkQXBPW25MF
LgNXrw//a0LQaXluWm7XXHAOe71ppxgx/k4ms+DQ9FvE5OW87tw8dRGBHkA8OAfm
uesm/nkgOR3IjYrRG+9kGGdc6l+pkpEM9UlGFYyPq/Sk0WQ6LaNnsQHfq9lLnxhZ
7Z+sVN/+klfj5ge7OZBmLgD0VlWzI4lt+tMuGzFTPkbWs8j8EpYhCia3hiLmSb8v
i7rlEc4yEbvGt6I/URAelt9DqjaB8Cssg2lHenKiDGuW4ISHbNdc2V1us1T7iTmB
8xZj+25xdc6RQpl2J/JdMq/O3N+LQem3rEi93HP6H+dfwU8WNZNzV/Q7MpvVAUHU
LDVjmkFPyCqlmCHulIp7Xr8iDyKoWvFVRNR55m/x9FHYiz5mN/CC6hJFGlRv+Q0y
A330hJgdCoBwqRX0EuDrjr3N2vktqWQCq/q9TaF+KvgYo4uGNQb8ZVeckzzd0m8w
2p9PBEzcu5cTpp/RRNgAF1vrQrZN/Uzj5gs0SIIrANTc6F3G9MHCgnRDVO9VtZ26
1A+zRxOkNzMSz7damyYflB5htHmVNGGSlDHs9COI5RO+qLjQ4JvJj9354nXlCPeS
8qDfgToYxrWsVu1dstF5xU18ijRI/1pCr6Wr/wGvzcdeoPMTeGhgmhZrIzF+ClMH
0MJFDH30kQvymmn1UE/2MwxYqP2HSD82N+3Zz//wGlU28fXLwR0=
=4Rli
-----END PGP SIGNATURE-----
pgpWkjmJZtCFC.pgp
Description: PGP signature
--- End Message ---
