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
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
TL;DR: "svn info -r HEAD > testfile" produces and empty file with svn 1.9.1
on Windows. But svn 1.8.13 produces expected output in the file. Does this
only happen for me?
When I updated to TortoiseSVN 1.9.1 (from 1.8.11), which uses svn 1.9.1 it
seems redirection of "svn info -r HEAD" (or any othe
The TortoiseSVN build of the commandline binaries in 1.9.0 and 1.9.1 have known
issues. Please retry with another release (following the CRT linkage rules), or
use a newer 1.9.x daily build of TortoiseSVN where the linkage problem is fixed.
I’m not sure if this fixes your specific problem, but I
Ok thanks for the input :) Sounds reasonable to suspect CRT linkage issues
since stdout/stderr I/O operations probably rely on the CRT behaving.
I'll see if a TortoiseSVN daily fixes the problem as soon as I get time.
But if that doesn't fix it, so I should file a bug with TortoiseSVN instead
then?
https://msdn.microsoft.com/en-us/library/ms235460.aspx
“Potential Errors Passing CRT Objects Across DLL Boundaries”
And really the first paragraph summarizes what happens here:
“When you pass C Run-time (CRT) objects such as file handles, locales, and
environment variables into or out of a DLL (f
Shall I file a bug report for this and/or provide additional information?
Kind regards,
Markus
-Ursprüngliche Nachricht-
Von: Grabner Markus [mailto:markus.grab...@alicona.com]
Gesendet: Montag, 14. September 2015 12:00
An: 'Philip Martin'
Cc: 'Branko Cibej'; use
The Apache Subversion developers have decided to migrate all tickets
and history from the current issue tracker at Tigris.org[1] to the
Jira instance hosted by the Apache Software Foundation[2].
We feel that an important aspect of the migration is properly
mapping the old accounts of people who've
