Processing commands for cont...@bugs.debian.org:
> retitle 982647 spyder-reports: incompatible with spyder 4.2.1+
Bug #982647 [src:spyder-reports] spyder-reports FTBFS with Spyder 4.2.1
Changed Bug title to 'spyder-reports: incompatible with spyder 4.2.1+' from
'spyder-reports FTBFS with Spyder
FYI: The status of the apertium-szl source package
in Debian's testing distribution has changed.
Previous version: 0.1.0-1.1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney
FYI: The status of the apertium-tur source package
in Debian's testing distribution has changed.
Previous version: 0.2.0~r83161-2.1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the
FYI: The status of the apertium-swe source package
in Debian's testing distribution has changed.
Previous version: 0.8.0-2
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney hint
FYI: The status of the apertium-oci source package
in Debian's testing distribution has changed.
Previous version: 0.1.0-1.1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney
FYI: The status of the apertium-rus source package
in Debian's testing distribution has changed.
Previous version: 0.2.0~r82706-1.1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the
FYI: The status of the apertium-nno source package
in Debian's testing distribution has changed.
Previous version: 1.0.0-2
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney hint
FYI: The status of the apertium-dan source package
in Debian's testing distribution has changed.
Previous version: 0.6.0-2
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney hint
FYI: The status of the apertium-arg source package
in Debian's testing distribution has changed.
Previous version: 0.1.2~r65494-2.1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the
FYI: The status of the apertium-tat source package
in Debian's testing distribution has changed.
Previous version: 0.1.0~r60887-2.1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the
FYI: The status of the apertium-srd source package
in Debian's testing distribution has changed.
Previous version: 1.2.0-1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney hint
FYI: The status of the apertium-spa-cat source package
in Debian's testing distribution has changed.
Previous version: 2.2.0-1
Current version: 2.2.0-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
FYI: The status of the apertium-cat source package
in Debian's testing distribution has changed.
Previous version: 2.6.0-2
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney hint
FYI: The status of the apertium-kaz source package
in Debian's testing distribution has changed.
Previous version: 0.1.0~r61338-2.1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the
FYI: The status of the apertium-pol source package
in Debian's testing distribution has changed.
Previous version: 0.1.1-2
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney hint
FYI: The status of the apertium-nob source package
in Debian's testing distribution has changed.
Previous version: 1.0.0-2
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney hint
FYI: The status of the apertium-hbs source package
in Debian's testing distribution has changed.
Previous version: 0.5.0~r68212-3.1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the
FYI: The status of the apertium-fra source package
in Debian's testing distribution has changed.
Previous version: 1.5.0-1.1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney
FYI: The status of the apertium-bel source package
in Debian's testing distribution has changed.
Previous version: 0.1.0~r81357-3
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the
FYI: The status of the apertium-crh source package
in Debian's testing distribution has changed.
Previous version: 0.2.0~r83161-2.1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the
FYI: The status of the apertium-cat-ita source package
in Debian's testing distribution has changed.
Previous version: 0.2.1-2
Current version: 0.2.1-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
pysph 1.0~b0~20191115.gite3d5e10-4 is marked for autoremoval from testing on
2021-03-14
It (build-)depends on packages with these RC bugs:
971289: beaker: Switch to python3-pycryptodome
https://bugs.debian.org/971289
This mail is generated by:
This flag is already in use, see https://salsa.debian.org/science-team/gmsh/-/
blob/master/debian/rules#L34
Hello everyone,
the ENABLE_SYSTEM_CONTRIB=1 seems not to be sufficient.
The build log shows this line:
-- Found Eigen
With this include given to c++:
Processing commands for cont...@bugs.debian.org:
> severity 982647 grave
Bug #982647 [src:spyder-reports] spyder-reports FTBFS with Spyder 4.2.1
Severity set to 'grave' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
982647:
severity 982647 grave
thanks
On Fri, Feb 12, 2021 at 10:48:48PM +0200, Adrian Bunk wrote:
> Source: spyder-reports
> Version: 0.1.1-4
> Severity: serious
> Tags: ftbfs
Thanks for picking this one up, Adrian. It turns out that it is
actually an upstream bug and this package is currently not
Package: python3-pweave
Version: 0.25-3
Severity: normal
On installing this package, I get the following warning:
Setting up python3-pweave (0.25-3) ...
/usr/lib/python3/dist-packages/pweave/__init__.py:47: SyntaxWarning: "is not"
with a literal. Did you mean "!="?
assert file != "" is not
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 13 Feb 2021 07:36:03 +
Source: numexpr
Architecture: source
Version: 2.7.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Antonio Valentino
Changes:
numexpr
numexpr_2.7.2-2_source.changes uploaded successfully to localhost
along with the files:
numexpr_2.7.2-2.dsc
numexpr_2.7.2-2.debian.tar.xz
numexpr_2.7.2-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
debian-science-maintainers mailing
Source: qrouter
Version: 1.4.71-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -g -O2 -ffile-prefix-
Source: pygmsh
Version: 7.1.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: siconos
Version: 4.3.1+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> The following tests FAI
G'day FTPMaster and Kartik...
I've pushed HFST 3.15.4 to https://salsa.debian.org/science-team/hfst which
should resolve all this.
The upstream tracking issue was https://github.com/hfst/hfst/issues/494 and
there's also been some emails to the HFST authors, with Kartik on CC, to
clear everything
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 13 Feb 2021 02:28:09 +0100
Source: dolfinx
Architecture: source
Version: 2019.2.0~git20210130.c14cb0a-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Drew Parsons
Changes:
dolfinx_2019.2.0~git20210130.c14cb0a-4_source.changes uploaded successfully to
localhost
along with the files:
dolfinx_2019.2.0~git20210130.c14cb0a-4.dsc
dolfinx_2019.2.0~git20210130.c14cb0a-4.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Processing commands for cont...@bugs.debian.org:
> reopen 980707
Bug #980707 {Done: Georges Khaznadar } [src:sympy]
octave-symbolic: FTBFS against sympy 1.7
Bug #982561 {Done: Georges Khaznadar } [src:sympy] sympy
breaks octave-symbolic autopkgtest: _PrintFunction' object has no attribute
Your message dated Sat, 13 Feb 2021 12:57:52 +
with message-id
and subject line Bug#982498: Removed package(s) from unstable
has caused the Debian Bug report #965546,
regarding geant321: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim
Your message dated Sat, 13 Feb 2021 12:57:52 +
with message-id
and subject line Bug#982498: Removed package(s) from unstable
has caused the Debian Bug report #957263,
regarding geant321: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 13 Feb 2021 12:57:52 +
with message-id
and subject line Bug#982498: Removed package(s) from unstable
has caused the Debian Bug report #925024,
regarding Updating the geant321 Uploaders list
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 13 Feb 2021 12:57:52 +
with message-id
and subject line Bug#982498: Removed package(s) from unstable
has caused the Debian Bug report #888539,
regarding geant321: Missing patches due to incomplete quilt conversion?
to be marked as done.
This means that you claim that
Your message dated Sat, 13 Feb 2021 12:57:52 +
with message-id
and subject line Bug#982498: Removed package(s) from unstable
has caused the Debian Bug report #872628,
regarding geant321: gxint fails to spawn interactive geant session
to be marked as done.
This means that you claim that the
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-tur | 0.2.0~r83161-2.1 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-tat | 0.1.0~r60887-2.1 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-szl | 0.1.0-1.1 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
Note
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-swe |0.8.0-2 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
Note
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-srd |1.2.0-1 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
Note
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-rus | 0.2.0~r82706-1.1 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-pol |0.1.1-2 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
Note
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-oci | 0.1.0-1.1 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
Note
Version: 1:3.21.14.dfsg-11+rm
Dear submitter,
as the package geant321 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
geant321 | 1:3.21.14.dfsg-11 | source, all
geant321-data | 1:3.21.14.dfsg-11 | all
geant321-doc | 1:3.21.14.dfsg-11 | all
libgeant321-2-dev | 1:3.21.14.dfsg-11+b6 | amd64, arm64, armel,
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-nob |1.0.0-2 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
Note
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-nno |1.0.0-2 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
Note
Your message dated Sat, 13 Feb 2021 12:55:20 +
with message-id
and subject line Bug#982428: Removed package(s) from unstable
has caused the Debian Bug report #967138,
regarding giella-sme: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Sat, 13 Feb 2021 12:55:03 +
with message-id
and subject line Bug#982427: Removed package(s) from unstable
has caused the Debian Bug report #945643,
regarding giella-core: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-kaz | 0.1.0~r61338-2.1 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
Your message dated Sat, 13 Feb 2021 12:56:01 +
with message-id
and subject line Bug#982446: Removed package(s) from unstable
has caused the Debian Bug report #942911,
regarding apertium-cat: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-hbs | 0.5.0~r68212-3.1 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-fra | 1.5.0-1.1 | source, all
--- Reason ---
ROM; Obsolete by new apertium language pairs
--
Note
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-dan |0.6.0-2 | source, all
--- Reason ---
ROM; Obsolete by newer apertium language pairs, unused
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-crh | 0.2.0~r83161-2.1 | source, all
--- Reason ---
ROM; Obsolete by newer apertium language pair
--
Version: 2.6.0-2+rm
Dear submitter,
as the package apertium-cat has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/982446
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-cat |2.6.0-2 | source, all
--- Reason ---
ROM; Obsolete by newer apertium language pair
--
Note
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-bel | 0.1.0~r81357-3 | source, all
--- Reason ---
ROM; Obsolete by newer apertium language pair
--
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
apertium-arg | 0.1.2~r65494-2.1 | source, all
--- Reason ---
ROM; Obsolete by newer apertium language pairs
--
Version: 0.0.20150917~r121176-3+rm
Dear submitter,
as the package giella-sme has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
giella-sme | 0.0.20150917~r121176-3 | source, all
giella-sme-dev | 0.0.20150917~r121176-3 | all
--- Reason ---
ROM; ROM; RC Buggy, obsolete by new
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
giella-core | 0.1.1~r129227+svn121148-2.1 | source, all
--- Reason ---
ROM; ROM; RC Buggy, obsolete by apertium-sme-nob now
Version: 0.1.1~r129227+svn121148-2.1+rm
Dear submitter,
as the package giella-core has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see
68 matches
Mail list logo
