Processed: Fwd: Re: libarrayfire-opencl3: "INTERNAL KERNEL BUILD ERROR" from af::matmulTN

Processing commands for cont...@bugs.debian.org: > reassign 881054 libclblas2 Bug #881054 [libarrayfire-opencl3] libarrayfire-opencl3: "INTERNAL KERNEL BUILD ERROR" from af::matmulTN Bug reassigned from package 'libarrayfire-opencl3' to 'libclblas2'. No longer marked as found in versions arrayfir

Bug#853399: Fwd: Re: [linbox-team/fflas-ffpack] Fails to build with gcc 7 (#74)

Control: tags -1 fixed-upstream Forwarded Message Subject:Re: [linbox-team/fflas-ffpack] Fails to build with gcc 7 (#74) Resent-From:dtorra...@piedmont.edu Date: Fri, 10 Feb 2017 00:25:27 -0800 From: Clément Pernet Reply-To: linbox-team/fflas-ffpack To:

Processed: Fwd: Re: [linbox-team/fflas-ffpack] Fails to build with gcc 7 (#74)

Processing control commands: > tags -1 fixed-upstream Bug #853399 [src:fflas-ffpack] fflas-ffpack: ftbfs with GCC-7 Added tag(s) fixed-upstream. -- 853399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian-s

Processed: Fwd: Re: [linbox-team/givaro] test-crt (sometimes) fails (#38)

Processing control commands: > tags -1 fixed-upstream Bug #852995 [src:givaro] givaro: FTBFS randomly (failing tests) Added tag(s) fixed-upstream. -- 852995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian

Bug#852995: Fwd: Re: [linbox-team/givaro] test-crt (sometimes) fails (#38)

Control: tags -1 fixed-upstream Forwarded Message Subject:Re: [linbox-team/givaro] test-crt (sometimes) fails (#38) Resent-From:dtorra...@piedmont.edu Date: Mon, 6 Feb 2017 06:28:06 -0800 From: Jean-Guillaume Dumas Reply-To: linbox-team/givaro To: li

Bug#853653: Fwd: Re: Fwd: Bug#853653: scilab: ftbfs with GCC-7

Message transféré Sujet : Re: Fwd: Bug#853653: scilab: ftbfs with GCC-7 Date : Tue, 31 Jan 2017 14:36:47 +0100 De : Clément David Organisation : Scilab Enteprises Pour : Sylvestre Ledru , Paul Bignier , Gilles Filippini Hi, Thanks for the information, this is fixed in the late

Bug#848137: Fwd: Re: Bug#848137: problem with the upgrade of tango-db

Forwarded Message Subject: Re: Bug#848137: problem with the upgrade of tango-db Date: Mon, 9 Jan 2017 10:00:59 +0100 From: Andreas Beckmann To: Paul Gevers On 2017-01-08 22:29, Paul Gevers wrote: > It would still be nice to confirm that this issue exists (in > experimental)

Processed: Re: Fwd: Re: yade and ipython5

Processing control commands: > tag -1 + patch Bug #840527 [src:yade] yade: ipython transition: FTBFS with ipython 5 Added tag(s) patch. -- 840527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian-science-ma

Bug#840527: Fwd: Re: yade and ipython5

Control: tag -1 + patch Hi, I ended up not using git, because it's not possible to build from git. Somehow there are changes from the orig tarball, the patch 05_reproducible-builds.patch does not apply. Here's a debdiff. With the patch the package builds and the IPython prompts show up in the do

Bug#840527: Fwd: Re: yade and ipython5

Hi Tobias, feel free to push to git (please create a new branch). I will try to test it on Saturday. Thanks! Anton 2016-10-26 21:11 GMT+02:00 Tobias Hansen : > Hi, > > the problem occurred in the file doc/sphinx/ipython_directive200.py. It > seems this is an old version of the file [1], so the

Bug#840527: Fwd: Re: yade and ipython5

Hi, the problem occurred in the file doc/sphinx/ipython_directive200.py. It seems this is an old version of the file [1], so the first thing to try would be to include the new version with a new name and edit doc/sphinx/conf.py so that it is used. Anton, do you mind if I push a patch to the packag

Bug#812852: Fwd: Re: Vigra auf ppc64el

Forwarded Message Subject: Re: Vigra auf ppc64el Date: Fri, 4 Mar 2016 15:56:16 +0100 From: Ullrich Koethe To: Daniel Stender CC: Francesco Biscani Hallo Daniel, unfortunately, we can't investigate this problem ourselves because we don't have access to a ppc system. Here

Fwd: Re: J

- Original Message - Sent: Wed, 02 Dec 2015 20:41:07 -0500 (EST) Subject: J YOUR TRUST IS NEEDED PLEASE -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#801060: Fwd: Re: Bug#798256: transition: hdf5

CCing #801060 for the record. Courriel original Objet: Re: Bug#798256: transition: hdf5 Date: 2015-10-06 12:59 De: Gilles Filippini À: Emilio Pozuelo Monfort Cc: 798...@bugs.debian.org, Emilio Pozuelo Monfort Le 2015-10-06 11:07, Emilio Pozuelo Monfort a écrit : On 05/10/15

Bug#794853: Fwd: Re: Mass bug filing about non free lena image.

I would love when we don't have a problem here ... DS Forwarded Message Subject: Re: Mass bug filing about non free lena image. Resent-Date: Wed, 12 Aug 2015 20:29:32 + (UTC) Resent-From: debian-de...@lists.debian.org Date: Wed, 12 Aug 2015 22:29:18 +0200 From: Jonas Smedega

Bug#792624: Fwd: Fwd: Re: multiarch = same and different date-entries in generated man page of i32/i64

Hmm, good point, David. Because I'm also upstream this would easily be possible. It had to stay in sync then to the application/api behavior, which is, however, only a matter of discipline. Maybe I can use some familiar tool like LaTeX for writing. Thanks for the impulse, I hadn't considered it

Bug#792624: Fwd: Fwd: Re: multiarch = same and different date-entries in generated man page of i32/i64

Roelof Berg writes: > help2man 1.47.1 IS used. Next I will try as a workaround setting >export SOURCE_DATE_EPOCH = $(shell date -d "$$(dpkg-parsechangelog > --count 1 -SDate)" +%s) > manually in debian/rules. Not everyone agrees with me, but I think using help2man at build time should be ge

Bug#792625: Fwd: Fwd: Re: multiarch = same and different date-entries in generated man page of i32/i64

help2man 1.47.1 IS used. Next I will try as a workaround setting export SOURCE_DATE_EPOCH = $(shell date -d "$$(dpkg-parsechangelog --count 1 -SDate)" +%s) manually in debian/rules. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.ali

Bug#792625: Fwd: Fwd: Re: multiarch = same and different date-entries in generated man page of i32/i64

Possibly a help2man version below 1.47.1 is used on the build server and help2man doesn't support SOURCE_DATE_EPOCH before this date. (See: https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal). I'm not familiar with the debian automated build infrastru

Bug#792624: Fwd: Re: multiarch = same and different date-entries in generated man page of i32/i64

Back from vacation: This is a consequence of #787675. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787675 Thanks to Anton Gladky for pointing me to that. The fix is on its way ... Roelof -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://l

Fwd: RE

i need your help-- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#756784: Fwd: Re: Bug#756784: visp: FTBFS on powerpc

On 2014-08-04 11:21:31, Emilio Pozuelo Monfort wrote: > On 02/08/14 14:38, Fabien Spindler wrote: > > Hi, > > > > Is it possible to relaunch the build of visp > > https://buildd.debian.org/status/package.php?p=visp&suite=unstable > > especially on powerpc arch. I suspect that a 3rd party was updat

Bug#746609: Fwd: Re: 3depict: Please update to use wxwidgets3.0

Original Message Subject: Re: 3depict: Please update to use wxwidgets3.0 Date: Thu, 24 Jul 2014 23:18:55 +0100 From: D Haley To: Olly Betts Hi, No it has not been missed. I have been busy over the last few weekends with other non-debian things. I could have done it last we

Bug#741131: Fwd: Re: Fwd: Bug#741131: nonfree file in source

--- Begin Message --- Dear Dimitris, it is source file itself, distributed under MIT license (see http://sylvester.jcoglan.com/) On 09.03.2014 21:06, Δημήτρης Ευταξιόπουλος wrote: Hello Alexey, could you please remove json/sylvester.js during a future SVN update since I received the attached