It is true that apticron doesn't use aptitude, but as long as I understand the
problem, this is still an aptitude bug. The question is the way you put
packages on hold. If you use aptitude for that (# aptitude hold foo), neither
apt nor dselect will consider it because it saves that information into an
internal database (see #137771). While if you do that by the traditional way
(# echo "foo hold" | dpkg --set-selections) it is considered by apt-get, and
also by apticron.
I'll block this bug, since it cannot be fixed before having #137771 fixed.
package apticron
block 431869 by 137771
thanks
It is true that apticron doesn't use aptitude, but as long as I understand the
problem, this is still an aptitude bug. The question is the way you put
packages on hold. If you use aptitude for that (# aptitude hold foo), neither
apt nor dselect will consider it because it saves that information into an
internal database (see #137771). While if you do that by the traditional way
(# echo "foo hold" | dpkg --set-selections) it is considered by apt-get, and
also by apticron.
I'll block this bug, since it cannot be fixed before having #137771 fixed.
Regards,
--
Tássia Camões Araújo