From d9e1702f7db1a1ac9bf05fd7148f46b2a0f2c098 Mon Sep 17 00:00:00 2001 From: James McCoy Date: Wed, 30 Nov 2016 02:32:43 +0000 Subject: Update 1.9 release notes --- debian/svn_1.9_releasenotes.html | 133 +++++++++++++++++++++------------------ 1 file changed, 73 insertions(+), 60 deletions(-) (limited to 'debian/svn_1.9_releasenotes.html') diff --git a/debian/svn_1.9_releasenotes.html b/debian/svn_1.9_releasenotes.html index ec3bf60..4569942 100644 --- a/debian/svn_1.9_releasenotes.html +++ b/debian/svn_1.9_releasenotes.html @@ -55,6 +55,8 @@ >Many enhancements and bug fixes
  • Known issues in the release
    • +
  • Troubleshooting issues specific to this release

    • Apache Subversion 1.9 is a superset of all previous Subversion @@ -168,65 +170,27 @@ and what impact these changes may have.

    Subversion 1.9 uses the same working copy format as Subversion 1.8.

    -

    Before using Subversion 1.9 with existing an 1.6 or 1.7 working copy, -users will be required to run the svn upgrade command to upgrade -working copy metadata to the new format. This command may take a while, and -for some users, it may be more practical to simply checkout a new working -copy.

    - -

    Subversion 1.9 can only upgrade working copies created with Subversion 1.6 -and Subversion 1.7.

    +

    Before using Subversion 1.9 with an existing Subversion 1.7 or older +working copy, users will be required to run the svn upgrade command +to upgrade working copy metadata to the new format. This command may take a +while in some cases, and for some users, it may be more practical to simply +checkout a new working copy.

    Note: Subversion 1.9 cannot upgrade working copies that a 1.6 client would have refused to operate upon before an svn cleanup was run (with a 1.6 client). In other words, before upgrading to 1.9, a 1.6 -client must be used to run svn cleanup on all 1.6 working copies that -require cleanup. Likewise, Subversion 1.9 cannot upgrade corrupt 1.6 working -copies. Unfixable problems can arise from missing or corrupt meta-data inside -.svn directories. Such damage to the 1.6 working copy is permanent, -and cannot be fixed even if svn cleanup is run prior to the upgrade.

    - -

    If your working copy does not upgrade cleanly, please check out a new one.

    +or older client must be used to run svn cleanup on all 1.6 or older +working copies that require cleanup. Likewise, Subversion 1.9 cannot upgrade +corrupt working copies. Unfixable problems can arise from missing or corrupt +meta-data inside .svn directories. Such damage to the working copy +is permanent, and cannot be fixed even if svn cleanup is run prior +to the upgrade.

    + +

    If your working copy does not upgrade cleanly, please check out a new one. +

    - -

    Upgraded Minimal Dependencies cycle. You can tell whether all format 7 features are enabled by looking for FSFS Logical Addressing: yes in the output of svnadmin info: if that line is printed, then the repository has all format 7 features enabled. +

    WARNING: Server restart @@ -386,7 +351,7 @@ the benefits. Format 6
    or older Upgraded to format 7
    from older formats Created as format 7
    not packed - Created as format 7
    packed + Created as format 7
    packed Reduction in dynamic memory usage1 yes @@ -674,14 +639,14 @@ in its documentation. The following restrictions and workarounds apply:

  • The first entry must refer to the first revision in the pack file. This is a non-issue for unpacked revisions. A simple solution is inserting a line for empty section of length 0: -
    • -
    +      
            Start       Length Type   Revision     Item 
            0            0 none       3000        0
            0          25a chgs       3999        1
          25a          3b9 chgs       3998        1
        ...
-
    
+
    +

    These problems have been fixed in 1.9.1. @@ -925,7 +890,7 @@ validation for various reasons (e.g. expired certificates).

    this option.

    The --trust-server-cert-failures option only works in conjunction with -the --no-interactive option.

    +the --non-interactive option.

    Previous versions of Subversion in non-interactive mode could only ignore certificates with an unknown certificate authority, but expired or otherwise @@ -1081,7 +1046,7 @@ to see your system's defaults and whether the options are available at all.

    This prints detailed format information for the given repository. -

    +

       $ svnadmin info /repos/apache/
@@ -1109,7 +1074,7 @@ to see your system's defaults and whether the options are available at all.
   
 
    Packing now takes a cache size parameter (-M) which is used for
 efficient operation on FSFS format 7 repositories.
-
    
+
    
 
 
       $ svnadmin pack -M 1000 /path/to/repository
@@ -1170,7 +1135,7 @@ on the transaction (commit-in-progress) before it becomes a commit.
    
 
 
    The new delrevprop command deletes a revision property from either
 a revision or a transaction.  It complements setrevprop which adds
-or modifies revprops.
+or modifies revprops.
    @@ -1505,6 +1470,54 @@ protocol. +
    +

    Troubleshooting issues specific to this release + +

    + +

    Subversion 1.9 introduces new features and makes use of new techniques +which can trigger problems not encountered in previous versions. In contrast to +known issues, things listed here are not due to some bug or issue in Subversion +itself and therefore cannot be fixed with a new patch release. +This section lists all known problems and provides instructions to solve them, +if they occur.

    + +
    +

    Lock/Unlock errors related to HTTP pipelining + +

    + +

    Subversion 1.9.0 introduces the use of HTTP pipelining for locking/unlocking +multiple files. While SVN detects whether HTTP pipelining is supported (and +falls back to non HTTP pipelining mode, if it isn't), issues can arrise, if +there are flaws or bugs with any of the protocols/applications involved in +processing pipelined HTTP requests.

    + +

    Especially, if there are older proxies present in the network topology, it's +possible that you run into issues, since being a technology which was +introduced in HTTP/1.1 (and the full performance benefit is not expected unless +you are using HTTP/2), this feature might have not been extensively tested by +your proxy vendor.

    + +

    To troubleshoot whether the proxy is causing an issue, try to lock/unlock +multiple files bypassing the proxy. If that works, please get in touch with +the proxy vendor to notify him about the problem and ask for support.

    + +

    It's also appreciated, if you would let the SVN developers know about the +effected proxy via the users mailing list so this troubleshooting section can +be updated.

    + +

    At the moment there is one potentially known proprietary proxy running into +this issue: Java-SSL-tunnel. See +Tortoise SVN mailing list +.

    + +
    + +
    +

    Subversion 1.7.x series no longer supported