Bug#853639: Fix for the regina-normal FTBFS with gcc 7

[Benjamin Burton]

Hi Adrian,

> A fix for the regina-normal FTBFS with gcc 7 is attached.

Having just uploaded the fix that has been sitting on my hard drive while I was 
on holiday all week, I realised that you had also sent in a patch for this 
(which of course is the same one-liner as mine).

Apologies for the duplicated effort, and thanks for looking into this.

- Ben.

Bug#871202: marked as done (qevercloud: FTBFS: make[4]: *** No rule to make target 'thrift_parser/thrift_lemon.cpp', needed by 'thrift_parser/CMakeFiles/thrift_parser_autogen'. Stop.)

[Debian Bug Tracking System]

Your message dated Sat, 19 Aug 2017 01:34:10 +
with message-id 
and subject line Bug#871202: fixed in qevercloud 3.0.3+ds-3
has caused the Debian Bug report #871202,
regarding qevercloud: FTBFS: make[4]: *** No rule to make target 
'thrift_parser/thrift_lemon.cpp', needed by 
'thrift_parser/CMakeFiles/thrift_parser_autogen'.  Stop.
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.)


-- 
871202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qevercloud
Version: 3.0.3+ds-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[4]: Entering directory 
> '/<>/qevercloud-3.0.3+ds/QEverCloudGenerator'
> make[4]: *** No rule to make target 'thrift_parser/thrift_lemon.cpp', needed 
> by 'thrift_parser/CMakeFiles/thrift_parser_autogen'.  Stop.
> make[4]: Leaving directory 
> '/<>/qevercloud-3.0.3+ds/QEverCloudGenerator'
> CMakeFiles/Makefile2:157: recipe for target 
> 'thrift_parser/CMakeFiles/thrift_parser_autogen.dir/all' failed
> make[3]: *** [thrift_parser/CMakeFiles/thrift_parser_autogen.dir/all] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/qevercloud_3.0.3+ds-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: qevercloud
Source-Version: 3.0.3+ds-3

We believe that the bug you reported is fixed in the latest version of
qevercloud, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang <073p...@gmail.com> (supplier of updated qevercloud package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 Aug 2017 10:11:01 +0800
Source: qevercloud
Binary: libqt5qevercloud3 qevercloud-doc qt5qevercloud-dev
Architecture: source
Version: 3.0.3+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Boyuan Yang <073p...@gmail.com>
Changed-By: Boyuan Yang <073p...@gmail.com>
Description:
 libqt5qevercloud3 - Unofficial Evernote Cloud API library for Qt5
 qevercloud-doc - QEverCloud library documentation
 qt5qevercloud-dev - Development files for libqt5qevercloud
Closes: 871202
Changes:
 qevercloud (3.0.3+ds-3) unstable; urgency=medium
 .
   * d/patches: refresh patch 0003 to fix FTBFS with gcc-7.
 (Closes: #871202)
   * d/control: bump Standards-Version to 4.0.1 (no changes needed)
   * d/control: remove Qt4-related package for upcoming Qt4 removal.
   * d/rules: review and remove Qt4 related instructions.
Checksums-Sha1:
 77dc31b377b73cb50703c08995700114be6532f0 1942 qevercloud_3.0.3+ds-3.dsc
 a4618969fa7dc9af65ca475b7267e05591b3bce6 6928 
qevercloud_3.0.3+ds-3.debian.tar.xz
 72c4f8bbcd2223b3392fe68f4dc518f0eb8b6444 5999 
qevercloud_3.0.3+ds-3_source.buildinfo
Checksums-Sha256:
 94d6bb9f52f6201be44f56c40f2726fad87fa6d8e6ebb4b7f795c3c87a770fd2 1942 
qevercloud_3.0.3+ds-3.dsc
 ece11ace870b781c0e93c850f0c250cdf25a87a03835607f01ad89a0deddd6ba 6928 
qevercloud_3.0.3+ds-3.debian.tar.xz
 aa56e4a51183844bab0ac5ef4c142a0a726a82be603fb16917980571cf283920 5999 
qevercloud_3.0.3+ds-3_source.buildinfo
Files:
 a5630cd8bd5e8740591897f7296dffa6 1942 libs optional qevercloud_3.0.3+ds-3.dsc
 3d512d0c0b897396e5019e675a7b62aa 6928 libs optional 
qevercloud_3.0.3+ds-3.debian.tar.xz
 64e6f6ae321288a08a9d1085b729dcb9 5999 libs optional 
qevercloud_3.0.3+ds-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE/Zzi2Nd1S3irJ5u9LDtDb+rGgQEFAlmXkcAACgkQLDtDb+rG
gQER7ggAms4xK3x2sblvXkoL8hYwBGGFlwvkTCh6W8intgGa0jUm1xiaUxVx+H8V

Bug#872586: drumgizmo: FTBFS on several arches because of test failures

[James Cowgill]

Hi,

On 18/08/17 21:32, Jeremy Bicha wrote:
> Source: drumgizmo
> Version: 0.9.14-2
> Severity: serious
> 
> drumgizmo fails to build from source on several release architectures
> that it used to build on because of test failures.
> 
> https://buildd.debian.org/status/package.php?p=drumgizmo

The attached patch does not fix all the test failures, but does fix the
3 affecting mips, and this should be enough to fix armel and mipsel as
well. Things are still broken on mips64el and s390x after this.

src/atomic.h:
This fixes enginetest by removing the assertion. My guess is that the
writer of the code meant to say "does this atomic use the std::atomic
implementation" (as opposed to the other implementation in src/atomic.h)
but instead said "is this atomic lock free" assuming that all
std::atomics are always lock free...

test/atomictest.cc:
Fixes atomictest by removing the test for lock free atomics. One some
architectures isLockFree may legitimately return false (eg it is
impossible to make atomic lock free on 32-bit mips). The test
was probably added with the same assumption as above.

plugingui/image.cc:
Fixes imagecachetest. The original code was not big-endian safe. Replace
the memcpy with shifts and ORs.

Thanks,
James
--- a/src/atomic.h
+++ b/src/atomic.h
@@ -151,8 +151,6 @@ public:
 	SettingRef(Atomic& value)
 		: value(value)
 	{
-		// string isn't lock free either
-		assert((std::is_same::value || value.is_lock_free()));
 	}
 
 	bool hasChanged()
--- a/test/atomictest.cc
+++ b/test/atomictest.cc
@@ -40,7 +40,6 @@ class AtomicTest
 	CPPUNIT_TEST(nonPodAtomicCanBeValueInitialized);
 	CPPUNIT_TEST(podAtomicCanBeValueAssigned);
 	CPPUNIT_TEST(nonPodAtomicCanBeValueAssigned);
-	CPPUNIT_TEST(podAtomicsAreLockFree);
 	CPPUNIT_TEST_SUITE_END();
 	
 	public:
@@ -99,23 +98,6 @@ class AtomicTest
 			CPPUNIT_ASSERT_EQUAL(s.load(), std::string{"hello world"});
 		}
 		
-		void podAtomicsAreLockFree() {
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			
-			// compile error: undefined reference to `__atomic_is_lock_free'
-			//CPPUNIT_ASSERT(isLockFree());
-		}
-		
 		// todo: further testing
 		
 	private:
@@ -123,12 +105,6 @@ class AtomicTest
 		bool isUsingStandardImpl() {
 			return std::is_base_of::value;
 		}
-		
-		template 
-		bool isLockFree() {
-			Atomic a;
-			return a.is_lock_free();
-		}
 };
 
 // Registers the fixture into the 'registry'
--- a/plugingui/image.cc
+++ b/plugingui/image.cc
@@ -86,10 +86,16 @@ void Image::setError()
 
 	std::uint32_t iw, ih;
 
-	std::memcpy(, ptr, sizeof(uint32_t));
+	iw = (uint32_t) ptr[0] |
+	 (uint32_t) ptr[1] << 8 |
+	 (uint32_t) ptr[2] << 16 |
+	 (uint32_t) ptr[3] << 24;
 	ptr += sizeof(uint32_t);
 
-	std::memcpy(, ptr, sizeof(uint32_t));
+	ih = (uint32_t) ptr[0] |
+	 (uint32_t) ptr[1] << 8 |
+	 (uint32_t) ptr[2] << 16 |
+	 (uint32_t) ptr[3] << 24;
 	ptr += sizeof(uint32_t);
 
 	_width = iw;


signature.asc
Description: OpenPGP digital signature

Bug#872595: calibre: please use system libmspack instead of embedded copy

[duck]

Source: calibre
Version: 3.4.0+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-CC: t...@security.debian.org


Quack,

Sorry for the bad news, but Calibre embed a very old version of 
libmspack to build a plugin: /usr/lib/calibre/calibre/plugins/lzx.so


Unfortunately, this library had a few security issues over time, and 
recently:

  https://security-tracker.debian.org/tracker/source-package/libmspack

So this means Calibre is affected (all versions is Debian) by these two 
security bugs and probably other older ones. The proper solution would 
be to use the libmspack library which has been fixed with all the fixes 
backported to stable and oldstable.


It is defined in 'setup/extensions.json' but I have no idea how to make 
it use the system library so I have no patch to suggest.


Btw it seems 'src/calibre/utils/' contains a lot of borrowed code which 
might lead to security problems too, so I would suggest to have a look 
and work things out with upstream to at least have build flags to use 
system libraries when available.


Regards.

--
Marc Dequènes

Bug#853535: marked as done (mame: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 19 Aug 2017 01:18:07 +0300
with message-id <20170818221807.hxjwhyc6ksag46ql@localhost>
and subject line mame 0.188+dfsg.1-1 builds with gcc 7
has caused the Debian Bug report #853535,
regarding mame: 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.)


-- 
853535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mame
Version: 0.182-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/mame_0.182-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

[...]
Compiling src/osd/modules/sound/direct_sound.cpp...
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g0 -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -MMD -MP -MP -DPTR64=1 
-DNDEBUG -DCRLF=2 -DLSB_FIRST -DXMD_H -DFLAC__NO_DLL -DNATIVE_DRC=drcbe_x64 
-DLUA_COMPAT_ALL -DLUA_COMPAT_5_1 -DLUA_COMPAT_5_2 -DNO_AFFINITY_NP 
-DUSE_NETWORK -DOSD_NET_USE_TAPTUN -D'INI_PATH="/etc/mame"' -DSDLMAME_X11 
-DUSE_XINPUT=0 -DSDLMAME_SDL2=1 -DOSD_SDL -DSDLMAME_UNIX -DUSE_OPENGL=1 
-D__STDC_LIMIT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_CONSTANT_MACROS 
-DIMGUI_DISABLE_OBSOLETE_FUNCTIONS -DUSE_QTDEBUG=1 -I/usr/X11/include 
-I/usr/X11R6/include -I/usr/openwin/include 
-I../../../../../3rdparty/asio/include 
-I../../../../../3rdparty/bgfx/examples/common 
-I../../../../../3rdparty/bgfx/include -I../../../../../3rdparty/bgfx/3rdparty 
-I../../../../../3rdparty/bx/include -I../../../../../3rdpart
 y/rapidjson/include -I../../../../../scripts/src/osd -I../../../../../src/emu 
-I../../../../../src/devices -I../../../../../src/osd -I../../../../../src/lib 
-I../../../../../src/lib/util -I../../../../../src/osd/modules/file 
-I../../../../../src/osd/modules/render -I../../../../../3rdparty 
-I../../../../../src/osd/sdl   -m64 -pipe -Wno-deprecated-declarations -O3 
-fno-strict-aliasing -Wno-unknown-pragmas -Wall -Wcast-align -Wundef 
-Wformat-security -Wwrite-strings -Wno-sign-compare -Wno-conversion 
-Wno-unused-result -Wno-array-bounds -m64 -I/usr/include/alsa -D_REENTRANT 
-I/usr/include/SDL2 -I/usr/include/freetype2 
-I/usr/include/x86_64-linux-gnu/qt5 -x c++ -std=c++14 -Woverloaded-virtual 
-include /<>/src/osd/sdl/sdlprefix.h -o 
"../../../../linux_gcc/obj/x64/Release/osd_sdl/src/osd/modules/sound/direct_sound.o"
 -c "../../../../../src/osd/modules/sound/direct_sound.cpp"
Compiling src/osd/modules/sound/js_sound.cpp...
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g0 -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -MMD -MP -MP -DPTR64=1 
-DNDEBUG -DCRLF=2 -DLSB_FIRST -DXMD_H -DFLAC__NO_DLL -DNATIVE_DRC=drcbe_x64 
-DLUA_COMPAT_ALL -DLUA_COMPAT_5_1 -DLUA_COMPAT_5_2 -DNO_AFFINITY_NP 
-DUSE_NETWORK -DOSD_NET_USE_TAPTUN -D'INI_PATH="/etc/mame"' -DSDLMAME_X11 
-DUSE_XINPUT=0 -DSDLMAME_SDL2=1 -DOSD_SDL -DSDLMAME_UNIX -DUSE_OPENGL=1 
-D__STDC_LIMIT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_CONSTANT_MACROS 
-DIMGUI_DISABLE_OBSOLETE_FUNCTIONS -DUSE_QTDEBUG=1 -I/usr/X11/include 
-I/usr/X11R6/include -I/usr/openwin/include 
-I../../../../../3rdparty/asio/include 
-I../../../../../3rdparty/bgfx/examples/common 
-I../../../../../3rdparty/bgfx/include 

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 853310 src:android-platform-system-core
Bug #853310 [src:android-platform-build] android-platform-build: ftbfs with 
GCC-7
Bug reassigned from package 'src:android-platform-build' to 
'src:android-platform-system-core'.
No longer marked as found in versions android-platform-build/1:7.0.0+r1-2.
Ignoring request to alter fixed versions of bug #853310 to the same values 
previously set
> reassign 853311 src:android-platform-system-core
Bug #853311 [src:android-platform-frameworks-base] 
android-platform-frameworks-base: ftbfs with GCC-7
Bug reassigned from package 'src:android-platform-frameworks-base' to 
'src:android-platform-system-core'.
No longer marked as found in versions 
android-platform-frameworks-base/1:7.0.0+r1-2.
Ignoring request to alter fixed versions of bug #853311 to the same values 
previously set
> forcemerge 853312 853310 853311
Bug #853312 [src:android-platform-system-core] android-platform-system-core: 
ftbfs with GCC-7
Bug #853310 [src:android-platform-system-core] android-platform-build: ftbfs 
with GCC-7
Marked as found in versions android-platform-system-core/1:7.0.0+r1-2.
Bug #853311 [src:android-platform-system-core] 
android-platform-frameworks-base: ftbfs with GCC-7
Marked as found in versions android-platform-system-core/1:7.0.0+r1-2.
Merged 853310 853311 853312
> affects 853310 src:android-platform-build src:android-platform-frameworks-base
Bug #853310 [src:android-platform-system-core] android-platform-build: ftbfs 
with GCC-7
Bug #853311 [src:android-platform-system-core] 
android-platform-frameworks-base: ftbfs with GCC-7
Bug #853312 [src:android-platform-system-core] android-platform-system-core: 
ftbfs with GCC-7
Added indication that 853310 affects src:android-platform-build and 
src:android-platform-frameworks-base
Added indication that 853311 affects src:android-platform-build and 
src:android-platform-frameworks-base
Added indication that 853312 affects src:android-platform-build and 
src:android-platform-frameworks-base
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
853310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853310
853311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853311
853312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871218: marked as done (alien-arena: FTBFS with GCC-7: undefined reference to `IQM_DrawVBO')

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 22:04:23 +
with message-id 
and subject line Bug#871218: fixed in alien-arena 7.66+dfsg-4
has caused the Debian Bug report #871218,
regarding alien-arena: FTBFS with GCC-7: undefined reference to `IQM_DrawVBO'
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.)


-- 
871218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alien-arena
Version: 7.66+dfsg-3
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

alien-arena FTBFS since GCC-7 was made the default compiler:

gcc  -g -O2 -fdebug-prefix-map=/build/alien-arena-7.66+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -ffast-math 
-fno-strict-aliasing  -Wl,-z,relro -Wl,-z,now -o alienarena 
client/alienarena-cl_ents.o client/alienarena-cl_fx.o 
client/alienarena-cl_http.o client/alienarena-cl_input.o 
client/alienarena-cl_inv.o client/alienarena-cl_irc.o 
client/alienarena-cl_main.o client/alienarena-cl_parse.o 
client/alienarena-cl_pred.o client/alienarena-cl_scrn.o 
client/alienarena-cl_stats.o client/alienarena-cl_updates.o 
client/alienarena-cl_tent.o client/alienarena-cl_view.o 
client/alienarena-console.o client/alienarena-keys.o client/alienarena-menu.o 
client/alienarena-qal.o client/alienarena-qmenu.o client/alienarena-snd_file.o 
client/alienarena-snd_openal.o game/alienarena-q_shared.o 
qcommon/alienarena-cmd.o qcommon/alienarena-cmodel.o 
qcommon/alienarena-common.o qcommon/alienarena-crc.o qcommon/alienarena-cvar.o 
qcommon/alienarena-files.o qcommon/alienarena-htable.o qcommon/al
 ienarena-md5.o qcommon/alienarena-mdfour.o qcommon/alienarena-net_chan.o 
qcommon/alienarena-pmove.o ref_gl/alienarena-r_bloom.o 
ref_gl/alienarena-r_draw.o ref_gl/alienarena-r_image.o 
ref_gl/alienarena-r_iqm.o ref_gl/alienarena-r_light.o 
ref_gl/alienarena-r_main.o ref_gl/alienarena-r_math.o 
ref_gl/alienarena-r_mesh.o ref_gl/alienarena-r_misc.o 
ref_gl/alienarena-r_model.o ref_gl/alienarena-r_particle.o 
ref_gl/alienarena-r_postprocess.o ref_gl/alienarena-r_program.o 
ref_gl/alienarena-r_ragdoll.o ref_gl/alienarena-r_script.o 
ref_gl/alienarena-r_shadowmaps.o ref_gl/alienarena-r_shadows.o 
ref_gl/alienarena-r_surf.o ref_gl/alienarena-r_text.o ref_gl/alienarena-r_ttf.o 
ref_gl/alienarena-r_varray.o ref_gl/alienarena-r_vbo.o 
ref_gl/alienarena-r_vlights.o ref_gl/alienarena-r_warp.o 
server/alienarena-sv_ccmds.o server/alienarena-sv_ents.o 
server/alienarena-sv_game.o server/alienarena-sv_init.o 
server/alienarena-sv_main.o server/alienarena-sv_send.o 
server/alienarena-sv_user.o server/alienarena-
 sv_world.o unix/alienarena-glob.o unix/alienarena-gl_glx.o 
unix/alienarena-net_udp.o unix/alienarena-qal_unix.o unix/alienarena-qgl_unix.o 
unix/alienarena-q_shunix.o unix/alienarena-rw_unix.o unix/alienarena-sys_unix.o 
unix/alienarena-vid_so.o  libgame.a libode.a -pthread -lX11 -lcurl -logg 
-lvorbis -lvorbisfile -lfreetype -lXxf86vm  -lz -lstdc++  -ljpeg -ldl -lm 
ref_gl/alienarena-r_iqm.o: In function `IQM_DrawFrame':
./source/ref_gl/r_iqm.c:1586: undefined reference to `IQM_DrawVBO'
collect2: error: ld returned 1 exit status
Makefile:1689: recipe for target 'alienarena' failed
make[2]: *** [alienarena] Error 1


Andreas


alien-arena_7.66+dfsg-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: alien-arena
Source-Version: 7.66+dfsg-4

We believe that the bug you reported is fixed in the latest version of
alien-arena, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated alien-arena package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 Aug 2017 23:35:09 +0200
Source: alien-arena
Binary: alien-arena alien-arena-server
Architecture: source
Version: 7.66+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 853543 libmpich-dev
Bug #853543 {Done: Thorsten Alteholz } [src:meep-mpich2] 
meep-mpich2: ftbfs with GCC-7
Bug reassigned from package 'src:meep-mpich2' to 'libmpich-dev'.
No longer marked as found in versions meep-mpich2/1.3-4.
No longer marked as fixed in versions 1.3-4.
> forcemerge 853324 853543
Bug #853324 {Done: Alastair McKinstry } [libmpich-dev] 
libmpich-dev: drop the gcc version check in mpicxx.h
Bug #853404 {Done: Alastair McKinstry } [libmpich-dev] 
libmpich-dev: drop the gcc version check in mpicxx.h
Bug #853532 {Done: Alastair McKinstry } [libmpich-dev] 
libmpich-dev: drop the gcc version check in mpicxx.h
Bug #853562 {Done: Alastair McKinstry } [libmpich-dev] 
libmpich-dev: drop the gcc version check in mpicxx.h
Bug #853562 {Done: Alastair McKinstry } [libmpich-dev] 
libmpich-dev: drop the gcc version check in mpicxx.h
Removed indication that 853562 affects src:bagel, src:madness, src:form, and 
src:mpqc3
Added indication that 853562 affects src:form,src:bagel,src:mpqc3,src:madness
Removed indication that 853324 affects src:bagel, src:madness, src:form, and 
src:mpqc3
Added indication that 853324 affects src:form,src:bagel,src:mpqc3,src:madness
Removed indication that 853404 affects src:bagel, src:madness, src:form, and 
src:mpqc3
Added indication that 853404 affects src:form,src:bagel,src:mpqc3,src:madness
Removed indication that 853532 affects src:mpqc3, src:madness, src:form, and 
src:bagel
Added indication that 853532 affects src:form,src:bagel,src:mpqc3,src:madness
Bug #853543 {Done: Thorsten Alteholz } [libmpich-dev] 
meep-mpich2: ftbfs with GCC-7
Added indication that 853543 affects src:form,src:bagel,src:mpqc3,src:madness
Marked as fixed in versions mpich/3.3~a2-2.
Added tag(s) patch.
Bug #853404 {Done: Alastair McKinstry } [libmpich-dev] 
libmpich-dev: drop the gcc version check in mpicxx.h
Bug #853532 {Done: Alastair McKinstry } [libmpich-dev] 
libmpich-dev: drop the gcc version check in mpicxx.h
Merged 853324 853404 853532 853543 853562
> affects 853324 src:meep-mpich2
Bug #853324 {Done: Alastair McKinstry } [libmpich-dev] 
libmpich-dev: drop the gcc version check in mpicxx.h
Bug #853404 {Done: Alastair McKinstry } [libmpich-dev] 
libmpich-dev: drop the gcc version check in mpicxx.h
Bug #853532 {Done: Alastair McKinstry } [libmpich-dev] 
libmpich-dev: drop the gcc version check in mpicxx.h
Bug #853543 {Done: Thorsten Alteholz } [libmpich-dev] 
meep-mpich2: ftbfs with GCC-7
Bug #853562 {Done: Alastair McKinstry } [libmpich-dev] 
libmpich-dev: drop the gcc version check in mpicxx.h
Added indication that 853324 affects src:meep-mpich2
Added indication that 853404 affects src:meep-mpich2
Added indication that 853532 affects src:meep-mpich2
Added indication that 853543 affects src:meep-mpich2
Added indication that 853562 affects src:meep-mpich2
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
853324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853324
853404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853404
853532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853532
853543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853543
853562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853589: marked as done (openexr: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 19 Aug 2017 00:33:47 +0300
with message-id <20170818213347.imoahe3vaf36db4p@localhost>
and subject line openexr builds in unstable
has caused the Debian Bug report #853589,
regarding openexr: 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.)


-- 
853589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openexr
Version: 2.2.0-11
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/openexr_2.2.0-11_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

[...]
/usr/include/OpenEXR/ImathVec.h:842:35: warning: dynamic exception 
specifications are deprecated in C++11; use 'noexcept' instead [-Wdeprecated]
 Vec4::normalizedExc () const throw (IEX_NAMESPACE::MathExc);
   ^
/usr/include/OpenEXR/ImathVec.h:1212:26: warning: dynamic exception 
specifications are deprecated in C++11; use 'noexcept' instead [-Wdeprecated]
 Vec2::normalizeExc () throw (IEX_NAMESPACE::MathExc)
  ^
/usr/include/OpenEXR/ImathVec.h:1249:33: warning: dynamic exception 
specifications are deprecated in C++11; use 'noexcept' instead [-Wdeprecated]
 Vec2::normalizedExc () const throw (IEX_NAMESPACE::MathExc)
 ^
/usr/include/OpenEXR/ImathVec.h:1704:26: warning: dynamic exception 
specifications are deprecated in C++11; use 'noexcept' instead [-Wdeprecated]
 Vec3::normalizeExc () throw (IEX_NAMESPACE::MathExc)
  ^
/usr/include/OpenEXR/ImathVec.h:1743:33: warning: dynamic exception 
specifications are deprecated in C++11; use 'noexcept' instead [-Wdeprecated]
 Vec3::normalizedExc () const throw (IEX_NAMESPACE::MathExc)
 ^
/usr/include/OpenEXR/ImathVec.h:2109:26: warning: dynamic exception 
specifications are deprecated in C++11; use 'noexcept' instead [-Wdeprecated]
 Vec4::normalizeExc () throw (IEX_NAMESPACE::MathExc)
  ^
/usr/include/OpenEXR/ImathVec.h:2150:33: warning: dynamic exception 
specifications are deprecated in C++11; use 'noexcept' instead [-Wdeprecated]
 Vec4::normalizedExc () const throw (IEX_NAMESPACE::MathExc)
 ^
In file included from ImfFlatImageChannel.cpp:41:0:
ImfFlatImageChannel.h: In member function 'virtual void 
Imf_2_2::TypedFlatImageChannel::resetBasePointer()':
ImfFlatImageChannel.h:324:19: error: invalid use of incomplete type 'class 
Imf_2_2::ImageLevel'
 (level().dataWindow().min.y / ySampling()) * pixelsPerRow() -
  ~^~
In file included from ImfFlatImageChannel.h:48:0,
 from ImfFlatImageChannel.cpp:41:
./ImfImageChannel.h:56:7: note: forward declaration of 'class 
Imf_2_2::ImageLevel'
 class ImageLevel;
   ^~
In file included from ImfFlatImageChannel.cpp:41:0:
ImfFlatImageChannel.h:325:19: error: invalid use of incomplete type 'class 
Imf_2_2::ImageLevel'
 (level().dataWindow().min.x / xSampling());
  ~^~
In file included from ImfFlatImageChannel.h:48:0,
 from ImfFlatImageChannel.cpp:41:
./ImfImageChannel.h:56:7: note: forward declaration of 'class 
Imf_2_2::ImageLevel'
 class ImageLevel;
   ^~
Makefile:512: recipe for target 'ImfFlatImageChannel.lo' failed
make[2]: *** [ImfFlatImageChannel.lo] Error 1
make[2]: Leaving directory '/<>/IlmImfUtil'
Makefile:498: 

Bug#853715: yrmcds: ftbfs with GCC-7

[Nobuhiro Iwamatsu]

Hi,

> Package: src:yrmcds
> Version: 1.1.8-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/yrmcds_1.1.8-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.

This problem fixed in upstream repository.
  
https://github.com/cybozu/yrmcds/commit/a7026e02da4fcc6d0260dfa49649446158147015

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#853639: marked as done (regina-normal: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 21:12:09 +
with message-id 
and subject line Bug#853639: fixed in regina-normal 5.1-2
has caused the Debian Bug report #853639,
regarding regina-normal: 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.)


-- 
853639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:regina-normal
Version: 5.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/regina-normal_5.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

[...]
make[3]: Leaving directory '/<>/builds/debbuild'
/usr/bin/make -f engine/CMakeFiles/regina-engine.dir/build.make 
engine/CMakeFiles/regina-engine.dir/build
make[3]: Entering directory '/<>/builds/debbuild'
[  0%] Building CXX object engine/CMakeFiles/regina-engine.dir/engine.cpp.o
cd /<>/builds/debbuild/engine && /usr/bin/c++   
-DREGINA_DLL_EXPORTS=1 -Dregina_engine_EXPORTS 
-I/<>/builds/debbuild/engine -I/<>/engine 
-I/usr/include/libxml2 -I/usr/include/x86_64-linux-gnu  -pthread  -std=c++11 
-O3 -DNDEBUG -fPIC   -o CMakeFiles/regina-engine.dir/engine.cpp.o -c 
/<>/engine/engine.cpp
[  0%] Building CXX object 
engine/CMakeFiles/regina-engine.dir/algebra/abeliangroup.cpp.o
cd /<>/builds/debbuild/engine && /usr/bin/c++   
-DREGINA_DLL_EXPORTS=1 -Dregina_engine_EXPORTS 
-I/<>/builds/debbuild/engine -I/<>/engine 
-I/usr/include/libxml2 -I/usr/include/x86_64-linux-gnu  -pthread  -std=c++11 
-O3 -DNDEBUG -fPIC   -o CMakeFiles/regina-engine.dir/algebra/abeliangroup.cpp.o 
-c /<>/engine/algebra/abeliangroup.cpp
[  0%] Building CXX object 
engine/CMakeFiles/regina-engine.dir/algebra/grouppresentation.cpp.o
cd /<>/builds/debbuild/engine && /usr/bin/c++   
-DREGINA_DLL_EXPORTS=1 -Dregina_engine_EXPORTS 
-I/<>/builds/debbuild/engine -I/<>/engine 
-I/usr/include/libxml2 -I/usr/include/x86_64-linux-gnu  -pthread  -std=c++11 
-O3 -DNDEBUG -fPIC   -o 
CMakeFiles/regina-engine.dir/algebra/grouppresentation.cpp.o -c 
/<>/engine/algebra/grouppresentation.cpp
[  1%] Building CXX object 
engine/CMakeFiles/regina-engine.dir/algebra/homgrouppresentation.cpp.o
cd /<>/builds/debbuild/engine && /usr/bin/c++   
-DREGINA_DLL_EXPORTS=1 -Dregina_engine_EXPORTS 
-I/<>/builds/debbuild/engine -I/<>/engine 
-I/usr/include/libxml2 -I/usr/include/x86_64-linux-gnu  -pthread  -std=c++11 
-O3 -DNDEBUG -fPIC   -o 
CMakeFiles/regina-engine.dir/algebra/homgrouppresentation.cpp.o -c 
/<>/engine/algebra/homgrouppresentation.cpp
[  1%] Building CXX object 
engine/CMakeFiles/regina-engine.dir/algebra/markedabeliangroup.cpp.o
cd /<>/builds/debbuild/engine && /usr/bin/c++   
-DREGINA_DLL_EXPORTS=1 -Dregina_engine_EXPORTS 
-I/<>/builds/debbuild/engine -I/<>/engine 
-I/usr/include/libxml2 -I/usr/include/x86_64-linux-gnu  -pthread  -std=c++11 
-O3 -DNDEBUG -fPIC   -o 
CMakeFiles/regina-engine.dir/algebra/markedabeliangroup.cpp.o -c 
/<>/engine/algebra/markedabeliangroup.cpp
[  1%] Building CXX object 
engine/CMakeFiles/regina-engine.dir/algebra/xmlalgebrareader.cpp.o
cd /<>/builds/debbuild/engine && /usr/bin/c++   
-DREGINA_DLL_EXPORTS=1 -Dregina_engine_EXPORTS 
-I/<>/builds/debbuild/engine -I/<>/engine 
-I/usr/include/libxml2 -I/usr/include/x86_64-linux-gnu  -pthread  -std=c++11 
-O3 -DNDEBUG -fPIC   -o 
CMakeFiles/regina-engine.dir/algebra/xmlalgebrareader.cpp.o -c 
/<>/engine/algebra/xmlalgebrareader.cpp
[  1%] Building CXX object 

Bug#871293: marked as done (libplb1: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 21:09:36 +
with message-id 
and subject line Bug#871293: fixed in palabos 1.5~r1+repack1-3
has caused the Debian Bug report #871293,
regarding libplb1: requires rebuild against GCC 7 and symbols/shlibs bump
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.)


-- 
871293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libplb1
Version: 1.5~r1+repack1-2
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-op-mangling

Hi,

It appears that your package provides an external symbol that is
affected by the recent name mangling changes in GCC 7. See:
https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling

In GCC 7, the name mangling for C++ conversion operators which return a
type using the abi_tag attribute (most commonly std::string) has
changed. When your library is compiled with GCC 7, it will now emit two
symbols for the conversion operator using the new and old naming.
Executables compiled with GCC 7 will always use the new symbol, while
old executables compiled using <= GCC 6 will use the old symbol. For new
executables to build without undefined references, your library will
need rebuilding with GCC 7.

To ensure that new executables will pull in the newer version of the
library built with GCC 7:
- Your library package should Build-Depend on g++ (>= 4:7).
- If your package provides a symbols file, ensure that the new
  conversion operator symbols have a version matching the version this
  bug is fixed in (including the Debian revision and tilde if
  necessary).

  Using apt as an example (debian/libapt-pkg5.0.symbols):
(c++)"URI::operator std::__cxx11::basic_string[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string()@APTPKG_5.0" 1.5~beta2~

  Where "1.5~beta2" is the version this bug was fixed in.

- If your package does not provide a symbols file, add a dh_makeshlibs
  override so that tight enough dependencies are generated.

  Using libebml as an example (debian/rules):
  + override_dh_makeshlibs:
  + # For new symbols when compiled with GCC 7
  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'

  Where "1.3.4-2" is the version this bug was fixed in.

- If your package is about to be renamed due to an upstream SONAME bump,
  you do not need to add any special symbols handling.

If you would like to know the exact name of the new symbols, using
"abipkgdiff" from abigail-tools might be able to help.

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: palabos
Source-Version: 1.5~r1+repack1-3

We believe that the bug you reported is fixed in the latest version of
palabos, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated palabos package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 Aug 2017 21:54:34 +0200
Source: palabos
Binary: libplb-dev libplb-doc libplb1
Architecture: source
Version: 1.5~r1+repack1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 libplb-dev - CFD solver based on the lattice Boltzmann method. Development fil
 libplb-doc - CFD solver based on the lattice Boltzmann method. Documentation
 libplb1- CFD solver based on the lattice Boltzmann method. Shared library
Closes: 871293
Changes:
 palabos (1.5~r1+repack1-3) unstable; urgency=medium
 .
   * [0987caf] Use compat level 10
   * [d3044c7] Apply cme fix dpkg
   * [7c84c9b] Remove dbg-package
   * [b74c6cc] Rebuild with GCC 7 to fix FTBFS of reverse dependencies.
   (Closes: #871293)
Checksums-Sha1:
 7b57af1641aa9d6322617900c5f719116e2547e2 2245 palabos_1.5~r1+repack1-3.dsc
 6447f2fce39ec8b177640079773e5bf0a10db5b0 20184 
palabos_1.5~r1+repack1-3.debian.tar.xz

Bug#871409: marked as done (libio-socket-ssl-perl: FTBFS: t/protocol_version.t failure)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 21:09:03 +
with message-id 
and subject line Bug#871409: fixed in libio-socket-ssl-perl 2.050-1
has caused the Debian Bug report #871409,
regarding libio-socket-ssl-perl: FTBFS: t/protocol_version.t failure
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.)


-- 
871409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libio-socket-ssl-perl
Version: 2.049-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest

As noticed by ci.debian.net:

 https://ci.debian.net/packages/libi/libio-socket-ssl-perl/unstable/amd64/

this package fails to build on current sid/amd64. debci.log indicates
this is fallout from openssl disabling TLS 1.0 and 1.1 recently:

 -openssl 1.1.0f-3
 +openssl 1.1.0f-4

See https://lists.debian.org/debian-devel-announce/2017/08/msg4.html

>From the build log:


  # looks like OpenSSL was compiled without SSLv3 support
  
  #   Failed test 'accept TLSv1'
  #   at t/protocol_version.t line 125.
  
  #   Failed test 'accept SSLv23:!TLSv1_2:!TLSv1_1'
  #   at t/protocol_version.t line 125.
  
  #   Failed test 'accept TLSv1_1'
  #   at t/protocol_version.t line 125.
  
  #   Failed test 'accept SSLv23:!TLSv1_2'
  #   at t/protocol_version.t line 125.
  # Looks like you failed 4 tests of 7.
  t/protocol_version.t .. 
  ok 1 - accept SSLv23 with any, got TLSv1_2
  not ok 2 - accept TLSv1
  not ok 3 - accept SSLv23:!TLSv1_2:!TLSv1_1
  not ok 4 - accept TLSv1_1
  not ok 5 - accept SSLv23:!TLSv1_2
  ok 6 - accept TLSv1_2 with TLSv1_2
  ok 7 - accept SSLv23 with TLSv1_2
  1..7
  Dubious, test returned 4 (wstat 1024, 0x400)
  Failed 4/7 subtests 
  [...]
  Test Summary Report
  ---
  t/protocol_version.t(Wstat: 1024 Tests: 7 Failed: 4)
Failed tests:  2-5
Non-zero exit status: 4
  t/sessions.t(Wstat: 256 Tests: 11 Failed: 1)
Failed test:  10
Non-zero exit status: 1
Parse errors: Bad plan.  You planned 35 tests but ran 11.
  Files=36, Tests=747, 42 wallclock secs ( 0.27 usr  0.04 sys +  7.04 cusr  
0.73 csys =  8.08 CPU)
  Result: FAIL
 
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libio-socket-ssl-perl
Source-Version: 2.050-1

We believe that the bug you reported is fixed in the latest version of
libio-socket-ssl-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated 
libio-socket-ssl-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 Aug 2017 21:46:12 +0200
Source: libio-socket-ssl-perl
Binary: libio-socket-ssl-perl
Architecture: source
Version: 2.050-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Salvatore Bonaccorso 
Closes: 871409
Description: 
 libio-socket-ssl-perl - Perl module implementing object oriented interface to 
SSL sockets
Changes:
 libio-socket-ssl-perl (2.050-1) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Disable network tests during autopkgtests like during build.
 .
   [ Salvatore Bonaccorso ]
   * Import upstream version 2.050
 - protocol_version.t can now deal when TLS 1.0 and/or TLS 1.1 are not
   supported. Fixes "FTBFS: t/protocol_version.t failure".
   (Closes: #871409)
   * Declare compliance with Debian policy 4.0.1
Checksums-Sha1: 
 738810da572db58624e7d208b6384dce47e3f2f1 2696 libio-socket-ssl-perl_2.050-1.dsc
 8597a676e78234b850605249f35058fb8e074749 220409 
libio-socket-ssl-perl_2.050.orig.tar.gz
 d76cc644976925747ead7aa09d4de56b3a68d69e 9608 
libio-socket-ssl-perl_2.050-1.debian.tar.xz
Checksums-Sha256: 
 a5796c3bd41bffd40edc74b0286d1c6ed602034480f2438e7ae2777112021c6c 2696 
libio-socket-ssl-perl_2.050-1.dsc
 54e6716e40df8b1c168d8f54a0b8f215313739bd99dda17adb7c00fe94656692 220409 
libio-socket-ssl-perl_2.050.orig.tar.gz
 

Bug#872525: [pkg-gnupg-maint] Bug#872525: debian-archive-keyring FTBFS with gnupg 2.1.23

[Adam D. Barratt]

[CC += 870780]

On Fri, 2017-08-18 at 03:46 -0400, Daniel Kahn Gillmor wrote:
> On Fri 2017-08-18 10:02:49 +0300, Adrian Bunk wrote:
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debian-archive-keyring.html
> >
> > ...
> > gpg --no-options --no-default-keyring --no-auto-check-trustdb 
> > --trustdb-name ./trustdb.gpg \
> > --keyring keyrings/team-members.gpg --verify \
> > keyrings/debian-archive-keyring.gpg.asc \
> > keyrings/debian-archive-keyring.gpg
> > gpg: Signature made Thu May 25 06:30:03 2017 -12
> > gpg:using RSA key C5CE5DC2C542CD59
> > gpg: BAD signature from "Adam D. Barratt " 
> > [unknown]
[...]
> The difference between the keyrings is the trust packets:
[...]
> This is happening because of a combination of several factors:
> 
> One of them is https://bugs.debian.org/870780 -- the
> debian-archive-keyring really shouldn't have OpenPGP trust packets in it
> in the first place.  Those are deliberately underspecified and
> vendor-specific:
[...]
> The larger problem here is that jetring (and debian-archive-keyring, and
> anything else which uses jetring) seems to assume some things about what
> GnuPG does with the contents of ~/.gnupg.
[...]
> If #870780 was resolved (perhaps by fixing jetring to use GnuPG's
> external interfaces?) and a new debian-archive-keyring.gpg.asc was
> created by Adam (or some other member of the team) then i think this
> problem would go away.

As discussed on IRC, I think the fundamental fix here needs to be in
jetring. In the short term, however, we could resolve the issue in d-a-k
in one of two ways.

1. Have the rules that generate the keyrings clean them afterwards. For
example, changing:

keyrings/debian-archive-keyring.gpg: active-keys/index
jetring-build -I $@ active-keys

to

keyrings/debian-archive-keyring.gpg: active-keys/index
jetring-build -I $@ active-keys
gpg --import-options import-export --import < $@ > $@.tmp
mv -f $@.tmp $@

and similarly for the removed keyring. (and maybe for the trusted.gpg.d
files as well?)

2. Add the manual equivalent of the above to the "pre-build" section of
README.maintainer, leaving the package creating crufty files and the
responsibility of cleaning them up resting with the person generating
the package.

Particularly if we want/need to clean up the trusted.gpg.d files as
well, I'm inclined towards option 1, even if it does mean a small bit of
repetition in the makefile.

Regards,

Adam

Bug#872586: drumgizmo: FTBFS on several arches because of test failures

[Jeremy Bicha]

Source: drumgizmo
Version: 0.9.14-2
Severity: serious

drumgizmo fails to build from source on several release architectures
that it used to build on because of test failures.

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

You can do something like the below snippet to ignore test failures on
some architectures but still have them be mandatory for the remaining
architectures.

override_dh_auto_test:
ifneq (,$(findstring
$(DEB_HOST_ARCH),"alpha","armel","hppa","mips","mips64el","powerpc","sparc64","s390x",))
-dh_auto_test
else
dh_auto_test
endif

Thanks,
Jeremy Bicha

Bug#872565: encfs: FTBFS on mips, mipsel: undefined reference to `__atomic_store_8'

[Eduard Bloch]

Hallo,
* James Cowgill [Fri, Aug 18 2017, 05:02:52PM]:
> Source: encfs
> Version: 1.9.2-1
> Severity: serious
> Tags: sid buster
> 
> Hi,
> 
> ensfc FTBFS on mips, mipsel and various ports architectures with the error:
> > libencfs.so.1.9.2: undefined reference to `__atomic_store_8'
> > libencfs.so.1.9.2: undefined reference to `__atomic_fetch_add_8'
> > collect2: error: ld returned 1 exit status
> 
> This happens because those architectures do not have native 64-bit
> atomic instructions and instead call out to libatomic to provide
> emulations of them. To allow linking on these architecture you must link
> against libatomic.
> 
> One option is to add the -latomic to LDFLAGS in the Debian package, or I
> could probably come up with a patch to be applied upstream which will
> link only on the architectures it's needed.
> 
> Note there is an upstream GCC bug about doing all this in the toolchain,
> but for the moment it has to be done per package:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358

Thank you. I will try to handcraft a patch for the build system itself
and push it upstream ASAP.

Reminds me on a similar problem with
https://buildd.debian.org/status/fetch.php?pkg=apt-cacher-ng=powerpc=3-5=1493319231=0
which is confusing, the current solution (detection of libatomic) was
successfull on mips and most other 32-bit arches. Needs a tougher
investigation, apparently.

Best regards,
Eduard.

Bug#872580: [node-evp-bytestokey] FTBFS with node v6

[Bastien ROUCARIÈS]

Package: node-evp-bytestokey
Version: 1.0.0-3
Severity: serious
forwarded: https://github.com/crypto-browserify/EVP_BytesToKey/issues/8

nodejs test.js 
TAP version 13
# password: password
ok 1 should be equal
# password: ふっかつ　あきる　すぶり　はやい　つける　まゆげ　たんさん　みんぞく　ねほりはほり　せまい　たいまつばな　ひはん
not ok 2 should be equal
  ---
operator: equal
expected: '96d23d45a6b1fe'
actual:   'e985b4ba0c84e2'
at: Test. (/home/bastien/Documents/Personnel/soft/debian/js/
node-evp-bytestokey/node-evp-bytestokey/test.js:13:7)
  ...
# password: Z͑ͫAͫ͗LͨͧG̑͗O͂̌!̿̋
not ok 3 should be equal
  ---
operator: equal
expected: 'fc960d2ad3186e'
actual:   '84190e0d926c7c'
at: Test. (/home/bastien/Documents/Personnel/soft/debian/js/
node-evp-bytestokey/node-evp-bytestokey/test.js:13:7)
  ...
# password: 
not ok 4 should be equal
  ---
operator: equal
expected: '01382ecc78e6ae'
actual:   '82282e0665da04'
at: Test. (/home/bastien/Documents/Personnel/soft/debian/js/
node-evp-bytestokey/node-evp-bytestokey/test.js:13:7)
  ...

1..4
# tests 4
# pass  1
# fail  3


signature.asc
Description: This is a digitally signed message part.

Bug#872438: [Pkg-javascript-devel] Bug#872438: Bug#872438: Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

[Jérémy Lal]

2017-08-18 20:38 GMT+02:00 Bastien ROUCARIES :

> On Fri, Aug 18, 2017 at 7:42 PM, Jérémy Lal  wrote:
> > James Cowgill replied this to my give back request on mip64el:
> >
> >> My guess is this GCC-7 bug which is breaking lots of stuff on mips64el
> >> at the moment:
> >> https://bugs.debian.org/871514
> >
> >> Thanks,
> >> James
> >
> > Cheers,
> >
> > Jérémy
>
> Thanks BTW why node has no debug symbols ?
>

Because
https://packages.debian.org/fr/sid/nodejs-dbgsym

Processed: severity of 870103 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 870103 important
Bug #870103 [freeplane] freeplane: a Java (knopflerfish) exception will prevent 
freeplane from starting
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
870103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871350: marked as done (erlang-cuttlefish: FTBFS: ERROR: OTP release 20 does not match required regex R16|17|18|19)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 19:04:19 +
with message-id 
and subject line Bug#871350: fixed in erlang-cuttlefish 2.0.11+dfsg-2
has caused the Debian Bug report #871350,
regarding erlang-cuttlefish: FTBFS: ERROR: OTP release 20 does not match 
required regex R16|17|18|19
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.)


-- 
871350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-cuttlefish
Version: 2.0.11+dfsg-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=rebar --with rebar
>dh_update_autotools_config -O--buildsystem=rebar
>dh_auto_configure -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> configure
> make[1]: Nothing to be done for 'configure'.
>dh_auto_build -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> build
> rebar_compile
> rebar compile skip_deps=true -vv
> DEBUG: Consult config file 
> "/<>/erlang-cuttlefish-2.0.11+dfsg/rebar.config"
> DEBUG: Rebar location: "/usr/bin/rebar"
> DEBUG: Consult config file 
> "/<>/erlang-cuttlefish-2.0.11+dfsg/src/cuttlefish.app.src"
> DEBUG: Available deps: []
> DEBUG: Missing deps  : []
> DEBUG: Plugins requested while processing 
> /<>/erlang-cuttlefish-2.0.11+dfsg: []
> DEBUG: Predirs: []
> ==> erlang-cuttlefish-2.0.11+dfsg (compile)
> DEBUG: Matched required ERTS version: 9.0.1 -> .*
> ERROR: OTP release 20 does not match required regex R16|17|18|19
> ERROR: compile failed while processing 
> /<>/erlang-cuttlefish-2.0.11+dfsg: rebar_abort
> /usr/share/dh-rebar/make/dh-rebar.Makefile:125: recipe for target 
> 'rebar_compile' failed
> make[1]: *** [rebar_compile] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2017/08/07/erlang-cuttlefish_2.0.11+dfsg-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: erlang-cuttlefish
Source-Version: 2.0.11+dfsg-2

We believe that the bug you reported is fixed in the latest version of
erlang-cuttlefish, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated erlang-cuttlefish 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 19 Aug 2017 03:11:02 +0900
Source: erlang-cuttlefish
Binary: erlang-cuttlefish
Architecture: source amd64
Version: 2.0.11+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: LeoFS maintainers team 
Changed-By: Nobuhiro Iwamatsu 
Description:
 erlang-cuttlefish - Erlang/OTP library for sysctl-like syntax
Closes: 871350
Changes:
 erlang-cuttlefish (2.0.11+dfsg-2) unstable; urgency=medium
 .
   * Fix build with OTP 20. (Closes: #871350)
 - Update patches/support_otp_19.
 - Add patches/remove-warnings_as_errors.
   * Bump Standards-Version to 4.0.0.
Checksums-Sha1:
 b1472aa601ea42e5680cacf840acb213674f0501 2204 
erlang-cuttlefish_2.0.11+dfsg-2.dsc
 711068b2f49da44b08927d627949e403763d232a 3632 
erlang-cuttlefish_2.0.11+dfsg-2.debian.tar.xz
 2a3dd59ac15b98dd1d3de09aaa79e7e0f7c08e9e 9346 
erlang-cuttlefish_2.0.11+dfsg-2_amd64.buildinfo
 5656a0331335707e12e4e43cccf0cf0bdbca2f38 151288 
erlang-cuttlefish_2.0.11+dfsg-2_amd64.deb
Checksums-Sha256:
 0de194b3b998e505a85561a77a564006348b287bda4da00ac4f054f40e254194 2204 

Bug#871295: marked as done (libhtmlcxx3v5: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 19:05:23 +
with message-id 
and subject line Bug#871295: fixed in htmlcxx 0.86-1.2
has caused the Debian Bug report #871295,
regarding libhtmlcxx3v5: requires rebuild against GCC 7 and symbols/shlibs bump
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.)


-- 
871295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhtmlcxx3v5
Version: 0.86-1.1
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-op-mangling

Hi,

It appears that your package provides an external symbol that is
affected by the recent name mangling changes in GCC 7. See:
https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling

In GCC 7, the name mangling for C++ conversion operators which return a
type using the abi_tag attribute (most commonly std::string) has
changed. When your library is compiled with GCC 7, it will now emit two
symbols for the conversion operator using the new and old naming.
Executables compiled with GCC 7 will always use the new symbol, while
old executables compiled using <= GCC 6 will use the old symbol. For new
executables to build without undefined references, your library will
need rebuilding with GCC 7.

To ensure that new executables will pull in the newer version of the
library built with GCC 7:
- Your library package should Build-Depend on g++ (>= 4:7).
- If your package provides a symbols file, ensure that the new
  conversion operator symbols have a version matching the version this
  bug is fixed in (including the Debian revision and tilde if
  necessary).

  Using apt as an example (debian/libapt-pkg5.0.symbols):
(c++)"URI::operator std::__cxx11::basic_string[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string()@APTPKG_5.0" 1.5~beta2~

  Where "1.5~beta2" is the version this bug was fixed in.

- If your package does not provide a symbols file, add a dh_makeshlibs
  override so that tight enough dependencies are generated.

  Using libebml as an example (debian/rules):
  + override_dh_makeshlibs:
  + # For new symbols when compiled with GCC 7
  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'

  Where "1.3.4-2" is the version this bug was fixed in.

- If your package is about to be renamed due to an upstream SONAME bump,
  you do not need to add any special symbols handling.

If you would like to know the exact name of the new symbols, using
"abipkgdiff" from abigail-tools might be able to help.

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: htmlcxx
Source-Version: 0.86-1.2

We believe that the bug you reported is fixed in the latest version of
htmlcxx, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated htmlcxx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Aug 2017 17:13:31 +0200
Source: htmlcxx
Binary: libhtmlcxx-dev libhtmlcxx3v5 libcss-parser0 libcss-parser-pp0v5
Architecture: source
Version: 0.86-1.2
Distribution: unstable
Urgency: medium
Maintainer: Ludovico Cavedon 
Changed-By: Stephen Kitt 
Description:
 libcss-parser-pp0v5 - simple CSS1 parser library for C++
 libcss-parser0 - simple CSS1 parser library for C
 libhtmlcxx-dev - simple HTML/CSS1 parser library for C++ (development)
 libhtmlcxx3v5 - simple HTML parser library for C++
Closes: 871295
Changes:
 htmlcxx (0.86-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add GCC 7 symbols (Closes: #871295).
Checksums-Sha1:
 af5faeff68069023cda0fb8e5eb11827a0672d3a 2140 htmlcxx_0.86-1.2.dsc
 ae0f2af25aee1b98f72977aaad1b5bdf828e8e3a 8376 htmlcxx_0.86-1.2.debian.tar.xz
 34cf5132d30188a172594e42c23da6ec7dd11672 6169 htmlcxx_0.86-1.2_source.buildinfo
Checksums-Sha256:
 9a3f886d5c8307ea3803c59f95cfb51f45d06b4099428dc9ba2eba0da3aaa4f8 2140 
htmlcxx_0.86-1.2.dsc
 

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 858250 pending
Bug #858250 [runc] Fails to build for unstable, build-depends not strict enough
Bug #861966 [runc] Fails to build for unstable, build-depends not strict enough
Added tag(s) pending.
Added tag(s) pending.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
858250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858250
861966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872438: [Pkg-javascript-devel] Bug#872438: Bug#872438: Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

[Bastien ROUCARIES]

On Fri, Aug 18, 2017 at 7:42 PM, Jérémy Lal  wrote:
> James Cowgill replied this to my give back request on mip64el:
>
>> My guess is this GCC-7 bug which is breaking lots of stuff on mips64el
>> at the moment:
>> https://bugs.debian.org/871514
>
>> Thanks,
>> James
>
> Cheers,
>
> Jérémy

Thanks BTW why node has no debug symbols ?

Bastien

>
> --
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Bug#872568: rsyslog: FTBFS on mips, mipsel - error: 'pThis' undeclared

[James Cowgill]

Source: rsyslog
Version: 8.29.0-1
Severity: serious
Tags: sid buster patch

Hi,

rsyslog FTBFS on mips, mipsel and various ports architectures with the
error:
> In file included from ../../runtime/prop.h:25:0,
>  from ../../runtime/glbl.h:38,
>  from ../../runtime/stream.h:73,
>  from ../../runtime/obj.h:48,
>  from ../../runtime/rsyslog.h:634,
>  from imptcp.c:61:
> imptcp.c: In function 'AcceptConnReq':
> imptcp.c:831:39: error: 'pThis' undeclared (first use in this function)
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>^
> ../../runtime/atomic.h:206:22: note: in definition of macro 
> 'ATOMIC_INC_uint64'
>pthread_mutex_lock(phlpmut); \
>   ^~~
> imptcp.c:831:2: note: in expansion of macro 'STATSCOUNTER_INC'
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>   ^~~~
> imptcp.c:831:39: note: each undeclared identifier is reported only once for 
> each function it appears in
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>^
> ../../runtime/atomic.h:206:22: note: in definition of macro 
> 'ATOMIC_INC_uint64'
>pthread_mutex_lock(phlpmut); \
>   ^~~
> imptcp.c:831:2: note: in expansion of macro 'STATSCOUNTER_INC'
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>   ^~~~

As the error suggests, pThis is not declared in that function. The code
is only used on architectures which do not have 64-bit atomics which is
why it only fails on some architectures.

There is an upstream pull request to fix this:
https://github.com/rsyslog/rsyslog/pull/1725

I've also attached the patch from that PR which should fix this.

Thanks,
James
From 2ea84c47b208214370034500f0aab19fe93cce7f Mon Sep 17 00:00:00 2001
From: Pete Nelson 
Date: Wed, 16 Aug 2017 17:19:33 -0400
Subject: [PATCH] correct paste oversight on mutex arg

Remove the 'pThis->' from the second argument to STATSCOUNTER_INC macro.
This only affects architectures without atomic uint64 actions, like aarm64.
Others do not use the mut argument, and it gets compiled out.
---
 plugins/imptcp/imptcp.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/plugins/imptcp/imptcp.c b/plugins/imptcp/imptcp.c
index c373c17e6..ab2a17e5b 100644
--- a/plugins/imptcp/imptcp.c
+++ b/plugins/imptcp/imptcp.c
@@ -828,7 +828,7 @@ AcceptConnReq(ptcplstn_t *pLstn, int *newSock, prop_t **peerName, prop_t **peerI
 		LogMsg(0, RS_RET_NO_ERRCODE, LOG_INFO, "imptcp: connection established with host: %s", propGetSzStr(*peerName));
 	}
 
-	STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
+	STATSCOUNTER_INC(pLstn->ctrSessOpen, pLstn->mutCtrSessOpen);
 	*newSock = iNewSock;
 
 finalize_it:
@@ -837,7 +837,7 @@ AcceptConnReq(ptcplstn_t *pLstn, int *newSock, prop_t **peerName, prop_t **peerI
 		if(iRet != RS_RET_NO_MORE_DATA && pLstn->pSrv->bEmitMsgOnOpen) {
 			LogError(0, NO_ERRCODE, "imptcp: connection could not be established with host: %s", propGetSzStr(*peerName));
 		}
-		STATSCOUNTER_INC(pLstn->ctrSessOpenErr, pThis->pLstn->mutCtrSessOpenErr);
+		STATSCOUNTER_INC(pLstn->ctrSessOpenErr, pLstn->mutCtrSessOpenErr);
 		/* the close may be redundant, but that doesn't hurt... */
 		if(iNewSock != -1)
 			close(iNewSock);


signature.asc
Description: OpenPGP digital signature

Bug#872438: [Pkg-javascript-devel] Bug#872438: Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

[Jérémy Lal]

James Cowgill replied this to my give back request on mip64el:

> My guess is this GCC-7 bug which is breaking lots of stuff on mips64el
> at the moment:
> https://bugs.debian.org/871514

> Thanks,
> James

Cheers,

Jérémy

Bug#872438: [Pkg-javascript-devel] Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

[Bastien ROUCARIES]

Starting program: /home/rouca/nodejs-6.11.2~dfsg/node
warning: GDB can't find the start of the function at 0xfff7fcd0c4.
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/mips64el-linux-gnuabi64/libthread_db.so.1".
warning: GDB can't find the start of the function at 0xfff7fcddc8.
[New Thread 0xfff59db1e0 (LWP 516)]
[New Thread 0xfff59bb1e0 (LWP 517)]
[New Thread 0xfff51bb1e0 (LWP 518)]
[New Thread 0xfff49bb1e0 (LWP 521)]
[New Thread 0xfff41bb1e0 (LWP 522)]

Thread 1 "node" received signal SIGBUS, Bus error.
0x0001 in ?? ()
(gdb) info register
  zero   at   v0   v1
 R0    00ffda68 4500d051 53731e19
a0   a1   a2   a3
 R4   0001 00ffda98 000120f81220 2ee04241
a4   a5   a6   a7
 R8   2ee63501 2ee41019 0003 0003
t0   t1   t2   t3
 R12  35436b00 84080018 811372e0 0009
s0   s1   s2   s3
 R16  0001 00ffda98 0001 
s4   s5   s6   s7
 R20  2ee635c8 beeddead 000120f81258 2ee3ed41
t8   t9   k0   k1
 R24  000120f82cc8 0001 0015 
gp   sp   s8   ra
 R28  000120f424b0 00ffda60 00ffda88 3540610c
status   lo   hi badvaddr
  04109cf3 604189374cdec514 00ebe2a5 0001
 cause   pc
  00800010 0001
  fcsr  fir  restart
  dc64 00739600 
(gdb) bt
warning: GDB can't find the start of the function at 0x3540610b.
#0  0x0001 in ?? ()
#1  0x3540610c in ?? ()
(gdb) frame
#0  0x0001 in ?? ()
(gdb)

Bug#853618: marked as done (plee-the-bear: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 17:20:42 +
with message-id 
and subject line Bug#853618: fixed in plee-the-bear 0.6.0-4
has caused the Debian Bug report #853618,
regarding plee-the-bear: 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.)


-- 
853618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:plee-the-bear
Version: 0.6.0-3.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/plee-the-bear_0.6.0-3.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

[...]
 from 
/<>/bear-engine/core/src/visual/bitmap_rendering_attributes.hpp:35,
 from 
/<>/bear-engine/core/src/visual/sprite.hpp:32,
 from 
/<>/bear-engine/core/src/visual/sprite_sequence.hpp:35,
 from 
/<>/bear-engine/core/src/visual/animation.hpp:32,
 from 
/<>/bear-engine/core/src/visual/code/animation.cpp:29:
/usr/include/claw/impl/rectangle.tpp: In member function 
'claw::math::rectangle claw::math::rectangle::cast_value_type_to() const':
/usr/include/claw/impl/rectangle.tpp:143:5: error: expected primary-expression 
before '(' token
 ( position.cast_value_type_to(), (U)width, (U)height );
 ^
/usr/include/claw/impl/rectangle.tpp:143:36: error: expected primary-expression 
before '>' token
 ( position.cast_value_type_to(), (U)width, (U)height );
^
/usr/include/claw/impl/rectangle.tpp:143:38: error: expected primary-expression 
before ')' token
 ( position.cast_value_type_to(), (U)width, (U)height );
  ^
In file included from /usr/include/claw/box_2d.hpp:129:0,
 from /<>/bear-engine/core/src/visual/types.hpp:33,
 from 
/<>/bear-engine/core/src/visual/bitmap_rendering_attributes.hpp:35,
 from 
/<>/bear-engine/core/src/visual/sprite.hpp:32,
 from 
/<>/bear-engine/core/src/visual/sprite_sequence.hpp:35,
 from 
/<>/bear-engine/core/src/visual/animation.hpp:32,
 from 
/<>/bear-engine/core/src/visual/code/animation.cpp:29:
/usr/include/claw/impl/box_2d.tpp: In member function 'claw::math::box_2d 
claw::math::box_2d::cast_value_type_to() const':
/usr/include/claw/impl/box_2d.tpp:139:5: error: expected primary-expression 
before '(' token
 ( first_point.cast_value_type_to(),
 ^
/usr/include/claw/impl/box_2d.tpp:139:39: error: expected primary-expression 
before '>' token
 ( first_point.cast_value_type_to(),
   ^
/usr/include/claw/impl/box_2d.tpp:139:41: error: expected primary-expression 
before ')' token
 ( first_point.cast_value_type_to(),
 ^
/usr/include/claw/impl/box_2d.tpp:140:40: error: expected primary-expression 
before '>' token
   second_point.cast_value_type_to() );
^
/usr/include/claw/impl/box_2d.tpp:140:42: error: expected primary-expression 
before ')' token
   second_point.cast_value_type_to() );
  ^
bear-engine/core/src/visual/CMakeFiles/bear_visual.dir/build.make:62: recipe 
for target 
'bear-engine/core/src/visual/CMakeFiles/bear_visual.dir/code/animation.cpp.o' 
failed
make[3]: *** 

Processed (with 1 error): updating runc and dependencies

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 858250 by 872440
Bug #858250 [runc] Fails to build for unstable, build-depends not strict enough
Bug #861966 [runc] Fails to build for unstable, build-depends not strict enough
858250 was not blocked by any bugs.
858250 was not blocking any bugs.
Added blocking bug(s) of 858250: 872440
861966 was not blocked by any bugs.
861966 was not blocking any bugs.
Added blocking bug(s) of 861966: 872440
> pending 858250
Unknown command or malformed arguments to command.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
858250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858250
861966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853610: marked as done (pesign: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 16:49:21 +
with message-id 
and subject line Bug#853537: fixed in gcc-7 7.2.0-1
has caused the Debian Bug report #853537,
regarding pesign: 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.)


-- 
853537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pesign
Version: 0.112-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/pesign_0.112-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

[...]
/usr/bin/gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror 
-Wno-cpp  -Wsign-compare -Wno-unused-result -Wno-unused-function -std=gnu11 
-fshort-wchar -fPIC -flto -fno-strict-aliasing -fno-merge-constants 
-fkeep-inline-functions -D_GNU_SOURCE -DCONFIG_x86_64 
-I/<>/include  -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -MM -MG 
-MF .daemon.d daemon.c
echo SOURCES=cms_common.c content_info.c oid.c password.c signed_data.c 
signer_info.c ucs2.c  pesign_context.c actions.c client.c efikeygen.c 
efisiglist.c siglist.c pesigcheck.c pesigcheck_context.c certdb.c pesign.c 
pesign_context.c actions.c daemon.c
SOURCES=cms_common.c content_info.c oid.c password.c signed_data.c 
signer_info.c ucs2.c pesign_context.c actions.c client.c efikeygen.c 
efisiglist.c siglist.c pesigcheck.c pesigcheck_context.c certdb.c pesign.c 
pesign_context.c actions.c daemon.c
make[3]: Leaving directory '/<>/src'
make[2]: Leaving directory '/<>/src'
make[2]: Entering directory '/<>/include'
for x in libdpe ; do \
make -C $x all ; \
done
make[3]: Entering directory '/<>/include/libdpe'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/include/libdpe'
make[2]: Leaving directory '/<>/include'
make[2]: Entering directory '/<>/libdpe'
make -f /<>/Make.deps deps SOURCES="libdpe.c pe_rawfile.c 
pe_allocspace.c pe_opthdr.c pe_updatenull.c pe_nextscn.c pe_updatefile.c 
pe_getscn.c pe_getdatadir.c pe_getshdr.c pe_readall.c pe_error.c pe_addcert.c 
pe_end.c pe_begin.c pe_getpehdr.c pe_update.c"
make[3]: Entering directory '/<>/libdpe'
echo SOURCES=libdpe.c pe_rawfile.c pe_allocspace.c pe_opthdr.c pe_updatenull.c 
pe_nextscn.c pe_updatefile.c pe_getscn.c pe_getdatadir.c pe_getshdr.c 
pe_readall.c pe_error.c pe_addcert.c pe_end.c pe_begin.c pe_getpehdr.c 
pe_update.c
SOURCES=libdpe.c pe_rawfile.c pe_allocspace.c pe_opthdr.c pe_updatenull.c 
pe_nextscn.c pe_updatefile.c pe_getscn.c pe_getdatadir.c pe_getshdr.c 
pe_readall.c pe_error.c pe_addcert.c pe_end.c pe_begin.c pe_getpehdr.c 
pe_update.c
make[3]: Leaving directory '/<>/libdpe'
/usr/bin/gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror 
-Wno-cpp  -Wsign-compare -Wno-unused-result -Wno-unused-function -std=gnu11 
-fshort-wchar -fPIC -flto -fno-strict-aliasing -fno-merge-constants 
-fkeep-inline-functions -D_GNU_SOURCE -DCONFIG_x86_64 
-I/<>/include  -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -c -o 
libdpe.o libdpe.c
/usr/bin/gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror 
-Wno-cpp  -Wsign-compare -Wno-unused-result -Wno-unused-function -std=gnu11 
-fshort-wchar -fPIC -flto -fno-strict-aliasing -fno-merge-constants 
-fkeep-inline-functions -D_GNU_SOURCE -DCONFIG_x86_64 
-I/<>/include  -Werror -Wdate-time 

Bug#853395: marked as done (fastd: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 16:49:21 +
with message-id 
and subject line Bug#853537: fixed in gcc-7 7.2.0-1
has caused the Debian Bug report #853537,
regarding fastd: 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.)


-- 
853537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fastd
Version: 18-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/fastd_18-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

[...]
-- Performing Test HAVE_ENDIAN_H - Success
-- Looking for be32toh
-- Looking for be32toh - found
-- Could NOT find Doxygen (missing:  DOXYGEN_EXECUTABLE) 
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_SYSCONFDIR


-- 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 7 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 
src/crypto/mac/uhash/builtin/CMakeFiles/mac_uhash_builtin.dir/build.make 
src/crypto/mac/uhash/builtin/CMakeFiles/mac_uhash_builtin.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" /<> /<>/src/crypto/mac/uhash/builtin 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/src/crypto/mac/uhash/builtin 
/<>/obj-x86_64-linux-gnu/src/crypto/mac/uhash/builtin/CMakeFiles/mac_uhash_builtin.dir/DependInfo.cmake
 --color=
Scanning dependencies of target mac_uhash_builtin
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f 
src/crypto/mac/uhash/builtin/CMakeFiles/mac_uhash_builtin.dir/build.make 
src/crypto/mac/uhash/builtin/CMakeFiles/mac_uhash_builtin.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  1%] Building C object 
src/crypto/mac/uhash/builtin/CMakeFiles/mac_uhash_builtin.dir/uhash_builtin.c.o
cd /<>/obj-x86_64-linux-gnu/src/crypto/mac/uhash/builtin && 
/usr/bin/cc  -D_GNU_SOURCE -D__APPLE_USE_RFC_3542 -I/<> 
-I/<>/obj-x86_64-linux-gnu/gen  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -g -DNDEBUG   -pthread -std=c99-flto -Wall -o 
CMakeFiles/mac_uhash_builtin.dir/uhash_builtin.c.o   -c 
/<>/src/crypto/mac/uhash/builtin/uhash_builtin.c
[  2%] Linking C static library libmac_uhash_builtin.a
cd /<>/obj-x86_64-linux-gnu/src/crypto/mac/uhash/builtin && 
/usr/bin/cmake -P CMakeFiles/mac_uhash_builtin.dir/cmake_clean_target.cmake
cd /<>/obj-x86_64-linux-gnu/src/crypto/mac/uhash/builtin && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/mac_uhash_builtin.dir/link.txt 
--verbose=1
/usr/bin/gcc-ar qc libmac_uhash_builtin.a  
CMakeFiles/mac_uhash_builtin.dir/uhash_builtin.c.o
Error running link command: Segmentation fault
src/crypto/mac/uhash/builtin/CMakeFiles/mac_uhash_builtin.dir/build.make:97: 
recipe for target 'src/crypto/mac/uhash/builtin/libmac_uhash_builtin.a' failed

Bug#853537: marked as done (binutils: /usr/bin/gcc-ar segfaults)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 16:49:21 +
with message-id 
and subject line Bug#853537: fixed in gcc-7 7.2.0-1
has caused the Debian Bug report #853537,
regarding binutils: /usr/bin/gcc-ar segfaults
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.)


-- 
853537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mariadb-10.1
Version: 10.1.21-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/mariadb-10.1_10.1.21-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

[...]
libtool: install: /usr/bin/install -c .libs/liblzma.a 
/<>/builddir/storage/tokudb/PerconaFT/./xz/lib/liblzma.a
libtool: install: chmod 644 
/<>/builddir/storage/tokudb/PerconaFT/./xz/lib/liblzma.a
libtool: install: ranlib 
/<>/builddir/storage/tokudb/PerconaFT/./xz/lib/liblzma.a
libtool: finish: 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/sbin"
 ldconfig -n /<>/builddir/storage/tokudb/PerconaFT/./xz/lib
--
Libraries have been installed in:
   /<>/builddir/storage/tokudb/PerconaFT/./xz/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
 during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
 during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
--
make[7]: Leaving directory 
'/<>/builddir/storage/tokudb/PerconaFT/xz/src/build_lzma-build/src/liblzma'
make[6]: Leaving directory 
'/<>/builddir/storage/tokudb/PerconaFT/xz/src/build_lzma-build/src/liblzma'
make[5]: Leaving directory 
'/<>/builddir/storage/tokudb/PerconaFT/xz/src/build_lzma-build/src/liblzma'
cd /<>/builddir/storage/tokudb/PerconaFT/xz/src/build_lzma-build 
&& /usr/bin/cmake -E touch 
/<>/builddir/storage/tokudb/PerconaFT/xz/src/build_lzma-stamp/build_lzma-install
[ 11%] Completed 'build_lzma'
cd /<>/builddir/storage/tokudb/PerconaFT && /usr/bin/cmake -E 
make_directory /<>/builddir/storage/tokudb/PerconaFT/CMakeFiles
cd /<>/builddir/storage/tokudb/PerconaFT && /usr/bin/cmake -E 
touch 
/<>/builddir/storage/tokudb/PerconaFT/CMakeFiles/build_lzma-complete
cd /<>/builddir/storage/tokudb/PerconaFT && /usr/bin/cmake -E 
touch 
/<>/builddir/storage/tokudb/PerconaFT/xz/src/build_lzma-stamp/build_lzma-done
make[4]: Leaving directory '/<>/builddir'
[ 11%] Built target build_lzma
/<>/storage/mroonga/vendor/groonga/lib/expr.c:3543:1: warning: 
const/copy propagation disabled: 19139 basic blocks and 71452 registers; 
increase --param max-gcse-memory above 171026104 [-Wdisabled-optimization]
[ 11%] Linking CXX static library libgroonga.a
cd /<>/builddir/storage/mroonga/vendor/groonga/lib && 
/usr/bin/cmake -P CMakeFiles/libgroonga.dir/cmake_clean_target.cmake
cd /<>/builddir/storage/mroonga/vendor/groonga/lib && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/libgroonga.dir/link.txt 
--verbose=1

Bug#853658: Forwarded upstream

[Sebastiaan Couwenberg]

On Mon, 7 Aug 2017 08:49:19 +0100 Ghislain Vaillant wrote:
> control: forwarded -1 https://github.com/Shark-ML/Shark/issues/194

Instead of packaging a snapshot as suggested by upstream, I suggest to
explicitly build the package with GCC 6 (as per the attached patch)(
until the new upstream release is available which builds successfully
with GCC 7.

Kind Regards,

Bas
diff --git a/debian/control b/debian/control
index dabad673..2afa097f 100644
--- a/debian/control
+++ b/debian/control
@@ -5,6 +5,8 @@ Section: science
 Priority: optional
 Build-Depends: cmake,
debhelper (>= 10),
+   gcc-6,
+   g++-6,
libblas-dev | libblas.so,
libboost-date-time-dev,
libboost-filesystem-dev,
diff --git a/debian/rules b/debian/rules
index 9e6a203e..0f4ad606 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,6 +9,9 @@ export DEB_CFLAGS_MAINT_APPEND = -Wall -pedantic
 export DEB_CXXFLAGS_MAINT_APPEND = -Wall -pedantic
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
+export CC=gcc-6
+export CXX=g++-6
+
 # Common cmake options.
 CMAKE_BUILD_OPTIONS = \
 	-DBUILD_SHARED_LIBS=ON \

Bug#853658: Forwarded upstream

[Ghislain Vaillant]

On 18/08/17 17:26, Sebastiaan Couwenberg wrote:

On Mon, 7 Aug 2017 08:49:19 +0100 Ghislain Vaillant wrote:

control: forwarded -1 https://github.com/Shark-ML/Shark/issues/194


Instead of packaging a snapshot as suggested by upstream, I suggest to
explicitly build the package with GCC 6 (as per the attached patch)(
until the new upstream release is available which builds successfully
with GCC 7.


That's a good point, though I am worried of the lack of response from 
upstream and lack of commit activity overall (compared to when I 
packaged the software initially).


Thanks for the patch, I'll incorporate it soon.

Ghis

Bug#872537: marked as done (mpgrafic FTBFS on 32bit: Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4))

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 16:22:13 +
with message-id 
and subject line Bug#872537: fixed in mpgrafic 0.3.14-1
has caused the Debian Bug report #872537,
regarding mpgrafic FTBFS on 32bit: Error: Type mismatch in argument 'size' at 
(1); passed INTEGER(8) to INTEGER(4)
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.)


-- 
872537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpgrafic
Version: 0.3.13-1
Severity: serious

https://buildd.debian.org/status/package.php?p=mpgrafic=sid

...
Making all in src
make[3]: Entering directory '/<>/src'
mpifort -cpp -DDOUB  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -c -o grafic_types.o grafic_types.f90
mpicc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o parallel_io.o parallel_io.c
parallel_io.c: In function 'parallel_write':
parallel_io.c:58:44: warning: format '%ld' expects argument of type 'long int', 
but argument 3 has type 'long long int' [-Wformat=]
 fprintf(stderr,"which is bigger than %ld\n",(int64_t)OFFSET_MAX);
  ~~^
  %lld
parallel_io.c: In function 'parallel_read':
parallel_io.c:79:44: warning: format '%ld' expects argument of type 'long int', 
but argument 3 has type 'long long int' [-Wformat=]
 fprintf(stderr,"which is bigger than %ld\n",(int64_t)OFFSET_MAX);
  ~~^
  %lld
mpifort -cpp -DDOUB  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -c -o grafic_io.o grafic_io.f90
grafic_io.f90:468:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:490:36:

 & offset, c_loc(tampon))
1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:495:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:355:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:377:36:

 & offset, c_loc(tampon))
1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:382:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:275:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:283:36:

 & offset, c_loc(tampon))
1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:288:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:172:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:180:36:

 & offset, c_loc(tampon))
1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:185:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
Makefile:446: recipe for target 'grafic_io.o' failed
make[3]: *** [grafic_io.o] Error 1
--- End Message ---
--- Begin Message ---
Source: mpgrafic
Source-Version: 0.3.14-1

We believe that the bug you reported is fixed in the latest version of
mpgrafic, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 872...@bugs.debian.org,
and the maintainer will 

Bug#855208: marked as done (runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 18:16:49 +0200
with message-id <9b091877-c9aa-bdda-3f7a-49e4529b0...@canonical.com>
and subject line Re: Bug#855208: [pkg-go] Bug#855208: docker still broken
has caused the Debian Bug report #855208,
regarding runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: 
flag provided but not defined: -bundle
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.)


-- 
855208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: runc
Version: 1.0.0~rc2+git20161109.131.5137186-1
Severity: grave
Justification: renders docker unusable
Control: affects -1 docker.io

After upgrading to 1.0.0~rc2+git20161109.131.5137186-1 , docker
containers fail to start:

 Cannot start service web: rpc error: code = 2 desc = "oci runtime error: flag 
provided but not defined: -bundle"

I don't know what docker version allows usage of runc 1.0 rc.

I'm tagging the severity as grave since runc appears to be a component
of docker (there are no other rdeps), and docker fails to work with this
version.

Saludos

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages runc depends on:
ii  libapparmor1  2.11.0-2
ii  libc6 2.24-9
ii  libseccomp2   2.3.1-2.1

runc recommends no packages.

runc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 1.0.0~rc2+git20170201.133.9df8b30-1

On Mon, 26 Jun 2017 17:45:28 -0400 Antoine Beaupre
 wrote:
> Control: fixed -1 1.0.0~rc2+git20170201.1
>
> On Fri, Feb 24, 2017 at 10:39:00PM +0100, Vincent Bernat wrote:
> > ❦ 24 février 2017 12:34 -0800, Norbert Kiesel  :
> >
> > > What else can I do to get docker working again?
> >
> > You can install the one from experimental. It works fine with runc and
> > containerd from unstable. At this point, Tim should just upload it to
> > unstable.
>
> From what I can tell, this is now fixed in unstable: I was able to
> install all of this with the sid packages in stretch.

Thanks, closing the bug then with a version which existed in unstable.

Cheers,
Balint--- End Message ---

Bug#872565: encfs: FTBFS on mips, mipsel: undefined reference to `__atomic_store_8'

[James Cowgill]

Source: encfs
Version: 1.9.2-1
Severity: serious
Tags: sid buster

Hi,

ensfc FTBFS on mips, mipsel and various ports architectures with the error:
> libencfs.so.1.9.2: undefined reference to `__atomic_store_8'
> libencfs.so.1.9.2: undefined reference to `__atomic_fetch_add_8'
> collect2: error: ld returned 1 exit status

This happens because those architectures do not have native 64-bit
atomic instructions and instead call out to libatomic to provide
emulations of them. To allow linking on these architecture you must link
against libatomic.

One option is to add the -latomic to LDFLAGS in the Debian package, or I
could probably come up with a patch to be applied upstream which will
link only on the architectures it's needed.

Note there is an upstream GCC bug about doing all this in the toolchain,
but for the moment it has to be done per package:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#872464: marked as done (zimlib: FTBFS all over the place due to symbols diff)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 15:36:20 +
with message-id 
and subject line Bug#872464: fixed in zimlib 2.0.0-2
has caused the Debian Bug report #872464,
regarding zimlib: FTBFS all over the place due to symbols diff
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.)


-- 
872464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zimlib
Version: 2.0.0-1
Severity: serious

Hi,
Once again zimlib FTBFS due to symbols file diffs. Please at least *try*
to get a working symbols file; you can at least build amd64 locally, and
we have porterboxen for a reason...

James
--- End Message ---
--- Begin Message ---
Source: zimlib
Source-Version: 2.0.0-2

We believe that the bug you reported is fixed in the latest version of
zimlib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 872...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated zimlib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 Aug 2017 17:17:32 +0200
Source: zimlib
Binary: libzim2 libzim-dev
Architecture: source
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Description:
 libzim-dev - library implementation of ZIM specifications (development)
 libzim2- library implementation of ZIM specifications
Closes: 872464
Changes:
 zimlib (2.0.0-2) unstable; urgency=medium
 .
   * Modernize Vcs-* fields: Use git (not cgit) in path.
   * Declare compliance with Debian Policy 4.0.1.
   * Update symbols file.
 Closes: Bug#872464. Thanks to James Clarke.
   * Update git-buildpackage config: Filter any .gitignore file.
   * Drop obsolete README.source: CDBS no longer used.
   * Update copyright info:
 + Use only Github issue tracker as preferred form of contact.
Checksums-Sha1:
 70e54d5c0c96b1c803b8885c44fff9754f539060 2080 zimlib_2.0.0-2.dsc
 1abeb848e2d9928a23e59c255498d74e0342f844 10312 zimlib_2.0.0-2.debian.tar.xz
 a197be958de06e20bf5353e6cbf1b33d5ce16f3a 6420 zimlib_2.0.0-2_amd64.buildinfo
Checksums-Sha256:
 3d95bc176883eda6110049aad69974d14ceda1eb3477d904a4b45ba418383735 2080 
zimlib_2.0.0-2.dsc
 2770f8103de27f88de72a3ce83977fb8c0973c548a13986ecc6ee1e71616618e 10312 
zimlib_2.0.0-2.debian.tar.xz
 30b1b6ddfbed060f0f3c5c1766c33ed46a202c2d8df65c995a53b46b825d877c 6420 
zimlib_2.0.0-2_amd64.buildinfo
Files:
 421422f94a8f59411525e92e19a5bdfd 2080 libs optional zimlib_2.0.0-2.dsc
 dfdbb91df68a824e2beadd5472471054 10312 libs optional 
zimlib_2.0.0-2.debian.tar.xz
 0c96722eedba07d74d02a2cc7cfc3968 6420 libs optional 
zimlib_2.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlmXBpYACgkQLHwxRsGg
ASEOQQ/8Cce2md519sNJ4Vgl0BuLDUjHrwkeqkCwSk5rnRG9vEOaWS49G7Jy+/B+
tUgssnBYWJVqiZDDoNbU7kLAyvi6Q0nnoZdam+le22iYzoCEExMIhd6gLohOgc7B
iXw2L/nasWUNnTo772XatzwwyDWEI6jS67l64kVKHm0hbgBGZ6/ZJjmowQZdOMHm
IZdWpljzTJiziF46LiF97ioQhVuLD58CWYK1ml5MT0Tq0s/nUbVk9vp29k2C2tox
/Gi2HFA6Bf6PP90TvB/jHK9sfoTJ6YZWAcWe1ltVBftdW97xZEjqGSf/nm7SJ3Dg
ETG2n3I2++O5JIMxZz8mD04Xe8MAga56E08OouYP8EQvoESsbKZNzb39BwSpeH4k
lqlMDcmMPcgREKPhMkYSJ7xbJb3CAZHZCNCEWhICNx/536xRWOOuQmoN6kMWrDxd
dWDeHyRnyykSf8u4qhkxIDAIRzh8STbYZ/m+IIqEQVShoZA1AMB6na+LRcN9c3/+
qICP0j3sEf0tkfwDG5aPOtualIj46wPoHFMRR4JkOMFsq7Aq15oO/SsXeOl+U0R/
ragopAcEJfTgCRagVLc/M+fNmjQpmX0nW9z9hY+X9EjR+IMP93le2/6Ya+rJInMy
N+9b8ynMeyqNnLvtcpuzRGP+oUfQPB4NBb/uRfxlftb5nVzCnJ0=
=eKya
-END PGP SIGNATURE End Message ---

Processed: closing 871354

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 871354
Bug #871354 [src:aspectj-maven-plugin] aspectj-maven-plugin: FTBFS: ERROR 
Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test 
(default-test) on project aspectj-maven-plugin: Execution 
default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test 
failed: There was an error in the forked process
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
871354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853634: marked as done (qtwebengine-opensource-src: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 18:10:40 +0300
with message-id <20170818151040.fshpdhnn42re7w35@localhost>
and subject line qtwebengine-opensource-src in unstable builds with gcc 7
has caused the Debian Bug report #853634,
regarding qtwebengine-opensource-src: 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.)


-- 
853634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qtwebengine-opensource-src
Version: 5.7.1+dfsg-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/qtwebengine-opensource-src_5.7.1+dfsg-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

[...]
   handle_ = other.handle_.Pass();
   ^~~~
[1429/12058] /usr/bin/g++ -MMD -MF 
obj/src/3rdparty/chromium/third_party/skia/src/effects/skia_library.SkBlurMaskFilter.o.d
 -DV8_DEPRECATION_WARNINGS -DCLD_VERSION=2 -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 
-DNO_TCMALLOC -DCHROMIUM_BUILD -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 
-DUSE_DEFAULT_RENDER_THEME=1 -DUSE_LIBJPEG_TURBO=1 -DUSE_X11=1 
-DENABLE_ONE_CLICK_SIGNIN -DENABLE_WEBRTC=1 -DENABLE_MEDIA_ROUTER=1 
-DUSE_PROPRIETARY_CODECS -DENABLE_PEPPER_CDMS -DENABLE_CONFIGURATION_POLICY 
-DENABLE_NOTIFICATIONS -DENABLE_HIDPI=1 -DENABLE_TOPCHROME_MD=1 -DUSE_UDEV 
-DDONT_EMBED_BUILD_METADATA -DFIELDTRIAL_TESTING_ENABLED 
-DENABLE_TASK_MANAGER=1 -DENABLE_PDF=1 -DENABLE_PLUGINS=1 
-DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1 -DENABLE_AUTOFILL_DIALOG=1 
-DENABLE_BACKGROUND=1 -DENABLE_PRINTING=1 -DENABLE_BASIC_PRINTING=1 
-DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE_APP_LIST=1 -DENABLE_SETTINGS_APP=1 
-DENABLE_SUPERVISED_USERS=1 -DENABLE_MDNS=1 -DENABLE_SERVICE_DISCOVERY=1 
-DFULL_SAFE_BROWSING -DSAFE_BR
 OWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DSK_SUPPORT_GPU=1 
-DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS 
'-DSK_DEFAULT_FONT_CACHE_LIMIT=(20*1024*1024)' -DSK_GAMMA_EXPONENT=1.2 
-DSK_GAMMA_CONTRAST=0.2 -DUSE_SYSTEM_ZLIB -DU_USING_ICU_NAMESPACE=0 
-DU_ENABLE_DYLOAD=0 -DU_STATIC_IMPLEMENTATION -DUSE_LIBPCI=1 -DUSE_OPENSSL=1 
-DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 
'-DQTWEBENGINEPROCESS_NAME="QtWebEngineProcess"' -Igen/shim_headers/zlib/target 
-Igen 
'-I/<>/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium' 
'-I/<>/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/skia/config'
 
'-I/<>/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/c'
 
'-I/<>/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/core'
 
'-I/<>/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/effects'
 '-I/<>/qtwebe
 
ngine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/images'
 
'-I/<>/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/lazy'
 
'-I/<>/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/pathops'
 
'-I/<>/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/pdf'
 
'-I/<>/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/pipe'
 
'-I/<>/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/ports'
 
'-I/<>/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/private'
 

Bug#853630: marked as done (qtbase-opensource-src: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 18:08:43 +0300
with message-id <20170818150843.mffbzd5jkh7wyc32@localhost>
and subject line qtbase-opensource-src in unstable builds with gcc 7
has caused the Debian Bug report #853630,
regarding qtbase-opensource-src: 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.)


-- 
853630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qtbase-opensource-src
Version: 5.7.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/qtbase-opensource-src_5.7.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

[...]
  ^
../../include/QtCore/../../src/corelib/global/qtypeinfo.h:69:24: error: invalid 
application of 'sizeof' to incomplete type 'QMimeMagicRuleMatcher'
 sizeOf = sizeof(T)
^
In file included from ../../include/QtCore/qlist.h:1:0,
 from 
../../include/QtCore/../../src/corelib/kernel/qobject.h:49,
 from ../../include/QtCore/qobject.h:1,
 from 
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:46,
 from ../../include/QtCore/qcoreapplication.h:1,
 from global/qt_pch.h:62:
../../include/QtCore/../../src/corelib/tools/qlist.h: In instantiation of 'void 
QList::node_destruct(QList::Node*, QList::Node*) [with T = 
QMimeMagicRuleMatcher]':
../../include/QtCore/../../src/corelib/tools/qlist.h:861:18:   required from 
'void QList::dealloc(QListData::Data*) [with T = QMimeMagicRuleMatcher]'
../../include/QtCore/../../src/corelib/tools/qlist.h:823:16:   required from 
'QList::~QList() [with T = QMimeMagicRuleMatcher]'
mimetypes/qmimeprovider_p.h:137:7:   required from here
../../include/QtCore/../../src/corelib/tools/qlist.h:490:31: warning: possible 
problem detected in invocation of delete operator: [-Wdelete-incomplete]
 while(from != to) --to, delete reinterpret_cast(to->v);
../../include/QtCore/../../src/corelib/tools/qlist.h:490:65: warning: invalid 
use of incomplete type 'class QMimeMagicRuleMatcher'
 while(from != to) --to, delete reinterpret_cast(to->v);
 ^
In file included from mimetypes/qmimedatabase.cpp:48:0:
mimetypes/qmimeprovider_p.h:65:7: note: forward declaration of 'class 
QMimeMagicRuleMatcher'
 class QMimeMagicRuleMatcher;
   ^
In file included from ../../include/QtCore/qlist.h:1:0,
 from 
../../include/QtCore/../../src/corelib/kernel/qobject.h:49,
 from ../../include/QtCore/qobject.h:1,
 from 
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:46,
 from ../../include/QtCore/qcoreapplication.h:1,
 from global/qt_pch.h:62:
../../include/QtCore/../../src/corelib/tools/qlist.h:490:31: note: neither the 
destructor nor the class-specific operator delete will be called, even if they 
are declared when the class is defined
 while(from != to) --to, delete reinterpret_cast(to->v);
../../include/QtCore/../../src/corelib/tools/qlist.h:492:61: error: invalid use 
of incomplete type 'class QMimeMagicRuleMatcher'
 while (from != to) --to, reinterpret_cast(to)->~T();
  ~~~^
In file included from mimetypes/qmimedatabase.cpp:48:0:

Bug#853588: marked as done (opencv: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 18:06:25 +0300
with message-id <20170818150625.vwcbadmfsazfkfve@localhost>
and subject line opencv in experimental builds fine with gcc 7
has caused the Debian Bug report #853588,
regarding opencv: 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.)


-- 
853588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 

Bug#853431: marked as done (gpgme1.0: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 18:00:00 +0300
with message-id <2017081815.x6wqopicx4ic3zhy@localhost>
and subject line gpgme1.0 1.9.0 builds with gcc 7
has caused the Debian Bug report #853431,
regarding gpgme1.0: 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.)


-- 
853431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gpgme1.0
Version: 1.8.0-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/gpgme1.0_1.8.0-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[6]: *** [qgpgmebackend.lo] Error 1
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../lang/cpp/src 
-I../../../src -I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/include/x86_64-linux-gnu/qt5 -fpic -DBUILDING_QGPGME -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c multideletejob.cpp 
-o multideletejob.o >/dev/null 2>&1
qgpgmechangeexpiryjob.cpp: In member function 'virtual GpgME::Error 
QGpgME::QGpgMEChangeExpiryJob::start(const GpgME::Key&, const QDateTime&)':
qgpgmechangeexpiryjob.cpp:81:14: error: 'bind' is not a member of 'std'
 run(std::bind(_expiry, std::placeholders::_1, key, expiry));
  ^~~~
qgpgmechangeexpiryjob.cpp:81:14: note: suggested alternative: 'find'
 run(std::bind(_expiry, std::placeholders::_1, key, expiry));
  ^~~~
  find
qgpgmechangeexpiryjob.cpp:81:40: error: 'std::placeholders' has not been 
declared
 run(std::bind(_expiry, std::placeholders::_1, key, expiry));
^~~~
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../lang/cpp/src 
-I../../../src -I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/include/x86_64-linux-gnu/qt5 -fpic -DBUILDING_QGPGME -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
qgpgmesecretkeyexportjob.cpp -o qgpgmesecretkeyexportjob.o >/dev/null 2>&1
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../lang/cpp/src 
-I../../../src -I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/include/x86_64-linux-gnu/qt5 -fpic -DBUILDING_QGPGME -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
gpgme_backend_debug.cpp -o gpgme_backend_debug.o >/dev/null 2>&1
In file included from qgpgmechangeexpiryjob.h:39:0,
 from qgpgmechangeexpiryjob.cpp:38:
threadedjobmixin.h: In instantiation of 'void 
QGpgME::_detail::Thread::run() [with T_result = 
std::tuple]':
qgpgmechangeexpiryjob.moc:111:1:   required from here
threadedjobmixin.h:113:30: error: 'm_function' was not declared in this scope
 m_result = m_function();
~~^~
threadedjobmixin.h:113:30: note: suggested alternative: 'setFunction'
 m_result = m_function();
~~^~
setFunction
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../lang/cpp/src 
-I../../../src -I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/include/x86_64-linux-gnu/qt5 -fpic -DBUILDING_QGPGME -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
qgpgmerefreshkeysjob.cpp -o 

Bug#853422: marked as done (glogg: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 17:08:22 +0300
with message-id <20170818140822.d5xdhniagc6m5rlj@localhost>
and subject line glogg builds in unstable
has caused the Debian Bug report #853422,
regarding glogg: 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.)


-- 
853422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glogg
Version: 1.1.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/glogg_1.1.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

[...]
src/session.cpp:64:22: error: expected ',' or '...' before '<' token
 std::function view_factory )
  ^
src/session.cpp: In member function 'ViewInterface* Session::open(const 
string&, int)':
src/session.cpp:70:39: error: 'view_factory' was not declared in this scope
 return openAlways( file_name, view_factory, nullptr );
   ^~~~
src/session.cpp: At global scope:
src/session.cpp:116:14: error: 
'std::vector > 
Session::restore' is not a static data member of 'class Session'
 std::function view_factory,
  ^~~~
src/session.cpp:116:14: error: 'function' is not a member of 'std'
src/session.cpp:116:14: note: suggested alternative: 'is_function'
 std::function view_factory,
  ^~~~
  is_function
src/session.cpp:116:36: error: expected primary-expression before '*' token
 std::function view_factory,
^
src/session.cpp:116:38: error: expected primary-expression before ')' token
 std::function view_factory,
  ^
src/session.cpp:116:41: error: 'view_factory' was not declared in this scope
 std::function view_factory,
 ^~~~
src/session.cpp:117:9: error: expected primary-expression before 'int'
 int *current_file_index )
 ^~~
src/session.cpp:118:1: error: expected ',' or ';' before '{' token
 {
 ^
src/session.cpp:175:14: error: 'std::function' has not been declared
 std::function view_factory,
  ^~~~
src/session.cpp:175:22: error: expected ',' or '...' before '<' token
 std::function view_factory,
  ^
src/session.cpp: In member function 'ViewInterface* Session::openAlways(const 
string&, int)':
src/session.cpp:183:27: error: 'view_factory' was not declared in this scope
 ViewInterface* view = view_factory();
   ^~~~
src/session.cpp:188:10: error: 'view_context' was not declared in this scope
 if ( view_context )
  ^~~~
Makefile:827: recipe for target '.obj/release-shared/session.o' failed
make[1]: *** [.obj/release-shared/session.o] Error 1
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
--- End Message ---
--- Begin Message ---
glogg builds in unstable:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/glogg.html

cu
Adrian

-- 

   "Is there 

Bug#853647: Upstream fix for the rsbackup FTBFS with gcc 7

[Adrian Bunk]

Control: tags -1 patch fixed-upstream

The upstream fix for the rsbackup FTBFS with gcc 7 is attached.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

>From 2faba794de0d08487d280d85870d294339a138f4 Mon Sep 17 00:00:00 2001
From: Richard Kettlewell 
Date: Sat, 5 Aug 2017 14:02:21 +0100
Subject: Add [[noreturn]] attributes to version/help functions

--- a/src/Command.h
+++ b/src/Command.h
@@ -140,10 +140,10 @@ public:
 
 private:
   /** @brief Display help message and terminate */
-  void help();
+  [[noreturn]] void help();
 
   /** @brief Display version string and terminate */
-  void version();
+  [[noreturn]] void version();
 };
 
 /** @brief Program command line */

Processed: Upstream fix for the bwm-ng FTBFS with gcc 7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream patch
Bug #853339 [src:bwm-ng] bwm-ng: ftbfs with GCC-7
Added tag(s) patch and fixed-upstream.

-- 
853339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853339: Upstream fix for the bwm-ng FTBFS with gcc 7

[Adrian Bunk]

Control: tags -1 fixed-upstream patch

The upstream fix for the bwm-ng FTBFS with gcc 7 is attached.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

>From d5daf15c2098040b8b01753d3cdce8c1c79fc528 Mon Sep 17 00:00:00 2001
From: David Seifert 
Date: Fri, 10 Feb 2017 21:30:49 +0100
Subject: Use `static inline` instead of `inline`

`inline` by itself is not portably guaranteed to emit
an external definition when needed in C99. The current
code base implicitly relies on GNU89 inline semantics,
which _always_ emit an external definition. More recent
versions of GCC and Clang switch to C99/C11 inline semantics
by default, which fails with undefined references.

See also:
* http://www.greenend.org.uk/rjk/tech/inline.html
* https://clang.llvm.org/compatibility.html#inline
* http://blahg.josefsipek.net/?p=529
---
 src/bwm-ng.c  |  4 ++--
 src/help.c|  4 ++--
 src/options.c | 16 
 src/output.c  | 22 +++---
 src/process.c | 28 ++--
 5 files changed, 37 insertions(+), 37 deletions(-)

Index: bwm-ng-0.6.1/src/bwm-ng.c
===
--- bwm-ng-0.6.1.orig/src/bwm-ng.c
+++ bwm-ng-0.6.1/src/bwm-ng.c
@@ -26,7 +26,7 @@
 
 /* handle interrupt signal */
 void sigint(int sig) FUNCATTR_NORETURN;
-inline void init(void);
+static inline void init(void);
 
 /* clear stuff and exit */
 #ifdef __STDC__
@@ -98,7 +98,7 @@ void sigint(int sig) {
 	deinit(0, NULL);
 }
 
-inline void init(void) {
+static inline void init(void) {
 	if_count=0;
 	delay=500;
 #if EXTENDED_STATS	
Index: bwm-ng-0.6.1/src/help.c
===
--- bwm-ng-0.6.1.orig/src/help.c
+++ bwm-ng-0.6.1/src/help.c
@@ -24,9 +24,9 @@
 #include "global_vars.h"
 #include "help.h"
 
-inline void print_help_line(const char *short_c,const char * long_c,const char *descr);
+static inline void print_help_line(const char *short_c,const char * long_c,const char *descr);
 
-inline void print_help_line(const char *short_c,const char * long_c,const char *descr) {
+static inline void print_help_line(const char *short_c,const char * long_c,const char *descr) {
 #ifdef LONG_OPTIONS
 printf("  %-23s",long_c);
 #else
Index: bwm-ng-0.6.1/src/options.c
===
--- bwm-ng-0.6.1.orig/src/options.c
+++ bwm-ng-0.6.1/src/options.c
@@ -30,12 +30,12 @@ static char* getToken(char** str, const
 char *trim_whitespace(char *str);
 int read_config(const char *config_file);
 #endif
-inline int str2output_unit(char *optarg);
+static inline int str2output_unit(char *optarg);
 #if EXTENDED_STATS
-inline int str2output_type(char *optarg);
+static inline int str2output_type(char *optarg);
 #endif
-inline int str2out_method(char *optarg);
-inline int str2in_method(char *optarg);
+static inline int str2out_method(char *optarg);
+static inline int str2in_method(char *optarg);
 
 #ifdef CONFIG_FILE
  /**
@@ -65,7 +65,7 @@ static char* getToken(char** str, const
 /**/
 #endif
 
-inline int str2output_unit(char *optarg) {
+static inline int str2output_unit(char *optarg) {
 if (optarg) {
 if (!strcasecmp(optarg,"bytes")) return BYTES_OUT;
 if (!strcasecmp(optarg,"bits")) return BITS_OUT;
@@ -76,7 +76,7 @@ inline int str2output_unit(char *optarg)
 }
 
 #if EXTENDED_STATS
-inline int str2output_type(char *optarg) {
+static inline int str2output_type(char *optarg) {
 if (optarg) {
 if (!strcasecmp(optarg,"rate")) return RATE_OUT;
 if (!strcasecmp(optarg,"max")) return MAX_OUT;
@@ -87,7 +87,7 @@ inline int str2output_type(char *optarg)
 }
 #endif  
 
-inline int str2out_method(char *optarg) {
+static inline int str2out_method(char *optarg) {
 if (optarg) {
 if (!strcasecmp(optarg,"plain")) return PLAIN_OUT;
 #ifdef HAVE_CURSES
@@ -109,7 +109,7 @@ inline int str2out_method(char *optarg)
 }
 
 
-inline int str2in_method(char *optarg) {
+static inline int str2in_method(char *optarg) {
 if (optarg) {
 #ifdef PROC_NET_DEV
 if (!strcasecmp(optarg,"proc")) return PROC_IN;
Index: bwm-ng-0.6.1/src/output.c
===
--- bwm-ng-0.6.1.orig/src/output.c
+++ bwm-ng-0.6.1/src/output.c
@@ -25,13 +25,13 @@
 #include "output.h"
 
 inline static const char *output_type2str(void);
-inline const char *input2str(void);
-inline const char *show_all_if2str(void);
-inline ullong direction2value(char mode,struct inout_long stats);
+static inline const char *input2str(void);
+static inline const char *show_all_if2str(void);

Processed: Upstream fix for the rsbackup FTBFS with gcc 7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #853647 [src:rsbackup] rsbackup: ftbfs with GCC-7
Added tag(s) patch and fixed-upstream.

-- 
853647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853400: marked as done (fgetty: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 13:49:05 +
with message-id 
and subject line Bug#853400: fixed in fgetty 0.7-2.1
has caused the Debian Bug report #853400,
regarding fgetty: 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.)


-- 
853400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fgetty
Version: 0.7-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/fgetty_0.7-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

[...]
 dpkg-source -b fgetty-0.7
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building fgetty using existing ./fgetty_0.7.orig.tar.bz2
dpkg-source: info: building fgetty in fgetty_0.7-2.debian.tar.xz
dpkg-source: info: building fgetty in fgetty_0.7-2.dsc
 debian/rules build
dh build
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
diet -Os cc -pipe -Os -fomit-frame-pointer -I../dietlibc/include -c fgetty.c 
-DTEST
fgetty.c: In function 'main':
fgetty.c:278:12: warning: implicit declaration of function 'isdigit' 
[-Wimplicit-function-declaration]
   else if (isdigit(tty[0])) {
^~~
diet -Os cc -pipe -Os -fomit-frame-pointer -I../dietlibc/include -c fmt_ulong.c 
-DTEST
diet -Os cc -o fgetty fgetty.o fmt_ulong.o
diet -Os cc -pipe -Os -fomit-frame-pointer -I../dietlibc/include -c login.c 
-DTEST
login.c:61:1: warning: return type defaults to 'int' [-Wimplicit-int]
 main(int argc,char *argv[]) {
 ^~~~
diet -Os cc -o login login.o
diet -Os cc -pipe -Os -fomit-frame-pointer -I../dietlibc/include -c login2.c 
-DTEST
login2.c:59:1: warning: return type defaults to 'int' [-Wimplicit-int]
 main(int argc,char *argv[]) {
 ^~~~
diet -Os cc -o login2 login2.o
gcc -Os -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
checkpassword.c -lcrypt -Wl,-z,relro -Wl,-z,now -o checkpassword
checkpassword.c: In function 'main':
checkpassword.c:75:11: warning: implicit declaration of function 'initgroups'; 
did you mean 'getgroups'? [-Wimplicit-function-declaration]
   if (initgroups(pw->pw_name,pw->pw_gid)==-1) return 1;
   ^~
   getgroups
checkpassword.c: In function '__write2':
checkpassword.c:12:3: warning: ignoring return value of 'write', declared with 
attribute warn_unused_result [-Wunused-result]
   write(2,message,strlen(message));
   ^~~~
/tmp/ccmIgk03.o: In function `main':
./checkpassword.c:89: undefined reference to `__write2'
collect2: error: ld returned 1 exit status
Makefile:24: recipe for target 'checkpassword' failed
make[1]: *** [checkpassword] Error 1
make[1]: Leaving directory '/<>'
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
--- End Message ---
--- Begin Message ---
Source: fgetty
Source-Version: 0.7-2.1

We believe that the bug you reported is fixed in the latest version of
fgetty, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 853...@bugs.debian.org,

Bug#872555: fcitx: 在gnome不能切换输入法，在xfce可以

[zaoqi]

Package: fcitx
Version: 1:4.2.9.1-6
Severity: grave
Justification: renders package unusable

在gnome不能切换输入法，在xfce可以



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fcitx depends on:
ii  fcitx-bin  1:4.2.9.1-6
ii  fcitx-data 1:4.2.9.1-6
ii  fcitx-modules  1:4.2.9.1-6

Versions of packages fcitx recommends:
ii  fcitx-config-gtk   0.4.8-3+b1
ii  fcitx-frontend-all 1:4.2.9.1-6
ii  fcitx-ui-classic   1:4.2.9.1-6
ii  im-config [im-switch]  0.30-1

Versions of packages fcitx suggests:
pn  fcitx-m17n   
pn  fcitx-tools  

-- no debconf information

Bug#872553: synaptic: Segmentation fault

[zaoqi]

Package: synaptic
Version: 0.84.2
Severity: grave
Tags: security
Justification: renders package unusable

Segmentation fault



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN:zh (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.15-1
ii  libapt-inst2.0   1.5~beta2
ii  libapt-pkg5.01.5~beta2
ii  libatk1.0-0  2.24.0-1
ii  libc62.24-14
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:7.1.0-13
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.53.4-3
ii  libgnutls30  3.5.14-2
ii  libgtk-3-0   3.22.18-1
ii  libpango-1.0-0   1.40.9-1
ii  libpangocairo-1.0-0  1.40.9-1
ii  libpcre2-8-0 10.22-3
ii  libstdc++6   7.1.0-13
ii  libvte-2.91-00.46.2-1
ii  libx11-6 2:1.6.4-3
ii  libxapian30  1.4.4-2
ii  policykit-1  0.105-18
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages synaptic recommends:
ii  libgtk2-perl   2:1.24992-1+b1
ii  rarian-compat  0.8.1-6+b1
ii  xdg-utils  1.1.1-1

Versions of packages synaptic suggests:
pn  apt-xapian-index 
pn  deborphan
pn  dwww 
pn  menu 
ii  software-properties-gtk  0.96.20.2-1
ii  tasksel  3.39

-- no debconf information

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 853395 src:gcc-7
Bug #853395 [src:fastd] fastd: ftbfs with GCC-7
Bug reassigned from package 'src:fastd' to 'src:gcc-7'.
No longer marked as found in versions fastd/18-2.
Ignoring request to alter fixed versions of bug #853395 to the same values 
previously set
> forcemerge 853537 853395
Bug #853537 [src:gcc-7] binutils: /usr/bin/gcc-ar segfaults
Bug #853610 [src:gcc-7] pesign: ftbfs with GCC-7
Bug #853395 [src:gcc-7] fastd: ftbfs with GCC-7
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR81829'.
Added indication that 853395 affects src:mariadb-10.1,src:pesign
Added tag(s) upstream.
Bug #853610 [src:gcc-7] pesign: ftbfs with GCC-7
Merged 853395 853537 853610
> affects 853537 src:fastd
Bug #853537 [src:gcc-7] binutils: /usr/bin/gcc-ar segfaults
Bug #853395 [src:gcc-7] fastd: ftbfs with GCC-7
Bug #853610 [src:gcc-7] pesign: ftbfs with GCC-7
Added indication that 853537 affects src:fastd
Added indication that 853395 affects src:fastd
Added indication that 853610 affects src:fastd
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
853395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853395
853537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853537
853610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872539: marked as done (qt5-style-plugins: fails to install on Sid)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 15:36:06 +0300
with message-id <20170818123606.o4vxt6pivxqqprvf@localhost>
and subject line Re: Bug#872539: qt5-style-plugins: fails to install on Sid
has caused the Debian Bug report #872539,
regarding qt5-style-plugins: fails to install on Sid
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.)


-- 
872539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qt5-style-plugins
Version: 5.0.0+git23.g335dbec-2
Severity: grave
Justification: renders package unusable

Hi!
Since qt5 in Debian Sid got updated to 5.9, qt5-style-plugins is no
longer installable due to its dependency on qtbase-abi-5-7-1 that is no
longer provided.

Here is what I get from APT when I try to install it on a fresh Sid:

root@HAL9000:~# apt install qt5-style-plugins
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 qt5-style-plugins : Depends: qtbase-abi-5-7-1 but it is not installable
 E: Unable to correct problems, you have held broken packages.


On a Debian Sid with Qt 5.7, qt5-style-plugins will block the upgrade of
qt5 packages to 5.9 unless you remove it prior to upgrading. If you use
'full-upgrade' it will be automatically removed during the upgrade, so
this is not a "hard" blocker.

I assigned a severity of 'grave' to this report because the package is
no longer installable on a freshly installed Sid, feel free to lower the
severity if you don’t think this is enough to warrant this high
severity.

Thanks in advance for looking into this, and please tell me if I can do
anything to help resolve this issue ;)

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qt5-style-plugins depends on:
ii  libc62.24-14
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.53.4-3
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.9-1
ii  libqt5core5a [qtbase-abi-5-7-1]  5.7.1+dfsg-4
ii  libqt5dbus5  5.7.1+dfsg-4
ii  libqt5gui5   5.7.1+dfsg-4
ii  libqt5widgets5   5.7.1+dfsg-4
ii  libstdc++6   7.1.0-13
ii  libx11-6 2:1.6.4-3

qt5-style-plugins recommends no packages.

qt5-style-plugins suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Aug 18, 2017 at 10:51:41AM +0200, vv221 wrote:
>...
> On a Debian Sid with Qt 5.7, qt5-style-plugins will block the upgrade of
> qt5 packages to 5.9 unless you remove it prior to upgrading. If you use
> 'full-upgrade' it will be automatically removed during the upgrade, so
> this is not a "hard" blocker.
>...

Thanks for your report.

The transition from Qt 5.7 to 5.9 in unstable has just started,
and such temporary breakage is expected in unstable.

I am closing this bug since this will be handled during the next
days as part of the transition without necessarily requiring any
action by the maintainer.

You can follow the status of the Qt 5.7 -> 5.9 transition at
  https://release.debian.org/transitions/html/qtbase-abi-5-9-0.html

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#872549: clasp FTBFS on armel: undefined reference to `__atomic_load_8'

[Adrian Bunk]

Source: clasp
Version: 3.3.2-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=clasp=armel=3.3.2-1=1503036865=0

...
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -DNDEBUG 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -Wl,-z,relro 
-Wl,-z,now -rdynamic CMakeFiles/test_clasp.dir/clause_creator_test.cpp.o 
CMakeFiles/test_clasp.dir/clause_test.cpp.o 
CMakeFiles/test_clasp.dir/cli_test.cpp.o 
CMakeFiles/test_clasp.dir/decision_heuristic_test.cpp.o 
CMakeFiles/test_clasp.dir/dependency_graph_test.cpp.o 
CMakeFiles/test_clasp.dir/dlp_builder_test.cpp.o 
CMakeFiles/test_clasp.dir/enumerator_test.cpp.o 
CMakeFiles/test_clasp.dir/facade_test.cpp.o 
CMakeFiles/test_clasp.dir/literal_test.cpp.o 
CMakeFiles/test_clasp.dir/minimize_test.cpp.o 
CMakeFiles/test_clasp.dir/parser_test.cpp.o 
CMakeFiles/test_clasp.dir/program_builder_test.cpp.o 
CMakeFiles/test_clasp.dir/rule_test.cpp.o 
CMakeFiles/test_clasp.dir/satelite_test.cpp.o 
CMakeFiles/test_clasp.dir/solver_test.cpp.o 
CMakeFiles/test_clasp.dir/test_main.cpp.o CMakeFiles/test_cla
 sp.dir/unfounded_check_test.cpp.o 
CMakeFiles/test_clasp.dir/weight_constraint_test.cpp.o  -o ../bin/test_clasp 
../lib/libclasp.a -lpthread ../lib/libpotassco.a 
../lib/libclasp.a(minimize_constraint.cpp.o): In function 
`std::__atomic_base::load(std::memory_order) const':
/usr/include/c++/7/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
../lib/libclasp.a(minimize_constraint.cpp.o): In function 
`std::__atomic_base::store(long long, std::memory_order)':
/usr/include/c++/7/bits/atomic_base.h:374: undefined reference to 
`__atomic_store_8'
../lib/libclasp.a(minimize_constraint.cpp.o): In function 
`std::__atomic_base::compare_exchange_strong(long long&, long long, 
std::memory_order, std::memory_order)':
/usr/include/c++/7/bits/atomic_base.h:477: undefined reference to 
`__atomic_compare_exchange_8'
../lib/libclasp.a(minimize_constraint.cpp.o): In function 
`std::__atomic_base::load(std::memory_order) const':
/usr/include/c++/7/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
/usr/include/c++/7/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
/usr/include/c++/7/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
/usr/include/c++/7/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
../lib/libclasp.a(minimize_constraint.cpp.o): In function 
`std::__atomic_base::store(long long, std::memory_order)':
/usr/include/c++/7/bits/atomic_base.h:374: undefined reference to 
`__atomic_store_8'
../lib/libclasp.a(minimize_constraint.cpp.o): In function 
`std::__atomic_base::operator+=(long long)':
/usr/include/c++/7/bits/atomic_base.h:312: undefined reference to 
`__atomic_fetch_add_8'
../lib/libclasp.a(minimize_constraint.cpp.o): In function 
`std::__atomic_base::load(std::memory_order) const':
/usr/include/c++/7/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
../lib/libclasp.a(minimize_constraint.cpp.o): In function 
`std::__atomic_base::compare_exchange_strong(long long&, long long, 
std::memory_order, std::memory_order)':
/usr/include/c++/7/bits/atomic_base.h:477: undefined reference to 
`__atomic_compare_exchange_8'
../lib/libclasp.a(minimize_constraint.cpp.o): In function 
`std::__atomic_base::load(std::memory_order) const':
/usr/include/c++/7/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
../lib/libclasp.a(minimize_constraint.cpp.o): In function 
`std::__atomic_base::compare_exchange_strong(long long&, long long, 
std::memory_order, std::memory_order)':
/usr/include/c++/7/bits/atomic_base.h:477: undefined reference to 
`__atomic_compare_exchange_8'
../lib/libclasp.a(minimize_constraint.cpp.o): In function 
`std::__atomic_base::load(std::memory_order) const':
/usr/include/c++/7/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
../lib/libclasp.a(parallel_solve.cpp.o): In function 
`std::__atomic_base::store(unsigned long long, 
std::memory_order)':
/usr/include/c++/7/bits/atomic_base.h:374: undefined reference to 
`__atomic_store_8'
../lib/libclasp.a(parallel_solve.cpp.o): In function 
`std::__atomic_base::load(std::memory_order) const':
/usr/include/c++/7/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
../lib/libclasp.a(parallel_solve.cpp.o): In function 
`std::__atomic_base::fetch_or(unsigned long long, 
std::memory_order)':
/usr/include/c++/7/bits/atomic_base.h:544: undefined reference to 
`__atomic_fetch_or_8'
../lib/libclasp.a(parallel_solve.cpp.o): In function 
`std::__atomic_base::load(std::memory_order) const':
/usr/include/c++/7/bits/atomic_base.h:396: undefined reference to 
`__atomic_load_8'
../lib/libclasp.a(parallel_solve.cpp.o): In function 
`std::__atomic_base::exchange(unsigned long long, 
std::memory_order)':
/usr/include/c++/7/bits/atomic_base.h:413: undefined reference to 
`__atomic_exchange_8'

Bug#872547: mapnik-reference FTBFS with nodejs 6.11.2

[Adrian Bunk]

Source: mapnik-reference
Version: 5.0.6-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mapnik-reference.html

...
   dh_auto_build
dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
make -j1
make[1]: Entering directory '/build/1st/mapnik-reference-5.0.6'
nodejs util/make-datasource-ref.js latest/datasources.template > 
latest/datasources.json
path.js:7
throw new TypeError('Path must be a string. Received ' + inspect(path));
^

TypeError: Path must be a string. Received [ 
'/build/1st/mapnik-reference-5.0.6/util/make-datasource-ref.js' ]
at assertPath (path.js:7:11)
at Object.basename (path.js:1355:5)
at Object. 
(/build/1st/mapnik-reference-5.0.6/util/make-datasource-ref.js:9:16)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:389:7)
Makefile:4: recipe for target 'latest/datasources.json' failed
make[1]: *** [latest/datasources.json] Error 1
make[1]: Leaving directory '/build/1st/mapnik-reference-5.0.6'
dh_auto_build: make -j1 returned exit code 2
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2

Bug#872542: qtwebkit-opensource-src: FTBFS on various release archs (i386, armel, armhf)

[Dmitry Shachnev]

Hi Gert!

On Fri, Aug 18, 2017 at 09:51:34AM +, Gert Wollny wrote:
> Source: qtwebkit-opensource-src
> Version: 5.9.1+dfsg-3
> Severity: serious
> Justification: FTBFS but build before
>
> Dear Maintainer,
>
> As can be seen from the build status, the package fails to build on these 
> release archs 
> as well as some non-release archs. 
>
> https://buildd.debian.org/status/package.php?p=qtwebkit-opensource-src=unstable
>
> Unfortunately the logs seem to be cut off before the actual error is reported

The i386 failure is already fixed in Git, will be in the next upload.

The armel/armhf failure is actually a bug in binutils, #852035, we are waiting
for the maintainer’s response there.

The issue with insane size of build logs is fixed in Git too.

--
Dmitry Shachnev

Processed: Re: Bug#871656: apt-offline: Does not validate Packages or .deb files in bundle

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +confirmed
Bug #871656 [apt-offline] apt-offline: Does not validate Packages or .deb files 
in bundle
Added tag(s) confirmed.
> severity -1 serious
Bug #871656 [apt-offline] apt-offline: Does not validate Packages or .deb files 
in bundle
Severity set to 'serious' from 'normal'
> tag -1 -moreinfo
Bug #871656 [apt-offline] apt-offline: Does not validate Packages or .deb files 
in bundle
Removed tag(s) moreinfo.

-- 
871656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872517: ffmpeg: CVE-2017-7206: heap-based buffer over-read in embed libav

[James Cowgill]

Hi,

On 18/08/17 03:46, Luciano Bello wrote:
> Package: ffmpeg
> X-Debbugs-CC: t...@security.debian.org secure-testing-
> t...@lists.alioth.debian.org
> Severity: grave
> Tags: security
> 
> Hi,
> 
> the following vulnerability was published for libav (which is embed in 
> ffmpeg).
> 
> CVE-2017-7206[0]:
> | The ff_h2645_extract_rbsp function in libavcodec in libav 9.21 allows
> | remote attackers to cause a denial of service (heap-based buffer
> | over-read) or obtain sensitive information from process memory via a
> | crafted h264 video file.
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2017-7206
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7206

The testcases from the libav bugreport don't seem to cause ffmpeg 3.3.3
or 3.2.5 to crash. However, the ffmpeg code looks very similar to the
code in libav before the fix, so ffmpeg might be affected but require a
slightly different testcase?

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#868609: le FTBFS with latest ncurses

[Raphael Geissert]

Alexander,

Do you plan to make a new release with the fixes? or should I grab the
patches from github?

I'd like to fix this some time soon to get le back in testing.

Thanks in advance.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net

Processed: Re: Bug#871656: apt-offline: Does not validate Packages or .deb files in bundle

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #871656 [apt-offline] apt-offline: Does not validate Packages or .deb files 
in bundle
Severity set to 'normal' from 'serious'
> tag -1 +moreinfo
Bug #871656 [apt-offline] apt-offline: Does not validate Packages or .deb files 
in bundle
Added tag(s) moreinfo.

-- 
871656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871656: apt-offline: Does not validate Packages or .deb files in bundle

[Ritesh Raj Sarraf]

Control: severity -1 normal
Control: tag -1 +moreinfo

Hello Stuart,

On Thu, 2017-08-10 at 23:17 +1000, Stuart Prescott wrote:
> apt-offline claims to do gpg validation of the contents of the zip
> file and
> claims that this is an important thing for it to do.
> 
>     --allow-unauthenticated
>  Don't  verify  GPG signatures for the data to be installed
> to APT.
>  Usage of this option is highly discouraged.
> 
> However, it appears that apt-offline only verifies the GPG signature
> on the
> Release file. If that check passes, then it is assumed that all
> referenced
> resources (Packages files) are OK and apt-offline does not check that
> the
> hashes for the Packages files are indeed correct.


Yes. We only check the Release file, which contains the checksum
details for the Packages file, which in turn contains the checksum
details for all data (.debs).


>  These Packages files are
> then fed directly to apt. Once apt has been fed a manipulated
> Packages file,
> it will then trust the .deb packages that it refers to.
> 

No. They aren't fed directly. We follow the same process that apt does.
 We sync them to the partial location and then apt do the verification.


> One can take a zip bundle, decompress it, alter the Packages file and
> the altered
> file was no rejected by "apt-offline install bundle.zip".
> 
> It seems that the existing GPG check of the Release file is rather
> pointless
> and gives a false sense of security validation. Either the bundle.zip
> has been
> securely handled all along and the GPG check is unnecessary, or
> bundle.zip has
> not been securely handled and it is incorrectly trusted.


Let's take a deb example here:

rrs@priyasi:~$ sudo apt upgrade
[sudo] password for rrs: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer
required:
  snap-confine ubuntu-core-launcher
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
  inkscape libgsl2
The following packages will be upgraded:
  linux-libc-dev
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B/1,331 kB of archives.
After this operation, 24.6 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
15:51 ♒♒♒☹  => 1  

rrs@priyasi:~$ apt policy linux-libc-dev
linux-libc-dev:
  Installed: 4.12.8+-45
  Candidate: 4.13~rc5-1~exp1
  Version table:
 4.13~rc5-1~exp1 100
100 http://deb.debian.org/debian experimental/main amd64
Packages
 *** 4.12.8+-45 100
100 /var/lib/dpkg/status
 4.12.6-1 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
 4.11.6-1 900
900 http://deb.debian.org/debian testing/main amd64 Packages
15:51 ♒♒♒   ☺

rrs@priyasi:~$ cd /var/cache/apt/archives/
15:51 ♒♒♒   ☺

rrs@priyasi:/var/cache/apt/archives$ ls -lh linux-libc-dev_4.13~rc5-
1~exp1_amd64.deb 
-rw-r--r-- 1 root root 1.3M Aug 17 01:24 linux-libc-dev_4.13~rc5-
1~exp1_amd64.deb
15:51 ♒♒♒   ☺

rrs@priyasi:/var/cache/apt/archives$ su -c "echo abc > linux-libc-
dev_4.13~rc5-1~exp1_amd64.deb "
Password: 
15:52 ♒♒♒   ☺

rrs@priyasi:/var/cache/apt/archives$ ls -lh linux-libc-dev_4.13~rc5-
1~exp1_amd64.deb -rw-r--r-- 1 root root 4 Aug 18 15:52 linux-libc-
dev_4.13~rc5-1~exp1_amd64.deb
15:52 ♒♒♒   ☺

rrs@priyasi:/var/cache/apt/archives$ sudo apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer
required:
  snap-confine ubuntu-core-launcher
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
  inkscape libgsl2
The following packages will be upgraded:
  linux-libc-dev
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 1,331 kB of archives.
After this operation, 24.6 kB disk space will be freed.
Do you want to continue? [Y/n] ^C
15:58 ♒♒♒☹  => 130  


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

signature.asc
Description: This is a digitally signed message part

Bug#867645: marked as done (ruby-influxdb: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: http.request(req))

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 10:19:40 +
with message-id 
and subject line Bug#867645: fixed in ruby-influxdb 0.3.16-1
has caused the Debian Bug report #867645,
regarding ruby-influxdb: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: 
http.request(req)
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.)


-- 
867645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-influxdb
Version: 0.2.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  Failure/Error: http.request(req)
> 
>  WebMock::NetConnectNotAllowedError:
>Real HTTP connections are disabled. Unregistered request: POST 
> http://influxdb.test:/ with body '{}' with headers {'Accept'=>'*/*', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'Authorization'=>'Basic dXNlcm5hbWU6cGFzc3dvcmQ=', 
> 'Content-Type'=>'application/octet-stream', 'User-Agent'=>'Ruby'}
> 
>You can stub this request with the following snippet:
> 
>stub_request(:post, "http://influxdb.test:/;).
>  with(body: {},
>   headers: {'Accept'=>'*/*', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'Authorization'=>'Basic dXNlcm5hbWU6cGFzc3dvcmQ=', 
> 'Content-Type'=>'application/octet-stream', 'User-Agent'=>'Ruby'}).
>  to_return(status: 200, body: "", headers: {})
> 
>registered request stubs:
> 
>stub_request(:post, "http://username:passw...@influxdb.test:/;)
> 
>
>  # ./lib/influxdb/client/http.rb:72:in `do_request'
>  # ./lib/influxdb/client/http.rb:26:in `block in post'
>  # ./lib/influxdb/client/http.rb:52:in `connect_with_retry'
>  # ./lib/influxdb/client/http.rb:25:in `post'
>  # ./spec/influxdb/client_spec.rb:35:in `block (3 levels) in  (required)>'
> 
> Finished in 0.17528 seconds (files took 0.65682 seconds to load)
> 117 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/influxdb/client_spec.rb:28 # InfluxDB::Client with basic auth GET
> rspec ./spec/influxdb/client_spec.rb:33 # InfluxDB::Client with basic auth 
> POST
> 
> /usr/bin/ruby2.3 /usr/bin/rspec ./spec/influxdb/cases/query_cluster_spec.rb 
> ./spec/influxdb/cases/query_continuous_query_spec.rb 
> ./spec/influxdb/cases/query_database_spec.rb 
> ./spec/influxdb/cases/query_retention_policy_spec.rb 
> ./spec/influxdb/cases/query_series_spec.rb 
> ./spec/influxdb/cases/query_shard_space_spec.rb 
> ./spec/influxdb/cases/query_shard_spec.rb 
> ./spec/influxdb/cases/query_user_spec.rb 
> ./spec/influxdb/cases/querying_spec.rb 
> ./spec/influxdb/cases/retry_requests_spec.rb 
> ./spec/influxdb/cases/udp_client_spec.rb 
> ./spec/influxdb/cases/write_points_spec.rb ./spec/influxdb/client_spec.rb 
> ./spec/influxdb/config_spec.rb ./spec/influxdb/logging_spec.rb 
> ./spec/influxdb/max_queue_spec.rb ./spec/influxdb/point_value_spec.rb 
> ./spec/influxdb/worker_spec.rb --format documentation failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/07/07/ruby-influxdb_0.2.3-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-influxdb
Source-Version: 0.3.16-1

We believe that the bug you reported is fixed in the latest version of
ruby-influxdb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 867...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-influxdb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing 

Bug#867645: marked as pending

[Pirate Praveen]

tag 867645 pending
thanks

Hello,

Bug #867645 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-influxdb.git/commit/?id=4270482

---
commit 4270482a8a7012fd33d52e109e660d0230a245b3
Author: Pirate Praveen 
Date:   Fri Aug 18 15:17:53 2017 +0530

upload to experimental

diff --git a/debian/changelog b/debian/changelog
index cafd0ce..8da6185 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+ruby-influxdb (0.3.16-1) experimental; urgency=medium
+
+  * New upstream release (Closes: #867645)
+  * Drop patch: no-cause-for-ruby-2.1.patch (fixed upstream)
+
+ -- Pirate Praveen   Fri, 18 Aug 2017 15:17:12 +0530
+
 ruby-influxdb (0.2.3-1) unstable; urgency=medium
 
   * Initial release (Closes: #811173)

Processed: Bug#867645 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 867645 pending
Bug #867645 [src:ruby-influxdb] ruby-influxdb: FTBFS: ERROR: Test "ruby2.3" 
failed: Failure/Error: http.request(req)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
867645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: To fix this qt must be in a stable state in i386 first

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 872353 by 872542
Bug #872353 [itksnap] itksnap: FTBFS on i386: unconditionally expects SSE 
support
872353 was not blocked by any bugs.
872353 was not blocking any bugs.
Added blocking bug(s) of 872353: 872542
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
872353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872542: qtwebkit-opensource-src: FTBFS on various release archs (i386, armel, armhf)

[Gert Wollny]

Source: qtwebkit-opensource-src
Version: 5.9.1+dfsg-3
Severity: serious
Justification: FTBFS but build before

Dear Maintainer,

As can be seen from the build status, the package fails to build on these 
release archs 
as well as some non-release archs. 

https://buildd.debian.org/status/package.php?p=qtwebkit-opensource-src=unstable

Unfortunately the logs seem to be cut off before the actual error is reported

best regards, 
Gert 


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.11.7-gentoo-radeon (SMP w/6 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Bug#871070: marked as done (ms-gsl: FTBFS: multi_span:1191:57: error: conversion to 'long unsigned int' from 'long int' may change the sign of the result [-Werror=sign-conversion])

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 09:19:37 +
with message-id 
and subject line Bug#871070: fixed in ms-gsl 0~git20170602.1f87ef7-2
has caused the Debian Bug report #871070,
regarding ms-gsl: FTBFS: multi_span:1191:57: error: conversion to 'long 
unsigned int' from 'long int' may change the sign of the result 
[-Werror=sign-conversion]
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.)


-- 
871070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ms-gsl
Version: 0~git20170602.1f87ef7-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> cd "/<>/obj-x86_64-linux-gnu/tests" && /usr/bin/c++  
> -DGSL_THROW_ON_CONTRACT_VIOLATION -I"/<>" 
> -I"/<>/include" -I"/<>/tests/./unittest-cpp"  -g 
> -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -std=c++14 
> -fno-strict-aliasing -Wall -Wcast-align -Wconversion -Wctor-dtor-privacy 
> -Werror -Wextra -Wno-missing-braces -Wnon-virtual-dtor -Wold-style-cast 
> -Woverloaded-virtual -Wpedantic -Wshadow -Wsign-conversion -o 
> CMakeFiles/owner_tests.dir/owner_tests.cpp.o -c 
> "/<>/tests/owner_tests.cpp"
> In file included from /<>/include/gsl/gsl:24:0,
>  from /<>/tests/utils_tests.cpp:19:
> /<>/include/gsl/multi_span:1191:57: error: conversion to 'long 
> unsigned int' from 'long int' may change the sign of the result 
> [-Werror=sign-conversion]
>  struct is_multi_span_oracle> : 
> std::true_type
>  ^~~~
> /<>/include/gsl/multi_span:1301:88: error: conversion to 'long 
> int' from 'long unsigned int' may change the sign of the result 
> [-Werror=sign-conversion]
>  template  details::SpanArrayTraits>
>   
>   ^
> /<>/include/gsl/multi_span: In constructor 'constexpr 
> gsl::multi_span RestDimensions>::multi_span(std::array&)':
> /<>/include/gsl/multi_span:1324:61: error: conversion to 'long 
> int' from 'long unsigned int' may change the sign of the result 
> [-Werror=sign-conversion]
>  : multi_span(arr.data(), bounds_type{static_bounds{}})
>  ^
> /<>/include/gsl/multi_span:1329:58: error: conversion to 'long 
> int' from 'long unsigned int' may change the sign of the result 
> [-Werror=sign-conversion]
>  static_assert(std::is_convertible bounds_type>::value,
>   ^
> /<>/include/gsl/multi_span: In constructor 'constexpr 
> gsl::multi_span::multi_span(const 
> std::array&)':
> /<>/include/gsl/multi_span:1336:61: error: conversion to 'long 
> int' from 'long unsigned int' may change the sign of the result 
> [-Werror=sign-conversion]
>  : multi_span(arr.data(), bounds_type{static_bounds{}})
>  ^
> /<>/include/gsl/multi_span:1340:58: error: conversion to 'long 
> int' from 'long unsigned int' may change the sign of the result 
> [-Werror=sign-conversion]
>  static_assert(std::is_convertible bounds_type>::value,
>   ^
> In file included from /<>/include/gsl/gsl_algorithm:22:0,
>  from /<>/tests/algorithm_tests.cpp:19:
> /<>/include/gsl/span: In constructor 'constexpr 
> gsl::span::span(gsl::span Extent>::element_type (&)[N])':
> /<>/include/gsl/span:373:51: error: conversion to 'long int' 
> from 'long unsigned int' may change the sign of the result 
> [-Werror=sign-conversion]
>  : storage_([0], details::extent_type())
>^
> /<>/include/gsl/span: In constructor 'constexpr 
> gsl::span::span(std::array&)':
> /<>/include/gsl/span:379:51: error: conversion to 'long int' 
> from 'long unsigned int' may change the sign of the result 
> [-Werror=sign-conversion]
>  : storage_([0], details::extent_type())
>^

Bug#853303: marked as done (agg: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 09:04:10 +
with message-id 
and subject line Bug#853303: fixed in agg 1:2.4-r127+dfsg1-1
has caused the Debian Bug report #853303,
regarding agg: 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.)


-- 
853303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:agg
Version: 2.5+dfsg1-11
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/agg_2.5+dfsg1-11_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[5]: Nothing to be done for 'all'.
make[5]: Leaving directory 
'/<>/agg-2.5+dfsg1/obj-pic/src/platform/win32'
Making all in AmigaOS
make[5]: Entering directory 
'/<>/agg-2.5+dfsg1/obj-pic/src/platform/AmigaOS'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory 
'/<>/agg-2.5+dfsg1/obj-pic/src/platform/AmigaOS'
Making all in BeOS
make[5]: Entering directory 
'/<>/agg-2.5+dfsg1/obj-pic/src/platform/BeOS'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory 
'/<>/agg-2.5+dfsg1/obj-pic/src/platform/BeOS'
Making all in mac
make[5]: Entering directory 
'/<>/agg-2.5+dfsg1/obj-pic/src/platform/mac'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory 
'/<>/agg-2.5+dfsg1/obj-pic/src/platform/mac'
make[5]: Entering directory '/<>/agg-2.5+dfsg1/obj-pic/src/platform'
make[5]: Nothing to be done for 'all-am'.
make[5]: Leaving directory '/<>/agg-2.5+dfsg1/obj-pic/src/platform'
make[4]: Leaving directory '/<>/agg-2.5+dfsg1/obj-pic/src/platform'
make[3]: Leaving directory '/<>/agg-2.5+dfsg1/obj-pic/src'
Making all in font_freetype
make[3]: Entering directory '/<>/agg-2.5+dfsg1/obj-pic/font_freetype'
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../include   -Wdate-time -D_FORTIFY_SOURCE=2 -I../include 
-I/usr/include/freetype2  -g -O2 
-fdebug-prefix-map=/<>/agg-2.5+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security -c -o 
libaggfontfreetype_la-agg_font_freetype.lo `test -f 'agg_font_freetype.cpp' || 
echo './'`agg_font_freetype.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I../include -I/usr/include/freetype2 -g -O2 
-fdebug-prefix-map=/<>/agg-2.5+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security -c agg_font_freetype.cpp  -fPIC -DPIC -o 
.libs/libaggfontfreetype_la-agg_font_freetype.o
In file included from agg_font_freetype.h:34:0,
 from agg_font_freetype.cpp:26:
../include/agg_scanline_u.h: In member function 'void 
agg::scanline32_u8_am::finalize(int)':
../include/agg_scanline_u.h:482:39: error: cannot call member function 'void 
agg::scanline_u8::finalize(int)' without object
 base_type::finalize(span_y);
   ^
../include/agg_scanline_u.h:485:70: error: cannot call member function 
'agg::scanline_u8::span* agg::scanline_u8::begin()' without object
 typename base_type::iterator span = base_type::begin();
  ^
../include/agg_scanline_u.h:486:55: error: cannot call member function 
'unsigned int agg::scanline_u8::num_spans() const' without object
 unsigned count = base_type::num_spans();
   ^
../include/agg_scanline_u.h:490:62: error: cannot call member function 'int 

Bug#853720: marked as done (agg: ftbfs of exactimage with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 09:04:10 +
with message-id 
and subject line Bug#853303: fixed in agg 1:2.4-r127+dfsg1-1
has caused the Debian Bug report #853303,
regarding agg: ftbfs of exactimage 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.)


-- 
853303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:exactimage
Version: 0.9.1-16
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/exactimage_0.9.1-16_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

[...]
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -fopenmp -ffunction-sections -fdata-sections 
-fPIC -Wno-sign-compare -std=gnu++98 -fPIC -funroll-loops -fomit-frame-pointer 
-funswitch-loops -fpeel-loops -ftracer -funit-at-a-time -frename-registers 
-ftree-vectorize -Wno-switch -Wno-switch-enum -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -I . -I/usr/include/agg2 -I/usr/include/freetype2 -I lib 
-I utility -I/usr/include/OpenEXR -I codecs/ -I bardecode -I utility -I utility 
-I/usr/X11/include -I/usr/include/efl-1 -I/usr/include/evas-1 
-I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/freetype2 
-I/usr/include/efl-1 -I/usr/include/eet-1 -I/usr/include/p11-kit-1 
-I/usr/include/efl-1 -I/usr/include/eo-1 -I/usr/include/efl-1 
-I/usr/include/eina-1 -I/usr/include/eina-1/eina -Igfx -D WITHEVAS_COLOR_PREMUL 
-I . -I lib -I gfx -D WITHEVAS_X11_CONNECTION -D WITHEVAS_X11_SCREEN  -c  -MMD 
-MP -MF 'objdir/lib/FG-Matrix.d'
  -o 'objdir/lib/FG-Matrix.o' 'lib/FG-Matrix.cc'
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -fopenmp -ffunction-sections -fdata-sections 
-fPIC -Wno-sign-compare -std=gnu++98 -fPIC -funroll-loops -fomit-frame-pointer 
-funswitch-loops -fpeel-loops -ftracer -funit-at-a-time -frename-registers 
-ftree-vectorize -Wno-switch -Wno-switch-enum -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -I . -I/usr/include/agg2 -I/usr/include/freetype2 -I lib 
-I utility -I/usr/include/OpenEXR -I codecs/ -I bardecode -I utility -I utility 
-I/usr/X11/include -I/usr/include/efl-1 -I/usr/include/evas-1 
-I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/freetype2 
-I/usr/include/efl-1 -I/usr/include/eet-1 -I/usr/include/p11-kit-1 
-I/usr/include/efl-1 -I/usr/include/eo-1 -I/usr/include/efl-1 
-I/usr/include/eina-1 -I/usr/include/eina-1/eina -Igfx -D WITHEVAS_COLOR_PREMUL 
-I . -I lib -I gfx -D WITHEVAS_X11_CONNECTION -D WITHEVAS_X11_SCREEN  -c  -MMD 
-MP -MF 'objdir/lib/GaussianBlur
 .d' -o 'objdir/lib/GaussianBlur.o' 'lib/GaussianBlur.cc'
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -fopenmp -ffunction-sections -fdata-sections 
-fPIC -Wno-sign-compare -std=gnu++98 -fPIC -funroll-loops -fomit-frame-pointer 
-funswitch-loops -fpeel-loops -ftracer -funit-at-a-time -frename-registers 
-ftree-vectorize -Wno-switch -Wno-switch-enum -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64 -I . -I/usr/include/agg2 -I/usr/include/freetype2 -I lib 
-I utility -I/usr/include/OpenEXR -I codecs/ -I bardecode -I utility -I utility 
-I/usr/X11/include -I/usr/include/efl-1 -I/usr/include/evas-1 
-I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/freetype2 
-I/usr/include/efl-1 -I/usr/include/eet-1 -I/usr/include/p11-kit-1 

Bug#872533: Easy to fix

[Julien Puydt]

Hi,

to fix the problem, either try a newer chai (#868319), or change the
expected strings to match the more precise error message we have now.

Snark on #debian-js

Bug#872539: qt5-style-plugins: fails to install on Sid

[vv221]

Package: qt5-style-plugins
Version: 5.0.0+git23.g335dbec-2
Severity: grave
Justification: renders package unusable

Hi!
Since qt5 in Debian Sid got updated to 5.9, qt5-style-plugins is no
longer installable due to its dependency on qtbase-abi-5-7-1 that is no
longer provided.

Here is what I get from APT when I try to install it on a fresh Sid:

root@HAL9000:~# apt install qt5-style-plugins
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 qt5-style-plugins : Depends: qtbase-abi-5-7-1 but it is not installable
 E: Unable to correct problems, you have held broken packages.


On a Debian Sid with Qt 5.7, qt5-style-plugins will block the upgrade of
qt5 packages to 5.9 unless you remove it prior to upgrading. If you use
'full-upgrade' it will be automatically removed during the upgrade, so
this is not a "hard" blocker.

I assigned a severity of 'grave' to this report because the package is
no longer installable on a freshly installed Sid, feel free to lower the
severity if you don’t think this is enough to warrant this high
severity.

Thanks in advance for looking into this, and please tell me if I can do
anything to help resolve this issue ;)

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qt5-style-plugins depends on:
ii  libc62.24-14
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.53.4-3
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.9-1
ii  libqt5core5a [qtbase-abi-5-7-1]  5.7.1+dfsg-4
ii  libqt5dbus5  5.7.1+dfsg-4
ii  libqt5gui5   5.7.1+dfsg-4
ii  libqt5widgets5   5.7.1+dfsg-4
ii  libstdc++6   7.1.0-13
ii  libx11-6 2:1.6.4-3

qt5-style-plugins recommends no packages.

qt5-style-plugins suggests no packages.

-- no debconf information

Bug#853639: Fix for the regina-normal FTBFS with gcc 7

[Adrian Bunk]

Control: tags -1 patch

A fix for the regina-normal FTBFS with gcc 7 is attached.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

--- regina-normal-5.1.orig/engine/triangulation/dim3/triangulation3.h
+++ regina-normal-5.1/engine/triangulation/dim3/triangulation3.h
@@ -42,6 +42,7 @@
 #define __TRIANGULATION3_H
 #endif
 
+#include 
 #include 
 #include 
 #include 

Processed: Fix for the regina-normal FTBFS with gcc 7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #853639 [src:regina-normal] regina-normal: ftbfs with GCC-7
Added tag(s) patch.

-- 
853639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#867485: marked as done (pyside FTBFS with python 3.6 as supported version)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 10:40:25 +0200
with message-id <20170818084025.64lcza7cgh7xj...@home.ouaza.com>
and subject line Re: Bug#867485: pyside FTBFS with python 3.6 as supported 
version
has caused the Debian Bug report #867485,
regarding pyside FTBFS with python 3.6 as supported version
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.)


-- 
867485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyside
Version: 1.2.2+source1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyside.html

...
mkdir -p build-3.6
dh_auto_configure -a --builddirectory=build-3.6 -- \
-DCMAKE_SKIP_RPATH=true -DLIB_SUFFIX=/x86_64-linux-gnu -DUSE_XVFB=true 
-DCTEST_TESTING_TIMEOUT=600 \
-DCMAKE_BUILD_TYPE:STRING="Release" \
-DPYTHON_SUFFIX=.cpython-36m"-x86_64-linux-gnu" \
-DDEFAULT_PYTHON_BASENAME=-python2.7
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_SKIP_RPATH=true 
-DLIB_SUFFIX=/x86_64-linux-gnu -DUSE_XVFB=true -DCTEST_TESTING_TIMEOUT=600 
-DCMAKE_BUILD_TYPE:STRING=Release -DPYTHON_SUFFIX=.cpython-36m-x86_64-linux-gnu 
-DDEFAULT_PYTHON_BASENAME=-python2.7
-- The C compiler identification is GNU 6.4.0
-- The CXX compiler identification is GNU 6.4.0
-- 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
-- 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
CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Shiboken-1.2.2/ShibokenConfig.cmake:5 (include):
  include could not find load file:


/usr/lib/x86_64-linux-gnu/cmake/Shiboken-1.2.2/ShibokenConfig.cpython-36m-x86_64-linux-gnu.cmake
Call Stack (most recent call first):
  CMakeLists.txt:8 (find_package)


-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found
-- Found Qt4: /usr/bin/qmake (found suitable version "4.8.7", minimum required 
is "4.5.0") 
-- Using xvfb-run to perform QtGui tests.
-- Detected OS: x11
CMake Error at CMakeLists.txt:148 (message):
  Could not detect Python module installation directory.


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Hello,

On Thu, 06 Jul 2017, Adrian Bunk wrote:
> CMake Error at 
> /usr/lib/x86_64-linux-gnu/cmake/Shiboken-1.2.2/ShibokenConfig.cmake:5 
> (include):
>   include could not find load file:
> 
> 
> /usr/lib/x86_64-linux-gnu/cmake/Shiboken-1.2.2/ShibokenConfig.cpython-36m-x86_64-linux-gnu.cmake

This is fixed with the new shiboken I uploaded last night.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/--- End Message ---

Bug#872538: sleepyhead FTBFS with Qt 5.9.1

[Adrian Bunk]

Source: sleepyhead
Version: 1.0.0-beta-2+dfsg-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sleepyhead.html

...
g++ -c -m64 -pipe -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT 
-fPIC -DLOCK_RESMED_SESSIONS -DGIT_BRANCH=\"UNKNOWN\" 
-DGIT_REVISION=\"UNKNOWN\" -DBETA_BUILD -D_TTY_POSIX_ -DQT_NO_DEBUG 
-DQT_PRINTSUPPORT_LIB -DQT_WEBKITWIDGETS_LIB -DQT_OPENGL_LIB -DQT_WIDGETS_LIB 
-DQT_WEBKIT_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SERIALPORT_LIB 
-DQT_CORE_LIB -I../../sleepyhead -I. -isystem /usr/include/x86_64-linux-gnu/qt5 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSerialPort -isystem /usr/include
 /x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o updateparser.o 
../../sleepyhead/updateparser.cpp
../../sleepyhead/updateparser.cpp: In member function 'void 
UpdatesParser::readUpdates()':
../../sleepyhead/updateparser.cpp:253:67: error: call of overloaded 
'compare(const char [14], Qt::CaseSensitivity)' is ambiguous
 if (xml.name().compare("PackageUpdate",Qt::CaseInsensitive)==0) {
   ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qregexp.h:47:0,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qstringlist.h:47,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:1094,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QDebug:1,
 from ../../sleepyhead/updateparser.cpp:9:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1583:12: note: candidate: 
int QStringRef::compare(const QString&, Qt::CaseSensitivity) const
 inline int QStringRef::compare(const QString , Qt::CaseSensitivity cs) const 
Q_DECL_NOTHROW
^~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1514:9: note: candidate: int 
QStringRef::compare(const QByteArray&, Qt::CaseSensitivity) const
 int compare(const QByteArray , Qt::CaseSensitivity cs = 
Qt::CaseSensitive) const
 ^~~
...

Bug#872480: marked as done ([node-acorn] Need depends on nodejs > 6)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 08:49:20 +
with message-id 
and subject line Bug#872480: fixed in acorn 5.1.1-1
has caused the Debian Bug report #872480,
regarding [node-acorn] Need depends on nodejs > 6
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.)


-- 
872480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-acorn
Version: 5.0.3-1
Severity: grave

This version use a lot of depends of nodejs > 6

YOu could drop the second patch serie and use an hard depends

acorn fail on testing

Bastien

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: acorn
Source-Version: 5.1.1-1

We believe that the bug you reported is fixed in the latest version of
acorn, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 872...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated acorn package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 Aug 2017 09:02:29 +0200
Source: acorn
Binary: node-acorn
Architecture: source all
Version: 5.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Julien Puydt 
Description:
 node-acorn - ECMAScript parser for Node.js
Closes: 872480
Changes:
 acorn (5.1.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Drop all patches and depend on nodejs (> 6) (Closes: #872480).
   * Add a patch to unbreak the compilation with node-es6-module-transpiler.
Checksums-Sha1:
 03a5746d57663b822d722fb6ad64fd3cff04db2f 2064 acorn_5.1.1-1.dsc
 c018c756e0f05a118e216a3276c1605d66468a36 1115390 acorn_5.1.1.orig.tar.gz
 e9217c3a8275a7f925884da7cf3304c0a7272fff 6152 acorn_5.1.1-1.debian.tar.xz
 cf12582327bbb4cf92e7d0664c72be2d346bb784 7228 acorn_5.1.1-1_amd64.buildinfo
 69d64bde082799be7fb01fba8732cc96c2016d5e 62086 node-acorn_5.1.1-1_all.deb
Checksums-Sha256:
 44225912de320cd63840ce9e84804333fad8eda76613d8b20f2fb75815b4f066 2064 
acorn_5.1.1-1.dsc
 6565d09b53cde7321526e3d5a39c8d522c8194bb231c93291a87aed266fb98e4 1115390 
acorn_5.1.1.orig.tar.gz
 628f86057c7d69b1c7474641c8821d7f182008c9058a894ceacd174fc870c216 6152 
acorn_5.1.1-1.debian.tar.xz
 0d4c03cfba97f4ffc47d0ea4be6a00da36c86575dae1657010951fe4ecff45de 7228 
acorn_5.1.1-1_amd64.buildinfo
 8b22fdd0b7761d67736d1d64d5cff85e1f590962de8e013fbbd222fa946c892c 62086 
node-acorn_5.1.1-1_all.deb
Files:
 3fcbb1723e9ed1caea2b25ad8f77da56 2064 web extra acorn_5.1.1-1.dsc
 7e559d3e18320a5c933f60162f1b2437 1115390 web extra acorn_5.1.1.orig.tar.gz
 e094cc19cac8f9fe84d2698882b7e873 6152 web extra acorn_5.1.1-1.debian.tar.xz
 eed359f0daa24e454623f3c5b9750ce1 7228 web extra acorn_5.1.1-1_amd64.buildinfo
 b67afecce9308478fb84642bb1331027 62086 web extra node-acorn_5.1.1-1_all.deb

-BEGIN PGP SIGNATURE-

iQJNBAEBCgA3FiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAlmWms8ZHGp1bGllbi5w
dXlkdEBsYXBvc3RlLm5ldAAKCRAExTvX/gMFUfejD/4m6xJBdfkSx05shXMyjaBn
+C77DgEddsNwAhMpkaNyO+YxlMqCad4XykEDq1k8/8L4BPjFFoRYIsmTz3egXRSr
L7nTDGzO5dTfzYMuk9qDqDYXj0uSfkfzRwBLpljn8imhLXIpBktzWZ24fK/Iah1g
fAdxJ+GgCKPKtomfutoDLnCRmToVUd81L+stzThMye2EOKMfkAl2tsMUoR1UHBAF
ePicHHwBg4584r7I4sRuDMu8wmBU+JoofC0W7yhtkS4UrdQnxGU9Stg5MOrgzaIu
zDVXg6sDysrkNbOoxduata01hYkpR8awcmX5WOrHfjzyP0GZL2Pz0iUyvWgKfXIX
4OtnGIQrdWDeAep1xkcjVG9TXV2dqYgjD4oM8I6m5IEwM1oqy79QP+AnXBdR3Rzq
GosvVLj83B2HerIKL0h3GqgLon+j+jav26sC+mOw/RwFDVORy7AkCmu5sncPgn/o
jigz9AVT67fPsqmE2t9Jv0E5o5gp/DtUxj53OAjB28FQO4zBPb32vSe0F4rc5Lm2
OJWRjSEJTYQQ5FemF0ufQ6SnY8FKIixMmUfO/iPXrv3vawsikMt1YPBrlmZqJ3Re
5c9duW0CmjwItW7CFu45mPOQsDMkK+0TSH4wmAFTD41XJql0JBQtOKLL9HhuBcu2
NRSwto9MNY7K6H0hvxNQvQ==
=iQS8
-END PGP SIGNATURE End Message ---

Processed: Not a problem in stretch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 872532 buster sid
Bug #872532 [w3m] w3m bricked: symbol lookup error: w3m: undefined symbol: 
Gpm_Wgetch
Added tag(s) buster and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
872532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Based on the information in the bug, does not seem to be a problem in jessie

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 865967 stretch buster sid
Bug #865967 [trac-tags] trac 1.2 no longer provides get_db_cnx
Added tag(s) buster, stretch, and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872537: mpgrafic FTBFS on 32bit: Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)

[Adrian Bunk]

Source: mpgrafic
Version: 0.3.13-1
Severity: serious

https://buildd.debian.org/status/package.php?p=mpgrafic=sid

...
Making all in src
make[3]: Entering directory '/<>/src'
mpifort -cpp -DDOUB  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -c -o grafic_types.o grafic_types.f90
mpicc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o parallel_io.o parallel_io.c
parallel_io.c: In function 'parallel_write':
parallel_io.c:58:44: warning: format '%ld' expects argument of type 'long int', 
but argument 3 has type 'long long int' [-Wformat=]
 fprintf(stderr,"which is bigger than %ld\n",(int64_t)OFFSET_MAX);
  ~~^
  %lld
parallel_io.c: In function 'parallel_read':
parallel_io.c:79:44: warning: format '%ld' expects argument of type 'long int', 
but argument 3 has type 'long long int' [-Wformat=]
 fprintf(stderr,"which is bigger than %ld\n",(int64_t)OFFSET_MAX);
  ~~^
  %lld
mpifort -cpp -DDOUB  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -c -o grafic_io.o grafic_io.f90
grafic_io.f90:468:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:490:36:

 & offset, c_loc(tampon))
1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:495:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:355:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:377:36:

 & offset, c_loc(tampon))
1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:382:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:275:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:283:36:

 & offset, c_loc(tampon))
1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:288:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:172:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:180:36:

 & offset, c_loc(tampon))
1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
grafic_io.f90:185:43:

 & ,offset,c_loc(taille_tampon))
   1
Error: Type mismatch in argument 'size' at (1); passed INTEGER(8) to INTEGER(4)
Makefile:446: recipe for target 'grafic_io.o' failed
make[3]: *** [grafic_io.o] Error 1

Bug#872535: sqlite FTBFS on arm* with gcc 7

[Adrian Bunk]

Source: sqlite
Version: 2.8.17-14
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/sqlite.html

...
cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-DTHREADSAFE=1 -o lemon ./tool/lemon.c
./tool/lemon.c: In function 'tplt_open':
./tool/lemon.c:2821:7: warning: implicit declaration of function 'access' 
[-Wimplicit-function-declaration]
   if( access(buf,004)==0 ){
   ^~
./tool/lemon.c:2713:14: note: previous declaration of 'access' was here
   extern int access();
  ^~
cp ./tool/lempar.c .
cp ./src/parse.y .
./lemon parse.y
Makefile:261: recipe for target 'parse.c' failed
make[2]: *** [parse.c] Segmentation fault
make[2]: *** Deleting file 'parse.c'
make[2]: Leaving directory '/build/1st/sqlite-2.8.17'
debian/rules:37: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2


I've confirmed on armel that the segfault is also present there,
and goes away when building lemon with gcc-6.

Bug#853326: [Pkg-freeipa-devel] Bug#853326: Fix for the bind-dyndb-ldap FTBFS with gcc 7

[Timo Aaltonen]

On 17.08.2017 19:45, Adrian Bunk wrote:
> Control: tags -1 patch fixed-upstream
> 
> The upstream fix for the bind-dyndb-ldap FTBFS with gcc 7
> is attached.

Thanks, my plan was to update bind-dyndb-ldap to a newer upstream
version, but that needs bind 9.11 which I've packaged and offered for
review months ago but so far has not entered the archive..


-- 
t

Bug#872533: node-chai FTBFS with nodejs 6.11.2

[Adrian Bunk]

Source: node-chai
Version: 3.5.0+dfsg-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-chai.html

...
   dh_auto_test
make -j1 test
make[1]: Entering directory '/build/1st/node-chai-3.5.0+dfsg'
==> [Test :: Node.js]

  
․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
  
․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
  
․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
  
․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․

  209 passing (438ms)
  4 failing

  1) expect throw:

  AssertionError: expected 'expected [Function: goodFn] to throw an 
error' to equal 'expected [Function] to throw an error'
  + expected - actual

  -"expected [Function: goodFn] to throw an error"
  +"expected [Function] to throw an error"
  
  at global.err 
(/build/1st/node-chai-3.5.0+dfsg/test/bootstrap/index.js:17:35)
  at Context. 
(/build/1st/node-chai-3.5.0+dfsg/test/expect.js:921:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)

  2) expect satisfy:

  expected 'blah
  + expected - actual

  -"blah: expected 2 to satisfy [Function: matcher]"
  +"blah: expected 2 to satisfy [Function]"
  
  at global.err 
(/build/1st/node-chai-3.5.0+dfsg/test/bootstrap/index.js:17:35)
  at Context. 
(/build/1st/node-chai-3.5.0+dfsg/test/expect.js:1025:5)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)

  3) should throw:

  AssertionError: expected 'expected [Function: goodFn] to throw an 
error' to equal 'expected [Function] to throw an error'
  + expected - actual

  -"expected [Function: goodFn] to throw an error"
  +"expected 

Bug#872532: w3m bricked: symbol lookup error: w3m: undefined symbol: Gpm_Wgetch

[積丹尼 Dan Jacobson]

X-Debbugs-Cc: dic...@invisible-island.net, yama...@jpl.org
Package: w3m
Version: 0.5.3-34
Severity: grave

With the latest upgrade of its dependencies, w3m is now 100 unusable on Debian.

$ w3m
w3m: symbol lookup error: w3m: undefined symbol: Gpm_Wgetch

We read in
http://invisible-island.net/ncurses/ncurses.faq.html#using_gpm_lib

"w3m contains some contorted code to exploit this, by abusing the
library interface: it defines several symbols that conflict with ncurses
to intercept calls to wgetch, while using other symbols from ncurses as
is. (There is also documented Gpm_Getch, but it is no longer present in
the GPM source code)."

Anyway I can no longer use w3m on Debian. It won't even start.

I can't even do
$ echo ooo|TERM=dumb w3m -dump
w3m: symbol lookup error: w3m: undefined symbol: Gpm_Wgetch

-- System Information:
Debian Release: buster/sid
  APT prefers experimental
  APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages w3m depends on:
ii  libc6  2.24-14
ii  libgc1c2   1:7.4.4-1
ii  libgpm21.20.7-1
ii  libssl1.1  1.1.0f-4
ii  libtinfo5  6.0+20170715-2
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages w3m recommends:
ii  ca-certificates  20170717

Versions of packages w3m suggests:
pn  cmigemo   
ii  curl  7.55.0-1
ii  dict  1.12.1+dfsg-4
pn  dict-wn   
ii  dictd 1.12.1+dfsg-4
pn  libsixel-bin  
ii  man-db2.7.6.1-2
ii  mime-support  3.60
pn  mpv   
ii  w3m-el-snapshot [w3m-el]  1.4.569+0.20170110-1
pn  w3m-img   
ii  wget  1.19.1-4
ii  xdg-utils 1.1.1-1
pn  xsel  

-- no debconf information

Bug#872531: node-argparse FTBFS with nodejs 6.11.2

[Adrian Bunk]

Source: node-argparse
Version: 1.0.7-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-argparse.html

...
[92m  147 passing (305ms)
  1 failing

  1) user defined type test an anonymous user-defined type:
 TypeError: argument "-d": Invalid dateType value: abc
  at module.exports 
(/build/1st/node-argparse-1.0.7/lib/argument/error.js:47:9)
  at ArgumentParser._getValue 
(/build/1st/node-argparse-1.0.7/lib/argument_parser.js:978:11)
  at ArgumentParser._getValues 
(/build/1st/node-argparse-1.0.7/lib/argument_parser.js:922:18)
  at ArgumentParser.takeAction 
(/build/1st/node-argparse-1.0.7/lib/argument_parser.js:374:31)
  at consumeOptional 
(/build/1st/node-argparse-1.0.7/lib/argument_parser.js:473:18)
  at ArgumentParser._parseKnownArgs 
(/build/1st/node-argparse-1.0.7/lib/argument_parser.js:556:18)
  at ArgumentParser.parseKnownArgs 
(/build/1st/node-argparse-1.0.7/lib/argument_parser.js:287:20)
  at ArgumentParser.parseArgs 
(/build/1st/node-argparse-1.0.7/lib/argument_parser.js:234:21)
  at /build/1st/node-argparse-1.0.7/test/user_defined_type.js:114:26
  at _tryBlock (assert.js:320:5)
  at _throws (assert.js:339:12)
  at Function.assert.throws (assert.js:369:3)
  at Context. 
(/build/1st/node-argparse-1.0.7/test/user_defined_type.js:113:12)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)



debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#872525: [pkg-gnupg-maint] Bug#872525: debian-archive-keyring FTBFS with gnupg 2.1.23

[Daniel Kahn Gillmor]

On Fri 2017-08-18 10:02:49 +0300, Adrian Bunk wrote:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debian-archive-keyring.html
>
> ...
> gpg --no-options --no-default-keyring --no-auto-check-trustdb --trustdb-name 
> ./trustdb.gpg \
>   --keyring keyrings/team-members.gpg --verify \
>   keyrings/debian-archive-keyring.gpg.asc \
>   keyrings/debian-archive-keyring.gpg
> gpg: Signature made Thu May 25 06:30:03 2017 -12
> gpg:using RSA key C5CE5DC2C542CD59
> gpg: BAD signature from "Adam D. Barratt " [unknown]
> Makefile:17: recipe for target 'verify-results' failed
> make[1]: *** [verify-results] Error 1
> make[1]: Leaving directory '/build/1st/debian-archive-keyring-2017.5'
> dh_auto_build: make -j1 returned exit code 2
> debian/rules:3: recipe for target 'build' failed
> make: *** [build] Error 2
>
>
> Works after downgrading gnupg to the buster version.
>
> The Debian GnuPG Maintainers are Cc'ed, please reassign
> if the bug turns out to be there.

The difference between the keyrings is the trust packets:

0 dkg@alice:/tmp/cdtemp.kXzrYG/debian-archive-keyring-2017.5$ diff -u <(pgpdump 
< /usr/share/keyrings/debian-archive-keyring.gpg) <(pgpdump < 
keyrings/debian-archive-keyring.gpg) | head -n 30
--- /dev/fd/63  2017-08-18 03:30:23.802753003 -0400
+++ /dev/fd/62  2017-08-18 03:30:23.806753375 -0400
@@ -4,8 +4,12 @@
Pub alg - RSA Encrypt or Sign(pub 1)
RSA n(4096 bits) - ...
RSA e(17 bits) - ...
+Old: Trust Packet(tag 12)(12 bytes)
+   Trust - 00 00 67 70 67 01 00 00 00 00 00 00 
 Old: User ID Packet(tag 13)(59 bytes)
User ID - Wheezy Stable Release Key 
+Old: Trust Packet(tag 12)(12 bytes)
+   Trust - 00 00 67 70 67 02 00 00 00 00 00 00 
 Old: Signature Packet(tag 2)(573 bytes)
Ver 4 - new
Sig type - Positive certification of a User ID and Public Key 
packet(0x13).
@@ -42,8 +46,8 @@
Hash left 2 bytes - cd 52 
RSA m^d mod n(4094 bits) - ...
-> PKCS-1
-Old: Trust Packet(tag 12)(2 bytes)
-   Trust - 00 03 
+Old: Trust Packet(tag 12)(6 bytes)
+   Trust - 00 03 67 70 67 00 
 Old: Signature Packet(tag 2)(540 bytes)
Ver 4 - new
Sig type - Generic certification of a User ID and Public Key 
packet(0x10).
@@ -56,8 +60,8 @@
Hash left 2 bytes - 43 61 
RSA m^d mod n(4096 bits) - ...
-> PKCS-1
0 dkg@alice:/tmp/cdtemp.kXzrYG/debian-archive-keyring-2017.5$ 



This is happening because of a combination of several factors:

One of them is https://bugs.debian.org/870780 -- the
debian-archive-keyring really shouldn't have OpenPGP trust packets in it
in the first place.  Those are deliberately underspecified and
vendor-specific:

  https://tools.ietf.org/html/rfc4880#section-5.10

  5.10.  Trust Packet (Tag 12)

   The Trust packet is used only within keyrings and is not normally
   exported.  Trust packets contain data that record the user's
   specifications of which key holders are trustworthy introducers,
   along with other information that implementing software uses for
   trust information.  The format of Trust packets is defined by a given
   implementation.

   Trust packets SHOULD NOT be emitted to output streams that are
   transferred to other users, and they SHOULD be ignored on any input
   other than local keyring files.



The larger problem here is that jetring (and debian-archive-keyring, and
anything else which uses jetring) seems to assume some things about what
GnuPG does with the contents of ~/.gnupg.

GnuPG upstream has been increasingly clear for several years now that if
you want portable, interoperable, or outward-facing stability from
GnuPG, you need to use its established interfaces, and not make
assumptions about what it's doing inside ~/.gnupg .  For example, the
creation of an exportable OpenPGP keyring (that is, linear concatenation
of OpenPGP packets representing an OpenPGP certificate) should be done
with --export, not with --keyring and then fishing around in the binarys
contents of the keyring itself.

GnuPG 2.1.23 is recording additional information (as compared to
previous versions) in the "Trust Packets" that it keeps in its internal
keyring.  This is fully in keeping with the OpenPGP spec.

If #870780 was resolved (perhaps by fixing jetring to use GnuPG's
external interfaces?) and a new debian-archive-keyring.gpg.asc was
created by Adam (or some other member of the team) then i think this
problem would go away.

Please do not fish out internal data structures from GnuPG's cache and
expect them to be constant across versions of GnuPG!  AFAIK, GnuPG
itself is able to read and interpret keyrings across versions, but it
isn't going to necessarily keep them entirely untouched because it uses
trust packets to cache its calculated validity and other information.

   --dkg


signature.asc
Description: PGP signature

Bug#872528: golang-github-grpc-ecosystem-grpc-gateway FTBFS: test failure

[Adrian Bunk]

Source: golang-github-grpc-ecosystem-grpc-gateway
Version: 1.1.0+git20170127.54.6863684-1
Severity: serious

Some recent change in unstable makes
golang-github-grpc-ecosystem-grpc-gateway FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-grpc-ecosystem-grpc-gateway.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-grpc-ecosystem-grpc-gateway.html

...
=== RUN   TestJSONPbMarshal
--- FAIL: TestJSONPbMarshal (0.00s)
marshal_jsonpb_test.go:108: got = 
uuid:"6EC2446F-7E89-4127-B3E6-5C05E6BECBA7" nested: 
uint64_value:18446744073709551615 enum_value:ONE oneof_string:"bar" 
map_value: map_value: ; want 
uuid:"6EC2446F-7E89-4127-B3E6-5C05E6BECBA7" nested: 
uint64_value:18446744073709551615 enum_value:ONE oneof_string:"bar" 
map_value: map_value: ; spec={false 
true  false 0x7fe8b0}
=== RUN   TestJSONPbMarshalFields
--- PASS: TestJSONPbMarshalFields (0.00s)
=== RUN   TestJSONPbUnmarshal
--- PASS: TestJSONPbUnmarshal (0.00s)
=== RUN   TestJSONPbUnmarshalFields
--- PASS: TestJSONPbUnmarshalFields (0.00s)
=== RUN   TestJSONPbEncoder
--- FAIL: TestJSONPbEncoder (0.00s)
marshal_jsonpb_test.go:322: got = 
uuid:"6EC2446F-7E89-4127-B3E6-5C05E6BECBA7" nested: 
uint64_value:18446744073709551615 oneof_string:"bar" map_value: map_value: ; want 
uuid:"6EC2446F-7E89-4127-B3E6-5C05E6BECBA7" nested: 
uint64_value:18446744073709551615 oneof_string:"bar" map_value: map_value: ; spec={false true  false 0x7ff220}
=== RUN   TestJSONPbEncoderFields
--- PASS: TestJSONPbEncoderFields (0.00s)
=== RUN   TestJSONPbDecoder
--- PASS: TestJSONPbDecoder (0.00s)
=== RUN   TestJSONPbDecoderFields
--- PASS: TestJSONPbDecoderFields (0.00s)
=== RUN   TestMarshalerForRequest
--- PASS: TestMarshalerForRequest (0.00s)
=== RUN   TestMuxServeHTTP
--- PASS: TestMuxServeHTTP (0.00s)
=== RUN   TestPopulateParameters
proto: no coders for runtime_test.proto2Message
proto: no encoder for NestedNonNull runtime_test.proto2Message [GetProperties]
2017/08/17 21:02:44 too many field values: uint64_value
--- PASS: TestPopulateParameters (0.00s)
=== RUN   TestPopulateParametersWithFilters
--- PASS: TestPopulateParametersWithFilters (0.00s)
FAIL
FAILgithub.com/grpc-ecosystem/grpc-gateway/runtime  0.031s
?   github.com/grpc-ecosystem/grpc-gateway/runtime/internal [no test files]
?   
github.com/grpc-ecosystem/grpc-gateway/third_party/googleapis/google/api
[no test files]
=== RUN   TestMaxCommonPrefix
--- PASS: TestMaxCommonPrefix (0.00s)
=== RUN   TestAdd
--- PASS: TestAdd (0.00s)
PASS
ok  github.com/grpc-ecosystem/grpc-gateway/utilities0.016s
dh_auto_test: go test -v -p 15 github.com/grpc-ecosystem/grpc-gateway/examples 
github.com/grpc-ecosystem/grpc-gateway/examples/clients/abe 
github.com/grpc-ecosystem/grpc-gateway/examples/clients/echo 
github.com/grpc-ecosystem/grpc-gateway/examples/examplepb 
github.com/grpc-ecosystem/grpc-gateway/examples/server 
github.com/grpc-ecosystem/grpc-gateway/examples/server/cmd/example-server 
github.com/grpc-ecosystem/grpc-gateway/examples/sub 
github.com/grpc-ecosystem/grpc-gateway/examples/sub2 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/descriptor 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/generator 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/gengateway 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/httprule 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-swagger 
github.com/grpc-ecosystem/grpc-gateway/protoc-gen-swagger/genswagger 
github.com/grpc-ecosyst
 em/grpc-gateway/runtime 
github.com/grpc-ecosystem/grpc-gateway/runtime/internal 
github.com/grpc-ecosystem/grpc-gateway/third_party/googleapis/google/api 
github.com/grpc-ecosystem/grpc-gateway/utilities returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 1

Bug#872517: ffmpeg: CVE-2017-7206: heap-based buffer over-read in embed libav

[Carl Eugen Hoyos]

Hi!

> the following vulnerability was published for libav

> (which is embed in ffmpeg).

This is not true.

Please provide valgrind or asan output (both show the 
issue easily for some avconv releases) for any 
affected FFmpeg version or close this issue.

Carl Eugen

Bug#872525: debian-archive-keyring FTBFS with gnupg 2.1.23

[Adrian Bunk]

Source: debian-archive-keyring
Version: 2017.5
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debian-archive-keyring.html

...
gpg --no-options --no-default-keyring --no-auto-check-trustdb --trustdb-name 
./trustdb.gpg \
--keyring keyrings/team-members.gpg --verify \
keyrings/debian-archive-keyring.gpg.asc \
keyrings/debian-archive-keyring.gpg
gpg: Signature made Thu May 25 06:30:03 2017 -12
gpg:using RSA key C5CE5DC2C542CD59
gpg: BAD signature from "Adam D. Barratt " [unknown]
Makefile:17: recipe for target 'verify-results' failed
make[1]: *** [verify-results] Error 1
make[1]: Leaving directory '/build/1st/debian-archive-keyring-2017.5'
dh_auto_build: make -j1 returned exit code 2
debian/rules:3: recipe for target 'build' failed
make: *** [build] Error 2


Works after downgrading gnupg to the buster version.

The Debian GnuPG Maintainers are Cc'ed, please reassign
if the bug turns out to be there.

Processed: forcibly merging 871583 871942

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 871583 871942
Bug #871583 {Done: Mike Hommey } [firefox-esr] 
firefox-esr: OOOBUpdate to 52.3.0 borks Firefox graphics
Bug #871607 {Done: Mike Hommey } [firefox-esr] 
firefox-esr: the display of the menu and the tabs is completely broken
Bug #871942 [firefox-esr] firefox-esr: Firefox will not render the YouTube page 
correctly nor play YT videos rel 8/12/17.
Severity set to 'important' from 'serious'
Marked Bug as done
Marked as fixed in versions firefox-esr/52.3.0esr-2.
Bug #871583 {Done: Mike Hommey } [firefox-esr] 
firefox-esr: OOOBUpdate to 52.3.0 borks Firefox graphics
There is no source info for the package 'firefox-esr' at version 
'52.3.0esr-1~deb8u1' with architecture ''
Unable to make a source version for version '52.3.0esr-1~deb8u1'
Marked as found in versions 52.3.0esr-1~deb8u1.
Marked as found in versions 52.3.0esr-1~deb8u1.
Bug #871607 {Done: Mike Hommey } [firefox-esr] 
firefox-esr: the display of the menu and the tabs is completely broken
Merged 871583 871607 871942
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
871583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871583
871607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871607
871942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Patch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 865967 patch
Bug #865967 [trac-tags] trac-tags plugin activation fails on fresh stable 
install
Added tag(s) patch.
> severity 865967 grave
Bug #865967 [trac-tags] trac-tags plugin activation fails on fresh stable 
install
Severity set to 'grave' from 'important'
> retitle 865967 trac 1.2 no longer provides get_db_cnx
Bug #865967 [trac-tags] trac-tags plugin activation fails on fresh stable 
install
Changed Bug title to 'trac 1.2 no longer provides get_db_cnx' from 'trac-tags 
plugin activation fails on fresh stable install'.
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
865967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#872400: marked as done (augeas: CVE-2017-7555: Improper handling of escaped strings leading to memory corruption)

[Debian Bug Tracking System]

Your message dated Fri, 18 Aug 2017 06:04:11 +
with message-id 
and subject line Bug#872400: fixed in augeas 1.8.1-1
has caused the Debian Bug report #872400,
regarding augeas: CVE-2017-7555: Improper handling of escaped strings leading 
to memory corruption
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.)


-- 
872400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: augeas
Version: 1.8.0-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/hercules-team/augeas/pull/480

Hi,

the following vulnerability was published for augeas.

CVE-2017-7555[0]:
crash/memory corruption when handling certain escaped strings

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-7555
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7555
[1] https://github.com/hercules-team/augeas/pull/480
[2] 
https://github.com/hercules-team/augeas/pull/480/commits/39592c4eef8d4826947adca94c7fbd6efb8d47ca
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1475621 (not
addessible at time of writing)
[4] http://www.openwall.com/lists/oss-security/2017/08/17/3

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: augeas
Source-Version: 1.8.1-1

We believe that the bug you reported is fixed in the latest version of
augeas, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 872...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated augeas package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 Aug 2017 07:15:24 +0200
Source: augeas
Binary: augeas-tools libaugeas-dev libaugeas0 augeas-dbg augeas-lenses 
augeas-doc
Architecture: source
Version: 1.8.1-1
Distribution: unstable
Urgency: high
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Description:
 augeas-dbg - Debugging symbols for libaugeas0
 augeas-doc - Augeas lenses documentation
 augeas-lenses - Set of lenses needed by libaugeas0 to parse config files
 augeas-tools - Augeas command line tools
 libaugeas-dev - Development files for writing applications based on libaugeas0
 libaugeas0 - Augeas configuration editing library and API
Closes: 715554 872400
Changes:
 augeas (1.8.1-1) unstable; urgency=high
 .
   * New upstream version 1.8.1
 - Fixes CVE-2017-7555 (Closes: #872400)
   * Add Multi-Arch support (Closes: #715554)
Checksums-Sha1:
 4a7dd0d16757d0f1f9954170092a37b43d727a31 2306 augeas_1.8.1-1.dsc
 24ebfd91e28af5c1392c5c6f42756f2b9d2327be 2165325 augeas_1.8.1.orig.tar.gz
 e676ccb216a524a28ef99bbff72ced69ba1c2e4d 9440 augeas_1.8.1-1.debian.tar.xz
 b5bb32439836512f7e86759abab3ea95ecda2f75 8394 augeas_1.8.1-1_source.buildinfo
Checksums-Sha256:
 70a5c5bcfd0606aa507d3c2602b0558fc96e9ff6da92d66dd5f6722df070d6a5 2306 
augeas_1.8.1-1.dsc
 65cf75b5a573fee2a5c6c6e3c95cad05f0101e70d3f9db10d53f6cc5b11bc9f9 2165325 
augeas_1.8.1.orig.tar.gz
 155beb5e76916690d8c49e3d696069a72c61c174798b0f0cbea509e2ea5df2ff 9440 
augeas_1.8.1-1.debian.tar.xz
 50f402ed86618a35849b54149cceb9b5b0a9887ed8c4e77960255079dd099a6f 8394 
augeas_1.8.1-1_source.buildinfo
Files:
 aa9b1c656c3b514b450ab28e5382e81d 2306 libs optional augeas_1.8.1-1.dsc
 623ff89d71a42fab9263365145efdbfa 2165325 libs optional augeas_1.8.1.orig.tar.gz
 924622bdc9717034f496de02d80feb09 9440 libs optional 
augeas_1.8.1-1.debian.tar.xz
 32ae69e19a263442e5787c50bf948334 8394 libs optional 
augeas_1.8.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlmWeEEACgkQdbcQY1wh
On7QPxAAsK8GhyzIO2YAM+jQGojkEUTmhMowYBmKg5FLgq5vRPPqFAMOrpeADYJr
EEkkP+vPY9feEVpG0YQ8fFaWYIg4qzk34A20xWnXrER7xEd+eK07SiPV+mDKjbkw
IJQ7C3LuXDxbAe85Xb23UxhuGT3icedqboOcxpJCvP8SG8mo/L6BUa4Dklr2vyDE
KCbkCOCX1j5q5iYzYXI16OxNBHhgmpPUtAnQeTzdIOQbtsWaoVZYKKUf4Ztfe/nh