1.14.2 is nearly 4y old. Since then, we have in Cauldron 1.14.3 (18m), 1.14.5 (13m).
Unsure whether this is a global or Python bug, notifying both.

Assignee: bugsquad => pkg-bugs
CC: (none) => python

I don't think it's a problem of age. BTW it's what is currently available on mga9 both for subversion, swig and python. So should be easily reproduceable by anybody just installing python3-svn.

It *looks* like a dyssynchronization with swig used to build the so modules.
That's why I try to rebuild to see whether it could help, but didn't.

(In reply to Bruno Cornec from comment #0)
> Description of problem:
> 
> The python-svn package is unusable on Mageia 9:
> 
> # python
> Python 3.10.18 (main, Dec  8 2025, 12:59:32) [GCC 12.3.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from svn import core
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
>   File "/usr/lib/python3.10/site-packages/svn/core.py", line 26, in <module>
>     from libsvn.core import *
>   File "/usr/lib64/python3.10/site-packages/libsvn/core.py", line 27, in
> <module>
>     from . import _core
> ImportError: /usr/lib64/python3.10/site-packages/libsvn/_core.so: undefined
> symbol: SWIG_InstallConstants
> 
Perhaps a missing include or equivalent in code that generates _core.so

Created attachment 15377 [details]
Patch for subversion-1.14.5 in cauldron

I find this patch in opensuse, I'll love to test my self but can't build with mock in this moment

(In reply to katnatek from comment #4)
> Created attachment 15377 [details]
> Patch for subversion-1.14.5 in cauldron
> 
> I find this patch in opensuse, I'll love to test my self but can't build
> with mock in this moment
In cauldron work, I'll see if I can import the patch in mageia 9

Nope, trying other patch, this from fedora

I no yet find a solution, but in the build process I see this

grep SWIG_InstallConstants RPMS/build.log 
subversion/bindings/swig/python/svn_client.c:40344:3: warning: implicit declaration of function 'SWIG_InstallConstants'; did you mean 'SWIG_Python_InstallConstants'? [-Wimplicit-function-declaration]
40344 |   SWIG_InstallConstants(d,swig_const_table);
subversion/bindings/swig/python/core.c:40077:3: warning: implicit declaration of function 'SWIG_InstallConstants'; did you mean 'SWIG_Python_InstallConstants'? [-Wimplicit-function-declaration]
40077 |   SWIG_InstallConstants(d,swig_const_table);
subversion/bindings/swig/python/svn_delta.c:11073:3: warning: implicit declaration of function 'SWIG_InstallConstants'; did you mean 'SWIG_Python_InstallConstants'? [-Wimplicit-function-declaration]
11073 |   SWIG_InstallConstants(d,swig_const_table);
subversion/bindings/swig/python/svn_diff.c:12353:3: warning: implicit declaration of function 'SWIG_InstallConstants'; did you mean 'SWIG_Python_InstallConstants'? [-Wimplicit-function-declaration]
12353 |   SWIG_InstallConstants(d,swig_const_table);
subversion/bindings/swig/python/svn_fs.c:17488:3: warning: implicit declaration of function 'SWIG_InstallConstants'; did you mean 'SWIG_Python_InstallConstants'? [-Wimplicit-function-declaration]
17488 |   SWIG_InstallConstants(d,swig_const_table);
subversion/bindings/swig/python/svn_ra.c:19836:3: warning: implicit declaration of function 'SWIG_InstallConstants'; did you mean 'SWIG_Python_InstallConstants'? [-Wimplicit-function-declaration]
19836 |   SWIG_InstallConstants(d,swig_const_table);
subversion/bindings/swig/python/svn_repos.c:24148:3: warning: implicit declaration of function 'SWIG_InstallConstants'; did you mean 'SWIG_Python_InstallConstants'? [-Wimplicit-function-declaration]
24148 |   SWIG_InstallConstants(d,swig_const_table);
subversion/bindings/swig/python/svn_wc.c:43304:3: warning: implicit declaration of function 'SWIG_InstallConstants'; did you mean 'SWIG_Python_InstallConstants'? [-Wimplicit-function-declaration]
43304 |   SWIG_InstallConstants(d,swig_const_table);

Yes I saz that as well. But as that sounded unrelated, didn't investigate.

@katnatek Have you tried to build the cauldron pkg on a mga9 system? to see if it come from subversion itself or swig or finally from our python3 pkg.

That is strange is in swig pkg there is a define in pyrun.swg file:

#define SWIG_InstallConstants(d, constants)           SWIG_Python_InstallConstants(d, constants)

like in subversion itself in "subversion/bindings/swig/python/" some files contains this define.

#define SWIG_InstallConstants(d, constants)           SWIG_Python_InstallConstants(d, constants)

CC: (none) => geiger.david68210

We can tried to patch the 8 files with:

sed -i 's|SWIG_InstallConstants(d,swig_const_table);|SWIG_Python_InstallConstants(d,swig_const_table);|'

(In reply to David GEIGER from comment #9)
> @katnatek Have you tried to build the cauldron pkg on a mga9 system? to see
> if it come from subversion itself or swig or finally from our python3 pkg.
> 
That will be the last resource

> That is strange is in swig pkg there is a define in pyrun.swg file:
> 
> #define SWIG_InstallConstants(d, constants)          
> SWIG_Python_InstallConstants(d, constants)
> 
> like in subversion itself in "subversion/bindings/swig/python/" some files
> contains this define.
> 
> #define SWIG_InstallConstants(d, constants)          
> SWIG_Python_InstallConstants(d, constants)
You find the same that I, I'm trying with the change you suggest, was in my todo for today

(In reply to David GEIGER from comment #10)
> We can tried to patch the 8 files with:
> 
> sed -i
> 's|SWIG_InstallConstants(d,swig_const_table);|SWIG_Python_InstallConstants(d,
> swig_const_table);|'

Did not work, the build show exactly the same, I confirm tha change is made, will test with the version in cauldron

I build 1.14.3 from cauldron revision and now the python code works,
is there a test that I should do before send to build?

RPMS:
apache-mod_dav_svn-1.14.3-1.1.mga9
lib64svn-gnome-keyring0-1.14.3-1.1.mga9
lib64svn-kwallet0-1.14.3-1.1.mga9
lib64svn0-1.14.3-1.1.mga9
lib64svnjavahl1-1.14.3-1.1.mga9
perl-SVN-1.14.3-1.1.mga9
python3-svn-1.14.3-1.1.mga9
subversion-1.14.3-1.1.mga9
subversion-devel-1.14.3-1.1.mga9
subversion-doc-1.14.3-1.1.mga9
subversion-server-1.14.3-1.1.mga9
subversion-tools-1.14.3-1.1.mga9
svn-javahl-1.14.3-1.1.mga9

SRPM:subversion-1.14.3-1.1.mga9

Assignee: pkg-bugs => qa-bugs
Keywords: (none) => advisory

FYI, I couldn't build 1-14-5 for mageia 9, if is necesary I'll build again and provide build log

MGA9-64 server Plasma Wayland on Compaq H000SB
No installation issues.
Followed procedure as in bug 33838 Comment 4 after adding the EDITOR env to this user.
I will not copy all the comands, but after making sure httpd is running, I could connect to http://localhost/svn/repos/
So good to go

Flags: (none) => test_passed_mga9_64+
CC: (none) => herman.viaene
Whiteboard: (none) => MGA9-64-OK

Before the update

python
Python 3.10.18 (main, Dec  8 2025, 12:59:32) [GCC 12.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from svn import core
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.10/site-packages/svn/core.py", line 26, in <module>
    from libsvn.core import *
  File "/usr/lib64/python3.10/site-packages/libsvn/core.py", line 27, in <module>
    from . import _core
ImportError: /usr/lib64/python3.10/site-packages/libsvn/_core.so: undefined symbol: SWIG_InstallConstants


installing python3-svn-1.14.3-1.1.mga9.x86_64.rpm lib64svn0-1.14.3-1.1.mga9.x86_64.rpm subversion-1.14.3-1.1.mga9.x86_64.rpm from //home/katnatek/qa-testing/x86_64
Preparing...                     ###################################################################################################
      1/3: lib64svn0             ###################################################################################################
      2/3: python3-svn           ###################################################################################################
      3/3: subversion            ###################################################################################################
      1/3: removing subversion-2:1.14.2-2.1.mga9.x86_64
                                 ###################################################################################################
      2/3: removing python3-svn-2:1.14.2-2.1.mga9.x86_64
                                 ###################################################################################################
      3/3: removing lib64svn0-2:1.14.2-2.1.mga9.x86_64
                                 ###################################################################################################

After

python
Python 3.10.18 (main, Dec  8 2025, 12:59:32) [GCC 12.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from svn import core
>>> 


I can svn up for advisories
mgarepo co foo

I not have anything to send but with Herman test looks good

Bruno can you confirm this works for you?

I used the packages updated in comment 17 to send advisories and changes to packages, looks good for me

CC: j.alberto.vc => andrewsfarm

I can confirm that it fixed the original issue, as well as the capacity for trac to show subverion repositories now.

For me good to be validated by QA.

Status: NEW => ASSIGNED

Validating.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2026-0009.html

Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED