Bug 877301

Summary:	createrepo -C does nothing on empty repo
Product:	Red Hat Enterprise Linux 6	Reporter:	Marko Myllynen <myllynen>
Component:	createrepo	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED ERRATA	QA Contact:	Karel Srot <ksrot>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	james.antill, jzeleny
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	createrepo-0.9.9-18.el6	Doc Type:	Bug Fix
Doc Text:	Cause: Timestamp check didn't pass if the file didn't exist. Consequence: An empty repo. was incorrectly flagged as up to date. Fix: Treat missing file as a failure, and not a pass. Result: Repo. is created when --checkts used on empty repo.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-30 07:44:27 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 Marko Myllynen 2012-11-16 08:12:10 UTC

Description of problem:
There's one corner case issue remaining with -C:

$ mkdir test
$ cd test
$ mkdir packages
$ createrepo -v -C .
repo is up to date
$ createrepo .

Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Sqlite DBs complete
$ rpm -V createrepo
$ rpm -q createrepo
createrepo-0.9.9-15.el6.noarch
$

Comment 2 RHEL Program Management 2012-12-14 08:11:58 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 James Antill 2013-04-16 20:19:16 UTC

commit f0020c470935cbb98ed4c53ef8ae24952e799a01
Author: Zdeněk Pavlas <zpavlas>
Date:   Fri Dec 14 11:20:21 2012 +0100

Comment 12 errata-xmlrpc 2013-05-30 07:44:27 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-2013-0879.html