t; /usr/lib/python2.7/dist-packages/libsvn/_core.x86_64-linux-gnu.so: undefined
>> symbol: svn_relpath__internal_style
>>
>> I submitted this to the ViewVC GitHub issue site for ViewVC and got back:
>>
>> This seems like a problem with Subversion's python bindings (which ViewVC
>&g
ted this to the ViewVC GitHub issue site for ViewVC and got back:
>
> This seems like a problem with Subversion's python bindings (which ViewVC
> depends on to do its thing for Subversion repositories), and specifically an
> issue with the packaging of those bindings on your specific plat
this I get:
ImportError: /usr/lib/python2.7/dist-packages/libsvn/_core.x86_64-linux-gnu.so:
undefined symbol: svn_relpath__internal_style
I submitted this to the ViewVC GitHub issue site for ViewVC and got back:
This seems like a problem with Subversion's python bindings (which
ViewVC depends
On 2021/02/17 6:17, Lev Serebryakov wrote:
> On 16.02.2021 23:52, Yasuhito FUTATSUKI wrote:
>>
>
>>> However, I don't think it is not an issue of Subversion release tarball
>>> but an issue of FreeBSD ports.
>>
>> This may be incorrect. It seems it is caused by wrong rule of
>> copy-swig-py:
On 16.02.2021 23:52, Yasuhito FUTATSUKI wrote:
However, I don't think it is not an issue of Subversion release tarball
but an issue of FreeBSD ports.
This may be incorrect. It seems it is caused by wrong rule of
copy-swig-py: target.
Yep, it is wrong in case of multi-job build. It works
py37/subversion-1.14.1/subversion/bindings/swig/python/libsvn/_repos.so ->
../.libs/_repos.so
lrwxr-xr-x 1 lev lev 15 17 Feb 00:13
work-py37/subversion-1.14.1/subversion/bindings/swig/python/libsvn/_wc.so ->
../.libs/_wc.so
]]]
So, there IS bug in subversion Makefiles: building of python bin
In article <210217035914.m0144...@mkii.yf.bsdclub.org>
futat...@yf.bsdclub.org writes:
> However, I don't think it is not an issue of Subversion release tarball
> but an issue of FreeBSD ports.
This may be incorrect. It seems it is caused by wrong rule of
copy-swig-py: target.
> Perhaps
In article
hartman.nat...@gmail.com writes:
> Are you building from a distribution tarball? (As opposed to a
> checkout or export of the 1.14.1 tag in our repository...) If so, did
> you run autogen.sh? I noticed some changes in
> subversion/bindings/swig/INSTALL on trunk that haven't been
In article
hartman.nat...@gmail.com writes:
> On Tue, Feb 16, 2021 at 12:32 PM Lev Serebryakov
> wrote:
> > I found cause, but as I'm not python programmer, I don't understand it.
> >
> > Old "import _XXX" (like "import _core" in
> > subversion/bindings/swig/python/core.py) works, new "from
Nathan Hartman wrote on Tue, 16 Feb 2021 17:15 +00:00:
> You can generate a diff to view the changes with:
>
> $ svn diff \
> https://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/swig/INSTALL\
>
On Tue, Feb 16, 2021 at 12:32 PM Lev Serebryakov
wrote:
> I found cause, but as I'm not python programmer, I don't understand it.
>
> Old "import _XXX" (like "import _core" in
> subversion/bindings/swig/python/core.py) works, new "from . import XXX"
> doesn't.
>
>I've patched these lines
On 16.02.2021 20:15, Nathan Hartman wrote:
Update to 1.14.1 break out-of-tree build of python bindings (with python
3.7).
Are you building from a distribution tarball? (As opposed to a
checkout or export of the 1.14.1 tag in our repository...) If so, did
you run autogen.sh? I noticed
On 16.02.2021 19:51, Yasuhito FUTATSUKI wrote:
Update to 1.14.1 break out-of-tree build of python bindings (with python
3.7).
1.14.0 works with same options, makefiles, etc. 1.14.1 fails to build
bindings when libraries are installed and swig is not installed (bindings are
built
On Tue, Feb 16, 2021 at 10:05 AM Lev Serebryakov
wrote:
>
>
>Update to 1.14.1 break out-of-tree build of python bindings (with python
> 3.7).
Are you building from a distribution tarball? (As opposed to a
checkout or export of the 1.14.1 tag in our repository...) If so,
Hi,
On 2021/02/17 0:04, Lev Serebryakov wrote:
>
> Update to 1.14.1 break out-of-tree build of python bindings (with python
> 3.7).
> 1.14.0 works with same options, makefiles, etc. 1.14.1 fails to build
> bindings when libraries are installed and swig is not inst
Update to 1.14.1 break out-of-tree build of python bindings (with python 3.7).
1.14.0 works with same options, makefiles, etc. 1.14.1 fails to build
bindings when libraries are installed and swig is not installed (bindings are
built as separate ntity, not together with subversion
Hi,
On 2020/04/13 4:04, Mark Phippard wrote:
> On Sun, Apr 12, 2020 at 1:10 PM Nico Kadel-Garcia wrote:
>
>> On Sat, Apr 11, 2020 at 3:21 PM Jarkko Hyvärinen
>> wrote:
>>>
>>> Hi
>>>
>>>
>>>
>>> I have installed Subvers
On Sun, Apr 12, 2020 at 1:10 PM Nico Kadel-Garcia wrote:
> On Sat, Apr 11, 2020 at 3:21 PM Jarkko Hyvärinen
> wrote:
> >
> > Hi
> >
> >
> >
> > I have installed Subversion 1.10.6 and python bindings
> (subversion-python) to CentOS 8 server from open
On Sat, Apr 11, 2020 at 3:21 PM Jarkko Hyvärinen
wrote:
>
> Hi
>
>
>
> I have installed Subversion 1.10.6 and python bindings (subversion-python) to
> CentOS 8 server from opensource.wandisco.com repo. My goal is to get Trac and
> Subversion working with CentOS 8.
>
Hi
I have installed Subversion 1.10.6 and python bindings (subversion-python) to
CentOS 8 server from opensource.wandisco.com repo. My goal is to get Trac and
Subversion working with CentOS 8.
After installation I encoutered two problems with python bindings:
1. If I run > ’python2
Hi,
In article
l...@serebryakov.spb.ru writes:
>
> Looks like python bindings doesn't work with pyhton 3. It could be
> built no problem, but "check-swig-py" target fails (see log below)
>
> Is it known problem or something wrong on my side?
It's known proble
Looks like python bindings doesn't work with pyhton 3. It could be
built no problem, but "check-swig-py" target fails (see log below)
Is it known problem or something wrong on my side?
===
if [ "LD_LIBRARY_PATH" = "DYLD_LIBRARY_PATH" ]; then for d in
/usr/h
Hi,
Im trying to use the python-swig bindings to copy the log entries of our
repository into a database for indexing and cross referencing. There is one
minor problem: The callback seems to be called a few times with invalid log
entries:
(-1L, {}, None)
That is obviously easy to filter out,
Dear list,
I thought I had subversion compiled OK, all the tests appear to be passing, but
when I went looking for the python bindings they were missing. Looking at the
VS2012 solution file, the __SWIG_PYTHON__ project seems to be empty and does
nothing when rebuilt.
So I have re-built
-Original Message-
From: Cooke, Mark [mailto:mark.co...@siemens.com]
Sent: donderdag 9 oktober 2014 14:32
To: users@subversion.apache.org
Subject: Compiling python bindings (VS2012, Windows 7)
Dear list,
I thought I had subversion compiled OK, all the tests appear
Hi,
I have subversion 1.6.11 installed on redhat 64bit server used since
long. Seems to be installed using rpm/yum not from source.
Can you suggest me how i get svn python binding for existing setup without
effective my current environment? everyone says of compiling from source,
which i am
From: kapila narang [mailto:kapilanar...@gmail.com]
Sent: 28 May 2013 12:08
To: users@subversion.apache.org
Subject: Get subversion python bindings on existing subversion setup
Hi,
I have subversion 1.6.11 installed on redhat 64bit server used since long
fixed our file-handle leak for, but I believe it points
to a bug in the Subversion bindings for which I'll try and provide a patch.
Before I file a bug I'd like to check I haven't misunderstood anything:
1. In the Python bindings core.Stream doesn't have a .close() method [a]. Is
there any
-handle leak for, but I believe it points to
a bug in the Subversion bindings for which I'll try and provide a patch. Before
I file a bug I'd like to check I haven't misunderstood anything:
1. In the Python bindings core.Stream doesn't have a .close() method [a]. Is
there any reason this might
/finally block.
Disclaimer: I'm not really familiar with the SVN/Python bindings.
However, concerning Python in general, explicitly calling close() is the
wrong way. Instead you should make sure files are closed by opening them
in a with clause:
with open(...) as f:
... # use f
with the SVN/Python bindings.
However, concerning Python in general, explicitly calling close() is the
wrong way. Instead you should make sure files are closed by opening them
in a with clause:
with open(...) as f:
... # use f
Unfortunately I'm targeting Python 2.4, but always worth mentioned
-Original Message-
From: Alagazam.net Subversion [mailto:s...@alagazam.net]
Sent: 21 March 2012 19:41
To: Brian Neal
Cc: users@subversion.apache.org
Subject: Re: Problem with Python bindings to SVN 1.7.4 on Windows
On 2012-03-21 20:14, Brian Neal wrote:
On Wed, Mar 21, 2012
Hello -
I'm trying to upgrade a Subversion and Trac install running on Windows
Server 2003 sp2.
I've installed Subversion 1.7.4 from the .msi file found here:
http://sourceforge.net/projects/win32svn/files/1.7.4/
I'm also using the Python 2.7 bindings found in that same directory
-Original Message-
From: Brian Neal [mailto:bgn...@gmail.com]
Sent: 21 March 2012 16:13
To: users@subversion.apache.org
Subject: Problem with Python bindings to SVN 1.7.4 on Windows
Hello -
I'm trying to upgrade a Subversion and Trac install running on Windows
Server 2003 sp2
On Wed, Mar 21, 2012 at 11:12 AM, Brian Neal bgn...@gmail.com wrote:
[... snip ..]
Hello -
I'm trying to upgrade a Subversion and Trac install running on Windows
Server 2003 sp2.
I've installed Subversion 1.7.4 from the .msi file found here:
. It is strange that I also need to copy those 2 DLL's
to the Python bindings folder.
Thanks,
BN
to find
the SVN binaries. It is strange that I also need to copy those 2 DLL's
to the Python bindings folder.
Thanks,
BN
Do you have another libeay32.dll and ssleay32.dll in some other folder
that is before Subversion\bin in your path ?
If that's the case and these are older versions there might
On Wed, Mar 21, 2012 at 1:41 PM, Alagazam.net Subversion
s...@alagazam.net wrote:
Do you have another libeay32.dll and ssleay32.dll in some other folder that
is before Subversion\bin in your path ?
If that's the case and these are older versions there might be trouble.
/David a.k.a. Alagazam
Guten Tag Brian Neal,
am Mittwoch, 21. März 2012 um 20:14 schrieben Sie:
Is there anything that can be done to avoid a problem like that in the
future? Perhaps a note in the readme? I have noticed that Bitnami and
Collabnet dump all the SVN and Python binding DLL's into the same
folder. I'm
with the
Subversion binaries (svn-win32-1.7.4.zip) and extract it (or at least
the dll:s) in the same folder where you have the Python bindings.
/David a.k.a. Alagazam
Dear all,
I am new to the list, so please allow me to ask a [maybe] beginner's
question.
I would like to get the SWIG bindings for svn-python, using Python 2.7
and SVN 1.6.13/15
I understood that unless someone already build them somewhere (couldn't
find them) I could build them
, but the configure process should probably
be modified so that the bindings can also be built out of tree.
Michael.
P.S. The documentation about how to build the bindings is
*extremely* poorly advertised. A search for python bindings
on the main page should at least turn up something that tells
people to read
in-tree builds.
Michael.
P.S. The documentation about how to build the bindings is
*extremely* poorly advertised. A search for python bindings
on the main page should at least turn up something that tells
people to read the INSTALL file in the subversion/bindings/swig
directory as one
the Subversion Python bindings installed. It tells me
to go here
http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91,
but that location does not contain the binaries. It suggests two other
sites, but I didn't have any luck finding the binaries there either.
Where can I find
on a windows system. I have downloaded
ViewVC 1.1.6, Python 2.6 and the Python windows extensions. I am running
Subversion 1.5.2 (r32768) on a Windows pc.
The instructions provided by ViewVC tell me that For Subversion support, I'll
need to have the Subversion Python bindings installed
On Monday 15 February 2010, Ramachandran, Vishwanath(IE10) wrote:
Will python-bindings swig support svn hooks scripts?
Hook scripts are executable file which can do pretty much anything they want.
What kind of python-bindings swig do you want?
There is a Collabnet subversion, which comes
Hi there
Will python-bindings swig support svn hooks scripts? There is a
Collabnet subversion, which comes with all the packages including python
which supports the scripts
But since we do not use Collabnet subversion, we are in need of only
python bindings, which supports hooks scripts
We have subversion 1.4.6, Does swig support 1.4? Any suggestions welcome
Regards
Vishwanath
From: Ramachandran, Vishwanath(IE10)
Sent: Monday, February 15, 2010 5:33 PM
To: users@subversion.apache.org
Subject: python bindings
Hi there
Will python-bindings swig support svn
Does it means, subversion 1.4.6 does support swig, ?
Regards
Vishwanath
From: vishwajeet singh [mailto:dextrou...@gmail.com]
Sent: Tuesday, February 16, 2010 12:41 PM
To: Ramachandran, Vishwanath(IE10)
Cc: users@subversion.apache.org
Subject: Re: python bindings
We
12:41 PM
*To:* Ramachandran, Vishwanath(IE10)
*Cc:* users@subversion.apache.org
*Subject:* Re: python bindings
We have subversion 1.4.6, Does swig support 1.4? Any suggestions welcome
First of all Subversion 1.4 series is no more supported so you should
upgrade it to higher version
50 matches
Mail list logo
