On Thu, 2007-03-29 at 06:13 +0530, Rahul Sundaram wrote: <snip> > The yum transaction failed with a unsigned gpg key error. Turned off gpg > key check and reran yum. Yum showed it was downloading 400+ MB but > proceeded to use the rpms build in the cache by presto in the previous > run. However it ended up showing now savings at all in the presto log. > You might want to check how the plugin is handling failed gpg checks. <snip> Okay, I found the problem. Presto was telling yum the package was local after successfully building the rpm, but yum will not import any gpg keys for local packages. Now presto 0.3.1 doesn't tell yum the package is local, but yum checks the local path anyway and won't redownload an rpm that already exists locally. It will also ask to import the public gpg key, just like it does without presto. Thanks for the bug report. Jonathan
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
