> On 15 Dec 2024, at 15:52, Nathan Hartman wrote:
>
> (Apologies for the duplicate; I meant to respond to the users@ list
> but omitted it the first time...)
>
> On Fri, Dec 13, 2024 at 12:10 PM Barry Scott wrote:
>>
>> I have a svn repo hosted on a Fedora
I have a svn repo hosted on a Fedora server that I access via http: using
mod_dav_svn-1.14.4-1.fc41.x86_64.
The repo has 1999 revs in it but fails to create rev 2000 with these errors
in the httpd error log:
[dav:error] An error occurred while committing the transaction. [500, #1]
[dav:error] Ca
PySVN home page: https://pysvn.sourceforge.io/
PySVN 1.9.13 supporting Subversion 1.14.1 and earlier.
Changes:
* Add support for subversion 1.14.1
* Use latest openssl 1.1.1k
* Fix issue with Client.mkdir() on Windows python 3.8 and later
* No longer able to build python 2.7 kits for Windows.
A
SCM Workbench features
* Support Subversion (svn), Mercurial (hg) and Git projects.
* Experimental support for Perforce (P4)
* Easy to learn and use
* Builtin User Guide describes the operation and features of the application.
* Add project wizard can scan for all your existing projects.
* All sub
PySVN home page: https://pysvn.sourceforge.io/
PySVN 1.9.12 supporting Subversion 1.14.0 and earlier.
Changes:
* Binary kits limited to using currently support versions of Subversion
and Python. However python 2.7 kits will be provided after python 2.7
goes end-of-life.
* Add support for subv
I'm doing some testing and want to test with plaintext passwords.
It seems that storing plaintext passwords can be compiled out. Is that why I
cannot configure it
back on?
Barry
PySVN home page: https://pysvn.sourceforge.io/
PySVN 1.9.11 supporting Subversion 1.13.0 and earlier.
Changes:
* Binary kits limited to using currently support versions of Subversion
and Python. However python 2.7 kits will be provided after python 2.7
goes end-of-life.
* Add suport for subve
SCM Workbench features
• Support Subversion (svn), Mercurial (hg) and Git projects.
• Experimental support for Perforce (P4)
• Easy to learn and use
• Builtin User Guide describes the operation and features of the
application.
• Add project wizard can scan
> On 6 Aug 2019, at 15:50, Daniel Shahaf wrote:
>
> Barry Scott wrote on Mon, 05 Aug 2019 10:14 +00:00:
>> Changes:
>> * Built against subversion 1.12.2, 1.11.1, 1.10.6 and 1.9.12
>
> Subversion 1.11.1 is no longer supported by the Subversion project (
PySVN home page: https://pysvn.sourceforge.io/
PySVN 1.9.10 supporting Subversion 1.12.0 and earlier.
Changes:
* Built against subversion 1.12.2, 1.11.1, 1.10.6 and 1.9.12
* Built against PyCXX 7.1.3 to pick up fix for a memory leak with python 3
strings
* Prepare for Python 3.8 - binary kit wi
PYSVN Extension release supporting Subversion 1.10.0, 1.9.7 and 1.8.19
This is update to pysvn which adds support for subversion 1.10.0.
Mac OS X kits are built for OSX 10.9 and later, testing on 10.13
Windows kits are build for Windows 7 or latest, tested on Windows 10.
Windows 64 bit kits are
SCM Workbench features
• Support Subversion (svn), Mercurial (hg) and Git projects.
• Easy to learn and use
• Builtin User Guide describes the operation and features of the
application.
• Add project wizard can scan for all your existing projects.
• All sub
SCM Workbench features
• Support Subversion (svn), Mercurial (hg) and Git projects.
• Easy to learn and use
• Built in User Guide describes the operation and features of the
application.
• Add project wizard can scan for all your existing projects.
• All su
PYSVN Extension release supporting Subversion 1.9.1, 1.8.14 and 1.7.22
Kits for Python 3.5 are new.
Mac OS X kits are built for OSX 10.9 and 10.10.
Features:
* Support python3 sorting of list of PysvnDict objects that name a known "key”.
* Support Subversion 1.9.1. Note: no Windows kit as no win3
PYSVN WorkBench release supporting Subversion 1.9.1, 1.8.14 and 1.7.22
Kits for Python 3.5 are new.
Mac OS X kits are built for OSX 10.9 and 10.10.
Improvements:
* Support for svn 1.9.1
* Sources changes to make use of WorkBench on linux simpler for packagers
* Add RPM spec file - tested on Fedo
> On 7 Sep 2015, at 21:21, Win32Svn wrote:
>
> On 2015-09-07 18:59, Barry Scott wrote:
>>> On 7 Sep 2015, at 11:43, Andreas Stieger wrote:
>>>
>>> Hi,
>>>
>>> Barry Scott wrote:
>>>> I see that the recent 1.7 and 1.8 win32svn
> On 7 Sep 2015, at 11:43, Andreas Stieger wrote:
>
> Hi,
>
> Barry Scott wrote:
>> I see that the recent 1.7 and 1.8 win32svn builds being announced, thanks
>> for
>> them.
>>
>> Do you know when the svn 1.9 win32svn build might be avail
I see that the recent 1.7 and 1.8 win32svn builds being announced, thanks for
them.
Do you know when the svn 1.9 win32svn build might be available?
Barry
Thanks will the required changes be in alpha3?
Is it possible to do the sort without using the private API?
Barry
pysvn author
On 6 Nov 2014, at 19:55, Ben Reser wrote:
> On 11/6/14 5:10 AM, Nico Kadel-Garcia wrote:
>> Out of curiosity, do the same issues occur with gcc on a modern box?
>> Th
I have been building pysvn against the latest svn kits. 1.7.18, 1.8.10 and
1.9.0-alpha2
using the Mac OS X Xcode 6.1 command line tools, clang is the compiler not gcc.
Compiling and testing pysvn against 1.7.18 and 1.8.10 works with no errors.
But I get compile errors when compiling pysvn agains
Note: It is not an error in svn to have no author or date in an svn log entry.
Do you see that same data using the svn command line? If so its not a TSVN
issue.
Barry
On 15 Jan 2013, at 08:42, Ajay Pawar wrote:
> Thanks Thorsten fro your prompt reply but the as I am the owner of the server
PySVN home page: http://pysvn.tigris.org/
PySVN Workbench documentation http://pysvn.tigris.org/docs/WorkBench.html
The kits have been built against SVN 1.7.8 release.
Features of this release:
* Support Subversion 1.7.8
Features of PySVN WorkBench:
* Easy to use working copy management
* Same
PySVN home page: http://pysvn.tigris.org/
The kits have been built against SVN 1.7.8 release
for python 2.6, 2.7, 3.2 and 3.3.
This release include:
* bug fixes for reported issues
* Support SVN 1.7.8
* New Mac installer
Features of PySVN:
* Natural python interface to Subversion
* Supports Sub
PySVN home page: http://pysvn.tigris.org/
PySVN Workbench documentation http://pysvn.tigris.org/docs/WorkBench.html
The kits have been built against SVN 1.7.3 and 1.6.17 release.
Features of this release:
* Support Subversion 1.7
* Add Upgrade command to allow 1.6 working copies to be upgrades b
PySVN home page: http://pysvn.tigris.org/
The kits have been built against SVN 1.7.3 and SVN 1.6.17release
for python 2.6, 2.7 and 3.2.
This release include:
* bug fixes for reported issues
* Support SVN 1.7
* Support Python 3.2
Features of PySVN:
* Natural python interface to Subversion
* Supp
PySVN home page: http://pysvn.tigris.org/
PySVN Workbench documentation http://pysvn.tigris.org/docs/WorkBench.html
The kits have been built against SVN 1.6.15 release.
Features of this release:
* Bug fixes for reported issues
Features of PySVN WorkBench:
* Easy to use working copy management
PySVN home page: http://pysvn.tigris.org/
The kits have been built against SVN 1.6.15 release
for python 2.6, 2.7 and 3.1.
This release include:
* bug fixes for reported issues
* On Mac OS X it is now possible to install pysvn kits for multiple versions of
python
* New binary kit for Apple's Pyt
On 26 Feb 2010, at 13:01, Stefan Sperling wrote:
> On Fri, Feb 26, 2010 at 12:05:52AM +0000, Barry Scott wrote:
> j
>> On 25 Feb 2010, at 23:18, Stefan Sperling wrote:
>>
>>> On Thu, Feb 25, 2010 at 10:30:18PM +, Barry Scott wrote:
>>>> I starting to
On 25 Feb 2010, at 23:18, Stefan Sperling wrote:
> On Thu, Feb 25, 2010 at 10:30:18PM +0000, Barry Scott wrote:
>> I starting to see failures to commit because of tree conflicts.
>>
>> svn status does not seem to show tree conflicts.
>
> It sure does. See examples
I starting to see failures to commit because of tree conflicts.
svn status does not seem to show tree conflicts.
Did I miss the way to find the tree conflicts?
At the moment I'm having to guess which folder is in conflict.
Barry
30 matches
Mail list logo
