Your message dated Sat, 27 Jan 2018 17:21:17 +0000
with message-id <[email protected]>
and subject line Bug#885537: fixed in nullmailer 1:2.1-6
has caused the Debian Bug report #885537,
regarding nullmailer: Please restore sysvinit support
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.)
--
885537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885537
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nullmailer
Version: 1:2.1-5
Severity: wishlist
Dear Maintainer,
As mentioned in the changelog and discussed in #884980, support for sysvinit
was dropped. For reference, quoting relevant entries:
- changelog.Debian
> * Drop support for sysvinit, due to dropping --daemon divergence from
> upstream
- NEWS.Debian
> * Support for sysvinit is not available in this version. This support
> relied on a patch against upstream which is no longer being carried in
> Debian.
- README.Debian, possibly related
> On request of its users the Debian version of nullmailer-send behaves
> differently from the corresponding upstream release. It forks into the
> background on startup and it sends status output to the system log
> daemon instead to standard error. If you have no running system log
> daemon, output will be sent to /dev/console. As of 1.00RC7-12 this
> behavior is optional and needs to be requested using nullmailer-send's
> --daemon and --syslog options (Debian only), see nullmailer-send(8).
As a result, we have a package that is a really simple and small MTA,
but mandates a given init system. I would even say that considering
nullmailer's purpose is to provide a simple and lightweight alternative
solution to uselessly constraining full-featured MTAs, this comes across
as self-defeating and at odds with your target users.
This moves leaves me shocked and perplexed. I read and understand the
logic behind the systemd-sysv dependency, but the situation seems really
wrong to me.
Please keep packaging a version that supports sysvinit. Please keep
supporting the necessary patch against new upstream versions, or rework
the initscript if possible.
Alternatively, please keep maintaining and packaging version 1.13 that
includes the necessary patch. Personally speaking, there is no way I'm
switching to systemd for nullmailer, so there is no way I'm upgrading
from my working 1.13 version to version 2 with the current dependency.
As mentioned in #884980, please document alternatives to nullmailer,
so users like me can choose between holding the outdated package or
uninstalling nullmailer.
Alternatively, please provide a way for users to install the software
without the mandatory switching to systemd init, and let them tinker
with their own startup solution, perhaps shipping the old initscript in
/usr/share/doc/ as a basis.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages nullmailer depends on:
ii debconf [debconf-2.0] 1.5.65
ii init-system-helpers 1.51
ii libc6 2.25-5
ii libgnutls30 3.5.16-1
ii libstdc++6 7.2.0-18
ii lsb-base 9.20170808
Versions of packages nullmailer recommends:
ii rsyslog [system-log-daemon] 8.31.0-2
nullmailer suggests no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: nullmailer
Source-Version: 1:2.1-6
We believe that the bug you reported is fixed in the latest version of
nullmailer, 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.
David Bremner <[email protected]> (supplier of updated nullmailer 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 Jan 2018 12:06:09 -0400
Source: nullmailer
Binary: nullmailer
Architecture: source
Version: 1:2.1-6
Distribution: experimental
Urgency: medium
Maintainer: David Bremner <[email protected]>
Changed-By: David Bremner <[email protected]>
Description:
nullmailer - simple relay-only mail transport agent
Closes: 885537 886121
Changes:
nullmailer (1:2.1-6) experimental; urgency=medium
.
[ David Bremner]
* Drop "Recommends: rsyslog | system-log-daemon"; a typical user for
nullmailer is probably in minimizing installed packages. Logging is
available via the systemd journal.
* Replace "Priority: extra" with "Priority: optional"
* Assert conformance with standards version 4.1.2
* Restore /etc/init.d/nullmailer, drop dependency on systemd-sysv
(Closes: #886121, #885537).
.
[ Felix Lechner ]
* Removed patch fixing protocol test for TLS (was fixed in 2.1)
* Re-enabled patch avoid race conditions in tests
* Changed watch file to Github
Checksums-Sha1:
05429c0b2ab19ef53aba6d9b0f71a1273d7e31d7 1788 nullmailer_2.1-6.dsc
92dacac374f684fdf8304361a472a1b6052c04eb 27512 nullmailer_2.1-6.debian.tar.xz
Checksums-Sha256:
5f0103452bbc19f6c5f51a0b7d20a124b932a30b5a9e84175286bbc0ae8bf176 1788
nullmailer_2.1-6.dsc
2e758309e043452f0b8228630096ce3cc81cd7fe33d8b7136d39f3ce8417fcbb 27512
nullmailer_2.1-6.debian.tar.xz
Files:
7bdf2d620eb34a5e9b57b48069926d1f 1788 mail optional nullmailer_2.1-6.dsc
3cd589d231c1dd0856e814579b06cd02 27512 mail optional
nullmailer_2.1-6.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlpsr/YACgkQ8gKXHaSn
nixQRQv/XudLJB8wFeXWkp5TC/QVi21PNRKe2Bu4hdyY6FYclLuPPVPOOaPUX5es
/zBx7wRCWAS8dKfNsr3awup3lcy0g1+sKwwuP/JljkrtL+rpGuLBi5UqjgBWAwG+
KHm9OjBY2PP9yxS5UoinRDCasUMZVzFHFkEj55BpbW44cc+fLqsjYDvXVzwuv+dz
BNvTCFdTVOwKFFSXxcahtYPBDFZ4A2fzr7jWJR5EuEnnLQWGR+ekbyMR0MviQQt6
9/6E69VTtKbcakJz2mLKuiJPqVUkinp+45tWf+wN9buvjD/ZguTdMcRbBMv2trA7
dKwJ72+2xS/oXO8+WZX4hZl5DYLfvUooNy3FW2wlwq5Puup5pHW4j2x1falQZspb
uAm+tV7nqODWMFuXlmRlsGXfKogiJCXEm2hkYSB3NU3LzHAnoHnAsueXp+wmk7do
Zy7HxIJzpAwHboH1I3ngdiwaBlm/0QygeLKWBm1IZetvxAPPj6eQvH8QgNi3KS1J
0GXoLBMY
=FXPA
-----END PGP SIGNATURE-----
--- End Message ---
