Control: reopen -1
The autopkgtest still times out in the salsa pipeline [1].
It is not clear to me whether #1101992 is now fixed, or whether a new
bug needs to be filed for the failing import.
I've copied what I hope is the relevant part of a pipeline job [2] below.
[1] https://salsa.debian.o
Control: severity -1 important
The autopkgtest of python-sparse 0.16.0a9-1 seems to be passing on
arm64 now, and numba is not yet built on s390x.
Control: severity -1 important
0.61.0+dfsg-1 and 0.61.2+dfsg-1 built successfully on arm64.
numba's binaries should probably be removed on mips64el.
Control: severity -1 important
This test passed on retry. I am downgrading the severity for now to
allow cp2k to migrate testing. The severity can be raised again if
the test proves to be flaky.
2025.1-1 2025-04-11 07:11:52 UTC
cp2k/2025.1-1
src:cp2k from unstable
2h 56m 43s pass
Source: patchelf
User: debian-m...@lists.debian.org
Usertags: mips64el
X-Debbugs-Cc: debian-m...@lists.debian.org
X-Debbugs-Cc: Sergio Durigan Junior
Version: 0.18.0-1.2
Severity: serious
Tags: ftbfs
Hi Maintainer
The recent upload of patchelf 0.18.0-1.2 FTBFS on mips64el [1]. I've
copied what
Source: mariadb
Version: 1:11.8.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2025-03-30, mariadb's autopkgtest
regressed in testing [1]. I've copied what I hope is the relevant
part of the log below.
Regards
Graham
[1] https://ci.de
Helpful people on # debian-python pointed to this part of the log:
make[1]: Leaving directory '/build/reproducible-path/esys-particle-2.3.5+dfsg2'
dh_installchangelogs -a
dh_installman -a
dh_python3 -a
E: dh_python3 dh_python3:198: no package to act on (python3-foo or one
with ${python3:D
Source: bbmap
Version: 39.18+dfsg-1
Severity: serious
Hi Maintainer
bbmap has a dependency on openjdk-17-jre-headless, which will not be
part of trixie, see #1102113
Regards
Graham
Source: esys-particle
Version: 2.3.5+dfsg2-8
Severity: serious
Tags: ftbfs
Hi Maintainer
When built with Python 3.13 only, esys-particle builds successfully,
but then the resulting package does not seem to be functioning
correctly and the autopkgtests time out (see #946206).
Comparing the binary
Control: reopen -1
Hi Bastian
While adjusting the version of the onetbb would avoid the FTBFS in
r-cran-rcppparallel right now, if onetbb ever gets an update in
stable, a backport, a +really upload, or an epoch, then
r-cran-rcppparallel will FTBFS again.
This really needs to be fixed in r-cran-r
Source: r-cran-rcppparallel
Version: 4:8.5.0-1
Severity: serious
Tags: ftbfs
Hi Maintainer
r-cran-rcppparallel FTBFS when rebuilt for onetbb 2022.1.0-1~exp1.
Note the non-numeric part of the version string.
I've copied what I hope is the relevant part of the log [1] below.
Regards
Graham
[1]
I think I see the problem.
The test run on 2025-01-29 03:55:04 UTC [1] against numpy/1:2.2.2+ds-2
should have failed, and prevented numpy from migrating to testing, but
debian/tests/control has all tests marked 'skip-not-installable'
(please don't do that), so the test result was considered 'neutr
It seems the BTS considers that 4.3.0-2 will re-introduce this bug to
testing because the changelog entry for 4.2.1-4 above was dropped from
debian/changelog.
Source: cctbx
Version: 2024.10+ds2+~3.22.1+ds1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime between 2025-01-25 and 2025-02-01, cctbx's autopkgtest
regressed in testing [1]. I've copied what I hope is the relevant
part of the log below.
Regards
Source: python3.12
Version: 3.12.9-1
Severity: serious
python3.12 is superseded by python3.13
Emilio wrote:
> This is blocking the numpy transition.
I triggered the autopkgtests of sympy/1.13.3-1 in testing with numpy
from unstable, and they passed on armel [1] and ppc64el [2].
I don't think the numpy transition is blocked by this, only sympy
itself by its test failures introduced by the
Source: gubbins
Version: 3.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2025-01-29, gubbins' autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.n
Source: lintian
Version: 2.121.1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2025-02-06, lintian's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debia
Control: severity -1 important
I have filed bug #1096029 requesting removal of cp2k's binaries on
these architectures, lowering severity.
Source: freefem++
Version: 4.14+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-12-26, freefem++'s autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://
Source: tiddit
Version: 3.6.1+dfsg-1
Severity: serious
Hi Maintainer
This package includes a Python extension module, which uses Numpy via
its binary interface. Such packages must depend on
python3-numpy-abiN.
If the package is using debhelper, this problem is usually due to a
missing dh_numpy3
Source: python-hdmedians
Version: 0.14.2-5.1
Severity: serious
Hi Maintainer
This package includes a Python extension module, which uses Numpy via
its binary interface. Such packages must depend on
python3-numpy-abiN.
If the package is using debhelper, this problem is usually due to a
missing d
Source: pycorrfit
Version: 1.1.7+nopack-1
Severity: serious
Hi Maintainer
This package includes a Python extension module, which uses Numpy via
its binary interface. Such packages must depend on
python3-numpy-abiN.
If the package is using debhelper, this problem is usually due to a
missing dh_n
Source: pyscanfcs
Version: 0.3.6+ds-4
Severity: serious
Tags: trixie sid
Hi Maintainer
This package includes a Python extension module, which uses Numpy via
its binary interface. Such packages must depend on
python3-numpy-abiN.
If the package is using debhelper, this problem is usually due to a
Source: meep
Version: 1.25.0-4
Severity: serious
Hi Maintainer
This package includes a Python extension module, which uses Numpy via
its binary interface. Such packages must depend on
python3-numpy-abiN.
If the package is using debhelper, this problem is usually due to a
missing dh_numpy3 call
Source: fpylll
Version: 0.6.3-1
Severity: serious
Hi Maintainer
This package includes a Python extension module, which uses Numpy via
its binary interface. Such packages must depend on
python3-numpy-abiN.
If the package is using debhelper, this problem is usually due to a
missing dh_numpy3 call
Source: fast-histogram
Version: 0.14-2
Severity: serious
Hi Maintainer
This package includes a Python extension module, which uses Numpy via
its binary interface. Such packages must depend on
python3-numpy-abiN.
If the package is using debhelper, this problem is usually due to a
missing dh_nump
Source: astropy-healpix
Version: 1.0.3-1
Severity: serious
Hi Maintainer
This package includes a Python extension module, which uses Numpy via
its binary interface. Such packages must depend on
python3-numpy-abiN.
If the package is using debhelper, this problem is usually due to a
missing dh_nu
Control: reopen -1
Hi
This bug was closed in cmake, however the autopkgtests of lfortran [1]
are still failing in testing.
Regards
Graham
[1] https://ci.debian.net/packages/l/lfortran/testing/arm64/
Source: python-einops
Version: 0.8.0-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/
Source: python-pyvista
Version: 0.44.1-10
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.n
Source: parallax
Version: 1.0.6-4
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packa
Source: patroni
Version: 3.3.5-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packag
Hi Markus
* Markus Blatt [250109 16:24]:
> the binary rebuild for version 2024.10+ds-3+b3 on January 7 failed on all
> architectures, see [1]
> and particularly [2] for amd64. The rebuilds were probably done for the
> python3.13 as default
> transition [3].
Looking at the transition tracker [1
I think this is due to the openturns FTBFS (see #1091444).
Hi Abou
On Tue, 7 Jan 2025 at 19:48, Abou Al Montacir wrote:
> The issue here is that the test machine is running FPC 3.2.2+dfsg-34 while
> the new CGE 7.0~alpha.3+dfsg1-4 requires FPC 3.2.2+dfsg-35 (which is a but by
> itself).
>
> I'll upload a new version enforcing this dependency and closin
Source: cluster3
Version: 1.59+ds-6
Severity: serious
Tags: ftbfs
Hi Maintainer
cluster3 is non-free and is not auto-buildable, so requires a manual
rebuild for the Python 3.13 transition. Please upload a build with
Python 3.13 as default, including binaries.
Regards
Graham
Source: digikam
Version: 4:8.5.0-1
Severity: serious
Tags: ftbfs
Hi Maintainer
As can be seen in reproducible builds [1], digikam currently FTBFS in unstable.
I believe this is due to the following in debian/control:
Build-Conflicts: imagemagick-6-common
While imagemagick-6-common is now a vir
Source: castle-game-engine
Version: 7.0~alpha.3+dfsg1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-12-17, castle-game-engine's autopkgtest regressed
in testing [1]. I've copied what I hope is the relevant part of the
log below.
Reg
Control: severity -1 important
Control: tags -1 + unreproducible
Hi Emmanuele
mfem builds for arm64 succeeded recently on the builds [1] and on
reproducible builds [2].
Would you please check whether it still fails for you?
I suspect your previous build happened during the openmpi transition.
Source: r-cran-seurat
Version: 5.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 5.1.0-1, r-cran-seurat has been failing its own
autopkgtests on riscv64 [1] and s390x [2] where it succeeded
previously.
I've copied what I hope is the
Control: affects -1 + src:r-cran-lwgeom
It seems at least r-cran-lwgeom needs updating to 0.2-14 for
compatibility with the new r-cran-sf [1].
version 0.2-14
st_perimeter() is deprecated in favor of st_perimeter_lwgeom(), as sf
takes over with sf::st_perimeter().
[1] https://cran.r-project.org
Source: pbsuite
Version: 15.8.24+dfsg-8
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-12-26, pbsuite's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
This regression allowed blasr/
Source: swig
Version: 4.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-02-28, swig's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/
Control: reopen -1
This is not yet solved. The autopkgtests are still failing in testing [1].
[1] https://ci.debian.net/packages/r/r-cran-sf/testing/amd64/
104s Some packages could not be installed. This may mean that you have
104s requested an impossible situation or if you are using the uns
Control: severity -1 important
Control: tags -1 + unreproducible
Hi Emmanuele
elkcode builds for arm64 succeeded recently on the builds [1] and on
reproducible builds [2].
Would you please check whether it still fails for you?
I suspect your previous build happened during the openmpi transition
Source: oxigraph
Version: 0.4.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-08-12, oxigraph's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.deb
Control: severity -1 important
Control: tags -1 + unreproducible
Hi Emanuele
I am unable to reproduce this failure on a porterbox. I also tried on
reproducible builds, but the build failed due to a test timeout, which
I think is unrelated.
Would you please check whether it still fails for you?
Author: Graham Inggs
Last-Update: 2024-12-19
--- a/questplus/tests/test_qp.py
+++ b/questplus/tests/test_qp.py
@@ -435,11 +435,11 @@
next_stim_1 = qp.next_stim['physical_magnitude_stim_1']
next_stim_2 = qp.next_stim['physical_magnitude_stim_2']
-if
Hi Emanuele
On Tue, 17 Dec 2024 at 08:25, Emanuele Rocca wrote:
> It seems that valgrind is currently building fine on both armhf and i386
> with mpi-defaults 1.17:
>
> https://people.debian.org/~ema/valgrind_armhf-2024-12-17T09:07:39Z.build
> https://people.debian.org/~ema/valgrind_i386-2024-12-
Please note that this also needs to be fixed in debian/tests/control
for the autopkgtest [1]. See below.
[1] https://ci.debian.net/packages/l/lilypond/testing/amd64/
39s The following packages have unmet dependencies:
39s satisfy:command-line : Depends: imagemagick-6.q16 but it is not installa
Control: tags -1 + patch
The attached patch was applied in Ubuntu.
From: Anshul Singh
Date: Wed, 11 Dec 2024 14:05:50 +0530
Subject: Patch to stop generating nan values in tests to work with latest attrs
Origin: upstream, https://github.com/python-attrs/cattrs/commit/96ed9a1c972814c379f9ea8faa34
Source: python-voip-utils
Version: 0.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 0.2.1-1, python-voip-utils fails its own
autopkgtest [1] on s390x (big-endian). I've copied what I hope is the
relevant part of the log below.
Thi
On Thu, 12 Dec 2024 at 13:55, Andrey Rakhmatullin wrote:
> Looks like the package only builds for the default Python version, I
> rebuilt it as is (as it wasn't binNMUed) and it still doesn't contain 3.13
> binaries. It uses cmake to build a single set of .so.
If tomopy cannot build for all suppo
Source: dulwich
Version: 0.21.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-12-11, dulwich's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
This regression allowed dulwich/0.22
Source: pylint
Version: 3.3.1-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/package
Source: mpich
Version: 4.2.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
The upload of mpich 4.2.1-2 is failing its own autopkgtests [1]. I've
copied what I hope are the relevant parts of the log below.
This regression prevents mpich 4.2.1-2 from migr
Source: python-rosettasciio
Version: 0.6-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertag: python3.13
Hi Maintainer
python-rosettasciio Build-Depends on python3-all-dev, but doesn't
build for all supported python3 versions.
I've copied below a portion of a recent amd64 build log
Hi Andrius
On Mon, 9 Dec 2024 at 08:54, Andrius Merkys wrote:
> dials autopkgtest apparently does not pull in the dependency on
> python3-gemmi. I think python3-dials should have 'Depends: python3-gemmi'.
Upstream's changelog mentions "gemmi-less objects can be used by other
gemmi-less software"
Source: dials
Version: 3.17.0+dfsg3-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-09-30, dial's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.deb
Source: celery
Version: 5.4.0-2.1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packa
Source: xraylib
Version: 4.0.0+dfsg1-5
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/
Source: ubelt
Version: 1.3.6-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages
Source: tomopy
Version: 1.15.0+ds1-8
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/pa
Source: supervisor
Version: 4.2.5-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/pac
Source: spyder
Version: 5.5.1+ds-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/pack
Source: smart-open
Version: 7.0.5-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/pac
Source: python-picologging
Version: 0.9.4-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian
Source: python-oslo.messaging
Version: 14.9.1-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.de
Source: python-omegaconf
Version: 2.3.0-1.1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian
Source: python-cheroot
Version: 10.0.1+ds1-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debia
Source: python-nexusformat
Version: 1.0.6-3
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian
Source: python-mouseinfo
Version: 0.0~git20230505000925.23791fa-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
Source: python-drf-spectacular
Version: 0.27.2-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.d
Source: python-django-compressor
Version: 4.5.1-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.
Source: python-beartype
Version: 0.19.0-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.n
> 296s Unsatisfied dependencies:
> 296s sbuild-build-depends-main-dummy:arm64 : Depends: libc-dev:arm64
> 296s Depends: libstdc++-dev:arm64
Is this uninstallability caused by a mismatch between the version of
glibc in unstable and the version in testing?
Control: affects -1 + src:glibc
This regression [1] currently blocks migration of glibc/2.40-4.
[1] https://ci.debian.net/packages/s/sbuild/testing/amd64/
Control: severity -1 important
This issue is not seen on the builds [1]. nor on reproducible builds [2].
As this bug currently blocks the openmpi transition, I am downgrading
the severity.
Please feel free to raise the severity again after openmpi has
migrated, if the problem persists.
[1] http
Source: pypandoc
Version: 1.13+ds0-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/pa
Source: pytest-jupyter
Version: 0.10.1-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.ne
Source: pyscreeze
Version: 0.0~git20240820225245.93f2775-5
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] ht
Source: pyautogui
Version: 0.0~git20230607111623.b4255d0-5
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] ht
Source: pocketsphinx-python
Version: 1:0.1.15-7
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.de
Source: ovn-octavia-provider
Version: 7.0.0-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debi
Source: pastescript
Version: 3.6.0-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/pa
Source: optlang
Version: 1.8.2-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packag
Source: openstack-trove
Version: 1:22.0.0-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian
Source: nibabel
Version: 5.2.1-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packag
Source: ndms2-client
Version: 0.1.3-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/p
Source: nabu
Version: 2024.1.9-3
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packag
Source: metakernel
Version: 0.30.2-6
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/pa
Source: mdp
Version: 3.6-8
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/m/m
Source: loguru
Version: 0.7.2-3
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/package
Source: jupytext
Version: 1.16.1+ds1-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/
Source: jupyter-server
Version: 2.14.2-4
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.ne
A guess here, but this was probably the cause of a previous FTBFS in augur [1].
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058394
Control: tags -1 + ftbfs
augur currently FTBFS in unstable on reproducible builds [1]. I've
filed a bug against pyfastx [2] to track this.
[1] https://tests.reproducible-builds.org/debian/rb-pkg/augur.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088355
Source: pyfastx
Version: 2.1.0-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The python3-fastx binary package contains:
/usr/lib/python3/dist-packages/pyfastx.cpython-312-x86_64-linux-gnu.so
However, the binary control file contains an unversioned d
Source: jinja2
Version: 3.1.3-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Hi Maintainer
The autopkgtests of this package fail with Python 3.13 [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/package
1 - 100 of 1129 matches
Mail list logo
