On Mon, Mar 18, 2013 at 02:33:28PM +0100, Arturo Moral wrote:
> Well, after upgrading, unattended-upgrades was launched daily as it should
> be. The only problem then was that it didn't perform any package upgrade
> even when there were things to upgrade.
> After checking the /var/log/unattended-upgrades/unattended-upgrades.log, I
> spotted the problem:

Thanks for this update.
 
> Initial blacklisted packages:
[..]
> The origin used by these packages is Raspbian, not Debian, so I updated my
> /etc/apt/apt.conf.d/50unattended-upgrades file and changed all Debian
> references by Raspbian and the problem seems to be solved by now.

This sounds like the raspbian pi people may want to provide a default
config for unattended-upgrades so that it works out-of-the-box for
them too. Would you mind submiting a bugreport to them? I'm happy to
help them with how to customize unattended-upgrades and carry their
config in my upstream branch.

Cheers,
 Michael
 
> Thanks all of you for your support.
> 
> ♥
> 
> 
> On Tue, Mar 12, 2013 at 6:39 PM, Arturo Moral <amo...@gmail.com> wrote:
> 
> > I just upgraded to version 0.79.5 (current in wheezy).
> >
> > I replaced my old "/etc/apt/apt.conf.d/50unattended-upgrades" config file
> > by the new one and modified some lines:
> >
> > // Automatically upgrade packages from these origin patterns
> > Unattended-Upgrade::Origins-Pattern {
> >         // Archive or Suite based matching:
> >         // Note that this will silently match a different release after
> >         // migration to the specified archive (e.g. testing becomes the
> >         // new stable).
> >         "o=Debian,a=testing";
> >         "o=Debian,a=testing-updates";
> > //      "o=Debian,a=proposed-updates";
> >         "origin=Debian,archive=testing,label=Debian-Security";
> >
> > };
> >
> > // List of packages to not update
> > Unattended-Upgrade::Package-Blacklist {
> > //    "vim";
> > //    "libc6";
> > //    "libc6-dev";
> > //    "libc6-i686";
> > };
> >
> > // This option allows you to control if on a unclean dpkg exit
> > // unattended-upgrades will automatically run
> > //   dpkg --force-confold --configure -a
> > // The default is true, to ensure updates keep getting installed
> > //Unattended-Upgrade::AutoFixInterruptedDpkg "false";
> >
> > // Split the upgrade into the smallest possible chunks so that
> > // they can be interrupted with SIGUSR1. This makes the upgrade
> > // a bit slower but it has the benefit that shutdown while a upgrade
> > // is running is possible (with a small delay)
> > //Unattended-Upgrade::MinimalSteps "true";
> >
> > // Install all unattended-upgrades when the machine is shuting down
> > // instead of doing it in the background while the machine is running
> > // This will (obviously) make shutdown slower
> > //Unattended-Upgrade::InstallOnShutdown "true";
> >
> > // Send email to this address for problems or packages upgrades
> > // If empty or unset then no email is sent, make sure that you
> > // have a working mail setup on your system. A package that provides
> > // 'mailx' must be installed. E.g. "u...@example.com"
> > //Unattended-Upgrade::Mail "root";
> >
> > // Set this value to "true" to get emails only on errors. Default
> > // is to always send a mail if Unattended-Upgrade::Mail is set
> > //Unattended-Upgrade::MailOnlyOnError "true";
> >
> > // Do automatic removal of new unused dependencies after the upgrade
> > // (equivalent to apt-get autoremove)
> > Unattended-Upgrade::Remove-Unused-Dependencies "true";
> >
> > // Automatically reboot *WITHOUT CONFIRMATION* if a
> > // the file /var/run/reboot-required is found after the upgrade
> > Unattended-Upgrade::Automatic-Reboot "true";
> >
> >
> > // Use apt bandwidth limit feature, this example limits the download
> > // speed to 70kb/sec
> > //Acquire::http::Dl-Limit "70";
> >
> >
> > Let's see how things go now.
> >
> > Love.
> >
> > On Sat, Mar 9, 2013 at 2:06 PM, Arturo Moral <amo...@gmail.com> wrote:
> >
> >> On Sat, Mar 9, 2013 at 1:42 PM, Steven Chamberlain 
> >> <ste...@pyro.eu.org>wrote:
> >>
> >>> Hi,
> >>>
> >>
> >> Hello, Steven,
> >>
> >>
> >>>
> >>> Today could you please re-check:
> >>>
> >>> # cat /var/spool/anacron/cron.daily
> >>>
> >> 20130308
> >>
> >>
> >>>
> >>> # grep anacron /var/log/syslog.1
> >>>
> >> Mar  7 12:54:22 raspi anacron[1939]: Job `cron.daily' terminated
> >> Mar  7 12:54:22 raspi anacron[1939]: Normal exit (1 job run)
> >> Mar  7 21:25:01 raspi /USR/SBIN/CRON[32538]: (root) CMD (test -x
> >> /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
> >> Mar  8 00:10:23 raspi anacron[1920]: Anacron 2.3 started on 2013-03-08
> >> Mar  8 00:10:23 raspi anacron[1920]: Will run job `cron.daily' in 5 min.
> >> Mar  8 00:10:23 raspi anacron[1920]: Jobs will be executed sequentially
> >> Mar  8 11:27:42 raspi anacron[1920]: Job `cron.daily' started
> >> Mar  8 11:27:42 raspi anacron[4741]: Updated timestamp for job
> >> `cron.daily' to 2013-03-08
> >>
> >> # grep anacron /var/log/syslog
> >> Mar  8 11:27:51 raspi anacron[1920]: Job `cron.daily' terminated
> >> Mar  8 11:27:51 raspi anacron[1920]: Normal exit (1 job run)
> >> Mar  8 21:25:01 raspi /USR/SBIN/CRON[24741]: (root) CMD (test -x
> >> /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
> >> Mar  8 23:32:17 raspi anacron[1920]: Anacron 2.3 started on 2013-03-08
> >> Mar  8 23:32:17 raspi anacron[1920]: Normal exit (0 jobs run)
> >>
> >> or:
> >>> # zgrep anacron /var/log/syslog.1.gz
> >>>
> >>
> >>> # tail /var/log/unattended-upgrades/unattended-upgrades.log
> >>>
> >> 2013-03-08 11:49:15,488 DEBUG fetch.run() result: 0
> >> 2013-03-08 11:49:15,490 DEBUG blacklist: []
> >> 2013-03-08 11:49:35,734 INFO Packages that are auto removed: ''
> >> 2013-03-08 11:49:35,736 DEBUG InstCount=0 DelCount=0 BrokenCout=0
> >> 2013-03-08 11:49:35,741 INFO No packages found that can be upgraded
> >> unattended
> >> 2013-03-08 12:18:00,782 INFO Initial blacklisted packages:
> >> 2013-03-08 12:18:00,786 INFO Starting unattended upgrades script
> >> 2013-03-08 12:18:00,801 INFO Allowed origins are: ['o=Debian,n=wheezy',
> >> 'o=Debian,n=wheezy-updates', 'o=Debian,n=wheezy-proposed-updates',
> >> 'o=Debian,n=wheezy,l=Debian-Security']
> >> 2013-03-08 12:19:22,738 INFO Packages that are auto removed: ''
> >> 2013-03-08 12:19:22,742 INFO No packages found that can be upgraded
> >> unattended
> >>
> >> All the entries in this log correspond to manual runs from yesterday's
> >> "--dry-run" tests.
> >>
> >>
> >>>
> >>> Thanks!
> >>>
> >>
> >> No problem at all. Thank you for keeping an eye on this.
> >>
> >> Cheers.
> >>
> >>
> >>> Regards,
> >>> --
> >>> Steven Chamberlain
> >>> ste...@pyro.eu.org
> >>>
> >>
> >>
> >


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to