On Mon, Nov 2, 2015 at 8:59 AM, Junek Leoš <ju...@oksystem.cz> wrote: > Hello, > > > > I am newbie in subversion administration or development issues. So I am > sorry if my question looks stupid. > > > > Why Subversion 1.8 RPMs were not included to RHEL 7 / Centos 7 / Oracle > Linux 7 (native) repositories, though it was released on 18th June 2013 and > RHEL 7 GA was introduced on June 2014? Even now, 28 months after Subversion > 1.8 release date I cannot find it in Centos repositories. > > e.g. http://merlin.fit.vutbr.cz/mirrors/centos/7.1.1503/os/x86_64/Packages/
If you'd like my RHEL 7 RPM building tooks they're up at https://github.com/nkadel/subversion-1.8.x-srpm. Red Hat doesn't publish major release updates for a stable OS because RHEL is a "server" operating system, long-term stable, and with pretty much guaranteed compatibility and stability with all previous software versions originall realeased with the OS. In particular, if you update to Subversion 1.8 on one system and have an NFS shared working copy on a non-updated system, or simply rsync hte copy to a non-updated system, you cannot use the new working copy on a host without updating Subversion. And small differences in formatting output, or in features like handling of submodules, can *break* your stable workflow pretty badly. The classic example is https://xkcd.com/1172/, which I occasionally cite at work. This reluctance to update happened with RHEL 5, which had Subversion 1.4. Red Hat did eventually upgrade to 1.6. I I think the big feature that got them to switch was the switch *away* from automatically and silently storing passwords in cleartext in $HOME/.subversion/. But it took years! Rpmforge used to publish just such updates, I used to submit them there, but my pull updates for Rpmforge have been languishing for some time, basically since Dag Weiers stepped back from maintaining Rpmforge. > Why is it available only via 3rdparty repositories, e.g. via WanDisco? Who > decided not to create RPMs of Subversion 1.8 for RHEL 7 based distributions. Red Hat. If you have a subscription, submit a feature request! EPEL won't publish them, because they refuse to replace existing RHEL components. Their approach is understandable, thought with the continuing lack of RPMforge updates it leaves people like you out in the cold. > I would like to install Subversion 1.8 from native distribution repository > and wonder why it is not available… My RPM building tools are published. I don't personally have a web service I can rely on sufficiently well to publish reliable, GPG signed RPM's and have high confidence that someone can't maliciously replace the repository, including a fake GPG key. Who checks the signature chain on website published GPG keys?
