1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#1099554: python3.13-{gdbm,tk} do not have any python dependencies

    From Adrian Bunk@21:1/5 to All on Wed Mar 5 00:00:02 2025
    Package: python3.13-gdbm
    Version: 3.13.2-1
    Severity: serious
    Control: affects -1 python3.13-tk

    Package: python3.13-gdbm
    Depends: libc6 (>= 2.2.5), libgdbm6t64 (>= 1.16)

    Package: python3.13-tk
    Depends: libc6 (>= 2.2.5), libtcl8.6 (>= 8.6.0), libtk8.6 (>= 8.6.0)


    Adding
    Depends: python3.13
    should be correct, so that removing an old libpython3.*-minimal
    will also remove them.


    This might also be the root cause of the problem workarounded with
    * python3.x-tk: Make byte-compilation depend on the availability of
    the interpreter.


    (Severity of this bug might be debatable, but it's trivial to fix.)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Matthias Klose@21:1/5 to Adrian Bunk on Thu Mar 6 09:10:03 2025
    Control: severity -1 important

    On 04.03.25 23:48, Adrian Bunk wrote:
    Package: python3.13-gdbm
    Version: 3.13.2-1
    Severity: serious
    Control: affects -1 python3.13-tk

    Package: python3.13-gdbm
    Depends: libc6 (>= 2.2.5), libgdbm6t64 (>= 1.16)

    Package: python3.13-tk
    Depends: libc6 (>= 2.2.5), libtcl8.6 (>= 8.6.0), libtk8.6 (>= 8.6.0)

    Adding
    Depends: python3.13
    should be correct, so that removing an old libpython3.*-minimal
    will also remove them.


    This might also be the root cause of the problem workarounded with
    * python3.x-tk: Make byte-compilation depend on the availability of
    the interpreter.

    No, the root cause is with the proposed solution, you have hard coded dependencies on all python3.x versions, forcing installation of these.
    Which is not what I would like to have.

    You should not directly depend on those packages, but instead using the python3-gdbm and python3-tk packages as dependencies.

    If people insist on having this dependency, then we'll have to build the python3-{gdbm,tk} packages from a separate source again, and removing
    the python3.XY-{gdbm,tk} packages.

    Matthias

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stefano Rivera@21:1/5 to All on Thu Mar 6 15:40:01 2025
    Hi Matthias (2025.03.06_03:58:25_-0400)
    No, the root cause is with the proposed solution, you have hard coded >dependencies on all python3.x versions, forcing installation of these.
    Which is not what I would like to have.

    Let me expand on this a little:

    tk and gdbm are stdlib modules that we make optional in Debian, shipping
    them in separate binary packages.

    Packages that need gdbm or tk depend on python3-gdbm and python3-tk, as
    if they were 3rd party python libraries.

    python3-gdbm (for example) depends on "python3.12-gdbm, python3.13-gdbm" (before the 3.13-only transition).
    This gives the same result as would be expected for a 3rd party python
    library: the module is available for all supported python3 versions. It
    just happens to have been achieved via binary packgages built in the
    python3.12 and python3.13 source packages.

    If we added the dependencies you propose, then installing python3-gdbm
    would necessarily install all supported python versions. This isn't
    desired.

    Stefano

    --
    Stefano Rivera
    http://tumbleweed.org.za/
    +1 415 683 3272

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)