Print

Print


On 3/5/12 10:32 PM, Steve Traylen wrote:
>
>
>
> On 5 Mar 2012, at 22:31, "Govind Songara" <[log in to unmask] 
> <mailto:[log in to unmask]>> wrote:
>
>> Thanks Cristina for fixing it.
>
> What was the problem? Just for interest,
forgot to EMI-sign some globus-* third-party packages.

C
>>
>>
>> On Mon, Mar 5, 2012 at 8:25 PM, [log in to unmask] 
>> <mailto:[log in to unmask]> <[log in to unmask] 
>> <mailto:[log in to unmask]>> wrote:
>>
>>     Hi,
>>
>>     the "signed" third-party repository is now ok.
>>     Please try again, sorry for the problems.
>>
>>     Cristina
>>
>>
>>     On 3/5/12 5:33 PM, Govind Songara wrote:
>>>     Hi Steve,
>>>
>>>     I have installed one of epel pkg  which is pulled by emi  i.e
>>>     bouncycastle
>>>     But emi cream install still complains..
>>>     ===================
>>>     warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key
>>>     ID b4d025b3
>>>     EMI-1-third-party/gpgkey                                 | 1.7
>>>     kB     00:00
>>>
>>>     Public key for globus-gsi-sysconfig-3.2-1.el5.x86_64.rpm is not
>>>     installed
>>>     ===================
>>>
>>>
>>>     On Mon, Mar 5, 2012 at 3:29 PM, Steve Traylen
>>>     <[log in to unmask] <mailto:[log in to unmask]>> wrote:
>>>
>>>         On Mar 5, 2012, at 4:01 PM, Govind Songara wrote:
>>>
>>>         > I am trying to install a EMI-1 cream  as per instruction here.
>>>         >
>>>         https://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1
>>>         >
>>>         > There were two problem faced..
>>>         > 1. epel rpm is not accessible
>>>         >
>>>         http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm
>>>         > which is  available from download.fedoraproject.org
>>>         <http://download.fedoraproject.org>
>>>         > 2. emi-cream-ce install  fails with message
>>>         > Public key for globus-gsi-sysconfig-3.2-1.el5.x86_64.rpm
>>>         is not installed
>>>         >
>>>         > Any advise.
>>>         This will be (I expect) because EMI added the EPEL signed
>>>         packages to their own repository but
>>>         the EMI signed repo file will not reference the EPEL key.
>>>
>>>         Import the EPEL key which can be done by installing any one
>>>         package from EPEL and then you should be fine.
>>>
>>>         Steve.
>>>
>>>
>>
>>