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
