[Yum-devel] signature checking issue if key is installed during session

[Hans-Peter Jansen]

Am Freitag, 8. Februar 2008 schrieb Dr. Peter Poeml:
> On Fri, Feb 08, 2008 at 11:22:27AM +0100, Hans-Peter Jansen wrote:
> > In spite of the fact that yum installed the key in a correct way, it
> > failed to use it in the same session, and succeeds in subsequent
> > sessions only.
> >
> > Now imagine, that you need to set up a new machine with say, 20 missing
> > keys. That leads to a very boring work flow.
> >
> > I cannot believe, that this behavior is due to my setup.
>
> I don't think so either, because it happens to me also.

Thanks for the confirmation. Could somebody from the kind audience sitting 
infront of a fedora latest setup try to reproduce this issue, please?

It could still be related to some SUSE rpm tweaks after all, as I'm sure, 
Peter is running some kind of SUSE setup also ;-).

> (But I'm using an ancient yum (2.4.2) and I wasn't sure that it happens
> with recent yum, but it seems like that!)

Yes, that's what if meant with "rather long standing"..

Peter, do you want updated packages¹? Since 2.4.2 happened a lot, but the 
lastest improvements are really astonishing! 

I couldn't believe the response times on the first few queries / dependancy 
solver runs. Given, that the alternatives were already slower or only 
marginally faster before (IIRC), it will be hard for them to catch up now, 
I believe ;-).

That's why I'm eagerly awaiting those two issues fixed.

Pete

¹) They consist of a few new dependant packages besides yum, but you need to 
rebuild the latter, because I carry my local setup within yum.spec, 
deactivated the dbus based updatesd (ahh looks, like it went into a package 
of its own now), and reanimated the former cron controlled automatic 
update, since it better fits my simple needs. I'm sorry, I should have 
thrown it on the build service already, but...