Bug 205317
| Summary: | yum crashes with "IndexError: list index out of range" | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James Ralston <ralston> | ||||||
| Component: | yum | Assignee: | Jeremy Katz <katzj> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 5 | ||||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2006-10-10 22:35:36 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
I also have a yum bugzilla report open for this bug: https://devel.linux.duke.edu/bugzilla/show_bug.cgi?id=647 (I can't create an external Bugzilla reference, because the Duke/yum bugzilla site doesn't appear to be one of the options.) yes, we know. the same people get them in both places. no need to file it twice. Noted. (Some people, like Mike Harris, always want to move bugs upstream if possible, so I wasn't sure.) What's the output of 'rpm -qa | grep openldap'? Created attachment 136877 [details]
output of "yum -d 10 update seamonkey-chat"
I can't reproduce the openldap problem (as I already upgraded those packages),
but here's another example caused by trying to upgrade seamonkey-chat.
The package breakdown is:
$ rpm -qa --qf '%{name}-%{version}-%{release}.%{arch}.rpm\n' | grep -i
seamonkey | sort
seamonkey-1.0.3-0.el4.1.x86_64.rpm
seamonkey-chat-1.0.3-0.el4.1.x86_64.rpm
seamonkey-devel-1.0.3-0.el4.1.x86_64.rpm
seamonkey-dom-inspector-1.0.3-0.el4.1.x86_64.rpm
seamonkey-js-debugger-1.0.3-0.el4.1.x86_64.rpm
seamonkey-mail-1.0.3-0.el4.1.x86_64.rpm
seamonkey-nspr-1.0.3-0.el4.1.x86_64.rpm
seamonkey-nspr-devel-1.0.3-0.el4.1.x86_64.rpm
seamonkey-nss-1.0.3-0.el4.1.x86_64.rpm
seamonkey-nss-devel-1.0.3-0.el4.1.x86_64.rpm
Can you try with yum 2.9.6 and see if this still happens? It looks to me like things should be fixed there (not that I then see an easy backport, but I want to at least see that things are fixed in the current code) Created attachment 136961 [details]
yum-2.9.6 output of "yum -d 10 update seamonkey-chat"
I rebuilt yum-2.9.6-1.src.rpm from Fedora Development for RHEL4, but it fails
in a different manner (see the attached output).
I'm using createrepo-0.4.4-0.2 on the repo server (also a RHEL4 box). Am I
missing newer bits that yum-2.9.6 needs?
okay - running 2.9.6 on rhel 4's rpm probably won't work. so that won't be a good test. Sigh. I'm going to open a service request for Red Hat to backport the yum infrastructure in RHEL5 to RHEL4, but I'm not going to hold my breath. In the meantime, for sites like us who are going to put yum on RHEL4, what's your recommendation for the best (as in, least likely to die/crash) version of yum to use? you should run yum 2.4.3 on rhel4. 2.6 _might_ work - but I can't guarantee that. Well, if 2.6 worked, then I probably wouldn't have filed this in the first place. ;) But regardless: noted; thanks. |
I'm running yum-2.6.1-0.fc5 on an x86_64 RHEL4 box. (I rebuilt from the SRPM package.) This setup has worked fine for many months, but now yum is crashing on multiple package updates that were part of the U4 release. An example: $ yum update 'openldap*' Loading "installonlyn" plugin Setting up Update Process Setting up repositories rhel [1/2] sei-rhel [2/2] Reading repository metadata in from local files Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Downloading header for openldap-servers to pack into transaction set. openldap-servers-2.2.13-6 100% |=========================| 37 kB 00:00 ---> Package openldap-servers.x86_64 0:2.2.13-6.4E set to be updated ---> Downloading header for openldap-devel to pack into transaction set. openldap-devel-2.2.13-6.4 100% |=========================| 53 kB 00:00 ---> Package openldap-devel.x86_64 0:2.2.13-6.4E set to be updated ---> Package openldap.x86_64 0:2.2.13-6.4E set to be updated ---> Package openldap-clients.x86_64 0:2.2.13-6.4E set to be updated ---> Downloading header for openldap-servers-sql to pack into transaction set. openldap-servers-sql-2.2. 100% |=========================| 31 kB 00:00 ---> Package openldap-servers-sql.x86_64 0:2.2.13-6.4E set to be updated --> Running transaction check --> Processing Dependency: openldap = 2.2.13-4 for package: compat-openldap Traceback (most recent call last): File "/usr/bin/yum", line 29, in ? yummain.main(sys.argv[1:]) File "/usr/share/yum-cli/yummain.py", line 138, in main (result, resultmsgs) = base.buildTransaction() File "__init__.py", line 401, in buildTransaction File "depsolve.py", line 226, in resolveDeps File "depsolve.py", line 357, in _processReq File "depsolve.py", line 418, in _requiringFromInstalled File "__init__.py", line 1479, in getInstalledPackageObject IndexError: list index out of range I didn't see a crash quite like this in the existing bug reports that I skimmed through. Also, this crash only seems to be happening on x86_64. I do *not* see the problem on an i386 box. I tried the latest development version (2.9.5), but it crashes as well. (Again, only on x86_64; i386 is fine.)