Thanks for the pointer Scott, appreciated. And also for fixing it in
Debian and consequently in Groovy which is a sync.
I see this fix in version 3.4.13. Hopefully this postfix SRU [1] will be
accepted and we will have version 3.4.11 in Focal, so we have two patch
level releases to consider if we want to update to 3.4.13. Checking the
changelog between 3.4.11 and 3.4.13 there are 6 "Bugfix", 3 "Noise
suppression", and 1 "Bitrot". After a discussion with my team they told
me we would need to define self-contained test cases for each of those
bug fixes and analyze the impact of the non "Bugfix" changes to convince
the SRU team to accept this new micro release.
I did some digging in the postfix-users mailing list and most of those
bugs are discussed there but some are hard to reproduce (build a test
case), there is a case where the OP offered access to their testing
server to one of the postfix maintainers to help debugging the issue
because it was not easily reproducible. With that in mind I think I will
not be able to define good test cases to justify all of them. If someone
could help me defining those test cases I'd be glad to do the rest of
the work.
For now, I am considering to just backport this patch to fix the bug
reported here:
20200530
Bugfix (introduced: Postfix 3.1): "postfix tls deploy-server-cert"
did not handle a missing optional argument. File:
conf/postfix-tls-script.
[1] https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881196
Title:
postfix tls deploy-server-cert fails with "can't shift that many"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1881196/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
