Re: pybuild and setuptools_scm
Hi Mathias (2024.07.12_06:47:39_+) > I had a similar problem when setuptools_scm kicked in during the build process > and produced versions different from the orig tarball. Packaging is in git and > tarballs are imported from PyPI. > > I disabled the automatic versioning with > > https://salsa.debian.org/tryton-team/python-csb43/-/commit/e8788e09818948231a48cc1472a5f5b65fcc > > Could you confirm this is the right approach or is there a more elegant way? That approach doesn't look great. Instead of that patch, just Build-Depend on python3-setuptools-cm, so that it can do its magic. In my testing it works just fine on your package. Oh, you're also missing pytest, so the package tests are failing. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1076421: RM: pydevd -- ROM; No longer needed for debugpy
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: pyd...@packages.debian.org, debian-python@lists.debian.org Control: affects -1 + src:pydevd pydevd was packaged purely to avoid having a vendored version of the package embedded in debugpy. debugpy has now diverged from the upstream pydevd in an incompatible way, and there is no prospect of the two merging again (see https://github.com/microsoft/debugpy/discussions/1611 for more details). I have therefore reverted to using the vendored version in debugpy. This renders the pydevd package unnecessary. There are also no other reverse dependencies in unstable.
Bug#1076422: RM: python-bytecode -- ROM; No longer needed for debugpy
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: python-bytec...@packages.debian.org, debian-python@lists.debian.org Control: affects -1 + src:python-bytecode python-bytecode was packaged purely to avoid having a vendored version embedded in pydevd. In turn, pydevd was packaged purely to avoid having a vendored version of the package embedded in debugpy. debugpy has now diverged from the upstream pydevd in an incompatible way, and there is no prospect of the two merging again (see https://github.com/microsoft/debugpy/discussions/1611 for more details). I have therefore reverted to using the vendored version in debugpy. This renders both the pydevd and python-bytecode packages unnecessary. I have already requested the removal of pydevd (#1076421), and there are no other reverse dependencies in unstable besides this.
