ros-rosdep 0.11.4-4 MIGRATED to testing

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

linbox 1.4.2-4 MIGRATED to testing

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

Bug#869162: marked as done (ros-rosinstall FTBFS: CalledProcessError: Command '[u'git', u'commit', u'-m', u'initial']' returned non-zero exit status 128)

Your message dated Tue, 25 Jul 2017 21:27:08 + with message-id and subject line Bug#869162: fixed in ros-rosinstall 0.7.7-5 has caused the Debian Bug report #869162, regarding ros-rosinstall FTBFS: CalledProcessError: Command '[u'git', u'commit', u'-m',

ros-wstool_0.1.13-4_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jul 2017 21:26:56 +0200 Source: ros-wstool Binary: python-wstool python3-wstool Architecture: source Version: 0.1.13-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

ros-rosinstall_0.7.7-5_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jul 2017 22:16:11 +0200 Source: ros-rosinstall Binary: python-rosinstall python3-rosinstall Architecture: source Version: 0.7.7-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Processed: Merge duplicates, the BTS gets confused when a bug is closed in a different package

Processing commands for cont...@bugs.debian.org: > reassign 868607 src:apertium-nno Bug #868607 {Done: Kartik Mistry } [src:apertium-swe-nor] apertium-swe-nor FTBFS: Error: Position on line 6990 near `O inf)␊;␊#sjeldent i` - stand-alone o or O doesn't make sense - maybe you

Processing of ros-rosinstall_0.7.7-5_source.changes

ros-rosinstall_0.7.7-5_source.changes uploaded successfully to localhost along with the files: ros-rosinstall_0.7.7-5.dsc ros-rosinstall_0.7.7-5.debian.tar.xz ros-rosinstall_0.7.7-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Processing of ros-wstool_0.1.13-4_source.changes

ros-wstool_0.1.13-4_source.changes uploaded successfully to localhost along with the files: ros-wstool_0.1.13-4.dsc ros-wstool_0.1.13-4.debian.tar.xz ros-wstool_0.1.13-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --

ros-wstool_0.1.13-4_source.changes REJECTED

ros-wstool_0.1.13-4.dsc: Invalid size hash for ros-wstool_0.1.13.orig.tar.gz: According to the control file the size hash should be 75201, but ros-wstool_0.1.13.orig.tar.gz has 75188. If you did not include ros-wstool_0.1.13.orig.tar.gz in your upload, a different version might already be

Processing of ros-wstool_0.1.13-4_source.changes

ros-wstool_0.1.13-4_source.changes uploaded successfully to localhost along with the files: ros-wstool_0.1.13-4.dsc ros-wstool_0.1.13-4.debian.tar.xz ros-wstool_0.1.13-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Bug#869691: gmp: please add support for arm64ilp32

Source: gmp Version: 6.1.2+dfsg-1 Severity: wishlist Tags: upstream patch Attached is a patched providing very basic initial suport for arm64ilp32, using the generic C support. To some degreee it is a placeholder until a less hacky patch is developed, although it does work and builds the

Bug#863291: libscalapack-openmpi1: memory leak in pXgemr2d

On Tue, 25 Jul 2017 23:03:23 +0800 Drew Parsons wrote: > Hi Grigory, >  > scalapack 2.0 is now available in experimental. >  > Could you test if your pXgemr2d problem persists when built against > scalapack 2.0 with openmpi 2.1.1 ? Note that scalapack 2.0 incorporates blacs,

Bug#863291: libscalapack-openmpi1: memory leak in pXgemr2d

Hi Grigory, scalapack 2.0 is now available in experimental. Could you test if your pXgemr2d problem persists when built against scalapack 2.0 with openmpi 2.1.1 ? Thanks, Drew -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#854228: Libraries not linked with their deps

On Tue, 21 Mar 2017 11:03:07 +0800 Drew Parsons wrote: > On Tue, 21 Mar 2017 10:50:29 +0800 Drew Parsons > wrote: > >  > > That document is from 1997 though.  The MPI standard has moved > through > > 2 major versions since then. But blacs remains

pybtex_0.21-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 22 Jul 2017 21:55:03 +0100 Source: pybtex Binary: pybtex python-pybtex python3-pybtex python-pybtex-doc Architecture: source all Version: 0.21-1 Distribution: unstable Urgency: medium Maintainer: Debian Science

Processed: bug 867496 is forwarded to https://github.com/morse-simulator/morse/pull/766

Processing commands for cont...@bugs.debian.org: > forwarded 867496 https://github.com/morse-simulator/morse/pull/766 Bug #867496 [src:morse-simulator] morse-simulator FTBFS: ImportError: No module named 'version' Set Bug forwarded-to-address to

Bug#869582: marked as done (apertium-eo-es FTBFS: Error: Position on line 159 near `O Vblex + Pers) (*1C` - stand-alone o or O doesn't make sense - maybe you meant 0?)

Your message dated Tue, 25 Jul 2017 12:06:44 +0200 with message-id and subject line Re: Bug#869582: apertium-eo-es FTBFS has caused the Debian Bug report #869582, regarding apertium-eo-es FTBFS: Error: Position on line 159 near

VEĽMI NALIEHAVÉ

Drahý priateľ, Mám pre Vás dôležitý návrh, prosím, urgentne napíšte späť môj súkromný e-mail :: mrshuange...@gmail.com S Pozdravom, Mrs Huan Gen. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

FW:

You Have been chosen for world heritage award This message, including any attachments, is intended only for the use of the intended recipient(s), and it may contain privileged and confidential information. If you are not the intended recipient, you are hereby notified that any review,

apertium-eo-es_0.9.1~r60655-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jul 2017 11:32:35 +0530 Source: apertium-eo-es Binary: apertium-eo-es Architecture: source all Version: 1:0.9.1~r60655-2 Distribution: unstable Urgency: low Maintainer: Debian Science Team

Processing of apertium-eo-es_0.9.1~r60655-2_amd64.changes

apertium-eo-es_0.9.1~r60655-2_amd64.changes uploaded successfully to localhost along with the files: apertium-eo-es_0.9.1~r60655-2.dsc apertium-eo-es_0.9.1~r60655-2.debian.tar.xz apertium-eo-es_0.9.1~r60655-2_all.deb apertium-eo-es_0.9.1~r60655-2_amd64.buildinfo Greetings, Your

apertium-eo-ca_0.9.1~r60655-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jul 2017 11:20:47 +0530 Source: apertium-eo-ca Binary: apertium-eo-ca Architecture: source all Version: 1:0.9.1~r60655-2 Distribution: unstable Urgency: low Maintainer: Debian Science Team

Processing of apertium-eo-ca_0.9.1~r60655-2_amd64.changes

apertium-eo-ca_0.9.1~r60655-2_amd64.changes uploaded successfully to localhost along with the files: apertium-eo-ca_0.9.1~r60655-2.dsc apertium-eo-ca_0.9.1~r60655-2.debian.tar.xz apertium-eo-ca_0.9.1~r60655-2_all.deb apertium-eo-ca_0.9.1~r60655-2_amd64.buildinfo Greetings, Your