Bug 923198 - [rfe] getting the list of mirrors from the metalink, for downloaded and local repo
Summary: [rfe] getting the list of mirrors from the metalink, for downloaded and local...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: librepo
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Mlcoch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-19 12:14 UTC by Ales Kozumplik
Modified: 2014-09-30 23:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-20 19:29:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ales Kozumplik 2013-03-19 12:14:58 UTC
This is not an important thing but DNF needs it for full Yum compatibility, so please consider adding this at some point.

There is no way to obtain the list of all mirrors from a repo obtained via a metalink. This should be possible with both remote and local repositories, in case e.g. the DNF user wants to see where exactly were the metadata downloaded from. 

Yum stores the metalink file with the downloaded repo for this purpose.

Comment 1 Tomas Mlcoch 2013-04-03 10:02:44 UTC
I've add support for store mirrorlist/metalink with downloaded metadata: https://github.com/Tojaj/librepo/commit/98464477201bdeda18df72cd4a5459b0fe9681ec
New option LRI_MIRRORS was added: https://github.com/Tojaj/librepo/commit/056a1152447b42ed03d13e320c21fb0bde7bee0f

Comment 2 Fedora Update System 2013-04-08 14:40:44 UTC
librepo-0.0.2-3.20130408git720d68d.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/librepo-0.0.2-3.20130408git720d68d.fc19

Comment 3 Fedora Update System 2013-04-20 19:29:07 UTC
librepo-0.0.2-3.20130408git720d68d.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


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