Bug#711826: no more unattended upgrades since Wheezy is out

2013-08-27 Thread Harald Dunkel
Just for the records, this is my current configuration: Unattended-Upgrade::Allowed-Origins { ${distro_id} stable; ${distro_id} oldstable; ${distro_id} stable-security; ${distro_id} oldstable-security; ${distro_id} stable-updates; ${distro_id}

Bug#711826: no more unattended upgrades since Wheezy is out

2013-07-15 Thread Michael Vogt
On Mon, Jul 08, 2013 at 12:09:24PM -0700, Andrew Pimlott wrote: Jumping into this bug... It would definitely help me to have one unattended-upgrades configuration that works without change across multiple Debian releases, even when I choose to stay behind the current stable for a while. The

Bug#711826: no more unattended upgrades since Wheezy is out

2013-07-15 Thread Andrew Pimlott
Excerpts from Michael Vogt's message of Sun Jul 14 23:18:14 -0700 2013: The current version of unattended-upgrades has the following lines: Unattended-Upgrade::Origins-Pattern { origin=Debian,archive=${distro_codename},label=Debian-Security; This should fix the problem. As a

Bug#711826: no more unattended upgrades since Wheezy is out

2013-07-08 Thread Andrew Pimlott
Jumping into this bug... It would definitely help me to have one unattended-upgrades configuration that works without change across multiple Debian releases, even when I choose to stay behind the current stable for a while. The problem is, the archive/suite in Debian release files seems to be

Bug#711826: no more unattended upgrades since Wheezy is out

2013-06-19 Thread Harald Dunkel
Hi Michael, On Mon, 17 Jun 2013 08:09:35 +0200 Michael Vogt m...@debian.org wrote: Attached is a patch for oldstable, unfortunately there is a chicken-and-egg problem here as the update itself will not come from stable-security. So it may well be that there is no solution other than to

Bug#711826: no more unattended upgrades since Wheezy is out

2013-06-17 Thread Michael Vogt
On Fri, Jun 14, 2013 at 06:07:47AM +0200, Harald Dunkel wrote: Changing config files for 1 or 2 PCs is not the problem. The problem is, that its not unattended anymore. I have to access appr. 150 servers, desktops and laptops to make this work again. Thats a lot of work for a package that

Bug#711826: no more unattended upgrades since Wheezy is out

2013-06-14 Thread Teodor MICU
2013/6/14 Harald Dunkel ha...@afaics.de: Changing config files for 1 or 2 PCs is not the problem. The problem is, that its not unattended anymore. I have to access appr. 150 servers, desktops and laptops to make this work again. Thats a lot of work for a package that promised to do its job

Bug#711826: no more unattended upgrades since Wheezy is out

2013-06-13 Thread Harald Dunkel
Changing config files for 1 or 2 PCs is not the problem. The problem is, that its not unattended anymore. I have to access appr. 150 servers, desktops and laptops to make this work again. Thats a lot of work for a package that promised to do its job silently in the background. I would highly

Bug#711826: no more unattended upgrades since Wheezy is out

2013-06-10 Thread Harald Dunkel
Package: unattended-upgrades Version: 0.62.2 Since Wheezy is out the unattended-upgrades for Squeeze don't work anymore. The default configuration in /etc/apt/apt.conf.d/50unattended-upgrades says Unattended-Upgrade::Allowed-Origins { ${distro_id} stable; ${distro_id}

Bug#711826: no more unattended upgrades since Wheezy is out

2013-06-10 Thread Teodor MICU
2013/6/10 Harald Dunkel harald.dun...@aixigo.de: Since Wheezy is out the unattended-upgrades for Squeeze don't work anymore. The default configuration in /etc/apt/apt.conf.d/50unattended-upgrades says Unattended-Upgrade::Allowed-Origins { ${distro_id} stable; stable == wheezy now,