Re: Subversion's test fails on aarch64, ppc64 and ppc64le

2022-03-02 Thread James McCoy
On Wed, Mar 02, 2022 at 03:47:23PM +, Danilo Spinella wrote: > Hi, > > I am the openSUSE maintainer of subversion package. With the latest > version, the automated build of subversion 1.14.1 for Tumbleweed is > failing due to the following test failure: > > 1) > testCrash_RequestChannel_nati

Re: svn commit: r1898524 - in /subversion/trunk/subversion: svn/help-cmd.c tests/cmdline/getopt_tests_data/svn--version--verbose_stdout tests/cmdline/getopt_tests_data/svn--version_stdout

2022-03-02 Thread Julian Foad
Julian Foad wrote: > Daniel Sahlberg wrote: >> Should the following lines also be removed [...] > Oh yes. Thank you. Please do if you have a moment, otherwise I'll get > to it some time this week. I got to it now. r1898535. I note that we might want to replace that with a matcher for variations o

Re: svn commit: r1898524 - in /subversion/trunk/subversion: svn/help-cmd.c tests/cmdline/getopt_tests_data/svn--version--verbose_stdout tests/cmdline/getopt_tests_data/svn--version_stdout

2022-03-02 Thread Julian Foad
Daniel Sahlberg wrote: >Should the following lines also be removed [...] Oh yes. Thank you. Please do if you have a moment, otherwise I'll get to it some time this week. - Julian

Re: svn commit: r1898524 - in /subversion/trunk/subversion: svn/help-cmd.c tests/cmdline/getopt_tests_data/svn--version--verbose_stdout tests/cmdline/getopt_tests_data/svn--version_stdout

2022-03-02 Thread Daniel Sahlberg
Den ons 2 mars 2022 12:04 skrev: > Modified: > subversion/trunk/subversion/tests/cmdline/getopt_tests_data/svn--version_stdout > URL: > http://svn.apache.org/viewvc/subversion/trunk/subversion/tests/cmdline/getopt_tests_data/svn--version_stdout?rev=1898524&r1=1898523&r2=1898524&view=diff > >

Re: A two-part vision for Subversion and large binary objects.

2022-03-02 Thread Julian Foad
Mark Phippard wrote: > That comment specifically talks about diff. [...] For an update, I > think it is unexpected and undesirable. [...] You're right, the comment I pointed to doesn't do anything to justify why 'update' should fetch it. And I agree it would be better if it didn't. Maybe we will b

Re: multi-wc-format review

2022-03-02 Thread Julian Foad
On Feb 25 2022, Daniel Shahaf wrote: >> [...] we are now deliberately choosing compatibility as the default, > > OK. However, in this case we should document this explicitly, since the > book explicitly documents that «svn upgrade» would upgrade to the "most > recent metadata format supported by

Re: multi-wc-format: upgrading externals

2022-03-02 Thread Julian Foad
Daniel Shahaf wrote: > multi-wc-format/BRANCH-README mentioned this: > >> [*] New externals working copies must inherit the format from their >>parent working copy, because [...] > > Upgrading a parent working copy upgrades external wc's too. However, > upgrading an external succeeds. Jud

Re: svn commit: r1898378 - in /subversion/trunk/subversion: include/ libsvn_client/ libsvn_wc/ svn/ tests/cmdline/getopt_tests_data/

2022-03-02 Thread Julian Foad
> Output will be, I suggest, like this: > > * WC format 31, compatible with Subversion v1.8 and newer > * WC format 32, compatible with Subversion v1.15 and newer r1898524.

Re: Creating future-version wc's

2022-03-02 Thread Julian Foad
Julian Foad wrote: > Daniel Shahaf wrote: >> I expected this to error out hard, since we can't create 1.16-format > Agreed, that seems better. Will do. r1898523. - Julian