Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 853541 src:tbb Bug #853541 [src:mathicgb] mathicgb: ftbfs with GCC-7 Bug reassigned from package 'src:mathicgb' to 'src:tbb'. No longer marked as found in versions mathicgb/1.0~git20170104-1. Ignoring request to alter fixed versions of

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 856356 https://github.com/linbox-team/linbox/issues/37 Bug #856356 [src:linbox] linbox FTBFS on mips/mipsel: segfault in test-charpoly Set Bug forwarded-to-address to 'https://github.com/linbox-team/linbox/issues/37'. > thanks Stopping

Bug#853413: marked as done (gazebo: ftbfs with GCC-7)

Your message dated Sat, 5 Aug 2017 23:11:36 +0300 with message-id <20170805201136.2uds4ysttj4imndc@localhost> and subject line gazebo builds with gcc 7 has caused the Debian Bug report #853413, regarding gazebo: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has

Bug#853660: marked as done (simbody: ftbfs with GCC-7)

Your message dated Sat, 5 Aug 2017 22:58:09 +0300 with message-id <20170805195809.62lpak2lrsn3vvo5@localhost> and subject line simbody builds with gcc 7 has caused the Debian Bug report #853660, regarding simbody: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem

Bug#870688: [Debian-science-sagemath] Sage 8.0 status (was Re: Sage 7.6 upload for RC bugfix and GAP 4.8.7 in unstable)

Tobias Hansen: > [..]> > > Hi, > > good work on finding the fpylll issue! Now the main holdup for sage 8.0 > is still cypari2 being stuck in NEW. I wrote on June 21 to > ftpmas...@debian.org and August 2 directly to the ftpmaster who helped > us get sagemath through NEW in time for stretch.

hypre 2.11.1-4 MIGRATED to testing

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

yade 2017.01a-9 MIGRATED to testing

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

Bug#853513: libvigraimpex: ftbfs with GCC-7

Control: forwarded -1 https://github.com/ukoethe/vigra/issues/409 Control: block 853447 with 853513 Control: block 853389 with 853513 On 2017-07-21 Daniel Stender wrote: > There's currently another build break happening: > > {standard input}: Assembler messages: >

Processed: Re: Bug#853513: libvigraimpex: ftbfs with GCC-7

Processing control commands: > forwarded -1 https://github.com/ukoethe/vigra/issues/409 Bug #853513 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-7 Set Bug forwarded-to-address to 'https://github.com/ukoethe/vigra/issues/409'. > block 853447 with 853513 Bug #853447 [src:hugin] hugin: ftbfs

Bug#870821: esys-particle FTBFS with perl 5.26

Source: esys-particle Version: 2.3.5+dfsg1-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/esys-particle.html ... ./makeglos.pl paper.glo Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\\newglossarytype\[(.*)\]{ <-- HERE

Bug#853392: marked as done (esys-particle: ftbfs with GCC-7)

Your message dated Sat, 5 Aug 2017 17:40:21 +0300 with message-id <20170805144021.bfwlkzipgirc7alj@localhost> and subject line Seems demoted to a warning in the released gcc 7 has caused the Debian Bug report #853392, regarding esys-particle: ftbfs with GCC-7 to be marked as done. This means that

Bug#870698: Possible fix for fplll/fpylll issue with default strategy path

Hi, I just pushed to fplll's Debian git repository a tentative 5.1.0-3 which would fix the recently reported issue with fpylll : I rewrote the patch for the default strategies path changes. I'm a bit at loss on how to check if that really fixes anything : I tried to build fpylll (success), but