-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This looks to be blocked up updates proxy used in Qubes. The purpose of
this proxy is to allow access only to the updates from some repository.
The key is not a part of the repository, thus is blocked. You need to
download the key manually, somehow verify it, then import it using sudo
rpm --import.
> - emacs /etc/yum.repos.d/google-chrome.repo - changed gpgcheck to 0, reran
> the yum command from the web site
>
> I'm bothered about the need to turn off gpgcheck. It makes me wonder if I
> really installed the "official" chrome browser. Anyone have a better
> procedure?
>
> SInce I am still playing around, I may end up reinstalling Qubes from
> scratch and reapplying the correct procedure.
>
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVFnnqAAoJENuP0xzK19cso/YH/0B1xnLrTu9nKMITqQdCiEXB
r0isF76Awe08/MUjjy9badBZZbM8xAQkKOM4dqGjQ5gOcEnI79vXsvSJKjJsMUW2
fy5JCqqGAcWbOf+8iOoZuEuLyTduBZMAUZWdpm14lTTW4s0GhEvLhGPBp5K5JB9Q
x5rqaOEqq9wPkH88sZu8Uf9tijVBgpfkhhtmyCBPW/pEWNt+7R+K0BUw1N3frJsr
LeBhCHp+jZPFphVrw9Gh6/zfGQCMQza18aCaLBKuw66cQWsP5RFbhUk8n4XrQ27n
vb6J9wt16UpBc7NXE11xyGLpNQZW4RNjjb5RQOmSJA8xKv08aMOgSHPxor104gY=
=zC1b
-----END PGP SIGNATURE-----