Bug 1218353 - [metadata] Failed to synchronize cache for repo
Summary: [metadata] Failed to synchronize cache for repo
Keywords:
Status: CLOSED DUPLICATE of bug 1219283
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-04 16:54 UTC by diegofernandez
Modified: 2015-05-28 14:35 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-05-28 14:35:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
/var/cache/dnf archive (1.75 MB, application/x-tar)
2015-05-04 16:54 UTC, diegofernandez
no flags Details

Description diegofernandez 2015-05-04 16:54:38 UTC
Created attachment 1021810 [details]
/var/cache/dnf archive

Description of problem: I'm trying to use DNF, but any command I try result in the following error:
"Failed to synchronize cache for repo 'Dropbox' from 'http://linux.dropbox.com/fedora/22/': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried, disabling.
Error: Failed to synchronize cache for repo 'fedora' from 'https://mirrors.fedoraproject.org/metalink?repo=fedora-22&arch=x86_64': Yum repo downloading error: Downloading error(s): repodata/025694bc7164bebf478246c5e2c80f9c3ea6891b12eafdb3864efe507cf3d600-filelists.xml.gz - Cannot download, all mirrors were already tried without success; repodata/6f30747a59d05cd7b75f31e0e3fc2a88f16a2fdd8fe84e09106edb9da0ed7b59-primary.xml.gz - Cannot download, all mirrors were already tried without success"


Version-Release number of selected component (if applicable): 0.6.5


How reproducible: Any command as: dnf update, dnf install, dnf upgrade.

Additional info: When I installed Fedora 22 it was working fine. After reboot it gives me that error.

Comment 1 Marcin Juszkiewicz 2015-05-28 14:35:18 UTC

*** This bug has been marked as a duplicate of bug 1219283 ***


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