Bug 639282 - [abrt] yum-utils-1.1.28-1.fc13: yumRepo.py:535:_dirSetupMkdir_p:RepoError: Error making cache directory: /var/tmp/yum-stephent-xWCO0K/x86_64/14xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Summary: [abrt] yum-utils-1.1.28-1.fc13: yumRepo.py:535:_dirSetupMkdir_p:RepoError: Er...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:efeec8a5
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-01 11:24 UTC by Steve Tyler
Modified: 2014-01-21 23:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-01 13:51:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (5.46 KB, text/plain)
2010-10-01 11:24 UTC, Steve Tyler
no flags Details

Description Steve Tyler 2010-10-01 11:24:33 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python -tt /usr/bin/repoquery --disablerepo=rpm* glibc --releasever=14xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
component: yum-utils
executable: /usr/bin/repoquery
kernel: 2.6.34.7-56.fc13.x86_64
package: yum-utils-1.1.28-1.fc13
reason: yumRepo.py:535:_dirSetupMkdir_p:RepoError: Error making cache directory: /var/tmp/yum-stephent-xWCO0K/x86_64/14xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
release: Fedora release 13 (Goddard)
time: 1285931752
uid: 500

How to reproduce
-----
1. [stephent@walnut ~]$ repoquery --disablerepo='rpm*' glibc --releasever=14xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Comment 1 Steve Tyler 2010-10-01 11:24:35 UTC
Created attachment 450983 [details]
File: backtrace

Comment 2 Steve Tyler 2010-10-01 11:33:07 UTC
The releaserver passed to repoquery has 479 characters.

$ echo -n 14xx... | wc -c
479

Comment 3 Steve Tyler 2010-10-01 11:46:32 UTC
[stephent@walnut ~]$ rpm -qa 'yum*' | sort
yum-3.2.28-4.fc13.noarch
yum-metadata-parser-1.1.4-1.fc13.x86_64
yum-presto-0.6.2-1.fc13.noarch
yum-utils-1.1.28-1.fc13.noarch

Comment 4 seth vidal 2010-10-01 12:57:35 UTC
yah, umm, Why did you pass in a releasever with 479 characters?

Comment 5 Steve Tyler 2010-10-01 13:20:13 UTC
(In reply to comment #4)
> yah, umm, Why did you pass in a releasever with 479 characters?

<g> It was "random", but I counted them after my experience with
Bug 566305 - "file" may trim too much of command line from core file
in which there was a sensitivity to the length of the command line.

Comment 6 seth vidal 2010-10-01 13:51:02 UTC
Well the yum-utils in upstream already catches the exception and outputs a tidy (though just as informative) error.

Comment 7 Steve Tyler 2010-10-01 16:33:39 UTC
(In reply to comment #6)
> Well the yum-utils in upstream already catches the exception and outputs a tidy
> (though just as informative) error.

OK, thanks. At least abrt won't be phoning home ... :-)


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