Bug#816423: marked as done (ros-simulators{,-dev}: update dependency to gazebo7)

Your message dated Wed, 2 Mar 2016 08:25:23 +0100 with message-id <20160302072523.ga25...@vis.informatik.uni-osnabrueck.de> and subject line closing has caused the Debian Bug report #816423, regarding ros-simulators{,-dev}: update dependency to gazebo7 to be marked as done. This means that you

apertium-nno-nob_1.1.0~r66076-1_amd64.changes is NEW

binary:apertium-nno-nob is NEW. source:apertium-nno-nob 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

Processing of apertium-nno-nob_1.1.0~r66076-1_amd64.changes

apertium-nno-nob_1.1.0~r66076-1_amd64.changes uploaded successfully to localhost along with the files: apertium-nno-nob_1.1.0~r66076-1.dsc apertium-nno-nob_1.1.0~r66076.orig.tar.bz2 apertium-nno-nob_1.1.0~r66076-1.debian.tar.xz apertium-nno-nob_1.1.0~r66076-1_all.deb Greetings,

r-cran-tm_0.6-2-2~bpo8+1_amd64.changes is NEW

binary:r-cran-tm is NEW. source:r-cran-tm 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

r-cran-nlp_0.1-9-1~bpo8+1_amd64.changes is NEW

binary:r-cran-nlp is NEW. source:r-cran-nlp 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

r-cran-lubridate_1.5.0-2~bpo8+1_amd64.changes is NEW

binary:r-cran-lubridate is NEW. source:r-cran-lubridate 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

r-cran-glmnet_2.0-2-2~bpo8+1_amd64.changes is NEW

binary:r-cran-glmnet is NEW. source:r-cran-glmnet 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

r-cran-arm_1.8-6-2~bpo8+1_amd64.changes is NEW

binary:r-cran-arm is NEW. source:r-cran-arm 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

Processing of r-cran-glmnet_2.0-2-2~bpo8+1_amd64.changes

r-cran-glmnet_2.0-2-2~bpo8+1_amd64.changes uploaded successfully to localhost along with the files: r-cran-glmnet_2.0-2-2~bpo8+1.dsc r-cran-glmnet_2.0-2-2~bpo8+1.debian.tar.xz r-cran-glmnet_2.0-2-2~bpo8+1_amd64.deb Greetings, Your Debian queue daemon (running on host

Processing of r-cran-nlp_0.1-9-1~bpo8+1_amd64.changes

r-cran-nlp_0.1-9-1~bpo8+1_amd64.changes uploaded successfully to localhost along with the files: r-cran-nlp_0.1-9-1~bpo8+1.dsc r-cran-nlp_0.1-9-1~bpo8+1.debian.tar.xz r-cran-nlp_0.1-9-1~bpo8+1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) --

Processing of r-cran-arm_1.8-6-2~bpo8+1_amd64.changes

r-cran-arm_1.8-6-2~bpo8+1_amd64.changes uploaded successfully to localhost along with the files: r-cran-arm_1.8-6-2~bpo8+1.dsc r-cran-arm_1.8-6-2~bpo8+1.debian.tar.xz r-cran-arm_1.8-6-2~bpo8+1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) --

Processing of r-cran-lubridate_1.5.0-2~bpo8+1_amd64.changes

r-cran-lubridate_1.5.0-2~bpo8+1_amd64.changes uploaded successfully to localhost along with the files: r-cran-lubridate_1.5.0-2~bpo8+1.dsc r-cran-lubridate_1.5.0-2~bpo8+1.debian.tar.xz r-cran-lubridate_1.5.0-2~bpo8+1_amd64.deb Greetings, Your Debian queue daemon (running on host

Processing of r-cran-tm_0.6-2-2~bpo8+1_amd64.changes

r-cran-tm_0.6-2-2~bpo8+1_amd64.changes uploaded successfully to localhost along with the files: r-cran-tm_0.6-2-2~bpo8+1.dsc r-cran-tm_0.6-2-2~bpo8+1.debian.tar.xz r-cran-tm_0.6-2-2~bpo8+1_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) --

Bug#812867: marked as done (Can't open perl script "/usr/share/doc/vtk-doc/html/doc_header2doxygen.pl")

Your message dated Wed, 02 Mar 2016 00:58:55 +0100 with message-id <1456876735.19843.14.ca...@gmail.com> and subject line Re: Can't open perl script "/usr/share/doc/vtk-doc/html/doc_header2doxygen.pl" has caused the Debian Bug report #812867, regarding Can't open perl script

Bug#814970: FTBFS: libpng12.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainers: A bunch of packages are flagged for removal because they depend on libm4ri: do you plan to fix this minor before the dead line [20160401] ? Thanks, Jerome -BEGIN PGP SIGNATURE- Version: GnuPG v2

Bug#815795: marked as done (libvigraimpex6: misses Breaks: libvigraimpex5v5 (>= 1.10.0+git20160120.803d5d4-1))

Your message dated Tue, 01 Mar 2016 23:22:18 + with message-id and subject line Bug#815795: fixed in libvigraimpex 1.10.0+git20160211.167be93-2 has caused the Debian Bug report #815795, regarding libvigraimpex6: misses Breaks: libvigraimpex5v5 (>=

Bug#814606: marked as done (libvigraimpex: FTBFS on armel (error: return type 'class std::future'))

Your message dated Tue, 01 Mar 2016 23:22:18 + with message-id and subject line Bug#814606: fixed in libvigraimpex 1.10.0+git20160211.167be93-2 has caused the Debian Bug report #814606, regarding libvigraimpex: FTBFS on armel (error: return type 'class

Bug#812850: marked as done (libvigraimpex: fail of test/impex)

Your message dated Tue, 01 Mar 2016 23:22:18 + with message-id and subject line Bug#812850: fixed in libvigraimpex 1.10.0+git20160211.167be93-2 has caused the Debian Bug report #812850, regarding libvigraimpex: fail of test/impex to be marked as done.

libvigraimpex_1.10.0+git20160211.167be93-2_multi.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 01 Mar 2016 23:32:30 +0100 Source: libvigraimpex Binary: libvigraimpex-dev libvigraimpex6 libvigraimpex-doc python-vigra python-vigra-doc Architecture: all source Version: 1.10.0+git20160211.167be93-2

Processing of libvigraimpex_1.10.0+git20160211.167be93-2_multi.changes

libvigraimpex_1.10.0+git20160211.167be93-2_multi.changes uploaded successfully to localhost along with the files: libvigraimpex_1.10.0+git20160211.167be93-2.dsc libvigraimpex_1.10.0+git20160211.167be93.orig.tar.xz libvigraimpex_1.10.0+git20160211.167be93-2.debian.tar.xz

Processed: Bug#815795 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 815795 pending Bug #815795 [libvigraimpex6] libvigraimpex6: misses Breaks: libvigraimpex5v5 (>= 1.10.0+git20160120.803d5d4-1) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 815795:

Processed: Bug#812850 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 812850 pending Bug #812850 [src:libvigraimpex] libvigraimpex: fail of test/impex Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 812850:

Processed: Bug#814606 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 814606 pending Bug #814606 [libvigraimpex] libvigraimpex: FTBFS on armel (error: return type 'class std::future') Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 814606:

Bug#815600: marked as done (isympy: lacks a dependency on python-sympy | python3-sympy)

Your message dated Tue, 01 Mar 2016 22:27:32 + with message-id and subject line Bug#815600: fixed in sympy 0.7.6.1-2 has caused the Debian Bug report #815600, regarding isympy: lacks a dependency on python-sympy | python3-sympy to be marked as done. This

sympy_0.7.6.1-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Mar 2016 18:13:45 +0100 Source: sympy Binary: isympy python-sympy python3-sympy python-sympy-doc Architecture: source all Version: 0.7.6.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science

ros-metapackages_1.5_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 01 Mar 2016 21:41:51 +0100 Source: ros-metapackages Binary: ros-core ros-core-dev ros-core-rosbuild-dev ros-core-python-dev ros-core-lisp-dev ros-base ros-base-dev ros-base-python-dev ros-base-lisp-dev ros-robot

Processing of ros-metapackages_1.5_source.changes

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

Processing of ros-metapackages_1.5_source.changes

ros-metapackages_1.5_source.changes uploaded successfully to ftp-master.debian.org along with the files: ros-metapackages_1.5.dsc ros-metapackages_1.5.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- debian-science-maintainers mailing list

Bug#814606: libvigraimpex: FTBFS on armel (error: return type 'class std::future')

On 01.03.2016 19:16, Ullrich Koethe wrote: >>> so, please run cmake with the flag "-DWITH_BOOST_THREAD=1". >> >> Yup, that works. > > Great. Ideally, we would like to activate this flag automatically for > non-conforming compilers, or at least issue a warning. Is there a way for > cmake to

Bug#816424: r-cran-httpuv: FTBFS on non-Linux: 'src/unix/async.o' failed

Source: r-cran-httpuv Version: 1.3.3-3 Severity: important Justification: fails to build from source Thanks for taking care of #814720/#814878! Linux builds of r-cran-httpuv are doing well, but builds for kFreeBSD and the Hurd are now hitting another issue: In file included from

Bug#816423: ros-simulators{,-dev}: update dependency to gazebo7

Source: ros-metapackages Version: 1.4 Severity: serious gazebo6 is gone. Please update your dependencies on ros-simulators / ros-simulators-dev to gazebo7 / libgazebo7-dev. Emilio -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#814606: libvigraimpex: FTBFS on armel (error: return type 'class std::future')

so, please run cmake with the flag "-DWITH_BOOST_THREAD=1". Yup, that works. Great. Ideally, we would like to activate this flag automatically for non-conforming compilers, or at least issue a warning. Is there a way for cmake to recognize your platform and toolchain? -- ** WARNING: You

Bug#814606: libvigraimpex: FTBFS on armel (error: return type 'class std::future')

On Tue, 1 Mar 2016 11:21:49 +0100 Ullrich Koethe wrote: > Since your toolchain apparently has no conforming implementation of > std::thread, you might want to try boost::thread as a fall-back. To do > so, please run cmake with the flag

Processing of sympy_0.7.6.1-2_amd64.changes

sympy_0.7.6.1-2_amd64.changes uploaded successfully to localhost along with the files: sympy_0.7.6.1-2.dsc sympy_0.7.6.1-2.debian.tar.xz isympy_0.7.6.1-2_all.deb python-sympy-doc_0.7.6.1-2_all.deb python-sympy_0.7.6.1-2_all.deb python3-sympy_0.7.6.1-2_all.deb Greetings, Your

apertium-nob_0.6.0~r66076-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Mar 2016 12:24:40 + Source: apertium-nob Binary: apertium-nob Architecture: source all Version: 0.6.0~r66076-1 Distribution: unstable Urgency: low Maintainer: Debian Science Team

apertium-swe_0.5.0~r66062-1_amd64.changes is NEW

binary:apertium-swe is NEW. source:apertium-swe 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

ros-common-msgs 1.12.4-1 MIGRATED to testing

FYI: The status of the ros-common-msgs source package in Debian's testing distribution has changed. Previous version: 1.12.3-5 Current version: 1.12.4-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

qrouter 1.3.38-1 MIGRATED to testing

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

Processing of apertium-swe_0.5.0~r66062-1_amd64.changes

apertium-swe_0.5.0~r66062-1_amd64.changes uploaded successfully to localhost along with the files: apertium-swe_0.5.0~r66062-1.dsc apertium-swe_0.5.0~r66062.orig.tar.bz2 apertium-swe_0.5.0~r66062-1.debian.tar.xz apertium-swe_0.5.0~r66062-1_all.deb Greetings, Your Debian queue

Bug#814720: marked as done (r-cran-httpuv: FTBFS: dependency 'Rcpp' is not available)

Your message dated Tue, 01 Mar 2016 16:07:09 + with message-id and subject line Bug#814720: fixed in r-cran-httpuv 1.3.3-3 has caused the Debian Bug report #814720, regarding r-cran-httpuv: FTBFS: dependency 'Rcpp' is not available to be marked as done.

Bug#814878: marked as done (r-cran-httpuv: FTBFS: ERROR: dependency 'Rcpp' is not available for package 'httpuv')

Your message dated Tue, 01 Mar 2016 16:07:09 + with message-id and subject line Bug#814878: fixed in r-cran-httpuv 1.3.3-3 has caused the Debian Bug report #814878, regarding r-cran-httpuv: FTBFS: ERROR: dependency 'Rcpp' is not available for package

r-cran-httpuv_1.3.3-3_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 01 Mar 2016 15:35:39 +0100 Source: r-cran-httpuv Binary: r-cran-httpuv Architecture: source amd64 Version: 1.3.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Processing of apertium-nob_0.6.0~r66076-1_amd64.changes

apertium-nob_0.6.0~r66076-1_amd64.changes uploaded successfully to localhost along with the files: apertium-nob_0.6.0~r66076-1.dsc apertium-nob_0.6.0~r66076.orig.tar.bz2 apertium-nob_0.6.0~r66076-1.debian.tar.xz apertium-nob_0.6.0~r66076-1_all.deb Greetings, Your Debian queue

apertium-nno_0.6.0~r66076-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Mar 2016 12:24:40 + Source: apertium-nno Binary: apertium-nno Architecture: source all Version: 0.6.0~r66076-1 Distribution: unstable Urgency: low Maintainer: Debian Science Team

apertium-dan_0.4.0~r66063-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Mar 2016 12:24:40 + Source: apertium-dan Binary: apertium-dan Architecture: source all Version: 0.4.0~r66063-1 Distribution: unstable Urgency: low Maintainer: Debian Science Team

Processing of apertium-dan_0.4.0~r66063-1_amd64.changes

apertium-dan_0.4.0~r66063-1_amd64.changes uploaded successfully to localhost along with the files: apertium-dan_0.4.0~r66063-1.dsc apertium-dan_0.4.0~r66063.orig.tar.bz2 apertium-dan_0.4.0~r66063-1.debian.tar.xz apertium-dan_0.4.0~r66063-1_all.deb Greetings, Your Debian queue

Bug#816397: libvlfeat-dev: SIFT feature silently removed

Package: libvlfeat-dev Version: 0.9.20+dfsg0-1 Severity: minor Hi there, I was hoping to use the SIFT feature from libvlfeat so I installed the libvlfeat-dev package which explicitly mentions SIFT in its description. However, it seems that the SIFT implementation has been removed from the

Bug#816387: qwtplot3d FTBFS on armel and armhf

Package: qwtplot3d Severity: serious Version: 0.2.7+svn191-9 The failure happens when building against QT5, QT4 succeeds. This appears to be related to the GL/glu.h include added in 03_fix_ftbs.patch. make[2]: Entering directory '/«BUILDDIR»/qwtplot3d-0.2.7+svn191/build-qt5' g++ -c -pipe -g -O2

Bug#816100: marked as done (trilinos: FTBFS on arch-dep binary-only build (dpkg-buildpackage -B))

Your message dated Tue, 01 Mar 2016 11:25:36 + with message-id and subject line Bug#816100: fixed in trilinos 12.4.2-2 has caused the Debian Bug report #816100, regarding trilinos: FTBFS on arch-dep binary-only build (dpkg-buildpackage -B) to be marked as

trilinos_12.4.2-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 01 Mar 2016 12:39:54 +0200 Source: trilinos Binary: trilinos-all-dev trilinos-dev libtrilinos-amesos12 libtrilinos-amesos-dev libtrilinos-amesos2-12 libtrilinos-amesos2-dev libtrilinos-anasazi12

Processing of trilinos_12.4.2-2_source.changes

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

ros-image-common_1.11.10-3_amd64.changes REJECTED

ACL dm: NEW uploads are not allowed === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#814606: libvigraimpex: FTBFS on armel (error: return type 'class std::future')

Since your toolchain apparently has no conforming implementation of std::thread, you might want to try boost::thread as a fall-back. To do so, please run cmake with the flag "-DWITH_BOOST_THREAD=1". Best Ulli On Sat, 13 Feb 2016 13:27:16 +0100 Andreas Metzler wrote:

Bug#816371: Please (build-) depend on astropy instead of pyfits

Package: healpy Version: 1.8.1-1 Severity: wishlist Dear Leo, please make the healpy package dependent from python-astropy and python3-astropy instead of pyfits. Pyfits is now an obsolete package and should be replaced by astropy. There will be no further development of pyfits. Best

Processed (with 1 error): Merging some numpy bugs that shall be fixed with 1.1

Processing commands for cont...@bugs.debian.org: > reassign 816369 python3-numpy 1:1.11.0~b2-1 Bug #816369 [src:healpy] TypeError: 'float' object cannot be interpreted as an index Bug reassigned from package 'src:healpy' to 'python3-numpy'. No longer marked as found in versions healpy/1.8.1-1.1.

Processed (with 4 errors): Merging some numpy bugs that shall be fixed with 1.1

Processing commands for cont...@bugs.debian.org: > retitle 816369 TypeError: 'float' object cannot be interpreted as an index Bug #816369 [src:healpy] healpy: FTBFS: ValueError: Header update sequence item #0 is invalid; the item must either be a 2-tuple containing a keyword and value, or a

Processed (with 3 errors): Merging some numpy bugs that shall be fixed with 1.1

Processing commands for cont...@bugs.debian.org: > clone 813781 -1 Bug #813781 [src:healpy] healpy: FTBFS: ValueError: Header update sequence item #0 is invalid; the item must either be a 2-tuple containing a keyword and value, or a 3-tuple containing a keyword, value, and comment string. Bug