Comment 6 for bug 1687129

Revision history for this message
Steve Langasek (vorlon) wrote :

My output with precise-updates:
$ sudo unattended-upgrades --debug --dry-run
Initial blacklisted packages:
Starting unattended upgrades script
Allowed origins are: ['o=Ubuntu,a=precise-security']
Checking: unattended-upgrades (["<Origin component:'main' archive:'' origin:'' label:'precise archive' site:'esm.ubuntu.com' isTrusted:True>"])
pkgs that look like they should be upgraded:
Fetched 0 B in 0s (0 B/s)
blacklist: []
InstCount=0 DelCount=0 BrokenCout=0
No packages found that can be upgraded unattended and no pending auto-removals
$

My output with precise-proposed:
$ sudo unattended-upgrades --debug --dry-runInitial blacklisted packages:
Starting unattended upgrades script
Allowed origins are: ['o=Ubuntu,a=precise-security', 'o=UbuntuESM,a=precise']
Checking: unattended-upgrades (["<Origin component:'main' archive:'' origin:'' label:'precise archive' site:'esm.ubuntu.com' isTrusted:True>"])
pkgs that look like they should be upgraded:
Fetched 0 B in 0s (0 B/s)
blacklist: []
InstCount=0 DelCount=0 BrokenCout=0
No packages found that can be upgraded unattended and no pending auto-removals
$

So it's not being installed. It doesn't look like the publication changes are live on esm.u.c.