Bug 672850

Since the cache is used for all possible composes, and people often name the repos the same thing in their configs even if they point at different locations, I can't come up with a good way to safely prune that stuff.  If you have suggestions, I'll listening.

Because the files and filenames in the createrepocache directory depend only on the contents of each .rpm and on its n-v-r, and not on any other part of the pathname to the .rpm, then:

1. Prune an entry (unlink it) if the last access to it was more than 10 days ago.

2. Scan the directory (look for entries to prune) whenever the number of entries in the createrepocache directory is more than 2.2 times the number of packages for the current compose.  Composes which use a small number of .rpms will scan "unfairly" often if the same cache also is used by composes of a large number of .rpms, but the cost of scanning is small compared to the cost of using a very large directory with many stale entries.

Also, the manual page should mention the maintenance aspects of createrepocache.

These still sound like risky things, or rather things that are not a normal part of the pungi run state.  I think at most I'd like to suggest a simple command line that somebody could run to prune the cache mentioned in the man page.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.