ros-metapackages is marked for autoremoval from testing

ros-metapackages 1.5 is marked for autoremoval from testing on 2016-05-15 It (build-)depends on packages with these RC bugs: 819710: libxdmf-dev: libxdmf-dev and libgzstream-dev: error when trying to install together -- debian-science-maintainers mailing list

fiat is marked for autoremoval from testing

fiat 1.6.0-1 is marked for autoremoval from testing on 2016-04-23 It (build-)depends on packages with these RC bugs: 817789: blockdiag: FTBFS: pep8 module is now in python-pep8 package -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

ffc is marked for autoremoval from testing

ffc 1.6.0-2 is marked for autoremoval from testing on 2016-04-23 It (build-)depends on packages with these RC bugs: 817789: blockdiag: FTBFS: pep8 module is now in python-pep8 package -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#820498: marked as done (tachyon: FTBFS with libpng16 on mipsel)

Your message dated Sun, 10 Apr 2016 01:11:07 + with message-id <20160410011107.ga4...@chase.mapreri.org> and subject line Re: Bug#820498: tachyon: FTBFS with libpng16 on mipsel has caused the Debian Bug report #820498, regarding tachyon: FTBFS with libpng16 on mipsel to be marked as done.

Bug#820429: libvigraimpex: FTBFS on kfreebsd-i386 and hurd-i386: Assertion failed: Sequence items differ at index 5

Hi, Emilio Pozuelo Monfort wrote: > Your package failed to build on hurd and kfreebsd-i386: > > Entering test suite GraphAlgorithmTestSuite > > Failure in GraphAlgorithmTest::testEdgeWeightComputation() > Assertion failed: Sequence items differ at index 5 [4.24264 != 4.24264] >

Processed: found 816116 in 0.8.3-5, tagging 816116, found 820498 in 0.99~b6+dsx-4

Processing commands for cont...@bugs.debian.org: > found 816116 0.8.3-5 Bug #816116 {Done: Gianfranco Costamagna } [libpolybori-dev] libpolybori-dev: Please change dependency from libpng12-dev to libpng-dev Marked as found in versions polybori/0.8.3-5. > tags 816116 +

yosys_0.6-4_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Apr 2016 16:38:20 +0200 Source: yosys Binary: yosys yosys-dev yosys-doc Architecture: source Version: 0.6-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Processed: Re: Bug#820530: pdal: FTBFS because of openmpi

Processing control commands: > severity -1 serious Bug #820530 [src:pdal] pdal: FTBFS because of openmpi Severity set to 'serious' from 'normal' > block -1 by 820113 Bug #820530 [src:pdal] pdal: FTBFS because of openmpi 820530 was not blocked by any bugs. 820530 was not blocking any bugs. Added

Processed: Re: Bug#820113: No rule to make target '/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so'

Processing control commands: > severity -1 serious Bug #820113 [libvtk6-dev] No rule to make target '/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so' Severity set to 'serious' from 'normal' -- 820113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820113 Debian Bug Tracking System

Bug#820113: No rule to make target '/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so'

control: severity -1 serious On Sat, Apr 09, 2016 at 03:06:20PM +, Mattia Rizzolo wrote: > On Tue, Apr 05, 2016 at 04:54:57PM +0200, Jochen Sprickerhof wrote: > > Package: libvtk6-dev > > Version: 6.2.0+dfsg1-11 > > Severity: normal > > > > Dear Maintainer, > > > > the latest vtk6 needs a

Processing of yosys_0.6-4_source.changes

yosys_0.6-4_source.changes uploaded successfully to localhost along with the files: yosys_0.6-4.dsc yosys_0.6-4.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- debian-science-maintainers mailing list

Bug#820113: No rule to make target '/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so'

On Tue, Apr 05, 2016 at 04:54:57PM +0200, Jochen Sprickerhof wrote: > Package: libvtk6-dev > Version: 6.2.0+dfsg1-11 > Severity: normal > > Dear Maintainer, > > the latest vtk6 needs a dependency on libhdf5-openmpi-dev, I guess it's > because rather on libhdf5-mpi-dev -- regards,

Re: Bug#752876: Comments regarding r-cran-spdep_0.5-92-1_amd64.changes

Hi Thorsten, would it be acceptable if I add this text to d/copyright? Kind regards Andreas. On Mon, Apr 04, 2016 at 06:52:24PM +0200, Roger Bivand wrote: > Hi Andreas, > > I have added: > > /* > This code is described in "Computational Geometry in C" (Second Edition), > Chapter 8.

Processing of yosys_0.6-3_source.changes

yosys_0.6-3_source.changes uploaded successfully to localhost along with the files: yosys_0.6-3.dsc yosys_0.6-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- debian-science-maintainers mailing list

Bug#820498: tachyon: FTBFS with libpng16 on mipsel

On Sat, 09 Apr 2016 09:26:58 +0200 Tobias Frost wrote: > Source: tachyon > Severity: serious > Justification: FTBFS but did in the past > > Dear maintainer, > > the package FTBFS with libpng 1.6 on mipsel (release arch) and others > non-release archs (mips64el and sh4) (it

Bug#704206: marked as done (teem: FTBFS[any-i386]: testsuite failures)

Your message dated Sat, 09 Apr 2016 10:04:00 + with message-id and subject line Bug#704206: fixed in teem 1.11.0~svn6057-1.1 has caused the Debian Bug report #704206, regarding teem: FTBFS[any-i386]: testsuite failures to be marked as done. This means

Bug#820503: marked as done (teem: Please enable verbose building)

Your message dated Sat, 09 Apr 2016 10:04:00 + with message-id and subject line Bug#820503: fixed in teem 1.11.0~svn6057-1.1 has caused the Debian Bug report #820503, regarding teem: Please enable verbose building to be marked as done. This means that you

teem_1.11.0~svn6057-1.1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Apr 2016 10:34:39 +0200 Source: teem Binary: libteem-dev teem-apps libteem2 libteem2-dbg Architecture: source Version: 1.11.0~svn6057-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Bug#704206: teem: diff for NMU version 1.11.0~svn6057-1.1

Hi Tobias, dcut ftp-master reschedule -d 0 -f teem_1.11.0~svn6057-1.1_source.changes thanks for the NMU! g. On Sat, 09 Apr 2016 10:36:05 +0200 Tobias Frost wrote: > Control: tags 704206 + pending > Control: tags 820503 + patch > Control: tags 820503 + pending > > Dear

Processing of teem_1.11.0~svn6057-1.1_source.changes

teem_1.11.0~svn6057-1.1_source.changes uploaded successfully to localhost along with the files: teem_1.11.0~svn6057-1.1.dsc teem_1.11.0~svn6057-1.1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- debian-science-maintainers mailing list

Processed: teem: diff for NMU version 1.11.0~svn6057-1.1

Processing control commands: > tags 704206 + pending Bug #704206 [src:teem] teem: FTBFS[any-i386]: testsuite failures Added tag(s) pending. > tags 820503 + patch Bug #820503 [teem] teem: Please enable verbose building Added tag(s) patch. > tags 820503 + pending Bug #820503 [teem] teem: Please

Processed: teem: diff for NMU version 1.11.0~svn6057-1.1

Processing control commands: > tags 704206 + pending Bug #704206 [src:teem] teem: FTBFS[any-i386]: testsuite failures Ignoring request to alter tags of bug #704206 to the same tags previously set > tags 820503 + patch Bug #820503 [teem] teem: Please enable verbose building Ignoring request to

Bug#820503: teem: Please enable verbose building

Package: teem Severity: normal teem uses silent rules, not showing the used compiler options. As some tools at Debian parse the buildlogs for e.g compiler options, please disable silent rules and make a verbose build. Thanks! -- tobi -- System Information: Debian Release: stretch/sid APT

Bug#820498: tachyon: FTBFS with libpng16 on mipsel

Source: tachyon Severity: serious Justification: FTBFS but did in the past Dear maintainer, the package FTBFS with libpng 1.6 on mipsel (release arch) and others non-release archs (mips64el and sh4) (it built on mipsel in the past, so it is RC) Note that hppa also shows a very similar error,