Ben Hutchings <[EMAIL PROTECTED]> writes: > On Fri, 2008-04-04 at 23:26 +0100, Ben Hutchings wrote: >> [EMAIL PROTECTED] (Göran Weinholt) wrote: >> > Package: unattended-upgrades >> > Version: 2.0 >> > Severity: critical >> > Tags: security >> >> The latest version is 0.25.1debian1. Which version are you really >> using, and with which distribution? > > I tested 0.2 and 0.25.1debian1 and could not reproduce this, *except* > when using the -d (debug) option. This option, among other things, sets > the APT configuration item Debug::pkgDPkgPM to 1, which causes it to > print dpkg command lines instead of running them. This is not a > documented behaviour, but then the option is not documented at all. > > Is it possible that you are using the -d option on the command line, or > have set Debug::pkgDPkgPM? "apt-config dump" will show the full apt > configuration.
I'm sorry for not answering earlier, somehow I lost your emails. The Version: 2.0 is an unfortunate mistake, I meant 0.2. As if only to make my embarrassment worse, I can no longer reproduce the bug. What I observed was that after running unattended-upgrade, there were still packages that had not been upgraded. Maybe this can be explained by some other theory than my initial theory. If so, then I'm sorry for sending you on a wild goose chase. I did use the -d option, but only when I was trying to find out why it didn't install the upgrades the first time. Perhaps --dry-run would be a better option name: I expected it to be more like --verbose. Am I still correct in believing that it is not enough to simply install the package for it to do upgrades automatically and unattended as described? Thanks, -- Göran Weinholt. Debian developer. Network administrator. "One does not stop the juggernaut by throwing oneself in front of it..." -- From the April 1967 issue of Persuasion.
