On Mon, May 9, 2016 at 9:43 AM, Kevin Fenzi kevin@scrye.com wrote:
On Mon, 9 May 2016 13:44:41 +0100 Peter Robinson pbrobinson@gmail.com wrote:
Sorry for delay for writing this. We wanted to provide latest DNF stack in EPEL7 which means we also need newer components like libsolv, hawkey, librepo, etc.
Some of those are in RHEL7.2 and unfortunately it's not that easy to get them updated:
- librepo
- libsolv
- hawkey
Probably some more, didn't remember. There are no ABI breakage with those updates and actually only PackageKit (via libhif) depends on it.
So I would like to ask EPSCo to provide exception to override those packages in EPEL7.
- We have never given an exception before that I know of. [I think
openstack asked for an exception but there was too much customer problems with it to make it possible. ] 2. You could have broken hundreds of thousands of computers (mainly because they have yum install in their cron jobs it looks like). Pushing and then asking for permission is not acceptable. It usually leads to the package set being removed and blacklisted from EPEL. 3. I understand the importance of this package set, and will try to work with you on this, but I am going to need a day to not be pissed.
Personally I think the proper place to do this is copr. EPEL really isn't the place to do it especially if it's "too hard" to work with the internal teams to get it updated in the appropriate EL release.
Well, that or the traditional way: create parallel installable forward compat packages and have the dnf in EPEL use them instead of the RHEL versions, ie, libsolv0.6 etc.
Has that path been explored?
They would still conflict on files, since libsolv uses the same soversion and have the same binary compatibility. I suppose if the build was patched to use a different library name, it could work.