Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 09 Mar 2021 06:29:09 +0100
Source: debian-science
Architecture: source
Version: 1.14.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Andreas Tille
Changes:
debian-science
debian-science_1.14.1_source.changes uploaded successfully to localhost
along with the files:
debian-science_1.14.1.dsc
debian-science_1.14.1.tar.xz
debian-science_1.14.1_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 09 Mar 2021 00:39:59 +0100
Source: basix
Architecture: source
Version: 0.0.1~git20210305.fe8fada-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Drew Parsons
Changes:
basix_0.0.1~git20210305.fe8fada-1_source.changes uploaded successfully to
localhost
along with the files:
basix_0.0.1~git20210305.fe8fada-1.dsc
basix_0.0.1~git20210305.fe8fada.orig.tar.gz
basix_0.0.1~git20210305.fe8fada-1.debian.tar.xz
Greetings,
Your Debian queue daemon (running
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 24 Feb 2021 18:09:57 +0100
Source: debian-science
Binary: science-all science-biology science-chemistry science-config
science-dataacquisition science-dataacquisition-dev science-datamanagement
Package: scilab-full-bin
Version: 6.1.0+dfsg1-7
Severity: wishlist
In Debian 11 Bullseye (current testing) and Sid, scilab-full-bin is not
available for armhf and i386, but in Debian 10 Buster is avaible.
Perhaps this is due to the limited number of architectures supported by
libjogl2-java:
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 08 Mar 2021 18:37:39 +0100
Source: petsc
Architecture: source
Version: 3.14.5+dfsg1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Drew Parsons
Changes:
petsc
Failed to deliver to '1910132...@qq.com'
SMTP module(domain qq.com) reports:
host mx3.qq.com says:
550 Mailbox unavailable or access denied
[MH0sEYmdVrcdpFPOXZnXAkqk+WrpHzgIM8H0v4RuSH/alAuCFrLQRR3zs11k1wyjnw== IP:
8.19.118.55]
Reporting-MTA: dns; stsh501.appriver.com
Original-Recipient:
petsc_3.14.5+dfsg1-1_source.changes uploaded successfully to localhost
along with the files:
petsc_3.14.5+dfsg1-1.dsc
petsc_3.14.5+dfsg1.orig.tar.xz
petsc_3.14.5+dfsg1-1.debian.tar.xz
petsc_3.14.5+dfsg1-1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host
Your message dated Mon, 08 Mar 2021 17:48:38 +
with message-id
and subject line Bug#983892: fixed in petsc 3.14.4+dfsg1-2
has caused the Debian Bug report #983892,
regarding libpetsc64-complex3.14-dev: leaves alternatives after purge:
/etc/alternatives/*petsc64*
to be marked as done.
This
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 08 Mar 2021 18:27:40 +0100
Source: petsc
Architecture: source
Version: 3.14.4+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Drew Parsons
Closes: 983892
petsc_3.14.4+dfsg1-2_source.changes uploaded successfully to localhost
along with the files:
petsc_3.14.4+dfsg1-2.dsc
petsc_3.14.4+dfsg1-2.debian.tar.xz
petsc_3.14.4+dfsg1-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
#
# bts-link upstream status pull for source package src:mathicgb
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #984231
#
# bts-link upstream status pull for source package src:form
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #984137
#
# bts-link upstream status pull for source package src:libvigraimpex
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #984213
X-Debbugs-CC: pierre.saram...@imag.fr debian-scie...@lists.debian.org
On Thu, 04 Mar 2021 18:31:28 +0100 Andreas Beckmann
wrote:
> Package: rheolef
> Version: 7.1-3
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed
Your message dated Mon, 08 Mar 2021 13:48:25 +
with message-id
and subject line Bug#984785: fixed in apertium-arg-cat 0.2.0-2
has caused the Debian Bug report #984785,
regarding apertium-arg-cat: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 08 Mar 2021 13:48:30 +
with message-id
and subject line Bug#984786: fixed in apertium-separable 0.3.6-2
has caused the Debian Bug report #984786,
regarding apertium-separable: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 08 Mar 2021 17:25:39 +0530
Source: apertium-separable
Architecture: source
Version: 0.3.6-2
Distribution: unstable
Urgency: high
Maintainer: Debian Science Team
Changed-By: Kartik Mistry
Closes: 984786
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 08 Mar 2021 18:03:51 +0530
Source: apertium-arg-cat
Architecture: source
Version: 0.2.0-2
Distribution: unstable
Urgency: high
Maintainer: Debian Science Team
Changed-By: Kartik Mistry
Closes: 984785
Changes:
apertium-separable_0.3.6-2_source.changes uploaded successfully to localhost
along with the files:
apertium-separable_0.3.6-2.dsc
apertium-separable_0.3.6-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
debian-science-maintainers mailing
apertium-arg-cat_0.2.0-2_source.changes uploaded successfully to localhost
along with the files:
apertium-arg-cat_0.2.0-2.dsc
apertium-arg-cat_0.2.0-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
debian-science-maintainers mailing list
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 08 Mar 2021 10:20:15 +
Source: mpich
Binary: libmpich-dev libmpich12 libmpich12-dbgsym mpich mpich-dbgsym mpich-doc
Architecture: source amd64 all
Version: 4.0~a1-1
Distribution: experimental
Urgency: medium
mpich_4.0~a1-1_amd64.changes uploaded successfully to localhost
along with the files:
mpich_4.0~a1-1.dsc
mpich_4.0~a1.orig.tar.xz
mpich_4.0~a1-1.debian.tar.xz
libmpich-dev_4.0~a1-1_amd64.deb
libmpich12-dbgsym_4.0~a1-1_amd64.deb
libmpich12_4.0~a1-1_amd64.deb
d/control wrongly mentions python - it does not need python to build.
Should just be removed.
-- Tino Didriksen
On Mon, 8 Mar 2021 at 12:39, Matthias Klose wrote:
> Package: src:apertium-arg-cat
> Version: 0.2.0-1
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
Whoops. That's an oversight in d/control - it should say python3 instead of
python.
This was fixed upstream last year (
https://github.com/apertium/apertium-separable/issues/28), so I was certain
this must be a bogus bug report - but no, I plain forgot to adjust
d/control.
-- Tino Didriksen
On
Package: src:apertium-separable
Version: 0.3.6-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
Package: src:apertium-arg-cat
Version: 0.2.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
On 2021-03-08 12:07, Drew Parsons wrote:
...
If libpetsc-complex3.14-dev is uninstalling cleanly as intended then
why would libpetsc64-complex3.14-dev not be doing the same?
Likewise, libpetsc64-complex3.14-dev should be behaving the same as
libpetsc64-real3.14-dev. Why is this problem only
Source: petsc
Followup-For: Bug #983892
Control: tags -1 help
I'm looking into this problem. It's not immediately obvious where the
problem ultimately lies for this reason: the petsc64 scripts have been
constructed by analogy (copy) with the correspond petsc
(petsc32) scripts.
The prerm scripts
Processing control commands:
> tags -1 help
Bug #983892 [libpetsc64-complex3.14-dev] libpetsc64-complex3.14-dev: leaves
alternatives after purge: /etc/alternatives/*petsc64*
Added tag(s) help.
--
983892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983892
Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:
> notfixed 888924 2019.1-1
Bug #888924 [libqhull-dev] qhull: backport latest package to stretch
No longer marked as fixed in versions qhull/2019.1-1.
> notfound 888924 2019.1-1
Bug #888924 [libqhull-dev] qhull: backport latest package to stretch
I should add:
dpkg-buildflags manpage does not list DFLAGS as a supported flag, but
explicitly mentioned that more flags might get added in the future if
needed for more languages.
DFLAGS was added with
commit d01d1f49c9734a39fc278f4d5b75444c96491023
Author: Guillem Jover
Date: Fri Nov 27
Package: python-escript
Version: 5.6-2
In my build enviroments, the DFLAGS dpkg-buildflags option is set (to
'-frelease').
python-escript in site_cons/extractdebbuild.py does not know about this
flag but should actually ignore it, AFAICT.
Suggested fix: Add DFLAGS to the ignoreflags list in line
34 matches
Mail list logo