Am Freitag, 8. Februar 2008 schrieb seth vidal: > On Fri, 2008-02-08 at 11:22 +0100, Hans-Peter Jansen wrote: > > Seth, thanks for your answer, but I fear, you got me wrong. > > I understood what you were saying I just haven't encountered this bug > before. So I wanted to make sure I had all the details > > > 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 didn't say it was due to your setup. I just needed to make sure I > understood all of the issues.
Seth, don't feel offended in any way, I merely talked to myself. > Can you tell me what version of rpm and rpm-python you have installed? > B/c that's the only variable that appears to be different b/t yours and > my installs, really. Sure, rpm 4.4.2 and rpm-python-4.4.2. Since Tim and you cannot reproduce the problem on Fedora, I suspect a SUSE rpm issue. Unfortunately the SUSE 4.4.2 rpm.rpm carries more then 80 additional patches.. Now, which one could affect the signature processing in this silly way, is the big question. The one called signature.diff looks innocent, though. Hopefully, I find some time tomorrow to look into it. Pete _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
