On Thu, Jul 25, 2019 at 9:04 AM Matthew Miller mattdm@mattdm.org wrote:
On Wed, Jul 24, 2019 at 09:43:20PM +0100, Phil Perry wrote:
The issue is .. they change the versions out and you then lose that package. next build it fails with the new one .. what do you do? The old package is no longer available anywhere.
One thing that can help here is to not treat the EPEL maintainers as an opaque "they". It's actually people you can talk directly to, and who should have your concerns as a consumer in mind. You could even become a comaintainer of the package.
The issue here is not related to maintainers of a given package, but rather one of EPEL policy whereby only the latest release of each package is available in the repository. As Johnny correctly
I disagree! The quote is "they change the versions out". If you're not ready for the version to be changed, coordinate with the maintainer. As I mentioned elsewhere, I hope that in the future with EPEL 8 with modularity enabled, you'd even have the option of having the old version available in parallel.
Keeping old versions around is more of a Bodhi problem. If it had an option to keep old versions when it recomposed the EPEL repos, then it'd be fine.