Could Not Parse Metalink Error Was No Repomd File
Contents |
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > The Dungeon > Archived (Click Header To See Sub-Forums) > F16 Development [SOLVED] yum update error FedoraForum
Error: File /var/cache/yum/i386/6/epel/metalink.xml Does Not Exist
Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=i386 error was Today's Posts Search F16 Development This section archived once F16 reached final release. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums file /var/cache/yum/i386/7/epel/metalink.xml does not exist Show Threads Show Posts Tag Search Advanced Search Go to Page... Page 1 of 2 1 2 > Thread Tools Search this Thread Display Modes #1 23rd May 2011, 06:19 AM raviainani Offline Registered
File /var/cache/yum/x86_64/7/epel/metalink.xml Does Not Exist
User Join Date: May 2011 Posts: 19 yum update error hi all, hope this is the right section for my problem if not please excuse me for this.... i am facing yum update error for past few days and i did a little googling but couldn't find the best way to do it. livna repo was giving me error firat so i disabled it by editing the .repo file but now when i do yum update following is
Cannot Retrieve Metalink For Repository Epel X86_64 Centos 7
the output [root@ravi ravi]# yum update Loaded plugins: langpacks, presto, refresh-packagekit Could not retrieve mirrorlist http://mirrors.rpmfusion.org/mirrorl...a-16&arch=i386 error was 14: curl#6 - "Couldn't resolve host" updates/metalink | 19 kB 00:01 Could not parse metalink https://mirrors.fedoraproject.org/me...-f16&arch=i386 error was No repomd file Error: Cannot retrieve repository metadata (repomd.xml) for repository: rpmfusion-free. Please verify its path and try again NOTE: - i have even tried yum clean all and then yum update / yum update --disablerepo=livna but till now no luck.... i am running FEDORA 15 thanks in advance ravi raviainani View Public Profile Find all posts by raviainani #2 23rd May 2011, 06:39 AM leigh123linux Guest Posts: n/a Re: yum update error Moved to Rawhide Quote: i am running FEDORA 15 You have F16 rawhide now. Code: Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=updates-released-f16&arch=i386 error was There aren't any F16 repo's only development aka rawhide. #3 23rd May 2011, 09:19 AM JohnVV Offline Registered User Join Date: Aug 2005 Location: Ann Arbor Age: 49 Posts: 3,953 Re: yum update error Quote: --disablerepo=livna seeing as that repo no longer exists WHY is it installed it is dead . Rawhide is THE NEXT version - right now fedora 16 and seeing as there are NO FEDORA 16 rpm's .... do not use "rawhide" turn it OFF then remove the old and dead livna.repo make sure that fedora is ON and updates is ON and updates-test
refresh-packagekitadobe-linux-x86_64 | 951 B 00:00:00fedora/19/x86_64/metalink cannot retrieve metalink for repository: epel/x86_64. please verify its path and try again | 25 kB
No Package Epel Release Available
00:00:00Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-19&arch=x86_64 error wasNo repomd fileError: File /var/cache/yum/x86_64/19/fedora/metalink.xml does not exist As seen from the epel centos 7 output, the problem is with some Fedora mirror. After googling for a solution and trying different fixes, none of which worked for me, I finally edited /etc/yum.repos.d/fedora.repo, commented out http://forums.fedoraforum.org/showthread.php?t=263369 the line mirrorlist and uncommented baseurl line. After that, everything worked. To conclude this post, the problem is with some mirror picked by yum. Posted by Stjepan Groš (sgros) at 18:49 Labels: english, fedora, fedora19, repository, sysadm, yum Location: Ivanja Reka, Croatia No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) About Me http://sgros.blogspot.com/2013/07/yum-error.html Stjepan Groš (sgros) scientist, consultant, security specialist, networking guy, system administrator, philosopher ;) View my complete profile Blog Archive ► 2016 (10) ► September (1) ► July (1) ► June (1) ► March (2) ► February (2) ► January (3) ► 2015 (13) ► December (4) ► October (2) ► August (1) ► June (1) ► April (1) ► March (1) ► February (2) ► January (1) ► 2014 (19) ► December (3) ► November (2) ► September (1) ► August (1) ► June (2) ► May (1) ► March (4) ► February (4) ► January (1) ▼ 2013 (42) ► December (6) ► November (5) ► October (1) ► September (2) ► August (4) ▼ July (3) yum error Replacing self-signed expired certificates using O... Upgrading to Fedora 19 ► June (2) ► May (1) ► March (6) ► February (2) ► January (10) ► 2012 (124) ► December (8) ► November (11) ► October (13) ► September (9) ► August (11) ► July (17) ► June (13) ► April (1) ► March (4)
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How do I resolve this yum problem: “no repomd file” up vote 1 down vote favorite I am using Fedora 20 and trying to install several software packages. e.g. sudo yum install python-matplotlib And get this response for every package I try: Loaded plugins: langpacks, refresh-packagekit adobe-linux-i386 | 951 B 00:00 epel/i386/metalink | 38 kB 00:00 Could not parse metalink https://mirrors.fedoraproject.org/metalink repo=epel-7&arch=i386 error was No repomd file One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable