Your message dated Tue, 4 May 2021 09:30:59 +0200 with message-id <YJD4MzYKljZ3QEa/@chou.cristau.org> and subject line Re: Bug#987924: unblock: exim4/4.94-19 has caused the Debian Bug report #987924, regarding unblock: exim4/4.94-19 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 owner@bugs.debian.org immediately.) -- 987924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987924 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: exim4/4.94-19
- From: Andreas Metzler <ametzler@bebt.de>
- Date: Sun, 2 May 2021 08:16:22 +0200
- Message-id: <[🔎] YI5Dtj+uV2Y0Wv8V@argenau.bebt.de>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock X-Debbugs-Cc: exim4@packages.debian.org Hello, Please consider exim4/4.94-19 for bullseye. Due to the newly introduced tainting mechanism exim upgrades from buster to bullseye currently require a lockstep upgrade of configuration file and exim binary. The new binary will not run with the old configuration and vice versa. -19 brings a patch that adds an option ("allow_insecure_tainted_data") to let the new daemon work with the old configuration at the price of spamming the logfile. -19 adds the option but has it disabled by default. I thought it fit better to _require_ handholding /now/ at dist-upgrade time. I am open to strong opinions to switch it on by default. I would appreciate a timely feedback on this review request. There is a security release scheduled for May 4th https://lists.exim.org/lurker/message/20210421.123632.08bb711a.en.html and I would like to be able prepare an upload and have it propagate to testing ASAP (on the same day!) and not have to discuss "allow_insecure_tainted_data", then. If you do not think that it is possible/wise to accept allow_insecure_tainted_data that quickly I will base the upload for the security release on -17 and will temporarily revert 17-->19. unblock exim4/4.94-19 TIA, cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'Attachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: Andreas Metzler <ametzler@bebt.de>, 987924-done@bugs.debian.org
- Cc: exim4@packages.debian.org
- Subject: Re: Bug#987924: unblock: exim4/4.94-19
- From: Julien Cristau <jcristau@debian.org>
- Date: Tue, 4 May 2021 09:30:59 +0200
- Message-id: <YJD4MzYKljZ3QEa/@chou.cristau.org>
- In-reply-to: <[🔎] YI5Dtj+uV2Y0Wv8V@argenau.bebt.de>
- References: <[🔎] YI5Dtj+uV2Y0Wv8V@argenau.bebt.de>
On Sun, May 02, 2021 at 08:16:22AM +0200, Andreas Metzler wrote: > unblock exim4/4.94-19 Unblocked, thanks. Cheers, Julien
--- End Message ---