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
what I hope is the relevant part of the log below.
Regards
Graham
[1] https://buildd.debian.org/status/logs.php?pkg=patchelf&arch=mips64el
writing ./many-syms-main
# Run the patched tool and libraries
./many-syms-main: symbol lookup error: ./many-syms-main: undefined
symbol: f225_speci
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
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
/esys/
Regards
Graham
-rcppparallel.
Regards
Graham
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
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.
log below.
Regards
Graham
[1] https://ci.debian.net/packages/c/cctbx/testing/amd64/
266s autopkgtest [06:45:11]: test dxtbx: [---
267s Testing dxtbx with python3.13:
271s Fatal Python error: Segmentation fault
271s
271s Current thread 0x7fc2049cf100 (most recent call first):
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
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
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
dh_numpy3 call in debian/rules.
There was a Lintain tag [1] for this issue, but I do not see now where
this is reported. You can also find further information in the
documentation [2] of the numpy package.
Regards
Graham
[1] https://lintian.debian.org/tags/missing-dependency-on-numpy-abi.html
[2
dh_numpy3 call in debian/rules.
There was a Lintain tag [1] for this issue, but I do not see now where
this is reported. You can also find further information in the
documentation [2] of the numpy package.
Regards
Graham
[1] https://lintian.debian.org/tags/missing-dependency-on-numpy-abi.html
dh_numpy3 call in debian/rules.
There was a Lintain tag [1] for this issue, but I do not see now where
this is reported. You can also find further information in the
documentation [2] of the numpy package.
Regards
Graham
[1] https://lintian.debian.org/tags/missing-dependency-on-numpy-abi.html
[2
a
missing dh_numpy3 call in debian/rules.
There was a Lintain tag [1] for this issue, but I do not see now where
this is reported. You can also find further information in the
documentation [2] of the numpy package.
Regards
Graham
[1] https://lintian.debian.org/tags/missing-dependency-on-numpy
in debian/rules.
There was a Lintain tag [1] for this issue, but I do not see now where
this is reported. You can also find further information in the
documentation [2] of the numpy package.
Regards
Graham
[1] https://lintian.debian.org/tags/missing-dependency-on-numpy-abi.html
[2] https
call in debian/rules.
There was a Lintain tag [1] for this issue, but I do not see now where
this is reported. You can also find further information in the
documentation [2] of the numpy package.
Regards
Graham
[1] https://lintian.debian.org/tags/missing-dependency-on-numpy-abi.html
[2]
https
dh_numpy3 call in debian/rules.
There was a Lintain tag [1] for this issue, but I do not see now where
this is reported. You can also find further information in the
documentation [2] of the numpy package.
Regards
Graham
[1] https://lintian.debian.org/tags/missing-dependency-on-numpy-abi.html
[2
dh_numpy3 call in debian/rules.
There was a Lintain tag [1] for this issue, but I do not see now where
this is reported. You can also find further information in the
documentation [2] of the numpy package.
Regards
Graham
[1] https://lintian.debian.org/tags/missing-dependency-on-numpy-abi.html
[2
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.debia
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]
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.debia
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.debia
s can be solved for future transitions if opm-simulators
had an explicit Build-Depends on libopm-common-dev, so Ben would place
opm-simulators in a higher dependency level than opm-common, ensuring
that opm-common is rebuilt before opm-simulators.
Regards
Graham
[1] https://release.debian.org/t
I think this is due to the openturns FTBFS (see #1091444).
this dependency and closing this bug.
The latest test still fails, while it can be seen in the log below
that fpc 3.2.2+dfsg-35 was used.
Regards
Graham
135s Free Pascal Compiler version 3.2.2+dfsg-35 [2025/01/05] for x86_64
135s Copyright (c) 1993-2021 by Florian Klaempfl and others
135s Target
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
virtual package provided by
imagemagick-7-common,
Regards
Graham
[1] https://tests.reproducible-builds.org/debian/rb-pkg/digikam.html
log below.
Regards
Graham
[1] https://ci.debian.net/packages/c/castle-game-engine/testing/amd64/
112s Free Pascal Compiler version 3.2.2+dfsg-34 [2024/07/13] for x86_64
112s Copyright (c) 1993-2021 by Florian Klaempfl and others
112s Target OS: Linux for x86-64
112s Compiling castle_tester_stan
.
Regards
Graham
[1] https://buildd.debian.org/status/logs.php?pkg=mfem&arch=arm64
[2] https://tests.reproducible-builds.org/debian/history/arm64/mfem.html
pe is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-seurat/testing/riscv64/
[2] https://ci.debian.net/packages/r/r-cran-seurat/testing/s390x/
185s ══ Failed tests
185s ── Fa
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
owed blasr/5.3.5+dfsg-7 to migrate to testing.
Regards
Graham
[1] https://ci.debian.net/packages/p/pbsuite/testing/amd64/
74s 2024-12-26 05:20:04,185 [INFO] Running /usr/bin/Honey spots
--reference lambda_modified.fasta mappingFinal.bam
74s Traceback (most recent call last):
74s File "
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.
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
transition.
Regards
Graham
[1] https://buildd.debian.org/status/logs.php?pkg=elkcode&arch=arm64
[2] https://tests.reproducible-builds.org/debian/history/arm64/elkcode.html
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
?
I suspect your previous build happened during the openmpi transition.
Regards
Graham
should be
able to confirm whether this patch is sufficient in experimental
before doing a team upload to unstable.
Regards
Graham
[1] https://ci.debian.net/packages/p/python-questplus/
Description: Allow more rounding errors in the tests with scipy 1.14
Bug-Debian: https://bugs.debian.org/1079788
nd_i386-2024-12-17T09:04:47Z.build
>
> Can you please double-check once again?
Indeed, on reproducible builds it seems valgrind now builds
successfully in unstable, but still fails in trixie.
I'm guessing something fixed between mpich 4.2.0-14 in trixie and
4.2.1-4 in unstable.
Regards
Graham
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
below.
This regression current prevents python-voip-utils 0.2.1-1 from
migrating to testing.
Regards
Graham
[1] https://ci.debian.net/packages/p/python-voip-utils/testing/s390x/
24s === FAILURES
==
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
ed dulwich/0.22.5-1, which has always been
failing its autopkgtests, to migrate to testing.
Regards
Graham
[1] https://ci.debian.net/packages/d/dulwich/testing/amd64/
232s ==
232s FAIL: tes
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.debia
from migrating to testing.
Regards
Graham
[1] https://ci.debian.net/packages/m/mpich/testing/amd64/
268s autopkgtest [19:11:09]: test compile-run-cc-pkgconf-mpi:
[---
268s
/tmp/autopkgtest-lxc.gno2b9sz/downtmp/build.McI/src/debian/tests/compile-run-cc-pkgconf-mpi:
1: pkg-c
build log [1].
unbcf_fast.cpython-313-x86_64-linux-gnu.so is missing.
Regards
Graham
[1] https://buildd.debian.org/status/logs.php?pkg=python-rosettasciio&arch=amd64
drwxr-xr-x root/root 0 2024-12-03 20:24 ./
drwxr-xr-x root/root 0 2024-12-03 20:24 ./usr/
drwxr-xr-x root/
other
gemmi-less software", so maybe it doesn't need to be a hard Depends:
python3-gemmi, and only needs to be added to debian/tests/control as a
dependency for the autopkgtest.
Regards
Graham
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
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.debia
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.debia
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.debia
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.debia
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.debia
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.debia
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.debia
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]
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]
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]
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]
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]
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
G
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]
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]
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]
> 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.debia
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]
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
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
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]
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]
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.debia
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.debia
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]
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.debia
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.debia
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.debia
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.debia
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/packa
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.debia
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.debia
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]
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
with the Python Team.
Regards
Graham
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088316
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004907
[3]
https://salsa.debian.org/debichem-team/psi4/-/commit/9321918390d2ccf5f00c04705974391e81fc863d
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.debia
1 - 100 of 1138 matches
Mail list logo
