Source: python-clickhouse-driver
Version: 0.2.3-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
As can be seen on reproducible builds [1], python-clickhouse-driver
FTBFS with Python 3.10 as the default version. I've copied what I
hope is
Source: python-pcl
Version: 0.3.0~rc1+dfsg-11
Severity: serious
Tags: ftbfs
Hi Maintainer
Since sometime around the end of January, python-pcl started to FTBFS
in unstable and testing [1]. I've copied what I hope is the relevant
part of the log below.
Regards
Graham
[1]
Control: tags -1 + patch
Patch available in ubuntu [1].
scikit-fmm (2019.1.30-1ubuntu1) jammy; urgency=medium
* Cythonize at build time to fix FTBFS with Python 3.10
* Call dh --with numpy3 to pick up dependency on numpy-abi
-- Graham Inggs Mon, 31 Jan 2022 13:30:41 +
[1] https
Source: kdevelop-python
Version: 5.6.2-2
Severity: serious
Tags: ftbfs
Forwarded: https://bugs.kde.org/show_bug.cgi?id=438206
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
kdevelop-python has a hardcoded build-dependency on python3.9-dev.
Changing this to the generic
ON 1.7.3)
make[2]: *** [Makefile:122: html-build] Error 2
Description: Ignore distutils deprecation warnings in doc build
Author: Graham Inggs
Last-Update: 2022-03-30
--- a/doc/source/conf.py
+++ b/doc/source/conf.py
@@ -149,6 +149,7 @@
r"OpenSSL\.rand is deprecated", # OpenSSL package in
Hi Markus
On Mon, 28 Mar 2022 at 20:01, Graham Inggs wrote:
> I don't think anything is needed right now, thanks. I will schedule a
> rebuild of opm-common once graphviz has built, and then retry
> opm-simulators.
It seems opm-simulators FTBFS in much the same way now after
opm-common
Hi Markus
On Mon, 28 Mar 2022 at 17:30, Markus Blatt wrote:
> I just took a look at the tracker and noticed that opm-common is level 3 and
> opm-simulators is level 2. If build attempts for level 3 come after level 2
> that migth explain the failure in the logs [1] and opm-common should be in a
Control: tags -1 confirmed
On Wed, 23 Mar 2022 at 17:21, Simon McVittie wrote:
> The GNOME team is ready for this transition now. As usual, lots of Shell
> extensions are affected by API changes and will need porting or removal,
> but as usual, I think removing the affected Shell extensions from
Source: mypy
Version: 0.931-1
Severity: serious
Tags: ftbfs
Hi Maintainer
Since sometime around mid-March, mypy started to FTBFS in unstable and
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1]
Control: tags -1 confirmed
On Sun, 6 Mar 2022 at 15:03, Matthias Klose wrote:
> Please setup a transition window for python 3.10 as the default python3
> version.
> A tracker is setup at
>
> https://release.debian.org/transitions/html/python3.10-default.html
>
> Thanks to many Debian and
Source: salmon
Version: 1.6.0+ds1-1
Severity: important
Tags: ftbfs
Hi Maintainer
Your package uses a vendored copy of catch.hpp. It will FTBFS once
glibc is upgraded to 2.34 due to MINSIGSTKSZ and SIGSTKSZ no longer
being defined as constants.
You could take this opportunity to switch to
Source: salmon
Version: 1.6.0+ds1-1
Severity: serious
Tags: ftbfs
Hi Maintainer
Since sometime around the end of January, salmon started to FTBFS in
unstable and testing [1]. I've copied what I hope is the relevant
part of the log below.
Regards
Graham
[1]
Source: yt
Version: 4.0.2-1
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
The debian/rules of yt contains the line:
rm
debian/python3-yt/usr/lib/python3.9/dist-packages/yt/frontends/gdf/tests/test_outputs.py*
This will
Hi Rajendra
On Sun, 6 Mar 2022 at 12:42, Rajendra Kharat1 wrote:
> Could you please share the steps to reproduce the issue.
> As when I am trying to reproduce I ran into different problem of segmentation
> fault.
> Below are the steps that I followed.
> 1. Install python3-xarray on debian on
Source: python-confluent-kafka
Version: 1.7.0-1
Severity: serious
Tags: ftbfs
X-Debbugs-CC: debian-s...@lists.debian.org, ol...@debian.org
Hi Maintainer
Since the upload of 1.7.0-1, python-confluent-kafka FTBFS on s390x and
some other big-endian architectures (e.g. powerpc, ppc64) [1]. I've
Source: ecflow
Version: 5.8.3-1
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
The debian/rules of ecflow contains:
PY3VERSIONS:=python3.10 python3.9
This will cause ecflow to FTBFS once python3.9 is no longer a
supported
There is a patch [1] in Ubuntu for this.
The link is also on libdeflate's tracker page [2] (bottom right).
[1] https://patches.ubuntu.com/libd/libdeflate/libdeflate_1.8-1ubuntu1.patch
[2] https://tracker.debian.org/pkg/libdeflate
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Dear Release Team
I would like to transition trilinos from 12.18 to 13.2. Trilinos
13.2.0-1~exp1 has already cleared NEW, the auto-trilinos tracker [1]
is correct, and I have tested
Hi Diane
On Mon, 21 Feb 2022 at 05:39, Diane Trout wrote:
> It would... except numpy 1.22 just hit experimental on the 18th. and
> numba isn't compatible with numpy 1.22. I tried adding this to
> d/control,
>
> python3-numpy (<< 1.22),
>
> but my sbuild resolver still picked up numpy from
Hi Étienne
On Fri, 18 Feb 2022 at 21:06, Étienne Mollier wrote:
> Thank you for keeping track of these things. I consider pushing
> castxml 0.4.4 to unstable, as after some basic testing I did not
> see it requiring changes in reverse (build) dependencies.
Great! I think you should go ahead.
Source: dask
Version: 2021.09.1+dfsg-2
Severity: serious
Tags: ftbfs
Control: affects -1 src:python-sparse
Hi Maintainer
Python-sparse was removed from testing in order to advance the Python
3.10 transition (#996584). Dask has a build-dependency on
python3-sparse, so currently FTBFS in
Source: dxvk
Version: 1.9.4+ds1-1
Hi Maintainer
dxvk has an autopkgtest dependency on wine-development, which is an
arch:all package that Depends: wine64-development |
wine32-development.
When dxvk's autopkgtests are run in a pure i386 environment,
wine64-development is not installable, and
Hi Rajendra
Thanks for taking a look!
Unfortunately, that cannot be the solution, as that commit is already
present in the version of pandas in the archive [1].
Regards
Graham
[1]
https://salsa.debian.org/science-team/pandas/-/blob/debian/pandas/core/arrays/datetimelike.py#L462
On Sun, 13
Dear MIPS Porters
Could somebody take a look a this issue please?
> Hi YunQiang,
>
> On Sun, 12 Dec 2021 21:51:28 +0100 Paul Gevers wrote:
> > Your package src:gcc-defaults-mipsen has been trying to
> > migrate for 62 days [2]. Hence, I am filing this bug.
>
> Any progress? It has been 1.5
Dear Arm Porters
Is anyone able to help with the bus error on armhf please?
On Wed, 16 Feb 2022 at 09:33, Andreas Tille wrote:
>
> Control: tags -1 upstream
> Control: forwarded -1
> https://github.com/scikit-learn/scikit-learn/issues/22503
> also sent another bug report
>
Source: insighttoolkit4
Version: 4.13.3withdata-dfsg2-1
Severity: important
Tags: ftbfs
Forwarded: https://github.com/InsightSoftwareConsortium/ITK/issues/2827
Control: affects -1 src:castxml
Hi Maintainer
insighttoolkit4 FTBFS when built with glibc 2.34, currently in experimental.
I've copied
Source: sunpy
Version: 3.1.3-1
Severity: important
Tags: ftbfs
Hi Maintainer
Sunpy FTBFS when built with DEB_BUILD_OPTIONS=nocheck due to missing files.
chmod a-x
debian/python*-sunpy/usr/lib/python*/dist-packages/sunpy/data/test/*.fts
chmod: cannot access
Control: reassign -1 src:ansible 2.10.7+merged+base+2.10.8+dfsg-1
Control: severity -1 serious
Control: affects -1 + src:dh-python
Control: tags -1 + ftbfs
Control: retitle -1 ansible: misbuilds with two supported Python versions
Reassigning to src:ansible.
I see the same in a debian unstable chroot with sbuild.
Hi Timo
I've scheduled binNMUs for cinnamon-settings-daemon and wacomtablet.
Please remember that libwacom needs a source-only upload for migration.
Regards
Graham
Source: pcapy
Version: 0.11.5-1
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
pcapy builds its extension for all Python versions, but only tests
against the default version. This issue will become serious once
Python 3.10
Source: psi4
Version: 1:1.3.2+dfsg-2
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
I noticed psi4 has a build-dependency on python3-dev, and will require
a rebuild for Python 3.10 to build
core.cpython-310-x86_64-linux-gnu.so instead of
Source: python-xarray
Version: 0.21.0-1
X-Debbugs-CC: debian...@lists.debian.org, debian-s...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
python-xarray's autopkgtests are failing on the big-endian s390x
architecture [1].
I've copied what
Source: python-xarray
Version: 0.21.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
python-xarray's autopkgtests are failing on the i386 architecture [1].
I've copied what I hope is the relevant part of the log
Source: opentsne
Version: 0.6.1-2
Severity: serious
Tags: ftbfs
Hi Maintainer
opentsne FTBFS on i386 [1] and this currently blocks migration to
testing. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1]
Source: libtorrent-rasterbar
Version: 2.0.5-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This is
Control: reopen -1
debian/tests/control still contains:
Test-Command: set -efu
; cp -r tests examples "$AUTOPKGTEST_TMP"
; for py in $(py3versions -r 2>/dev/null)
; do cd "$AUTOPKGTEST_TMP"
; echo "Testing with $py:"
; $py -m unittest discover -s tests -v
; done
...and the test still
Source: tkrzw-python
Version: 0.1.28-2
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
tkrzw-python only builds for the default python3 version, but then
attempts to run atuopkgtests against all versions.
Regards
Graham
[1]
package in the archive affected by it, it may be quickest just to work
around it here for now. The attached patch worked for me.
Regards
Graham
Description: Avoid broken version check in ax_python_devel.m4
Author: Graham Inggs
Last-Update: 2022-01-26
--- a/configure.ac
+++ b/configure.ac
@@ -304,7
Source: pitivi
Version: 2020.09.2-3
Severity: serious
Tags: ftbfs bookworm sid
Hi Maintainer
Since sometime around January 15, pitivi started to FTBFS in unstable [1].
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1]
Source: glade
Version: 3.38.2-6
Severity: serious
Tags: ftbfs bookworm sid
Hi Maintainer
Since sometime around January 13, glade started to FTBFS in unstable [1].
I've copied what I hope is the relevant part of the log below.
Regards
Graham
[1]
Source: pytorch
Version: 1.8.1-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This is seen
on the
On Sat, 22 Jan 2022 at 10:45, YunQiang Su wrote:
> Sure. I will.
Thank you!
On Sat, 22 Jan 2022 at 10:12, YunQiang Su wrote:
> Let's have a try to build matplotlib with -O3, and try to build hkl with it.
> If it works, we can workaround it for now.
> I will continue to dig the real problem of gcc (maybe).
To be clear, will you try building matplotlib with -O3 and if it
Hi YunQiang Su
Have you been able to make any progress with this issue?
If not, then we should consider asking ftp-master for temporary
removal of the affected mips64el packages from testing. We'd like to
move the python3-defaults transition along.
Regards
Graham
Control: severity -1 serious
Bumping severity since we are no longer in freeze.
Source: node-pbkdf2
Version: 3.1.1-1
X-Debbugs-CC: debian...@lists.debian.org, debian-s...@lists.debian.org
Severity: important
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since 3.1.1-1, node-pbkdf2's autopkgtests have been failing on the
big-endian s390x architecture
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Hi Maintainer
The release team no longer [1] considers popcon a criterion for
inclusion in the list of key packages [2].
This email is a courtesy reminder of this bug, and should prevent
instant auto-removal once the rule is changed in britney.
Regards
Graham
[1]
Source: kicad
Version: 6.0.0+dfsg1-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
This package build-depends on libpython3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This is seen
Control: tags -1 + pending fixed-in-experimental
Control: block 967275 by -1
Control: severity 967275 important
Control: block 967831 by -1
Control: severity 967831 important
Hi Felipe
On Sun, 6 Jun 2021 at 23:42, Felipe Castro wrote:
> Hi, I'm the new upstream maintainer of GtkDatabox and we
Hi Antonio
On Fri, 31 Dec 2021 at 14:27, Antonio Valentino
wrote:
> Do you have an updated pointer to a build failure?
> ... or can we consider to close or at least reduce the severity of this
> issue?
builds failed again on amd64 yesterday in both testing and unstable
see
Hi Jude
On Sat, 1 Jan 2022 at 10:51, Jude DaShiell wrote:
>* What led up to the situation?
>Wrote a line of code for interpretation.
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
> ran yabasic ty.bas. line of code was
> input "enter
Hi Adrian
Thanks for the NMU. I'm going to cherry-pick upstream's commit [1]
instead. No need to cancel though, as your upload should just be
superseded.
Regards
Graham
[1]
https://github.com/OpenOrienteering/mapper/commit/e247f7270fc36ac9c62abe2f179a891d1df98616
Source: ceph
Version: 16.2.6+ds-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This is seen
on the
On Tue, 2 Feb 2021 at 11:06, Graham Inggs wrote:
> It would be nice if we had some automated way of detecting when
> r-cran-glmmtmb needs a rebuild.
Upstream included such a check in version 1.1.0 [1].
r-cran-glmmtb's autopkgtests have been complaining since 2021-09-23
16:13:22
Hi Dima
On Mon, 20 Dec 2021 at 22:40, Dima Kogan wrote:
> I installed python3.10, and asked the build system to use it. Instead of
> the error you're reporting, I get a build error: it can't find the numpy
> headers because python3-numpy is built for python3.9. This makes sense.
numpy
Source: tkrzw-python
Version: 0.1.28-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Hi Maintainer
This package build-depends on libpython3-all-dev, but does not build
extensions/libraries for all supported python3 versions. This is seen
Source: mrgingham
Version: 1.20-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev
Control: affects -1 src:python3-defaults
Hi Maintainer
mrgingham's
Source: python-hypothesis
Version: 5.43.3-1
Severity: serious
Tag: bookworm sid ftbfs
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults
Hi Maintainer
Source: busco
Version: 5.2.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults
Hi Maintainer
As can be seen [1], the autopkgtests
Hi Nliesh
On Wed, 1 Dec 2021 at 23:00, Nilesh Patra wrote:
> But we should make a list of all such packages and ping for Graham/Sebastian
> to propagate the hints accordingly. Probably that's what Graham wanted to say
> in the first place.
I've already added hints marking
Hi Nilesh
On Wed, 1 Dec 2021 at 13:03, Nilesh Patra wrote:
> One i386 autopkgtest failure for r-bioc-biocparallel is stalling the entire
> migration. Rest stuff looks okay.
There's at least one more regression; in gffread, caused by
r-bioc-gviz [1]. Please check that each r-bioc* package is
Source: python-skbio
Version: 0.5.6-5
Severity: serious
Tags: ftbfs patch
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
Now that scikit-learn has at least built on amd64 [1], we can now see
a new failure in python-skbio [2]. I have copied part of the log
below.
This
Source: aspcud
Version: 1:1.9.5-1
Severity: important
Hi Maintainer
Your package uses a vendored copy of catch.hpp. It will FTBFS once
glibc is upgraded to 2.34 due to MINSIGSTKSZ and SIGSTKSZ no longer
being defined.
You could take this opportunity to switch to using the catch2 package
[1] in
Source: segyio
Version: 1.8.3-1.1
Severity: important
Forwarded: https://github.com/equinor/segyio/issues/520
Hi Maintainer
Your package uses a vendored copy of catch.hpp. It will FTBFS once
glibc is upgraded to 2.34 due to MINSIGSTKSZ and SIGSTKSZ no longer
being defined.
You could take this
Control: reopen -1
For some reason, this package runs the tests from
debian/tests/test_reprozip.py [1], instead of from upstream.
[1]
https://salsa.debian.org/science-team/reprozip/-/blob/master/debian/tests/test_reprozip.py#L236
Control: tags -1 + patch fixed-upstream
Both of these issues are fixed in:
https://github.com/biocore/scikit-bio/commit/357c7fe847187bc540c4914c3ffd607d9432857d
801 - 900 of 2671 matches
Mail list logo
