Bug 1516631

Summary:	Option to prefer one MirrorManager protocol over the other
Product:	[Fedora] Fedora	Reporter:	srakitnican <samuel.rakitnican>
Component:	dnf	Assignee:	rpm-software-management
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	dmach, ignatenko, jmracek, mhatina, packaging-team-maint, rpm-software-management, vedran, vmukhame
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-29 12:24:43 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:

Description srakitnican 2017-11-23 07:01:02 UTC

Since I am caching packages with Squid, I would like dnf to always use http mirrors over the https ones so that Squid can do its job.

There seems to be an option for metalink URL "&protocol=", but changing that makes all repository files not upgradeable (.rpmnew).

I would like to see a dnf.conf option to specify protocol that should be used.

Comment 1 Daniel Mach 2017-11-29 12:24:43 UTC

We recommend using rpmconf or python3-dnf-plugin-rpmconf to manage the .rpmnew files.
We'd like to avoid changing dnf just to avoid config file handling.