Red Hat Bugzilla – Bug 977299
RFE - update root in epel6 to something newer.
Last modified: 2013-07-13 16:15:41 EDT
Hi, I have various requests for the root version within EPEL6 in particular to move to something newer than the current root-5.28.00h-3.el6. Can this happen? Many Thanks Steve.
I have had this request a few times before. There is a stability criteria in EPEL that updates should not cause backward incompatibilities. Updating to a new base release of root will cause the soname of all root libraries to change, e.g. libCore.so.5.28 → libCore.so.5.34. So things that users have compiled against the existing version would need to be recompiled. This is the reason I have so far not updated root to new base releases in stable distributions. This stability criteria can be somewhat relaxed if the package in question is a leaf package. For the distribution (Fedora/EPEL) root is a leaf package since it does not have any packages depending on it. So from this point of view an update could be considered despite the introduced backward incompatibility. However, the issue of user code having been compiled against the root libraries that will break if root is updated still exists. So there is a conflict between the desire to have the latest version in EPEL and having a stable binary version. It is not possible to have both. As a maintainer I have to choose one of the two. If the users of the root packages in EPEL agree that newer versions are more important than version stability I can change the maintenance strategy to accommodate that. But it would need to be a general opinion shared by most of the users, not the opinion of a few. I don't know how to gauge the opinion of the users in a reliable way on this issue. Obviously, those that want the newest version approach are heard more loudly since those are the ones that want a change. The users who value the stable version approach are currently not heard since it is not clear to them that they should voice their opinion. I am not dead set against updating, but it needs to be done after some reflection of the consequences.
root-5.34.09-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/root-5.34.09-1.el5
root-5.34.09-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/root-5.34.09-1.fc19
root-5.34.09-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/root-5.34.09-1.fc18
root-5.34.09-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/root-5.34.09-1.el6
Package root-5.34.09-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing root-5.34.09-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-10652/root-5.34.09-1.el6 then log in and leave karma (feedback).
root-5.34.09-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
root-5.34.09-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
root-5.34.09-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
root-5.34.09-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.