Source: ticcutils
Version: 0.4-5
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
User: debian-de...@lists.debian.org
Usertags: autoreconf
Dear Maintainer,
The package ticcutils fails to build on ppc64el, as on new architectures,
because the config.{guess,sub}
Hi Sylvestre,
On 06/26/2014 02:33 PM, Sylvestre Ledru wrote:
On 26/06/2014 09:53, Breno Leitao wrote:
Source: timblserver
/bin/bash ../libtool --tag=CXX --mode=link g++ -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security
-Wall -I/usr/include/libxml2
Package: libmatio
Version: 1.5.2-1
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Dear Maintainer,
The package libmatio does not build on new architecture because the libtool
files is not updated automatically by either autoreconf (just updates the
config
I am still facing the same issue on package 2.0.0-5, which is suppose
to contain the fix.
I tested on ppc64el, take a look at the problem, which seems to be the same.
The following tests FAILED:
1 - INTEGRATION_audio (Timeout)
3 -
Package: opencv
Version: 2.4.8+dfsg1-2.2
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Dear Maintainer,
With the recent changes in tbb package, now it builds on ppc64el, so, we should
enable opencv to depend on tbb as the other architectures.
I just
Source: libgtkdatabox
Version: 0.9.2.0
Severity: normal
Tags: patch
Dear Maintainer,
Currently this package FTBFS when compiled in new architectures (as ppc64el)
that is not supported on the outdated package autotools files, mainly because
it fails to understand that the new architectures has
Source: blitz++
Version: 0.10-1
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
User: debian-de...@lists.debian.org
Usertags: autoreconf
Dear Maintainer,
Currently this package FTBFS when compiled in new architectures (as ppc64el)
that is not supported on the
Package: mmdb
Version: 1.25.5-1
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
User: debian-de...@lists.debian.org
Usertags: autoreconf
Dear Maintainer,
Currently this package FTBFS when compiled in new architectures (as ppc64el)
that is not supported on the
Control: retitle -1 healpy FTBFS on arm64, ppc64 and ppc64el test failure
Hi,
The same problem happen on ppc64el, as the following log shows:
http://ftp.unicamp.br/pub/ppc64el/debian/buildd-upstream/build_logs/logs/healpy_1.8.1-1_ppc64el.build
I created the following upstream bug also:
Source: clblas
Version: 6
Severity: wishlist
Currently, clblas has altivec disabled due to bug #798024.
This causes some performance issue on ppc64el platform.
I am opening this bug to track altivec enablement for clblas.
I might also work to have this solved.
Breno
-- System Information:
I am looking at this problem, and I understand that the following patch fixes
this problem:
--- critterding-1.0-beta12.1.orig/src/brainz/brainz.cpp
+++ critterding-1.0-beta12.1/src/brainz/brainz.cpp
@@ -137,7 +137,7 @@ Brainz::Brainz()
// clear Motor Outputs
-beta12.1/debian/changelog 2016-07-17 17:11:02.0
-0400
@@ -1,3 +1,10 @@
+critterding (1.0-beta12.1-1.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fixing FTBFS on GCC 6. (Closes: 811621)
+
+ -- Breno Leitao <bren...@br.ibm.com> Sun, 17 Jul 2016 16:46:12 -0400
+
critterdin
Is anyone looking/debugging this issue?
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
I am looking at this issue, and the first test set is checkall.
If I run it inside dpkg-buildpackage, it fails as in the log, but, if I run
it isolated, I see no errors, as showed:
$ ./checkall 2>&1 | grep -i fail
$
Looking all tests I see "-> OK". Anyway, I am continue to debug what is the
On 11/27/2016 07:16 PM, Ghislain Vaillant wrote:
> On Thu, 24 Nov 2016 18:49:29 -0200 Breno Leitao <bren...@br.ibm.com> wrote:
>> I am looking at this issue, and the first test set is checkall.
>>
>> If I run it inside dpkg-buildpackage, it fails as in the log, but, if
We just created a pull request to have this fixed upstream.
https://github.com/pydata/numexpr/pull/235
Should we create a Debian patch also?
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
On 11/20/2016 07:41 AM, Adrian Bunk wrote:
>
> Lots of failures like:
>
Yes. I just tried it here, and more than 40 tests failed.
It is usually off by 1, and I am wondering if we are being bite by a similar
issue I found on OpenJDK, where there are math inconsistency when using
optimization
Hello Ghislain,
On 12/09/2016 07:01 AM, Ghislain Vaillant wrote:
> I might eventually just bypass testing for ppc64el to let the package
> transition to testing, unless you think you are gonna have a fix ready very
> soon. With the transition window extended to 10 days and the soft-freeze
>
Hi Ghis,
On 12/14/2016 09:30 AM, Ghislain Vaillant wrote:
> Thanks for your contribution. Let me know if a long-term solution comes up
> later.
Sure. I closed the bug on the changelog, but, you can keep it open to track
the final and long term solution.
--
debian-science-maintainers mailing
cy=medium
+
+ * Avoid running tests with long double on ppc64el due to failing tests
+(Closes: #844403)
+ * Add build-dependency for latex.
+
+ -- Breno Leitao <lei...@debian.org> Fri, 09 Dec 2016 16:12:51 -0500
+
nfft (3.3.2-1) unstable; urgency=medium
* New upstream version 3.3.2
20 matches
Mail list logo
