Bug 877301 - createrepo -C does nothing on empty repo
createrepo -C does nothing on empty repo
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: createrepo (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: packaging-team-maint
Karel Srot
Depends On:
  Show dependency treegraph
Reported: 2012-11-16 03:12 EST by Marko Myllynen
Modified: 2013-05-30 03:44 EDT (History)
2 users (show)

See Also:
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:
Last Closed: 2013-05-30 03:44:27 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marko Myllynen 2012-11-16 03:12:10 EST
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
Comment 2 RHEL Product and Program Management 2012-12-14 03:11:58 EST
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 16:19:16 EDT
commit f0020c470935cbb98ed4c53ef8ae24952e799a01
Author: Zdeněk Pavlas <zpavlas@redhat.com>
Date:   Fri Dec 14 11:20:21 2012 +0100
Comment 12 errata-xmlrpc 2013-05-30 03:44:27 EDT
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.


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