Bug 1411349 - dnf makes wrong assumptions about metalinks
Summary: dnf makes wrong assumptions about metalinks
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 578256
TreeView+ depends on / blocked
 
Reported: 2017-01-09 14:33 UTC by Daniel Mach
Modified: 2017-02-10 16:00 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-02-10 16:00:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Daniel Mach 2017-01-09 14:33:51 UTC
When repo config contains:
metalink=...
but there's no 'metalink' string in the URL,
dnf/librepo considers the metalink address a mirrorlist and fails on unknown URL:

error: Curl error (6): Couldn't resolve host name for http://<metalink xmlns:mm0="http://fedorahosted.org/mirrormanager" xmlns="http://www.metalinker.org/" version="3.0" generator="mirrormanager" type="dynamic" pubdate="Mon, 09 Jan 2017 14:22:50 GMT">/repodata/repomd.xml [Could not resolve host: <metalink xmlns:mm0="http] (http://<metalink xmlns:mm0="http://fedorahosted.org/mirrormanager" xmlns="http://www.metalinker.org/" version="3.0" generator="mirrormanager" type="dynamic" pubdate="Mon, 09 Jan 2017 14:22:50 GMT">/repodata/repomd.xml).

This is probably caused by using an obsolete librepo feature:
http://rpm-software-management.github.io/librepo/lib.html#librepo.LRO_MIRRORLIST

Could you replace it with LRO_MIRRORLISTURL and LRO_METALINKURL?

Comment 1 Daniel Mach 2017-01-09 14:52:52 UTC
Clarification on why to fix this issue:
1) migrate dnf from deprecated to supported librepo features
2) support dynamically generated metalinks (I'm working on something like a mirror manager for composes) that have no 'metalink' in URL

Comment 3 Jaroslav Mracek 2017-02-10 16:00:00 UTC
Bugs fixed in version of dnf-2.0.1-1.


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