Re: officially retire 1.9?

2019-08-05 Thread Mark Phippard
On Mon, Aug 5, 2019 at 2:27 PM Stefan Sperling  wrote:

> Those two operating systems have always been the ones shipping the
> oldest possible SVN release, as far as I can remember. So if they don't
> need Subversion 1.9, I don't see any reason for us to support it beyond
> its 4 years lifetime promised on our web site.
>


Makes sense to me ...  +1

-- 
Thanks

Mark Phippard


officially retire 1.9?

2019-08-05 Thread Stefan Sperling
Subversion 1.9.0 is 4 years old today (release on August 5 2015).
http://subversion.apache.org/roadmap.html#release-planning says that
each LTS release is supported for 4 years.

Julian said on IRC that perhaps we decided to support 2 LTS releases
for either 4 years or until another LTS release appears.
Which means 1.9 would still be supported until 1.14 is released.

But do we really want to continue supporting 1.9?

Do we really want to support two LTS releases at once?
I think this situation arose only because 1.9 got caught in the transition
phase towards our new release planning guidelines.

SVN 1.10 has been picked up by the latest Debian-stable release and also
appears to be included in the upcoming CentOS 8 (which will match RHEL 8,
as far as I know).

Those two operating systems have always been the ones shipping the
oldest possible SVN release, as far as I can remember. So if they don't
need Subversion 1.9, I don't see any reason for us to support it beyond
its 4 years lifetime promised on our web site.


Re: patch on files with svn:keywords ends up with 0600 perms

2019-08-05 Thread Stefan Sperling
On Mon, Aug 05, 2019 at 08:40:48AM -0400, Doug Robinson wrote:
> Gentle reminder.
> 
> On Fri, Jul 26, 2019 at 5:43 PM Doug Robinson 
> wrote:

Hi Doug,

The problem should be fixed with this commit: https://svn.apache.org/r1864440
It's a simple matter of creating temporary files in the working copy's temp
directory instead of the system-wide one.

Regards,
Stefan

> > Committers, et. al.:
> >
> > This was just sent to us by a customer.  We've verified on at 1.10.4.  I
> > checked in JIRA and didn't find a matching bug.  Should I create a new JIRA?
> > 
> >
> > $ svnadmin create test_repo
> >
> > $ svn co file:///tmp/test_repo accnt
> > Checked out revision 0.
> >
> > $ cd accnt/
> > $ touch a.c b.c
> > $ svn add a.c b.c
> > A a.c
> > A b.c
> >
> > # Adding property only on a.c
> > $ svn propset svn:keywords "Id Revision Date URL Author Header" a.c
> > property 'svn:keywords' set on 'a.c'
> > $ ls -l
> > total 0
> > -rw-r--r-- 1 accnt qa-others 0 Jul 25 13:47 a.c
> > -rw-r--r-- 1 accnt qa-others 0 Jul 25 13:47 b.c
> > $ svn commit -m "test commit"
> > Adding a.c
> > Adding b.c
> > Transmitting file data ..done
> > Committing transaction...
> > Committed revision 1.
> > $ svn patch /tmp/patch
> > U a.c
> > > applied hunk @@ -0,0 +1,1 @@ with offset 0
> > U b.c
> > > applied hunk @@ -0,0 +1,1 @@ with offset 0
> >
> > # After applying patch the permission on the file with property
> > svn:keywords has changed.
> > $ ls -l
> > total 8
> > -rw--- 1 accnt qa-others 11 Jul 25 13:49 a.c
> > -rw-r--r-- 1 accnt qa-others 28 Jul 25 13:49 b.c
> >
> > $ umask
> > 0022
> >
> > # The patch applied:
> > $ cat /tmp/patch
> > Index: a.c
> > ===
> > --- a.c (revision 1)
> > +++ a.c (working copy)
> > @@ -0,0 +1 @@
> > +test patch
> > Index: b.c
> > ===
> > --- b.c (revision 1)
> > +++ b.c (working copy)
> > @@ -0,0 +1 @@
> > +test patch without keywords
> >
> > --
> > *DOUGLAS B ROBINSON* SENIOR PRODUCT MANAGER
> >
> > T +1 925 396 1125
> > *E* doug.robin...@wandisco.com
> >
> 
> 
> -- 
> *DOUGLAS B ROBINSON* SENIOR PRODUCT MANAGER
> 
> T +1 925 396 1125
> *E* doug.robin...@wandisco.com
> 
> -- 
> 
> 
> * *
> 
> **The LIVE DATA Company
> *Find out more 
> *wandisco.com *
> 
> 
> 
>  
> 
> *
> 
> 
> THIS MESSAGE 
> AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY AND MAY BE PRIVILEGED
> 
> If 
> this message was misdirected, WANdisco, Inc. and its subsidiaries, 
> ("WANdisco") does not waive any confidentiality or privilege. If you are 
> not the intended recipient, please notify us immediately and destroy the 
> message without disclosing its contents to anyone. Any distribution, use or 
> copying of this email or the information it contains by other than an 
> intended recipient is unauthorized. The views and opinions expressed in 
> this email message are the author's own and may not reflect the views and 
> opinions of WANdisco, unless the author is authorized by WANdisco to 
> express such views or opinions on its behalf. All email sent to or from 
> this address is subject to electronic storage and review by WANdisco. 
> Although WANdisco operates anti-virus programs, it does not accept 
> responsibility for any damage whatsoever caused by viruses being passed.


Re: patch on files with svn:keywords ends up with 0600 perms

2019-08-05 Thread Doug Robinson
Gentle reminder.

On Fri, Jul 26, 2019 at 5:43 PM Doug Robinson 
wrote:

> Committers, et. al.:
>
> This was just sent to us by a customer.  We've verified on at 1.10.4.  I
> checked in JIRA and didn't find a matching bug.  Should I create a new JIRA?
> 
>
> $ svnadmin create test_repo
>
> $ svn co file:///tmp/test_repo accnt
> Checked out revision 0.
>
> $ cd accnt/
> $ touch a.c b.c
> $ svn add a.c b.c
> A a.c
> A b.c
>
> # Adding property only on a.c
> $ svn propset svn:keywords "Id Revision Date URL Author Header" a.c
> property 'svn:keywords' set on 'a.c'
> $ ls -l
> total 0
> -rw-r--r-- 1 accnt qa-others 0 Jul 25 13:47 a.c
> -rw-r--r-- 1 accnt qa-others 0 Jul 25 13:47 b.c
> $ svn commit -m "test commit"
> Adding a.c
> Adding b.c
> Transmitting file data ..done
> Committing transaction...
> Committed revision 1.
> $ svn patch /tmp/patch
> U a.c
> > applied hunk @@ -0,0 +1,1 @@ with offset 0
> U b.c
> > applied hunk @@ -0,0 +1,1 @@ with offset 0
>
> # After applying patch the permission on the file with property
> svn:keywords has changed.
> $ ls -l
> total 8
> -rw--- 1 accnt qa-others 11 Jul 25 13:49 a.c
> -rw-r--r-- 1 accnt qa-others 28 Jul 25 13:49 b.c
>
> $ umask
> 0022
>
> # The patch applied:
> $ cat /tmp/patch
> Index: a.c
> ===
> --- a.c (revision 1)
> +++ a.c (working copy)
> @@ -0,0 +1 @@
> +test patch
> Index: b.c
> ===
> --- b.c (revision 1)
> +++ b.c (working copy)
> @@ -0,0 +1 @@
> +test patch without keywords
>
> --
> *DOUGLAS B ROBINSON* SENIOR PRODUCT MANAGER
>
> T +1 925 396 1125
> *E* doug.robin...@wandisco.com
>


-- 
*DOUGLAS B ROBINSON* SENIOR PRODUCT MANAGER

T +1 925 396 1125
*E* doug.robin...@wandisco.com

-- 


* *

**The LIVE DATA Company
*Find out more 
*wandisco.com *



 

*


THIS MESSAGE 
AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY AND MAY BE PRIVILEGED

If 
this message was misdirected, WANdisco, Inc. and its subsidiaries, 
("WANdisco") does not waive any confidentiality or privilege. If you are 
not the intended recipient, please notify us immediately and destroy the 
message without disclosing its contents to anyone. Any distribution, use or 
copying of this email or the information it contains by other than an 
intended recipient is unauthorized. The views and opinions expressed in 
this email message are the author's own and may not reflect the views and 
opinions of WANdisco, unless the author is authorized by WANdisco to 
express such views or opinions on its behalf. All email sent to or from 
this address is subject to electronic storage and review by WANdisco. 
Although WANdisco operates anti-virus programs, it does not accept 
responsibility for any damage whatsoever caused by viruses being passed.