Ask Your Question
1

RPM-GPG case mismatch in packages how do I report a bug or do I need to?

asked 2013-11-22 16:25:40 -0500

four-corners-of-law gravatar image

updated 2014-04-11 16:42:34 -0500

remjg gravatar image

I attemtped to report this on the Red hat system but it's quite unfriendly so I'd like to ask where if anywhere I should report this bug. Upper and lowercase letters in computer language are quite important and I don't know if this is a genuine issue or if the NSA snuck a key in the package (snark). Can anyone tell me if I should report the bug here. I just cut and pasted it as I was reporting it on the red hat system but I didn't want to spend all day figuring out how to use their system for what could be a huge issue or could be a minor issue. Anyway, the keys actually don't match.

keys mismatch on reported keys and the key that I got Alphanurerically with case ignored they are the same but in the computer world upper and lower case make a huge difference, or at least that's what I've been told. incidentally I am an out of work former lawyer and my wife is a copyeditor I would be glad to offer to do some work on editing some documents. I'll copy and paste the requesite portions of the logs from the console so you can see the mismatch. Either I've got a bad package or the keys are generated in some way that I don't understand.

Notice the difference in the keys from the two packages that are supposed to be the same. First and second copy and paste sections highlighting the differences are separated by *** lines. start of first copy and paste begins below. Just look at the keys. That will highlight the problem. I made them bold here so you can easily see what the issue is.


Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-20-x86_64 Importing GPG key 0x246110C1: Userid : "Fedora (20) fedora@fedoraproject.org" Fingerprint: c7c9 a9c8 9153 f201 83ce 7cba 2eb1 61fa 2461 10c1 Package : fedora-release-20-0.7.noarch (@koji-override-0/$releasever) From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-20-x86_64

end of first documentation


beginning of second documentation

[myusername@localhost ~]$ gpg --quiet --with-fingerprint /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-20-x86_64 pub 4096R/246110C1 2013-05-16 Fedora (20) fedora@fedoraproject.org Key fingerprint = C7C9 A9C8 9153 F201 83CE 7CBA 2EB1 61FA 2461 10C1

end of second cut and paste operation


Version-Release number of selected component (if applicable): Fedora 20


awhide.

How reproducible: Heck if I know.

Steps to Reproduce: 1. 2. 3.

Actual results:

Expected results: Possible corrupt package. *







Additional info:

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2013-11-25 04:26:59 -0500

cobra gravatar image

It does look like a bug, if the GPG key wont import.

Check the definitive guide to submitting Fedora bug reports for the simple instructions of how to do it.

Those keys should be encoded in a way that the case makes no difference, and if the new Beta Fedora is checking them out with case sensitivity, then it is wrong. Of course, it's entirely possible that something else is going wrong, but more information about what you were doing and which tools/command lines you were giving at the time of the failure would help them out enormously.

I must admit, I've not really had any problems with the Bugzilla system that the Fedora project use - although I've only ever reported a couple of bugs over the years. It's kinda your end of the contract, though - if you run the Beta version of Fedora, then you should expect some things to be broken, and be diligent enough to report the faults through the bug system.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2013-11-22 16:25:40 -0500

Seen: 237 times

Last updated: Nov 25 '13