B1;2704;0cOn Thu, Jan 13, 2011 at 01:31:58PM +0100, Alexander Reichle-Schmehl 
wrote:
> Package: unattended-upgrades
> Version: 0.62.2
> Severity: minor
>
> Hi!

Hi and hhanks for your bugreport!
 
> Google's chromium repository doesn't seem to work with unattended-upgrades.
> 
> It's Release file contains:
> 
> Origin: Google, Inc.
> Suite: stable
> 
> So I should add "Google, Inc. stable" to the Allowed-Origins, shouldn't I?

Indeed, there is a escaping issue here, it splits on whitespace. In
the current version you should be able to just write it as "Google,
Inc.:stable" (note the ":" intead of the space).

For the new version (not uploaded yet) it will be:
 Origins-Pattern { "origin=Google\, Inc.,archive=stable"; };
(note the "\"). But the new version will support the old synatax, so
if you add the ":" you should be fine :)

Cheers,
 Michael

> However, that leads to the following error:
> 
> $ sudo unattended-upgrade --dry-run
> Traceback (most recent call last):
>   File "/usr/bin/unattended-upgrade", line 533, in <module>
>     main()
>   File "/usr/bin/unattended-upgrade", line 299, in main
>     allowed_origins = get_allowed_origins()
>   File "/usr/bin/unattended-upgrade", line 89, in get_allowed_origins
>     (distro_id, distro_codename) = s.split()
> ValueError: too many values to unpack
> 
> Seems to be similar to #536754, but that was fixed in 0.62.  So I guess it
> doesn't like the , or . sign.
> 
> 
> Best regards,
>   Alexander
> 
> -- System Information:
> Debian Release: 6.0
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages unattended-upgrades depends on:
> ii  apt                     0.8.10           Advanced front-end for dpkg
> ii  apt-utils               0.8.10           APT utility programs
> ii  debconf [debconf-2.0]   1.5.36           Debian configuration management 
> sy
> ii  lsb-release             3.2-23.1         Linux Standard Base version 
> report
> ii  python                  2.6.6-3+squeeze4 interactive high-level 
> object-orie
> ii  python-apt              0.7.100.1        Python interface to libapt-pkg
> ii  ucf                     3.0025+nmu1      Update Configuration File: 
> preserv
> 
> unattended-upgrades recommends no packages.
> 
> Versions of packages unattended-upgrades suggests:
> ii  bsd-mailx          8.1.2-0.20100314cvs-1 simple mail user agent
> 
> -- Configuration Files:
> /etc/apt/apt.conf.d/50unattended-upgrades changed:
> // Automatically upgrade packages from these (origin, archive) pairs
> Unattended-Upgrade::Allowed-Origins {
>       "${distro_id} stable";
>       "${distro_id} ${distro_codename}-security";
> //    "${distro_id} ${distro_codename}-updates";
> //    "${distro_id} ${distro_codename}-proposed-updates";
>       "Google, Inc. stable"
> };
> // List of packages to not update
> Unattended-Upgrade::Package-Blacklist {
> //    "vim";
> //    "libc6";
> //    "libc6-dev";
> //    "libc6-i686";
> };
> // 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. The package 'mailx'
> // must be installed or anything that provides /usr/bin/mail.
> //Unattended-Upgrade::Mail "root@localhost";
> // Do automatic removal of new unused dependencies after the upgrade
> // (equivalent to apt-get autoremove)
> //Unattended-Upgrade::Remove-Unused-Dependencies "false";
> // Automatically reboot *WITHOUT CONFIRMATION* if a 
> // the file /var/run/reboot-required is found after the upgrade 
> //Unattended-Upgrade::Automatic-Reboot "false";
> // Use apt bandwidth limit feature, this example limits the download
> // speed to 70kb/sec
> //Acquire::http::Dl-Limit "70";
> 
> 
> -- debconf information:
>   unattended-upgrades/enable_auto_updates: false
> 
> 



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

Reply via email to