Bug 250398 - Can't
Summary: Can't
Keywords:
Status: CLOSED DUPLICATE of bug 246792
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 7
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-01 11:50 UTC by John Pye
Modified: 2014-01-21 22:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-08-01 12:26:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John Pye 2007-08-01 11:50:22 UTC
Description of problem:
When running 'yum clean all', I get the following error, repeatedly:

[john@jdpipe ascend]$ sudo yum clean all
Cleaning up Everything
Error: Error accessing directory //var/cache/yum/fedora-debuginfo/headers,
[Errno 2] No such file or directory: '//var/cache/yum/fedora-debuginfo/headers'
[john@jdpipe ascend]$ sudo yum clean all
Cleaning up Everything
Error: Error accessing directory //var/cache/yum/fedora-debuginfo/headers,
[Errno 2] No such file or directory: '//var/cache/yum/fedora-debuginfo/headers'
[john@jdpipe ascend]$ 


Version-Release number of selected component (if applicable):
yum 3.2.1 on Fedora 7

How reproducible:
Every time (on this system)

Steps to Reproduce:
1.yum clean all
2.yum clean all
  
Actual results:
[john@jdpipe ascend]$ sudo yum clean all
Cleaning up Everything
Error: Error accessing directory //var/cache/yum/fedora-debuginfo/headers,
[Errno 2] No such file or directory: '//var/cache/yum/fedora-debuginfo/headers'
[john@jdpipe ascend]$ sudo yum clean all
Cleaning up Everything
Error: Error accessing directory //var/cache/yum/fedora-debuginfo/headers,
[Errno 2] No such file or directory: '//var/cache/yum/fedora-debuginfo/headers'
[john@jdpipe ascend]$ 


Expected results:
I'd expect it to flag the headers as being clean and move on, or else explain to
me what I need to do to overcome this problem.

Additional info:
Let me know what extra tests I can do to resolve this. Probably this bug arises
as a result of a ctrl-C on yum, but all the same yum should be robust against this.

Cheers
JP

Comment 1 Seth Vidal 2007-08-01 12:26:14 UTC

*** This bug has been marked as a duplicate of 246792 ***


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