Re: [ANNOUNCE] Apache Subversion 1.14.3 released
On Tue, Jan 16, 2024 at 4:08 PM Daniel Sahlberg wrote: > > Den mån 15 jan. 2024 kl 20:44 skrev Dunnill, Robert : >> >> Is a document available on how to update Apache under Subversion Edge? > > > I think that Subversion Edge is no longer supported (we removed the download > links a while back) so you should probably update to another Subversion > server solution or even switching to a hosting provider. But it is probably > better to ask this question directly to CollabNet (now digital.ai), at least > if you have a commercial license. +1, it has not been maintained since I parted ways with CollabNet 3 years ago and even then it had probably been 5+ years since I had an engineering team working on it. You also cannot simply replace the binaries with someone else's as it required them to be built a specific way so we could support so many different OS as well as the Python bindings it included for ViewVC. I do not think the version of SVN is really that critical to upgrade as most improvements happen on the client, but given that the versions of Apache httpd and OpenSSL are likely ancient and full of CVE's you should probably try to move to something else. Mark
Re: [External] : Re: Can't connect to github anymore
On 16 Jan 2024, at 15:44, Daniel Sahlberg wrote: > TortoiseSVN, the Windows client, has some scripts that actually allow > "diffing" of Word and Excel documents. So does Araxis Merge (not affiliated, just a happy customer). Sean
Re: [ANNOUNCE] Apache Subversion 1.14.3 released
Den mån 15 jan. 2024 kl 20:44 skrev Dunnill, Robert : > Is a document available on how to update Apache under Subversion Edge? > I think that Subversion Edge is no longer supported (we removed the download links a while back) so you should probably update to another Subversion server solution or even switching to a hosting provider. But it is probably better to ask this question directly to CollabNet (now digital.ai), at least if you have a commercial license. Kind regards, Daniel > > RD > > -Original Message- > From: hartmannat...@apache.org > Sent: Thursday, December 28, 2023 9:00 PM > To: annou...@subversion.apache.org; users@subversion.apache.org; > d...@subversion.apache.org > Subject: [ANNOUNCE] Apache Subversion 1.14.3 released > > [You don't often get email from hartmannat...@apache.org. Learn why this > is important at https://aka.ms/LearnAboutSenderIdentification ] > > EXTERNAL EMAIL > > I'm happy to announce the release of Apache Subversion 1.14.3. > Please choose the mirror closest to you by visiting: > > https://subversion.apache.org/download.cgi#recommended-release > > This is a stable bugfix release of the Apache Subversion open source > version control system. > > SHA-512 checksums are available at: > > > https://www.apache.org/dist/subversion/subversion-1.14.3.tar.bz2.sha512 > https://www.apache.org/dist/subversion/subversion-1.14.3.tar.gz.sha512 > https://www.apache.org/dist/subversion/subversion-1.14.3.zip.sha512 > > PGP Signatures are available at: > > https://www.apache.org/dist/subversion/subversion-1.14.3.tar.bz2.asc > https://www.apache.org/dist/subversion/subversion-1.14.3.tar.gz.asc > https://www.apache.org/dist/subversion/subversion-1.14.3.zip.asc > > For this release, the following people have provided PGP signatures: > >Nathan Hartman (CODE SIGNING KEY) [rsa4096/583F00ADF981C39F] with > fingerprint: > 3F8E 467C B336 6E30 13E1 120D 583F 00AD F981 C39F >Stefan Sperling [dsa1024/E5D30273F59D25F0] with fingerprint: > B1CF 1060 A1E9 34D1 9E86 D6D6 E5D3 0273 F59D 25F0 >Daniel Sahlberg [rsa3072/28DB47329CFFDC63] with fingerprint: > 4FFC B55C 0D0D 9343 CFB4 611F 28DB 4732 9CFF DC63 >Evgeny Kotkov [rsa4096/B64FFF1209F9FA74] with fingerprint: > E7B2 A7F4 EC28 BE9F F8B3 8BA4 B64F FF12 09F9 FA74 >Johan Corveleyn [rsa4096/B59CE6D6010C8AAD] with fingerprint: > 8AA2 C10E EAAD 44F9 6972 7AEA B59C E6D6 010C 8AAD > > These public keys are available at: > > https://www.apache.org/dist/subversion/subversion-1.14.3.KEYS > > Release notes for the 1.14.x release series may be found at: > > https://subversion.apache.org/docs/release-notes/1.14.html > > You can find the list of changes between 1.14.3 and earlier versions at: > > https://svn.apache.org/repos/asf/subversion/tags/1.14.3/CHANGES > > Questions, comments, and bug reports to users@subversion.apache.org. > > Thanks, > - The Subversion Team > > -- > To unsubscribe, please see: > > https://subversion.apache.org/mailing-lists.html#unsubscribing > [Sage] > > The information contained in this email transmission may constitute > confidential information. If you are not the intended recipient, please > take notice that reuse of the information is prohibited. > >
Re: [External] : Re: Can't connect to github anymore
Den tis 16 jan. 2024 kl 19:58 skrev Trent Fisher : > > On 1/14/2024 2:52 PM, Nico Kadel-Garcia wrote: > > On Sun, Jan 14, 2024 at 2:27 PM sean > wrote: > > On 2024-01-13 16:11, Nico Kadel-Garcia wrote: > > > There are not many compelling reasons > to use Subversion anymore, except the ability to check out only > subdirectories from a branch and the insistence that a single central > repository is the only source of truth. > > The ability to `svn lock` files is very useful if your repo has a lot of > non-mergeable files, like say MS Office documents. > > I have never once found that feature to be useful since I first used > Subversion back around 2001. Mind you, I'd treat Word documents as > binaries objects and not consider them suitable for incremental > changes in a source control system. > > There are numerous documentation teams who I have worked with over the > years who would differ with this. Version control is essential for their > files (they may not be able to directly compare them, but they can tell > when changes were made and who made them), and having locking is the only > way to make this work (which is one of the reasons why Git will never work > for them). > > However, I would agree with you that binaries generated from some other > source document is not appropriate for version control (e.g. checking in > PDF versions of documents), but Word documents are the primary source > documents, therefore needing version control. > > Before I got these teams on to SVN, they were storing everything in a > shared folder with numerous old copies of each document laying around (e.g. > foo.doc, foo.doc.old, foo.doc.1jun2013, foo.doc.bak, etc), which is an > accident waiting to happen. > > TortoiseSVN, the Windows client, has some scripts that actually allow "diffing" of Word and Excel documents. It is not perfect (and big formatting changes can really throw you off) but it is quite good and helps if you need to use DOCX or XLSX as your "source". For Word, it uses a built-in comparison feature and for Excel it uses conditional formatting to highlight changes. Kind regards, Daniel
Re: [External] : Re: Can't connect to github anymore
On 1/14/2024 2:52 PM, Nico Kadel-Garcia wrote: On Sun, Jan 14, 2024 at 2:27 PM sean wrote: On 2024-01-13 16:11, Nico Kadel-Garcia wrote: There are not many compelling reasons to use Subversion anymore, except the ability to check out only subdirectories from a branch and the insistence that a single central repository is the only source of truth. The ability to `svn lock` files is very useful if your repo has a lot of non-mergeable files, like say MS Office documents. I have never once found that feature to be useful since I first used Subversion back around 2001. Mind you, I'd treat Word documents as binaries objects and not consider them suitable for incremental changes in a source control system. There are numerous documentation teams who I have worked with over the years who would differ with this. Version control is essential for their files (they may not be able to directly compare them, but they can tell when changes were made and who made them), and having locking is the only way to make this work (which is one of the reasons why Git will never work for them). However, I would agree with you that binaries generated from some other source document is not appropriate for version control (e.g. checking in PDF versions of documents), but Word documents are the primary source documents, therefore needing version control. Before I got these teams on to SVN, they were storing everything in a shared folder with numerous old copies of each document laying around (e.g. foo.doc, foo.doc.old, foo.doc.1jun2013, foo.doc.bak, etc), which is an accident waiting to happen.
