Bug 998499 - baseurl metadata downloads broken after 734cf28
Summary: baseurl metadata downloads broken after 734cf28
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: librepo
Version: rawhide
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-08-19 13:00 UTC by Ales Kozumplik
Modified: 2014-09-30 23:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-03 08:43:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ales Kozumplik 2013-08-19 13:00:41 UTC
It seems that commit 734cf28 breaks the following:

#! /usr/bin/python

import librepo
import time

MIRROR="""https://mirrors.fedoraproject.org/metalink?repo=updates-released-f19&arch=x86_64"""
DESTDIR="./"
URL="""http://linuxdownload.adobe.com/linux/x86_64/"""


if __name__ == "__main__":
    h = librepo.Handle()
    h.destdir = DESTDIR
    h.interruptible = True
    h.repotype = librepo.LR_YUMREPO
    h.url = URL
    h.yumdlist = ["primary", "filelists", "prestodelta", "group_gz"]
    # h.local = True
    h.perform(librepo.Result())
    print(h.url)
    print(h.mirrors)

the error is:
librepo.LibrepoException: (19, 'Yum repo downloading error: Downloading error(s): repodata/filelists.xml.gz - Cannot download, all mirrors were already tried without success; repodata/primary.xml.gz - Cannot download, all mirrors were already tried without success', 'Usable URL not found')

Please treat prior to releasing the new librepo version.

Comment 1 Tomas Mlcoch 2013-08-20 08:29:29 UTC
Fixed in HEAD https://github.com/Tojaj/librepo/commit/eef00afa5cc9c7890670c8271d7b890b97550979

The issue was caused by the fact, that "sha" checksum in context of repodata means "sha1" checksum.

Comment 2 Ales Kozumplik 2013-08-20 08:57:58 UTC
This works, thanks.


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