hypre 2.11.1-4 MIGRATED to testing
FYI: The status of the hypre source package in Debian's testing distribution has changed. Previous version: 2.11.1-3 Current version: 2.11.1-4 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
yade 2017.01a-9 MIGRATED to testing
FYI: The status of the yade source package in Debian's testing distribution has changed. Previous version: 2017.01a-8 Current version: 2017.01a-9 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- 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: > forwarded 856356 https://github.com/linbox-team/linbox/issues/37 Bug #856356 [src:linbox] linbox FTBFS on mips/mipsel: segfault in test-charpoly Set Bug forwarded-to-address to 'https://github.com/linbox-team/linbox/issues/37'. > thanks Stopping processing here. Please contact me if you need assistance. -- 856356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856356 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#853413: marked as done (gazebo: ftbfs with GCC-7)
Your message dated Sat, 5 Aug 2017 23:11:36 +0300 with message-id <20170805201136.2uds4ysttj4imndc@localhost> and subject line gazebo builds with gcc 7 has caused the Debian Bug report #853413, regarding gazebo: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 853413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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
Bug#853660: marked as done (simbody: ftbfs with GCC-7)
Your message dated Sat, 5 Aug 2017 22:58:09 +0300 with message-id <20170805195809.62lpak2lrsn3vvo5@localhost> and subject line simbody builds with gcc 7 has caused the Debian Bug report #853660, regarding simbody: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 853660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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:
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 853541 src:tbb Bug #853541 [src:mathicgb] mathicgb: ftbfs with GCC-7 Bug reassigned from package 'src:mathicgb' to 'src:tbb'. No longer marked as found in versions mathicgb/1.0~git20170104-1. Ignoring request to alter fixed versions of bug #853541 to the same values previously set > forcemerge 853403 853541 Bug #853403 {Done: Steve Capper} [src:tbb] flexbar: ftbfs with GCC-7 Bug #853679 {Done: Steve Capper } [src:tbb] tbb: ftbfs with GCC-7 Bug #853541 [src:tbb] mathicgb: ftbfs with GCC-7 Unset Bug forwarded-to-address Severity set to 'important' from 'serious' Marked Bug as done Added indication that 853541 affects src:flexbar Marked as fixed in versions tbb/2017~U7-2. Marked as found in versions tbb/4.3~20150611-2. Bug #853679 {Done: Steve Capper } [src:tbb] tbb: ftbfs with GCC-7 Merged 853403 853541 853679 > affects 853403 src:mathicgb Bug #853403 {Done: Steve Capper } [src:tbb] flexbar: ftbfs with GCC-7 Bug #853541 {Done: Steve Capper } [src:tbb] mathicgb: ftbfs with GCC-7 Bug #853679 {Done: Steve Capper } [src:tbb] tbb: ftbfs with GCC-7 Added indication that 853403 affects src:mathicgb Added indication that 853541 affects src:mathicgb Added indication that 853679 affects src:mathicgb > thanks Stopping processing here. Please contact me if you need assistance. -- 853403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853403 853541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853541 853679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853679 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#870688: [Debian-science-sagemath] Sage 8.0 status (was Re: Sage 7.6 upload for RC bugfix and GAP 4.8.7 in unstable)
Tobias Hansen: > [..]> > > Hi, > > good work on finding the fpylll issue! Now the main holdup for sage 8.0 > is still cypari2 being stuck in NEW. I wrote on June 21 to > ftpmas...@debian.org and August 2 directly to the ftpmaster who helped > us get sagemath through NEW in time for stretch. Let's see if it helps. > > I'm also not totally sure if the sagemath packages can be built at the > moment. When I build in a schroot with sage deps installed with > DEB_BUILD_OPTIONS=parallel=5 fakeroot debian/rules binary > after the build is almost completed, including running the tests, it > later tries again to run the test suite and fails (I attached the end of > the console output). I wanted to try if this also happens with sbuild > once the fpylll problem is fixed. > > However I will be on vacation the next three weeks. > > The accidental upload of cysignals 1.6.5 to unstable is now a RC bug > (#870688). Not sure if we should fix it by downgrading cysignals, > patching sage 7.6 or just let the bug sit until we upload sage 8.0. At > least the "Breaks: sagemath (<< 8.0~)" does indeed prevent cysignals > from migrating to testing, which is good. > > [..] Hi, I'm at DebConf over the next week and will very likely be able to find some time to deal with this. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git -- 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#870698: Possible fix for fplll/fpylll issue with default strategy path
Hi, I just pushed to fplll's Debian git repository a tentative 5.1.0-3 which would fix the recently reported issue with fpylll : I rewrote the patch for the default strategies path changes. I'm a bit at loss on how to check if that really fixes anything : I tried to build fpylll (success), but then trying to "import fpylll" in python gave: RuntimeError: You must get the file local/bin/sage-maxima.lisp so I can't really test seriously... Cheers, Snark on #debian-science -- 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#853392: marked as done (esys-particle: ftbfs with GCC-7)
Your message dated Sat, 5 Aug 2017 17:40:21 +0300 with message-id <20170805144021.bfwlkzipgirc7alj@localhost> and subject line Seems demoted to a warning in the released gcc 7 has caused the Debian Bug report #853392, regarding esys-particle: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 853392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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
Bug#870821: esys-particle FTBFS with perl 5.26
Source: esys-particle Version: 2.3.5+dfsg1-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/esys-particle.html ... ./makeglos.pl paper.glo Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\\newglossarytype\[(.*)\]{ <-- HERE (.*)}{(.*)}{(.*)}/ at ./makeglos.pl line 49. Makefile:606: recipe for target 'ESyS-Particle_Tutorial.pdf' failed make[4]: *** [ESyS-Particle_Tutorial.pdf] Error 255 -- 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: Re: Bug#853513: libvigraimpex: ftbfs with GCC-7
Processing control commands: > forwarded -1 https://github.com/ukoethe/vigra/issues/409 Bug #853513 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-7 Set Bug forwarded-to-address to 'https://github.com/ukoethe/vigra/issues/409'. > block 853447 with 853513 Bug #853447 [src:hugin] hugin: ftbfs with GCC-7 853447 was blocked by: 853513 853447 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #853447 to the same blocks previously set > block 853389 with 853513 Bug #853389 [src:enblend-enfuse] enblend-enfuse: ftbfs with GCC-7 853389 was not blocked by any bugs. 853389 was not blocking any bugs. Added blocking bug(s) of 853389: 853513 -- 853389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853389 853447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853447 853513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853513 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#853513: libvigraimpex: ftbfs with GCC-7
Control: forwarded -1 https://github.com/ukoethe/vigra/issues/409 Control: block 853447 with 853513 Control: block 853389 with 853513 On 2017-07-21 Daniel Stenderwrote: > There's currently another build break happening: > > {standard input}: Assembler messages: > {standard input}:512533: Warning: end of file not at end of a line; newline > inserted > {standard input}: Error: open CFI at the end of file; missing .cfi_endproc > directive > c++: internal compiler error: Killed (program cc1plus) > Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. [...] > make[4]: Leaving directory > '/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj.python2.7' Afaict from the message this is gcc *6* crashing. As noted before 1.11.1 /builds/ successfully with gcc 7, there is just the testsuite error in run_test_blockwisewatersheds.sh. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers