On Wed, 29 Sep 2021 09:57:08 +0200 Jan Wagner <w...@cyconet.org> wrote:
> Hi there,
>
> Am 22.09.21 um 22:26 schrieb Jakub Filo:
> > * What led up to the situation?
> > Upgrading to Bullseye, the /lib/systemd/system/postfwd.service file
> > is no longer available and therefore the service does not start - the
> > upgrade effectively broke a working package
> > * What exactly did you do (or not do) that was effective (or
>
> just wonna ask if this bug qualifies for an update in bullseye?
>
> The patch fixing this is:
>
https://gitlab.uncompleted.org/debian/postfwd/-/commit/d0ecd91cc74c6934b53792da0a3bb8a649b6a40d.patch
> and is really trivial. Yes, it is fixed in unstable already.
>
> Thanks, Jan.
> --
> Never write mail to <w...@spamfalle.info>, you have been warned!
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.12
> GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M+ V- PS
> PE Y++
> PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++
> ------END GEEK CODE BLOCK------
As I stated in the report, I fixed it for myself, but I thnk that this
is a bug which breaks postfwd for many people upgrading from Buster to
Bullseye. If you had the systemd service enabled but you did not set
STARTUP=1 in /etc/default/postfwd, then it worked in Buster and does not
work in Bullseye. And systemd does not make it exactly clear that the
service failed to start. I think the update should be done even for such
small thing, as that change was not mentioned in any change log and
broke functionality in a way that required manual invervention.
