On 01/29/2018 07:29 PM, Stephen John Smoogen wrote:

On 29 January 2018 at 05:53, Avi Kivity <avi@scylladb.com> wrote:
Recently, I ran into breakage due to yaml-cpp-0.5.3 breaking yaml-cpp-0.5.1's ABI. The breakage was due to upstream not maintaining ABI compatibility (something that's very hard with some C++ libraries), but recovering from it was pretty hard, due to EPEL not keeping old packages around.

If old packages were kept around, we could just tell people to run "yum downgrade yaml-cpp-0.5.1" and then pin that package, until the ABI issue was resolved. As it was, we had to refer them to the package from koji, which means that new installs become harder.

Can we change the policy to keep old packages in the repository, to prevent this in the future?

This requires a bit of work due to the way that EPEL is made into a repository. It would require changing the layout quite a bit for what seems a 'simple' change. It is hopefully going to be on the books for this year though.

Thanks, it will make recovering from upgrade disasters a lot easier.