Bug#890231: sagemath should use gdb, not gdb-python2, to be removed for buster

2018-02-12 Thread Matthias Klose
On 12.02.2018 15:41, Ximin Luo wrote:
> Understood, but the entirety of sagemath is python2 at the moment and doesn't 
> support python3 (upstream is working on it).
> 
> What's the timeframe for removal of gdb-python2 and will there be a 
> gdb-python3 alternative?

gdb is built using python3.  So maybe there is a misunderstanding, but how does
sagemath use python for debugging? Does it add it's own pretty printers so that
it needs python2? How is the gdb usage related to Python2?

-- 
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#890231: sagemath should use gdb, not gdb-python2, to be removed for buster

2018-02-12 Thread Matthias Klose
Package: src:sagemath
Version: 8.2-3
Severity: important
Tags: sid buster

sagemath should use gdb, not gdb-python2, to be removed for buster.  Please
don't introduce new python2 (build) dependencies.

-- 
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#888912: sagemath test failures with mpfr 4.0.0 and several architectures

2018-01-30 Thread Matthias Klose
Package: src:sagemath
Version: 8.2-1
Severity: serious
Tags: sid buster

see https://buildd.debian.org/status/package.php?p=sagemath=unstable

test failures on every architecture.

-- 
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#888911: giac test failures with mpfr 4.0.0 on several architectures

2018-01-30 Thread Matthias Klose
Package: src:giac
Version: 1.2.3.57+dfsg1-2
Severity: serious
Tags: sid buster

see https://buildd.debian.org/status/package.php?p=giac

failing tests at least on the release architectures amd64 and armhf.

-- 
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#888550: glm has some silly GCC version checks, removed upstream

2018-01-27 Thread Matthias Klose
Package: src:glm
Version: 0.9.8.4-1.1
Severity: serious
Tags: sid buster patch

glm has some silly GCC version checks, removed upstream

see https://launchpad.net/bugs/1745685

patch at
http://launchpadlibrarian.net/354819354/glm_0.9.8.4-1.1_0.9.8.4-1.1ubuntu1.diff.gz

-- 
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#888459: flint-arb's tests fail on 32bit archs using mpfr 4.0.0

2018-01-25 Thread Matthias Klose
Package: src:flint-arb
Version: 2.11.1-2
Severity: serious
Tags: sid buster

as seen on
https://release.debian.org/transitions/html/auto-mpfr4.html
https://buildd.debian.org/status/package.php?p=flint-arb

the testsuite fails on all 32bit architectures.

cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -I/<>
-I/usr/local/include -I/usr/local/include -I/usr/include test/t-sqrt.c -o
../build/arf/test/t-sqrt -L/<> -L/usr/local/lib -L/usr/local/lib
-L/usr/lib -lflint-arb -lflint -lmpfr -lgmp -lm -lpthread  -MMD -MP -MF
../build/arf/test/t-sqrt.d -MT "../build/arf/test/t-sqrt" -MT
"../build/arf/test/t-sqrt.d"
flooraddmul_uiPASS
cmpabs_2exp_siPASS
addset_round_uirootPASS
add_siPASS
mulPASS
set_fmpqPASS
submul_uiPASS
mul_siPASS
abs_bound_lt_2exp_siPASS
sub_siPASS
get_dPASS
addmul_fmpzPASS
add_uiPASS
frexpPASS
rsqrtPASS
subPASS
cmpabsPASS
set_fmprPASS
set_round_fmpzPASS
mul_uiPASS
abs_bound_lt_2exp_fmpzPASS
sub_uiPASS
set_fmpz_2expPASS
complex_sqrPASS
complex_mulPASS
abs_bound_le_2exp_fmpzPASS
submul_fmpzPASS
divFAIL (aliasing 4)!
prec = 352, rnd = 4

x =
(4586997233048136541430758450064474100387735230759824291973833691816938709832156080645343570059119116156929
* 2^-154742412678922490659733883)

y =
(51814976846671518298238808760042830604686502339620382299366747655022166929406808804341858227567903870767891933265103849315791036770763130077955430384829058539908460614800988509303528381975119100503701824233100229972596599113543202092890645352456600459286399836135725531911334505568114757105479020098464557517116791851426250751
* 2^-154742431125385089392575577)

v =
(2135987036418233318920600437589210504846524088997312026086185915310372929010612927677735486095361
* 2^-154742412678922490659733852)

r1 = 1, r2 = 1
../Makefile.subdirs:84: recipe for target '../build/arf/test/t-div_RUN' failed
make[3]: *** [../build/arf/test/t-div_RUN] Aborted
make[3]: *** Waiting for unfinished jobs
PASS
PASS
PASS
make[3]: Leaving directory '/<>/arf'
Makefile:179: recipe for target 'check' failed
make[2]: *** [check] Error 2
make[2]: Leaving directory '/<>'

-- 
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#866460: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

-- 
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#866484: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

-- 
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#866480: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

-- 
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#866495: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

-- 
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#866435: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

-- 
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#866430: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

-- 
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#884516: python-bayespy autopkg tests fail on several architectures

2017-12-15 Thread Matthias Klose
Package: src:python-bayespy
Version: 0.5.12-1
Severity: important
Tags: sid buster

(seen on the autopkg tests on Ubuntu)

It looks like 0.5.12 is failing it's autopkg tests at least on arm64, armhf,
ppc64el and s390x (all succeeding with 0.5.8).

arm64, ppc64el, s390x:
Test the message to parents of Concatenate node. ... Segmentation fault (core
dumped)

armhf:
Test the message from SumMultiply node to its parents. ... Segmentation fault
(core dumped)

Succeeding targets are amd64 and i386.

In a Debian test rebuild, the package seems to succeed on at least amd64.

-- 
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#881236: flint-arb: tests fail on amd64 and i386

2017-11-08 Thread Matthias Klose
Package: src:flint-arb
Version: 2.11.1-1
Severity: serious
Tags: sid buster

The x86* builds fail with:

make[3]: Leaving directory '/<>/dlog'
make[3]: Entering directory '/<>/arb_fmpz_poly'
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -I/<>
-I/usr/local/include -I/usr/local/include -I/usr/include test/t-evaluate_acb.c
-o ../build/arb_fmpz_poly/test/t-evaluate_acb -L/<>
-L/usr/local/lib -L/usr/local/lib -L/usr/lib -lflint-arb -lflint -lmpfr -lgmp
-lm -lpthread  -MMD -MP -MF ../build/arb_fmpz_poly/test/t-evaluate_acb.d -MT
"../build/arb_fmpz_poly/test/t-evaluate_acb" -MT
"../build/arb_fmpz_poly/test/t-evaluate_acb.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -I/<>
-I/usr/local/include -I/usr/local/include -I/usr/include
test/t-gauss_period_minpoly.c -o
../build/arb_fmpz_poly/test/t-gauss_period_minpoly -L/<>
-L/usr/local/lib -L/usr/local/lib -L/usr/lib -lflint-arb -lflint -lmpfr -lgmp
-lm -lpthread  -MMD -MP -MF ../build/arb_fmpz_poly/test/t-gauss_period_minpoly.d
-MT "../build/arb_fmpz_poly/test/t-gauss_period_minpoly" -MT
"../build/arb_fmpz_poly/test/t-gauss_period_minpoly.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -I/<>
-I/usr/local/include -I/usr/local/include -I/usr/include test/t-complex_roots.c
-o ../build/arb_fmpz_poly/test/t-complex_roots -L/<>
-L/usr/local/lib -L/usr/local/lib -L/usr/lib -lflint-arb -lflint -lmpfr -lgmp
-lm -lpthread  -MMD -MP -MF ../build/arb_fmpz_poly/test/t-complex_roots.d -MT
"../build/arb_fmpz_poly/test/t-complex_roots" -MT
"../build/arb_fmpz_poly/test/t-complex_roots.d"
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -I/<>
-I/usr/local/include -I/usr/local/include -I/usr/include test/t-evaluate_arb.c
-o ../build/arb_fmpz_poly/test/t-evaluate_arb -L/<>
-L/usr/local/lib -L/usr/local/lib -L/usr/lib -lflint-arb -lflint -lmpfr -lgmp
-lm -lpthread  -MMD -MP -MF ../build/arb_fmpz_poly/test/t-evaluate_arb.d -MT
"../build/arb_fmpz_poly/test/t-evaluate_arb" -MT
"../build/arb_fmpz_poly/test/t-evaluate_arb.d"
evaluate_acbgauss_period_minpoly../Makefile.subdirs:84: recipe for
target '../build/arb_fmpz_poly/test/t-gauss_period_minpoly_RUN' failed
make[3]: *** [../build/arb_fmpz_poly/test/t-gauss_period_minpoly_RUN] Floating
point exception
make[3]: *** Waiting for unfinished jobs

-- 
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#880633: ros should not introduce Python2 modules only

2017-11-02 Thread Matthias Klose
Package: src:ros-angles
Version: 1.9.11-1
Severity: important
Tags: sid buster

ros should not introduce Python2 modules only, given that Python2 will be
end-of-live soonish.  Please package python3 modules as well. Not just for this
package but for all other ros packages as well.

-- 
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#729956: Python 3 Statsmodels & Pandas

2017-09-17 Thread Matthias Klose
On 16.09.2017 22:59, Yuri D'Elia wrote:
> On Sat, Sep 16 2017, Diane Trout wrote:
>> python3-pandas: Pandas is not installable
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875723
> 
> I would have expected the rebuild of python packages affected by the
> fpectl extension with a transition, but it doesn't seem to be the case?

no, we don't want to rename the python2.7 package.

> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874253
> 
> More Breaks where added to {python,python3}-stdlib itself, but there are
> still packages which didn't rebuild.

fix them, they fail for unrelated reasons ;)

-- 
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#875671: fix test dependencies

2017-09-13 Thread Matthias Klose
Package: src:lapack
Version: 3.7.1-3
Tags: patch

dpkg-dev expects gcc ...

http://launchpadlibrarian.net/336816854/lapack_3.7.1-3ubuntu1_3.7.1-3ubuntu2.diff.gz

-- 
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#729956: Forwarded upstream

2017-09-06 Thread Matthias Klose
On 06.09.2017 23:45, Diane Trout wrote:
> I was trying to build it right now but I'm getting a dependency error.
> 
>  libpython2.7-stdlib : Breaks: python-pandas-lib (<= 0.20.3-1) but
> 0.20.3-1 is to be installed

this is unrelated, and waiting for #874413.

-- 
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#871505: openturns: testsuite failure on i386

2017-08-08 Thread Matthias Klose
Package: src:openturns
Version: 1.7-3
Severity: serious
Tags: sid buster

417/417 Test #371: cppcheck_FunctionalChaos_gsobol
..   Passed   77.75 sec

99% tests passed, 1 tests failed out of 417

Total Test time (real) = 198.44 sec

The following tests FAILED:
202 - cppcheck_GeneralizedPareto_std (Failed)
Errors while running CTest
Makefile:143: recipe for target 'test' failed
make[2]: *** [test] Error 8
make[2]: Leaving directory '/<>/build-python2.7'
debian/rules:120: recipe for target 'cmake-test-2.7' failed
make[1]: *** [cmake-test-2.7] Error 2

-- 
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#853513: libvigraimpex: ftbfs with GCC-7

2017-08-08 Thread Matthias Klose
On 08.08.2017 07:51, Andreas Metzler wrote:
> On 2017-08-07 Matthias Klose <d...@debian.org> wrote:
>> Control: tags -1 + patch
> 
>> patch at
>> http://launchpadlibrarian.net/332312910/libvigraimpex_1.10.0+git20160211.167be93+dfsg-2build3_1.10.0+git20160211.167be93+dfsg-2ubuntu1.diff.gz
> 
> Hello,
> 
> For me that one only fixes the FTBFS of vigra rdeps (hugin, enblend,
> saga, ) but the testsuite breakage also found in upstream 1.11.1 in
> blockwise watershed test is unresolved.

sorry, yes. I noticed that later too.

-- 
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#853513: libvigraimpex: ftbfs with GCC-7

2017-08-07 Thread Matthias Klose
Control: tags -1 + patch

patch at
http://launchpadlibrarian.net/332312910/libvigraimpex_1.10.0+git20160211.167be93+dfsg-2build3_1.10.0+git20160211.167be93+dfsg-2ubuntu1.diff.gz

-- 
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#853345: cernlib: ftbfs with GCC-7

2017-08-06 Thread Matthias Klose
a work around can be found at
http://launchpadlibrarian.net/332177358/cernlib_20061220+dfsg3-4.3build1_20061220+dfsg3-4.3ubuntu1.diff.gz

-- 
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#853345: cernlib: ftbfs with GCC-7

2017-08-06 Thread Matthias Klose
Control: forwarded -1 https://gcc.gnu.org/PR81723
Control: tags -1 + moreinfo

> gfortran cwerf64.F
> E: Build killed with signal TERM after 150 minutes of inactivity

that might be a GCC issue, however it would be nice to see the command line
arguments passed, and getting a test case extracted.

-- 
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#866501: yade: depends on obsolete python-imaging (replace with python3-pil or python-pil)

2017-06-29 Thread Matthias Klose
Package: src:yade
Version: 2017.01a-8
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.

-- 
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#866495: woo: depends on obsolete python-imaging (replace with python3-pil or python-pil)

2017-06-29 Thread Matthias Klose
Package: src:woo
Version: 1.0+dfsg1-1
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.

-- 
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#866484: sympy: depends on obsolete python-imaging (replace with python3-pil or python-pil)

2017-06-29 Thread Matthias Klose
Package: src:sympy
Version: 1.0-3
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.

-- 
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#866480: skimage: depends on obsolete python-imaging (replace with python3-pil or python-pil)

2017-06-29 Thread Matthias Klose
Package: src:skimage
Version: 0.12.3-9
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.

-- 
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#866465: python-fabio: depends on obsolete python-imaging (replace with python3-pil or python-pil)

2017-06-29 Thread Matthias Klose
Package: src:python-fabio
Version: 0.4.0+dfsg-2
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.

-- 
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#866460: pyfai: depends on obsolete python-imaging (replace with python3-pil or python-pil)

2017-06-29 Thread Matthias Klose
Package: src:pyfai
Version: 0.13.0+dfsg-1
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.

-- 
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#866435: ipe-tools: depends on obsolete python-imaging (replace with python3-pil or python-pil)

2017-06-29 Thread Matthias Klose
Package: src:ipe-tools
Version: 20150406-3
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.

-- 
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#866430: guiqwt: depends on obsolete python-imaging (replace with python3-pil or python-pil)

2017-06-29 Thread Matthias Klose
Package: src:guiqwt
Version: 3.0.3-1
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.

-- 
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#853703: vtk6: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:vtk6
Version: 6.3.0+dfsg1-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/vtk6_6.3.0+dfsg1-3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
Feature record: CXX_FEATURE:0cxx_thread_local
Feature record: CXX_FEATURE:0cxx_trailing_return_types
Feature record: CXX_FEATURE:0cxx_unicode_literals
Feature record: CXX_FEATURE:0cxx_uniform_initialization
Feature record: CXX_FEATURE:0cxx_unrestricted_unions
Feature record: CXX_FEATURE:0cxx_user_literals
Feature record: CXX_FEATURE:0cxx_variable_templates
Feature record: CXX_FEATURE:0cxx_variadic_macros
Feature record: CXX_FEATURE:0cxx_variadic_templates
Performing C++ SOURCE FILE Test HAVE_GCC_ERROR_RETURN_TYPE succeeded with the 
following output:
Change Dir: /<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_35100/fast"
make[2]: Entering directory 
'/<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_35100.dir/build.make 
CMakeFiles/cmTC_35100.dir/build
make[3]: Entering directory 
'/<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_35100.dir/src.cxx.o
/usr/bin/mpic++ -g -O2 -fdebug-prefix-map=/<>/vtk6-6.3.0+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DHAVE_GCC_ERROR_RETURN_TYPE   -Werror=return-type -o 
CMakeFiles/cmTC_35100.dir/src.cxx.o -c 
/<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp/src.cxx
Linking CXX executable cmTC_35100
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_35100.dir/link.txt 
--verbose=1
/usr/bin/mpic++   -g -O2 -fdebug-prefix-map=/<>/vtk6-6.3.0+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DHAVE_GCC_ERROR_RETURN_TYPE  -Wl,-z,relro  
CMakeFiles/cmTC_35100.dir/src.cxx.o  -o cmTC_35100 -rdynamic 
make[3]: Leaving directory 
'/<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp'

Source file was:
int main() { return 0; }
Performing C++ SOURCE FILE Test HAVE_GCC_VISIBILITY succeeded with the 
following output:
Change Dir: /<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_6e79c/fast"
make[2]: Entering directory 
'/<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_6e79c.dir/build.make 
CMakeFiles/cmTC_6e79c.dir/build
make[3]: Entering directory 
'/<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_6e79c.dir/src.cxx.o
/usr/bin/mpic++ -g -O2 -fdebug-prefix-map=/<>/vtk6-6.3.0+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DHAVE_GCC_VISIBILITY   -fvisibility=hidden -o 
CMakeFiles/cmTC_6e79c.dir/src.cxx.o -c 
/<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp/src.cxx
Linking CXX executable cmTC_6e79c
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_6e79c.dir/link.txt 
--verbose=1
/usr/bin/mpic++   -g -O2 -fdebug-prefix-map=/<>/vtk6-6.3.0+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DHAVE_GCC_VISIBILITY  -Wl,-z,relro  
CMakeFiles/cmTC_6e79c.dir/src.cxx.o  -o cmTC_6e79c -rdynamic 
make[3]: Leaving directory 
'/<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/vtk6-6.3.0+dfsg1/debian/build/CMakeFiles/CMakeTmp'

Source file was:
int main() { return 0; }
dh_auto_configure: cmake ../.. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_C_COMPILER=mpicc 
-DCMAKE_CXX_COMPILER=mpic++ -DBUILD_DOCUMENTATION=ON -DBUILD_EXAMPLES=ON 
-DBUILD_SHARED_LIBS=ON 

Bug#853686: trilinos: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:trilinos
Version: 12.10.1-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/trilinos_12.10.1-3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
cd /<>/obj-x86_64-linux-gnu/packages/sacado/test/UnitTests && 
/usr/bin/cmake -E cmake_link_script 
CMakeFiles/Sacado_FadKokkosTests_Serial.dir/link.txt --verbose=1
/usr/bin/mpicxx -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++11  -Wl,-z,relro -Wl,--as-needed 
CMakeFiles/Sacado_FadKokkosTests_Serial.dir/Fad_KokkosTests_Serial.cpp.o  -o 
Sacado_FadKokkosTests_Serial.exe 
-Wl,-rpath,/<>/obj-x86_64-linux-gnu/packages/sacado/src:/<>/obj-x86_64-linux-gnu/packages/kokkos/containers/src:/<>/obj-x86_64-linux-gnu/packages/teuchos/kokkoscomm/src:/<>/obj-x86_64-linux-gnu/packages/teuchos/kokkoscompat/src:/<>/obj-x86_64-linux-gnu/packages/teuchos/remainder/src:/<>/obj-x86_64-linux-gnu/packages/teuchos/numerics/src:/<>/obj-x86_64-linux-gnu/packages/teuchos/comm/src:/<>/obj-x86_64-linux-gnu/packages/teuchos/parameterlist/src:/<>/obj-x86_64-linux-gnu/packages/teuchos/core/src:/<>/obj-x86_64-linux-gnu/packages/kokkos/core/src
 -rdynamic .
 ./../src/libtrilinos_sacado.so.12.10.1 
../../../kokkos/containers/src/libtrilinos_kokkoscontainers.so.12.10.1 
../../../teuchos/kokkoscomm/src/libtrilinos_teuchoskokkoscomm.so.12.10.1 
../../../teuchos/kokkoscompat/src/libtrilinos_teuchoskokkoscompat.so.12.10.1 
../../../teuchos/remainder/src/libtrilinos_teuchosremainder.so.12.10.1 
../../../teuchos/numerics/src/libtrilinos_teuchosnumerics.so.12.10.1 
/usr/lib/liblapack.so /usr/lib/libblas.so 
../../../teuchos/comm/src/libtrilinos_teuchoscomm.so.12.10.1 
../../../teuchos/parameterlist/src/libtrilinos_teuchosparameterlist.so.12.10.1 
../../../teuchos/core/src/libtrilinos_teuchoscore.so.12.10.1 
../../../kokkos/core/src/libtrilinos_kokkoscore.so.12.10.1 
/usr/lib/x86_64-linux-gnu/libdl.so 
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 49%] Built target Sacado_FadKokkosTests_Serial
[ 49%] Linking CXX executable TpetraKernels_blas2_MV_Serial.exe
cd /<>/obj-x86_64-linux-gnu/packages/tpetra/kernels/unit_test && 
/usr/bin/cmake -E cmake_link_script 
CMakeFiles/TpetraKernels_blas2_MV_Serial.dir/link.txt --verbose=1
/usr/bin/mpicxx -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++11  -Wl,-z,relro -Wl,--as-needed 
CMakeFiles/TpetraKernels_blas2_MV_Serial.dir/blas2_MV_Serial.cpp.o  -o 
TpetraKernels_blas2_MV_Serial.exe 
-Wl,-rpath,/<>/obj-x86_64-linux-gnu/packages/tpetra/kernels/src:/<>/obj-x86_64-linux-gnu/packages/teuchos/comm/src:/<>/obj-x86_64-linux-gnu/packages/teuchos/parameterlist/src:/<>/obj-x86_64-linux-gnu/packages/teuchos/core/src:/<>/obj-x86_64-linux-gnu/packages/kokkos/algorithms/src:/<>/obj-x86_64-linux-gnu/packages/kokkos/containers/src:/<>/obj-x86_64-linux-gnu/packages/kokkos/core/src
 -rdynamic ../src/libtrilinos_tpetrakernels.so.12.10.1 
../../../teuchos/comm/src/libtrilinos_teuchoscomm.so.12.10.1 
../../../teuchos/parameterlist/src/libtrilinos_teuchosparameterlist.so.12.10.1 
../../../teuchos/core/sr
 c/libtrilinos_teuchoscore.so.12.10.1 
../../../kokkos/algorithms/src/libtrilinos_kokkosalgorithms.so.12.10.1 
../../../kokkos/containers/src/libtrilinos_kokkoscontainers.so.12.10.1 
../../../kokkos/core/src/libtrilinos_kokkoscore.so.12.10.1 
/usr/lib/x86_64-linux-gnu/libdl.so 
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 49%] Built target TpetraKernels_blas2_MV_Serial
[ 49%] Linking CXX executable TpetraTSQR_FullTsqr_Accuracy.exe
cd /<>/obj-x86_64-linux-gnu/packages/tpetra/tsqr/test && 
/usr/bin/cmake -E cmake_link_script 
CMakeFiles/TpetraTSQR_FullTsqr_Accuracy.dir/link.txt --verbose=1
/usr/bin/mpicxx -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong 

Bug#853660: simbody: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:simbody
Version: 3.5.4+dfsg-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/simbody_3.5.4+dfsg-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
In file included from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/./include/SimTKcommon/basics.h:43:0,
 from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/EventHandler.h:27,
 from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/src/EventHandler.cpp:24:
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/Measure.h:629:34:
 error: invalid use of incomplete type 'const class SimTK::Subsystem'
 && this->getSubsystem().isSameSubsystem(right.getSubsystem()),
~~^~
/<>/simbody-3.5.4+dfsg/SimTKcommon/./include/SimTKcommon/internal/ExceptionMacros.h:282:13:
 note: in definition of macro 'SimTK_ERRCHK_ALWAYS'
 do{if(!(cond))SimTK_THROW3(SimTK::Exception::ErrorCheck,\
 ^~~~
In file included from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/Subsystem.h:30:0,
 from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/System.h:30,
 from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/EventHandler.h:30,
 from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/src/EventHandler.cpp:24:
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/Measure.h:128:7:
 note: forward declaration of 'class SimTK::Subsystem'
 class Subsystem;
   ^
In file included from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/./include/SimTKcommon/basics.h:43:0,
 from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/EventHandler.h:27,
 from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/src/EventHandler.cpp:24:
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/Measure.h:
 In constructor 'SimTK::Measure_::Scale::Scale(SimTK::Subsystem&, 
SimTK::Real, const SimTK::Measure_&)':
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/Measure.h:653:31:
 error: invalid use of incomplete type 'const class SimTK::Subsystem'
(this->getSubsystem().isSameSubsystem(operand.getSubsystem()),
 ~~^~
/<>/simbody-3.5.4+dfsg/SimTKcommon/./include/SimTKcommon/internal/ExceptionMacros.h:282:13:
 note: in definition of macro 'SimTK_ERRCHK_ALWAYS'
 do{if(!(cond))SimTK_THROW3(SimTK::Exception::ErrorCheck,\
 ^~~~
In file included from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/Subsystem.h:30:0,
 from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/System.h:30,
 from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/EventHandler.h:30,
 from 
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/src/EventHandler.cpp:24:
/<>/simbody-3.5.4+dfsg/SimTKcommon/Simulation/include/SimTKcommon/internal/Measure.h:128:7:
 note: forward declaration of 'class SimTK::Subsystem'
 class Subsystem;
   ^
SimTKcommon/sharedTarget/CMakeFiles/SimTKcommon.dir/build.make:737: recipe for 
target 
'SimTKcommon/sharedTarget/CMakeFiles/SimTKcommon.dir/__/Simulation/src/EventHandler.cpp.o'
 failed
make[3]: *** 
[SimTKcommon/sharedTarget/CMakeFiles/SimTKcommon.dir/__/Simulation/src/EventHandler.cpp.o]
 Error 1
SimTKcommon/sharedTarget/CMakeFiles/SimTKcommon.dir/build.make:881: recipe for 
target 
'SimTKcommon/sharedTarget/CMakeFiles/SimTKcommon.dir/__/Simulation/src/System.cpp.o'
 failed
make[3]: *** 
[SimTKcommon/sharedTarget/CMakeFiles/SimTKcommon.dir/__/Simulation/src/System.cpp.o]
 Error 1

Bug#853658: shark: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:shark
Version: 3.1.3+ds1-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/shark_3.1.3+ds1-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
writing output... [ 98%] rest_sources/tutorials/for_developers/writing_tutorials
writing output... [100%] rest_sources/tutorials/tutorials

generating indices... genindex
writing additional pages... search
copying images... [  4%] 
rest_sources/tutorials/algorithms/../images/featuresDenoisingAutoencoder.png
copying images... [  9%] 
rest_sources/tutorials/algorithms/../images/MOOExperiment.svg
copying images... [ 13%] 
rest_sources/tutorials/algorithms/../images/featuresDropoutAutoencoder.png
copying images... [ 18%] rest_sources/tutorials/images/linearRegression.png
copying images... [ 22%] 
rest_sources/tutorials/algorithms/../images/mocma_dtlz2.svg
copying images... [ 27%] rest_sources/tutorials/images/clustering.png
copying images... [ 31%] 
rest_sources/tutorials/algorithms/../images/cma_himmelblau.svg
copying images... [ 36%] rest_sources/tutorials/images/faces.png
copying images... [ 40%] rest_sources/tutorials/images/face0.png
copying images... [ 45%] 
rest_sources/tutorials/algorithms/../images/featuresDropoutTiedAutoencoder.png
copying images... [ 50%] 
rest_sources/tutorials/algorithms/../images/featuresDenoisingTiedAutoencoder.png
copying images... [ 54%] rest_sources/tutorials/images/reconstruction0.png
copying images... [ 59%] rest_sources/about_shark/images/lgplv3-147x51.png
copying images... [ 63%] 
rest_sources/tutorials/algorithms/../images/rbm_graph.svg
copying images... [ 68%] 
rest_sources/tutorials/algorithms/../images/featuresTiedAutoencoder.png
copying images... [ 72%] 
rest_sources/tutorials/algorithms/../images/featuresAutoencoder.png
copying images... [ 77%] rest_sources/tutorials/images/oldFaithful.jpg
copying images... [ 81%] 
rest_sources/tutorials/algorithms/../images/features.png
copying images... [ 86%] rest_sources/tutorials/images/facesMean.png
copying images... [ 90%] rest_sources/tutorials/images/oldFaithfulData.png
copying images... [ 95%] rest_sources/tutorials/images/linearRegressionData.png
copying images... [100%] 
rest_sources/tutorials/first_steps/../images/shark_directory_structure.png

copying downloadable files... [ 20%] 
../examples/Supervised/data/quickstartData.csv
copying downloadable files... [ 40%] ../examples/Supervised/data/C.csv
copying downloadable files... [ 60%] 
../examples/Supervised/data/regressionLabels.csv
copying downloadable files... [ 80%] static/text_files/test.txt
copying downloadable files... [100%] 
../examples/Supervised/data/regressionInputs.csv

copying static files... done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 474 warnings.
cd /<>/shark-3.1.3+ds1/obj-x86_64-linux-gnu/doc && /usr/bin/cmake -E 
copy /<>/shark-3.1.3+ds1/doc/doxygen_pages/css/besser.css 
/<>/shark-3.1.3+ds1/obj-x86_64-linux-gnu/doc/doxygen_pages/css/besser.css
make[3]: Leaving directory '/<>/shark-3.1.3+ds1/obj-x86_64-linux-gnu'
[ 16%] Built target doc
make[2]: Leaving directory '/<>/shark-3.1.3+ds1/obj-x86_64-linux-gnu'
Makefile:163: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>/shark-3.1.3+ds1/obj-x86_64-linux-gnu'
dh_auto_build: make -j64 returned exit code 2
debian/rules:28: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
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#853641: rheolef: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:rheolef
Version: 6.7-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/rheolef_6.7-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../config -I../../util/qd 
-I../../include -Wdate-time -D_FORTIFY_SOURCE=2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++11 -Wall -Werror -Wno-unused 
-Wno-strict-aliasing -Wno-literal-suffix -Wno-deprecated-declarations -O3 -MT 
tensor-eig3.lo -MD -MP -MF .deps/tensor-eig3.Tpo -c tensor-eig3.cc  -fPIC -DPIC 
-o .libs/tensor-eig3.o
mv -f .deps/tensor-eig3.Tpo .deps/tensor-eig3.Plo
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../config -I../../util/qd  -I../../include   -Wdate-time 
-D_FORTIFY_SOURCE=2  -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall 
-Werror -Wno-unused -Wno-strict-aliasing -Wno-literal-suffix 
-Wno-deprecated-declarations -O3  -MT tensor3.lo -MD -MP -MF .deps/tensor3.Tpo 
-c -o tensor3.lo tensor3.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../config -I../../util/qd 
-I../../include -Wdate-time -D_FORTIFY_SOURCE=2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++11 -Wall -Werror -Wno-unused 
-Wno-strict-aliasing -Wno-literal-suffix -Wno-deprecated-declarations -O3 -MT 
tensor3.lo -MD -MP -MF .deps/tensor3.Tpo -c tensor3.cc  -fPIC -DPIC -o 
.libs/tensor3.o
mv -f .deps/tensor3.Tpo .deps/tensor3.Plo
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../config -I../../util/qd  -I../../include   -Wdate-time 
-D_FORTIFY_SOURCE=2  -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall 
-Werror -Wno-unused -Wno-strict-aliasing -Wno-literal-suffix 
-Wno-deprecated-declarations -O3  -MT tensor4.lo -MD -MP -MF .deps/tensor4.Tpo 
-c -o tensor4.lo tensor4.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../config -I../../util/qd 
-I../../include -Wdate-time -D_FORTIFY_SOURCE=2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++11 -Wall -Werror -Wno-unused 
-Wno-strict-aliasing -Wno-literal-suffix -Wno-deprecated-declarations -O3 -MT 
tensor4.lo -MD -MP -MF .deps/tensor4.Tpo -c tensor4.cc  -fPIC -DPIC -o 
.libs/tensor4.o
mv -f .deps/tensor4.Tpo .deps/tensor4.Plo
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../config -I../../util/qd  -I../../include   -Wdate-time 
-D_FORTIFY_SOURCE=2  -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall 
-Werror -Wno-unused -Wno-strict-aliasing -Wno-literal-suffix 
-Wno-deprecated-declarations -O3  -MT tensor-exp.lo -MD -MP -MF 
.deps/tensor-exp.Tpo -c -o tensor-exp.lo tensor-exp.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../config -I../../util/qd 
-I../../include -Wdate-time -D_FORTIFY_SOURCE=2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++11 -Wall -Werror -Wno-unused 
-Wno-strict-aliasing -Wno-literal-suffix -Wno-deprecated-declarations -O3 -MT 
tensor-exp.lo -MD -MP -MF .deps/tensor-exp.Tpo -c tensor-exp.cc  -fPIC -DPIC -o 
.libs/tensor-exp.o
mv -f .deps/tensor-exp.Tpo .deps/tensor-exp.Plo
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../config -I../../util/qd  -I../../include   -Wdate-time 
-D_FORTIFY_SOURCE=2  -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall 
-Werror -Wno-unused -Wno-strict-aliasing -Wno-literal-suffix 
-Wno-deprecated-declarations -O3  -MT tensor4-dexp.lo -MD -MP -MF 
.deps/tensor4-dexp.Tpo -c -o tensor4-dexp.lo tensor4-dexp.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../config 

Bug#853653: scilab: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:scilab
Version: 5.5.2-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/scilab_5.5.2-4_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../modules/core/includes  -I./includes/ -I./src/jni/ -I./src/cpp/ 
-I./src/c/ -I../../modules/jvm/includes/ 
-I../../modules/output_stream/includes/ -I../../modules/commons/src/jni/ 
-I../../modules/localization/includes/ -I../../modules/fileio/includes/ 
-I../../modules/scicos_blocks/src/jni/ -I../../modules/api_scilab/includes/ 
-I/usr/lib/jvm/java-8-openjdk-amd64/include 
-I/usr/lib/jvm/java-8-openjdk-amd64/include/linux  -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fno-stack-protector -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o src/jni/libscixcos_algo_la-Palette.lo `test -f 
'src/jni/Palette.cpp' || echo './'`src/jni/Palette.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../modules/core/includes 
-I./includes/ -I./src/jni/ -I./src/cpp/ -I./src/c/ 
-I../../modules/jvm/includes/ -I../../modules/output_stream/includes/ 
-I../../modules/commons/src/jni/ -I../../modules/localization/includes/ 
-I../../modules/fileio/includes/ -I../../modules/scicos_blocks/src/jni/ 
-I../../modules/api_scilab/includes/ 
-I/usr/lib/jvm/java-8-openjdk-amd64/include 
-I/usr/lib/jvm/java-8-openjdk-amd64/include/linux -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fno-stack-protector -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c src/jni/Palette.cpp  -fPIC -DPIC -o 
src/jni/.libs/libscixcos_algo_la-Palette.o
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../modules/core/includes  -I./includes/ -I./src/jni/ -I./src/cpp/ 
-I./src/c/ -I../../modules/jvm/includes/ 
-I../../modules/output_stream/includes/ -I../../modules/commons/src/jni/ 
-I../../modules/localization/includes/ -I../../modules/fileio/includes/ 
-I../../modules/scicos_blocks/src/jni/ -I../../modules/api_scilab/includes/ 
-I/usr/lib/jvm/java-8-openjdk-amd64/include 
-I/usr/lib/jvm/java-8-openjdk-amd64/include/linux  -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fno-stack-protector -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o src/jni/libscixcos_algo_la-Modelica.lo `test -f 
'src/jni/Modelica.cpp' || echo './'`src/jni/Modelica.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../modules/core/includes 
-I./includes/ -I./src/jni/ -I./src/cpp/ -I./src/c/ 
-I../../modules/jvm/includes/ -I../../modules/output_stream/includes/ 
-I../../modules/commons/src/jni/ -I../../modules/localization/includes/ 
-I../../modules/fileio/includes/ -I../../modules/scicos_blocks/src/jni/ 
-I../../modules/api_scilab/includes/ 
-I/usr/lib/jvm/java-8-openjdk-amd64/include 
-I/usr/lib/jvm/java-8-openjdk-amd64/include/linux -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fno-stack-protector -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c src/jni/Modelica.cpp  -fPIC -DPIC -o 
src/jni/.libs/libscixcos_algo_la-Modelica.o
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../modules/core/includes  -I./includes/ -I./src/jni/ -I./src/cpp/ 
-I./src/c/ -I../../modules/jvm/includes/ 
-I../../modules/output_stream/includes/ -I../../modules/commons/src/jni/ 
-I../../modules/localization/includes/ -I../../modules/fileio/includes/ 
-I../../modules/scicos_blocks/src/jni/ -I../../modules/api_scilab/includes/ 
-I/usr/lib/jvm/java-8-openjdk-amd64/include 
-I/usr/lib/jvm/java-8-openjdk-amd64/include/linux  -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fno-stack-protector -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o src/cpp/libscixcos_algo_la-xcosUtilities.lo `test 
-f 

Bug#853635: qwtplot3d: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:qwtplot3d
Version: 0.2.7+svn191-10.1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/qwtplot3d_0.2.7+svn191-10.1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
  
(optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EE17_M_default_appendEm@Base
 0.2.7
  (optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EED1Ev@Base 0.2.7
  (optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EED2Ev@Base 0.2.7
- (optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EEaSERKS3_@Base 0.2.7
- (optional=templinst)_ZNSt6vectorIN5Qwt3D6Plot3D5LightESaIS2_EEaSERKS4_@Base 
0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIN5Qwt3D5LabelESaIS1_EEaSERKS3_@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIN5Qwt3D6Plot3D5LightESaIS2_EEaSERKS4_@Base 
0.2.7
  
(optional=templinst)_ZNSt6vectorIN5Qwt3D6TripleESaIS1_EE12emplace_backIJS1_EEEvDpOT_@Base
 0.2.7
- 
(optional=templinst)_ZNSt6vectorIN5Qwt3D6TripleESaIS1_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base
 0.2.7
- 
(optional=templinst)_ZNSt6vectorIN5Qwt3D6TripleESaIS1_EE19_M_emplace_back_auxIJS1_EEEvDpOT_@Base
 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIN5Qwt3D6TripleESaIS1_EE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPS1_S3_EERKS1_@Base
 0.2.7
+ 
_ZNSt6vectorIN5Qwt3D6TripleESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.2.7+svn191-10.1
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIN5Qwt3D6TripleESaIS1_EE19_M_emplace_back_auxIJS1_EEEvDpOT_@Base
 0.2.7
  (optional=templinst)_ZNSt6vectorIN5Qwt3D6TripleESaIS1_EEaSERKS3_@Base 0.2.7
- (optional=templinst)_ZNSt6vectorIPdSaIS0_EEaSERKS2_@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIPdSaIS0_EEaSERKS2_@Base 0.2.7
  (optional=templinst)_ZNSt6vectorIS_IPdSaIS0_EESaIS2_EED1Ev@Base 0.2.7
  (optional=templinst)_ZNSt6vectorIS_IPdSaIS0_EESaIS2_EED2Ev@Base 0.2.7
- (optional=templinst)_ZNSt6vectorIS_IPdSaIS0_EESaIS2_EEaSERKS4_@Base 0.2.7
- (optional=templinst)_ZNSt6vectorIS_IjSaIjEESaIS1_EED1Ev@Base 0.2.7
- (optional=templinst)_ZNSt6vectorIS_IjSaIjEESaIS1_EED2Ev@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIS_IPdSaIS0_EESaIS2_EEaSERKS4_@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIS_IjSaIjEESaIS1_EED1Ev@Base 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIS_IjSaIjEESaIS1_EED2Ev@Base 0.2.7
  (optional=templinst)_ZNSt6vectorIS_IjSaIjEESaIS1_EEaSERKS3_@Base 0.2.7
- 
(optional=templinst)_ZNSt6vectorIdSaIdEE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPdS1_EERKd@Base
 0.2.7
- 
(optional=templinst)_ZNSt6vectorIdSaIdEE19_M_emplace_back_auxIJRKdEEEvDpOT_@Base
 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIdSaIdEE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPdS1_EERKd@Base
 0.2.7
+ 
_ZNSt6vectorIdSaIdEE17_M_realloc_insertIJRKdEEEvN9__gnu_cxx17__normal_iteratorIPdS1_EEDpOT_@Base
 0.2.7+svn191-10.1
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIdSaIdEE19_M_emplace_back_auxIJRKdEEEvDpOT_@Base
 0.2.7
  (optional=templinst)_ZNSt6vectorIdSaIdEEaSERKS1_@Base 0.2.7
- 
(optional=templinst)_ZNSt6vectorIjSaIjEE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPjS1_EERKj@Base
 0.2.7
- 
(optional=templinst)_ZNSt6vectorIjSaIjEE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPjS1_EEmRKj@Base
 0.2.7
- (optional=templinst)_ZNSt6vectorIjSaIjEE17_M_default_appendEm@Base 0.2.7
- 
(optional=templinst)_ZNSt6vectorIjSaIjEE19_M_emplace_back_auxIJjEEEvDpOT_@Base 
0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIjSaIjEE13_M_insert_auxEN9__gnu_cxx17__normal_iteratorIPjS1_EERKj@Base
 0.2.7
+#MISSING: 0.2.7+svn191-10.1# 
(optional=templinst)_ZNSt6vectorIjSaIjEE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPjS1_EEmRKj@Base
 0.2.7

Bug#853624: pytango: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:pytango
Version: 9.2.0-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/pytango_9.2.0-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
copying tango/tango_futures.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/tango
copying tango/client.py -> /<>/.pybuild/pythonX.Y_2.7/build/tango
copying tango/futures.py -> /<>/.pybuild/pythonX.Y_2.7/build/tango
copying tango/globals.py -> /<>/.pybuild/pythonX.Y_2.7/build/tango
copying tango/green.py -> /<>/.pybuild/pythonX.Y_2.7/build/tango
copying tango/pipe_data.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/tango
creating /<>/.pybuild/pythonX.Y_2.7/build/tango/databaseds
copying tango/databaseds/database.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/tango/databaseds
copying tango/databaseds/db_errors.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/tango/databaseds
copying tango/databaseds/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/tango/databaseds
creating 
/<>/.pybuild/pythonX.Y_2.7/build/tango/databaseds/db_access
copying tango/databaseds/db_access/beacon.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/tango/databaseds/db_access
copying tango/databaseds/db_access/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/tango/databaseds/db_access
copying tango/databaseds/db_access/sqlite3.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/tango/databaseds/db_access
running build_ext
Traceback (most recent call last):
  File "setup.py", line 531, in 
main()
  File "setup.py", line 528, in main
return setup(**setup_args())
  File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
  File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
  File "setup.py", line 172, in run
dftbuild.run(self)
  File "/usr/lib/python2.7/distutils/command/build.py", line 128, in run
self.run_command(cmd_name)
  File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/build_ext.py", line 
75, in run
_build_ext.run(self)
  File "/usr/lib/python2.7/distutils/command/build_ext.py", line 340, in run
self.build_extensions()
  File "setup.py", line 231, in build_extensions
if V(gcc_ver) >= V("4.3.3"):
  File "/usr/lib/python2.7/distutils/version.py", line 40, in __init__
self.parse(vstring)
  File "/usr/lib/python2.7/distutils/version.py", line 107, in parse
raise ValueError, "invalid version number '%s'" % vstring
ValueError: invalid version number '7'
E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
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#853603: ovito: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:ovito
Version: 2.8.1+dfsg2-5
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/ovito_2.8.1+dfsg2-5_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
Generating moc source 
Particles_automoc.dir/moc_AmbientOcclusi_NWQUBGPRPAKE2O.cpp
Generating moc source 
Particles_automoc.dir/moc_AssignColorMod_YQ4AOCY4V4INRU.cpp
Generating moc source 
Particles_automoc.dir/moc_ColorCodingMod_REU5T3WHGONWOH.cpp
Generating moc source 
Particles_automoc.dir/moc_ColorLegendOve_DECOYBQMPHSQBW.cpp
Generating moc source 
Particles_automoc.dir/moc_AffineTransfor_F5BJU2C2XPKIHB.cpp
Generating moc source 
Particles_automoc.dir/moc_CombineParticl_JPUDXBHOSSTRQU.cpp
Generating moc source 
Particles_automoc.dir/moc_CreateBondsMod_Q4SFVF7Q2D2GSG.cpp
Generating moc source 
Particles_automoc.dir/moc_DeleteParticle_UQRULK6O2R6P53.cpp
Generating moc source 
Particles_automoc.dir/moc_LoadTrajectory_A5EFV3Z74YY33O.cpp
Generating moc source 
Particles_automoc.dir/moc_ShowPeriodicIm_EYFXBGAXV43OU5.cpp
Generating moc source Particles_automoc.dir/moc_SliceModifier_XOAF6Q6JX6JULK.cpp
Generating moc source 
Particles_automoc.dir/moc_WrapPeriodicIm_LRQ4RQG3Z6GFQD.cpp
Generating moc source 
Particles_automoc.dir/moc_ComputeBondLen_V52Y7NJTGHSUMQ.cpp
Generating moc source 
Particles_automoc.dir/moc_ComputePropert_PMG6IMT7LEHW4M.cpp
Generating moc source 
Particles_automoc.dir/moc_FreezeProperty_ZUJCWFUYOWEJYL.cpp
Generating moc source 
Particles_automoc.dir/moc_ClearSelection_KSHN4FP5CFYYLI.cpp
Generating moc source 
Particles_automoc.dir/moc_ExpandSelectio_DGKNUVM4K5ETZY.cpp
Generating moc source 
Particles_automoc.dir/moc_InvertSelectio_YAGUY4PRZRDBNC.cpp
Generating moc source 
Particles_automoc.dir/moc_ManualSelectio_5YZD54HNXSW52S.cpp
Generating moc source 
Particles_automoc.dir/moc_SelectExpressi_4CKG3CA5OCYA3I.cpp
Generating moc source 
Particles_automoc.dir/moc_SelectParticle_35IL24ISCYTBCG.cpp
Generating moc source 
Particles_automoc.dir/moc_BondPropertyOb_6MLMLPTBTAHAEN.cpp
Generating moc source Particles_automoc.dir/moc_BondType_KVAI4H764UANLB.cpp
Generating moc source 
Particles_automoc.dir/moc_BondTypeProper_SDDQQ6JGNDYNIZ.cpp
Generating moc source Particles_automoc.dir/moc_BondsDisplay_A7R3FEDMEP7T7B.cpp
Generating moc source Particles_automoc.dir/moc_BondsObject_BUN6OSNJEX2Z2L.cpp
Generating moc source 
Particles_automoc.dir/moc_ParticleDispla_UXVBVFYXB6QYYX.cpp
Generating moc source 
Particles_automoc.dir/moc_ParticleProper_3ABKLKXHK7JNUN.cpp
Generating moc source Particles_automoc.dir/moc_ParticleType_5DI27Z6JNQ6FWB.cpp
Generating moc source 
Particles_automoc.dir/moc_ParticleTypePr_4PIXKDQKB5XUHL.cpp
Generating moc source 
Particles_automoc.dir/moc_SimulationCell_TC6V3I7VTT5GS6.cpp
Generating moc source 
Particles_automoc.dir/moc_SimulationCell_LAWGMTIFHTPP5P.cpp
Generating moc source Particles_automoc.dir/moc_SurfaceMesh_7ZXZ7ANL63ZMV7.cpp
Generating moc source 
Particles_automoc.dir/moc_SurfaceMeshDis_OVDG3U4U2RMRWM.cpp
Generating moc source 
Particles_automoc.dir/moc_TrajectoryDisp_QACH2464B6QF7L.cpp
Generating moc source 
Particles_automoc.dir/moc_TrajectoryGene_V6MBZZ425GUNVS.cpp
Generating moc source 
Particles_automoc.dir/moc_TrajectoryObje_W7VIJKAAP2LWKC.cpp
Generating moc source Particles_automoc.dir/moc_VectorDisplay_IL7OY4HIS2DTJV.cpp
Generating moc source 
Particles_automoc.dir/moc_ParticleSelect_TNHG27Y7Y5ERUQ.cpp
Generating moc compilation Particles_automoc.cpp
make[3]: Leaving directory 
'/<>/ovito-2.8.1+dfsg2/obj-x86_64-linux-gnu'
[ 33%] Built target Particles_automoc
make[2]: Leaving directory 
'/<>/ovito-2.8.1+dfsg2/obj-x86_64-linux-gnu'
Makefile:163: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory 
'/<>/ovito-2.8.1+dfsg2/obj-x86_64-linux-gnu'
dh_auto_build: make -j64 returned exit code 2
debian/rules:5: recipe for target 'build' failed
make: *** 

Bug#853601: openturns: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:openturns
Version: 1.7-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/openturns_1.7-3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]

   ^
lib/src/CMakeFiles/OT.dir/build.make:113: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/ApproximationAlgorithm.cxx.o' failed
make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Algo/ApproximationAlgorithm.cxx.o] 
Error 1
lib/src/CMakeFiles/OT.dir/build.make:377: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/PenalizedLeastSquaresAlgorithm.cxx.o' 
failed
make[4]: *** 
[lib/src/CMakeFiles/OT.dir/Base/Algo/PenalizedLeastSquaresAlgorithm.cxx.o] 
Error 1
lib/src/CMakeFiles/OT.dir/build.make:449: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/FFT.cxx.o' failed
make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Algo/FFT.cxx.o] Error 1
lib/src/CMakeFiles/OT.dir/build.make:617: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/DesignProxy.cxx.o' failed
make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Algo/DesignProxy.cxx.o] Error 1
lib/src/CMakeFiles/OT.dir/build.make:665: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/LeastSquaresMethod.cxx.o' failed
make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Algo/LeastSquaresMethod.cxx.o] 
Error 1
lib/src/CMakeFiles/OT.dir/build.make:353: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/LeastSquaresMetaModelSelectionFactory.cxx.o'
 failed
make[4]: *** 
[lib/src/CMakeFiles/OT.dir/Base/Algo/LeastSquaresMetaModelSelectionFactory.cxx.o]
 Error 1
lib/src/CMakeFiles/OT.dir/build.make:473: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/KissFFT.cxx.o' failed
make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Algo/KissFFT.cxx.o] Error 1
lib/src/CMakeFiles/OT.dir/build.make:713: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/SVDMethod.cxx.o' failed
make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Algo/SVDMethod.cxx.o] Error 1
lib/src/CMakeFiles/OT.dir/build.make:737: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/CholeskyMethod.cxx.o' failed
make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Algo/CholeskyMethod.cxx.o] Error 1
lib/src/CMakeFiles/OT.dir/build.make:545: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/GaussKronrod.cxx.o' failed
make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Algo/GaussKronrod.cxx.o] Error 1
lib/src/CMakeFiles/OT.dir/build.make:1577: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Diff/FiniteDifferenceGradient.cxx.o' failed
make[4]: *** 
[lib/src/CMakeFiles/OT.dir/Base/Diff/FiniteDifferenceGradient.cxx.o] Error 1
lib/src/CMakeFiles/OT.dir/build.make:329: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/LeastSquaresMetaModelSelection.cxx.o' 
failed
make[4]: *** 
[lib/src/CMakeFiles/OT.dir/Base/Algo/LeastSquaresMetaModelSelection.cxx.o] 
Error 1
lib/src/CMakeFiles/OT.dir/build.make:1601: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Diff/FiniteDifferenceHessian.cxx.o' failed
make[4]: *** 
[lib/src/CMakeFiles/OT.dir/Base/Diff/FiniteDifferenceHessian.cxx.o] Error 1
lib/src/CMakeFiles/OT.dir/build.make:1625: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Diff/NonCenteredFiniteDifferenceGradient.cxx.o' 
failed
make[4]: *** 
[lib/src/CMakeFiles/OT.dir/Base/Diff/NonCenteredFiniteDifferenceGradient.cxx.o] 
Error 1
lib/src/CMakeFiles/OT.dir/build.make:593: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/IteratedQuadrature.cxx.o' failed
make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Algo/IteratedQuadrature.cxx.o] 
Error 1
lib/src/CMakeFiles/OT.dir/build.make:761: recipe for target 
'lib/src/CMakeFiles/OT.dir/Base/Algo/KarhunenLoeveP1Factory.cxx.o' failed
make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Algo/KarhunenLoeveP1Factory.cxx.o] 
Error 1
lib/src/CMakeFiles/OT.dir/build.make:1649: recipe for target 

Bug#853591: openigtlink: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:openigtlink
Version: 1.11.0-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/openigtlink_1.11.0-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
cd /<>/obj-x86_64-linux-gnu/Source && /usr/bin/cc  
-DOpenIGTLink_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<>/Source -I/<>/Source/igtlutil  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -w -fno-tree-vectorize 
-O3 -DNDEBUG -fPIC   -o CMakeFiles/OpenIGTLink.dir/igtlutil/igtl_polydata.o   
-c /<>/Source/igtlutil/igtl_polydata.c
[ 34%] Building CXX object 
Source/CMakeFiles/OpenIGTLink.dir/igtlColorTableMessage.o
cd /<>/obj-x86_64-linux-gnu/Source && /usr/bin/g++   
-DOpenIGTLink_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<>/Source -I/<>/Source/igtlutil  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -ftemplate-depth-50 
-fno-tree-vectorize -O3 -DNDEBUG -fPIC   -o 
CMakeFiles/OpenIGTLink.dir/igtlColorTableMessage.o -c 
/<>/Source/igtlColorTableMessage.cxx
[ 35%] Building CXX object 
Source/CMakeFiles/OpenIGTLink.dir/igtlCapabilityMessage.o
cd /<>/obj-x86_64-linux-gnu/Source && /usr/bin/g++   
-DOpenIGTLink_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<>/Source -I/<>/Source/igtlutil  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -ftemplate-depth-50 
-fno-tree-vectorize -O3 -DNDEBUG -fPIC   -o 
CMakeFiles/OpenIGTLink.dir/igtlCapabilityMessage.o -c 
/<>/Source/igtlCapabilityMessage.cxx
[ 36%] Building CXX object 
Source/CMakeFiles/OpenIGTLink.dir/igtlImageMetaMessage.o
cd /<>/obj-x86_64-linux-gnu/Source && /usr/bin/g++   
-DOpenIGTLink_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<>/Source -I/<>/Source/igtlutil  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -ftemplate-depth-50 
-fno-tree-vectorize -O3 -DNDEBUG -fPIC   -o 
CMakeFiles/OpenIGTLink.dir/igtlImageMetaMessage.o -c 
/<>/Source/igtlImageMetaMessage.cxx
[ 37%] Building CXX object 
Source/CMakeFiles/OpenIGTLink.dir/igtlLabelMetaMessage.o
cd /<>/obj-x86_64-linux-gnu/Source && /usr/bin/g++   
-DOpenIGTLink_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<>/Source -I/<>/Source/igtlutil  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -ftemplate-depth-50 
-fno-tree-vectorize -O3 -DNDEBUG -fPIC   -o 
CMakeFiles/OpenIGTLink.dir/igtlLabelMetaMessage.o -c 
/<>/Source/igtlLabelMetaMessage.cxx
[ 37%] Building CXX object Source/CMakeFiles/OpenIGTLink.dir/igtlPointMessage.o
cd /<>/obj-x86_64-linux-gnu/Source && /usr/bin/g++   
-DOpenIGTLink_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<>/Source -I/<>/Source/igtlutil  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -ftemplate-depth-50 
-fno-tree-vectorize -O3 -DNDEBUG -fPIC   -o 
CMakeFiles/OpenIGTLink.dir/igtlPointMessage.o -c 
/<>/Source/igtlPointMessage.cxx
[ 38%] Building CXX object 
Source/CMakeFiles/OpenIGTLink.dir/igtlTrackingDataMessage.o
cd /<>/obj-x86_64-linux-gnu/Source && /usr/bin/g++   
-DOpenIGTLink_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<>/Source -I/<>/Source/igtlutil  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -ftemplate-depth-50 
-fno-tree-vectorize -O3 -DNDEBUG -fPIC   -o 
CMakeFiles/OpenIGTLink.dir/igtlTrackingDataMessage.o -c 
/<>/Source/igtlTrackingDataMessage.cxx
[ 39%] Building CXX object 
Source/CMakeFiles/OpenIGTLink.dir/igtlPolyDataMessage.o
cd /<>/obj-x86_64-linux-gnu/Source && /usr/bin/g++   
-DOpenIGTLink_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<>/Source -I/<>/Source/igtlutil  -g -O2 

Bug#853588: opencv: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:opencv
Version: 2.4.9.1+dfsg-2.1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/opencv_2.4.9.1+dfsg-2.1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]

Determining if the include file sys/videoio.h exists failed with the following 
output:
Change Dir: 
/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_0bde0/fast"
make[2]: Entering directory 
'/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_0bde0.dir/build.make 
CMakeFiles/cmTC_0bde0.dir/build
make[3]: Entering directory 
'/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_0bde0.dir/CheckIncludeFile.c.o
/usr/bin/cc-g -O2 -fdebug-prefix-map=/<>/opencv-2.4.9.1+dfsg=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W 
-Wall -Werror=return-type -Werror=address -Werror=sequence-point -Wformat 
-Werror=format-security -Wmissing-declarations -Wmissing-prototypes 
-Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wno-narrowing 
-fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -msse 
-msse2 -ffunction-sections  -O3 -DNDEBUG   -o 
CMakeFiles/cmTC_0bde0.dir/CheckIncludeFile.c.o   -c 
/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.c
/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.c:1:10:
 fatal error: sys/videoio.h: No such file or directory
 #include 
  ^~~
compilation terminated.
CMakeFiles/cmTC_0bde0.dir/build.make:65: recipe for target 
'CMakeFiles/cmTC_0bde0.dir/CheckIncludeFile.c.o' failed
make[3]: *** [CMakeFiles/cmTC_0bde0.dir/CheckIncludeFile.c.o] Error 1
make[3]: Leaving directory 
'/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_0bde0/fast' failed
make[2]: *** [cmTC_0bde0/fast] Error 2
make[2]: Leaving directory 
'/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


Determining if the include file ffmpeg/avformat.h exists failed with the 
following output:
Change Dir: 
/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_e0ac5/fast"
make[2]: Entering directory 
'/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_e0ac5.dir/build.make 
CMakeFiles/cmTC_e0ac5.dir/build
make[3]: Entering directory 
'/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_e0ac5.dir/CheckIncludeFile.c.o
/usr/bin/cc-g -O2 -fdebug-prefix-map=/<>/opencv-2.4.9.1+dfsg=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W 
-Wall -Werror=return-type -Werror=address -Werror=sequence-point -Wformat 
-Werror=format-security -Wmissing-declarations -Wmissing-prototypes 
-Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wno-narrowing 
-fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -msse 
-msse2 -ffunction-sections  -O3 -DNDEBUG   -o 
CMakeFiles/cmTC_e0ac5.dir/CheckIncludeFile.c.o   -c 
/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.c
/<>/opencv-2.4.9.1+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.c:1:10:
 fatal error: ffmpeg/avformat.h: No such file or directory
 #include 
  ^~~
compilation terminated.
CMakeFiles/cmTC_e0ac5.dir/build.make:65: recipe for target 
'CMakeFiles/cmTC_e0ac5.dir/CheckIncludeFile.c.o' failed
make[3]: *** [CMakeFiles/cmTC_e0ac5.dir/CheckIncludeFile.c.o] Error 1
make[3]: Leaving directory 

Bug#853557: morse-simulator: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:morse-simulator
Version: 1.4-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/morse-simulator_1.4-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_SYSCONFDIR
CPACK_DEBIAN_PACKAGE_DEPENDS


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
make[1]: Leaving directory '/<>'
   dh_auto_build
dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
make -j1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -H/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make -f CMakeFiles/man.dir/build.make CMakeFiles/man.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/man.dir/DependInfo.cmake 
--color=
Scanning dependencies of target man
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f CMakeFiles/man.dir/build.make CMakeFiles/man.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
env 
PYTHONPATH=/<>/obj-x86_64-linux-gnu:/<>/obj-x86_64-linux-gnu/src:/<>/obj-x86_64-linux-gnu/fakeenv:/<>/src:/<>/testing:/<>/bindings/pymorse/src/:$PYTHONPATH
 PYTHONDONTWRITEBYTECODE="morse" MORSESOURCE=/<> /usr/bin/python3 
/usr/bin/sphinx-build -b man -c /<>/obj-x86_64-linux-gnu/doc 
/<>/doc/man /<>/obj-x86_64-linux-gnu/doc/man && 
/bin/gzip -f /<>/obj-x86_64-linux-gnu/doc/man/*.1
Running Sphinx v1.4.9
making output directory...

Exception occurred:
  File "conf.py", line 15, in 
ImportError: No module named 'version'
The full traceback has been saved in /tmp/sphinx-err-y2w85cz7.log, if you want 
to report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
CMakeFiles/man.dir/build.make:60: recipe for target 'CMakeFiles/man' failed
make[3]: *** [CMakeFiles/man] Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:134: recipe for target 'CMakeFiles/man.dir/all' failed
make[2]: *** [CMakeFiles/man.dir/all] Error 2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
Makefile:141: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_build: make -j1 returned exit code 2
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
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#853541: mathicgb: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:mathicgb
Version: 1.0~git20170104-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/mathicgb_1.0~git20170104-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating build/autotools/mathicgb.pc
config.status: executing depfiles commands
config.status: executing libtool commands
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
/bin/bash ./libtool  --tag=CXX   --mode=compile g++ -DPACKAGE_NAME=\"mathicgb\" 
-DPACKAGE_TARNAME=\"mathicgb\" -DPACKAGE_VERSION=\"1.0\" 
-DPACKAGE_STRING=\"mathicgb\ 1.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DHAVE_CXX11=1 -DPACKAGE=\"mathicgb\" -DVERSION=\"1.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I.  -I./ -I./src/ 
-I/usr/src/gtest/include -I/usr/src/gtest -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o src/mathicgb/ReducerPack.lo 
src/mathicgb/ReducerPack.cpp
libtool: compile:  g++ -DPACKAGE_NAME=\"mathicgb\" 
-DPACKAGE_TARNAME=\"mathicgb\" -DPACKAGE_VERSION=\"1.0\" 
"-DPACKAGE_STRING=\"mathicgb 1.0\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DHAVE_CXX11=1 -DPACKAGE=\"mathicgb\" -DVERSION=\"1.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I. -I./ -I./src/ 
-I/usr/src/gtest/include -I/usr/src/gtest -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 "-fdebug-prefix-map=/<>=." -fstack-protector-strong -Wformat 
-Werror=format-security -c src/mathicgb/ReducerPack.cpp  -fPIC -DPIC -o 
src/mathicgb/.libs/ReducerPack.o
libtool: compile:  g++ -DPACKAGE_NAME=\"mathicgb\" 
-DPACKAGE_TARNAME=\"mathicgb\" -DPACKAGE_VERSION=\"1.0\" 
"-DPACKAGE_STRING=\"mathicgb 1.0\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DHAVE_CXX11=1 -DPACKAGE=\"mathicgb\" -DVERSION=\"1.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I. -I./ -I./src/ 
-I/usr/src/gtest/include -I/usr/src/gtest -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 "-fdebug-prefix-map=/<>=." -fstack-protector-strong -Wformat 
-Werror=format-security -c src/mathicgb/ReducerPack.cpp -o 
src/mathicgb/ReducerPack.o >/dev/null 2>&1
/bin/bash ./libtool  --tag=CXX   --mode=compile g++ -DPACKAGE_NAME=\"mathicgb\" 
-DPACKAGE_TARNAME=\"mathicgb\" -DPACKAGE_VERSION=\"1.0\" 
-DPACKAGE_STRING=\"mathicgb\ 1.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
-DHAVE_CXX11=1 -DPACKAGE=\"mathicgb\" -DVERSION=\"1.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 

Bug#853545: meshlab: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:meshlab
Version: 1.3.2+dfsg1-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/meshlab_1.3.2+dfsg1-3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
../../../vcglib/wrap/io_trimesh/import_out.h: In static member function 'static 
bool vcg::tri::io::ImporterOUT::ReadHeader(const char*, unsigned 
int&, unsigned int&)':
../../../vcglib/wrap/io_trimesh/import_out.h:91:15: error: no matching function 
for call to 'vcg::tri::io::ImporterOUT::ReadHeader(FILE*&)'
  ReadHeader(fp);

   ^
../../../vcglib/wrap/io_trimesh/import_out.h:80:13: note: candidate: static 
bool vcg::tri::io::ImporterOUT::ReadHeader(FILE*, unsigned int&, 
unsigned int&)
 static bool ReadHeader(FILE *fp,unsigned int _cams, unsigned int 
_points){

 ^~
../../../vcglib/wrap/io_trimesh/import_out.h:80:13: note:   candidate expects 3 
arguments, 1 provided
../../../vcglib/wrap/io_trimesh/import_out.h:88:13: note: candidate: static 
bool vcg::tri::io::ImporterOUT::ReadHeader(const char*, unsigned 
int&, unsigned int&)
 static bool ReadHeader(const char * filename,unsigned int &/*num_cams*/, 
unsigned int &/*num_points*/){

 ^~
../../../vcglib/wrap/io_trimesh/import_out.h:88:13: note:   candidate expects 3 
arguments, 1 provided
../../../vcglib/wrap/io_trimesh/import_out.h: In static member function 'static 
int vcg::tri::io::ImporterOUT::Open(OpenMeshType&, 
std::vector&, 
std::vector&, const char*, const char*, 
const char*, bool (*)(int, const char*)) [with OpenMeshType = CMeshO]':
../../../vcglib/wrap/io_trimesh/import_out.h:152:11: warning: ignoring return 
value of 'int fscanf(FILE*, const char*, ...)', declared with attribute 
warn_unused_result [-Wunused-result]
 fscanf(fp,"%f %f %f ",,,);

 ~~^
../../../vcglib/wrap/io_trimesh/import_out.h:154:11: warning: ignoring return 
value of 'int fscanf(FILE*, const char*, ...)', declared with attribute 
warn_unused_result [-Wunused-result]
 fscanf(fp,"%d %d %d ",,,);

 ~~^
../../../vcglib/wrap/io_trimesh/import_out.h:157:11: warning: ignoring return 
value of 'int fscanf(FILE*, const char*, ...)', declared with attribute 
warn_unused_result [-Wunused-result]
 fscanf(fp,"%d ",_corr);

 ~~^~
../../../vcglib/wrap/io_trimesh/import_out.h:159:13: warning: ignoring return 
value of 'int fscanf(FILE*, const char*, ...)', declared with attribute 
warn_unused_result [-Wunused-result]
   fscanf(fp,"%d %d %f %f ",_cam,_sift,,);

   ~~^~
../../../vcglib/wrap/io_trimesh/import_out.h: In static member function 'static 
void vcg::tri::io::ImporterOUT::readline(FILE*, char*, int) [with 
OpenMeshType = CMeshO]':
../../../vcglib/wrap/io_trimesh/import_out.h:72:11: warning: ignoring return 
value of 'int fscanf(FILE*, const char*, ...)', declared with attribute 
warn_unused_result [-Wunused-result]
 fscanf(fp, "%c", );

 ~~^~
../../../vcglib/wrap/io_trimesh/import_out.h:75:15: warning: ignoring return 
value of 'int fscanf(FILE*, const char*, ...)', declared with attribute 
warn_unused_result [-Wunused-result]
 fscanf(fp, "%c", );

 ~~^~
Makefile:385: recipe for target 'meshlabdocumentbundler.o' failed
make[2]: *** [meshlabdocumentbundler.o] Error 1
make[2]: Leaving directory 
'/<>/meshlab-1.3.2+dfsg1/meshlab/src/common'
Makefile:111: recipe for target 'sub-common-make_default-ordered' failed
make[1]: *** [sub-common-make_default-ordered] Error 2
make[1]: Leaving directory '/<>/meshlab-1.3.2+dfsg1/meshlab/src'
debian/rules:59: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 

Bug#853540: mathic: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:mathic
Version: 1.0~git20160320-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/mathic_1.0~git20160320-4_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
- 
(optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
 1.0~git20160320
+#MISSING: 1.0~git20160320-4# 
(optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
 1.0~git20160320
  _ZNK6mathic13BoolParameter12argumentTypeB5cxx11Ev@Base 1.0~git20160320
  _ZNK6mathic13BoolParameter13valueAsStringB5cxx11Ev@Base 1.0~git20160320
  _ZNK6mathic13ColumnPrinter14getColumnCountEv@Base 1.0~git20130827
@@ -118,20 +118,24 @@
  
_ZNK6mathic9CliParser29pushBackRegisteredActionNamesERSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base
 1.0~git20160320
  
_ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED1Ev@Base 
1.0~git20160320
  
_ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED2Ev@Base 
1.0~git20160320
- 
(optional)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base
 1.0~git20160320
- 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJRKS5_EEEvDpOT_@Base
 1.0~git20160320
+ 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 1.0~git20160320-4
+#MISSING: 1.0~git20160320-4# 
(optional)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base
 1.0~git20160320
+#MISSING: 1.0~git20160320-4# 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJRKS5_EEEvDpOT_@Base
 1.0~git20160320
  
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base
 1.0~git20160320
  
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base
 1.0~git20160320
- 
(optional)_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base
 1.0~git20130827
- 
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIJS6_EEEvDpOT_@Base
 1.0~git20130827
+ 
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE17_M_realloc_insertIJS6_EEEvN9__gnu_cxx17__normal_iteratorIPS6_S8_EEDpOT_@Base
 1.0~git20160320-4
+#MISSING: 1.0~git20160320-4# 
(optional)_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base
 1.0~git20130827
+#MISSING: 1.0~git20160320-4# 
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIJS6_EEEvDpOT_@Base
 1.0~git20130827
  
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EED1Ev@Base
 1.0~git20130827
  
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EED2Ev@Base
 1.0~git20130827
- 
(optional)_ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIISE_EEEvDpOT_@Base
 1.0~git20160320
- 
_ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIJSE_EEEvDpOT_@Base
 1.0~git20160320
+ 
_ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE17_M_realloc_insertIJSE_EEEvN9__gnu_cxx17__normal_iteratorIPSE_SG_EEDpOT_@Base
 1.0~git20160320-4
+#MISSING: 1.0~git20160320-4# 

Bug#853513: libvigraimpex: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/libvigraimpex_1.10.0+git20160211.167be93+dfsg-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:41:
/usr/include/c++/7/sstream:790:5: note: candidate: template void 
std::__cxx11::swap(std::__cxx11::basic_istringstream<_CharT, _Traits, 
_Allocator>&, std::__cxx11::basic_istringstream<_CharT, _Traits, _Allocator>&)
 swap(basic_istringstream<_CharT, _Traits, _Allocator>& __x,
 ^~~~
/usr/include/c++/7/sstream:790:5: note:   template argument 
deduction/substitution failed:
In file included from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/resampling_convolution.hxx:46:0,
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/resizeimage.hxx:46,
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/stdimagefunctions.hxx:74,
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/nonlineardiffusion.hxx:41,
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/convolution.hxx:44,
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:45:
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/imagecontainer.hxx:770:53:
 note:   mismatched types 'std::__cxx11::basic_istringstream<_CharT, _Traits, 
_Allocator>' and 'int'
 std::swap(highestLevel_, other.highestLevel_);
 ^
In file included from /usr/include/c++/7/complex:45:0,
 from 
/usr/include/boost/python/converter/builtin_converters.hpp:13,
 from /usr/include/boost/python/converter/arg_to_python.hpp:17,
 from /usr/include/boost/python/call.hpp:15,
 from /usr/include/boost/python/object_core.hpp:14,
 from /usr/include/boost/python/args.hpp:25,
 from /usr/include/boost/python.hpp:11,
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:41:
/usr/include/c++/7/sstream:783:5: note: candidate: template void 
std::__cxx11::swap(std::__cxx11::basic_stringbuf<_CharT, _Traits, _Alloc>&, 
std::__cxx11::basic_stringbuf<_CharT, _Traits, _Alloc>&)
 swap(basic_stringbuf<_CharT, _Traits, _Allocator>& __x,
 ^~~~
/usr/include/c++/7/sstream:783:5: note:   template argument 
deduction/substitution failed:
In file included from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/resampling_convolution.hxx:46:0,
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/resizeimage.hxx:46,
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/stdimagefunctions.hxx:74,
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/nonlineardiffusion.hxx:41,
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/convolution.hxx:44,
 from 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/vigranumpy/src/core/convolution.cxx:45:
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/imagecontainer.hxx:770:53:
 note:   mismatched types 'std::__cxx11::basic_stringbuf<_CharT, _Traits, 
_Alloc>' and 'int'
 std::swap(highestLevel_, other.highestLevel_);
 ^
vigranumpy/src/core/CMakeFiles/vigranumpy_filters.dir/build.make:89: recipe for 
target 
'vigranumpy/src/core/CMakeFiles/vigranumpy_filters.dir/convolution.cxx.o' failed
make[4]: *** 
[vigranumpy/src/core/CMakeFiles/vigranumpy_filters.dir/convolution.cxx.o] 

Bug#853518: linbox: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:linbox
Version: 1.4.2-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/linbox_1.4.2-3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
make[3]: Entering directory '/<>/tests/matrix'
make[3]: Nothing to be done for 'check'.
make[3]: Leaving directory '/<>/tests/matrix'
make[3]: Entering directory '/<>/tests'
make  check-TESTS
make[4]: Entering directory '/<>/tests'
make[5]: Entering directory '/<>/tests'
g++ -DHAVE_CONFIG_H -I. -I..  -DLinBoxTestOnly -O2 -Wall -g -DNDEBUG 
-U_LB_DEBUG -g -DNDEBUG -U_LB_DEBUG -I../linbox -D__FFLASFFPACK_HAVE_CBLAS 
-fopenmp -std=gnu++11  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o test-commentator.o test-commentator.C
g++ -DHAVE_CONFIG_H -I. -I..  -DLinBoxTestOnly -O2 -Wall -g -DNDEBUG 
-U_LB_DEBUG -g -DNDEBUG -U_LB_DEBUG -I../linbox -D__FFLASFFPACK_HAVE_CBLAS 
-fopenmp -std=gnu++11  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o test-det.o test-det.C
g++ -DHAVE_CONFIG_H -I. -I..  -DLinBoxTestOnly -O2 -Wall -g -DNDEBUG 
-U_LB_DEBUG -g -DNDEBUG -U_LB_DEBUG -I../linbox -D__FFLASFFPACK_HAVE_CBLAS 
-fopenmp -std=gnu++11  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o test-frobenius.o test-frobenius.C
g++ -DHAVE_CONFIG_H -I. -I..  -DLinBoxTestOnly -O2 -Wall -g -DNDEBUG 
-U_LB_DEBUG -g -DNDEBUG -U_LB_DEBUG -I../linbox -D__FFLASFFPACK_HAVE_CBLAS 
-fopenmp -std=gnu++11  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o test-solve.o test-solve.C
g++ -DHAVE_CONFIG_H -I. -I..  -DLinBoxTestOnly -O2 -Wall -g -DNDEBUG 
-U_LB_DEBUG -g -DNDEBUG -U_LB_DEBUG -I../linbox -D__FFLASFFPACK_HAVE_CBLAS 
-fopenmp -std=gnu++11  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o test-rational-solver.o test-rational-solver.C
g++ -DHAVE_CONFIG_H -I. -I..  -DLinBoxTestOnly -O2 -Wall -g -DNDEBUG 
-U_LB_DEBUG -g -DNDEBUG -U_LB_DEBUG -I../linbox -D__FFLASFFPACK_HAVE_CBLAS 
-fopenmp -std=gnu++11  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o test-rational-solver-adaptive.o 
test-rational-solver-adaptive.C
g++ -DHAVE_CONFIG_H -I. -I..  -DLinBoxTestOnly -O2 -Wall -g -DNDEBUG 
-U_LB_DEBUG -g -DNDEBUG -U_LB_DEBUG -I../linbox -D__FFLASFFPACK_HAVE_CBLAS 
-fopenmp -std=gnu++11  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o test-rank-u32.o test-rank-u32.C
g++ -DHAVE_CONFIG_H -I. -I..  -DLinBoxTestOnly -O2 -Wall -g -DNDEBUG 
-U_LB_DEBUG -g -DNDEBUG -U_LB_DEBUG -I../linbox -D__FFLASFFPACK_HAVE_CBLAS 
-fopenmp -std=gnu++11  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o test-rank-md.o test-rank-md.C
g++ -DHAVE_CONFIG_H -I. -I..  -DLinBoxTestOnly -O2 -Wall -g -DNDEBUG 
-U_LB_DEBUG -g -DNDEBUG -U_LB_DEBUG -I../linbox -D__FFLASFFPACK_HAVE_CBLAS 
-fopenmp -std=gnu++11  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o test-rank-Int.o test-rank-Int.C
g++ -DHAVE_CONFIG_H -I. -I..  -DLinBoxTestOnly -O2 -Wall -g -DNDEBUG 
-U_LB_DEBUG -g -DNDEBUG -U_LB_DEBUG -I../linbox -D__FFLASFFPACK_HAVE_CBLAS 
-fopenmp -std=gnu++11  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o test-cra.o test-cra.C
g++ -DHAVE_CONFIG_H -I. -I..  -DLinBoxTestOnly -O2 

Bug#853501: libosmocore: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:libosmocore
Version: 0.9.0-6
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/libosmocore_0.9.0-6_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
gb/gprs_ns_test.c:224:28: warning: 'gprs_ns_unblock' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_unblock[1] = {
^~~
gb/gprs_ns_test.c:219:28: warning: 'gprs_ns_alive_ack' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_alive_ack[1] = {
^
gb/gprs_ns_test.c:206:28: warning: 'gprs_ns_alive' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_alive[1] = {
^
gb/gprs_ns_test.c:200:28: warning: 'gprs_ns_reset_nsei2' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_reset_nsei2[12] = {
^~~
gb/gprs_ns_test.c:192:28: warning: 'gprs_ns_reset_vci2' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_reset_vci2[12] = {
^~
gb/gprs_ns_test.c:184:28: warning: 'gprs_ns_reset' defined but not used 
[-Wunused-const-variable=]
 static const unsigned char gprs_ns_reset[12] = {
^
/bin/bash ../libtool  --tag=CC   --mode=link gcc -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o 
gb/gprs_ns_test gb/gprs_ns_test.o ../src/libosmocore.la ../src/gb/libosmogb.la 
../src/vty/libosmovty.la -ldl  
libtool: link: gcc -Wall -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -Wl,--as-needed -o gb/.libs/gprs_ns_test gb/gprs_ns_test.o  
../src/.libs/libosmocore.so ../src/gb/.libs/libosmogb.so 
../src/vty/.libs/libosmovty.so -ldl
gcc -DHAVE_CONFIG_H -I. -I..  -I../include -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
kasumi/kasumi_test.o kasumi/kasumi_test.c
/bin/bash ../libtool  --tag=CC   --mode=link gcc -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o 
kasumi/kasumi_test kasumi/kasumi_test.o ../src/libosmocore.la 
../src/gsm/libgsmint.la 
libtool: link: gcc -Wall -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -Wl,--as-needed -o kasumi/.libs/kasumi_test kasumi/kasumi_test.o 
 ../src/.libs/libosmocore.so ../src/gsm/.libs/libgsmint.a 
/<>/src/.libs/libosmocore.so -ldl
kasumi/kasumi_test.o: In function `test_expansion':
./tests/kasumi/kasumi_test.c:27: undefined reference to `_compare_mem'
./tests/kasumi/kasumi_test.c:28: undefined reference to `_compare_mem'
./tests/kasumi/kasumi_test.c:29: undefined reference to `_compare_mem'
./tests/kasumi/kasumi_test.c:30: undefined reference to `_compare_mem'
./tests/kasumi/kasumi_test.c:31: undefined reference to `_compare_mem'
kasumi/kasumi_test.o:./tests/kasumi/kasumi_test.c:32: more undefined references 
to `_compare_mem' follow
collect2: error: ld returned 1 exit status
Makefile:686: recipe for target 'kasumi/kasumi_test' failed
make[5]: *** [kasumi/kasumi_test] Error 1
make[5]: Leaving directory '/<>/tests'
Makefile:1028: recipe for target 'check-am' failed
make[4]: *** [check-am] Error 2
make[4]: Leaving directory '/<>/tests'
Makefile:518: recipe for target 'check-recursive' failed
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory '/<>'
Makefile:809: recipe for target 'check' failed
make[2]: *** [check] Error 2
make[2]: Leaving directory '/<>'

Bug#853436: gtkmathview: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:gtkmathview
Version: 0.8.0-14
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/gtkmathview_0.8.0-14_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
  SVG yes
  PostScript  yes

Performance

  Builder cache   no

touch debian/stamp-autotools
/usr/bin/make -C . 
make[1]: Entering directory '/<>'
/usr/bin/make  all-recursive
make[2]: Entering directory '/<>'
Making all in scripts
make[3]: Entering directory '/<>/scripts'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/scripts'
Making all in config
make[3]: Entering directory '/<>/config'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/config'
Making all in auto
make[3]: Entering directory '/<>/auto'
g++ -DHAVE_CONFIG_H -I. -I.. -I../src/common -I../src/frontend/gmetadom -I.. 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/libxml2 -I/usr/include/gmetadom/gdome_cpp_smart 
-I/usr/include/libgdome   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -W -Wall -c -o dumpEntitiesTable.o dumpEntitiesTable.cc
In file included from 
/usr/include/gmetadom/gdome_cpp_smart/GdomeSmartDOMChar.hh:78:0,
 from 
/usr/include/gmetadom/gdome_cpp_smart/GdomeSmartDOMBasic.hh:27,
 from /usr/include/gmetadom/gdome_cpp_smart/GdomeSmartDOM.hh:27,
 from ../src/frontend/gmetadom/gmetadom.hh:22,
 from dumpEntitiesTable.cc:25:
/usr/include/gmetadom/gdome_cpp_smart/GdomeSmartDOMTraits.hh: In static member 
function 'static std::char_traits::char_type 
std::char_traits::to_char_type(const int_type&)':
/usr/include/gmetadom/gdome_cpp_smart/GdomeSmartDOMTraits.hh:102:25: warning: 
narrowing conversion of '(std::char_traits::int_type)__c' 
from 'std::char_traits::int_type {aka long unsigned int}' 
to 'std::char_traits::char_type {aka short unsigned int}' 
inside { } [-Wnarrowing]
   char_type __r = { __c };
 ^~~
/bin/bash ../libtool  --tag=CXX   --mode=link g++  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -W -Wall  -Wl,-z,relro -o dumpEntitiesTable 
dumpEntitiesTable.o -lgmetadom_gdome_cpp_smart -lgdome -lglib-2.0 -lxml2 
libtool: link: g++ -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -W -Wall -Wl,-z 
-Wl,relro -o dumpEntitiesTable dumpEntitiesTable.o  
/usr/lib/libgmetadom_gdome_cpp_smart.so /usr/lib/libgdome.so -lglib-2.0 -lxml2
dumpEntitiesTable.o: In function `dump(char const*)':
./auto/dumpEntitiesTable.cc:43: undefined reference to 
`GdomeSmartDOM::GdomeString::operator std::__cxx11::basic_string() const'
./auto/dumpEntitiesTable.cc:47: undefined reference to 
`GdomeSmartDOM::GdomeString::operator std::__cxx11::basic_string() const'
collect2: error: ld returned 1 exit status
Makefile:448: recipe for target 'dumpEntitiesTable' failed
make[3]: *** [dumpEntitiesTable] Error 1
make[3]: Leaving directory '/<>/auto'
Makefile:559: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:444: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>'
/usr/share/cdbs/1/class/makefile.mk:77: recipe for target 
'debian/stamp-makefile-build' failed
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
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#853420: gle-graphics: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:gle-graphics
Version: 4.2.5-6
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/gle-graphics_4.2.5-6_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
 void g_arrowline(double x2, double y2, int flag, int can_fillpath) 
throw(ParserError);
^
../core.h:276:54: warning: dynamic exception specifications are deprecated in 
C++11; use 'noexcept' instead [-Wdeprecated]
 void g_arrow(double dx, double dy, int can_fillpath) throw(ParserError);
  ^
../core.h:298:47: warning: dynamic exception specifications are deprecated in 
C++11; use 'noexcept' instead [-Wdeprecated]
 int g_set_compatibility(const string& compat) throw (ParserError);
   ^
../core.h:299:49: warning: dynamic exception specifications are deprecated in 
C++11; use 'noexcept' instead [-Wdeprecated]
 int g_parse_compatibility(const string& compat) throw (ParserError);
 ^
../core.h:326:43: warning: dynamic exception specifications are deprecated in 
C++11; use 'noexcept' instead [-Wdeprecated]
 void g_set_arrow_style(const char* shape) throw (ParserError);
   ^
../core.h:327:39: warning: dynamic exception specifications are deprecated in 
C++11; use 'noexcept' instead [-Wdeprecated]
 void g_set_arrow_tip(const char* tip) throw (ParserError);
   ^
../core.h:329:59: warning: dynamic exception specifications are deprecated in 
C++11; use 'noexcept' instead [-Wdeprecated]
 void g_bitmap(GLEBitmap*, double wx, double wy, int type) throw(ParserError);
   ^
../core.h:421:47: warning: dynamic exception specifications are deprecated in 
C++11; use 'noexcept' instead [-Wdeprecated]
 void g_postscript(char *ss,double w,double h) throw (ParserError);
   ^
g++ -fPIC -DHAVE_CONFIG_H -DGLEVN="\"4.2.5\"" -Wno-write-strings -pthread 
-I/usr/include/poppler/glib -I/usr/include/poppler -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libpng16 
-Wdate-time -D_FORTIFY_SOURCE=2 -DDEBIAN_EPOCH=1467909911 -c fcontour.cpp -o 
fcontour.o
g++ -fPIC -DHAVE_CONFIG_H -DGLEVN="\"4.2.5\"" -Wno-write-strings -pthread 
-I/usr/include/poppler/glib -I/usr/include/poppler -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libpng16 
-Wdate-time -D_FORTIFY_SOURCE=2 -DDEBIAN_EPOCH=1467909911 -c ffitcontour.cpp -o 
ffitcontour.o
In file included from ffitcontour.cpp:51:0:
/usr/include/stdlib.h:735:12: error: expected unqualified-id before 'int'
 extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^
/usr/include/stdlib.h:735:12: error: expected ')' before 'int'
/usr/include/stdlib.h:735:12: error: expected ')' before 'int'
In file included from /usr/include/c++/7/cmath:47:0,
 from /usr/include/c++/7/math.h:36,
 from ffitcontour.cpp:53:
/usr/include/c++/7/bits/std_abs.h:52:11: error: '::abs' has not been declared
   using ::abs;
   ^~~
Makefile:60: recipe for target 'ffitcontour.o' failed
make[3]: *** 

Bug#853416: getfem++: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:getfem++
Version: 5.1+dfsg1-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/getfem++_5.1+dfsg1-4_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
   if (i) dists.push_back(i); if (j) dists.push_back(j);
  ^~
../src/getfem/getfem_mesher.h:631:7: warning: this 'if' clause does not 
guard... [-Wmisleading-indentation]
   if (k) dists.push_back(k); if (l) dists.push_back(l);
   ^~
../src/getfem/getfem_mesher.h:631:34: note: ...this statement, but the latter 
is misleadingly indented as if it were guarded by the 'if'
   if (k) dists.push_back(k); if (l) dists.push_back(l);
  ^~
../src/getfem/getfem_mesher.h:632:7: warning: this 'if' clause does not 
guard... [-Wmisleading-indentation]
   if (m) dists.push_back(m); if (n) dists.push_back(n);
   ^~
../src/getfem/getfem_mesher.h:632:34: note: ...this statement, but the latter 
is misleadingly indented as if it were guarded by the 'if'
   if (m) dists.push_back(m); if (n) dists.push_back(n);
  ^~
../src/getfem/getfem_mesher.h:633:7: warning: this 'if' clause does not 
guard... [-Wmisleading-indentation]
   if (o) dists.push_back(o); if (p) dists.push_back(p);
   ^~
../src/getfem/getfem_mesher.h:633:34: note: ...this statement, but the latter 
is misleadingly indented as if it were guarded by the 'if'
   if (o) dists.push_back(o); if (p) dists.push_back(p);
  ^~
../src/getfem/getfem_mesher.h:634:7: warning: this 'if' clause does not 
guard... [-Wmisleading-indentation]
   if (q) dists.push_back(q); if (r) dists.push_back(r);
   ^~
../src/getfem/getfem_mesher.h:634:34: note: ...this statement, but the latter 
is misleadingly indented as if it were guarded by the 'if'
   if (q) dists.push_back(q); if (r) dists.push_back(r);
  ^~
../src/getfem/getfem_mesher.h:635:7: warning: this 'if' clause does not 
guard... [-Wmisleading-indentation]
   if (s) dists.push_back(s); if (t) dists.push_back(t);
   ^~
../src/getfem/getfem_mesher.h:635:34: note: ...this statement, but the latter 
is misleadingly indented as if it were guarded by the 'if'
   if (s) dists.push_back(s); if (t) dists.push_back(t);
  ^~
test_mesh_generation.cc: In function 'int main(int, char**)':
test_mesh_generation.cc:144:23: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
   fixed.push_back(base_node(0,-z));
   ^~~
test_mesh_generation.cc:146:5: note: here
 case 2: dist = D2; break; /* union of 2 disks */
 ^~~~
make[3]: Leaving directory '/build/getfem++-DZRk9N/getfem++-5.1+dfsg1/tests'
Makefile:1553: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/build/getfem++-DZRk9N/getfem++-5.1+dfsg1/tests'
Makefile:543: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/build/getfem++-DZRk9N/getfem++-5.1+dfsg1'
dh_auto_test: make -j64 check VERBOSE=1 returned exit code 2
debian/rules:3: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
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#853413: gazebo: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:gazebo
Version: 7.3.1+dfsg-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/gazebo_7.3.1+dfsg-3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
[ 83%] Building CXX object 
gazebo/gui/CMakeFiles/gazebo_gui.dir/building/moc_WindowDoorInspectorDialog.cxx.o
cd /<>/gazebo-7.3.1+dfsg/obj-x86_64-linux-gnu/gazebo/gui && 
/usr/bin/c++   -DHAVE_OPENGL -DLIBBULLET_VERSION=2.83 
-DLIBBULLET_VERSION_GT_282 -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
-DQT_WEBKIT_LIB -DQT_XMLPATTERNS_LIB -DQT_XML_LIB -Dgazebo_gui_EXPORTS 
-I/<>/gazebo-7.3.1+dfsg 
-I/<>/gazebo-7.3.1+dfsg/obj-x86_64-linux-gnu 
-I/<>/gazebo-7.3.1+dfsg/deps -I/usr/include/x86_64-linux-gnu 
-I/usr/include/libusb-1.0 -isystem /usr/include/ignition/math2 -isystem 
/usr/include/OGRE/RTShaderSystem -isystem /usr/include/OGRE -isystem 
/usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Paging -isystem 
/usr/include/OGRE/Overlay -isystem /usr/include/sdformat-4.2 -isystem 
/usr/include/qt4 -isystem /usr/include/qt4/QtWebKit -isystem 
/usr/include/qt4/QtXmlPatterns -isystem /usr/include/qt4/QtGui -isystem 
/usr/include/qt4/QtXml -isystem /usr/include/qt4/QtCore  -g -O2 
-fdebug-prefix-map=/<>/gazebo-7.3.1+dfsg=. -fstack-protector-strong 
-Wformat -Werror=for
 mat-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wextra -Wno-long-long 
-Wno-unused-value -Wno-unused-value -Wno-unused-value -Wno-unused-value 
-Wfloat-equal -Wshadow -Winit-self -Wswitch-default -Wmissing-include-dirs 
-pedantic -fvisibility=hidden -fvisibility-inlines-hidden -std=c++11 
-DBUILDING_DLL_GZ_GUI -mfpmath=sse -msse -msse2 -msse3 -mssse3 -DSSE -fPIC   
-fPIC -o CMakeFiles/gazebo_gui.dir/building/moc_WindowDoorInspectorDialog.cxx.o 
-c 
/<>/gazebo-7.3.1+dfsg/obj-x86_64-linux-gnu/gazebo/gui/building/moc_WindowDoorInspectorDialog.cxx
[ 83%] Building CXX object 
gazebo/gui/CMakeFiles/gazebo_gui.dir/building/moc_WindowItem.cxx.o
cd /<>/gazebo-7.3.1+dfsg/obj-x86_64-linux-gnu/gazebo/gui && 
/usr/bin/c++   -DHAVE_OPENGL -DLIBBULLET_VERSION=2.83 
-DLIBBULLET_VERSION_GT_282 -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
-DQT_WEBKIT_LIB -DQT_XMLPATTERNS_LIB -DQT_XML_LIB -Dgazebo_gui_EXPORTS 
-I/<>/gazebo-7.3.1+dfsg 
-I/<>/gazebo-7.3.1+dfsg/obj-x86_64-linux-gnu 
-I/<>/gazebo-7.3.1+dfsg/deps -I/usr/include/x86_64-linux-gnu 
-I/usr/include/libusb-1.0 -isystem /usr/include/ignition/math2 -isystem 
/usr/include/OGRE/RTShaderSystem -isystem /usr/include/OGRE -isystem 
/usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Paging -isystem 
/usr/include/OGRE/Overlay -isystem /usr/include/sdformat-4.2 -isystem 
/usr/include/qt4 -isystem /usr/include/qt4/QtWebKit -isystem 
/usr/include/qt4/QtXmlPatterns -isystem /usr/include/qt4/QtGui -isystem 
/usr/include/qt4/QtXml -isystem /usr/include/qt4/QtCore  -g -O2 
-fdebug-prefix-map=/<>/gazebo-7.3.1+dfsg=. -fstack-protector-strong 
-Wformat -Werror=for
 mat-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wextra -Wno-long-long 
-Wno-unused-value -Wno-unused-value -Wno-unused-value -Wno-unused-value 
-Wfloat-equal -Wshadow -Winit-self -Wswitch-default -Wmissing-include-dirs 
-pedantic -fvisibility=hidden -fvisibility-inlines-hidden -std=c++11 
-DBUILDING_DLL_GZ_GUI -mfpmath=sse -msse -msse2 -msse3 -mssse3 -DSSE -fPIC   
-fPIC -o CMakeFiles/gazebo_gui.dir/building/moc_WindowItem.cxx.o -c 
/<>/gazebo-7.3.1+dfsg/obj-x86_64-linux-gnu/gazebo/gui/building/moc_WindowItem.cxx
[ 83%] Building CXX object 
gazebo/gui/CMakeFiles/gazebo_gui.dir/model/moc_CollisionConfig.cxx.o
cd /<>/gazebo-7.3.1+dfsg/obj-x86_64-linux-gnu/gazebo/gui && 
/usr/bin/c++   -DHAVE_OPENGL -DLIBBULLET_VERSION=2.83 
-DLIBBULLET_VERSION_GT_282 -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
-DQT_WEBKIT_LIB -DQT_XMLPATTERNS_LIB -DQT_XML_LIB -Dgazebo_gui_EXPORTS 
-I/<>/gazebo-7.3.1+dfsg 
-I/<>/gazebo-7.3.1+dfsg/obj-x86_64-linux-gnu 
-I/<>/gazebo-7.3.1+dfsg/deps -I/usr/include/x86_64-linux-gnu 

Bug#853392: esys-particle: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:esys-particle
Version: 2.3.4+dfsg1-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/esys-particle_2.3.4+dfsg1-4_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include 
-I../Foundation -I../Parallel -I../Fields -I../Parser -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 
-fdebug-prefix-map=/<>/esys-particle-2.3.4+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
HertzianViscoElasticInteraction.cpp -o HertzianViscoElasticInteraction.o 
>/dev/null 2>&1
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include 
-I../Foundation -I../Parallel -I../Fields -I../Parser -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 
-fdebug-prefix-map=/<>/esys-particle-2.3.4+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
BondedInteractionCpData.cpp -o BondedInteractionCpData.o >/dev/null 2>&1
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include 
-I../Foundation -I../Parallel -I../Fields -I../Parser -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 
-fdebug-prefix-map=/<>/esys-particle-2.3.4+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
RotThermPairInteraction.cpp -o RotThermPairInteraction.o >/dev/null 2>&1
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include 
-I../Foundation -I../Parallel -I../Fields -I../Parser -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 
-fdebug-prefix-map=/<>/esys-particle-2.3.4+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c Interaction.cpp -o 
Interaction.o >/dev/null 2>&1
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include 
-I../Foundation -I../Parallel -I../Fields -I../Parser -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 
-fdebug-prefix-map=/<>/esys-particle-2.3.4+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
RotElasticInteraction.cpp -o RotElasticInteraction.o >/dev/null 2>&1
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include 
-I../Foundation -I../Parallel -I../Fields -I../Parser -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 
-fdebug-prefix-map=/<>/esys-particle-2.3.4+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
ElasticInteraction.cpp -o ElasticInteraction.o >/dev/null 2>&1
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include 
-I../Foundation -I../Parallel -I../Fields -I../Parser -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 
-fdebug-prefix-map=/<>/esys-particle-2.3.4+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
RotPairInteraction.cpp -o RotPairInteraction.o >/dev/null 2>&1
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include 
-I../Foundation -I../Parallel -I../Fields -I../Parser -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 
-fdebug-prefix-map=/<>/esys-particle-2.3.4+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
RotThermElasticInteraction.cpp -o RotThermElasticInteraction.o >/dev/null 2>&1
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include 
-I../Foundation -I../Parallel -I../Fields -I../Parser -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 
-fdebug-prefix-map=/<>/esys-particle-2.3.4+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
ShortBondedInteraction.cpp -o ShortBondedInteraction.o >/dev/null 2>&1
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include 
-I../Foundation -I../Parallel -I../Fields -I../Parser -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -g -O2 
-fdebug-prefix-map=/<>/esys-particle-2.3.4+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
BondedInteraction.cpp -o BondedInteraction.o >/dev/null 2>&1
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include 
-I../Foundation -I../Parallel -I../Fields 

Bug#853399: fflas-ffpack: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:fflas-ffpack
Version: 2.2.2-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/fflas-ffpack_2.2.2-4_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
make[3]: Leaving directory '/<>/fflas-ffpack/interfaces'
Making check in checkers
make[3]: Entering directory '/<>/fflas-ffpack/checkers'
make[3]: Nothing to be done for 'check'.
make[3]: Leaving directory '/<>/fflas-ffpack/checkers'
make[3]: Entering directory '/<>/fflas-ffpack'
make[3]: Nothing to be done for 'check-am'.
make[3]: Leaving directory '/<>/fflas-ffpack'
make[2]: Leaving directory '/<>/fflas-ffpack'
Making check in tests
make[2]: Entering directory '/<>/tests'
Making check in data
make[3]: Entering directory '/<>/tests/data'
make[4]: Entering directory '/<>/tests/data'
make[4]: Nothing to be done for 'check-am'.
make[4]: Leaving directory '/<>/tests/data'
make[3]: Leaving directory '/<>/tests/data'
make[3]: Entering directory '/<>/tests'
make  check-TESTS
make[4]: Entering directory '/<>/tests'
make[5]: Entering directory '/<>/tests'
g++ -DHAVE_CONFIG_H -I. -I..  -I.. -g -I../fflas-ffpack/ 
-I../fflas-ffpack/utils/ -I../fflas-ffpack/fflas/ -I../fflas-ffpack/ffpack 
-I../fflas-ffpack/field -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -Wall -DNDEBUG 
-UFFLASFFPACK_DEBUG  -std=gnu++11 -D__FFLASFFPACK_HAVE_CBLAS  -fopenmp  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-strict-aliasing   -fabi-version=6 -c -o test-lu.o 
test-lu.C
In file included from test-lu.C:62:0:
test-utils.h: In function 'Field* FFPACK::chooseField(Givaro::Integer, 
uint64_t)':
test-utils.h:80:24: error: 'bind' is not a member of 'std'
auto bitrand = 
std::bind(std::uniform_int_distribution(2,maxV.bitsize()-1),
^~~~
test-utils.h:80:24: note: suggested alternative: 'find'
auto bitrand = 
std::bind(std::uniform_int_distribution(2,maxV.bitsize()-1),
^~~~
find
Makefile:1150: recipe for target 'test-lu.o' failed
make[5]: *** [test-lu.o] Error 1
make[5]: Leaving directory '/<>/tests'
Makefile:1393: recipe for target 'check-TESTS' failed
make[4]: *** [check-TESTS] Error 2
make[4]: Leaving directory '/<>/tests'
Makefile:1624: recipe for target 'check-am' failed
make[3]: *** [check-am] Error 2
make[3]: Leaving directory '/<>/tests'
Makefile:1180: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/<>/tests'
Makefile:572: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
debian/rules:19: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
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#853385: einspline: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:einspline
Version: 0.9.2-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/einspline_0.9.2-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
./src/time_multi.c:1885: undefined reference to `eval_UBspline_3d_c_vgh'
time_multi.o: In function `time_3d_real_float_all':
./src/time_multi.c:1973: undefined reference to `eval_UBspline_3d_s'
./src/time_multi.c:2006: undefined reference to `eval_UBspline_3d_s_vgh'
time_multi.o: In function `time_3d_real_double_all':
./src/time_multi.c:2102: undefined reference to `eval_UBspline_3d_d'
./src/time_multi.c:2135: undefined reference to `eval_UBspline_3d_d_vgh'
time_multi.o: In function `time_3d_complex_double_all':
./src/time_multi.c:2228: undefined reference to `eval_UBspline_3d_z'
./src/time_multi.c:2282: undefined reference to `eval_UBspline_3d_z_vgh'
time_multi.o: In function `test_complex_double_vgh':
./src/time_multi.c:2357: undefined reference to `eval_UBspline_3d_z_vgh'
./src/time_multi.c:2408: undefined reference to `eval_UBspline_3d_z_vgh'
time_multi.o: In function `test_double':
./src/time_multi.c:2479: undefined reference to `eval_UBspline_3d_d'
./src/time_multi.c:2511: undefined reference to `eval_UBspline_3d_d'
time_multi.o: In function `test_double_vgh':
./src/time_multi.c:2583: undefined reference to `eval_UBspline_3d_d_vgh'
./src/time_multi.c:2638: undefined reference to `eval_UBspline_3d_d_vgh'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_z_vg'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_s_vgh'
./.libs/libeinspline.so: undefined reference to `eval_UBspline_3d_z_vgl'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_d'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_z_vgl'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_z'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_c_vgl'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_s_vg'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_c_vg'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_d_vgl'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_s_vgl'
./.libs/libeinspline.so: undefined reference to `eval_UBspline_3d_z_vg'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_z_vgh'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_d_vg'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_c'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_s'
./.libs/libeinspline.so: undefined reference to `eval_NUBspline_3d_c_vgh'
collect2: error: ld returned 1 exit status
Makefile:864: recipe for target 'time_multi' failed
make[3]: *** [time_multi] Error 1
make[3]: Leaving directory '/<>/src'
Makefile:678: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>/src'
Makefile:473: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j64 returned exit code 2
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
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#853404: form: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:form
Version: 4.1-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/form_4.1-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]

/* confdefs.h */
#define PACKAGE_NAME "FORM"
#define PACKAGE_TARNAME "form"
#define PACKAGE_VERSION "4.1"
#define PACKAGE_STRING "FORM 4.1"
#define PACKAGE_BUGREPORT "f...@nikhef.nl"
#define PACKAGE_URL ""
#define PACKAGE "form"
#define VERSION "4.1"
#define MAJORVERSION 4
#define MINORVERSION 1
#define HAVE_PRODUCTIONDATE_H /**/
#define STDC_HEADERS 1
#define TIME_WITH_SYS_TIME 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_FCNTL_H 1
#define HAVE_LIMITS_H 1
#define HAVE_SYS_FILE_H 1
#define LINUX /**/
#define HAVE_UNISTD_H 1
#define UNIX /**/
#define SIZEOF_CHAR 1
#define SIZEOF_SHORT 2
#define SIZEOF_INT 4
#define SIZEOF_LONG 8
#define SIZEOF_LONG_LONG 8
#define SIZEOF_VOID_P 8
#define SIZEOF_OFF_T 8
#define LP64 /**/
#ifdef WITHPTHREADS
#define WITHPOSIXCLOCK /**/
#endif

configure: exit 1
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man 
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu 
--libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-parform returned exit code 1
debian/rules:13: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
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#853370: deal.ii: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:deal.ii
Version: 8.4.2-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/deal.ii_8.4.2-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
   ^~~
/<>/include/deal.II/base/table_indices.h:178:5: note: here
 case 6: // fallthrough
 ^~~~
/<>/include/deal.II/base/table_indices.h:179:7: warning: this 
statement may fall through [-Wimplicit-fallthrough=]
   indices[5 % N] = index5;
   ^~~
/<>/include/deal.II/base/table_indices.h:180:5: note: here
 case 5: // fallthrough
 ^~~~
/<>/include/deal.II/base/table_indices.h:181:7: warning: this 
statement may fall through [-Wimplicit-fallthrough=]
   indices[4 % N] = index4;
   ^~~
/<>/include/deal.II/base/table_indices.h:182:5: note: here
 case 4: // fallthrough
 ^~~~
/<>/include/deal.II/base/table_indices.h:183:7: warning: this 
statement may fall through [-Wimplicit-fallthrough=]
   indices[3 % N] = index3;
   ^~~
/<>/include/deal.II/base/table_indices.h:184:5: note: here
 case 3: // fallthrough
 ^~~~
/<>/include/deal.II/base/table_indices.h:185:7: warning: this 
statement may fall through [-Wimplicit-fallthrough=]
   indices[2 % N] = index2;
   ^~~
/<>/include/deal.II/base/table_indices.h:186:5: note: here
 case 2: // fallthrough
 ^~~~
/<>/include/deal.II/base/table_indices.h:187:7: warning: this 
statement may fall through [-Wimplicit-fallthrough=]
   indices[1 % N] = index1;
   ^~~
/<>/include/deal.II/base/table_indices.h:188:5: note: here
 case 1: // fallthrough
 ^~~~
source/numerics/CMakeFiles/obj_numerics.debug.dir/build.make:65: recipe for 
target 'source/numerics/CMakeFiles/obj_numerics.debug.dir/data_out.cc.o' failed
make[3]: *** [source/numerics/CMakeFiles/obj_numerics.debug.dir/data_out.cc.o] 
Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:2638: recipe for target 
'source/numerics/CMakeFiles/obj_numerics.debug.dir/all' failed
make[2]: *** [source/numerics/CMakeFiles/obj_numerics.debug.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 36%] Built target obj_opencascade.debug
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
Makefile:130: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_build: make -j2 returned exit code 2
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
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#853380: dx: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:dx
Version: 1:4.4.4-9
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/dx_4.4.4-9_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C:7107:1: warning: ISO C++ forbids converting a string constant to 
'String {aka char*}' [-Wwrite-strings]
EditorWindow.C: In member function 'boolean EditorWindow::javifyNetwork()':
EditorWindow.C:7170:17: warning: ISO C++ forbids converting a string constant 
to 'char*' [-Wwrite-strings]
  char* macros = "/java/server/dxmacros";
 ^~~
EditorWindow.C: In member function 'void EditorWindow::setUndoActivation()':
EditorWindow.C:7545:62: warning: ISO C++ forbids converting a string constant 
to 'XmStringCharSet {aka char*}' [-Wwrite-strings]
 XmString xmstr = XmStringCreateLtoR (button_label, "bold");
  ^
Makefile:1101: recipe for target 'EditorWindow.o' failed
make[6]: *** [EditorWindow.o] Error 1
make[6]: Leaving directory '/<>/src/uipp/dxuilib'
Makefile:879: recipe for target 'all' failed
make[5]: *** [all] Error 2
make[5]: Leaving directory '/<>/src/uipp/dxuilib'
Makefile:406: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/<>/src/uipp'
Makefile:402: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>/src'
Makefile:433: recipe for target 'all-recursive' failed
make[2]: 

Bug#853350: coinor-cbc: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:coinor-cbc
Version: 2.8.12-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/coinor-cbc_2.8.12-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
CbcSolver.cpp:1863:28: warning: macro "__DATE__" might prevent reproducible 
builds [-Wdate-time]
   "Build Date: %s \n", __DATE__);
^~~~
CbcSolver.cpp:8457:52: warning: macro "__DATE__" might prevent reproducible 
builds [-Wdate-time]
   << ", build " << __DATE__ << std::endl;
^~~~
 g++ -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/include/coin -I/usr/include/coin 
-DCOIN_NO_CLP_MESSAGE -DUSE_CBCCONFIG -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DCBC_BUILD -c CbcSolver.cpp -o CbcSolver.o >/dev/null 
2>&1
/bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I`echo 
.` -I../src  -I/usr/include/coin -I/usr/include/coin-DCOIN_NO_CLP_MESSAGE 
-DUSE_CBCCONFIG -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security   -DCBC_BUILD -c -o CbcSolverHeuristics.lo 
CbcSolverHeuristics.cpp
 g++ -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/include/coin -I/usr/include/coin 
-DCOIN_NO_CLP_MESSAGE -DUSE_CBCCONFIG -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DCBC_BUILD -c CbcSolverHeuristics.cpp  -fPIC -DPIC -o 
.libs/CbcSolverHeuristics.o
 g++ -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/include/coin -I/usr/include/coin 
-DCOIN_NO_CLP_MESSAGE -DUSE_CBCCONFIG -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DCBC_BUILD -c CbcSolverHeuristics.cpp -o 
CbcSolverHeuristics.o >/dev/null 2>&1
/bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I`echo 
.` -I../src  -I/usr/include/coin -I/usr/include/coin-DCOIN_NO_CLP_MESSAGE 
-DUSE_CBCCONFIG -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security   -DCBC_BUILD -c -o CbcSolverAnalyze.lo 
CbcSolverAnalyze.cpp
 g++ -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/include/coin -I/usr/include/coin 
-DCOIN_NO_CLP_MESSAGE -DUSE_CBCCONFIG -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DCBC_BUILD -c CbcSolverAnalyze.cpp  -fPIC -DPIC -o 
.libs/CbcSolverAnalyze.o
 g++ -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/include/coin -I/usr/include/coin 
-DCOIN_NO_CLP_MESSAGE -DUSE_CBCCONFIG -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DCBC_BUILD -c CbcSolverAnalyze.cpp -o 
CbcSolverAnalyze.o >/dev/null 2>&1
/bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I`echo 
.` -I../src  -I/usr/include/coin -I/usr/include/coin-DCOIN_NO_CLP_MESSAGE 
-DUSE_CBCCONFIG -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security   -DCBC_BUILD -c -o CbcMipStartIO.lo CbcMipStartIO.cpp
 g++ -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/include/coin -I/usr/include/coin 
-DCOIN_NO_CLP_MESSAGE -DUSE_CBCCONFIG -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DCBC_BUILD -c CbcMipStartIO.cpp  -fPIC -DPIC -o 
.libs/CbcMipStartIO.o
 g++ -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/include/coin -I/usr/include/coin 
-DCOIN_NO_CLP_MESSAGE -DUSE_CBCCONFIG -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DCBC_BUILD -c CbcMipStartIO.cpp -o CbcMipStartIO.o 
>/dev/null 2>&1

Bug#853345: cernlib: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:cernlib
Version: 20061220+dfsg3-4.3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/cernlib_20061220+dfsg3-4.3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
gfortran cgplg64.F
gfortran clogam64.F
gfortran clogok.F
gfortran cpolyz64.F
gfortran cpolyzd.F
gfortran cpsipg.F
gfortran crit.F
gfortran csqrtk.F
gfortran cwerf64.F
E: Build killed with signal TERM after 150 minutes of inactivity

Build finished at 2017-01-27T15:55:02Z

Finished



+--+
| Cleanup  |
+--+

Purging /<>
Not cleaning session: cloned chroot in use
E: Build failure (dpkg-buildpackage died)

+--+
| Summary  |
+--+

Build Architecture: amd64
Build-Space: 223824
Build-Time: 9342
Distribution: unstable
Fail-Stage: build
Host Architecture: amd64
Install-Time: 16
Job: cernlib_20061220+dfsg3-4.3
Machine Architecture: amd64
Package: cernlib
Package-Time: 9392
Source-Version: 20061220+dfsg3-4.3
Space: 223824
Status: attempted
Version: 20061220+dfsg3-4.3

Finished at 2017-01-27T15:55:02Z
Build needed 02:36:32, 223824k disk space
E: Build failure (dpkg-buildpackage died)
DC-Status: Failed 9393.19890499s
DC-Time-Estimation: 9393.19890499 versus expected 578 (r/m: 15.251209178183391 
; m: 578.0)

-- 
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#853333: blitz++: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:blitz++
Version: 1:0.10+ds-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/blitz++_0.10+ds-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
   ^
../../blitz/array/newet-macros.h:125:1: note: in definition of macro 
'BZ_DECLARE_ARRAY_ET_BINARY_SCALAR'
 name(const BZ_BLITZ_SCOPE(ETBase)& d1, const sca d2)\
 ^~~~
../../blitz/array/ops.h:127:1: note: in expansion of macro 
'BZ_DECLARE_ARRAY_ET_SCALAR_OPS'
 BZ_DECLARE_ARRAY_ET_SCALAR_OPS(complex)
 ^~
../../blitz/array/ops.h:93:35: note:   substitution of deduced template 
arguments resulted in errors seen above
 BZ_DECLARE_ARRAY_ET_BINARY_SCALAR(operator-,  Subtract, sca)   \
   ^
../../blitz/array/newet-macros.h:125:1: note: in definition of macro 
'BZ_DECLARE_ARRAY_ET_BINARY_SCALAR'
 name(const BZ_BLITZ_SCOPE(ETBase)& d1, const sca d2)\
 ^~~~
../../blitz/array/ops.h:127:1: note: in expansion of macro 
'BZ_DECLARE_ARRAY_ET_SCALAR_OPS'
 BZ_DECLARE_ARRAY_ET_SCALAR_OPS(complex)
 ^~
In file included from ../../blitz/globeval.cc:34:0,
 from ../../blitz/array/ops.cc:38,
 from ../../blitz/array.cc:13,
 from ../../blitz/array-impl.h:2559,
 from ../../blitz/array.h:37,
 from ../../src/globals.cpp:12:
../../blitz/tvevaluate.h: In instantiation of 'static void 
blitz::_tv_evaluator::evaluate_unaligned(T_numtype*, const 
T_expr&, T_update) [with T_numtype = int; T_expr = 
blitz::_bz_ArrayExpr >; T_update = 
blitz::_bz_update; bool unroll = false; int N_length = 2]':
../../blitz/globeval.cc:303:7:   required from 'static void 
blitz::chunked_updater::unaligned_update(T_numtype*, T_expr, blitz::diffType) [with T_numtype = 
int; T_expr = blitz::_bz_ArrayExpr >; T_update = 
blitz::_bz_update; int N = 2; blitz::diffType = long int]'
../../blitz/globeval.cc:342:41:   recursively required from 'static void 
blitz::_bz_meta_binaryAssign::assign(T_data*, T_expr, blitz::diffType, 
blitz::diffType, T_update) [with T_data = int; T_expr = 
blitz::_bz_ArrayExpr >; T_update = 
blitz::_bz_update; int I = 6; blitz::diffType = long int]'
../../blitz/globeval.cc:342:41:   required from 'static void 
blitz::_bz_meta_binaryAssign::assign(T_data*, T_expr, blitz::diffType, 
blitz::diffType, T_update) [with T_data = int; T_expr = 
blitz::_bz_ArrayExpr >; T_update = 
blitz::_bz_update; int I = 7; blitz::diffType = long int]'
../../blitz/globeval.cc:404:13:   required from 'void 
blitz::_bz_evaluateWithUnitStride(T_dest&, typename T_dest::T_iterator&, 
T_expr, blitz::diffType, T_update) [with T_dest = blitz::TinyVector; 
T_expr = blitz::_bz_ArrayExpr >; T_update = 
blitz::_bz_update; typename T_dest::T_iterator = 
blitz::FastTV2Iterator; blitz::diffType = long int]'
../../blitz/globeval.cc:591:31:   required from 'static void 
blitz::_bz_evaluator<1>::evaluateWithStackTraversal(T_dest&, T_expr, T_update) 
[with T_dest = blitz::TinyVector; T_expr = 
blitz::_bz_ArrayExpr >; T_update = 
blitz::_bz_update]'
../../blitz/globeval.cc:279:58:   required from 'void 
blitz::_bz_evaluate(T_dest&, T_expr, T_update) [with T_dest = 
blitz::TinyVector; T_expr = 
blitz::_bz_ArrayExpr >; T_update = 
blitz::_bz_update]'
../../blitz/tvevaluate.h:135:17:   required from 'static void 
blitz::_tv_evaluator::select_evaluation(blitz::TinyVector&, const T_expr&, T_update) 

Bug#853338: bossa: ftbfs with GCC-7

2017-01-31 Thread Matthias Klose
Package: src:bossa
Version: 1.3~20120408-5
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/bossa_1.3~20120408-5_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
In file included from /usr/include/c++/7/memory:80:0,
 from src/Samba.h:25,
 from src/Command.h:25,
 from src/Shell.cpp:23:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
CPP src/Command.cpp
g++ -Wall -MT obj/Command.o -MD -MP -MF obj/Command.d -DVERSION=\"1.3a\" -g -O2 
`dpkg-buildflags --get CXXFLAGS` `dpkg-buildflags --get CPPFLAGS` -Isrc/arm-dis 
-c -o obj/Command.o src/Command.cpp
In file included from src/Samba.h:27:0,
 from src/Command.h:25,
 from src/Command.cpp:29:
src/SerialPort.h:64:18: warning: 'template class std::auto_ptr' is 
deprecated [-Wdeprecated-declarations]
 typedef std::auto_ptr Ptr;
  ^~~~
In file included from /usr/include/c++/7/memory:80:0,
 from src/Samba.h:25,
 from src/Command.h:25,
 from src/Command.cpp:29:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
In file included from src/FlashFactory.h:25:0,
 from src/Command.h:27,
 from src/Command.cpp:29:
src/Flash.h:107:18: warning: 'template class std::auto_ptr' is 
deprecated [-Wdeprecated-declarations]
 typedef std::auto_ptr Ptr;
  ^~~~
In file included from /usr/include/c++/7/memory:80:0,
 from src/Samba.h:25,
 from src/Command.h:25,
 from src/Command.cpp:29:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
src/Command.cpp: In member function 'virtual void CommandMwb::invoke(char**, 
int)':
src/Command.cpp:710:26: error: ISO C++ forbids comparison between pointer and 
integer [-fpermissive]
 if (input == '\0' ||
  ^~~~
src/Command.cpp: In member function 'virtual void CommandMww::invoke(char**, 
int)':
src/Command.cpp:813:26: error: ISO C++ forbids comparison between pointer and 
integer [-fpermissive]
 if (input == '\0' ||
  ^~~~
Makefile:243: recipe for target 'obj/Command.o' failed
make[1]: *** [obj/Command.o] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:13: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
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#852011: petsc (libpetsc3.7.4-dev) depends on libgfortran-5-dev

2017-01-20 Thread Matthias Klose
Package: src:petsc
Version: 3.7.5+dfsg1-2
Severity: serious
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-5, gcc-5-legacy

petsc (libpetsc3.7.4-dev) depends on libgfortran-5-dev

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-6/g++-6.

Please keep this report open until the package uses the default
compiler version (or gcc-6) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.

The severity of this report is likely to be raised before the release,
so that the gcc-5 package can be removed for the release.

-- 
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#852007: flint: non-standard gcc/g++ used for build (gcc-5)

2017-01-20 Thread Matthias Klose
Package: src:flint
Version: 2.5.2-14
Severity: serious
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-5, gcc-5-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-6/g++-6.

Please keep this report open until the package uses the default
compiler version (or gcc-6) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.

The severity of this report is likely to be raised before the release,
so that the gcc-5 package can be removed for the release.

-- 
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#850150: freemat ftbfs with LLVM 3.9

2017-01-04 Thread Matthias Klose
Package: src:freemat
Version:
Severity: important
Tags: sid stretch

[100%] Linking CXX executable FreeMat
cd /home/packages/tmp/freemat-4.2+dfsg1/debian/build/src && /usr/bin/cmake -E
cmake_link_script CMakeFiles/FreeMat.dir/link.txt --verbose=1
/usr/bin/x86_64-linux-gnu-g++   -g -O2
-fdebug-prefix-map=/home/packages/tmp/freemat-4.2+dfsg1=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -
D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  -Wl,-Bsymbolic-functions -Wl,-z,relro
CMakeFiles/FreeMat.dir/application.moc.cpp.o
CMakeFiles/FreeMat.dir/application.cpp.o
CMakeFiles/FreeMat.dir/FuncMode.moc.cpp.o
CMakeFiles/FreeMat.dir/ScriptMode.moc.cpp.o
CMakeFiles/FreeMat.dir/FuncMode.cpp.o CMakeFiles/FreeMat.dir/ScriptMode.cpp.o
CMakeFiles/FreeMat.dir/FuncTerminal.cpp.o
CMakeFiles/FreeMat.dir/MainApp.moc.cpp.o CMakeFiles/FreeMat.dir/MainApp.cpp.o
CMakeFiles/FreeMat.dir/main.cpp.o CMakeFiles/FreeMat.dir/DumbTerminal.moc.cpp.o
CMakeFiles/FreeMat.dir/DumbTerminal.cpp.o
CMakeFiles/FreeMat.dir/Terminal.moc.cpp.o CMakeFiles/FreeMat.dir/Loader.cpp.o
CMakeFiles/FreeMat.dir/Terminal.cpp.o CMakeFiles/FreeMat.dir/qrc_FreeMat.cxx.o
CMakeFiles/FreeMat.dir/dummy.f.o  -o FreeMat  -L/usr/lib/llvm-3.9/lib -rdynamic
../libs/libCore/libCore.a ../libs/libFN/libFN.a
../libs/libGraphics/libGraphics.a ../libs/libFreeMat/libFreeMatlib.a
../libs/libXP/libXP.a ../libs/libMex/libMex.a ../libs/libMatC/libMatC.a
../libs/libFN/levmar-2.3/liblevmar.a ../libs/libMath/libLAPACK_C/liblapack_c.a
../libs/libMath/libDynBlas/libdynblas.a ../libs/libMath/libBLAS_C/libblasref.a
-lQtCore -lQtGui -lQtNetwork -lQtOpenGL -lQtXml -lQtSvg -lGLU -lGL -lncurses
-lpcre -lfftw3 -lfftw3f -lz -larpack ../libs/libMath/libLAPACK_C/liblapack_c.a
-lffi -lportaudio -lboost_math_c99 -lclang -lclangAnalysis
-lclangApplyReplacements -lclangARCMigrate -lclangAST -lclangASTMatchers
-lclangBasic -lclangCodeGen -lclangDriver -lclangDynamicASTMatchers -lclangEdit
-lclangFormat -lclangFrontend -lclangFrontendTool -lclangIndex -lclangLex
-lclangParse -lclangQuery -lclangRename -lclangRewrite -lclangRewriteFrontend
-lclangSema -lclangSerialization -lclangStaticAnalyzerCheckers
-lclangStaticAnalyzerCore -lclangStaticAnalyzerFrontend -lclangTidy
-lclangTidyGoogleModule -lclangTidyLLVMModule -lclangTidyMiscModule
-lclangTidyReadabilityModule -lclangTidyUtils -lclang
/usr/lib/llvm-3.9/lib/libLLVMExecutionEngine.a
/usr/lib/llvm-3.9/lib/libLLVMOption.a /usr/lib/llvm-3.9/lib/libLLVMIRReader.a
/usr/lib/llvm-3.9/lib/libLLVMLTO.a /usr/lib/llvm-3.9/lib/libLLVMInterpreter.a
/usr/lib/llvm-3.9/lib/libLLVMX86CodeGen.a /usr/lib/llvm-3.9/lib/libLLVMX86Desc.a
/usr/lib/llvm-3.9/lib/libLLVMX86Info.a /usr/lib/llvm-3.9/lib/libLLVMAsmParser.a
/usr/lib/llvm-3.9/lib/libLLVMBitReader.a
/usr/lib/llvm-3.9/lib/libLLVMBitWriter.a /usr/lib/llvm-3.9/lib/libLLVMCodeGen.a
/usr/lib/llvm-3.9/lib/libLLVMipo.a /usr/lib/llvm-3.9/lib/libLLVMLinker.a
/usr/lib/llvm-3.9/lib/libLLVMSelectionDAG.a
/usr/lib/llvm-3.9/lib/libLLVMInstrumentation.a -lclangAnalysis
-lclangApplyReplacements -lclangARCMigrate -lclangAST -lclangASTMatchers
-lclangBasic -lclangCodeGen -lclangDriver -lclangDynamicASTMatchers -lclangEdit
-lclangFormat -lclangFrontend -lclangFrontendTool -lclangIndex -lclangLex
-lclangParse -lclangQuery -lclangRename -lclangRewrite -lclangRewriteFrontend
-lclangSema -lclangSerialization -lclangStaticAnalyzerCheckers
-lclangStaticAnalyzerCore -lclangStaticAnalyzerFrontend -lclangTidy
-lclangTidyGoogleModule -lclangTidyLLVMModule -lclangTidyMiscModule
-lclangTidyReadabilityModule -lclangTidyUtils
/usr/lib/llvm-3.9/lib/libLLVMIRReader.a /usr/lib/llvm-3.9/lib/libLLVMAsmParser.a
/usr/lib/llvm-3.9/lib/libLLVMVectorize.a
/usr/lib/llvm-3.9/lib/libLLVMObjCARCOpts.a
/usr/lib/llvm-3.9/lib/libLLVMExecutionEngine.a
/usr/lib/llvm-3.9/lib/libLLVMRuntimeDyld.a -lffi
/usr/lib/llvm-3.9/lib/libLLVMObject.a
/usr/lib/llvm-3.9/lib/libLLVMMCDisassembler.a
/usr/lib/llvm-3.9/lib/libLLVMAsmPrinter.a /usr/lib/llvm-3.9/lib/libLLVMCodeGen.a
/usr/lib/llvm-3.9/lib/libLLVMBitReader.a
/usr/lib/llvm-3.9/lib/libLLVMBitWriter.a
/usr/lib/llvm-3.9/lib/libLLVMInstrumentation.a
/usr/lib/llvm-3.9/lib/libLLVMScalarOpts.a
/usr/lib/llvm-3.9/lib/libLLVMInstCombine.a /usr/lib/llvm-3.9/lib/libLLVMTarget.a
/usr/lib/llvm-3.9/lib/libLLVMTransformUtils.a
/usr/lib/llvm-3.9/lib/libLLVMAnalysis.a
/usr/lib/llvm-3.9/lib/libLLVMProfileData.a
/usr/lib/llvm-3.9/lib/libLLVMMCParser.a
/usr/lib/llvm-3.9/lib/libLLVMDebugInfoCodeView.a
/usr/lib/llvm-3.9/lib/libLLVMX86AsmPrinter.a /usr/lib/llvm-3.9/lib/libLLVMMC.a
/usr/lib/llvm-3.9/lib/libLLVMX86Utils.a /usr/lib/llvm-3.9/lib/libLLVMCore.a
/usr/lib/llvm-3.9/lib/libLLVMSupport.a -lrt -ldl -ltinfo -lpthread -lz -lm
-lgfortran -lquadmath
/usr/lib/llvm-3.9/lib/libclangCodeGen.a(CoverageMappingGen.cpp.o): In function
`(anonymous
namespace)::CounterCoverageMappingBuilder::addCounters(llvm::coverage::Counter,
llvm::coverage::Counter, llvm::coverage::Counter)':

Bug#847110: please disable the "pretty" build, not showing compiler invocations

2016-12-05 Thread Matthias Klose
Package: src:yosys
Version: 0.7-2

Please call the build step with PRETTY=0, showing the compiler args by default.
You should that that in the build logs warnings as well.

-- 
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#844090: package fails to build on all 32bit architectures

2016-11-12 Thread Matthias Klose
Package: src:libgap-sage
Version: 4.8.3+g69a66f0+dsx-1
Severity: important
Tags: sid stretch

the package fails to build on all 32bit architectures, symbols files need an 
update.

-- 
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#835953: yosys: non-standard gcc/g++ used for build (gcc-5)

2016-08-29 Thread Matthias Klose
Package: yosys
Version: 0.6-6
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-5, gcc-5-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-6/g++-6.

Please keep this report open until the package uses the default
compiler version (or gcc-6) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.

The severity of this report is likely to be raised before the release,
so that the gcc-5 package can be removed for the release.

-- 
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#835292: pcl 1.8 fails to build on armel and armhf (OpenGLES?)

2016-08-24 Thread Matthias Klose
Package: src:pcl
Version: 1.8.0+dfsg1-2
Severity: serious
Tags: sid stretch

pcl 1.8 fails to build on armel and armhf (OpenGLES?)

cd /«BUILDDIR»/pcl-1.8.0+dfsg1/build/apps/in_hand_scanner && /usr/bin/c++
-DEIGEN_USE_NEW_STDVECTOR -DEIGEN_YES_I_KNOW_SPARSE_MODULE_IS_NOT_STABLE_YET
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB
-DQT_WIDGETS_LIB -Dqh_QHpointer
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)"
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)"
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)"
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)"
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)"
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)"
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)"
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
-DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)"
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)" -isystem
/usr/include/eigen3 -isystem /usr/include/ni -isystem /usr/include/openni2
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/recognition/include/pcl/recognition/3rdparty
-isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem
/usr/include/arm-linux-gnueabihf/qt5/QtCore -isystem
/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -isystem
/usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem
/usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem
/usr/include/arm-linux-gnueabihf/qt5/QtConcurrent -isystem
/usr/include/arm-linux-gnueabihf/qt5/QtOpenGL -I/usr/include/vtk-6.3
-I/usr/include/freetype2
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent/include
-I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi
-I/usr/include/python2.7 -I/usr/include/arm-linux-gnueabihf
-I/usr/include/hdf5/openmpi -I/usr/include/libxml2 -I/usr/include/jsoncpp
-I/usr/include/tcl -I/«BUILDDIR»/pcl-1.8.0+dfsg1/build/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/common/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/geometry/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/io/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/filters/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/sample_consensus/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/segmentation/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/visualization/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/kdtree/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/features/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/surface/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/octree/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/registration/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/keypoints/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/tracking/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/search/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/recognition/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/ml/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/stereo/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/build/apps
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/apps/include
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/build/apps/in_hand_scanner
-I/«BUILDDIR»/pcl-1.8.0+dfsg1/apps/in_hand_scanner/include  -g -O2
-fdebug-prefix-map=/«BUILDDIR»/pcl-1.8.0+dfsg1=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time
-D_FORTIFY_SOURCE=2  -pthread -fopenmp -fPIC -o
CMakeFiles/pcl_offline_integration.dir/src/opengl_viewer.cpp.o -c
/«BUILDDIR»/pcl-1.8.0+dfsg1/apps/in_hand_scanner/src/opengl_viewer.cpp
In file included from /usr/include/GL/gl.h:2055:0,
 from
/«BUILDDIR»/pcl-1.8.0+dfsg1/apps/in_hand_scanner/src/opengl_viewer.cpp:52:
/usr/include/GL/glext.h:468:19: error: conflicting declaration 'typedef
std::ptrdiff_t GLsizeiptr'
 typedef ptrdiff_t GLsizeiptr;
   ^~
In file included from /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:95:0,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/qgl.h:39,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/QGLWidget:1,
 from
/«BUILDDIR»/pcl-1.8.0+dfsg1/apps/in_hand_scanner/include/pcl/apps/in_hand_scanner/opengl_viewer.h:46,
 from
/«BUILDDIR»/pcl-1.8.0+dfsg1/apps/in_hand_scanner/src/opengl_viewer.cpp:41:
/usr/include/GLES3/gl3.h:69:25: note: previous declaration as 'typedef
khronos_ssize_t GLsizeiptr'
 typedef khronos_ssize_t GLsizeiptr;
 ^~
In file included from /usr/include/GL/gl.h:2055:0,
 from
/«BUILDDIR»/pcl-1.8.0+dfsg1/apps/in_hand_scanner/src/opengl_viewer.cpp:52:
/usr/include/GL/glext.h:469:19: error: conflicting declaration 'typedef
std::ptrdiff_t GLintptr'
 typedef ptrdiff_t GLintptr;
   ^~~~
In file included from /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:95:0,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/qgl.h:39,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/QGLWidget:1,
 from

Bug#814596: please default to openmpi on x32

2016-02-13 Thread Matthias Klose

Package: src:mpi-defaults
Version: 1.2

please default to openmpi on x32. Please do it now, so that package maintainers 
can do the changes for s390x and x32 at once, instead of having to touch 
packages twice.


--
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#813691: make openmpi the default on s390x

2016-02-04 Thread Matthias Klose

Package: src:mpi-defaults
Version: 1.0.2+nmu2
Tags: patch

please make openmpi the default on s390x. while mpi itself is not used that much 
on s390x, it may be better to go with the implementation which is used for most 
architectures.


patch at
https://launchpad.net/ubuntu/+source/mpi-defaults/1.0.2+nmu2ubuntu1

--
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#813691: make openmpi the default on s390x

2016-02-04 Thread Matthias Klose

Control: tag -1 - moreinfo

On 04.02.2016 13:08, Ansgar Burchardt wrote:

Control: tag -1 moreinfo

On Thu, 2016-02-04 at 12:59 +0100, Matthias Klose wrote:

Package: src:mpi-defaults
Version: 1.0.2+nmu2
Tags: patch

please make openmpi the default on s390x. while mpi itself is not
used that much
on s390x, it may be better to go with the implementation which is
used for most
architectures.

patch at
https://launchpad.net/ubuntu/+source/mpi-defaults/1.0.2+nmu2ubuntu1


OpenMPI is currently not built on s390x: it is not listed in the source
packages Architecture: field.


now filed #813694 for openmpi.

--
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#803477: petsc: FTBFS against mpich

2016-01-26 Thread Matthias Klose

now rebuilt on s390x.

--
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#811257: make the configure steps a bit more debuggable

2016-01-17 Thread Matthias Klose

Package: src:petsc
Version: 3.6.2.dfsg1-3
Tags: patch

just show the configure.log for failed configure runs.
diff -Nru petsc-3.6.2.dfsg1/debian/rules petsc-3.6.2.dfsg1/debian/rules
--- petsc-3.6.2.dfsg1/debian/rules	2015-10-24 17:06:43.0 +
+++ petsc-3.6.2.dfsg1/debian/rules	2016-01-17 00:04:46.0 +
@@ -126,7 +126,8 @@
 
 
 override_dh_auto_configure:
-	dh_auto_configure -p$(PETSC_DEBUG_PACKAGE) --  \
+	@echo = $(PETSC_DEBUG_PACKAGE) =
+	if dh_auto_configure -p$(PETSC_DEBUG_PACKAGE) --  \
   --with-debugging=1  \
   --shared-library-extension=_real \
   --with-hypre=1 --with-hypre-dir=/usr --with-clanguage=C++ --with-c-support \
@@ -135,8 +136,14 @@
   PETSC_DIR=$(CURDIR) --PETSC_ARCH=$(PETSC_DEBUG_BUILD_DIR) \
 CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" \
 FCFLAGS="$(FCFLAGS)"  FFLAGS="$(FFLAGS)"  \
-CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" MAKEFLAGS="$(MAKEFLAGS)"
-	dh_auto_configure -p$(PETSC_VERSIONED_DEV_PACKAGE) --  \
+CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" MAKEFLAGS="$(MAKEFLAGS)"; then \
+	  : ; \
+	else \
+	  cat configure.log; \
+	  false; \
+	fi
+	@echo = $(PETSC_VERSIONED_DEV_PACKAGE) =
+	if dh_auto_configure -p$(PETSC_VERSIONED_DEV_PACKAGE) --  \
   --with-debugging=0  \
   --shared-library-extension=_real \
   --with-hypre=1 --with-hypre-dir=/usr --with-clanguage=C++ --with-c-support \
@@ -145,8 +152,14 @@
   PETSC_DIR=$(CURDIR) --PETSC_ARCH=$(PETSC_BUILD_DIR) \
 CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" \
 FCFLAGS="$(FCFLAGS)"  FFLAGS="$(FFLAGS)"  \
-CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" MAKEFLAGS="$(MAKEFLAGS)"
-	dh_auto_configure -p$(PETSC_COMPLEX_VERSIONED_DEV_PACKAGE) --  \
+CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" MAKEFLAGS="$(MAKEFLAGS)"; then \
+	  : ; \
+	else \
+	  cat configure.log; \
+	  false; \
+	fi
+	@echo = $(PETSC_COMPLEX_VERSIONED_DEV_PACKAGE) =
+	if dh_auto_configure -p$(PETSC_COMPLEX_VERSIONED_DEV_PACKAGE) --  \
   --with-debugging=0  \
   --with-scalar-type=complex --shared-library-extension=_complex \
   $(CONFIGURATION_OPTIONS)  \
@@ -154,8 +167,14 @@
   PETSC_DIR=$(CURDIR) --PETSC_ARCH=$(PETSC_COMPLEX_BUILD_DIR) \
 CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" \
 FCFLAGS="$(FCFLAGS)"  FFLAGS="$(FFLAGS)"  \
-CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" MAKEFLAGS="$(MAKEFLAGS)"
-	dh_auto_configure -p$(PETSC_COMPLEX_DEBUG_PACKAGE) --  \
+CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" MAKEFLAGS="$(MAKEFLAGS)"; then \
+	  : ; \
+	else \
+	  cat configure.log; \
+	  false; \
+	fi
+	@echo = $(PETSC_COMPLEX_DEBUG_PACKAGE) =
+	if dh_auto_configure -p$(PETSC_COMPLEX_DEBUG_PACKAGE) --  \
   --with-debugging=1  \
   --with-scalar-type=complex --shared-library-extension=_complex \
   $(CONFIGURATION_OPTIONS)  \
@@ -163,7 +182,12 @@
   PETSC_DIR=$(CURDIR) --PETSC_ARCH=$(PETSC_COMPLEX_DEBUG_BUILD_DIR) \
 CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" \
 FCFLAGS="$(FCFLAGS)"  FFLAGS="$(FFLAGS)"  \
-CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" MAKEFLAGS="$(MAKEFLAGS)"
+CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" MAKEFLAGS="$(MAKEFLAGS)"; then \
+	  : ; \
+	else \
+	  cat configure.log; \
+	  false; \
+	fi
 
 
 override_dh_auto_build:
-- 
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#805300: new upstream 2.7 fixing the build failures

2016-01-17 Thread Matthias Klose

Control: tags -1 + patch

fyi,
https://launchpad.net/ubuntu/+source/getdp/2.7.0-0ubuntu1
builds with the updated dependencies in unstable.

the packaging also links against python-dev.

--
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#811231: /usr/lib/mpich/lib doesn't exist, causing petsc fail to build on mpich archs

2016-01-16 Thread Matthias Klose

Package: src:mpich,src:petsc
Severity: serious
Tags: sid stretch patch

the petsc configury expects both /usr/lib//include and /usr/lib//lib, 
or else it fails. openmpi provides these, while mpich is missing this symlink.


with this patch, and the additional patch in #811229, petsc should build on 
mpich based archs.


I think this should be fixed in mpich, not in petsc.
diff -Nru mpich-3.2/debian/changelog mpich-3.2/debian/changelog
--- mpich-3.2/debian/changelog	2016-01-16 22:01:11.0 +0100
+++ mpich-3.2/debian/changelog	2016-01-17 00:01:49.0 +0100
@@ -1,3 +1,9 @@
+mpich (3.2-4ubuntu3) xenial; urgency=medium
+
+  * libmpich-dev: Install a /usr/lib/mpich/lib symlink.
+
+ -- Matthias Klose <d...@ubuntu.com>  Sat, 16 Jan 2016 23:49:34 +0100
+
 mpich (3.2-4ubuntu2) xenial; urgency=medium
 
   * Limit the GCC version check to the major version.
diff -Nru mpich-3.2/debian/rules mpich-3.2/debian/rules
--- mpich-3.2/debian/rules	2016-01-16 23:04:28.0 +0100
+++ mpich-3.2/debian/rules	2016-01-17 00:01:38.0 +0100
@@ -79,6 +79,11 @@
 		sed -i 's:$(CURDIR)/debian/tmp/::g' $$fn ;\
 	done
 
+override_dh_install:
+	dh_install
+	mkdir -p debian/libmpich-dev/usr/lib/mpich
+	ln -sf ../$(DEB_HOST_MULTIARCH) debian/libmpich-dev/usr/lib/mpich/lib
+
 override_dh_installchangelogs:
 	dh_installchangelogs README
 
-- 
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#811191: [regression] lapack 3.6.0 fails the testsuite

2016-01-16 Thread Matthias Klose

Package: src:lapack
Version: 3.6.0-2
Severity: important
Tags: sid stretch

Regressed compared to 3.5.0.

According to
https://ci.debian.net/packages/l/lapack/unstable/amd64/

lapack fails the lapack-testsuite, but is very terse about what exactly failed:

adt-run [11:49:05]: test lapack-testsuite: [---
Total errors: 2
adt-run [11:50:15]: test lapack-testsuite: ---]
adt-run [11:50:15]: test lapack-testsuite:  - - - - - - - - - - results - - - - 
- - - - - -

lapack-testsuite FAIL non-zero exit status 1
adt-run [11:50:15]:  summary
xerbla-fortran   PASS
xerbla-c PASS
blas-testsuite   PASS
lapack-testsuite FAIL non-zero exit status 1

According to http://autopkgtest.ubuntu.com/packages/l/lapack/
it fails on armhf and i386 as well.

--
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#811191: [regression] lapack 3.6.0 fails the testsuite

2016-01-16 Thread Matthias Klose

On 16.01.2016 18:00, Sébastien Villemot wrote:

I was aware of the failure but decided to nevertheless add  that

> testsuite as an autopkgtest, in order to make the test failures more visible.

I'll never understand why people do that ... once Debian adds succeeding autopkg 
tests as a requirement for migration to testing your're screwed.


You really should mark these as XFAIL (expected to fail) and still succeed the 
test.

--
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#811210: add patch

2016-01-16 Thread Matthias Klose

Control: tags -1 + patch

  * Limit the GCC version check to the major version.

diff -Nru mpich-3.2/debian/patches/gcc-check.diff mpich-3.2/debian/patches/gcc-check.diff
--- mpich-3.2/debian/patches/gcc-check.diff	1970-01-01 01:00:00.0 +0100
+++ mpich-3.2/debian/patches/gcc-check.diff	2016-01-16 22:01:04.0 +0100
@@ -0,0 +1,16 @@
+Index: b/src/binding/cxx/mpicxx.h.in
+===
+--- a/src/binding/cxx/mpicxx.h.in
 b/src/binding/cxx/mpicxx.h.in
+@@ -17,10 +17,8 @@
+ // between 3.2.3 and 3.4.3 (!!)  Normally such changes
+ // should only occur at major releases (e.g., version 3 to 4)
+ #ifdef __GNUC__ 
+-# if __GNUC__ >= @GNUCXX_VERSION@ 
+-#  if __GNUC_MINOR__ > 2 && @GNUCXX_MINORVERSION@ == 2 
++# if __GNUC__ > @GNUCXX_VERSION@ 
+ #  error 'Please use the same version of GCC and g++ for compiling MPICH and user MPI programs'
+-#  endif
+ # endif 
+ #endif
+ 
diff -Nru mpich-3.2/debian/patches/series mpich-3.2/debian/patches/series
--- mpich-3.2/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ mpich-3.2/debian/patches/series	2016-01-16 21:45:39.0 +0100
@@ -0,0 +1 @@
+gcc-check.diff
-- 
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#811210: mpicxx.h always errors out with an unfullfillable compiler check

2016-01-16 Thread Matthias Klose

Package: src:mpich
Version: 3.2-4
Severity: grave
Tags: sid stretch

/usr/include/mpich/mpicxx.h reads

#ifdef __GNUC__
# if __GNUC__ >= 5
#  if __GNUC_MINOR__ > 2 && 3 == 2
#  error 'Please use the same version of GCC and g++ for compiling MPICH and 
user MPI programs'

#  endif
# endif
#endif

so this always errors out. Proposing to limit this check to the major version, 
or completely remove it.


--
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#801132: fix build on at least powerpc and ppc64el

2015-10-06 Thread Matthias Klose

Package: src:simbody
Version: 3.5.1+dfsg-1.1
Tags: patch

these archs only define the __linux__ macro.

patch at
http://launchpadlibrarian.net/220418128/simbody_3.5.1%2Bdfsg-1.1_3.5.1%2Bdfsg-1.1ubuntu1.diff.gz

--
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#800668: iep ftbfs, missing build dependencies, still fails tests

2015-10-05 Thread Matthias Klose

[please reply to the submitter and/or the original sender of the email too]

> I can make a new upload with an explicit empty test target, will it
> solve your issue?

well, it certainly will succeed the build, however why not find out why it 
fails?

--
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#800668: iep ftbfs, missing build dependencies, still fails tests

2015-10-02 Thread Matthias Klose

Package: src:iep
Version: 3.7-1
Severity: serious
Tags: sid stretch

the package is missing build dependencies on python3-pyzolib and python3-pyqt4, 
but even with these the package still fails the tests.  Note the odd warning 
about pyzolib.path as well, however it still ftbfs without it.


I: pybuild base:170: cd /home/packages/tmp/iep-3.7/.pybuild/pythonX.Y_3.5/build; 
python3.5 -m unittest discover -v

iep.tools.iepFileBrowser (unittest.loader._FailedTest) ... ERROR

==
ERROR: iep.tools.iepFileBrowser (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: iep.tools.iepFileBrowser
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File 
"/home/packages/tmp/iep-3.7/.pybuild/pythonX.Y_3.5/build/iep/tools/iepFileBrowser/__init__.py", 
line 51, in 

from .browser import Browser
  File 
"/home/packages/tmp/iep-3.7/.pybuild/pythonX.Y_3.5/build/iep/tools/iepFileBrowser/browser.py", 
line 11, in 

from .tree import Tree
  File 
"/home/packages/tmp/iep-3.7/.pybuild/pythonX.Y_3.5/build/iep/tools/iepFileBrowser/tree.py", 
line 780, in 

class PopupMenu(iep.iepcore.menu.Menu):
AttributeError: module 'iep.iepcore' has no attribute 'menu'


--
Ran 1 test in 0.000s

FAILED (errors=1)
Started our command server
Note about pyzolib.path - better use pathlib (part of py34)
E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: cd 
/home/packages/tmp/iep-3.7/.pybuild/pythonX.Y_3.5/build; python3.5 -m unittest 
discover -v


--
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#799218: please enable parallel builds

2015-09-16 Thread Matthias Klose
Package: src:pcl
Version: 1.7.2-10
Tags: patch

Please enable parallel builds, reducing the build time:

%:
dh  $@ --parallel --builddirectory=build

-- 
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#797809: no patch yet

2015-09-02 Thread Matthias Klose
Control: tags -1 - patch

sorry, no patch yet.

there are multiple issues involved:

 - building with SD 3.0
 - building with -std=c++11
 - building with boost 1.58

-- 
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#797809: gazebo ftbfs with SDF 3.0

2015-09-02 Thread Matthias Klose
Package: src:gazebo
Version: 5.0.1+dfsg-2.1
Severity: serious
Tags: sid stretch patch

gazebo explicitly wants SDF 2.3, fails with 3.0.

-- 
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#797281: ompl ftbfs in unstable

2015-08-29 Thread Matthias Klose
Package: src:ompl
Version: 0.14.2+dfsg-1
Severity: serious
Tags: sid stretch

ompl ftbfs in unstable, see the attached log.

dpkg-buildpackage: source package ompl
dpkg-buildpackage: source version 0.14.2+dfsg-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Leopold Palomo-Avellaneda 
l...@alaxarxa.net
 dpkg-source --before-build ompl-0.14.2+dfsg
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --builddirectory=build --buildsystem=cmake --parallel
   dh_testdir -O--builddirectory=build -O--buildsystem=cmake -O--parallel
   dh_auto_clean -O--builddirectory=build -O--buildsystem=cmake -O--parallel
   debian/rules override_dh_clean
make[1]: Entering directory '/scratch/packages/tmp/ompl-0.14.2+dfsg'
rm -rf build
rm -rf CMakeModules/ompl.pc
rm -rf py-bindings/ompl/bindings_generator.py*
rm -rf py-bindings/ompl/__init__.pyc
rm -rf .registered
rm -rf src/external/installPyPlusPlus.bat
rm -rf src/external/installPyPlusPlus.sh
rm -rf src/ompl/config.h
rm -rf tests/resources/config.h
rm -rf doc/markdown/api_overview.md  doc/markdown/download.md
rm -rf doc/markdown/mainpage.md
rm -rf py-bindings/bindings
rm -rf tests/BoostTestTeamCityReporter.h
find py-bindings/ -name *.pypp.*  | xargs -n1 rm -rf
find py-bindings/ -name *.pyc  | xargs -n1 rm -rf
find py-bindings/ -name *.so  | xargs -n1 rm -rf 
dh_clean
make[1]: Leaving directory '/scratch/packages/tmp/ompl-0.14.2+dfsg'
 debian/rules build-arch
dh build-arch --builddirectory=build --buildsystem=cmake --parallel
   dh_testdir -a -O--builddirectory=build -O--buildsystem=cmake -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/scratch/packages/tmp/ompl-0.14.2+dfsg'
mkdir -p build 
dh_auto_configure --builddirectory=build -- -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_C_FLAGS_RELEASE=-g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
-DCMAKE_CXX_FLAGS_RELEASE=-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2   
-DCMAKE_SHARED_LINKER_FLAGS_RELEASE=-Wl,-z,relro -Wl,--as-needed 
-DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_SKIP_INSTALL_RPATH=TRUE 
-DOMPL_ODESOLVER=ON -DOMPL_REGISTRATION=OFF -DOMPL_BUILD_PYBINDINGS=ON 
-DOMPL_BUILD_PYTESTS=OFF  
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_C_FLAGS_RELEASE=-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2 -DCMAKE_CXX_FLAGS_RELEASE=-g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2  
 -DCMAKE_SHARED_LINKER_FLAGS_RELEASE=-Wl,-z,relro -Wl,--as-needed 
-DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_SKIP_INSTALL_RPATH=TRUE 
-DOMPL_ODESOLVER=ON -DOMPL_REGISTRATION=OFF -DOMPL_BUILD_PYBINDINGS=ON 
-DOMPL_BUILD_PYTESTS=OFF
-- The CXX compiler identification is GNU 5.2.1
-- The C compiler identification is GNU 5.2.1
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Building RelWithDebInfo
-- Boost version: 1.58.0
-- Found the following Boost libraries:
--   date_time
--   thread
--   serialization
--   filesystem
--   system
--   program_options
--   unit_test_framework
--   chrono
-- Boost version: 1.58.0
-- Found the following Boost libraries:
--   python
CMake Warning (dev) at CMakeModules/PythonBindingsUtils.cmake:26 
(get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run cmake --help-policy CMP0045 for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target py_ompl.
Call Stack (most recent call first):
  py-bindings/CMakeLists.txt:6 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at src/ompl/CMakeLists.txt:81 (get_target_property):
  Policy CMP0026 is not set: Disallow use of the LOCATION target property.
  Run cmake --help-policy CMP0026 for policy details.  Use the cmake_policy
  command to set the policy and suppress this warning.

  The LOCATION property should not be read from target ompl.  Use the
  target name directly with add_custom_command, or use the generator
  expression $TARGET_FILE, as appropriate.

This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done
-- Generating done
-- Build files have been written to: 
/scratch/packages/tmp/ompl-0.14.2+dfsg/build
make[1]: 

Bug#797285: tango ftbfs in unstable

2015-08-29 Thread Matthias Klose
Package: src:tango
Version: 8.1.2c+dfsg-5
Severity: serious
Tags: sid stretch

tango ftbfs in unstable,

libtool: link: g++ -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -std=c++11 -D_REENTRANT -DOMNI_UNLOADABLE_STUBS -Wl,-z
-Wl,relro -o .libs/notifd2db notifd2db.o  -L../../lib/cpp/server
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so
-L../../lib/cpp/log4tango/src
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/log4tango/src/.libs/liblog4tango.so
-lzmq -ldl -L/usr/lib -lomniORB4 -lomniDynamic4 -lCOS4 -lnsl -lomnithread 
-lpthread
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2constunsigned long::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2constlong::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2constint::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2constunsigned char::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2constdouble::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2constunsigned int::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2constshort::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2constunsigned short::str'
/scratch/packages/tmp/tango-8.1.2c+dfsg/build/lib/cpp/server/.libs/libtango.so:
undefined reference to `Tango::ranges_type2constfloat::str'
collect2: error: ld returned 1 exit status
Makefile:472: recipe for target 'notifd2db' failed
make[4]: *** [notifd2db] Error 1
make[4]: Leaving directory
'/scratch/packages/tmp/tango-8.1.2c+dfsg/build/utils/notifd2db'
Makefile:432: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/scratch/packages/tmp/tango-8.1.2c+dfsg/build/utils'
Makefile:524: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/scratch/packages/tmp/tango-8.1.2c+dfsg/build'
Makefile:454: recipe for target 'all' failed
make[1]: *** [all] Error 2

-- 
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#797284: pytango ftbfs in unstable

2015-08-29 Thread Matthias Klose
Package: src:pytango
Version: 8.1.5-1
Severity: serious
Tags: sid stretch

pytango ftbfs in unstable:

creating /scratch/packages/tmp/pytango-8.1.5/build/sphinx/html
Running Sphinx v1.3.1
Traceback (most recent call last):
  File setup.py, line 528, in module
main()
  File setup.py, line 525, in main
return setup(**setup_args())
  File /usr/lib/python2.7/distutils/core.py, line 151, in setup
dist.run_commands()
  File /usr/lib/python2.7/distutils/dist.py, line 953, in run_commands
self.run_command(cmd)
  File /usr/lib/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
  File setup.py, line 210, in run
dftbuild.run(self)
  File /usr/lib/python2.7/distutils/command/build.py, line 128, in run
self.run_command(cmd_name)
  File /usr/lib/python2.7/distutils/cmd.py, line 326, in run_command
self.distribution.run_command(command)
  File /usr/lib/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
  File setup.py, line 282, in run
sphinx.setup_command.BuildDoc.run(self)
  File /usr/lib/python2.7/dist-packages/sphinx/setup_command.py, line 161, in 
run
freshenv=self.fresh_env)
  File /usr/lib/python2.7/dist-packages/sphinx/application.py, line 126, in
__init__
confoverrides or {}, self.tags)
  File /usr/lib/python2.7/dist-packages/sphinx/config.py, line 277, in 
__init__
execfile_(filename, config)
  File /usr/lib/python2.7/dist-packages/sphinx/util/pycompat.py, line 128, in
execfile_
exec_(code, _globals)
  File /usr/lib/python2.7/dist-packages/six.py, line 672, in exec_
exec(exec _code_ in _globs_, _locs_)
  File string, line 1, in module
  File conf.py, line 15, in module
  File
/scratch/packages/tmp/pytango-8.1.5/build/lib.linux-x86_64-2.7/PyTango/__init__.py,
line 120, in module
from . import _PyTango
ImportError:
/scratch/packages/tmp/pytango-8.1.5/build/lib.linux-x86_64-2.7/PyTango/_PyTango.so:
undefined symbol: _ZN5Tango11DeviceProxy14get_corba_nameB5cxx11Eb
dh_auto_build: python setup.py build --force returned exit code 1
debian/rules:13: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/scratch/packages/tmp/pytango-8.1.5'

-- 
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#797284: pytango ftbfs in unstable

2015-08-29 Thread Matthias Klose
On 08/29/2015 06:45 PM, PICCA Frederic-Emmanuel wrote:
 ok, when I unmangle the symbol, I get this
 
 c++filt _ZN5Tango11DeviceProxy14get_corba_nameB5cxx11Eb
 
 Tango::DeviceProxy::get_corba_name[abi:cxx11](bool)
 
 so it seems that this FTBFS is about a cxx11 ABi change.
 
 during this build the c++ code compile in pytango (boost python)is noo more 
 compatible with the 
 libtango8 (whcih is not yest recompile with gcc5 due to the FTBF).
 
 Even if a compilation of tango and then pytango should be possible.
 
 I am wondering if the right solution is not to create a libtango8v5 and then 
 to recompile pytango with this version ?
 
 can I have yur opinion doko ?

sure, renaming the library sounds fine. However, it currently ftbfs.

-- 
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#797284: pytango ftbfs in unstable

2015-08-29 Thread Matthias Klose
On 08/29/2015 08:51 PM, PICCA Frederic-Emmanuel wrote:
 I am working on it with the upstream.
 
 once fixed,I will upload a tango with the v5 extension. then I will ask for a 
 transition
 right ?

any libstdc++6 follow-up transition is waived. you can just upload to unstable.

-- 
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#778108: root-system: ftbfs with GCC-5

2015-08-14 Thread Matthias Klose
Control: tags -1 + patch

the new upstream version fixes the build failures with GCC 5. Had to work around
the build failure on armhf, and enabled the builds for powerpc and ppc64el.
Note that I forgot to prepare the dfsg tarball.

https://launchpad.net/ubuntu/+source/root-system/5.34.30-0ubuntu3

-- 
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#791008: coinutils: library transition may be needed when GCC 5 is the default

2015-08-11 Thread Matthias Klose
On 08/11/2015 11:45 PM, Miles Lubin wrote:
 On Tue, Aug 11, 2015 at 2:02 PM, Julien Cristau jcris...@debian.org wrote:
 coinutils exposes a number of things involving std::string e.g. in
 CoinParam or CoinFileIO (the first two I've checked), so
 coinor-libcoinutils3 needs to be renamed.

 A possible patch is available at
 https://launchpad.net/ubuntu/+source/coinutils/2.9.15-3ubuntu1
 
 Thank you for confirming the issue. As the maintainer of this package,
 I do not currently have the time to prepare for a transition.

ok, NMUing the package.

-- 
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#791226: add patch

2015-08-09 Thread Matthias Klose
Control: tags -1 + patch

this depends on the openexr transition.
  * Rename library packages for g++5 ABI transition.

diff -Nru opencv-2.4.9+dfsg/debian/control opencv-2.4.9+dfsg/debian/control
--- opencv-2.4.9+dfsg/debian/control2014-09-08 10:10:39.0 +
+++ opencv-2.4.9+dfsg/debian/control2015-08-06 07:19:43.0 +
@@ -92,15 +92,15 @@
 Package: libcv2.4
 Architecture: all
 Depends: ${misc:Depends},
-   libopencv-core2.4,
-   libopencv-imgproc2.4,
-   libopencv-flann2.4,
-   libopencv-features2d2.4,
-   libopencv-calib3d2.4,
-   libopencv-objdetect2.4,
-   libopencv-legacy2.4,
-   libopencv-video2.4,
-   libopencv-ml2.4
+   libopencv-core2.4v5,
+   libopencv-imgproc2.4v5,
+   libopencv-flann2.4v5,
+   libopencv-features2d2.4v5,
+   libopencv-calib3d2.4v5,
+   libopencv-objdetect2.4v5,
+   libopencv-legacy2.4v5,
+   libopencv-video2.4v5,
+   libopencv-ml2.4v5
 Description: computer vision library - libcv* translation package
  This package provide files for translation from libcv2.1 to libcv2.4.
  .
@@ -141,7 +141,7 @@
 Package: libhighgui2.4
 Architecture: all
 Depends: ${misc:Depends},
-   libopencv-highgui2.4
+   libopencv-highgui2.4v5
 Description: computer vision library - libhighgui translation package
  This package provide files for translation from libhighgui2.1 to 
libhighgui2.4.
  .
@@ -186,14 +186,14 @@
 Package: libcvaux2.4
 Architecture: all
 Depends: ${misc:Depends},
-   libopencv-core2.4,
-   libopencv-imgproc2.4,
-   libopencv-features2d2.4,
-   libopencv-calib3d2.4,
-   libopencv-objdetect2.4,
-   libopencv-legacy2.4,
-   libopencv-video2.4,
-   libopencv-contrib2.4
+   libopencv-core2.4v5,
+   libopencv-imgproc2.4v5,
+   libopencv-features2d2.4v5,
+   libopencv-calib3d2.4v5,
+   libopencv-objdetect2.4v5,
+   libopencv-legacy2.4v5,
+   libopencv-video2.4v5,
+   libopencv-contrib2.4v5
 Description: computer vision library - libcvaux translation package
  This package provide files for translation from libcvaux2.1 to libcvaux2.4.
  .
@@ -274,7 +274,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: ${misc:Depends}, libopencv-core2.4 (= ${binary:Version}),
+Depends: ${misc:Depends}, libopencv-core2.4v5 (= ${binary:Version}),
zlib1g-dev
 Description: development files for libopencv-core
  This package contains the header files and static library needed to compile
@@ -290,12 +290,14 @@
  analysis, structural analysis, motion analysis and object tracking, object
  recognition, camera calibration and 3D reconstruction.
 
-Package: libopencv-core2.4
+Package: libopencv-core2.4v5
 Section: libs
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends}, ${shlibs:Depends}
+Conflicts: libopencv-core2.4
+Replaces: libopencv-core2.4
 Description: computer vision core library
  This package contains the OpenCV (Open Computer Vision) core runtime 
libraries.
  .
@@ -315,7 +317,7 @@
 Multi-Arch: same
 Depends: ${misc:Depends},
libopencv-core-dev (= ${binary:Version}),
-   libopencv-ml2.4 (= ${binary:Version})
+   libopencv-ml2.4v5 (= ${binary:Version})
 Description: development files for libopencv-ml
  This package contains the header files and static library needed to compile
  applications that use OpenCV (Open Computer Vision) Machine Learning library.
@@ -330,13 +332,15 @@
  analysis, structural analysis, motion analysis and object tracking, object
  recognition, camera calibration and 3D reconstruction.
 
-Package: libopencv-ml2.4
+Package: libopencv-ml2.4v5
 Section: libs
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends},
-   libopencv-core2.4 (= ${binary:Version})
+   libopencv-core2.4v5 (= ${binary:Version})
+Conflicts: libopencv-ml2.4
+Replaces: libopencv-ml2.4
 Description: computer vision Machine Learning library
  This package contains the OpenCV (Open Computer Vision) Machine Learning
  runtime libraries.
@@ -357,7 +361,7 @@
 Multi-Arch: same
 Depends: ${misc:Depends},
libopencv-core-dev (= ${binary:Version}),
-   libopencv-imgproc2.4 (= ${binary:Version})
+   libopencv-imgproc2.4v5 (= ${binary:Version})
 Description: development files for libopencv-imgproc
  This package contains the header files and static library needed to compile
  applications that use OpenCV (Open Computer Vision) Image Processing library.
@@ -372,13 +376,15 @@
  analysis, structural analysis, motion analysis and object tracking, object
  recognition, camera calibration and 3D reconstruction.
 
-Package: libopencv-imgproc2.4
+Package: libopencv-imgproc2.4v5
 Section: libs
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends},
-   libopencv-core2.4 (= ${binary:Version})
+   libopencv-core2.4v5 (= 

Bug#794736: libvigraimpex: library transition is needed when GCC 5 is the default

2015-08-06 Thread Matthias Klose
Package: src:libvigraimpex
Version: 1.10.0+dfsg-9
Severity: serious
Tags: sid stretch confirmed
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

[ confirmed, for both 1.10.0+dfsg-9 in experimental and 1.9.0+dfsg-10 in 
unstable ]


Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

What is needed:

 - Rebuild the library using g++/g++-5 from experimental. Note that
   most likely all C++ libraries within the build dependencies need
   a rebuild too. You can find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150701/
   Search for BEGIN GCC CXX11 in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.

 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append v5 to the name of the package
   (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:

 user release.debian@packages.debian.org
 usertag this issue + transition
 block this issue by 790756
 reassign this issue release.debian.org

 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition

-- 
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#791226: opencv: library transition may be needed when GCC 5 is the default

2015-08-05 Thread Matthias Klose
Control: tags -1 + confirmed
Control: retitle -1 opencv: library transition is needed when GCC 5 is the 
default

confirmed, or else at least visp breaks/ftbfs

-- 
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#778123: ftbfs with GCC-5

2015-07-25 Thread Matthias Klose
Control: tags -1 + pending

this is part of the gfortran mod transition as well, and needs its build
dependencies built first using gfortran 5.

-- 
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#778106: rheolef: ftbfs with GCC-5

2015-07-25 Thread Matthias Klose

after fixing

--- a/skit/plib2/load_chunk.h
+++ b/skit/plib2/load_chunk.h
@@ -28,7 +28,7 @@ load_chunk (std::istream s, RandomItera
 {
 while (iter != last)
 if (!(s  *iter++)) return false;
-return s;
+return bool(s);
 }
 template class RandomIterator, class GetFunction
 inline
@@ -37,7 +37,7 @@ load_chunk (std::istream s, RandomItera
 {
 while (iter != last)
 if (! get_element (s, *iter++)) return false;
-return s;
+return bool(s);
 }
 } // namespace rheolef
 #endif // _RHEOLEF_LOAD_CHUNK_H

I get:

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../config -fno-strict-aliasing
-I../../include -I/usr/include/suitesparse -D_FORTIFY_SOURCE=2 -O3
-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -std=c++11 -Wall -Wno-unused -Werror
-Wno-strict-aliasing -O2 -MT index_set.lo -MD -MP -MF .deps/index_set.Tpo -c
index_set.cc  -fPIC -DPIC -o .libs/index_set.o
In file included from /usr/include/boost/serialization/set.hpp:26:0,
 from ../../include/rheolef/index_set.h:38,
 from index_set.cc:21:
/usr/include/boost/serialization/detail/stack_constructor.hpp: In constructor
'boost::serialization::detail::stack_constructArchive,
T::stack_construct(Archive, unsigned int)':
/usr/include/boost/serialization/detail/stack_constructor.hpp:54:9: error:
'load_construct_data_adl' is not a member of 'boost::serialization'
 boost::serialization::load_construct_data_adl(
 ^
Makefile:727: recipe for target 'index_set.lo' failed
make[4]: *** [index_set.lo] Error 1
Makefile:621: recipe for target 'all' failed
make[3]: *** [all] Error 2
Makefile:451: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
Makefile:561: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/scratch/packages/tmp/rheolef-6.5'
debian/rules:59: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2

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


  1   2   >