Package: unattended-upgrades
Version: 0.79.5

Short summary: If I do this:

echo 'APT::Get { AllowUnauthenticated "true" }' > 
/etc/apt/apt.conf.d/80allowunauthenticated

then unattended-upgrades considers all packages to be mysteriously
"blacklisted" and they are not upgraded.

This is probably related to this apt bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=353800

It would be nice if unattended-upgrades could have his own logic
regarding what packages are suitable to be upgraded instead of
(apparently) blindly trusting apt when apt is wrong.

If that is not possible, it would be nice if at least debug output
could say *anything* about the reasons why a given package is blacklisted.

The following output is taken from a virtual qemu machine running
Debian 7.1 on which base-files has been downgraded by hand to the
version in Debian 7.0 to see how it is upgraded.

Initial blacklisted packages: 
Starting unattended upgrades script
Allowed origins are: ['o=Debian,a=stable', 
'origin=Debian,archive=stable,label=Debian-Security']
Checking: base-files (["<Origin component:'main' archive:'stable' 
origin:'Debian' label:'Debian' site:'mymirror' isTrusted:True>"])
pkgs that look like they should be upgraded: base-files

Fetched 0 B in 0s (0 B/s)                                                       
fetch.run() result: 0
<apt_pkg.AcquireItem object:Status: 2 Complete: 1 Local: 1 IsTrusted: 0 
FileSize: 78646 
DestFile:'/var/cache/apt/archives/base-files_7.1wheezy1_amd64.deb' DescURI: 
'http://mymirror/debian/pool/main/b/base-files/base-files_7.1wheezy1_amd64.deb' 
ID:0 ErrorText: ''>
check_conffile_prompt('/var/cache/apt/archives/base-files_7.1wheezy1_amd64.deb')
found pkg: base-files
conffile line: '/etc/debian_version a81dbdee5126e79a7099b890c5a36ebe'
current md5: a81dbdee5126e79a7099b890c5a36ebe
conffile line: '/etc/dpkg/origins/debian 731423fa8ba067262f8ef37882d1e742'
current md5: 731423fa8ba067262f8ef37882d1e742
conffile line: '/etc/host.conf 4eb63731c9f5e30903ac4fc07a7fe3d6'
current md5: 4eb63731c9f5e30903ac4fc07a7fe3d6
conffile line: '/etc/issue dba73326d9d6ae1147e8d6793bcdbe07'
current md5: dba73326d9d6ae1147e8d6793bcdbe07
conffile line: '/etc/issue.net b08d336396c8314f778375db545b0e32'
current md5: b08d336396c8314f778375db545b0e32
conffile line: '/etc/os-release 42d92a8b24aacf4b78c2b82a5fa64285'
current md5: 42d92a8b24aacf4b78c2b82a5fa64285
blacklist: ['base-files']
Checking (blacklist): base-files
skipping blacklisted package 'base-files'
package 'base-files' not upgraded
InstCount=0 DelCount=0 BrokenCout=0
Option --dry-run given, *not* performing real actions
Packages that are upgraded: 


By looking at this, how can the user infer that the package is
blacklisted because of an obscure apt bug not having anything to do
with unattended-upgrades?

Thanks.


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to