Re: release.py create-tag failed to update STATUS

Julian Foad wrote on Sat, 14 Apr 2018 18:21 +0100: > Daniel Shahaf wrote on 2018-04-14: > > > It's because it uses "svnmucc -r put <...>" but STATUS has already > > > been modified between r and HEAD. > > > > Agreed. It's perfectly possible for the branch to have changed between the > > magic r

[PATCH] Fix variable name with path to rdoc

Patch fixes typo introduced in r1806570 most probably by copy&paste of similar line searching for ruby binary. [[[ * configure.ac Fix variable name with path to rdoc ]]] Index: configure.ac === --- configure.ac(revision 18291

Re: release.py create-tag failed to update STATUS

Daniel Shahaf wrote on 2018-04-14: > > It's because it uses "svnmucc -r put <...>" but STATUS has already > > been modified between r and HEAD. > > Agreed. It's perfectly possible for the branch to have changed between the > magic revision and HEAD. When editing STATUS, the base revision (argu

Re: release.py create-tag failed to update STATUS

Julian Foad wrote on Wed, Apr 11, 2018 at 08:21:19 +0100: > Running "release.py create-tag" just now failed: > > + release.py --base-dir /opt/svnrm create-tag 1.10.0 r1827917 > INFO:root:Creating tag for 1.10.0 > r1828867 committed by julianfoad at 2018-04-11T07:00:33.547290Z > INFO:root:Bumping r

Re: How to disable lz4 support when library is installed in system?

> > What should I pass to "configure" to PREVENT detection & usage of lz4 > > library installed in system? `--without-lz4' doesn't work. Yes, I can reproduce this. '--without-lz4' results in: configure: lz4 configuration via prefix checking for LZ4_compress_default in -llz4... yes which is not