Bug 1083185

Summary:	createrepo tracebacks on nonexisting pkglist
Product:	Red Hat Enterprise Linux 6	Reporter:	Karel Srot <ksrot>
Component:	createrepo	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED ERRATA	QA Contact:	Stanislav Zidek <szidek>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.5	CC:	james.antill, jzeleny, szidek, vmukhame
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	createrepo-0.9.9-20.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1083182	Environment:
Last Closed:	2014-05-14 13:41:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Karel Srot 2014-04-01 15:43:20 UTC

$ rpm -q createrepo
createrepo-0.9.9-18.el6.noarch

$ createrepo -i blah .
Traceback (most recent call last):
  File "/usr/share/createrepo/genpkgmetadata.py", line 291, in <module>
    main(sys.argv[1:])
  File "/usr/share/createrepo/genpkgmetadata.py", line 243, in main
    conf = parse_args(args, conf)
  File "/usr/share/createrepo/genpkgmetadata.py", line 198, in parse_args
    pfo = open(conf.pkglist, 'r')
IOError: [Errno 2] No such file or directory: 'blah'

+++ This bug was initially created as a clone of Bug #1083182 +++

Description of problem:

# rpm -q createrepo
createrepo-0.9.9-21.el7.noarch

# createrepo -i blah .
Traceback (most recent call last):
  File "/usr/share/createrepo/genpkgmetadata.py", line 294, in <module>
    main(sys.argv[1:])
  File "/usr/share/createrepo/genpkgmetadata.py", line 246, in main
    conf = parse_args(args, conf)
  File "/usr/share/createrepo/genpkgmetadata.py", line 201, in parse_args
    pfo = open(conf.pkglist, 'r')
IOError: [Errno 2] No such file or directory: 'blah'

Comment 8 errata-xmlrpc 2014-05-14 13:41:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0491.html