SCIENTIFIC-LINUX-USERS Archives

January 2008

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jan Iven <[log in to unmask]>
Reply To:
Date:
Thu, 31 Jan 2008 10:16:27 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
On 31/01/08 03:25, Michael Mansour wrote:
> Hi,
> 
>> On Thu, Jan 31, 2008 at 10:57:35AM +1000, Michael Mansour wrote:
>>> Is the cern key a valid key?
>>> # rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-cern
>>> error: /etc/pki/rpm-gpg/RPM-GPG-KEY-cern: import read failed(0).
>> It has been like this "for years".
> 
> Hmm.. why not just remove it or get cern to fix their key?
> 
> Is this an issue for TUV or SL?

Neither, this is between CERN and SL.. the key used to work in SL3, but 
newer "rpm" versions insist on a newer GPG key version. The problem 
really just comes from the header lines in the GPG key file, replacing 
1.2.1 with 1.2.6 works for me (which we (obviously) do for our own 
"site" release, SLC4).

Correct key is available from
http://linuxsoft.cern.ch/cern/slc46/x86_64/docs/RPM-GPG-KEY-cern
(untrusted source etc, but the encoded key blob is actually unchanged).

Connie/Troy, could you perhaps add this to the next SL releases 
(4.6/5.2)? I don't think this is worth modifying the current images for.

Sorry
Jan

ATOM RSS1 RSS2