Bug#1104147: setup-testbed doesn't configure qemu console unless it detects serial ports

Hi Simon (2025.04.26_18:43:26_+) Sorry, no. Because of the Rube Goldberg machine that autopkgtest-virt-qemu currently uses to invoke arbitrary commands on the testbed, it needs /usr/bin/python3 before it can run apt. It only needs python3-minimal and not full python3, I think. Yeah, I can

Bug#1104147: setup-testbed doesn't configure qemu console unless it detects serial ports

Hi Simon (2025.04.26_09:12:53_+) 3. Have a command line argument to install them? Or an environment variable, perhaps? setup-testbed has historically not taken command-line arguments except for the sysroot to act on, and adding a proper command-line parser to it doesn't seem hugely appea

Bug#1103652: broken by ansible 12

Hi Marco (2025.04.20_22:42:38_+) Still broken, now a trivial playbook fails with: I can see why the code is broken, but without reproducing it, I don't know if I've fixed it. Can you provide a minimal trival playbook that triggers this? Stefano -- Stefano Rivera http://tumbleweed.org

Bug#1103044: mat2: unsatisfiable dependency on python2

Hi Dmitry (2025.04.14_13:21:17_+) What do you think about patching setuptools to generate #!python3 instead of #!python? This should make dh_python3 do the right thing, and should not cause much difference on systems other than Debian. That is tempting. I think the future-looking option he

Bug#1101532: systemd: unable to migrate to Testing because of removed packages

Hi Josh (2025.04.02_19:27:34_+) I think it's important to distinguish between "communication problem" and "obstruction". "obstruction" is a problem that goes to DAM; "communication problem" can potentially look like that, but once it's resolved as *not* being that, it should ideally be rapidl

Bug#1081553: transition: abseil

Hi Emilio (2025.03.10_09:47:59_+) I see some failures that didn't seem to be listed in the initial report. E.g. grpc grpc was noted before, but failed for new reasons. Filed #1100044 with an NMU, it looks like GCS will incorporate it into a maintainer upload soon. and mozc kenhys has

Bug#1078614: Downgrading severity of "extrepo-data: will FTBFS during trixie support period"

Hi Thomas (2025.03.10_12:58:17_+) Stefano, I believe you wrote more to me on IRC, but forgot what it was. Please write here if you remember your suggestion. I think you missed it at the end of my message: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078614#14 That's due to a hardcode

Bug#1099545: hugin-tools: hugin's Python3.12 cache files are not cleared on Python3.13 upgrades

Hi Alexandre (2025.03.10_10:32:28_+) Maybe can Stefano answer help you. Greetings https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099543#15 If you install modules to a private path like that, you should install an rtupdate script in /usr/share/python3/runtime.d/ that calls py3clean and

Bug#1099543: dh-debputy: after Python3.13 becomes standard, a lot of .../__pycache__/*.cpython-312.pyc files are left behind

Hi Niels (2025.03.05_15:29:40_+) I've notive that the Python3.12 cache files are not properly cleared on Python upgraded. root@antec:~# cruft | grep debputy /usr/share/debputy/debputy/disabled-plugins/__pycache__/lua.cpython-312.pyc [...] Stefano, can you help me with what I am ge

Bug#1094277: transition: python3.13-only

Hi Emilio (2025.02.24_22:18:26_+) Uploaded 3.13.2-1, thanks. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1096194: python3-cffi: bump priority to Depends: python3-dev

Hi Drew (2025.02.17_14:31:48_+) > > Most do not need python3-dev at runtime. My assumption has been that all > > the ones that are appropriate for use in the Debian archive fit that. > > Fair enough. I had meant to ask if there were other ways of using cffi. > > In that case Suggests is proba

Bug#1096194: python3-cffi: bumpy priority to Depends: python3-dev

Hi Drew (2025.02.17_14:18:25_+) > Does it need to be building cffi extensions at runtime, can't they be > built during the package build? Note that regular users can't write to > /usr/lib/ so building things at runtime is non-trivial to do correctly. Looking at this more, this is python3-dolfi

Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap

Hi Bastian (2025.02.04_14:05:07_+) > > > Provides: linux-libc-dev-amd64, linux-libc-dev-arm64, ... > > We have two proposed provides schemes here, can we select one and add > > it? > > Something like simple providers is the easiest to do. So, by implementing this Provides scheme, Helmut's cros

Bug#1094278: Avoid explicit Python version dependencies

Hi Aurélien (2025.01.26_20:02:16_+) > That’s not correct for the version you’ve mentioned in the bug report. > kdevelop-python 24.12.1-1 has : > > Build-Depends: debhelper-compat (= 13), dh-sequence-kf6, cmake (>= 3.19~), > extra-cmake-modules (>= 6.0.0~), gettext, kdevelop-dev (>= 4:24.12~),

Bug#1094277: transition: python3.13-only

Hi Debian (2025.01.26_17:52:52_+) > Package: python-netfilterqueue > Package: python-picologging Uploaded these two, filed (blocking) bugs for the rest. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1086087: closed by Drew Parsons (Re: Bug#1086087 FTBFS with arch: all on arm64: Imported target "MPI::MPI_Fortran" includes non-existent path "/usr/lib/x86_64-linux-gnu/fortr

Hi Debian (2024.12.06_13:42:02_+) > openmpi is now updated to OpenMPI 5, > and adios2 is now building successfully again on arm64. > So closing this bug now. The bug wasn't precisely that. It was about the package not building arch:indep parts on non-amd64. They seem to assume amd64. That's n

Bug#1084157: renewed python-sigstore packaging work

Hi Simon (2024.12.05_22:48:05_+) > I'd appreciate help and collaborators on this! Feel free to add me as an uploader. I think the Python Team would make sense for it. If you're not a member, https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#joining-the-team Ste

Bug#1088676: dh-python: pyproject plugin: unpack_wheel improvement

Hi Hilko (2024.11.29_22:43:04_+) > Unfortunately, this does not work in my case. pybuild installs qto > packages python3-ndiff and python3-zenmap, respectively – with no > obvious way to override the package names. Turns out it can be overridden, I had to dig about to figure out how all of thi

Bug#1086088: adios2 FTBFS with Python 3.13

Hi pini (2024.11.28_17:58:24_+) > Here is an improved patch proposal. Much better, thanks. Committed that. I had to do some more tweaks, but the package now builds and passes autopkgtests. 1. h5vol was never installed into debian/tmp, so dh_install failed. Reverting the h5vol changes was r

Bug#1086088: adios2 FTBFS with Python 3.13

Hi pini (2024.11.19_21:37:51_+) > I've committed it to git. But I'll team-upload it without the h5vol > part, as I also have a low confidence in it. No, I spoke too soon. Autopkgtest fails: The 3.13 library seems to have been built as if it was for 3.12. I'll look deeper tomorrow. Stefano --

Bug#1086088: adios2 FTBFS with Python 3.13

Hi pini (2024.11.17_14:19:37_+) > >ninja: error: build.ninja:5098: multiple rules generate > > lib/python3/dist-packages/adios2/bindings/adios2_bindings_serial.cpython-312-aarch64-linux-gnu.so > > Here is a patch proposal. Please review it as I'm not sure about the h5vol > part. You may

Bug#1082219: python-globus-sdk FTBFS with Python 3.13

Hi Étienne (2024.10.22_22:12:19_+) > python3.12 tests ran fine. Backtraces suggests I might have > been missing a necessary rebuild of python-cryptography, so > probably unrelated and already fine on your testbed, but you may > want to double check, just in case. Yes, exactly. Confirmed that

Bug#1081694: dipy python3.13

Hi Michael (2024.10.14_12:53:01_+) > Where can I get a python3-numpy ~= 1.26.4 that supports Python 3.13 > for local testing? I'm afraid the testing I've been doing on debusine.debian.net was on arm64, so probably not what you're looking for. You can build yourself one using the python3-all f

Bug#1082267: python-scitrack FTBFS with Python 3.13

Hi Étienne (2024.10.09_20:35:12_+) > I consider closing this issue, even though I didn't manage to > make all tests pass right now. The current numpy versions in > experimental do not look compatible with python3.13 at t time, > and this is causing a number of other tests to fail with failure

Bug#1080668: Missing Build-Depends on python3-setuptools

Hi Petter (2024.10.09_07:45:10_+) > Unfortunately, the change in src/configure.ac, where > > python3 -c 'import distutils.sysconfig; > print(distutils.sysconfig.get_python_lib())' > > was replaced with > > python3 -c 'import sysconfig; print(sysconfig.get_path("platlib"))' > > changes

Bug#1081342: FTBFS: gpg.errors.GPGMEError: gpgme_op_encrypt_sign: GnuPG: No agent running

Hi Daniel (2024.10.08_19:02:59_+) > I added gpg-agent to the Build-Depends and impass seems to build without > error on the buildd network Yep, it works for unshare in debusine, now. Thanks! Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1081660: FTBFS with Python 3.13

Hi Emmanuel (2024.10.04_22:29:34_+) > I could note in the build in debusine that it use pybind11 2.13.5, but > now there's a new version 2.13.6. Could you please re-run the build to > see if at least if the error is reproduced? Retried: https://debusine.debian.net/artifact/829117/ I see: E

Bug#1080550: closed by Mattias Ellert (Bug not reproducible)

Hi 1080550 (2024.10.04_11:38:23_+) > Ah, yes, reviewing the build log, the issue was installability of a > Build-Depend at the time. It shouldn't have got caught-up in the MBF. Ah, it was one I'd already identified as a false-positive and closed: https://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#1080550: closed by Mattias Ellert (Bug not reproducible)

Hi Mattias, > I can not reproduce this bug. Ah, yes, reviewing the build log, the issue was installability of a Build-Depend at the time. It shouldn't have got caught-up in the MBF. Sorry. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1065416: Bastian's offer in #1065416

Hi Ben (2024.09.11_22:38:24_+) > > > While potential solutions to this bug are being discussed, would you > > > please consider removing the Provides from linux-libc-dev? > > > > I am open to doing so. > [...] > > I raised this at today's team meeting and it was agreed to do this; see >

Bug#1079496: dh-python: -X option does not exclude file from renaming

Hi Drew (2024.08.24_14:56:07_+) > > I pushed a git branch with a patch that adds this feature > > (exclude_ext_rename), as I've already written it. But I don't think it's > > a feature we need. So I don't intend to merge it. > > Fair enough for scipy. Across the broader python ecosystem it mi

Bug#1079496: dh-python: -X option does not exclude file from renaming

Hi Drew (2024.08.24_11:39:04_+) > Currently -X only applies to byte-compilation. The only way to do what > you want is --no-ext-rename, but that's all or nothing. > > I think we can extend -X to apply to C extensions too... Thinking about that some more, I actually don't see any point in this

Bug#1065416: requesting input on recent posts to #1065416

Hi Bastian (2024.08.16_17:53:17_+) > > The Technical Committee is hoping that this will be resolved without > > requiring us to make a decision. If the take-over offer resolves the > > issue, then we will probably vote to take no further action. > > Well, take-over removes the need for talk.

Bug#1070659: transition: re2

Hi Emilio (2024.05.22_07:03:30_+) > Go ahead. Uploaded, built, and installed everywhere. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1070158: bullseye-pu: package distro-info-data/0.51+deb11u6

Hi Jonathan (2024.05.12_10:56:13_+) > Control: tag -1 confirmed > > On Tue, Apr 30, 2024 at 08:58:52PM -0400, Stefano Rivera wrote: > > 1. bullseye and bookworm LTS & ELTS. > > 2. Ubuntu 24.10 Oracular Oriole > > Please go ahead, but if you'd prefer to wait until the final date for > bullseye

Bug#1070659: transition: re2

Hi Adrian (2024.05.07_17:39:58_+) > Could this be solved through Provides, so that it could be handled > with binNMUs during abseil transitions? Implemented in 20240501-2. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1070659: transition: re2

Hi Adrian (2024.05.07_17:39:58_+) > Could this be solved through Provides, so that it could be handled > with binNMUs during abseil transitions? > > Example: > > Package: libboost-regex1.74.0 > Depends: ..., libicu72 (>= 72.1~rc-1~),... > Provides: libboost-regex1.74.0-icu72 > > $ cat /var/

Bug#1064213: incus-agent: Incus Agent never starts due to ConditionPathExists

Hi Mathias (2024.02.18_19:43:13_+) > I suspect you're seeing this on the host system running Incus? If so, > that's expected behavior. Nope, in a VM inside Incus. > Incus' default mode of operation when launching a VM is to > dynamically inject the `incus-agent` binary into the VM's envir

Bug#1061388: sbuild doesn't support autotpkgest-virt-incus: Error: mkdir /sbuild-nonexistent: permission denied

Hi Debian (2024.01.23_13:41:47_+) > D: Running command: incus exec autopkgtest-lxd-ltsezo -- strace -f -A -o > /tmp/strace.log env LC_ALL=C.UTF-8 LANG=en_US.UTF-8 HOME=/sbuild-nonexistent > DEB_BUILD_OPTIONS=parallel=16 SHELL=/bin/sh sh -c cd / && exec "$@" exec perl > -e Err there was some

Bug#1060027: RM: setuptools-scm-git-archive -- ROM; obsoleted by setuptools-scm 7

Hi julien.puydt (2024.01.05_08:05:59_+) > I've been following the situation since quite long, but it's not ready > to go yet as far as my notes say: > > - for cheroot, we need to wait for the next upstream version: > https://github.com/cherrypy/cheroot/issues/515 > > - for matplotlib, the nex

Bug#1059881: autopkgtest: Automatically parsing the summary file in error conditions

Hi Paul (2024.01.03_06:44:59_+) > $(man autopkgtest) has a section on OUTPUT FORMAT, isn't that what you're > after? Oh, one more thing: The code looks like it can output "erroneous package:" but this isn't documented. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1056828: Severity / marking of "uses cython3-legacy" bugs

Hi Rebecca (2024.01.03_21:27:49_+) > pandas and statsmodels are currently using cython3-legacy. I left their > cython 3.0 bugs open when I made this change, as I do want to actually > switch them to cython 3.x at some point. > > These bugs have now been raised to RC. Is this an intentional a

Bug#1059881: autopkgtest: Automatically parsing the summary file in error conditions

Hi Paul (2024.01.03_06:44:59_+) > $(man autopkgtest) has a section on OUTPUT FORMAT, isn't that what you're > after? Aha. I'd missed that. OK, so I can expect just blame: or badpkg:, not arbitrary other strings. That's helpful. And we probably need to figure out how to handle SKIP *. Stefan

Bug#1059444: LXD: cython3 autopkgtest hangs forever due to stall in copyup

lxd 323739 root 298w FIFO 0,14 0t0 24974400 pipe I assume lxd is proxying the data to and from lxc exec: $ ps waux | grep 'lxc exec' stefanor 125535 0.2 0.1 1540868 32312 pts/13 Sl+ 10:49 0:09 /snap/lxd/24918/bin/lxc exec autopkgtest-lxd-jvgqvo -- env -i bash -

Bug#1059444: LXD: cython3 autopkgtest hangs forever due to stall in copyup

Hi Debian (2023.12.25_17:20:25_+) > This reproduces reliably, but I haven't got to the bottom of it. It > looks like a stalled pipeline somewhere. Caught it again, the tee from lib/in-testbed/wrapper.sh is trying to write to stdout, but buffer is full. And autopkgtest isn't reading the buffer

Bug#1058096: Processed: Bug#1058096 marked as pending in xonsh

Hi Debian (2023.12.17_17:48:05_+) Whoops, that was a typo, I was meaning to close 1057596. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1025218: marked as pending in python-urllib3

Hi Daniele (2023.11.09_23:31:30_+) > Unfortunately tests just hangs somehow (I can reproduce on my chroot, but > you can also see the pipeline on salsa). There's one particularly slow test that is causing upstream issues at the moment too. Cherry-picked this PR into a patch: https://github.com

Bug#1055022: bullseye-pu: package distro-info-data/0.51+deb11u5, distro-info/1.0+deb11u1

Hi Adam (2023.10.29_19:17:58_+) > It looks like you uploaded a binary-only build of distro-info-data, > rather than including a source build: Indeed, oops. Kill that, I'll do a source-only upload. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1041692: python3-mesonpy: could the build be verbose by default

Hi Simon (2023.10.14_10:54:21_+) > > Another way to achieve this in packages like python-fabio and pyfai > > would be to bypass pyproject and meson-python to run Meson directly, > > either manually per-package via "export PYBUILD_SYSTEM=meson", or maybe > > automatically in pybuild when build-b

Bug#1053408: qt6-webengine: FTBFS with re2 >= 20230601 (which requires abseil)

Hi Patrick (2023.10.07_12:06:27_+) > qt6-webengine based on chromium 116 or later will not hit unstable > before June 2024 or so and I feel like trying to patch the bundled > version of chromium will be going down the rabbit hole. > > However, I can switch to the bundled version of re2 until

Bug#1047929: irclog2html: Fails to build source after successful build

Hi Lucas (2023.09.04_18:35:47_+) > This was most likely fixed thanks to that change in dh-python > 6.20230825: >* Remove *.egg-info directories in clean step, as part of Debian's wider > effort to improve clean targets. Thanks Stuart Prescott for the patch. > > So I'm closing this bug

Bug#1028157: cython update

Hi Yaroslav (2023.08.11_13:34:59_+) > On Fri, 11 Aug 2023, Drew Parsons wrote: > > ... > > > > But in any case PR18242 looks simple enough to backport to scipy 1.10.1 . > > Would need to be tested first. Get cython3 into experimental so we can > > check. > > Dear Stefano, would you have time

Bug#1043301: dh-python should declare Depends python3 >= 3.11

Hi Tianyu (2023.08.09_03:28:06_+) > I believe dh-python should either declare dependency on python3 >= 3.11, or > install python3-tomli on python3 << 3.11 and use tomli as fallback when > tomllib can't be imported. That's fair enough. Stefano -- Stefano Rivera http://tumbleweed.org.za/

Bug#1041711: libmovit8: nageru fails to compile a shader on startup

Hi Steinar (2023.07.22_14:49:30_+) > This is very weird. It seems there's a truncation somewhere: Yeah, exactly. > I suppose there's nothing odd locale-wise or similar about your setup? Nope, same error with LC_ALL=C. Nicolas next to me (also on an AMD system running Debian unstable) hits ex

Bug#1041538: dh-python: Unhelpful inclusion of optional packages in Depends

Control: reassign -1 poetry Control: affects -1 dh-python > I'd call this an upstream poetry issue. > > It shouldn't declare optional dependencies as required. It should rather > create an extra to encapsulate any optional dependencies that aren't > part of a defined extra. Reassigning the bug.

Bug#1035635: tox: Upgrading to tox 4

Hi Sebastian (2023.07.11_20:06:16_+) > Except to speed up removal of some of the reverse dependencies, do you > need anything from our side? It doesn't look like rebuilds are required. Nope, beyond that it was just an FYI. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3

Bug#1028436: transition: re2

Hi Sebastian (2023.06.13_21:42:46_+) > Please go ahead with the upload to unstable. Uploaded, thanks! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1037078: closed by Paul Gevers (closing still open unblock requests)

Control: reopen -1 Control: user release.debian@packages.debian.org Control: usertag -1 pu Control: retitle -1 bookworm-pu: package dh-python/5.20230130+deb12u1 Control: tag -1 bookworm > The unblock requests that I'm closing in this message all came in after the > deadline of 2023-05-28 12:00

Bug#1035645: closed by Debian FTP Masters (reply to Holger Levsen ) (Bug#1035645: fixed in reprotest 0.7.24)

Control: reopen -1 Control: notfixed -1 reprotest/0.7.24 I'm afraid one more tweak is required to resolve the issue. The change I made in dh-python to support tox 4 means you'll need to add a Build-Depends on python3-wheel, to build the wheel that we give to tox to test. Stefano -- Stefano Rive

Bug#1035645: reprotest: FTBFS with tox 4

Hi Vagrant (2023.05.09_23:13:30_+) > > + *_proxy,TERM Ah, you spotted the typo, good :) Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1035645: reprotest: FTBFS with tox 4

Hi Vagrant (2023.05.07_00:01:34_+) > This patch is trivial and fixes building with tox 4, but unfortunately > breaks building with tox 3: How about this, works on both, by using the multiline syntax: diff --git a/tox.ini b/tox.ini index 1c3488d..579e4bd 100644 --- a/tox.ini +++ b/tox.ini @@ -

Bug#1019293: python3-pip: installs setup_requires into /tmp/.../overlay/local/bin but then adds /tmp/.../overlay/bin to PATH

Hi Simon (2023.01.20_13:54:00_+) Actually, with a tweak, it can work. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1019293: python3-pip: installs setup_requires into /tmp/.../overlay/local/bin but then adds /tmp/.../overlay/bin to PATH

Hi Simon (2023.01.20_13:54:00_+) > > That will use the posix_local scheme by default on Debian, which won't do > > what pip expects, when it assumes the posix_prefix scheme to be used. > > Probably selecting having pip explicitly select posix_prefix when > > --prefix is supplied would make sens

Bug#993589: distro-info-data: Please consider shipping default mirror URLs per distro

Hi Johannes (2023.01.16_21:28:53_+) > I like the idea of distro-info & distro-info-data taking on more > responsibility, but it probably means we need to redesign the data > schema. I'm thinking YAML/toml data. > > That in turn means rewriting the distro-info libraries (at least to > provide a

Bug#1027213: gavodachs: autopkgtest fail with numpy/1.24.1

Hi Markus (2023.01.09_10:45:30_+) > I'd be fine with the patch, as it won't actually break anything that > hasn't been broken already, but I have already prepared a fix > in , waiting > for an upload (delayed because of holidays, I suspect).

Bug#1026312: Setuptools 65.5.0-1.1 breaks installing Python modules/extensions via meson

Hi Simon (2022.12.20_18:59:12_+) > This appears to be a behaviour change in the build system, and I think it's > triggered by the new setuptools. It is. The Debian detection in meson doesn't support the newer distutils that dynamically sources available schema from the sysconfig module. I'm wo

Bug#1024766: python-cassandra-driver: FTBFS on python3.11-dbg on powerpc and ppc64

Control: clone -1 -2 Control: reassign -2 python3-cffi-backend Control: found -2 python3-cffi-backend/1.15.1-3+b1 > I simplified that down even further to this in python-cffi: > > from cffi import FFI > ffi = FFI() > p = ffi.new("int *", 123) > ffi.gc(p, lambda x: None) Let's track this separate

Bug#1022526: python-ssdeep: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command

Hi Bo (2022.11.19_05:05:19_+) > One question: > If I put the packahe under Debian Python team, should to change > maintainer to DPT from QA team? Yes. And if it's in the Python Team it needs a human maintainer/uploader too. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1024271: python-cffi: FTBFS on hppa - c/test_c.py test faults and drops core

Hi John (2022.11.17_23:22:15_+) > If the python-cffi test checks the passing of structs larger than 8 > bytes, then maybe there is a problem: From a quick look at the test suite, there are a lot of tests that do that. Also, FWIW: before this test suite crash, we had a different test failure o

Bug#1024010: compreffor FTBFS with Python 3.11 as supported version

Hi Nilesh (2022.11.16_14:22:09_+) > This seems to stem from moving a header file in py3.11 > > $ apt-file search longintrepr.h > [...] > libpython3.10-dev: /usr/include/python3.10/longintrepr.h > libpython3.11-dev: /usr/include/python3.11/cpython/longintrepr.h > > Was this really intended? Y

Bug#1022449: python-maxminddb: diff for NMU version 2.0.3-1.1

Hi Faidon (2022.11.11_22:25:52_+) > I don't mind having an NMU, though, whether targeted or for the new > upstream version itself. Sure, happy to NMU a new upstream version, too. I'll 0-day NMU that. I'm afraid this specific bug isn't fixed there, yet, so we still need to carry a patch. But i

Bug#1023030: pysha3: Affected by CVE-2022-37454, unmaintained, remove from Debian?

Hi Salvatore (2022.10.29_12:34:35_+) > Probably a good idea, if we can have that happen in time for bookworm. > Will you work on the reverse dependency to make it possible and then > request the removal for src:pysha3? Reverse dependency fixed, I'll file for RM now. SR -- Stefano Rivera h

Bug#1019849: python3-virtualenv: Please do not depend on python3-pip

Hi Benjamin (2022.09.15_07:26:00_+) > This looks like an accident. Probably coming from the upstream's Python > packaging metadata. Thanks for catching it! Oh, no, spoke too soon. This was added manually for pip 20. Possibly for the pip seeder? SR -- Stefano Rivera http://tumbleweed.org.

Bug#1019501: ansible-mitogen should probably depend on ansible and not on ansible-core

control: retitle -1 Support ansible 6 (2.13) Hi Florian (2022.09.11_20:09:21_+) > Looking at https://tracker.debian.org/pkg/python-mitogen > under actions it says: "unsatisfied dependency on ansible-core (< 2.13) " > > Now ansible-core 2.13.3-1 has a regression: > https://tracker.debian.org

Bug#101700: 1: ${python3:Depends} not expanded in Recommends line

Control: tag -1 - unreproducible Hi Marc (2022.08.15_19:29:46_+) > Now I know. The package in question is not python3-gensio, it's > gensio-bin. Aha, you are hitting this bit of logic: https://salsa.debian.org/python-team/tools/dh-python/-/blob/0895a390c27c8d7a4b1150aeca79505a9784a3f5/dhpyth

Bug#1016467: python3-configobj: places "private" files in top level of /usr/lib/python3/dist-packages

Control: forwarded -1 https://github.com/DiffSK/configobj/issues/32 Control: tag -1 + upstream Hi Julian (2022.08.01_06:26:09_+) > A package should not be placing "_version.py" or "validate.py" in the > top directory of this hierarchy. Instead, the layout should be > something like: Yeah, th

Bug#1011063: scp: Received message too long 1163022927

Control: tag -1 + patch https://salsa.debian.org/debian/dput-ng/-/merge_requests/20 SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1010480: virtualenv: skip creating of .gitignore when creating virtualenv in .

Tag: -1 + upstream This sounds like a purely upstream bug, I'd encourage you to file it at: https://github.com/pypa/virtualenv FWIW, I see a very similar issue: https://github.com/pypa/virtualenv/issues/2003 that was resolved by adding a command line flag. SR -- Stefano Rivera http://tumblew

Bug#1010371: gav: Source moved to GitHub

Source: gav Version: 0.9.0-3.1 - Forwarded message from Cesare Zavattari - > From: Cesare Zavattari > Subject: Package GAV changed repo > To: ubuntu-m...@lists.ubuntu.com > Date: Tue, 26 Apr 2022 13:00:55 +0200 > > Hi All, > just to inform you that GAV (Gpl Arcade Volleyball) moved fro

Bug#1009916: [venv] creation failed because of mising loca/bin/python

Hi julien.puydt (2022.04.20_15:51:50_+) > ERROR Virtual environment creation failed, executable /tmp/build-env- > nu5yo_4s/local/bin/python missing That was easy enough to work-around by selecting the posix_prefix sysconfig layout in python3-build. See: https://github.com/pypa/build/pull/463

Bug#1008810: thrift: FTBFS with Python 3.10

Hi László (2022.04.03_06:25:52_+) > With all due respect, it's a Golang FTBFS and not a Python one. Thanks. I think there is a Python 3.10 issue entangled in here, but it's fixed in 0.16.0: https://github.com/apache/thrift/commit/b724787d373de99feeab0eb2e052f8c8d3ed SR -- Stefano Rive

Bug#1008402: khmer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

Hi Andreas (2022.04.03_08:15:43_+) > Thanks a lot for the patch. Do you mean by "it isn't complete yet" the > issue that the build now fails with > >FileNotFoundError: [Errno 2] No such file or directory: '' > > as per Salsa CI[1]? Exactly. That filename could be special cased (maybe in

Bug#1004952: onnx: diff for NMU version 1.7.0+dfsg-3.1

Hi M. (2022.03.26_22:54:08_+) > The patch looks good to me and should be eligible to upload > without delay. Thank you, rescheduled to 0-day. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1007912: automake-1.16: autopkgtest regression in 1:1.16.5-1.2: AttributeError: module 'sysconfig' has no attribute 'get_default_scheme'

Hi Simon (2022.03.18_12:52:33_+) Hrm, not sure how I missed that, thanks. I'll make something upstreamable. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1006615: python3-pybind11: Handle Python 3.10's default sysconfig paths

Hi Gianfranco (2022.03.09_15:40:56_+) > Why is then gemmi in Ubuntu installing stuff into /usr/local/lib/python3.10 > and dh-python not moving it into /usr/lib? Because dh_python3 hasn't been called yet, at this point in the build. You need to update the dh_install config file. > -- Installi

Bug#1005149: pybuild not cleanly removing /usr/lib/python3.10/dist-packages

Hi William (2022.02.07_23:58:40_+) > While building ansible version 2.10.7+merged+base+2.10.8+dfsg-1 with python > 3.10 I have noticed that /usr/lib/python3.10/dist-packages/ansible is not > properly cleaned out. These builds are successfully cleaning out > /usr/lib/python3.9/dist-packages/ansi

Bug#1004378: dh_python3: does not correctly handle some cases of os-versioned dependencies

Hi Julian (2022.01.26_10:00:17_+) > I'm in the process of packaging the latest version of send2trash, and > have stumbled upon an interesting bug. > > During the build, I get the warnings: > >dh_python3 -O--buildsystem=pybuild > I: dh_python3 pydist:293: Cannot find package that provides

Bug#1004379: dh-python: provide pytest wrapper to test all python versions

Hi Drew (2022.01.26_09:56:25_+) FYI, this is work in progress on providing something to help here: https://salsa.debian.org/python-team/tools/dh-python/-/merge_requests/27 SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#970158: pyparsing isn't Python 2 compatible: time to remove pypy support? (was: Bug#970158: Updating the pyparsing Uploaders list)

Hi Thomas (2022.01.26_10:34:13_+) > When building 3.0.7, I get: > > I: pybuild base:237: pypy setup.py clean > Traceback (most recent call last): > File "setup.py", line 8, in > from pyparsing import __version__ as pyparsing_version > File "/<>/pyparsing/__init__.py", line 100 > m

Bug#1003482: libre2-dev: re2.pc contains "-std=c++11"

Control: forwarded -1 https://code-review.googlesource.com/c/re2/+/59570 Tag: -1 + upstream Makes sense, I submitted a patch upstream. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1003775: ansible-mitogen: not working with ansible from experimental

Hi Reiner (2022.01.15_17:40:48_+) > In the update you also added a dependency on ansible << 2.13. > Unfortunately this is no longer installable with ansible from > experimental, because the packaging has recently changed there. > src:ansible-core now contains the ansible binaries (2.12.0 curren

Bug#1003687: python-pip breaks python-virtualenv autopkgtest: invalid syntax

Hi Paul (2022.01.13_18:00:41_+) We have a transition in progress, although not coordinated with you guys. See #1003573. Once that is done, all the python3 side will work again. We need to get python2-pip through NEW to get 2.7 virtualenvs working again. I'll probably mark those tests as skip-

Bug#1003396: python3-flexmock: must not ship /usr/lib/python3/dist-packages/docs/conf.py

Hi Adrian (2022.01.09_14:06:47_+) Whoops! Good catch, regression in the new upstream that I missed. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#978949: dh-python: pybuild build system detection not consistent

Hi Gianfranco (2021.01.01_11:10:53_+) > I think, when certainity is around 50% the package should just error > out and the user should manually specify the needed build system, this > might fix all this uncertainity. I wouldn't trust the certainty numbers enough to do that, I think it would ca

Bug#1001838: AttributeError: 'NoneType' object has no attribute 'group'

Hi Christoph (2021.12.17_13:45:19_+) > I have no idea if this is a bug in dh-python or elsewhere, but it's > showing up here. It's a dh-python bug, from the environment marker parsing in 5.20211213. Thanks! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Bug#1001799: dh-python: python_version marker parsed incorrectly, adds a dependency that should be skipped

Hi Luca (2021.12.16_13:15:58_+) Agreed, this is a regression, thanks. I meant to explicitly deal with <3, but forgot. SR > Package: dh-python > Version: 5.20211214 > Severity: serious > Justification: causes FTBFS in reverse deps > > Hi, > > With the following in setup.py's install_requir

Bug#1001459: dh-python: SetuptoolsDeprecationWarning: setup.py install is deprecated

Hi Julian (2021.12.10_14:20:35_+) > running install_scripts > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. We're adding support for the build mechanism soo

Bug#1000826: python3-pip: incorrect version comparisons in requirements with Python 3.10

Hi Scott (2021.11.29_19:53:16_+) If I recall correctly, this is due to us having an older setuptools to support Python 2.7. We need to update setuptools to fix this (and carry a separate old one for 2.7, as long as python2.7 remains in the archive). Try updating setuptools from PyPI in the vi

Bug#996995: dh-python: Unable to parse debian/control

Hi Chris (2021.10.22_08:24:04_+) Thanks for the bug and the patch. I'm going to take a slightly different approach (and add test coverage). I thought it was too good to be true when my parsing rewrite passed all the tests on the first attempt :P SR -- Stefano Rivera http://tumbleweed.org

Bug#996822: ensurepip throws an AssertionError on pypy3

Hi Ophir (2021.10.19_17:13:16_+) > > > Again, not sure what you're expecting there. > > If python3-pip is supposed to work with pypy, I would expect `apt install > pypy3 python3-pip && pypy3 -m ensurepip --version` to return “pip 20.3.4-4”. > Instead, it returns the long error message you

  1   2   >