Re: move certain svn props to top level path?

[Branko Čibej]

On 04.04.2018 23:12, Stefan wrote:
>
> Hi,
>
> atm we specify the following svn properties on trunk:
>
>   * bugtraq:url
>   * bugtraq:logregexp
>   * tsvn:logwidthmarker
>   * tsvn:projectlanguage
>   * webviewer:revision
>   * (possibly by the time you read this, I added webviewer:pathrevision)
>
> Since these properties are currently not set project wide but rather
> on each branch/tags we now have branches still pointing to the old
> bugtrag:url (f.e. the 1.9.x branch) and some branches not having
> certain properties at all (f.e.  the 1.7.x branch missing the
> webviewer:revision property).
>
> I'd therefore like to suggest that we specify these properties just
> once at the top level (i.e. on
> https://svn.apache.org/repos/asf/subversion) and remove them on the
> sub-nodes (i.e. trunk, branches/xxx, tags/xxx, etc.). This will ensure
> we have a consistent setting for these project wise.
>
> Thoughts?
>


I don't even know what these properties are, nor why they're set on our
trunk directory. Assuming they're used by some tools that I'm unaware of
(ok ... I can probably guess what the tsvn: ones are for), you can only
move them a level up if these tools treat them as inheritable properties.

-- Brane

Re: Subversion1.10.0-rc2 up for testing/signing

[Branko Čibej]

Summary:

+1 to release (Windows)

Platform

Windows 10 Pro x64

Build tools:
  Microsoft Visual Studio Professional 2015
  CMake 3.2.3
  SCons 2.3.4 (patched for MSVC14)

Source dependencies:
  APR 1.5.2
  APR-Util 1.5.4
  zlib 1.2.8
  httpd 2.4.16 with pcre-8.37
  SQLite 3.8.8.3 (amalgamated)
  Serf 1.3.8
  OpenSSL 1.0.2

Other dependencies:
  Python 2.7.9
  Perl 5.26.1 (Strawberry Perl)
  Ruby 2.3.3
  Swig 3.0.12
  Java 1.8.0_45-b14
  JUnit 4.11

Verified:

  Tarball contents and signatures

  (fsfs) x (local, svnserve, serf)
  check-javahl
  check-swig-py
  check-swig-pl

Known issues:

  * Ruby 2.x bindings do not build with VS2015

GPG signatures committed to the dist/dev/subversion repository.

Re: move certain svn props to top level path?

[Stefan]

On 04/04/2018 23:47, Branko Čibej wrote:
> On 04.04.2018 23:12, Stefan wrote:
>> Hi,
>>
>> atm we specify the following svn properties on trunk:
>>
>>   * bugtraq:url
>>   * bugtraq:logregexp
>>   * tsvn:logwidthmarker
>>   * tsvn:projectlanguage
>>   * webviewer:revision
>>   * (possibly by the time you read this, I added webviewer:pathrevision)
>>
>> Since these properties are currently not set project wide but rather
>> on each branch/tags we now have branches still pointing to the old
>> bugtrag:url (f.e. the 1.9.x branch) and some branches not having
>> certain properties at all (f.e.  the 1.7.x branch missing the
>> webviewer:revision property).
>>
>> I'd therefore like to suggest that we specify these properties just
>> once at the top level (i.e. on
>> https://svn.apache.org/repos/asf/subversion) and remove them on the
>> sub-nodes (i.e. trunk, branches/xxx, tags/xxx, etc.). This will ensure
>> we have a consistent setting for these project wise.
>>
>> Thoughts?
>>
>
> I don't even know what these properties are, nor why they're set on our
> trunk directory. Assuming they're used by some tools that I'm unaware of
> (ok ... I can probably guess what the tsvn: ones are for), you can only
> move them a level up if these tools treat them as inheritable properties.
>
> -- Brane

I'm not sure if there are other tools around using these. I'm talking
here TSVN which utilizes all of these properties and yes, it's treating
them as inheritable ones. There seem to be other tools using these as
well [1/2], though I can't say for sure whether they are treating them
as inheritable (though I'd strongly suspect so).

[1]
https://stackoverflow.com/questions/47846726/how-to-work-with-svn-propertiesbugtraqlogregex
[2]
https://markphip.blogspot.de/2007/01/integrating-subversion-with-your-issue.html

Regards,
Stefan




smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: [wuzhouhui: Re: width of output of 'svn shelves' is too large]

[Daniel Shahaf]

We're getting feedback on 'svn shelve' on users@.  Does anyone want to follow 
up?

- Forwarded message from wuzhouhui <1530108...@qq.com> -

> Date: Sat, 31 Mar 2018 18:17:17 +0800
> From: wuzhouhui <1530108...@qq.com>
> To: Daniel Shahaf 
> Cc: Subversion 
> Subject: Re: width of output of 'svn shelves' is too large
> Message-Id: 
> X-Mailer: Apple Mail (2.3273)
> 
> 
> > On 31 Mar 2018, at 1:28 AM, Daniel Shahaf  wrote:
> > 
> > wuzhouhui wrote on Mon, Mar 19, 2018 at 19:26:08 +0800:
> >> The width of terminal is 80 column, but the width of output of 'svn 
> >> shelves' is 82
> >> at least, I think 80 is better.
> > 
> > Thanks for testing the pre-releases.
> > 
> >> What do you think?
> > 
> > Agreed in principle, but cannot reproduce the original problem.  With 
> > current
> > trunk, the output for me is 70 columns.  By code inspection, that should be 
> > the
> > case so long as the shelf name is ≤29 characters (plus or minus the length 
> > of
> > the right-hand side description, which can vary by ±5 columns).
> > 
> > What version are you testing with?
> 
> Version: subversion-1.10.0-rc1.tar.bz2
> OS: ubuntu 16.04
> Configure args: ./configure --with-lz4=internal
> 
> That's what I encountered:
> 
> > wzh@localhost:/tmp/subversion-1.10.0-rc1/subversion/svn/wc$ ../svn shelves 
> > | tee /tmp/a.out
> > a   3 mins old235 bytes1 paths 
> > changed
> >  
> >  a |1 +
> >  1 file changed, 1 insertion(+)
> > 
> > wzh@localhost:/tmp/subversion-1.10.0-rc1/subversion/svn/wc$ wc -L /tmp/a.out
> > 82 /tmp/a.out
> > wzh@localhost:/tmp/subversion-1.10.0-rc1/subversion/svn/wc$
> 
> It seemed that the max width of shelves's output is 82 column even if the 
> name of shelve is
> a single char 'a' and the changes is 1 line.
> 
> In addition, I found another issue:
> 1. Create a empty file (named 'a') and version it, then commit.
> 2. Add some contents to file 'a'
> 3. svn shelve a a
> Now, the file 'a' will be deleted, that isn't what I want.
> 

- End forwarded message -

move certain svn props to top level path?

[Stefan]

Hi,

atm we specify the following svn properties on trunk:

  * bugtraq:url
  * bugtraq:logregexp
  * tsvn:logwidthmarker
  * tsvn:projectlanguage
  * webviewer:revision
  * (possibly by the time you read this, I added webviewer:pathrevision)

Since these properties are currently not set project wide but rather on
each branch/tags we now have branches still pointing to the old
bugtrag:url (f.e. the 1.9.x branch) and some branches not having certain
properties at all (f.e.  the 1.7.x branch missing the webviewer:revision
property).

I'd therefore like to suggest that we specify these properties just once
at the top level (i.e. on https://svn.apache.org/repos/asf/subversion)
and remove them on the sub-nodes (i.e. trunk, branches/xxx, tags/xxx,
etc.). This will ensure we have a consistent setting for these project wise.

Thoughts?

Regards,
Stefan



smime.p7s
Description: S/MIME Cryptographic Signature