Your message dated Sun, 13 Jul 2025 18:34:00 +0000 with message-id <e1ub1ws-004zyk...@fasolo.debian.org> and subject line Bug#1108377: fixed in bsd-mailx 8.1.2-0.20220412cvs-1.1 has caused the Debian Bug report #1108377, regarding bsd-mailx: allow TMPDIR env to override /tmp 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.) -- 1108377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: chkrootkit Version: 0.58b-4 Severity: minor Dear Maintainer, since I've upgraded systems to trixie, logcheck mails me daily system events like these: Jun 27 00:01:21 hostname chkrootkit-daily[2588815]: sending alert to root: [chkrootkit] alert for hostname.example.org Jun 27 00:01:21 hostname chkrootkit-daily[2589917]: mail: /tmp/mail.RsXXXX8kWKZT: Read-only file system That is while: - the system can send mails - /tmp is writable - chkrootkit reports no issues Obviously I can rather easily ignore those in logcheck but I would like to know what's going on first. Do you have any idea? Thanks for maintaining chkrootkit! -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Democracy in the US is dying not in darkness but in the bright light and its death is televised.
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: bsd-mailx Source-Version: 8.1.2-0.20220412cvs-1.1 Done: Andrew Bower <and...@bower.uk> We believe that the bug you reported is fixed in the latest version of bsd-mailx, 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 1108...@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 bsd-mailx 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, 09 Jul 2025 23:03:16 +0100 Source: bsd-mailx Architecture: source Version: 8.1.2-0.20220412cvs-1.1 Distribution: unstable Urgency: medium Maintainer: Robert Luberda <rob...@debian.org> Changed-By: Andrew Bower <and...@bower.uk> Closes: 1108377 Changes: bsd-mailx (8.1.2-0.20220412cvs-1.1) unstable; urgency=medium . * Non-maintainer upload. * Patch to honour TMPDIR. (Closes: #1108377) Thanks: Richard Lewis, Holger Levsen. Checksums-Sha1: 259cb48caa226d9aa1644bbe06ab59985b319ac0 1586 bsd-mailx_8.1.2-0.20220412cvs-1.1.dsc d771bb740bfb0ba938f7ff487bb013cc8b2831a4 49836 bsd-mailx_8.1.2-0.20220412cvs-1.1.debian.tar.xz 7834a11195855e7bbc3e2fd7ce26a8ba199373a1 5721 bsd-mailx_8.1.2-0.20220412cvs-1.1_source.buildinfo Checksums-Sha256: e260dc101ecf4b5f3c5ec902ae45c4cbf210e10bcb0800f81d467fa36a73c040 1586 bsd-mailx_8.1.2-0.20220412cvs-1.1.dsc f2743b28ec1e3822e914575c3677669041ea97abf3ce454a269859d287c1c364 49836 bsd-mailx_8.1.2-0.20220412cvs-1.1.debian.tar.xz 6bf2d4b477c8e3fc4d577a69be87c7a0d299523d8c407c28d8f72f8085c8ad99 5721 bsd-mailx_8.1.2-0.20220412cvs-1.1_source.buildinfo Files: f001e20fd394ccb1e7e0cf88c2749363 1586 mail optional bsd-mailx_8.1.2-0.20220412cvs-1.1.dsc fde3385e2643b0980a1e59f6a181bc68 49836 mail optional bsd-mailx_8.1.2-0.20220412cvs-1.1.debian.tar.xz fc606697974c66264d95c7a15bee9288 5721 mail optional bsd-mailx_8.1.2-0.20220412cvs-1.1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE9ecZmu9eXGflVYc/dA1oiINl0okFAmhz+i8ACgkQdA1oiINl 0onAJgf+PPrsTE2/OxuwumL+CnDe3vZ9io8dIbqigpbEUDjomorkkPJ9uWF2TOEG g6OA2MDe1DhM8ghWey73Vy+rGRkGqN7NOkxDXfNGU43W7LFTB3JXsxU1l6qmfVTu Fwk8UKiafLOJ/Y0xUhTNvybh0sYMyJxAEfDKhHcTt7LMqr2CtU1cOBAbMNpfsV8E ELUhLMZDF6lp8ocCX8XRo8Vf4NydIK5iXe3SIXwoLAyU1YipS+qObx2C7pJMFGMn uswThVAhu9KOC8vK649hiJXifmUhgrJ9KQrjb2ooEM3DPUyPj86iSl9HIEVR2Bfz 6b6bJsQFzHds8rSKqAY0t9UqApX4CA== =dDZb -----END PGP SIGNATURE-----
Description: PGP signature
--- End Message ---
