Re: A little pre-packaging help, please?

2020-03-13 Thread Michael Pilato
> https://home.apache.org/~danielsh/subversion-20200311_001/subversion-nightly-r1875088.tar.gz > https://home.apache.org/~danielsh/subversion-20200311_001/subversion-nightly-r1875088.tar.gz.asc > > For future reference, that's the output of «release.py build-env > trunk-nightly && > release.py ro

Re: A little pre-packaging help, please?

2020-03-13 Thread Yasuhito FUTATSUKI
On 2020/03/13 21:53, Michael Pilato wrote: > One thing that appears to be different about this tarball than a typical > release tarball is the absence of the swig-generated wrapper files > (...python/svn_client.c, etc.). I'm going to take a crack at replicating > your release environment (the

Re: A little pre-packaging help, please?

2020-03-13 Thread Daniel Shahaf
Michael Pilato wrote on Fri, 13 Mar 2020 12:53 +00:00: > > https://home.apache.org/~danielsh/subversion-20200311_001/subversion-nightly-r1875088.tar.gz > > https://home.apache.org/~danielsh/subversion-20200311_001/subversion-nightly-r1875088.tar.gz.asc > > > > For future reference, that's the outp

Re: svn commit: r1875127 - /subversion/site/publish/docs/release-notes/1.14.html

2020-03-13 Thread Nathan Hartman
On Thu, Mar 12, 2020 at 3:01 PM Daniel Shahaf wrote: > Nathan Hartman wrote on Thu, 12 Mar 2020 18:15 +00:00: > > On Thu, Mar 12, 2020 at 12:36 PM Daniel Shahaf > > wrote: > > > hartmannat...@apache.org wrote on Thu, 12 Mar 2020 15:15 -: > > > > 1.14 release notes: Document selectable shelvin

Re: svn commit: r1875127 - /subversion/site/publish/docs/release-notes/1.14.html

2020-03-13 Thread Daniel Shahaf
Nathan Hartman wrote on Fri, 13 Mar 2020 14:36 -0400: > On Thu, Mar 12, 2020 at 3:01 PM Daniel Shahaf wrote: > > - Promote #shelving from h4 to h3 > > - Transform #checkpoint to an #h4 inside #shelving > > - Reword #shelving-transition to be more explicitly only about > > "upgrading existing she

Re: A little pre-packaging help, please?

2020-03-13 Thread Michael Pilato
> However as I wrote before[1] it is need to specify SWIG_PY_OPTS > shell/environment variable to generate SWIG Python bindings C source > and support codes. The value of SWIG_PY_OPTS depends on which is its > target py2 or py3, on which SWIG version is prior 4.0 or not. This was the key thing lac

Re: A little pre-packaging help, please?

2020-03-13 Thread Michael Pilato
I'm attaching what I used to make this work, which is a Docker-based process. Just expand the tarball, enter the resulting directory, and run ./docker-build.sh. From: Michael Pilato Sent: Friday, March 13, 2020 2:49 PM To: Yasuhito FUTATSUKI ; dev@subversion.apac