Bug#1060711: python3-wxgtk4.0: Library dependency too lenient

2024-01-22 Thread Matthias Urlichs

On 22.01.24 18:54, Scott Talbert wrote:
I'll try to find a way to tighten wxPython's dependency on be >= the 
wxWidgets it was compiled with.


Thanks, that's all I'm asking for.

--
-- Matthias Urlichs



Bug#1060711: python3-wxgtk4.0: Library dependency too lenient

2024-01-22 Thread Matthias Urlichs

On 17.01.24 15:01, Scott Talbert wrote:

On Wed, 17 Jan 2024, Matthias Urlichs wrote:


On 16.01.24 23:58, Scott Talbert wrote:
Do I understand correctly that you installed the python3-wxgtk4.0 
4.2.1+dfsg-3
binary package from Debian Testing into a Debian 12 system and 
that's how you encountered this error? 


Yes. So? Mix+match from stable+testing is rather common when you're 
developing stuff, and Policy 3.5 doesn't say "umm well that only 
applies for dependencies from the same release".


Sorry, but that's not generally supported, at least for wxWidgets 
related packages.  Sometimes we change compile options and other 
things that change the ABI.



I noticed …

However, perhaps you misunderstood. I'm not asking for "support mix and 
match of wx*-related packages". I'm asking for "support mix+match 
between releases; if and when that doesn't work, please set the 
dependencies so that the user can't install a mix-and-match system in 
the first place".


See also: https://lists.debian.org/debian-devel/2024/01/msg00266.html — 
NB, please disregard my snarky "go away" pseudo-quote there. That was 
not intended to reflect your reply here.


--
-- Matthias Urlichs



Bug#1060711: python3-wxgtk4.0: Library dependency too lenient

2024-01-22 Thread Scott Talbert

On Mon, 22 Jan 2024, Matthias Urlichs wrote:


On 17.01.24 15:01, Scott Talbert wrote:

On Wed, 17 Jan 2024, Matthias Urlichs wrote:


On 16.01.24 23:58, Scott Talbert wrote:
Do I understand correctly that you installed the python3-wxgtk4.0 
4.2.1+dfsg-3
binary package from Debian Testing into a Debian 12 system and that's how 
you encountered this error? 


Yes. So? Mix+match from stable+testing is rather common when you're 
developing stuff, and Policy 3.5 doesn't say "umm well that only applies 
for dependencies from the same release".


Sorry, but that's not generally supported, at least for wxWidgets related 
packages.  Sometimes we change compile options and other things that change 
the ABI.



I noticed …

However, perhaps you misunderstood. I'm not asking for "support mix and match 
of wx*-related packages". I'm asking for "support mix+match between releases; 
if and when that doesn't work, please set the dependencies so that the user 
can't install a mix-and-match system in the first place".


I didn't misunderstand - you're asking for mis+match of wx-related (to 
include wxWidgets and wxPython) packages between releases, which isn't 
supported.  wxPython is a Python wrapper for wxWidgets, so it is by 
necessity tightly coupled with wxWidgets.  I'll try to find a way to 
tighten wxPython's dependency on be >= the wxWidgets it was compiled with.


See also: https://lists.debian.org/debian-devel/2024/01/msg00266.html — NB, 
please disregard my snarky "go away" pseudo-quote there. That was not 
intended to reflect your reply here.


Yes, I saw that.

Scott

Bug#1060711: python3-wxgtk4.0: Library dependency too lenient

2024-01-16 Thread Scott Talbert

On Sat, 13 Jan 2024, Matthias Urlichs wrote:


Package: python3-wxgtk4.0
Version: 4.2.1+dfsg-3
Severity: normal
X-Debbugs-Cc: sm...@smurf.noris.de

Installing the version from Testing says


import wx.core

Traceback (most recent call last):
 File "", line 1, in 
 File "/usr/lib/python3/dist-packages/wx/__init__.py", line 17, in 
   from wx.core import *
 File "/usr/lib/python3/dist-packages/wx/core.py", line 12, in 
   from ._core import *
ImportError: 
/usr/lib/python3/dist-packages/wx/_core.cpython-311-x86_64-linux-gnu.so: 
undefined symbol: _ZN13wxRadioButtonD2Ev, version WXU_3.2




due to its dependency on libwxgtk3.2-1, which apparently needs to be >=
3.2.4 instead of 3.2.2.

Semantic versioning appears to be overrated. :-(


Hello Matthias,

Do I understand correctly that you installed the python3-wxgtk4.0 4.2.1+dfsg-3
binary package from Debian Testing into a Debian 12 system and that's how 
you encountered this error?


Scott



Bug#1060711: python3-wxgtk4.0: Library dependency too lenient

2024-01-13 Thread Matthias Urlichs
Package: python3-wxgtk4.0
Version: 4.2.1+dfsg-3
Severity: normal
X-Debbugs-Cc: sm...@smurf.noris.de

Installing the version from Testing says

>>> import wx.core
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/wx/__init__.py", line 17, in 
from wx.core import *
  File "/usr/lib/python3/dist-packages/wx/core.py", line 12, in 
from ._core import *
ImportError: 
/usr/lib/python3/dist-packages/wx/_core.cpython-311-x86_64-linux-gnu.so: 
undefined symbol: _ZN13wxRadioButtonD2Ev, version WXU_3.2
>>>

due to its dependency on libwxgtk3.2-1, which apparently needs to be >=
3.2.4 instead of 3.2.2.

Semantic versioning appears to be overrated. :-(


-- System Information:
Debian Release: 12.4
  APT prefers stable
  APT policy: (750, 'stable'), (700, 'testing'), (650, 'oldstable'), (600, 
'oldoldstable'), (500, 'stable-security'), (500, 'oldstable-security'), (500, 
'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.1.0-10-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-wxgtk4.0 depends on:
ii  libc6 2.36-9+deb12u3
ii  libgcc-s1 12.2.0-14
ii  libstdc++613.2.0-9
ii  libwxbase3.2-13.2.4+dfsg-1
ii  libwxgtk-gl3.2-1  3.2.4+dfsg-1
ii  libwxgtk3.2-1 3.2.2+dfsg-2
ii  python3   3.11.2-1+b1
ii  python3-numpy 1:1.24.2-1
ii  python3-pil   9.4.0-1.1+b1
ii  python3-six   1.16.0-4

python3-wxgtk4.0 recommends no packages.

Versions of packages python3-wxgtk4.0 suggests:
pn  wx3.2-doc  

-- debconf-show failed