Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
That sent before I entered the description. Sorry. I'm getting this since last night from cron: /etc/cron.hourly/0yum-hourly.cron: Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/20/updates/gen/updateinfo.xml', mode 'rt' at 0x106cc00> Removing the offending file doesn't help. I have default config settings for yum-cron config files. yum-cron-3.4.3-152.fc20.noarch yum-cron-daily-3.4.3-152.fc20.noarch
I can attach the offending file, but it's big-ish (20M). Let me know.
Still happening. Here's more info on the file: env TZ=UTC ls -al /var/cache/yum/x86_64/20/updates/gen/updateinfo.xml -rw-r--r--. 1 root root 20436507 May 8 06:10 /var/cache/yum/x86_64/20/updates/gen/updateinfo.xml
Created attachment 1023474 [details] problematic updateinfo.xml, gzipped Attached is the updateinfo.xml file, gzipped.
This issue should be resolved with the latest repodata that synced out this morning. Can someone please confirm? Thanks
Not resolved on Fedora 20, as of this writing. 'yum clean all' followed by 'yum update' results in some of the usual yum logging noise, ulitmately interrupted by the error Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/20/updates/gen/updateinfo.xml', mode 'rt' at 0x1231d20> A second 'yum update' (not preceded by the 'yum clean all') yields the same error immediately, without the preceding logging noise.
Works for me now - at least for the mirror I was pointed to (http://linux.mirrors.es.net). For my education and being better informed, what was the source of the issue & ultimate fix. Quick pointer somewhere so I can follow the bread crumbs is fine.
Indeed, the error goes away if I modify the yum configuration for the fedora-updates repo, uncommenting the 'baseurl:' line and commenting out the 'metalink:' line. So apparently the corrected metadata has not yet made it to the mirrors, or at least to the mirrors that are tried by default by my machine.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.