Bug#854896: exim4: Dpkg fails to upgrade exim4 on debian sid.

2017-02-12 Thread felipe
Hi Andreas! Indeed this host does have ipv6 disabled. After reconfiguring exim4 it finishes the installation and it has been working normally since then. You can close this, as it seems it was a configuration problem on my end rather than a bug with exim4. Thank you for helping out! On 12-02-

Bug#854896: exim4: Dpkg fails to upgrade exim4 on debian sid.

2017-02-12 Thread Marc Haber
On Sun, Feb 12, 2017 at 03:03:12PM +0100, Andreas Metzler wrote: > On 2017-02-12 Marc Haber wrote: > > Why are the exim packages still using /var/run in the first place? I > > think this should be changed after the stretch release. > [...] > > Let's fix this now, when we are already touching the

Bug#854896: exim4: Dpkg fails to upgrade exim4 on debian sid.

2017-02-12 Thread Andreas Metzler
On 2017-02-12 felipe wrote: >> On 11-02-2017 23:25, Vincent Lefevre wrote: >>> fev 11 13:57:11 fx8350 exim4[21370]: ALERT: exim paniclog >>> /var/log/exim4/paniclog has non-zero size…broken >> There may be interesting information in this file. > This is the output: > $ sudo cat /var/log/exim4

Bug#854896: exim4: Dpkg fails to upgrade exim4 on debian sid.

2017-02-12 Thread felipe
Hi, > On 11-02-2017 23:25, Vincent Lefevre wrote: >> fev 11 13:57:11 fx8350 exim4[21370]: ALERT: exim paniclog >> /var/log/exim4/paniclog has non-zero size…broken > > There may be interesting information in this file. > This is the output: $ sudo cat /var/log/exim4/paniclog 2017-02-10 11:20:36

Bug#854896: exim4: Dpkg fails to upgrade exim4 on debian sid.

2017-02-12 Thread Andreas Metzler
On 2017-02-12 Marc Haber wrote: [...] > Why are the exim packages still using /var/run in the first place? I > think this should be changed after the stretch release. [...] Let's fix this now, when we are already touching the init script. cu Andreas -- `What a good friend you are to him, Dr. Ma

Bug#854896: exim4: Dpkg fails to upgrade exim4 on debian sid.

2017-02-11 Thread Marc Haber
On Sat, Feb 11, 2017 at 03:00:29PM -0200, felipe wrote: > fev 11 13:57:11 fx8350 systemd[1]: exim4.service: PID file > /var/run/exim4/exim.pid not readable (y…rectory I would be interested what this line reads in full, and whether /var/run is a proper link to /run, and whether /run/exim4 exists.

Bug#854896: exim4: Dpkg fails to upgrade exim4 on debian sid.

2017-02-11 Thread Vincent Lefevre
Hi, On 2017-02-11 15:00:29 -0200, felipe wrote: > Package: exim4 > Version: 4.89~RC3-1 > Severity: normal > > Dear Maintainer, > > apt upgrade fails to upgrade exim4 and exim4-daemon-light. No problems on my machine. I also have QUEUERUNNER='combined' in the /etc/default/exim4 file. > fev 11

Bug#854896: exim4: Dpkg fails to upgrade exim4 on debian sid.

2017-02-11 Thread felipe
Hello! This is the output: $ cat /etc/default/exim4 # /etc/default/exim4 EX4DEF_VERSION='' # 'combined' - one daemon running queue and listening on SMTP port # 'no' - no daemon running the queue # 'separate' - two separate daemons # 'ppp' - only run queue with /etc/ppp/ip-up.d

Bug#854896: exim4: Dpkg fails to upgrade exim4 on debian sid.

2017-02-11 Thread Andreas Metzler
On 2017-02-11 felipe wrote: > Package: exim4 > Version: 4.89~RC3-1 > Severity: normal > Dear Maintainer, > apt upgrade fails to upgrade exim4 and exim4-daemon-light. [...] > fev 11 13:57:10 fx8350 systemd[1]: Starting LSB: exim Mail Transport Agent... > fev 11 13:57:11 fx8350 exim4[21370]: Sta