[FC3] Hi
As many ppl have read or expirenced, yum updates are suddenly turned into a nightmare.
For 3 days now i cant update the system (and cPanel uses it too and hangs also with updates). ################### # yum clean all (i hated this because it deleted 200+ packages that i wanted to save for future boxes to update with to save bandwidth) Cleaning up Everything 0 headers removed 0 packages removed 0 metadata files removed 0 cache files removed # yum update Setting up Update Process Setting up Repos core 100% |=========================| 1.1 kB 00:00 dries 100% |=========================| 0 B 00:00 //var/cache/yum/dries/repomd.xml:1: parser error : Document is empty
^ //var/cache/yum/dries/repomd.xml:1: parser error : Start tag expected, '<' not found
^ Cannot open/read repomd.xml file for repository: dries Error importing repomd.xml from dries: Error: could not parse file //var/cache/yum/dries/repomd.xml ####### At the moment is stalls on "dries" but also happens on the others. This are the repo's i use: ######## -rw-r--r-- 1 root root 129 Sep 21 19:04 dag.repo -rw-r--r-- 1 root root 163 Sep 21 19:04 dries.repo -rw-r--r-- 1 root root 255 Sep 21 19:04 extras.repo -rw-r--r-- 1 root root 233 Sep 21 19:04 fedora-devel.repo -rw-r--r-- 1 root root 244 Sep 21 19:04 fedora.repo -rw-r--r-- 1 root root 280 Sep 21 19:04 fedora-updates.repo -rw-r--r-- 1 root root 282 Sep 21 19:04 fedora-updates-testing.repo -rw-r--r-- 1 root root 477 Sep 21 19:04 freshrpms.repo ######### and disabled the -testing -devel repo's. I was in need to install a package but i went to the orginal site and downloaded a source and compiled it. I realy want to see this fixed. Because i am not the only user and i was not the first reporter of this. I hope the FC team / yum team will take a close look on this.
Danny Terweij - Net Tuning | Net wrote:
[FC3] Hi
As many ppl have read or expirenced, yum updates are suddenly turned into a nightmare.
For 3 days now i cant update the system (and cPanel uses it too and hangs also with updates). ################### # yum clean all (i hated this because it deleted 200+ packages that i wanted to save for future boxes to update with to save bandwidth) Cleaning up Everything 0 headers removed 0 packages removed 0 metadata files removed 0 cache files removed # yum update Setting up Update Process Setting up Repos core 100% |=========================| 1.1 kB 00:00 dries 100% |=========================| 0 B 00:00 //var/cache/yum/dries/repomd.xml:1: parser error : Document is empty
^ //var/cache/yum/dries/repomd.xml:1: parser error : Start tag expected, '<' not found
^ Cannot open/read repomd.xml file for repository: dries Error importing repomd.xml from dries: Error: could not parse file //var/cache/yum/dries/repomd.xml ####### At the moment is stalls on "dries" but also happens on the others. This are the repo's i use: ######## -rw-r--r-- 1 root root 129 Sep 21 19:04 dag.repo -rw-r--r-- 1 root root 163 Sep 21 19:04 dries.repo -rw-r--r-- 1 root root 255 Sep 21 19:04 extras.repo -rw-r--r-- 1 root root 233 Sep 21 19:04 fedora-devel.repo -rw-r--r-- 1 root root 244 Sep 21 19:04 fedora.repo -rw-r--r-- 1 root root 280 Sep 21 19:04 fedora-updates.repo -rw-r--r-- 1 root root 282 Sep 21 19:04 fedora-updates-testing.repo -rw-r--r-- 1 root root 477 Sep 21 19:04 freshrpms.repo ######### and disabled the -testing -devel repo's. I was in need to install a package but i went to the orginal site and downloaded a source and compiled it. I realy want to see this fixed. Because i am not the only user and i was not the first reporter of this. I hope the FC team / yum team will take a close look on this.
If you are using third party repositories that fail FC team cant do anything about that. If mirrors are failing yum team cant do anything either. If you find bugs report them in bugzilla
regards Rahul
From: "Rahul Sundaram" sundaram@redhat.com
If you are using third party repositories that fail FC team cant do anything about that. If mirrors are failing yum team cant do anything either. If you find bugs report them in bugzilla
Okay, no support i guess.
Tell me,
http://apt.sw.be/dries/fedora/linux/3/i386/dries/RPMS/
is there missing something that yum is not working on"dries" ? And if yum fails on "core" or "updates" is it missing also something at the mirror's ?
Danny.
Danny Terweij - Net Tuning | Net wrote:
From: "Rahul Sundaram" sundaram@redhat.com
If you are using third party repositories that fail FC team cant do anything about that. If mirrors are failing yum team cant do anything either. If you find bugs report them in bugzilla
Okay, no support i guess.
Tell me,
http://apt.sw.be/dries/fedora/linux/3/i386/dries/RPMS/
is there missing something that yum is not working on"dries" ? And if yum fails on "core" or "updates" is it missing also something at the mirror's ?
Danny.
Yum usually bombs out for any problem with repository conflicts. Try disabling dries, then run yum to update the core and other co-operating repositories. For the dries repository, you could file bug reports at dries or add exclude="packagename" to the dries repo file.
The archives should be more specific on how to exclude packages for individual repositories and other programs such as "smart" which are intended to handle repo conflicts.
Jim
From: "Jim Cornette" fc-cornette@insight.rr.com
is there missing something that yum is not working on"dries" ? And if yum fails on "core" or "updates" is it missing also something at
the
mirror's ?
Yum usually bombs out for any problem with repository conflicts. Try disabling dries, then run yum to update the core and other co-operating repositories. For the dries repository, you could file bug reports at dries or add exclude="packagename" to the dries repo file.
Ok and it always worked :) Let see i disabled "dries" :
##### #yum update Setting up Update Process Setting up Repos core 100% |=========================| 1.1 kB 00:00 dag 100% |=========================| 1.1 kB 00:00 freshrpms 100% |=========================| 951 B 00:00 extras 100% |=========================| 951 B 00:00 updates 100% |=========================| 0 B 00:00 //var/cache/yum/updates/repomd.xml:1: parser error : Document is empty
^ //var/cache/yum/updates/repomd.xml:1: parser error : Start tag expected, '<' not found
^ Cannot open/read repomd.xml file for repository: updates Error importing repomd.xml from updates: Error: could not parse file //var/cache/yum/updates/repomd.xml ####
Now what :)
Danny
Danny, I don't think it's your fault. I am also getting the exact same error, for a configuration that always worked. I haven't done a 'yum update' for a couple of weeks now. Maybe the latest update to yum itself broke it.
As of now, I am waiting for a solution to pop up somewhere. -nat
Hi,
Danny, I don't think it's your fault. I am also getting the exact same error, for a configuration that always
worked.
I haven't done a 'yum update' for a couple of weeks now. Maybe the latest update to yum itself broke it.
What i do, it never gets a update indeed. By removing a failed repo then another one gets in error. I tried 1 by 1 to see where it was ending... it ends in "0" repo's enabled. I only can say it must be fixed somewhere else but not at user level.
It also sounds that if a new yum package will be released, it must be downloaded bij hand and installed with rpm i guess...
As of now, I am waiting for a solution to pop up somewhere.
Me to, and for security updates i do that manual in meantime.
Danny
-
Danny.Terweij -
Jim Cornette -
Nat Gross -
Rahul Sundaram