severity 840064 important
merge 840064 816959 781639
tags 840064 - moreinfo
thanks
Hello,
I'm sorry I wrote my last email thinking about an unattended upgrade
done using the apticron output (or using apticron directly, but this
isn't possible)
I looked to the code more carefully seeing that there is a part to
handle the report oh packages on held status, I suppose it's better
to improve this part despite of using the allow-change-held-packages
switch.
Nevertheless I continue thinking that this bug must not be a grave one,
but also not a normal one, so I'm raising it to important.
On 17/11/2016 17:56, gregor herrmann wrote:
On Thu, 17 Nov 2016 16:57:30 +0100, Francesco Namuri wrote:
thanks for your bug report. I'm downgrading it to normal severity
waiting for more information. IMHO this is not a bug but I'd like
to see the error you're getting. Can you please attach it to
this report?
What I get is a mail from cron:
From: Cron Daemon <root@$domain>
To: root@$domain
Subject: Cron <root@$host> if test -x /usr/sbin/apticron; then
/usr/sbin/apticron --cron; else true; fi
Date: Thu, 17 Nov 2016 16:39:45 +0100
E: Held packages were changed and -y was used without
--allow-change-held-packages.
And that's all.
Trying to automatically update a package that has the "held"
flag it's a dangerous/unwanted behavior, IMHO the warning/error
should be raised and the executions must stop.
It makes apticron pretty useless as I don't get any information about
which (held or not held) packages are available for updating.
The solution proposed "allow-change-held-packages" it's also
very dangerous, as you can see in the man page:
This is in a line with `apt-get -s' i.e. nothing is updated, it's
just about getting the list of packages by simulating an update.
Cheers,
gregor
