FYI: The status of the psimd source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.0~git20200417.85427dd-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple
FYI: The status of the opencascade source package
in Debian's testing distribution has changed.
Previous version: 7.3.3+dfsg1-2
Current version: 7.4.1+dfsg1-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
FYI: The status of the lbt source package
in Debian's testing distribution has changed.
Previous version: 1.2.2-6
Current version: 1.2.2-7
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
FYI: The status of the fxdiv source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.0~git20200417.b408327-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple
FYI: The status of the brial source package
in Debian's testing distribution has changed.
Previous version: 1.2.7-1
Current version: 1.2.8-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
FYI: The status of the deal.ii source package
in Debian's testing distribution has changed.
Previous version: 9.1.1-9
Current version: 9.1.1-10
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
deal.ii 9.1.1-10 is marked for autoremoval from testing on 2020-05-23
It is affected by these RC bugs:
956371: deal.ii: FTBFS with opencascade 7.4 (library transistion)
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
FYI: The status of the auto-07p source package
in Debian's testing distribution has changed.
Previous version: 0.9.2+dfsg-2
Current version: 0.9.2+dfsg-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
binary:libipe7.2.16 is NEW.
binary:libipe7.2.16 is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
Packages are routinely
ipe_7.2.16-1_amd64.changes uploaded successfully to localhost
along with the files:
ipe_7.2.16-1.dsc
ipe_7.2.16.orig.tar.gz
ipe_7.2.16-1.debian.tar.xz
ipe-dbgsym_7.2.16-1_amd64.deb
ipe_7.2.16-1_amd64.buildinfo
ipe_7.2.16-1_amd64.deb
libipe-dev_7.2.16-1_amd64.deb
Your message dated Sat, 02 May 2020 21:04:17 +
with message-id
and subject line Bug#956359: fixed in netgen 6.2.1804+dfsg1-3.1
has caused the Debian Bug report #956359,
regarding netgen: FTBFS with new opencascade 7.4 (library transistion)
to be marked as done.
This means that you claim that
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 27 Apr 2020 22:01:24 +0200
Source: netgen
Architecture: source
Version: 6.2.1804+dfsg1-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Tobias Frost
Closes: 956359
Your message dated Sat, 02 May 2020 20:58:18 +
with message-id
and subject line Bug#959371: Removed package(s) from unstable
has caused the Debian Bug report #923417,
regarding pspp: CVE-2019-9211
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 02 May 2020 20:58:18 +
with message-id
and subject line Bug#959371: Removed package(s) from unstable
has caused the Debian Bug report #932951,
regarding pspp build-depends on cruft package.
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 02 May 2020 20:58:18 +
with message-id
and subject line Bug#959371: Removed package(s) from unstable
has caused the Debian Bug report #942609,
regarding pspp: build with -O2 to avoid misbuild with CFLAGS=-O3
to be marked as done.
This means that you claim that the
Your message dated Sat, 02 May 2020 20:58:18 +
with message-id
and subject line Bug#959371: Removed package(s) from unstable
has caused the Debian Bug report #937328,
regarding pspp: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Version: 1.2.0-3+rm
Dear submitter,
as the package pspp 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/959371
The
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
pspp |1.2.0-3 | source
pspp | 1.2.0-3+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel,
ppc64el, s390x
--- Reason ---
RoQA; RC
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 02 May 2020 20:41:19 +0200
Source: glm
Architecture: source
Version: 0.9.9.8+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Carsten Schoenert
Changes:
glm
glm_0.9.9.8+ds-1_source.changes uploaded successfully to localhost
along with the files:
glm_0.9.9.8+ds-1.dsc
glm_0.9.9.8+ds.orig.tar.xz
glm_0.9.9.8+ds-1.debian.tar.xz
glm_0.9.9.8+ds-1_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Your message dated Sat, 02 May 2020 17:18:38 +
with message-id
and subject line Bug#959378: fixed in gap-guava 3.15+ds-2
has caused the Debian Bug report #959378,
regarding gap-guava-bin: please update for new GAP ABI
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 02 May 2020 14:39:35 +
with message-id
and subject line Bug#958114: fixed in libsvm 3.24+ds-4
has caused the Debian Bug report #958114,
regarding can not use because commonutil can not be imported
to be marked as done.
This means that you claim that the problem has
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 02 May 2020 10:12:38 +0200
Source: libsvm
Architecture: source
Version: 3.24+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Christian Kastner
Closes: 958114
libsvm_3.24+ds-4_source.changes uploaded successfully to localhost
along with the files:
libsvm_3.24+ds-4.dsc
libsvm_3.24+ds-4.debian.tar.xz
libsvm_3.24+ds-4_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
debian-science-maintainers
Your message dated Sat, 02 May 2020 13:18:31 +
with message-id
and subject line Bug#958641: fixed in liblinear 2.3.0+dfsg-4
has caused the Debian Bug report #958641,
regarding can not use because commonutil can not be imported
to be marked as done.
This means that you claim that the problem
libsvm_3.24+ds-4.dsc: Invalid size hash for libsvm_3.24+ds.orig.tar.xz:
According to the control file the size hash should be 146268,
but libsvm_3.24+ds.orig.tar.xz has 145976.
If you did not include libsvm_3.24+ds.orig.tar.xz in your upload, a different
version
might already be known to the
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 02 May 2020 10:10:18 +0200
Source: liblinear
Architecture: source
Version: 2.3.0+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Christian Kastner
Closes: 958641
libsvm_3.24+ds-4_source.changes uploaded successfully to localhost
along with the files:
libsvm_3.24+ds-4.dsc
libsvm_3.24+ds-4.debian.tar.xz
libsvm_3.24+ds-4_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
debian-science-maintainers
liblinear_2.3.0+dfsg-4_source.changes uploaded successfully to localhost
along with the files:
liblinear_2.3.0+dfsg-4.dsc
liblinear_2.3.0+dfsg-4.debian.tar.xz
liblinear_2.3.0+dfsg-4_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Hi Christian,
I eventually filed an issue with the PyPI maintainer on GitHub [1] with
a request for them to resolve this with upstream directly, as that
seemed to be the most appropriate course of action.
Thanks for reporting the issue. Should I open a sister-issue on libsvm upstream
GitHub
Service Web universitaire
Attention !!
Nous sommes actuellement en train de traiter tous les comptes de
messagerie. Pour ce faire, vous devez répondre immédiatement à cet
e-mail pour confirmer votre compte contre les logiciels espions et les
spams, vous devrez utiliser les liens suivants.
Your message dated Sat, 02 May 2020 10:04:05 +
with message-id
and subject line Bug#949540: fixed in tango 9.3.4~rc4+dfsg1-1~exp1
has caused the Debian Bug report #949540,
regarding libtango-tools: Move tango_admin into a directory in $PATH
to be marked as done.
This means that you claim
Your message dated Sat, 02 May 2020 10:04:06 +
with message-id
and subject line Bug#949549: fixed in tango 9.3.4~rc4+dfsg1-1~exp1
has caused the Debian Bug report #949549,
regarding tango-accesscontrol: Does not use hardening flags for compilation
to be marked as done.
This means that you
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 02 May 2020 11:40:18 +0200
Source: tango
Architecture: source
Version: 9.3.4~rc4+dfsg1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Picca Frédéric-Emmanuel
tango_9.3.4~rc4+dfsg1-1~exp1_source.changes uploaded successfully to localhost
along with the files:
tango_9.3.4~rc4+dfsg1-1~exp1.dsc
tango_9.3.4~rc4+dfsg1.orig.tar.xz
tango_9.3.4~rc4+dfsg1-1~exp1.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
reprounzip 1.0.10-1 is marked for autoremoval from testing on 2020-05-05
It is affected by these RC bugs:
950839: reprounzip: reprounzip autopkg test fails with python 3.8
951957: reprounzip: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.8 3.7" returned exit code 13
--
Processing control commands:
> tag -1 pending
Bug #958114 [python3-libsvm] can not use because commonutil can not be imported
Added tag(s) pending.
--
958114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
Your message dated Sat, 02 May 2020 08:36:19 +
with message-id
and subject line Bug#959366: fixed in seaborn 0.10.1-1
has caused the Debian Bug report #959366,
regarding python3-seaborn: Allow fallback to scipy when statsmodels is present
and issues runtime errors
to be marked as done.
This
binary:libqnnpack-dev is NEW.
binary:libqnnpack0 is NEW.
binary:libqnnpack0 is NEW.
binary:libqnnpack-dev is NEW.
source:qnnpack is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 02 May 2020 10:00:57 +0200
Source: seaborn
Architecture: source
Version: 0.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Andreas Tille
Closes: 959366
Changes:
Hi Tiziano,
On 2020-04-24 12:37, Tiziano Zito wrote:
>> In any case, the official version has certainly seen far more widespread
>> use than the PyPI version (the former being around for a decade, the
>> latter for a few months), so we need to be aware that changing this
>> might break a lot of
qnnpack_0.0~git20190828.7d2a4e9-1_amd64.changes uploaded successfully to
localhost
along with the files:
qnnpack_0.0~git20190828.7d2a4e9-1.dsc
qnnpack_0.0~git20190828.7d2a4e9.orig.tar.xz
qnnpack_0.0~git20190828.7d2a4e9-1.debian.tar.xz
libqnnpack-dev_0.0~git20190828.7d2a4e9-1_amd64.deb
seaborn_0.10.1-1_source.changes uploaded successfully to localhost
along with the files:
seaborn_0.10.1-1.dsc
seaborn_0.10.1.orig.tar.gz
seaborn_0.10.1-1.debian.tar.xz
seaborn_0.10.1-1_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
43 matches
Mail list logo
