Bug 141343 - Subversion swig bindings incompatible with swig=1.3.23
Summary: Subversion swig bindings incompatible with swig=1.3.23
Alias: None
Product: Fedora
Classification: Fedora
Component: subversion   
(Show other bugs)
Version: rawhide
Hardware: All Linux
Target Milestone: ---
Assignee: Joe Orton
QA Contact:
: 147647 (view as bug list)
Depends On: 142970
TreeView+ depends on / blocked
Reported: 2004-11-30 16:13 UTC by Ryan Skadberg
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version: 1.1.3-7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-03-22 14:44:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch adding swig 1.3.24 support to subversion 1.1.x (20.95 KB, patch)
2005-03-17 11:13 UTC, Max Bowsher
no flags Details | Diff

Description Ryan Skadberg 2004-11-30 16:13:13 UTC
Description of problem:
Swig 1.3.23 currently in devel is compiled against an older version of
subversion, not the current version that comes with devel

Version-Release number of selected component (if applicable):

Comment 1 Phil Knirsch 2004-12-01 13:28:14 UTC
Good catch. Rebuilt today so it should be linked now against newest
version of subversion.

Read ya, Phil

Comment 2 Ryan Skadberg 2004-12-03 00:09:39 UTC
Turns out I had it backwards.  Subversion is linked against the old swig:

Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package swig.i386 0:1.3.23-1 set to be updated
--> Running transaction check
--> Processing Dependency: libswigpy.so.0 for package: subversion
--> Processing Dependency: libswigpl.so.0 for package: subversion-perl
--> Finished Dependency Resolution
Error: missing dep: libswigpy.so.0 for pkg subversion
Error: missing dep: libswigpl.so.0 for pkg subversion-perl
[root@codewarrior ~]# rpm -e swif

[root@codewarrior ~]# rpm -e swig
error: Failed dependencies:
        libswigpl.so.0 is needed by (installed)
        libswigpy.so.0 is needed by (installed) subversion-1.1.1-4.i386

Comment 3 Ryan Skadberg 2004-12-12 20:49:14 UTC
Changing the title to reflect actual bug.

Comment 4 Joe Orton 2004-12-14 12:31:06 UTC
subversion does not build against the new swig unfortunately :( Some
concerted effort is needed here to port to the new release, or the
python bindings will have to be removed for a while.

Comment 5 Shane Ley 2004-12-26 03:00:55 UTC
That sounds like a good plan for the immediate future, Joe. They can
always be readded when things are working properly again.

Comment 6 Joe Orton 2005-01-11 12:45:42 UTC
The bindings in the Raw Hide Subversion are now disabled.  For FC4
this means doing one of:

- shipping SVN without python/perl bindings
- someone doing all the work to update SVN to the 1.3.23 swig interface
- backing down to an older swig

Comment 7 Max Bowsher 2005-01-16 12:00:41 UTC
I've commented in bug 142970 (component=swig) about the development
turbulence that SWIG has recently passed through with respect to
multi-module bindings, and requested an update to 1.3.24.

Meanwhile, I will try to get the newly-added support for SWIG 1.3.24
in Subversion tested a bit more and backported to a 1.1.x release in
time for FC4.

Comment 8 Joe Orton 2005-01-17 12:32:02 UTC
Thanks a lot, Max!

Comment 9 Joe Orton 2005-02-10 09:26:42 UTC
*** Bug 147647 has been marked as a duplicate of this bug. ***

Comment 10 Max Bowsher 2005-03-17 11:12:18 UTC
Since FC4t1 is out, and Subversion is still slowly moving towards a 1.1.4
release,  I'm attaching here the patch which adds support for swig 1.3.24, and
will be included in 1.1.4 when we eventually get there.

Comment 11 Max Bowsher 2005-03-17 11:13:12 UTC
Created attachment 112082 [details]
Patch adding swig 1.3.24 support to subversion 1.1.x

Comment 12 Joe Orton 2005-03-22 14:44:16 UTC
Thank you very much, Max!  1.1.3-7 in Raw Hide uses the above patch and
re-enables the swig-based bindings.  I've tested the python bindings to work fine.

Note You need to log in before you can comment on or make changes to this bug.