Your message dated Tue, 7 May 2019 20:02:38 +0200
with message-id <20190507180238.gd1...@argenau.bebt.de>
and subject line Re: Bug#926952: sa-exim: Unbuildable/uninstallable in sid
has caused the Debian Bug report #926952,
regarding sa-exim: Unbuildable/uninstallable in sid
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.)
--
926952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sa-exim
Version: 4.2.1-16
Severity: serious
Control: block -1 by 879687
Hello,
with exim4/4.92-5 I have dropped support for sa-exim:
The dlopen localscan patch in exim4 has been nonfunctional in unstable
for quite some time (4.92~RC2-1/experimental/18 Dec, 4.92~RC3-1
unstable/26 Dec and buster/03 Jan). The issue only popped up end of
March on the upstream user support ML.
At this time I opened a tracking bug in exim #925982 and looked at
sa-exim. It is dead upstream since 2006 and buggy:
* https://lists.exim.org/lurker/message/20180726.113354.6d03efde.en.html
* #879687
(This might be same issue, I just do not know. Chunking is
enabled by (upstream) default.)
At this point we (exim4) decided that this was a good time to finally
drop the dlopen localscan patch. We did that and adopted exim
accordingly:
- improve the example/docs for content-scanning in exim without sa-exim
- drop the abovementioned patch and the virtual Provides for
exim4-localscanapi-2.0 and also drop the exim-dev package (only
needed for sa-exim). Exim now also Conflicts with sa-exim.
However, what I did *not* do was consult you before I did this. I am
sorry for that. It is still possible to reinstate exim-dev and try to
fix exim to make sa-exim work again. But imho only if sa-exim is fixed
in the first place and is tested and found to be working with current
exim.
What are your thoughts on this?
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'
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On 2019-05-04 Magnus Holmgren <holmg...@debian.org> wrote:
[...]
> which handles CRLF line endings when scanning headers. Do you think that you
> can then re-enable local_scan for the release?
Thanks for looking into this in detail. I gather that stuff is (now)
a lot less broken than I thought it was.
I have just uploaded -6 unchanged to unstable and am therefore closing
this report.
cu Andreas
PS: Sorry for the delay, I was basically offline last week.
--
`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'
signature.asc
Description: PGP signature
--- End Message ---
