Re: Install SVN 1.6.11 on RHEL 7.7
On Tue, Dec 7, 2021 at 5:16 AM Stefan Sperling wrote: > > On Tue, Dec 07, 2021 at 03:19:45PM +0530, Abhishek Kumar wrote: > > Dear Team, > > There is a Planned Linux OS Upgradation of Server from existing version RHEL > > 6 to RHEL 7.7 where SVN Server(SVN V1.6.11) setup is done. > > > > Kindly provide the installation steps and compatibility for the same. > > > > *Existing* > > > > SVN Version Linux Version > > V1.6.11 RHEL 6.10 > > *Planned* > > SVN Version Linux Version > > V1.6.11 RHEL 7.7 > > Subversion 1.6.11 was released in April 2010 (almost 12 years ago!) > and is affected by numerous security issues listed here: > https://subversion.apache.org/security/ > > You should consider upgrading SVN to a supported version, instead > of upgrading only the RHEL system itself. > > For latest SVN source releases, see: > https://subversion.apache.org/download.cgi#source-releases > > For SVN binary packages specific to RHEL, see: > https://subversion.apache.org/packages.html#redhat > > > Looking forward to a quick reply and prompt support. > > This mailing list is a volunteer forum. As such, no specific guarantees > can be made regarding support requests. > > Regards, > Stefan Some years back, I used to publish updated releases of Subversion for the repoforge repository. I stepped away from that hobby when the repoforge admin decided to stop adding new packages. While RHEL 7 has subversion 1.6 built-in, my more recent RPM building tools are available at https://github.com/nkadel/subversion-1.11.x-srpm. Wandisco used to publish up-to-date releases. but with the loss of popularity of Subversion, people have not spent much energy to backport current releases to older operating systems.
Re: Install SVN 1.6.11 on RHEL 7.7
Collabnet has the most recent releases of subversion, at https://www.collab.net/downloads/subversion#show-Linux .
Re: Changed file permissions after committing user-crontabs
Guten Tag Daniel Sahlberg, am Mittwoch, 24. November 2021 um 22:22 schrieben Sie: > If you don't see it on newer Ubuntus - do you have another umask on these? Some have 0002, others 0022 and I found one with 0007. Though, all individual cron files on all systems I looked at have the same restricted permissions rw for users only. And I'm somewhat sure to have not changed umasks manually on all of those systems and/or changed permissions of cron files manually after committing. Mit freundlichen Grüßen Thorsten Schöning -- AM-SoFT IT-Service - Bitstore Hameln GmbH Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK E-Mail: thorsten.schoen...@am-soft.de Web:http://www.AM-SoFT.de/ Tel: 05151- 9468- 0 Tel: 05151- 9468-55 Fax: 05151- 9468-88 Mobil: 0178-8 9468-04 AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 221853 - Geschäftsführer: Janine Galonska
svn::auto-props and svn:needs-lock
Hello, I'm having trouble with these features. I have a folder on which I have set svn:auto-props to *=svn:needs-lock=*. I have another folder within this folder for which I would like anything inside to not require locks. It seems, I have no way of removing auto setting the needs lock property on newly added files? This makes sense I guess, considering svn:needs-lock doesn't require a value, just needs to be set. Feels like the needs-lock requiring either 0 or 1 as a value would make this customizable? Am I correct in my assumption? Or is there a way of handling this specific scenario gracefully? Best, Sebastian
