Syntax changes to haproxy 1.5 render valid 1.4 configurations unusable. This sort of package update should not happen in stable Fedora releases.
Just curious, what exactly makes the configuration unusable? If you want to stay on haproxy 1.4, could you use 'yum downgrade' and yum-versionlock to avoid updates to 1.5?
> Just curious, what exactly makes the configuration unusable? There were two issues we noticed: * Two frontend/listen blocks with the same name but on different interfaces breaks 1.5. This is probably understandable as a bug fix, but it does make configuration stricter. * acl too_many avg_queue(<backend>) gt (and other options) used to have the backend as an optional argument, but it's now required in 1.5, even for listen blockss with a single backend. > If you want to stay on haproxy 1.4, could you use 'yum downgrade' and yum-versionlock to avoid updates to 1.5? We've already updated our configuration to be 1.5-compatible. Even if we didn't, "yum downgrade" would only be a stopgap, as we wouldn't be able to get security updates.
As a side note, 1.5 has been a major release *four years* in the making. Don't you think it would be reasonable to wait for that to go into the next Fedora release and not spring it on current users?