Bug#609876: unattended-upgrades: Doesn't work with arbitary named third party repositories

2011-02-14 Thread Alexander Reichle-Schmehl
Hi! * Michael Vogt [110204 13:41]: > Hi and hhanks for your bugreport! You are welcome! > > 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 i

Bug#609876: unattended-upgrades: Doesn't work with arbitary named third party repositories

2011-02-04 Thread Michael Vogt
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

Bug#609876: unattended-upgrades: Doesn't work with arbitary named third party repositories

2011-01-13 Thread Alexander Reichle-Schmehl
Package: unattended-upgrades Version: 0.62.2 Severity: minor Hi! 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? However, that