Re: Bug Report: Subversion 1.7 segfaults when using gnome-keyring authentication (Linux x64)

[Stefan Hett]

Hi Vikram,

Hi,

I'm also stuck with this same issue,
"svn up" makes svn segfaults and coring.
This started happening when I give
my new password set in my svn server.

Can some one please help on this?
Any help is highly appreciated.

Thanks
Vikram
Unfortunately the 1.7 branch is no longer supported. Said that, 1.7.19 
contained a fix for a crash related to gnome keyrings. Since the OP 
stated he had the crash with 1.7.20 as well as with 1.7.19 that fixed 
issue cannot be the one he was reporting, but maybe it applies in your 
case (if you are running an older 1.7 version)?


Otherwise the OP stated that he didn't get crashes when using SVN 1.8 
and that's what I suggest you'd try as well, if possible.


--
Regards,
Stefan Hett

Re: Subversion commit email script and "unprintable" characters

[Philip Martin]

Alfred von Campe  writes:

> On Jan 19, 2016, at 15:09, Philip Martin wrote:
>
>> I think that means your bindings were built against python 2.7, which
>> provides PyCapsule_Import, while you are trying to use 2.6, which does
>> not provide it.
>
> Thanks for the info.  So how do I resolve this?  I’m not a Python person,
> but I do know we have a parallel installation of Python 2.7 on the server.
> I am using the WANDisco repo for Subversion binaries and have the latest
> 1.8.X version installed on the server, including the subversion-python
> package.  But my guess is that the Python 2.7 installation can’t see the
> subversion-python files.  Is there a way to install it with easy-install-2.7
> or pip2.7?

The Subversion Python bits have been installed in the Python 2.6 tree
and really need to be in the Python 2.7 tree.  On a CentOS 6 machine
with Python 2.7 installed via scl I can make things work by moving the
Python bits from the 2.6 location to the 2.7 location.  As root:

mv /usr/lib64/python2.6/site-packages/libsvn 
/opt/rh/python27/root/usr/lib64/python2.7/site-packages
mv /usr/lib64/python2.6/site-packages/svn 
/opt/rh/python27/root/usr/lib64/python2.7/site-packages

Then I can do:

$ svnadmin create repo
$ scl enable python27 python
Python 2.7.5 (default, Dec  3 2013, 08:35:16) 
[GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from svn import repos
>>> r = repos.open("repo")
>>>

-- 
Philip Martin
WANdisco

Re: Subversion commit email script and "unprintable" characters

[Alfred von Campe]

On Jan 20, 2016, at 6:40, Philip Martin wrote:

> The Subversion Python bits have been installed in the Python 2.6 tree
> and really need to be in the Python 2.7 tree.  On a CentOS 6 machine
> with Python 2.7 installed via scl I can make things work by moving the
> Python bits from the 2.6 location to the 2.7 location.

We are using Python-2.7 from the IUS Community Project and not SCL, and I
was not able to get this to work.  I copied the files from /usr/lib/python2.6
to /usr/lib/python2.7 (both under site-packages), but the python2.7 binary
did not find the svn files (there is another svn library installed as an egg
via easy_install).  I’m ready to punt on this issue, as we will be moving to
new Subversion servers soon, and I believe they will be running RHEL 7 so I
shouldn’t have to play these games.  It should not be this hard to run the
new mailer.py script on a RHEL/CentOS 6 system, especially since active
development on it appears to have stopped before RHEL 7 came out.

Alfred

Re: Subversion commit email script and "unprintable" characters

[Philip Martin]

Alfred von Campe  writes:

> It should not be this hard to run the
> new mailer.py script on a RHEL/CentOS 6 system, especially since active
> development on it appears to have stopped before RHEL 7 came out.

You encountered a packaging bug.  WANdisco's Subversion 1.8 package for
RHEL/CentOS 6 is going to be rebuilt to have useable python bindings.

-- 
Philip Martin
WANdisco

Re: Subversion commit email script and "unprintable" characters

[Alfred von Campe]

On Jan 20, 2016, at 11:29, Philip Martin wrote:

> You encountered a packaging bug.  WANdisco's Subversion 1.8 package for
> RHEL/CentOS 6 is going to be rebuilt to have useable python bindings.

Excellent, thanks for the update.  I will wait for the next release and
then try again.

Alfred

Modifying SVN Externals with Specific Revision

[Crast, Nicholas]

Hi all,

I have a folder with the svn:externals property set, grabbing an external 
folder from a different part of the repository:
-r6367 ../common/testproc proc1/common

If I go into proc1/common and edit a file in there, svn stat shows the file as 
modified, but it seems that since I specified a specific revision, I am unable 
to commit the modified external file. It is essentially ignored by svn commit.

This is, in fact, the behavior I want. I just want to know if it's guaranteed 
that modifications to external directories with a specific revisions will not 
be committed.

Can someone verify this? Cannot find this specific case anywhere.

-Nick


Nick Crast
Software Engineer
Saab Sensis Corporation
Phone: 315-445-5703
Email: nicholas.cr...@saabsensis.com


This message is intended only for the addressee and may contain information 
that is company confidential or privileged. Any technical data in this message 
may be exported only in accordance with the U.S. International Traffic in Arms 
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be 
unlawful. If you are not the intended recipient, or the person responsible for 
delivering to the intended recipient, you should not read, copy, disclose or 
otherwise use this message. If you have received this email in error, please 
delete it, and advise the sender immediately.