Bug 2352958

Summary:	dnf5 does not pull signing keys for repos where signing keys are specified as URL
Product:	[Fedora] Fedora	Reporter:	Tim Flink <tflink>
Component:	dnf5	Assignee:	Evan Goode <egoode>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	41	CC:	egoode, jkolarik, kparal, nsella, pkratoch, ppisar, rpm-software-management
Target Milestone:	---	Keywords:	Regression, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	dnf5-5.2.12.0-1.fc41 dnf5-5.2.12.0-1.fc42	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-03-20 00:17:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tim Flink 2025-03-17 16:03:37 UTC

As of 5.2.11.0, dnf5 does not pull signing certs for repos where signing keys are specified as a URL. This shows up most frequently with third-party repos

Reproducible: Always

Steps to Reproduce:
1. Install third-party repo that specifies a signing key with a URL (e.g https://packagecloud.io/filips/FirefoxPWA)
2. attempt to install package from that repo
Actual Results:  
# dnf install firefoxpwa
Updating and loading repositories:
 FirefoxPWA                                                                             100% |   2.3 KiB/s |   2.7 KiB |  00m01s
>>> Librepo error: repomd.xml GPG signature verification error: Signing key not found                                           
Repositories loaded.
Failed to resolve the transaction:
No match for argument: firefoxpwa
You can try to add to command line:
  --skip-unavailable to skip unavailable packages


Expected Results:  
Valid package from valid repo installs correctly, even if the signing key is specified as URL.

Filed upstream as https://github.com/rpm-software-management/dnf5/issues/2134

Comment 1 Evan Goode 2025-03-17 17:52:16 UTC

https://github.com/rpm-software-management/dnf5/pull/2138 will resolve this.

Comment 2 Kamil Páral 2025-03-18 09:28:20 UTC

F42 Final freeze starts on 2025-04-01, would be great to have the fix included.

Comment 3 Fedora Update System 2025-03-18 23:12:05 UTC

FEDORA-2025-748bf44daa (dnf5-5.2.12.0-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-748bf44daa

Comment 4 Fedora Update System 2025-03-19 02:31:49 UTC

FEDORA-2025-748bf44daa has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-748bf44daa`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-748bf44daa

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2025-03-19 07:43:37 UTC

FEDORA-2025-8a9f93ae43 (dnf5-5.2.12.0-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-8a9f93ae43

Comment 6 Fedora Update System 2025-03-20 00:17:47 UTC

FEDORA-2025-8a9f93ae43 (dnf5-5.2.12.0-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2025-03-20 04:36:44 UTC

FEDORA-2025-748bf44daa (dnf5-5.2.12.0-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.