Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1516631 - Option to prefer one MirrorManager protocol over the other
Summary: Option to prefer one MirrorManager protocol over the other
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-23 07:01 UTC by srakitnican
Modified: 2017-11-29 12:24 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-29 12:24:43 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1247076 None None None Never
Github fedora-infra mirrormanager2 issues 100 None None None Never

Internal Links: 1247076

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.


Note You need to log in before you can comment on or make changes to this bug.