Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-12-01 Thread Michael Vogt
On Fri, Nov 28, 2014 at 01:23:14PM +0200, Martin-Éric Racine wrote: 2014-11-27 16:58 GMT+02:00 Martin-Éric Racine martin-eric.rac...@iki.fi: 2014-11-27 13:50 GMT+02:00 Alexandre Detiste alexandre.deti...@gmail.com: Sorry, but this hardly qualifies as a log. It only shows the intallation of

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-28 Thread Martin-Éric Racine
2014-11-27 16:58 GMT+02:00 Martin-Éric Racine martin-eric.rac...@iki.fi: 2014-11-27 13:50 GMT+02:00 Alexandre Detiste alexandre.deti...@gmail.com: Sorry, but this hardly qualifies as a log. It only shows the intallation of one single package and a summary. :/ Martin-Éric I had grabbed

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-28 Thread Martin-Éric Racine
2014-11-28 13:47 GMT+02:00 Alexandre Detiste alexandre.deti...@gmail.com: What does run /etc/cron.daily/* on your system ? Have you switched recently to systemd ? Maybe this bug is totally unrelated to unattended-upgrades linked to systemd. I doubt it. Whatever handles cron jobs is not

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-28 Thread Alexandre Detiste
I have just now fixed a potential bug in systemd-cron (setting IgnoreSIGPIPE=false in systemd service file); but maybe anacron.service should be fixed too. I use systemd, but not systemd-cron. Here, anacron does the work. I filled a bug against anacron for this, as this might cause a

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-27 Thread Martin-Éric Racine
2014-11-25 16:59 GMT+02:00 Michael Vogt m...@debian.org: On Mon, Nov 24, 2014 at 08:19:36PM +0200, Martin-Éric Racine wrote: 2014-11-24 12:27 GMT+02:00 Michael Vogt m...@debian.org: On Sat, Nov 22, 2014 at 01:31:39PM +0200, Martin-Éric Racine wrote: 2) Please note that the change to a single

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-27 Thread Alexandre Detiste
Hi, Sorry, but this hardly qualifies as a log. It only shows the intallation of one single package and a summary. :/ Martin-Éric I had grabbed 0.83.2 yesterday from incoming, and the run from this morning was perfect. What I reported was against 0.83 patched with what you had attached

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-27 Thread Martin-Éric Racine
2014-11-27 13:50 GMT+02:00 Alexandre Detiste alexandre.deti...@gmail.com: Sorry, but this hardly qualifies as a log. It only shows the intallation of one single package and a summary. :/ Martin-Éric I had grabbed 0.83.2 yesterday from incoming, and the run from this morning was perfect.

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-25 Thread Michael Vogt
On Mon, Nov 24, 2014 at 08:19:36PM +0200, Martin-Éric Racine wrote: 2014-11-24 12:27 GMT+02:00 Michael Vogt m...@debian.org: On Sat, Nov 22, 2014 at 01:31:39PM +0200, Martin-Éric Racine wrote: 2) Please note that the change to a single log file did not fix what the initial bug report asked,

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-25 Thread Alexandre Detiste
Hi, with version 0.83.1 you still get the full logs? I've tested 0.83.1 . It's now much better, but there are spurious newlines: - body += \n.join(content) + body += .join(content) Alexandre Detiste---BeginMessage--- La mise à niveau automatique a renvoyé : True Packages that were

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-24 Thread Michael Vogt
On Sat, Nov 22, 2014 at 01:31:39PM +0200, Martin-Éric Racine wrote: 2014-10-28 12:51 GMT+02:00 Michael Vogt m...@debian.org: On Wed, Oct 22, 2014 at 07:35:40AM +0200, Alexandre Detiste wrote: control: reopen -1 Since this change, the mail I receive contains the changes from all

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-24 Thread Michael Vogt
On Sat, Nov 22, 2014 at 01:31:39PM +0200, Martin-Éric Racine wrote: 2014-10-28 12:51 GMT+02:00 Michael Vogt m...@debian.org: On Wed, Oct 22, 2014 at 07:35:40AM +0200, Alexandre Detiste wrote: control: reopen -1 Since this change, the mail I receive contains the changes from all

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-24 Thread Martin-Éric Racine
2014-11-24 12:27 GMT+02:00 Michael Vogt m...@debian.org: On Sat, Nov 22, 2014 at 01:31:39PM +0200, Martin-Éric Racine wrote: 2) Please note that the change to a single log file did not fix what the initial bug report asked, which was to document how logging options can be configured. ;)

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-11-22 Thread Martin-Éric Racine
2014-10-28 12:51 GMT+02:00 Michael Vogt m...@debian.org: On Wed, Oct 22, 2014 at 07:35:40AM +0200, Alexandre Detiste wrote: control: reopen -1 Since this change, the mail I receive contains the changes from all previous days. See multiple 'Log Started' in attached mail. Thanks for your

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-10-28 Thread Michael Vogt
On Wed, Oct 22, 2014 at 07:35:40AM +0200, Alexandre Detiste wrote: control: reopen -1 Since this change, the mail I receive contains the changes from all previous days. See multiple 'Log Started' in attached mail. Thanks for your bugreport. The attached patch should fix this problem. It

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-10-21 Thread Alexandre Detiste
control: reopen -1 Since this change, the mail I receive contains the changes from all previous days. See multiple 'Log Started' in attached mail. Log started: 2014-10-19 Log started: 2014-10-20 Log started: 2014-10-22 Alexandre Detiste---BeginMessage--- La mise à niveau automatique a renvoyé 

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-09-11 Thread Michael Vogt
On Fri, Aug 29, 2014 at 05:21:02PM +0300, Martin-Éric Racine wrote: Package: unattended-upgrades Version: 0.82.8 Severity: normal Thanks for your bugreport. [..] While the number of older files kept as unattended-upgrades.log.[1-7].gz and unattended-upgrades-shutdown.log.[1-7].gz remains

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-09-11 Thread Martin-Éric Racine
2014-09-11 16:15 GMT+03:00 Michael Vogt m...@debian.org: On Fri, Aug 29, 2014 at 05:21:02PM +0300, Martin-Éric Racine wrote: Package: unattended-upgrades Version: 0.82.8 Severity: normal Thanks for your bugreport. Thanks for your reply. [..] While the number of older files kept as

Bug#759693: unattended-upgrades: please document how to configure the logging options

2014-08-29 Thread Martin-Éric Racine
Package: unattended-upgrades Version: 0.82.8 Severity: normal By default, unattended-upgrades seems to log the following to /var/log/unattended-upgrades/: unattended-upgrades-shutdown.log (plus gzipped older logs as *.[1-7].gz) unattended-upgrades.log (plus gzipped older logged as *.[1-7].gz)