fenics is marked for autoremoval from testing

fenics 1:1.5.0.1 is marked for autoremoval from testing on 2016-09-01 It (build-)depends on packages with these RC bugs: 827740: isympy: isympy start fails: No module named sympy.interactive 830365: sympy: FTBFS: Please install the mpmath package with a version >= 0.19 --

fiat is marked for autoremoval from testing

fiat 2016.1.0-1 is marked for autoremoval from testing on 2016-09-01 It (build-)depends on packages with these RC bugs: 827740: isympy: isympy start fails: No module named sympy.interactive 830365: sympy: FTBFS: Please install the mpmath package with a version >= 0.19 --

sympy is marked for autoremoval from testing

sympy 1.0-1 is marked for autoremoval from testing on 2016-09-01 It is affected by these RC bugs: 830365: sympy: FTBFS: Please install the mpmath package with a version >= 0.19 827740: isympy: isympy start fails: No module named sympy.interactive -- debian-science-maintainers mailing list

ffc is marked for autoremoval from testing

ffc 2016.1.0-1 is marked for autoremoval from testing on 2016-09-01 It (build-)depends on packages with these RC bugs: 827740: isympy: isympy start fails: No module named sympy.interactive 830365: sympy: FTBFS: Please install the mpmath package with a version >= 0.19 --

Bug#831189: marked as done (librecad: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory)

Your message dated Fri, 05 Aug 2016 04:33:42 + with message-id and subject line Bug#831189: fixed in librecad 2.0.9-3 has caused the Debian Bug report #831189, regarding librecad: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or

Processing of librecad_2.0.9-3_amd64.changes

librecad_2.0.9-3_amd64.changes uploaded successfully to localhost along with the files: librecad_2.0.9-3.dsc librecad_2.0.9-3.debian.tar.xz librecad-data_2.0.9-3_all.deb librecad-dbgsym_2.0.9-3_amd64.deb librecad_2.0.9-3_amd64.deb Greetings, Your Debian queue daemon (running on

Bug#833383: ros-std-msgs: split headers and message definitions

‎Hello Jochen, > Interesting point, what would be the use case? These messages definition could be used to generate bindings for other programming languages and/or frameworks. In my specific case, in YARP (another middleware for robotics similar to ROS) we have a way to publish/subscribe to

Bug#831069: marked as done (qtiplot: FTBFS with GCC 6: src/analysis/dialogs/FitDialog.cpp:1025:41: error: no matching function for call to 'QTableWidgetItem::setFlags(bool)')

Your message dated Thu, 4 Aug 2016 21:32:29 +0200 with message-id and subject line Closing the bug has caused the Debian Bug report #831069, regarding qtiplot: FTBFS with GCC 6: src/analysis/dialogs/FitDialog.cpp:1025:41:

Processed: Closing the bug

Processing commands for cont...@bugs.debian.org: > notfound 831069 0.9.8.9-14 Bug #831069 [src:qtiplot] qtiplot: FTBFS with GCC 6: src/analysis/dialogs/FitDialog.cpp:1025:41: error: no matching function for call to 'QTableWidgetItem::setFlags(bool)' No longer marked as found in versions

Processing of lua-torch-sys_0~20160415-g8d2b8fa-1_amd64.changes

lua-torch-sys_0~20160415-g8d2b8fa-1_amd64.changes uploaded successfully to localhost along with the files: lua-torch-sys_0~20160415-g8d2b8fa-1.dsc lua-torch-sys_0~20160415-g8d2b8fa.orig.tar.gz lua-torch-sys_0~20160415-g8d2b8fa-1.debian.tar.xz

Processing of lua-torch-paths_0~20160203-g68d579a-1_amd64.changes

lua-torch-paths_0~20160203-g68d579a-1_amd64.changes uploaded successfully to localhost along with the files: lua-torch-paths_0~20160203-g68d579a-1.dsc lua-torch-paths_0~20160203-g68d579a.orig.tar.gz lua-torch-paths_0~20160203-g68d579a-1.debian.tar.xz

I Want Investment In Your Country

Hello, I am writing this email to you in regard to my request for an investment opportunity in your country. I am searching for business opportunity in your country when I came across your contact and I decide to open up communication with you. I am interested in exploring ways to establish

clapack 3.2.1+dfsg-1 MIGRATED to testing

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

Processing of primesieve_5.7.0+ds-1_i386.changes

primesieve_5.7.0+ds-1_i386.changes uploaded successfully to localhost along with the files: primesieve_5.7.0+ds-1.dsc primesieve_5.7.0+ds.orig.tar.gz primesieve_5.7.0+ds-1.debian.tar.xz libprimesieve7-dbgsym_5.7.0+ds-1_i386.deb libprimesieve7-dev-common_5.7.0+ds-1_all.deb

Processed: notfixed 820815 in 3.47+dfsg1-1, fixed 820815 in 3.47+dfsg1-1, reassign 827474 to src:libreoffice ...

Processing commands for cont...@bugs.debian.org: > notfixed 820815 3.47+dfsg1-1 Bug #820815 {Done: Dimitrios Eftaxiopoulos } [src:freefem++] freefem++: please make the build reproducible (fileordering,timestamps) No longer marked as fixed in versions

Bug#833425: Aw: Re: Bug#833425: mpi-defaults: switch to openmpi on hppa architecture

Hello Mattia, On 04.08.2016 12:49, Mattia Rizzolo wrote: > On Thu, Aug 04, 2016 at 12:02:51PM +0200, Helge Deller wrote: >> Currently I've stopped all hppa buildds and plan to upgrade them to gcc6 >> before starting them again. And, I've started a test build of boost1.6.1 >> to check if the

Bug#833425: marked as done (mpi-defaults: switch to openmpi on hppa architecture)

Your message dated Thu, 04 Aug 2016 12:37:39 + with message-id and subject line Bug#833425: fixed in mpi-defaults 1.7 has caused the Debian Bug report #833425, regarding mpi-defaults: switch to openmpi on hppa architecture to be marked as done. This means

mpi-defaults_1.7_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 04 Aug 2016 11:38:16 + Source: mpi-defaults Binary: mpi-default-dev mpi-default-bin Architecture: source Version: 1.7 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Processing of mpi-defaults_1.7_source.changes

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

kido_0.1.0+dfsg-1_amd64.changes is NEW

binary:libkido-dev is NEW. binary:libkido-gui-dev is NEW. binary:libkido-gui-osg-dev is NEW. binary:libkido-gui-osg0.1 is NEW. binary:libkido-gui0.1 is NEW. binary:libkido-optimizer-ipopt-dev is NEW. binary:libkido-optimizer-ipopt0.1 is NEW. binary:libkido-optimizer-nlopt-dev is NEW.

Processing of kido_0.1.0+dfsg-1_amd64.changes

kido_0.1.0+dfsg-1_amd64.changes uploaded successfully to localhost along with the files: kido_0.1.0+dfsg-1.dsc kido_0.1.0+dfsg.orig.tar.gz kido_0.1.0+dfsg-1.debian.tar.xz libkido-dev_0.1.0+dfsg-1_amd64.deb libkido-gui-dev_0.1.0+dfsg-1_amd64.deb

3Depict upload

Dear Debian-science, I have recently updated the 3depict package on Alioth [1] to 0.0.19, and would like to request an upload. This closes an RC bug ( #831200 ). I have successfully cowbuilt the package, and it is (on my local system) lintian-clean. Thanks. [1]

Bug#833425: Aw: Re: Bug#833425: mpi-defaults: switch to openmpi on hppa architecture

Hi all, On 04/08/2016 11:02, Helge Deller wrote: > Hi Mattia, > >> On Thu, Aug 04, 2016 at 09:34:35AM +0200, Helge Deller wrote: >>> mpi-defaults depends on libmpich-dev for the hppa architecture (like m68k >>> and sh4). >>> All other architectures use libopenmpi-dev. >>> Is there a reason for

Bug#833425: Aw: Re: Bug#833425: mpi-defaults: switch to openmpi on hppa architecture

On Thu, Aug 04, 2016 at 12:02:51PM +0200, Helge Deller wrote: > > > The openmpi packages builds successfully on hppa, so I'd suggest to switch > > > to openmpi for hppa (and maybe m68k and sh4?) too. > > > > notice that switching default means rebuilding all the rdep in the > > correct order (ben

GRAN OFERTA: FUJITSU S780 i5 -15,6" + Windows 7 sólo por 207 Euros

Gran oferta   FUJITSU S780 i5 -15,6" - 4 GB de RAM 250 GB de Disco duro     207,02 EUR   

libgetdata_0.9.3-1_amd64.changes ACCEPTED into unstable

Mapping sid to unstable. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 03 Aug 2016 12:41:46 +0100 Source: libgetdata Binary: libgetdata-doc libgetdata-dev libgetdata7 libgetdata++6 libfgetdata5 libf95getdata6 libgetdata-tools python-pygetdata libgetdata-perl

Bug#833425: Aw: Re: Bug#833425: mpi-defaults: switch to openmpi on hppa architecture

Hi Mattia, > On Thu, Aug 04, 2016 at 09:34:35AM +0200, Helge Deller wrote: > > mpi-defaults depends on libmpich-dev for the hppa architecture (like m68k > > and sh4). > > All other architectures use libopenmpi-dev. > > Is there a reason for that? > > reason is that at that time openmpi was not

Processing of libgetdata_0.9.3-1_amd64.changes

libgetdata_0.9.3-1_amd64.changes uploaded successfully to localhost along with the files: libgetdata_0.9.3-1.dsc libgetdata_0.9.3.orig.tar.xz libgetdata_0.9.3-1.debian.tar.xz libf95getdata6-dbgsym_0.9.3-1_amd64.deb libf95getdata6_0.9.3-1_amd64.deb libfgetdata5-dbgsym_0.9.3-1_amd64.deb

Bug#833425: Aw: mpi-defaults: switch to openmpi on hppa architecture

On Thu, Aug 04, 2016 at 11:10:50AM +0200, Helge Deller wrote: > When building boost-1.6.1 I [1] get: > /usr/include/mpich/mpicxx.h:21:4: error: #error 'Please use the same version > of GCC and g++ for compiling MPICH and user MPI programs' > # error 'Please use the same version of GCC and g++

Bug#833425: Aw: mpi-defaults: switch to openmpi on hppa architecture

Some more details regarding the request to switch mpi-defaults to openmpi on hppa: When building boost-1.6.1 I [1] get: /usr/include/mpich/mpicxx.h:21:4: error: #error 'Please use the same version of GCC and g++ for compiling MPICH and user MPI programs' # error 'Please use the same version

Bug#833425: mpi-defaults: switch to openmpi on hppa architecture

On Thu, Aug 04, 2016 at 09:34:35AM +0200, Helge Deller wrote: > mpi-defaults depends on libmpich-dev for the hppa architecture (like m68k and > sh4). > All other architectures use libopenmpi-dev. > Is there a reason for that? reason is that at that time openmpi was not available on those

Bug#833383: ros-std-msgs: split headers and message definitions

Hi Daniele, * Daniele E. Domenichelli [2016-08-03 19:35]: > It would be very useful to be able to install the message definitions without > installing the whole libstd-msgs-dev package that depends on many other > packages. Interesting point, what would be the use case?

Bug#833425: mpi-defaults: switch to openmpi on hppa architecture

Package: mpi-defaults Version: 1.6 mpi-defaults depends on libmpich-dev for the hppa architecture (like m68k and sh4). All other architectures use libopenmpi-dev. Is there a reason for that? The openmpi packages builds successfully on hppa, so I'd suggest to switch to openmpi for hppa (and maybe

ignition-msgs_0.4.0-1_amd64.changes is NEW

binary:libignition-msgs-dev is NEW. binary:libignition-msgs0 is NEW. source:ignition-msgs 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