Michael Pilato wrote on Wed, 11 Mar 2020 14:25 +00:00:
> > While you're waiting for someone to manually roll a nightly tarball, can we
> > circle back to the original problem for a minute: What stops you from
> > running autogen.sh? Is it just that you'd like someone to figure out
> > the list of build dependency package names and configure arguments for
> > a working copy build for your platform? (Note this could be a concern
> > even for tarball builds, if both py2 and py3 are installed.)
>
> So, yes, I "just" need a functional 1.14-to-be Subversion with Python 3
> bindings for the purposes of testing my attempts to convert ViewVC
> itself to Python 3. But I'd also like to get a head start on getting
> some of this working in CollabNet's public and private ecosystems,
> which depend on having a Subversion release tarball as their starting
> block. My request was aimed at hopefully meeting all of those needs
> simultaneously.
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 roll trunk-nightly $(svn info --show-item=revision -- $REPOS_URL)»
in a plain Debian stable VM with the following packages installed:
subversion python-yaml pax gettext m4
You may need to pass PYTHON=python3 to configure.
Cheers,
Daniel
Received on 2020-03-11 16:38:14 CET