Processing of hfst_3.9.0~r4595-3_amd64.changes

hfst_3.9.0~r4595-3_amd64.changes uploaded successfully to localhost along with the files: hfst_3.9.0~r4595-3.dsc hfst_3.9.0~r4595-3.debian.tar.xz hfst-dbgsym_3.9.0~r4595-3_amd64.deb hfst_3.9.0~r4595-3_amd64.deb libhfst42-dbgsym_3.9.0~r4595-3_amd64.deb

Bug#809446: marked as done (python3-libhfst: Package will become non-working once python3.5 is default python3)

Your message dated Wed, 10 Feb 2016 16:20:43 + with message-id and subject line Bug#809446: fixed in hfst 3.9.0~r4595-3 has caused the Debian Bug report #809446, regarding python3-libhfst: Package will become non-working once python3.5 is default python3

Re: shark_3.0.1+ds1-1_amd64.changes REJECTED

On 05/02/16 23:00, Thorsten Alteholz wrote: Hi Ghislain, please mention the BSD license of doc/* in your debian/copyright. Thanks! Thorsten === 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

Bug#810990: marked as done (libxmlrpcpp-dev: /usr/include/base64.h already shipped by heimdal-dev)

Your message dated Wed, 10 Feb 2016 20:11:36 +0100 with message-id <20160210191136.ga23...@vis.informatik.uni-osnabrueck.de> and subject line libxmlrpcpp-dev: /usr/include/base64.h already shipped by heimdal-dev has caused the Debian Bug report #810990, regarding libxmlrpcpp-dev:

Processing of libosmocore_0.9.0-4_source.changes

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

apertium-dan-nor_1.2.2~r65301-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 10 Feb 2016 09:33:33 +0530 Source: apertium-dan-nor Binary: apertium-dan-nor Architecture: source all Version: 1.2.2~r65301-1 Distribution: unstable Urgency: low Maintainer: Debian Science Team

Processing of mpi-defaults_1.2_source.changes

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

openggsn_0.92-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 09 Feb 2016 18:49:05 +0100 Source: openggsn Binary: openggsn libgtp0 libgtp-dev Architecture: source amd64 Version: 0.92-1 Distribution: unstable Urgency: low Maintainer: Debian Science Maintainers

libosmocore_0.9.0-4_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Feb 2016 20:24:50 +0100 Source: libosmocore Binary: libosmocore libosmocodec0 libosmocodec-doc libosmocore6 libosmocore-doc libosmogb4 libosmogsm5 libosmogsm-doc libosmovty3 libosmovty-doc libosmoctrl0

mpi-defaults_1.2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 10 Feb 2016 20:18:28 + Source: mpi-defaults Binary: mpi-default-dev mpi-default-bin Architecture: source Version: 1.2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Bug#814370: arachne-pnr: Typo in short description

Package: arachne-pnr Severity: minor Dear Maintainer, The short description of arachne-pnr says "Place and route tool for iCE40 family FGPAs". I believe it should be "FPGAs" instead of "FGPAs". As this typo comes from upstream, I also reported it in

Processing of python-pynlpl_0.7.7.1-1_amd64.changes

python-pynlpl_0.7.7.1-1_amd64.changes uploaded successfully to localhost along with the files: python-pynlpl_0.7.7.1-1.dsc python-pynlpl_0.7.7.1.orig.tar.gz python-pynlpl_0.7.7.1-1.debian.tar.xz python-pynlpl_0.7.7.1-1_all.deb python3-pynlpl_0.7.7.1-1_all.deb Greetings, Your

python-pynlpl_0.7.7.1-1_amd64.changes is NEW

binary:python-pynlpl is NEW. binary:python3-pynlpl is NEW. source:python-pynlpl 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

r-cran-coin is marked for autoremoval from testing

r-cran-coin 1.1-2-1 is marked for autoremoval from testing on 2016-03-18 It (build-)depends on packages with these RC bugs: 813641: multcomp: FTBFS: Error : package 'MASS' required by 'TH.data' could not be found -- debian-science-maintainers mailing list

vitables is marked for autoremoval from testing

vitables 2.1-1 is marked for autoremoval from testing on 2016-03-18 It (build-)depends on packages with these RC bugs: 813643: numexpr: FTBFS: TypeError: 'float' object cannot be interpreted as an index -- debian-science-maintainers mailing list

Processing of r-cran-yaml_2.1.13-4_amd64.changes

r-cran-yaml_2.1.13-4_amd64.changes uploaded successfully to localhost along with the files: r-cran-yaml_2.1.13-4.dsc r-cran-yaml_2.1.13-4.debian.tar.xz r-cran-yaml-dbgsym_2.1.13-4_amd64.deb r-cran-yaml_2.1.13-4_amd64.deb Greetings, Your Debian queue daemon (running on host

sfepy is marked for autoremoval from testing

sfepy 2015.1-2 is marked for autoremoval from testing on 2016-03-18 It (build-)depends on packages with these RC bugs: 813643: numexpr: FTBFS: TypeError: 'float' object cannot be interpreted as an index -- debian-science-maintainers mailing list

r-cran-lsmeans is marked for autoremoval from testing

r-cran-lsmeans 2.21-1-1 is marked for autoremoval from testing on 2016-03-18 It (build-)depends on packages with these RC bugs: 813641: multcomp: FTBFS: Error : package 'MASS' required by 'TH.data' could not be found -- debian-science-maintainers mailing list

numexpr is marked for autoremoval from testing

numexpr 2.4.3-1 is marked for autoremoval from testing on 2016-03-18 It is affected by these RC bugs: 813643: numexpr: FTBFS: TypeError: 'float' object cannot be interpreted as an index -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

pytables is marked for autoremoval from testing

pytables 3.2.2-1 is marked for autoremoval from testing on 2016-03-18 It (build-)depends on packages with these RC bugs: 813643: numexpr: FTBFS: TypeError: 'float' object cannot be interpreted as an index -- debian-science-maintainers mailing list

r-cran-yaml_2.1.13-4_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 11 Feb 2016 05:21:54 +0100 Source: r-cran-yaml Binary: r-cran-yaml Architecture: source amd64 Version: 2.1.13-4 Distribution: unstable Urgency: low Maintainer: Debian Science Team

Bug#814149: add alternative for /usr/bin/dx

Hi Hans-Christoph On 8 February 2016 at 21:25, Hans-Christoph Steiner wrote: > We have just packaged the "Dalvik Explorer" aka android-platform-dalvik > which is always used as the command util 'dx'. Always? IBM's DX has been around since 1991. :) > This conflicts with >

Bug#814149: add alternative for /usr/bin/dx

Seems to me that if y'all don't want to add an alternatives setup, then we'll just do a Conflicts. All of the Android docs and tools just reference 'dx' so not providing 'dx' is not an option. Plus in my 35 years of using computers in dotcom startups, media and art, psychiatry, mobile and

Bug#814149: add alternative for /usr/bin/dx

On Wed, 10 Feb 2016 11:36:23 Hans-Christoph Steiner wrote: > Seems to me that if y'all don't want to add an alternatives setup, then > we'll just do a Conflicts. All of the Android docs and tools just > reference 'dx' so not providing 'dx' is not an option. Plus in my 35 > years of using

Processing of mpi-defaults_1.1_source.changes

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

Bug#814149: add alternative for /usr/bin/dx

I agree with Graham, this is a plain and simple naming clash.  The only reasonable resolution is to rename one (or both) of the binaries.   You could workaround the clash with Conflicts:, but that's not reasonable either since there's no reason both binaries shouldn't coexists. A possible

mpi-defaults_1.1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 10 Feb 2016 10:41:49 + Source: mpi-defaults Binary: mpi-default-dev mpi-default-bin Architecture: source Version: 1.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Lån tilbud fra MoneySave Solutions

Hej MoneySave Solutions er et finansieringsselskab, der har specialiseret sig i at yde; Boliglån, personlige lån, investeringslån, konsolidering af gælden lån, auto lån, Ferie lån, tilbage til skolen lån, kommercielle lån, Udstyr Lån, Nødsituation/ uventede udgifter Lån. Vores lånetilbud

Bug#813691: marked as done (make openmpi the default on s390x)

Your message dated Wed, 10 Feb 2016 11:23:55 + with message-id and subject line Bug#813691: fixed in mpi-defaults 1.1 has caused the Debian Bug report #813691, regarding make openmpi the default on s390x to be marked as done. This means that you claim

Processing of pyfftw_0.10.1+dfsg1-1_source.changes

pyfftw_0.10.1+dfsg1-1_source.changes uploaded successfully to localhost along with the files: pyfftw_0.10.1+dfsg1-1.dsc pyfftw_0.10.1+dfsg1.orig.tar.gz pyfftw_0.10.1+dfsg1-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) --

pyfftw_0.10.1+dfsg1-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 02 Feb 2016 17:07:23 + Source: pyfftw Binary: python-pyfftw python-pyfftw-dbg python3-pyfftw python3-pyfftw-dbg Architecture: source Version: 0.10.1+dfsg1-1 Distribution: unstable Urgency: medium Maintainer:

Bug#810522: marked as done (pyfftw: FTBFS: TypeError: can't pickle Cython.Compiler.FlowControl.NameAssignment objects)

Your message dated Wed, 10 Feb 2016 11:49:37 + with message-id and subject line Bug#810522: fixed in pyfftw 0.10.1+dfsg1-1 has caused the Debian Bug report #810522, regarding pyfftw: FTBFS: TypeError: can't pickle

Bug#746998: marked as done (pyfftw: FTBFS on architectures without long double)

Your message dated Wed, 10 Feb 2016 11:49:37 + with message-id and subject line Bug#746998: fixed in pyfftw 0.10.1+dfsg1-1 has caused the Debian Bug report #746998, regarding pyfftw: FTBFS on architectures without long double to be marked as done. This

Bug#812296: [PATCH] Fix GCC 6 FTBFS

I am compiling vtk6 with gcc-6 with the attached patch. Regards, Gerardo --- a/CMake/GenerateExportHeader.cmake 2016-02-10 23:14:42.395094043 -0400 +++ b/CMake/GenerateExportHeader.cmake 2016-02-10 23:10:16.756787993 -0400 @@ -166,7 +166,7 @@ execute_process(COMMAND