Hey, Teodor, On Fri, Mar 8, 2013 at 6:09 PM, Teodor MICU <mteo...@gmail.com> wrote:
> control: -1 severity normal > > 2013/3/8 Arturo Moral <amo...@gmail.com>: > >> This config was removed in version 0.79.5 and might not work at all: > > > > I'm currently using 0.79.4, therefore the config change does not affect > me, > > right? > > You should not use it, 0.79.5 will migrate to testing on the following > days. > I'm using it because it's the current version in testing. It's not a personal choice and I will be happy upgrading to 0.79.5 when that time comes. > > > Anyway, my main issue is that the unattended upgrades don't run. If it > would > > be only a config file problem, they would run but with no upgradable > > candidates. > > You didn't show that u-a doesn't work. From what we've seen so far it > works as expected, maybe you need to investigate why Cron doesn't > run?! > So far, cron is doing its job with the rest of the jobs. I did not find any reference about tweaking cron in unattended-upgrades documentation for making the package works. For me, if unattended-upgrades is not doing its daily check after being enabled and well configured, the package does not work properly. If I missed a final step after installing, enabling and configuring for making it work autonomously, please let me know. > > Do you know for sure that there are packages to be upgraded? Running > "apt-get upgrade" will tell you. If "apt-get" doesn't find packages to > be upgraded, neither does u-a. > I've been doing the upgrades manually and there were several packages to upgrade since I installed and "enabled" unattended-upgrades. Anyway, I'm not having any issue on what updates or what doesn't. I should see a log file inside /var//log/unattended-upgrades/ with details on every day's check but the file didn't exist until I ran a --dry-run days after enabling. > > Cheers >
