I have a puppet setup which adds the google package signing key, the google repo and then tries to install google-chrome-stable. It has been working fine on many servers for the past 6 months until today when it just broke.
Here are steps to repro (on Ubuntu 12.04.2)
~$ wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add
~$ echo deb http://dl.google.com/linux/chrome/deb/ stable main | sudo tee /etc/apt/sources.list.d/google.list
~$ sudo apt-get update
~$ sudo apt-get install -y google-chrome
The repo is the exact same key and repo that gets added when you manually install the .deb from google, I'm not sure why I can't install it without the following errors now coming up:
~$ sudo apt-get install -y google-chrome-stable
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libwmf0.2-7 libilmbase6 libcdt4 libpathplan4 libopenexr6 libdjvulibre21 libgraph4
libdjvulibre-text
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
google-chrome-stable
0 upgraded, 1 newly installed, 0 to remove and 46 not upgraded.
Need to get 41.9 MB of archives.
After this operation, 160 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
google-chrome-stable
E: There are problems and -y was used without --force-yes
I'm aware that I can force the install but the point is - why has it changed? It used to not complain about this.
apt-get auto-removeafter Idpkg -r'ed it. – Sekm Jun 13 '13 at 05:09