Bug#798601: GCC Update
Probably related to the latest GCC update, I'll take care of 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
Processed: tagging 798675, tagging 798665, tagging 798666
Processing commands for cont...@bugs.debian.org: > tags 798675 + sid stretch Bug #798675 [src:openscad] openscad: package has broken dependecies Added tag(s) stretch and sid. > tags 798665 + sid stretch Bug #798665 [src:mmtk] mmtk: FTBFS: Not compatible with python-numpy 1.9 Added tag(s) stretch and sid. > tags 798666 + sid stretch Bug #798666 [src:dirspec] dirspec: FTBFS: Fails PEP8 checks Added tag(s) sid and stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 798665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798665 798666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798666 798675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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#798652: scilab: scilab doesn't work on ppc64el: could not find the Java configuration for the model <>
Package: scilab Version: 5.5.2-1 Severity: normal While scilab is available on ppc64el, it doesn't actually work: > $ /usr/bin/scilab > Could not find the Java configuration for the model . Please contact > us on http://bugzilla.scilab.org > /usr/bin/scilab-bin: error while loading shared libraries: libjava.so: cannot > open shared object file: No such file or directory I apply this patch to get rid of the error: > --- scilab-5.5.2.orig/bin/scilab > +++ scilab-5.5.2/bin/scilab > @@ -528,7 +528,7 @@ > "ppc"|"powerpc") > proc="ppc" > ;; > -"ppc64"|"ppc64el") > +"ppc64"|"ppc64el"|"ppc64le") > proc="ppc64" > ;; > "s390") Unfortunately, we then get another error: > $ /usr/bin/scilab > Could not create a Scilab main class. Error: > Exception in thread "main" java.lang.ExceptionInInitializerError > at javax.media.opengl.GLProfile.(GLProfile.java:120) > at org.scilab.modules.gui.SwingView.(Unknown Source) > at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source) > at org.scilab.modules.core.Scilab.(Unknown Source) > Caused by: java.lang.RuntimeException: Please port CPU detection to your > platform (linux/ppc64) > at > jogamp.common.os.PlatformPropsImpl.getCPUTypeImpl(PlatformPropsImpl.java:304) > at > jogamp.common.os.PlatformPropsImpl.(PlatformPropsImpl.java:134) > ... 4 more > > Scilab cannot create Scilab Java Main-Class (we have not been able to find > the main Scilab class. Check if the Scilab and thirdparty packages are > available). Thanks, Erwan. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
python-qwt_6.1.2~a3-1~exp1_i386.changes REJECTED
Maintainer request. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- 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#798651: getfem++: FTBFS on ppc64el: Could not find the Java configuration for the model
Package: getfem++ Version: 4.2.1~beta1~svn4635~dfsg-5 Severity: normal Dear Maintainer, getfem++ doesn't build on ppc64el. Let me know if you need any details. > powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -fno-strict-aliasing -Wall -g -O2 > -fstack-protector-strong -Wformat -Werror=format-security -O3 > -D_FORTIFY_SOURCE=2 -DGMM_USES_BLAS -I/usr/include -I/usr/include -fPIC > -I../../../src/getfem -I../../../src/getfem -I./.. -I. > -I/usr/lib/python2.7/dist-packages/numpy/core/include > -I/usr/include/python2.7 -c getfem_python_c.c -o ./getfem_python_c.o > In file included from > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1804:0, > from > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:17, > from > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4, > from getfem_python_c.c:22: > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2: > warning: #warning "Using deprecated NumPy API, disable it by " "#defining > NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp] > #warning "Using deprecated NumPy API, disable it by " \ > ^ > powerpc64le-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions > -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat > -Werror=format-security -Wl,-z,relro -Wall -g -O2 -fstack-protector-strong > -Wformat -Werror=format-security -O3 -D_FORTIFY_SOURCE=2 -DGMM_USES_BLAS > -I/usr/include -I/usr/include ./getfem_python_c.o -L../.libs > -L../../../src/.libs -lgetfemint -lgetfem -lzmumps_seq -lcmumps_seq > -ldmumps_seq -lsmumps_seq -lmuparser -lqhull -lsuperlu -lblas -lsuperlu > -lmetis -lstdc++ -lm -o ./_getfem.so > make[6]: Leaving directory > '/build/getfem++-QE2FtB/getfem++-4.2.1~beta1~svn4635~dfsg/interface/src/python' > Making all in scilab > make[6]: Entering directory > '/build/getfem++-QE2FtB/getfem++-4.2.1~beta1~svn4635~dfsg/interface/src/scilab' > SCI_DISABLE_TK=1 SCI_JAVA_ENABLE_HEADLESS=1 scilab -nw -nb -f > /build/getfem++-QE2FtB/getfem++-4.2.1~beta1~svn4635~dfsg/interface/src/scilab/makefile_builder.sce > Could not find the Java configuration for the model . Please contact > us on http://bugzilla.scilab.org > /usr/bin/scilab-bin: error while loading shared libraries: libjava.so: cannot > open shared object file: No such file or directory > Makefile:893: recipe for target 'all' failed > make[6]: *** [all] Error 127 It seems the bug is in scilab. I'll file a bug. Maybe it would be good to leave this bug open until scilab is fixed, and then we can check if this package works on ppc64el. Thanks, Erwan. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Processed (with 2 errors): your mail
Processing commands for cont...@bugs.debian.org: > retitle 798652 scilab: scilab doesn't work on ppc64el: could not find Bug #798652 [scilab] scilab: scilab doesn't work on ppc64el: could not find the Java configuration for the model <> Changed Bug title to 'scilab: scilab doesn't work on ppc64el: could not find' from 'scilab: scilab doesn't work on ppc64el: could not find the Java configuration for the model <>' > the Java configuration for the model Unknown command or malformed arguments to command. > retitle 798651 getfem++: FTBFS on ppc64el: Could not find the Java Bug #798651 [getfem++] getfem++: FTBFS on ppc64el: Could not find the Java configuration for the model Changed Bug title to 'getfem++: FTBFS on ppc64el: Could not find the Java' from 'getfem++: FTBFS on ppc64el: Could not find the Java configuration for the model ' > configuration for the model Unknown command or malformed arguments to command. > block 798651 by 798652 Bug #798651 [getfem++] getfem++: FTBFS on ppc64el: Could not find the Java 798651 was not blocked by any bugs. 798651 was not blocking any bugs. Added blocking bug(s) of 798651: 798652 > thanks Stopping processing here. Please contact me if you need assistance. -- 798651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798651 798652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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#798652: scilab: scilab doesn't work on ppc64el: could not find the Java configuration for the model <>
Jogl has to be updated too. I think there is a familiar patch for another arch. Le 11 septembre 2015 15:45:19 GMT+02:00, Erwan Prioula écrit : >Package: scilab >Version: 5.5.2-1 >Severity: normal > >While scilab is available on ppc64el, it doesn't actually work: >> $ /usr/bin/scilab >> Could not find the Java configuration for the model . Please >contact us on http://bugzilla.scilab.org >> /usr/bin/scilab-bin: error while loading shared libraries: >libjava.so: cannot open shared object file: No such file or directory > >I apply this patch to get rid of the error: >> --- scilab-5.5.2.orig/bin/scilab >> +++ scilab-5.5.2/bin/scilab >> @@ -528,7 +528,7 @@ >> "ppc"|"powerpc") >> proc="ppc" >> ;; >> -"ppc64"|"ppc64el") >> +"ppc64"|"ppc64el"|"ppc64le") >> proc="ppc64" >> ;; >> "s390") > >Unfortunately, we then get another error: >> $ /usr/bin/scilab >> Could not create a Scilab main class. Error: >> Exception in thread "main" java.lang.ExceptionInInitializerError >> at javax.media.opengl.GLProfile.(GLProfile.java:120) >> at org.scilab.modules.gui.SwingView.(Unknown Source) >> at org.scilab.modules.gui.SwingView.registerSwingView(Unknown >Source) >> at org.scilab.modules.core.Scilab.(Unknown Source) >> Caused by: java.lang.RuntimeException: Please port CPU detection to >your platform (linux/ppc64) >> at >jogamp.common.os.PlatformPropsImpl.getCPUTypeImpl(PlatformPropsImpl.java:304) >> at >jogamp.common.os.PlatformPropsImpl.(PlatformPropsImpl.java:134) >> ... 4 more >> >> Scilab cannot create Scilab Java Main-Class (we have not been able to >find the main Scilab class. Check if the Scilab and thirdparty packages >are available). > >Thanks, >Erwan. > >-- >debian-science-maintainers mailing list >debian-science-maintainers@lists.alioth.debian.org >http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers -- Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.-- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Processed: your mail
Processing commands for cont...@bugs.debian.org: > retitle 798652 scilab: scilab doesn't work on ppc64el: could not find the > Java configuration for the model Bug #798652 [scilab] scilab: scilab doesn't work on ppc64el: could not find Changed Bug title to 'scilab: scilab doesn't work on ppc64el: could not find the Java configuration for the model ' from 'scilab: scilab doesn't work on ppc64el: could not find' > retitle 798651 getfem++: FTBFS on ppc64el: Could not find the Java > configuration for the model Bug #798651 [getfem++] getfem++: FTBFS on ppc64el: Could not find the Java Changed Bug title to 'getfem++: FTBFS on ppc64el: Could not find the Java configuration for the model ' from 'getfem++: FTBFS on ppc64el: Could not find the Java' > thanks Stopping processing here. Please contact me if you need assistance. -- 798651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798651 798652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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#798665: mmtk: FTBFS: Not compatible with python-numpy 1.9
Source: mmtk Version: 2.7.9-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, mmtk fails to build from source in unstable/amd64 as python-numpy 1.9 removed oldnumeric: [..] dh_auto_build python setup.py build --force Traceback (most recent call last): File "setup.py", line 66, in from Scientific import N File "/usr/lib/python2.7/dist-packages/Scientific/N.py", line 6, in from numpy.oldnumeric import * ImportError: No module named oldnumeric dh_auto_build: python setup.py build --force returned exit code 1 debian/rules:34: recipe for target 'build' failed make: *** [build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/mmtk_2.7.9-1.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Thu Sep 10 15:18:40 GMT+12 2015 I: pbuilder-time-stamp: 1441941520 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: Mounting /dev/shm I: Mounting /sys I: policy-rc.d already exists I: Installing the build-deps -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder TeamDescription: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper (>= 9), cython, libnetcdf-dev, python-all-dev, python-numpy, python-netcdf, python-scientific, python-sphinx (>= 1.0.7+dfsg) dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 20260 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ... Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on cython; however: Package cython is not installed. pbuilder-satisfydepends-dummy depends on libnetcdf-dev; however: Package libnetcdf-dev is not installed. pbuilder-satisfydepends-dummy depends on python-all-dev; however: Package python-all-dev is not installed. pbuilder-satisfydepends-dummy depends on python-numpy; however: Package python-numpy is not installed. pbuilder-satisfydepends-dummy depends on python-netcdf; however: Package python-netcdf is not installed. pbuilder-satisfydepends-dummy depends on python-scientific; however: Package python-scientific is not installed. pbuilder-satisfydepends-dummy depends on python-sphinx (>= 1.0.7+dfsg); however: Package python-sphinx is not installed. Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ... Reading package lists... Building dependency tree... Reading state information... Initializing package states... Writing extended state information... Building tag database... pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) The following NEW packages will be installed: cython{a} docutils-common{a} fonts-font-awesome{a} fonts-lato{a} hdf5-helpers{a} libblas-common{a} libblas3{a} libcurl3-gnutls{a} libcurl4-gnutls-dev{a} libexpat1{a} libexpat1-dev{a} libgfortran3{a} libgnutls-deb0-28{a} libgssapi-krb5-2{a} libhdf5-8{a} libhdf5-cpp-8{a} libhdf5-dev{a} libhogweed4{a} libidn11{a} libjpeg-dev{a} libjpeg62-turbo{a} libjpeg62-turbo-dev{a} libjs-jquery{a} libjs-modernizr{a} libjs-sphinxdoc{a} libjs-underscore{a} libk5crypto3{a} libkeyutils1{a} libkrb5-3{a} libkrb5support0{a} liblapack3{a} libldap-2.4-2{a} libnetcdf-dev{a} libnetcdf7{a} libnetcdfc7{a} libnettle6{a} libp11-kit0{a} libpython-all-dev{a} libpython-dev{a} libpython-stdlib{a} libpython2.7{a} libpython2.7-dev{a} libpython2.7-minimal{a} libpython2.7-stdlib{a} librtmp1{a} libsasl2-2{a} libsasl2-modules-db{a} libssh2-1{a} libssl1.0.0{a} libtasn1-6{a} mime-support{a} python{a} python-alabaster{a} python-all{a} python-all-dev{a} python-babel{a}