Hide Forgot
Description of problem: I have a number of self-generated yum repos and when i update (re-indexing) them and then try to run "pkcon refresh" i get the following error: The transaction failed: no-more-mirrors-to-try, failure: repodata/filelists.xml.gz from smhi: [Errno 256] No more mirrors to try. (This also happens if i try the same thing in the gui) If i instead run "yum update" or "yum makecache" then packagekit metadata is updated fine via the yum refresh-packagekit plugin. Because of this no updated packages are available via PackageKit until yum has been run before. Version-Release number of selected component (if applicable): PackageKit-0.5.8-13.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Add/remove package in yum repo and re-index 2. Run "pkcon refresh" 3. Actual results: Pkcon throws an error. Expected results: PackageKit should refresh its metadata. Additional info:
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
(In reply to comment #0) > The transaction failed: no-more-mirrors-to-try, failure: > repodata/filelists.xml.gz from smhi: [Errno 256] No more mirrors to try. Can you attach the repomd.xml file for the smhi repo please.
Created attachment 518839 [details] repomd.xml for affected repository
Hmm, that looks fine (old style, but fine nonetheless) -- can you grab me the output of: sudo NETWORK=TRUE /usr/share/PackageKit/helpers/yum/yumBackend.py refresh-cache true Thanks. Richard.
Created attachment 518858 [details] output from yumBackend.py command
Okay, thanks for that. It seems the refresh cache is working correctly, so that narrows it down to one of the refresh cache actions PackageKit is doing. This is a little trickier to debug: First, run "pkmon" Verify that no background tasks are executing, if they are wait patiently. sudo killall packagekitd sudo /usr/sbin/packagekitd --verbose --backend=yum --disable-timer Then, run "pkcon refresh" Then please attach *all* the output from the daemon, including the setup stuff. Thanks. Richard.
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
(In reply to Richard Hughes from comment #7) > Okay, thanks for that. It seems the refresh cache is working correctly, so > that narrows it down to one of the refresh cache actions PackageKit is > doing. This is a little trickier to debug: > > First, run "pkmon" > > Verify that no background tasks are executing, if they are wait patiently. > > sudo killall packagekitd > sudo /usr/sbin/packagekitd --verbose --backend=yum --disable-timer > > Then, run "pkcon refresh" > > Then please attach *all* the output from the daemon, including the setup > stuff. Thanks. > > Richard. I have an outstanding request on this, but cant reproduce it anymore. So as far as i'm concerned, you can close this bug.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/