Processing of petsc_3.7.5+dfsg1-2_source.changes

petsc_3.7.5+dfsg1-2_source.changes uploaded successfully to localhost along with the files: petsc_3.7.5+dfsg1-2.dsc petsc_3.7.5+dfsg1-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list

Processing of tango_9.2.5a+dfsg1-1_source.changes

tango_9.2.5a+dfsg1-1_source.changes uploaded successfully to localhost along with the files: tango_9.2.5a+dfsg1-1.dsc tango_9.2.5a+dfsg1.orig.tar.gz tango_9.2.5a+dfsg1-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Bug#851578: python-numba: fails to install: SyntaxError: invalid syntax

Package: python-numba Version: 0.30.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From

petsc_3.7.5+dfsg1-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 16 Jan 2017 21:24:40 +0800 Source: petsc Binary: libpetsc3.7-dev libpetsc3.7.5-dev petsc-dev libpetsc3.7.5 libpetsc3.7.5-dbg petsc3.7.5-doc libpetsc-complex-3.7-dev libpetsc-complex-3.7.5-dev

tango_9.2.5a+dfsg1-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 16 Jan 2017 10:58:19 +0100 Source: tango Binary: liblog4tango5v5 liblog4tango-dev liblog4tango-doc libtango9 libtango-dev libtango-doc libtango-tools tango-common tango-db tango-starter tango-accesscontrol

Bug#848137: marked as done (tango-db: fails to upgrade from 'jessie': mysqldump: tango has insufficent privileges to SHOW CREATE PROCEDURE `class_att_prop`!)

Your message dated Mon, 16 Jan 2017 15:05:40 + with message-id and subject line Bug#848137: fixed in tango 9.2.5a+dfsg1-1 has caused the Debian Bug report #848137, regarding tango-db: fails to upgrade from 'jessie': mysqldump: tango has insufficent

Bug#838112: uctodata: fails to upgrade from 'jessie' - trying to overwrite /etc/ucto/es.abr

Followup-For: Bug #838112 Control: found -1 0.3.1-1 Control: affects -1 + ucto Hi, that bug has just reappered: Preparing to unpack .../ucto_0.9.5-1_amd64.deb ... Unpacking ucto (0.9.5-1) over (0.5.3-3.1+b1) ... dpkg: warning: unable to delete old directory '/etc/ucto': Directory not

Processed: Re: uctodata: fails to upgrade from 'jessie' - trying to overwrite /etc/ucto/es.abr

Processing control commands: > found -1 0.3.1-1 Bug #838112 {Done: Maarten van Gompel } [uctodata] uctodata: fails to upgrade from 'jessie' - trying to overwrite /etc/ucto/es.abr Marked as found in versions uctodata/0.3.1-1 and reopened. > affects -1 + ucto Bug #838112

Processing of yorick-optimpack_1.3.2+dfsg+1.4.0-1_source.changes

yorick-optimpack_1.3.2+dfsg+1.4.0-1_source.changes uploaded successfully to localhost along with the files: yorick-optimpack_1.3.2+dfsg+1.4.0-1.dsc yorick-optimpack_1.3.2+dfsg+1.4.0.orig-optimpack1.tar.xz yorick-optimpack_1.3.2+dfsg+1.4.0.orig.tar.gz

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

Hello Paul > Officially, no, because the documentation says: "If files exist in both > data and scripts, they will both be executed in an unspecified order." > However, the current behavior of dbconfig-common is to first run the > script and then run the admin code and then run the user code. So

yorick-optimpack_1.3.2+dfsg+1.4.0-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 16 Jan 2017 16:46:00 +0100 Source: yorick-optimpack Binary: yorick-optimpack Architecture: source Version: 1.3.2+dfsg+1.4.0-1 Distribution: unstable Urgency: low Maintainer: Debian Science Maintainers

tango_9.2.5a+dfsg1-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 16 Jan 2017 18:17:17 +0100 Source: tango Binary: liblog4tango5v5 liblog4tango-dev liblog4tango-doc libtango9 libtango-dev libtango-doc libtango-tools tango-common tango-db tango-starter tango-accesscontrol

Processing of tango_9.2.5a+dfsg1-2_source.changes

tango_9.2.5a+dfsg1-2_source.changes uploaded successfully to localhost along with the files: tango_9.2.5a+dfsg1-2.dsc tango_9.2.5a+dfsg1-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list

Processing of r-cran-spdep_0.6-9-1_amd64.changes

r-cran-spdep_0.6-9-1_amd64.changes uploaded successfully to localhost along with the files: r-cran-spdep_0.6-9-1.dsc r-cran-spdep_0.6-9.orig.tar.gz r-cran-spdep_0.6-9-1.debian.tar.xz r-cran-spdep-dbgsym_0.6-9-1_amd64.deb r-cran-spdep_0.6-9-1_amd64.buildinfo

vmtk is marked for autoremoval from testing

vmtk 1.3+dfsg-2 is marked for autoremoval from testing on 2017-02-01 It is affected by these RC bugs: 850026: vmtk: transitive B-D on both libssl-dev and libssl1.0-dev -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

theano is marked for autoremoval from testing

theano 0.8.2-3 is marked for autoremoval from testing on 2017-02-01 It is affected by these RC bugs: 848764: theano: FTBFS: Test failures -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

paraview is marked for autoremoval from testing

paraview 5.1.2+dfsg1-1 is marked for autoremoval from testing on 2017-01-26 It is affected by these RC bugs: 845887: paraview: switch to build depend on the metapackage default-libmysqlclient-dev -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

sfepy is marked for autoremoval from testing

sfepy 2016.2-2 is marked for autoremoval from testing on 2017-02-09 It (build-)depends on packages with these RC bugs: 840823: execnet: testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen] FAILED 846771: python-traits: FTBFS: dh_auto_test: pybuild --test -i

K

Can we talk -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

Hi Frederic-Emmanuel, On 01/16/17 18:10, PICCA Frederic-Emmanuel wrote: >> Officially, no, because the documentation says: "If files exist in both >> data and scripts, they will both be executed in an unspecified order." >> However, the current behavior of dbconfig-common is to first run the >>

Bug#838112: uctodata: fails to upgrade from 'jessie' - trying to overwrite /etc/ucto/es.abr

Quoting Andreas Beckmann (2017-01-16 17:24:19) > Followup-For: Bug #838112 > Control: found -1 0.3.1-1 > Control: affects -1 + ucto > > that bug has just reappered: > > Preparing to unpack .../ucto_0.9.5-1_amd64.deb ... > Unpacking ucto (0.9.5-1) over (0.5.3-3.1+b1) ... > dpkg: warning:

peace Of The Lord Be With You And Your Family

Dear friend, I am Mrs Alice Banneth from Burkina Faso are you online? I have important issue to discus with you. Reply to my private email address : (mrsalicebanne...@yahoo.com) -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

ignition-msgs_0.6.1-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Jan 2017 00:03:26 + Source: ignition-msgs Binary: libignition-msgs0 libignition-msgs-dev Architecture: source Version: 0.6.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Processing of ignition-msgs_0.6.1-1_source.changes

ignition-msgs_0.6.1-1_source.changes uploaded successfully to localhost along with the files: ignition-msgs_0.6.1-1.dsc ignition-msgs_0.6.1.orig.tar.bz2 ignition-msgs_0.6.1-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) --

r-cran-spatstat 1.48-0-1 MIGRATED to testing

FYI: The status of the r-cran-spatstat source package in Debian's testing distribution has changed. Previous version: 1.47-0-1 Current version: 1.48-0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

r-cran-plotrix 3.6-4-1 MIGRATED to testing

FYI: The status of the r-cran-plotrix source package in Debian's testing distribution has changed. Previous version: 3.6-3-1 Current version: 3.6-4-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

python-escript 5.0-2 MIGRATED to testing

FYI: The status of the python-escript source package in Debian's testing distribution has changed. Previous version: 5.0-1 Current version: 5.0-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

fenics 1:2016.2.0.1 MIGRATED to testing

FYI: The status of the fenics source package in Debian's testing distribution has changed. Previous version: 1:1.5.0.1 Current version: 1:2016.2.0.1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

r-cran-jsonlite 1.2-1 MIGRATED to testing

FYI: The status of the r-cran-jsonlite source package in Debian's testing distribution has changed. Previous version: 1.1-2 Current version: 1.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

r-cran-pbdzmq 0.2.5+dfsg-1 MIGRATED to testing

FYI: The status of the r-cran-pbdzmq source package in Debian's testing distribution has changed. Previous version: 0.2.4+dfsg-1 Current version: 0.2.5+dfsg-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day

petsc 3.7.4+dfsg1-9 MIGRATED to testing

FYI: The status of the petsc source package in Debian's testing distribution has changed. Previous version: 3.7.4+dfsg1-8 Current version: 3.7.4+dfsg1-9 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you