Well dug Dan :) On 24/05/2012, at 3:27, Dan Carley <[email protected]> wrote:
> On 27 April 2012 06:15, denmat <[email protected]> wrote: > Normally what happens is that if it is 'assumed yes', yum will > automatically accept the public key via the url - I don't know why > Jenkins is different - but it appears to install a new repo file and > try to import the pubkey again on install - maybe this confuses yum? > Just speculating - not going to investigate further :) > > The problem stems from Yum on EL5 not being able to parse user attributes > within key. It can be worked around a bit more cleanly by removing the > attribute from the public key. I've written a blog post with more details: > > http://dan.carley.co/blog/2012/05/22/yum-gpg-keys-for-jenkins/ > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
