Package: unattended-upgrades
Version: 0.82
Followup-For: Bug #647883
Sam,
As another user of unattended-upgrades, thanks for your patch.
However, it can be marginally improved. By continuing to use
${distro_codename} instead of stable, unattended-upgrades won't
break the moment stable becomes
Unfortunately this is slightly more severe than previously identified.
The previously-linked logs show this:
2013/12/15 18:42:31 [alert] 2889#0: cache manager process 2895 exited
with fatal code 2 and cannot be respawned
In other words, the cache manager cannot run when nginx-extras is
Hi,
Michael Vogt wrote:
I commited it to bzr and it will be part of
the next upload, changelog:
[ Iain Nicol ]
* unattended-upgrade:
- ensure pkgs_to_upgrade stays sorted and fix crash
Let me know if that is accurate enough.
Spot on.
I did a sanity check that bzr head works
Hi Michael,
Thanks for testing [the unattended-upgrade change]! Indeed, when it
re-evals the state it needs to update the pkgs_to_upgrade list as
well. This is fixed in bzr now as well!
Thanks, but if you'll let me drag this bug out a little longer :-)...
There's a problem with the latest
On 2011-09-19, Michael Vogt wrote:
Thanks for your bugreport and sorry for the slow reply. I was on
vacation.
Holidays are good :-).
On Tue, Aug 30, 2011 at 07:26:24PM +, Iain Nicol wrote:
unattended-upgrades ran as scheduled, and successfully
security-upgraded all of the apache
Package: unattended-upgrades
Version: 0.72.3
Severity: minor
Am running unattended-upgrades 0.72.3 from testing, but otherwise I'm
running squeeze.
I had apache2 installed:
aptitude install \
apache2{,-mpm-prefork,-utils,.2-bin,.2-common}=2.2.16-6+squeeze1
unattended-upgrades ran as
6 matches
Mail list logo
