Hide Forgot
Description of problem: This issue was previously reported in Bug 160323 back in 2005. Essentially, if yum is used against a server or a proxy that does not support HTTP/1.1 byte ranges (Accept-Range: none), then it will fail to download the header for the RPM file it is trying to install. Given that the byte range support is optional for the server to support, it seems like yum should support servers that do this. Looking at the yum source, it seems that the only place that really uses the byte range support is getHeader(): yum/yumRepo.py:getHeader() -> yum/yumRepo.py:_getFile(start=start, end=end) which calls into urlgrabber with a start and end range. It seems to me that we could go in and detect if the server supports ranges (some pseudo-code below), and then if it does *not* just download the whole package to look at the pieces we care about. Yes, the performance won't be as good as just fetching the range we care about, but at least it will still work against these oddly (but correctly) configured servers. Version-Release number of selected component (if applicable): yum-3.2.29 (and all earlier versions) Pseudo-code to detect range support: import urllib2 response = urllib2.urlopen(url) info = response.info() response.close() if 'Accept-Ranges' in info and info['Accept-Ranges'] == "none": ranges_supported = False else: ranges_supported = True
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.