keras 2.1.5-1 MIGRATED to testing

FYI: The status of the keras source package in Debian's testing distribution has changed. Previous version: 2.1.1-1 Current version: 2.1.5-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

dune-pdelab is marked for autoremoval from testing

dune-pdelab 2.5.0~rc1-2 is marked for autoremoval from testing on 2018-04-07 It (build-)depends on packages with these RC bugs: 891151: dune-uggrid: dune-uggrid FTBFS with cmake 3.10.2-1 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

dune-grid-glue is marked for autoremoval from testing

dune-grid-glue 2.5.0-1 is marked for autoremoval from testing on 2018-04-07 It (build-)depends on packages with these RC bugs: 891151: dune-uggrid: dune-uggrid FTBFS with cmake 3.10.2-1 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

bcolz is marked for autoremoval from testing

bcolz 1.1.0+ds1-5 is marked for autoremoval from testing on 2018-04-15 It is affected by these RC bugs: 893273: bcolz: FTBFS and Debci failure -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

dune-functions is marked for autoremoval from testing

dune-functions 2.5.1-1 is marked for autoremoval from testing on 2018-04-07 It (build-)depends on packages with these RC bugs: 891151: dune-uggrid: dune-uggrid FTBFS with cmake 3.10.2-1 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

dune-uggrid is marked for autoremoval from testing

dune-uggrid 2.5.1-1 is marked for autoremoval from testing on 2018-04-07 It is affected by these RC bugs: 891151: dune-uggrid: dune-uggrid FTBFS with cmake 3.10.2-1 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

dune-grid is marked for autoremoval from testing

dune-grid 2.5.1-1 is marked for autoremoval from testing on 2018-04-07 It (build-)depends on packages with these RC bugs: 891151: dune-uggrid: dune-uggrid FTBFS with cmake 3.10.2-1 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#893869: marked as done (libgl2ps1.4: please pull latest version for VTK support)

Your message dated Sat, 24 Mar 2018 22:19:51 + with message-id and subject line Bug#893869: fixed in gl2ps 1.4.0+dfsg1-2 has caused the Debian Bug report #893869, regarding libgl2ps1.4: please pull latest version for VTK support to be marked as done. This

Accepted gl2ps 1.4.0+dfsg1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 23:09:42 +0100 Source: gl2ps Binary: libgl2ps-dev libgl2ps1.4 libgl2ps-doc Architecture: source Version: 1.4.0+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

gl2ps_1.4.0+dfsg1-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 23:09:42 +0100 Source: gl2ps Binary: libgl2ps-dev libgl2ps1.4 libgl2ps-doc Architecture: source Version: 1.4.0+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Bug#876410: libgl2ps1: please include support for SOURCE_DATE_EPOCH

Hi Mike, thanks for the bugreport. I do not think, that adding the fixed timestamp to all files produced by the gl2os that is what the users want. Regards Anton 2017-09-21 22:28 GMT+02:00 Mike Miller : > Package: libgl2ps1 > Version: 1.3.9-4 > Severity: wishlist > Tags:

Processing of gl2ps_1.4.0+dfsg1-2_source.changes

gl2ps_1.4.0+dfsg1-2_source.changes uploaded successfully to localhost along with the files: gl2ps_1.4.0+dfsg1-2.dsc gl2ps_1.4.0+dfsg1-2.debian.tar.xz gl2ps_1.4.0+dfsg1-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Processing of openctm_1.0.3+dfsg1-2_source.changes

openctm_1.0.3+dfsg1-2_source.changes uploaded successfully to localhost along with the files: openctm_1.0.3+dfsg1-2.dsc openctm_1.0.3+dfsg1-2.debian.tar.xz openctm_1.0.3+dfsg1-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Accepted openctm 1.0.3+dfsg1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 19:01:59 +0200 Source: openctm Binary: libopenctm-dev libopenctm1 openctm-tools python-openctm openctm-doc Architecture: source Version: 1.0.3+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian

openctm_1.0.3+dfsg1-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 19:01:59 +0200 Source: openctm Binary: libopenctm-dev libopenctm1 openctm-tools python-openctm openctm-doc Architecture: source Version: 1.0.3+dfsg1-2 Distribution: unstable Urgency: medium Maintainer:

Accepted optlang 1.4.0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 24 Mar 2018 14:59:06 -0400 Source: optlang Binary: python-optlang python3-optlang Architecture: source Version: 1.4.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Processing of optlang_1.4.0-1_source.changes

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

optlang_1.4.0-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 24 Mar 2018 14:59:06 -0400 Source: optlang Binary: python-optlang python3-optlang Architecture: source Version: 1.4.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Bug#893783: spyder3: does not start even after --reset

On Thu, 22 Mar 2018 10:47:17 + Jitse Niesen wrote: > I don't know the root cause, but it seems to be an incompatibility > between python-tornado and pyzmq and possibly jupyter-client, caused by > a change in tornado version 5. Maybe pyzmq needs to be at least version

Accepted r-cran-coin 1.2-2-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 15:26:21 +0100 Source: r-cran-coin Binary: r-cran-coin Architecture: source Version: 1.2-2-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

r-cran-coin_1.2-2-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 15:26:21 +0100 Source: r-cran-coin Binary: r-cran-coin Architecture: source Version: 1.2-2-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Bug#887682: r-cran-utf8: FTBFS on m68k: missing value where TRUE/FALSE needed

Hi Aaron, On Thu, 18 Jan 2018 21:33:47 -0500 "Aaron M. Ucko" wrote: > The build of r-cran-utf8 for m68k (admittedly not a release > architecture) failed: > > Error in if (any(i)) x[i] <- paste0(x[i], "\n", indentString) : > missing value where TRUE/FALSE needed > ERROR:

Processing of r-cran-coin_1.2-2-2_source.changes

r-cran-coin_1.2-2-2_source.changes uploaded successfully to localhost along with the files: r-cran-coin_1.2-2-2.dsc r-cran-coin_1.2-2.orig.tar.gz r-cran-coin_1.2-2-2.debian.tar.xz r-cran-coin_1.2-2-2_amd64.buildinfo Greetings, Your Debian queue daemon (running on host

Bug#882555: r-cran-ddalpha: FTBFS on m68k: no boost::math::Rlog1p

Hi Aaron, On Thu, 23 Nov 2017 16:54:33 -0500 "Aaron M. Ucko" wrote: > The build of r-cran-ddalpha for m68k (admittedly not a release > architecture) failed: > > g++ -std=gnu++11 -I/usr/share/R/include -DNDEBUG > -I"/usr/lib/R/site-library/Rcpp/include"-fpic -g -O2 >

Bug#887680: r-cran-git2r: FTBFS on m68k: missing value where TRUE/FALSE needed

Hi Aaron, On Thu, 18 Jan 2018 21:05:31 -0500 "Aaron M. Ucko" wrote: > The build of r-cran-git2r for m68k (admittedly not a release > architecture) failed: > > Error in if (nc[currentIndex] == 0L) upperBlockIndex <- c(upperBlockIndex, > : > missing value where TRUE/FALSE

Accepted r-cran-mcmcpack 1.4-2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 14:24:55 +0100 Source: r-cran-mcmcpack Binary: r-cran-mcmcpack Architecture: source Version: 1.4-2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

r-cran-mcmcpack_1.4-2-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 14:24:55 +0100 Source: r-cran-mcmcpack Binary: r-cran-mcmcpack Architecture: source Version: 1.4-2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Processing of r-cran-mcmcpack_1.4-2-1_source.changes

r-cran-mcmcpack_1.4-2-1_source.changes uploaded successfully to localhost along with the files: r-cran-mcmcpack_1.4-2-1.dsc r-cran-mcmcpack_1.4-2.orig.tar.gz r-cran-mcmcpack_1.4-2-1.debian.tar.xz r-cran-mcmcpack_1.4-2-1_source.buildinfo Greetings, Your Debian queue daemon

Bug#888219: marked as done (ignition-math4: FTBFS on *i386: OrientedBoxTest.OperatorStreamOut fails)

Your message dated Sat, 24 Mar 2018 13:34:56 + with message-id and subject line Bug#888219: fixed in ignition-math4 4.0.0+dfsg1-4 has caused the Debian Bug report #888219, regarding ignition-math4: FTBFS on *i386: OrientedBoxTest.OperatorStreamOut fails

Accepted ignition-math4 4.0.0+dfsg1-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 13:16:33 + Source: ignition-math4 Binary: libignition-math4 libignition-math4-dev Architecture: source Version: 4.0.0+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

ignition-math4_4.0.0+dfsg1-4_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 13:16:33 + Source: ignition-math4 Binary: libignition-math4 libignition-math4-dev Architecture: source Version: 4.0.0+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Debian Science

Processing of ignition-math4_4.0.0+dfsg1-4_source.changes

ignition-math4_4.0.0+dfsg1-4_source.changes uploaded successfully to localhost along with the files: ignition-math4_4.0.0+dfsg1-4.dsc ignition-math4_4.0.0+dfsg1-4.debian.tar.xz ignition-math4_4.0.0+dfsg1-4_source.buildinfo Greetings, Your Debian queue daemon (running on host

r-cran-erm_0.16-0-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 13:35:23 +0100 Source: r-cran-erm Binary: r-cran-erm Architecture: source Version: 0.16-0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Accepted r-cran-erm 0.16-0-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 13:35:23 +0100 Source: r-cran-erm Binary: r-cran-erm Architecture: source Version: 0.16-0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Processing of r-cran-erm_0.16-0-1_source.changes

r-cran-erm_0.16-0-1_source.changes uploaded successfully to localhost along with the files: r-cran-erm_0.16-0-1.dsc r-cran-erm_0.16-0.orig.tar.gz r-cran-erm_0.16-0-1.debian.tar.xz r-cran-erm_0.16-0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host

Bug#892572: marked as done (gazebo9: fails to start due to missing symbol in libgazebo_rendering.so.9)

Your message dated Sat, 24 Mar 2018 14:03:17 +0100 with message-id <369bbaf0-26fe-dab7-59e5-b709f094d...@openrobotics.org> and subject line Re: Bug#892573: gazebo9: fails to start due to missing symbol in libgazebo_rendering.so.9 has caused the Debian Bug report #892573, regarding gazebo9: fails

Bug#892573: marked as done (gazebo9: fails to start due to missing symbol in libgazebo_rendering.so.9)

Your message dated Sat, 24 Mar 2018 14:03:17 +0100 with message-id <369bbaf0-26fe-dab7-59e5-b709f094d...@openrobotics.org> and subject line Re: Bug#892573: gazebo9: fails to start due to missing symbol in libgazebo_rendering.so.9 has caused the Debian Bug report #892573, regarding gazebo9: fails

Bug#893692: marked as done (bcolz: uses pybuild's internal paths)

Your message dated Sat, 24 Mar 2018 10:49:31 + with message-id and subject line Bug#893692: fixed in bcolz 1.2.0+ds1-1 has caused the Debian Bug report #893692, regarding bcolz: uses pybuild's internal paths to be marked as done. This means that you claim

Accepted bcolz 1.2.0+ds1-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 11:31:55 +0100 Source: bcolz Binary: python-bcolz python3-bcolz bcolz-doc Architecture: all source Version: 1.2.0+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

bcolz_1.2.0+ds1-1_multi.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 11:31:55 +0100 Source: bcolz Binary: python-bcolz python3-bcolz bcolz-doc Architecture: all source Version: 1.2.0+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Processing of bcolz_1.2.0+ds1-1_multi.changes

bcolz_1.2.0+ds1-1_multi.changes uploaded successfully to localhost along with the files: bcolz_1.2.0+ds1-1.dsc bcolz_1.2.0+ds1.orig.tar.xz bcolz_1.2.0+ds1-1.debian.tar.xz bcolz-doc_1.2.0+ds1-1_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Bug#892573: gazebo9: fails to start due to missing symbol in libgazebo_rendering.so.9

Gazebo starts successfully with the new version of ignition-msgs; the bug can be closed. Thanks! On Fri, Mar 23, 2018 at 8:24 AM, Jose Luis Rivero wrote: > I run a gazebo9 installation inside our buildfarm and run gazebo for a few > seconds to confirm that it can not

Bug#857414: marked as done (r-cran-bayesm: broken symlinks: /usr/share/doc/r-cran-bayesm/{Some_Useful_R_Pointers.pdf, Tips_On_Using_bayesm.pdf})

Your message dated Sat, 24 Mar 2018 09:30:10 + with message-id and subject line Bug#857414: fixed in r-cran-bayesm 3.1-0.1-2 has caused the Debian Bug report #857414, regarding r-cran-bayesm: broken symlinks:

silx_0.7.0+dfsg-2~bpo9+1_source.changes ACCEPTED into stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 09:18:23 +0100 Source: silx Binary: silx python-silx python-silx-dbg python3-silx python3-silx-dbg python-silx-doc Architecture: source Version: 0.7.0+dfsg-2~bpo9+1 Distribution: stretch-backports

Accepted silx 0.7.0+dfsg-2~bpo9+1 (source) into stretch-backports

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 09:18:23 +0100 Source: silx Binary: silx python-silx python-silx-dbg python3-silx python3-silx-dbg python-silx-doc Architecture: source Version: 0.7.0+dfsg-2~bpo9+1 Distribution: stretch-backports Urgency: medium

Bug#893273: marked as done (bcolz: FTBFS and Debci failure)

Your message dated Sat, 24 Mar 2018 09:26:54 + with message-id and subject line Bug#893273: fixed in bcolz 1.1.2+ds1-1 has caused the Debian Bug report #893273, regarding bcolz: FTBFS and Debci failure to be marked as done. This means that you claim that

r-cran-bayesm_3.1-0.1-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 24 Mar 2018 08:15:42 +0100 Source: r-cran-bayesm Binary: r-cran-bayesm Architecture: source Version: 3.1-0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Accepted r-cran-bayesm 3.1-0.1-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 24 Mar 2018 08:15:42 +0100 Source: r-cran-bayesm Binary: r-cran-bayesm Architecture: source Version: 3.1-0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Accepted bcolz 1.1.2+ds1-1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 09:02:12 +0100 Source: bcolz Binary: python-bcolz python3-bcolz bcolz-doc Architecture: all source Version: 1.1.2+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

bcolz_1.1.2+ds1-1_multi.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Mar 2018 09:02:12 +0100 Source: bcolz Binary: python-bcolz python3-bcolz bcolz-doc Architecture: all source Version: 1.1.2+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Processing of silx_0.7.0+dfsg-2~bpo9+1_source.changes

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

Processing of bcolz_1.1.2+ds1-1_multi.changes

bcolz_1.1.2+ds1-1_multi.changes uploaded successfully to localhost along with the files: bcolz_1.1.2+ds1-1.dsc bcolz_1.1.2+ds1.orig.tar.xz bcolz_1.1.2+ds1-1.debian.tar.xz bcolz-doc_1.1.2+ds1-1_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Bug#816424: Failed to replace libuv1 in r-cran-httpuv

Control: tags -1 help Hi, I tried to follow the advise given in bug #816424 and commited an according change to r-cran-httpuv Git[1]. Unfortunately this ends up in a series of errors like this: http.cpp: In member function 'void HttpRequest::_on_request_read(uv_stream_t*, ssize_t, uv_buf_t)':

Processed: Failed to replace libuv1 in r-cran-httpuv

Processing control commands: > tags -1 help Bug #816424 [src:r-cran-httpuv] r-cran-httpuv: FTBFS on non-Linux: 'src/unix/async.o' failed Added tag(s) help. -- 816424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processing of r-cran-bayesm_3.1-0.1-2_source.changes

r-cran-bayesm_3.1-0.1-2_source.changes uploaded successfully to localhost along with the files: r-cran-bayesm_3.1-0.1-2.dsc r-cran-bayesm_3.1-0.1-2.debian.tar.xz r-cran-bayesm_3.1-0.1-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --