Mageia forum

Hello,
I have installed mageia 6. Not sure the repos are configured correctly.
The public keys for the chrome browser google appears twice. It's also twice in the list media.

Code: Select all: urpmq --list-media active Core Release2 Core Updates Nonfree Release2 Nonfree Updates Tainted Updates Core 32bit Release Core 32bit Updates Nonfree 32bit Release Nonfree 32bit Updates chrome_x86_64 google-chrome

cheers

You are missing at least tainted release, for the Mageia repos. The two chrome ones are google repos. You only need one of those, not sure why you set them up twice.
Please show the output of

Code: Select all: urpmq --list-media active --list-url

Code: Select all: [nigel@localhost ~]$ urpmq --list-media active --list-url Core Release2 http://mirror.internode.on.net/pub/mageia/distrib/6/x86_64/media/core/release Core Updates http://mirror.internode.on.net/pub/mageia/distrib/6/x86_64/media/core/updates Nonfree Release2 http://mirror.internode.on.net/pub/mageia/distrib/6/x86_64/media/nonfree/release Nonfree Updates http://mirror.internode.on.net/pub/mageia/distrib/6/x86_64/media/nonfree/updates Tainted Updates http://mirror.internode.on.net/pub/mageia/distrib/6/x86_64/media/tainted/updates Core 32bit Release http://mirror.internode.on.net/pub/mageia/distrib/6/i586/media/core/release Core 32bit Updates http://mirror.internode.on.net/pub/mageia/distrib/6/i586/media/core/updates Nonfree 32bit Release http://mirror.internode.on.net/pub/mageia/distrib/6/i586/media/nonfree/release Nonfree 32bit Updates http://mirror.internode.on.net/pub/mageia/distrib/6/i586/media/nonfree/updates chrome_x86_64 http://dl.google.com/linux/chrome/rpm/stable/x86_64 google-chrome http://dl.google.com/linux/chrome/rpm/stable/x86_64 [nigel@localhost ~]$

doktor5000 wrote:The two chrome ones are google repos. You only need one of those, not sure why you set them up twice.

IIRC if you set up the repo and name it chrome_x86_64 as recommended in the Maqeia, Google chrome may create the second, named google-chrome. That happened to me once.

Jim

I have got rid of the one of the google repos, but there are still 2 google keys.

Well, they are probably the same, but if you don't post them others cannot really tell ?

jkerr82508 wrote:
doktor5000 wrote:The two chrome ones are google repos. You only need one of those, not sure why you set them up twice.

IIRC if you set up the repo and name it chrome_x86_64 as recommended in the Maqeia, Google chrome may create the second, named google-chrome. That happened to me once.

Well nobody provided feedback on the MAQeia so far that this is the case, and I've not added the chrome repo since I installed mga5 initially, and back then the automatic repo configuration by simply installing chrome did not work, so it had to be added manually as update repository. If you can review the MAQeia instructions on a fresh installation I'd be more then happy to update the MAQeia accordingly.

I cannot copy the contents of the MCC keys.
https://pasteboard.co/GCQNvw6.png

cheers

I have just confirmed this on Mageia 5 and Mageia 6

I set up the repository with the name chrome_x86_64
When I installed google-chrome-stable, using rpmdrake, it created a new repo named google-chrome
It also created a cron job which is run daily. That cron job checks for a repo named google-chrome and if it does not find it, it creates it.

I think it would be best if the recommended repo name was changed to google-chrome in:
viewtopic.php?f=36&t=2053

This in fact is what is suggested in:
viewtopic.php?f=36&t=3101

Installing the google key, does install two keys. When associating the key with the repo it is necessary to select the one identified as 7fac5991. In my test the other key, d38b4796, did not work. This should probably be added in the Maqeia.

Jim

Changed the repo name in the MAQeia.

jkerr82508 wrote:When associating the key with the repo it is necessary to select the one identified as 7fac5991. In my test the other key, d38b4796, did not work. This should probably be added in the Maqeia.

That's already mentioned there, just added 7fac5991 a second time for the association of the key with the repo to make it more obvious.

So, is there anyway to fix it?

How to remove the bad key.

There is no problem with having both keys on your system, provided the correct one is associated with the repo as described in: viewtopic.php?f=36&t=2053#p15047 (Scroll down to near the end of that post.)

If you mean how to disassociate the key from the repo, then you use the same dialogue that you use to associate it. There is a remove option.

Jim

Thanks Jim,
I think I have done it. The 7fac5991 key.

cheers
Nigel

Mageia forum

[SOLVED]Google had a bad signature

[SOLVED]Google had a bad signature

Re: Google had a bad signature

Re: Google had a bad signature

Re: Google had a bad signature

Re: Google had a bad signature

Re: Google had a bad signature

Re: Google had a bad signature

Re: Google had a bad signature

Re: Google had a bad signature

Re: Google had a bad signature

Re: Google had a bad signature

Re: Google had a bad signature