[Cooker] Media sources changed to official but keys still cooker

View: New views
5 Messages — Rating Filter:   Alert me  

[Cooker] Media sources changed to official but keys still cooker

by Barry Jackson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I am seeing varying mix ups in gpg keys on two machines that were
running cooker and now have been switched to 2010.0 official media.
Both using $MIRRORLIST
Most of the gpg keys (all contrib) are still cooker on one machine, and
virtually all keys ( including Main ) on the other.
As a consequence package installations report bad signatures.

Re: [Cooker] Media sources changed to official but keys still cooker

by Fabrice FACORAT :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

2009/11/5 Barry Jackson <zen25000@...>:
> I am seeing varying mix ups in gpg keys on two machines that were running
> cooker and now have been switched to 2010.0 official media.
> Both using $MIRRORLIST
> Most of the gpg keys (all contrib) are still cooker on one machine, and
> virtually all keys ( including Main ) on the other.
> As a consequence package installations report bad signatures.

it had been said that you should remove all media, and then re-add them again



--
Close the World, Open the Net
http://www.linux-wizard.net

Re: [Cooker] Media sources changed to official but keys still cooker

by Frederic Crozat :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Le jeudi 05 novembre 2009 à 15:06 +0000, Barry Jackson a écrit :
> I am seeing varying mix ups in gpg keys on two machines that were
> running cooker and now have been switched to 2010.0 official media.
> Both using $MIRRORLIST
> Most of the gpg keys (all contrib) are still cooker on one machine, and
> virtually all keys ( including Main ) on the other.
> As a consequence package installations report bad signatures.

contrib key is always cooker keys.

Did you remove ALL your cooker before adding new one ? I wrote a mail to
cooker on tuesday about that (and it is documented in the erratas).

--
Frederic Crozat <fcrozat@...>
Mandriva


Re: [Cooker] Media sources changed to official but keys still cooker

by Barry Jackson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 05/11/09 15:52, Frederic Crozat wrote:

> Le jeudi 05 novembre 2009 à 15:06 +0000, Barry Jackson a écrit :
>> I am seeing varying mix ups in gpg keys on two machines that were
>> running cooker and now have been switched to 2010.0 official media.
>> Both using $MIRRORLIST
>> Most of the gpg keys (all contrib) are still cooker on one machine, and
>> virtually all keys ( including Main ) on the other.
>> As a consequence package installations report bad signatures.
>
> contrib key is always cooker keys.
>
> Did you remove ALL your cooker before adding new one ? I wrote a mail to
> cooker on tuesday about that (and it is documented in the erratas).
>
Yes, I removed everything.
I will remove everything again, then add a full set from mcc and report
back.

Re: [Cooker] Media sources changed to official but keys still cooker

by Barry Jackson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 05/11/09 17:04, Barry Jackson wrote:

> On 05/11/09 15:52, Frederic Crozat wrote:
>> Le jeudi 05 novembre 2009 à 15:06 +0000, Barry Jackson a écrit :
>>> I am seeing varying mix ups in gpg keys on two machines that were
>>> running cooker and now have been switched to 2010.0 official media.
>>> Both using $MIRRORLIST
>>> Most of the gpg keys (all contrib) are still cooker on one machine, and
>>> virtually all keys ( including Main ) on the other.
>>> As a consequence package installations report bad signatures.
>>
>> contrib key is always cooker keys.
>>
>> Did you remove ALL your cooker before adding new one ? I wrote a mail to
>> cooker on tuesday about that (and it is documented in the erratas).
>>
> Yes, I removed everything.
> I will remove everything again, then add a full set from mcc and report
> back.
>
Well that seems to have fixed it so must be my fault :-(
Your ML comment flew under my radar as it was buried in a more general
thread, and I have read the 2010.0 errata several times but I don't see
this issue mentioned.
Sorry for the distraction.