Bug 681953 - [abrt] yum-3.2.28-5.fc13: yumRepo.py:1312:_commonRetrieveDataMD:OSError: [Errno 2] No such file or directory
Summary: [abrt] yum-3.2.28-5.fc13: yumRepo.py:1312:_commonRetrieveDataMD:OSError: [Err...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 13
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:de81bfed
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-03 17:13 UTC by Phil V
Modified: 2014-01-21 23:17 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 12:05:14 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (2.93 KB, text/plain)
2011-03-03 17:13 UTC, Phil V
no flags Details

Description Phil V 2011-03-03 17:13:47 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/yum search fs lint
component: yum
executable: /usr/bin/yum
kernel: 2.6.34.7-66.fc13.x86_64
package: yum-3.2.28-5.fc13
reason: yumRepo.py:1312:_commonRetrieveDataMD:OSError: [Errno 2] No such file or directory
release: Fedora release 13 (Goddard)
How to reproduce: not sure, but perhaps there was a network problem.
time: 1299027582
uid: 500

Comment 1 Phil V 2011-03-03 17:13:49 UTC
Created attachment 482120 [details]
File: backtrace

Comment 2 James Antill 2011-03-03 17:58:40 UTC
Where you running multiple yum's as a user?

We've recently fixed that upstream (users now get locking too).

Otherwise, not sure ... but it's pretty much a given that f13 isn't going to get a new yum at this point. Feel free to try the rawhide rebuild yum, if you want (repos.fedorapeople.org).

Comment 3 Phil V 2011-03-03 18:22:55 UTC
(Wow that was quick.)

Yes, I was running multiple 'yum search' and/or 'yum info' simultaneously as a user.

Since it's just information retrieval there's limited need for locking.

Comment 4 Guillaume Lemaître 2011-03-21 20:09:46 UTC
Package: yum-3.2.28-5.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. run 'yum info lua' in a first shell
2. while cache being updated, run 'yum list lua' in another shell
3. second instance of yum runs pretty well until this crash.

Comment 5 Bug Zapper 2011-05-30 11:08:07 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 WONTFIX if it remains open with a Fedora 
'version' of '13'.

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 prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2011-06-27 12:05:14 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 7 Tobias Mueller 2011-10-06 23:00:42 UTC
I just got that on F14, but I can't update the relevant flag.


Note You need to log in before you can comment on or make changes to this bug.