Bug 1689591

Summary:	RFE: Add support for passing a gpgkey file path to --repofrompath
Product:	[Fedora] Fedora	Reporter:	Neal Gompa <ngompa13>
Component:	dnf	Assignee:	Jaroslav Mracek <jmracek>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	dmach, jmracek, jrohel, mblaha, mhatina, packaging-team-maint, pkratoch, rpm-software-management, vmukhame
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	dnf-4.2.2-1.fc30 dnf-4.2.2-1.fc29	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-31 00:04:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1665453

Description Neal Gompa 2019-03-16 20:55:28 UTC

Description of problem:
When trying to produce Mageia containers for alternative architectures, we need to use repos using --repofrompath. However, since --repofrompath doesn't have an optional third argument for setting gpgkey file path, installs fail because it can't verify package signatures.

Version-Release number of selected component (if applicable):
4.2.1-1.fc31

How reproducible:
Always

Steps to Reproduce:
1. Clone https://github.com/juanluisbaptiste/docker-brew-mageia
2. Run mkimage-dnf.sh --rootfs=/code/6/ --version=6 -a armv7hl --mirror=http://distro.ibiblio.org/pub/linux/distributions/mageia/distrib/6/armv7hl

Actual results:
Installation fails due to being unable to validate signatures

Expected results:
--repofrompath takes three parameters, and the last one is the gpgkey, and makes it so that it can validate and install successfully.

Comment 1 Jaroslav Mracek 2019-03-19 11:45:49 UTC

I created a patch (https://github.com/rpm-software-management/dnf/pull/1357) that allows adjustments of configurations using --setopt=<repo>.<option>=value syntax.

Comment 2 Fedora Update System 2019-03-27 13:37:19 UTC

dnf-4.2.2-1.fc30 librepo-1.9.6-1.fc30 libdnf-0.28.1-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b504d6ad8f

Comment 3 Fedora Update System 2019-03-27 13:37:43 UTC

dnf-4.2.2-1.fc29 librepo-1.9.6-1.fc29 libdnf-0.28.1-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7fbfa37585

Comment 4 Fedora Update System 2019-03-27 18:18:25 UTC

dnf-4.2.2-1.fc30, libdnf-0.28.1-1.fc30, librepo-1.9.6-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b504d6ad8f

Comment 5 Fedora Update System 2019-03-27 20:01:55 UTC

dnf-4.2.2-1.fc29, libdnf-0.28.1-1.fc29, librepo-1.9.6-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7fbfa37585

Comment 6 Fedora Update System 2019-03-31 00:04:08 UTC

dnf-4.2.2-1.fc30, libdnf-0.28.1-1.fc30, librepo-1.9.6-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2019-03-31 03:00:45 UTC

dnf-4.2.2-1.fc29, libdnf-0.28.1-1.fc29, librepo-1.9.6-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.