Processed: Re: Bug#813691: make openmpi the default on s390x

2016-02-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #813691 [src:mpi-defaults] make openmpi the default on s390x Added tag(s) moreinfo. -- 813691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --

Bug#813691: make openmpi the default on s390x

2016-02-04 Thread Matthias Klose
Package: src:mpi-defaults Version: 1.0.2+nmu2 Tags: patch please make openmpi the default on s390x. while mpi itself is not used that much on s390x, it may be better to go with the implementation which is used for most architectures. patch at

Bug#813691: make openmpi the default on s390x

2016-02-04 Thread Matthias Klose
Control: tag -1 - moreinfo On 04.02.2016 13:08, Ansgar Burchardt wrote: Control: tag -1 moreinfo On Thu, 2016-02-04 at 12:59 +0100, Matthias Klose wrote: Package: src:mpi-defaults Version: 1.0.2+nmu2 Tags: patch please make openmpi the default on s390x. while mpi itself is not used that much

Processed: Re: Bug#813691: make openmpi the default on s390x

2016-02-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 - moreinfo Bug #813691 [src:mpi-defaults] make openmpi the default on s390x Removed tag(s) moreinfo. -- 813691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --

Processing of paraview_5.0.0+dfsg1-1_source.changes

2016-02-04 Thread Debian FTP Masters
paraview_5.0.0+dfsg1-1_source.changes uploaded successfully to ftp-master.debian.org along with the files: paraview_5.0.0+dfsg1-1.dsc paraview_5.0.0+dfsg1.orig.tar.xz paraview_5.0.0+dfsg1-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org) --

Processing of paraview_5.0.0+dfsg1-1_source.changes

2016-02-04 Thread Debian FTP Masters
paraview_5.0.0+dfsg1-1_source.changes uploaded successfully to localhost along with the files: paraview_5.0.0+dfsg1-1.dsc paraview_5.0.0+dfsg1.orig.tar.xz paraview_5.0.0+dfsg1-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) --

Processing of mlpack_2.0.0-2_amd64.changes

2016-02-04 Thread Debian FTP Masters
mlpack_2.0.0-2_amd64.changes uploaded successfully to localhost along with the files: mlpack_2.0.0-2.dsc mlpack_2.0.0-2.debian.tar.xz libmlpack-dev_2.0.0-2_amd64.deb libmlpack2-dbgsym_2.0.0-2_amd64.deb libmlpack2_2.0.0-2_amd64.deb mlpack-bin-dbgsym_2.0.0-2_amd64.deb

Processing of urdfdom-headers_0.4.0-1_source.changes

2016-02-04 Thread Debian FTP Masters
urdfdom-headers_0.4.0-1_source.changes uploaded successfully to ftp-master.debian.org along with the files: urdfdom-headers_0.4.0-1.dsc urdfdom-headers_0.4.0.orig.tar.gz urdfdom-headers_0.4.0-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host coccia.debian.org)

Processing of urdfdom-headers_0.4.0-1_source.changes

2016-02-04 Thread Debian FTP Masters
urdfdom-headers_0.4.0-1_source.changes uploaded successfully to localhost along with the files: urdfdom-headers_0.4.0-1.dsc urdfdom-headers_0.4.0.orig.tar.gz urdfdom-headers_0.4.0-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) --

Processed: block 813691 with 813694

2016-02-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 813691 with 813694 Bug #813691 [src:mpi-defaults] make openmpi the default on s390x 813691 was not blocked by any bugs. 813691 was not blocking any bugs. Added blocking bug(s) of 813691: 813694 > thanks Stopping processing here. Please

Re: Regarding VTK 7.0.0

2016-02-04 Thread Anton Gladky
Hi Elvis, we discussed it a couple of days ago with other people, interested in it VTK7 (CC-ing them). We are not sure, whether vtk7 can coexist with vtk6 without conflicts. From my POV, it is a little bit late to start a large transition process. So, if both of those versions can coexist - no

Re: Regarding VTK 7.0.0

2016-02-04 Thread Elvis Stansvik
2016-02-04 15:41 GMT+01:00 Ghislain Vaillant : > It is next on my TODO list, I had a bunch of RCs to clear out before. > > I will soon be contacting the VTK 6 maintainers to coordinate our > efforts towards VTK 7. > Excellent news Ghis. Elvis > > Cheers, > Ghis > > > On

Regarding VTK 7.0.0

2016-02-04 Thread Elvis Stansvik
Hi all, Just wanted to ask if VTK 7.0.0 is being packaged for Debian, and if so, when it might turn up? Now that VTK supports Python 3, will there be a python3-vtk7 package? Thanks for all the great packaging work. Best regards, Elvis -- debian-science-maintainers mailing list

openstereogram is marked for autoremoval from testing

2016-02-04 Thread Debian testing autoremoval watch
openstereogram 0.1+20080921-2 is marked for autoremoval from testing on 2016-03-09 It (build-)depends on packages with these RC bugs: 812643: jgit: FTBFS - 2 tests fail -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

paraview_5.0.0+dfsg1-1_source.changes ACCEPTED into unstable

2016-02-04 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Feb 2016 22:51:08 +0100 Source: paraview Binary: paraview paraview-dev paraview-doc paraview-python Architecture: source Version: 5.0.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science

urdfdom-headers_0.4.0-1_source.changes ACCEPTED into unstable

2016-02-04 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Jan 2016 20:29:59 + Source: urdfdom-headers Binary: liburdfdom-headers-dev Architecture: source Version: 0.4.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

mlpack_2.0.0-2_amd64.changes ACCEPTED into unstable

2016-02-04 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Feb 2016 23:26:01 + Source: mlpack Binary: libmlpack-dev libmlpack2 mlpack-bin mlpack-doc Architecture: source amd64 all Version: 2.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science

Bug#813415: libvigraimpex5v5: soname bump without package name change

2016-02-04 Thread Andreas Metzler
On 2016-02-01 Daniel Stender wrote: [...] > I've expected this bug to appear now. I've already prepared a fix for -2, > it's coming up very soon. Hello, GIT head seems to be missing a Package: libvigraimpex6 +Replaces: libvigraimpex5v5 (>=

oce 0.17.1-1 MIGRATED to testing

2016-02-04 Thread Debian testing watch
FYI: The status of the oce source package in Debian's testing distribution has changed. Previous version: 0.15-7 Current version: 0.17.1-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

freecad 0.15.4671+dfsg1-4 MIGRATED to testing

2016-02-04 Thread Debian testing watch
FYI: The status of the freecad source package in Debian's testing distribution has changed. Previous version: 0.15.4671+dfsg1-3 Current version: 0.15.4671+dfsg1-4 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a

Bug#802318: marked as done (scoop: FTBFS: test break on Python 3.5 in reproducible builds CI)

2016-02-04 Thread Debian Bug Tracking System
Your message dated Thu, 4 Feb 2016 15:40:54 +0100 with message-id <56b362f6.50...@danielstender.com> and subject line scoop: FTBFS: test break on Python 3.5 in reproducible builds CI has caused the Debian Bug report #802318, regarding scoop: FTBFS: test break on Python 3.5 in reproducible builds

Re: Regarding VTK 7.0.0

2016-02-04 Thread Ghislain Vaillant
It is next on my TODO list, I had a bunch of RCs to clear out before. I will soon be contacting the VTK 6 maintainers to coordinate our efforts towards VTK 7. Cheers, Ghis On 04/02/16 14:28, Anton Gladky wrote: Hi Elvis, we discussed it a couple of days ago with other people, interested in

Re: Regarding VTK 7.0.0

2016-02-04 Thread Elvis Stansvik
Hi Anton, 2016-02-04 15:28 GMT+01:00 Anton Gladky : > Hi Elvis, > > we discussed it a couple of days ago with other people, > interested in it VTK7 (CC-ing them). We are not sure, whether > vtk7 can coexist with vtk6 without conflicts. From my > POV, it is a little bit late to