Bug#853457: ipsec-tools: ftbfs with GCC-7

[Noah Meyerhans]

On Tue, Jan 31, 2017 at 09:32:19AM +, Matthias Klose wrote:
> cfparse.y:546:39: note: using the range [1, -9223372036854775808] for 
> directive argument
> In file included from /usr/include/stdio.h:938:0,
>  from cfparse.y:50:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: format output 
> between 2 and 21 bytes into a destination of size 10
>return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
>   ^~~~
> __bos (__s), __fmt, __va_arg_pack ());
> ~
> cfparse.y:1388:39: error: '%lu' directive output may be truncated writing 
> between 1 and 20 bytes into a region of size 10 [-Werror=format-truncation=]
> snprintf(portbuf, sizeof(portbuf), "%lu", $4);
>^
> cfparse.y:1388:39: note: using the range [1, 18446744073709551615] for 
> directive argument

There are several errors during compilation. Most of them follow a
similar pattern to what's above. They generally come down to a bit of
"clever" optimization to save a few bytes here and there. For example,
if we're storing a network prefix length in an int, we know the maximum
value will never need more than 4 bytes when represented as a
null-terminated string, e.g. "128\0". However, an arbitrary int can
require 11 bytes in the same representation. In these cases, we should
simply make the buffers big enough to keep gcc quiet.

Most of these format string issues relate to internal data and interally
allocated buffers, and they don't seem to be particurly problematic.
However, the format string issue when writing entries to utmp definitely
doesn't seem right. Utmpx defined the ut_id field as a 4 byte buffer. In
racoon, we're writing to that buffer with the following:

snprintf(ut.ut_id, sizeof ut.ut_id, TERMSPEC, port);

Where TERMSPEC is defined as "vpn%d". There's really no way that this
can work. I think ut_line is a more appropriate field in utmp for this
information.

Attached is a patch that I believe addresses the issues. I'd appreciate
feedback before I push it.

noah

Index: pkg-ipsec-tools/src/racoon/cfparse.y
===
--- pkg-ipsec-tools.orig/src/racoon/cfparse.y
+++ pkg-ipsec-tools/src/racoon/cfparse.y
@@ -2564,7 +2564,7 @@ set_isakmp_proposal(rmconf)
 		plog(LLV_DEBUG2, LOCATION, NULL,
 			"encklen=%d\n", s->encklen);
 
-		memset(types, 0, ARRAYLEN(types));
+		memset(types, 0, ARRAYLEN(types) * sizeof(types[0]));
 		types[algclass_isakmp_enc] = s->algclass[algclass_isakmp_enc];
 		types[algclass_isakmp_hash] = s->algclass[algclass_isakmp_hash];
 		types[algclass_isakmp_dh] = s->algclass[algclass_isakmp_dh];
Index: pkg-ipsec-tools/src/racoon/isakmp_cfg.c
===
--- pkg-ipsec-tools.orig/src/racoon/isakmp_cfg.c
+++ pkg-ipsec-tools/src/racoon/isakmp_cfg.c
@@ -1701,7 +1701,7 @@ isakmp_cfg_accounting_system(port, raddr
 
 	memset(, 0, sizeof ut);
 	gettimeofday((struct timeval *)_tv, NULL);
-	snprintf(ut.ut_id, sizeof ut.ut_id, TERMSPEC, port);
+	snprintf(ut.ut_line, sizeof ut.ut_line, TERMSPEC, port);
 
 	switch (inout) {
 	case ISAKMP_CFG_LOGIN:
@@ -1713,7 +1713,7 @@ isakmp_cfg_accounting_system(port, raddr
 
 		plog(LLV_INFO, LOCATION, NULL,
 			"Accounting : '%s' logging on '%s' from %s.\n",
-			ut.ut_user, ut.ut_id, addr);
+			ut.ut_user, ut.ut_line, addr);
 
 		pututxline();
 
@@ -1723,7 +1723,7 @@ isakmp_cfg_accounting_system(port, raddr
 
 		plog(LLV_INFO, LOCATION, NULL,
 			"Accounting : '%s' unlogging from '%s'.\n",
-			usr, ut.ut_id);
+			usr, ut.ut_line);
 
 		pututxline();
 
@@ -1920,7 +1920,7 @@ isakmp_cfg_setenv(iph1, envp, envc)
 	char *splitlist_cidr;
 	char defdom[MAXPATHLEN + 1];
 	int cidr, tmp;
-	char cidrstr[4];
+	char cidrstr[12];
 	int i, p;
 	int test;
 
@@ -1983,7 +1983,7 @@ isakmp_cfg_setenv(iph1, envp, envc)
 	tmp = ntohl(iph1->mode_cfg->mask4.s_addr);
 	for (cidr = 0; tmp != 0; cidr++)
 		tmp <<= 1;
-	snprintf(cidrstr, 3, "%d", cidr);
+	snprintf(cidrstr, 12, "%d", cidr);
 
 	if (script_env_append(envp, envc, "INTERNAL_CIDR4", cidrstr) != 0) {
 		plog(LLV_ERROR, LOCATION, NULL, "Cannot set INTERNAL_CIDR4\n");


signature.asc
Description: PGP signature

Bug#853430: marked as done (gosmore: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 05:13:59 +
with message-id 
and subject line Bug#870812: Removed package(s) from unstable
has caused the Debian Bug report #853430,
regarding gosmore: 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.)


-- 
853430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gosmore
Version: 0.0.0.svn30327-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/gosmore_0.0.0.svn30327-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 /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from jni/gosmore.cpp:83:
/usr/include/glib-2.0/glib/deprecated/gthread.h:265:10: note: declared here
 void g_thread_init   (gpointer vtable);
  ^
jni/gosmore.cpp:3377:22: warning: 'void g_thread_init(gpointer)' is deprecated 
[-Wdeprecated-declarations]
   g_thread_init (NULL);  // Something to do with curl progress bar

  ^
In file included from /usr/include/glib-2.0/glib.h:107:0,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from jni/gosmore.cpp:83:
/usr/include/glib-2.0/glib/deprecated/gthread.h:265:10: note: declared here
 void g_thread_init   (gpointer vtable);
  ^
In file included from /usr/include/gtk-2.0/gtk/gtkcalendar.h:40:0,
 from /usr/include/gtk-2.0/gtk/gtk.h:53,
 from jni/gosmore.cpp:83:
jni/gosmore.cpp:3425:46: warning: cast to pointer from integer of different 
size [-Wint-to-pointer-cast]
   GTK_SIGNAL_FUNC (HitGtkButton), (char*)i);

  ^
/usr/include/gtk-2.0/gtk/gtksignal.h:51:62: note: in definition of macro 
'gtk_signal_connect'
gtk_signal_connect_full ((object), (name), (func), NULL, (func_data), NULL, 
0, 0)
  ^
jni/gosmore.cpp: At global scope:
jni/gosmore.cpp:2070:14: warning: 'casing' defined but not used 
[-Wunused-variable]
 static short casing[10 + CASING_MAX * 2];
  ^~
Makefile:56: recipe for target 'gosmore' failed
make[1]: *** [gosmore] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j64 returned exit code 2
debian/rules:17: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 0.0.0.svn30327-1+rm

Dear 

Bug#824046: marked as done (libtkx-perl: FTBFS: Tcl error 'Foo at /usr/lib/x86_64-linux-gnu/perl5/5.22/Tcl.pm line 585.\n' while invoking scalar result call)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 05:05:37 +
with message-id 
and subject line Bug#870495: Removed package(s) from unstable
has caused the Debian Bug report #824046,
regarding libtkx-perl: FTBFS: Tcl error 'Foo at 
/usr/lib/x86_64-linux-gnu/perl5/5.22/Tcl.pm line 585.\n' while invoking scalar 
result call
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.)


-- 
824046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtkx-perl
Version: 1.09-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

libtkx-perl fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../libglapi-mesa_11.2.1-2_amd64.deb ...
  Unpacking libglapi-mesa:amd64 (11.2.1-2) ...
  Selecting previously unselected package libx11-xcb1:amd64.
  Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1_amd64.deb ...
  Unpacking libx11-xcb1:amd64 (2:1.6.3-1) ...
  Selecting previously unselected package libxcb-dri2-0:amd64.
  Preparing to unpack .../libxcb-dri2-0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-dri2-0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-dri3-0:amd64.
  Preparing to unpack .../libxcb-dri3-0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-dri3-0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-glx0:amd64.
  Preparing to unpack .../libxcb-glx0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-glx0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-present0:amd64.
  Preparing to unpack .../libxcb-present0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-present0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-randr0:amd64.
  Preparing to unpack .../libxcb-randr0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-randr0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-render0:amd64.
  Preparing to unpack .../libxcb-render0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-render0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-shape0:amd64.
  Preparing to unpack .../libxcb-shape0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-shape0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-sync1:amd64.
  Preparing to unpack .../libxcb-sync1_1.11.1-1_amd64.deb ...
  Unpacking libxcb-sync1:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-xfixes0:amd64.
  Preparing to unpack .../libxcb-xfixes0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-xfixes0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxfixes3:amd64.
  Preparing to unpack .../libxfixes3_1%3a5.0.1-2+b2_amd64.deb ...
  Unpacking libxfixes3:amd64 (1:5.0.1-2+b2) ...
  Selecting previously unselected package libxdamage1:amd64.
  Preparing to unpack .../libxdamage1_1%3a1.1.4-2+b1_amd64.deb ...
  Unpacking libxdamage1:amd64 (1:1.1.4-2+b1) ...
  Selecting previously unselected package libxshmfence1:amd64.
  Preparing to unpack .../libxshmfence1_1.2-1_amd64.deb ...
  Unpacking libxshmfence1:amd64 (1.2-1) ...
  Selecting previously unselected package libxxf86vm1:amd64.
  Preparing to unpack .../libxxf86vm1_1%3a1.1.4-1_amd64.deb ...
  Unpacking libxxf86vm1:amd64 (1:1.1.4-1) ...
  Selecting previously unselected package libgl1-mesa-glx:amd64.
  Preparing to unpack .../libgl1-mesa-glx_11.2.1-2_amd64.deb ...
  Unpacking libgl1-mesa-glx:amd64 (11.2.1-2) ...
  Selecting previously unselected package libpixman-1-0:amd64.
  Preparing to unpack .../libpixman-1-0_0.33.6-1_amd64.deb ...
  Unpacking libpixman-1-0:amd64 (0.33.6-1) ...
  Selecting previously unselected package libfontenc1:amd64.
  Preparing to unpack .../libfontenc1_1%3a1.1.3-1_amd64.deb ...
  Unpacking libfontenc1:amd64 (1:1.1.3-1) ...
  Selecting previously unselected package libxfont1:amd64.
  Preparing to unpack .../libxfont1_1%3a1.5.1-1_amd64.deb ...
  Unpacking libxfont1:amd64 (1:1.5.1-1) ...
  Selecting previously unselected package xvfb.
  Preparing to unpack .../xvfb_2%3a1.18.3-1_amd64.deb ...
  Unpacking xvfb (2:1.18.3-1) ...
  Processing triggers for libc-bin (2.22-7) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for systemd (229-5) ...
  Setting up libtcl8.6:amd64 (8.6.5+dfsg-2) ...
  Setting up libtcl-perl (1.04+ds-1) ...
  Setting up libpng16-16:amd64 (1.6.21-4) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up ucf (3.0036) ...
  Setting up fonts-dejavu-core (2.35-1) 

Bug#868011: marked as done (wcsaxes deprecated; about to remove)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 05:04:21 +
with message-id 
and subject line Bug#870486: Removed package(s) from unstable
has caused the Debian Bug report #868011,
regarding wcsaxes deprecated; about to remove
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.)


-- 
868011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wcsaxes
Version: 0.9-1
Severity: grave
Tags: buster sid
Control: block 867906 by -1

Hi,

wcsaxes is deprecated since a while and going to be replaced by astropy:

import astropy.visualization.wcsaxes

does the same thing now. Since there is an RC bugreport #867906, I don't
see a reason to keep it in testing. So, if you really want to keep it,
tell me that you want to take over. Otherwise, I will ask ftp-masters to
remove it in a few weeks.

Best regards

Ole
--- End Message ---
--- Begin Message ---
Version: 0.9-1+rm

Dear submitter,

as the package wcsaxes has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870486

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#824839: marked as done (librrd-simple-perl: FTBFS on armhf and arm64: t/23graph.t failures)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 05:05:00 +
with message-id 
and subject line Bug#870494: Removed package(s) from unstable
has caused the Debian Bug report #824839,
regarding librrd-simple-perl: FTBFS on armhf and arm64: t/23graph.t failures
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.)


-- 
824839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librrd-simple-perl
Version: 1.44-3
Severity: serious
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
User: debian-p...@lists.debian.org
Usertags: autopkgtest zrh2016

This package fails to build from source on armhf on
tests.reproducible-builds.org, and fails its test suite on arm64 on
ci.debian.net. In both cases t/23graph.t fails, but the failing test
cases differ.

 
https://tests.reproducible-builds.org/rb-pkg/unstable/armhf/librrd-simple-perl.html
 https://ci.debian.net/packages/libr/librrd-simple-perl/unstable/arm64/

arm64:

Test Summary Report
---
t/23graph.t  (Wstat: 1536 Tests: 226 Failed: 6)
  Failed tests:  77-79, 129, 174, 176
  Non-zero exit status: 6


armhf:

Test Summary Report
---
t/23graph.t  (Wstat: 1536 Tests: 226 Failed: 6)
  Failed tests:  73, 75, 162, 207, 209, 211
  Non-zero exit status: 6

#   Failed test 'graph() return hash (annual)'
#   at t/23graph.t line 69.
# Compared $data->[0]
#got : 'bytesIn min nan'
# expect : 'bytesIn min -nan'

#   Failed test 'graph() return hash (monthly)'
#   at t/23graph.t line 69.
# Compared $data->[0]
#got : 'bytesIn min nan'
# expect : 'bytesIn min -nan'

#   Failed test 'graph() return hash (monthly)'
#   at t/23graph.t line 69.
# Compared $data->[0]
#got : 'bytesIn min nan'
# expect : 'bytesIn min -nan'

#   Failed test 'graph() return hash (3years)'
#   at t/23graph.t line 69.
# Compared $data->[0]
#got : 'bytesIn min nan'
# expect : 'bytesIn min -nan'

#   Failed test 'graph() return hash (monthly)'
#   at t/23graph.t line 69.
# Compared $data->[0]
#got : 'bytesIn min nan'
# expect : 'bytesIn min -nan'

#   Failed test 'graph() return hash (annual)'
#   at t/23graph.t line 69.
# Compared $data->[0]
#got : 'bytesIn min nan'
# expect : 'bytesIn min -nan'
# Looks like you failed 6 tests of 226.

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Version: 1.44-4+rm

Dear submitter,

as the package librrd-simple-perl has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870494

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#867906: marked as done (wcsaxes FTBFS with python 3.6 as supported version)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 05:04:21 +
with message-id 
and subject line Bug#870486: Removed package(s) from unstable
has caused the Debian Bug report #867906,
regarding wcsaxes 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.)


-- 
867906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wcsaxes
Version: 0.9-1
Severity: serious
Tags: patch buster sid

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

...
= test session starts ==
platform linux -- Python 3.6.2rc2, pytest-3.0.6, py-1.4.34, pluggy-0.4.0 -- 
/usr/bin/python3.6
cachedir: ../.cache

Running tests with wcsaxes version 0.9.
Running tests in lib.linux-x86_64-3.6/wcsaxes docs.

Date: 2017-07-10T00:59:56

Platform: Linux-4.9.0-3-amd64-x86_64-with-debian-buster-sid

Executable: /usr/bin/python3.6

Full Python Version: 
3.6.2rc2 (default, Jul  8 2017, 14:29:22) 
[GCC 6.4.0 20170704]

encodings: sys: utf-8, locale: ANSI_X3.4-1968, filesystem: ascii
byteorder: little
float info: dig: 15, mant_dig: 15

Numpy: 1.12.1
Scipy: not available
Matplotlib: 2.0.0
h5py: not available
Pandas: not available
Astropy: 1.3.3
Using Astropy options: remote_data.

rootdir: /tmp/wcsaxes-test-28xjlge8, inifile: setup.cfg
collecting ... collected 48 items / 2 errors

 ERRORS 
 ERROR collecting lib.linux-x86_64-3.6/wcsaxes/tests/test_formatter_locator.py _
/usr/lib/python3/dist-packages/astropy/tests/pytest_plugins.py:175: in collect
module = self.fspath.pyimport()
/usr/lib/python3/dist-packages/py/_path/local.py:662: in pyimport
__import__(modname)
E File 
"/tmp/wcsaxes-test-28xjlge8/lib.linux-x86_64-3.6/wcsaxes/tests/test_formatter_locator.py",
 line 155
E   assert fl.formatter([15.392231] * u.degree, None)[0] == 
"15$^\circ$23'32\""
E  ^
E   SyntaxError: invalid escape sequence \c
 ERROR collecting lib.linux-x86_64-3.6/wcsaxes/tests/test_formatter_locator.py _
/usr/lib/python3/dist-packages/_pytest/python.py:418: in _importtestmodule
mod = self.fspath.pyimport(ensuresyspath=importmode)
/usr/lib/python3/dist-packages/py/_path/local.py:662: in pyimport
__import__(modname)
E File 
"/tmp/wcsaxes-test-28xjlge8/lib.linux-x86_64-3.6/wcsaxes/tests/test_formatter_locator.py",
 line 155
E   assert fl.formatter([15.392231] * u.degree, None)[0] == 
"15$^\circ$23'32\""
E  ^
E   SyntaxError: invalid escape sequence \c
 pytest-warning summary 
WC1 None [pytest] section in setup.cfg files is deprecated, use [tool:pytest] 
instead.
!!! Interrupted: 2 errors during collection 
== 1 pytest-warnings, 2 error in 1.45 seconds ==
/usr/lib/python3/dist-packages/astropy/config/configuration.py:541: 
ConfigurationMissingWarning: Configuration defaults will be used due to 
FileNotFoundError:2 on None
  warn(ConfigurationMissingWarning(msg))
debian/rules:14: recipe for target 'test-python3.6' failed
make[1]: *** [test-python3.6] Error 2
make[1]: Leaving directory '/build/1st/wcsaxes-0.9'
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2


Attached is the patch I found in Ubuntu.
diff -pruN 0.9-1/debian/patches/invalid-escapes.patch 
0.9-1ubuntu1/debian/patches/invalid-escapes.patch
--- 0.9-1/debian/patches/invalid-escapes.patch  1970-01-01 00:00:00.0 
+
+++ 0.9-1ubuntu1/debian/patches/invalid-escapes.patch   2017-06-21 
10:15:07.0 +
@@ -0,0 +1,11 @@
+--- a/wcsaxes/tests/test_formatter_locator.py
 b/wcsaxes/tests/test_formatter_locator.py
+@@ -152,7 +152,7 @@
+ assert fl.formatter([15.392231] * u.degree, None)[0] == 
six.u('15\xb023\'32"')
+ from ..rc_utils import rc_context
+ with rc_context(rc={'text.usetex': True}):
+-assert fl.formatter([15.392231] * u.degree, None)[0] == 
"15$^\circ$23'32\""
++assert fl.formatter([15.392231] * u.degree, None)[0] == 
"15$^\\circ$23'32\""
+ 
+ @pytest.mark.parametrize(('format'), ['x.xxx', 'dd.ss', 'dd:ss', 
'mdd:mm:ss'])
+ def test_invalid_formats(self, format):
diff -pruN 0.9-1/debian/patches/series 0.9-1ubuntu1/debian/patches/series
--- 

Bug#817729: marked as done (wysihtml: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 05:02:08 +
with message-id 
and subject line Bug#870441: Removed package(s) from unstable
has caused the Debian Bug report #817729,
regarding wysihtml: Removal of debhelper compat 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.)


-- 
817729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wysihtml
Severity: important
Usertags: compat-4-removal

Hi,

The package wysihtml uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 0.13-5.2+rm

Dear submitter,

as the package wysihtml has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870441

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#870377: marked as done (gcc-5-doc: FTBFS with perl 5.26: Unescaped left brace in regex is illegal)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 05:01:23 +
with message-id 
and subject line Bug#870438: Removed package(s) from unstable
has caused the Debian Bug report #870377,
regarding gcc-5-doc: FTBFS with perl 5.26: Unescaped left brace in regex is 
illegal
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.)


-- 
870377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-5-doc
Version: 5.3.0-2
Severity: serious
Tags: sid buster
Justification: fails to build from source

[...]
(cd gcc/doc && perl ../../contrib/texi2pod.pl -Dfngccint=gccint-5 
-DBUGURL=http://bugs.debian.org/) < gcc/doc/invoke.texi > gcc.pod
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in 
m/^\@strong{ <-- HERE (.*)}$/ at ../../contrib/texi2pod.pl line 319.
debian/Makefile:198: recipe for target 'gcc.pod' failed
make[2]: *** [gcc.pod] Error 255
make[2]: Leaving directory '/build/gcc-5-doc-5.3.0'
debian/rules:56: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
[...]

Andreas


gcc-5-doc_5.3.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 5.3.0-2+rm

Dear submitter,

as the package gcc-5-doc has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870438

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#678216: marked as done (icewm-themes: copyright file does not give location of source, licence statements not included)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 04:52:26 +
with message-id 
and subject line Bug#869982: Removed package(s) from unstable
has caused the Debian Bug report #678216,
regarding icewm-themes: copyright file does not give location of source, 
licence statements not included
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.)


-- 
678216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icewm-themes
Version: 1.2.26-2
Severity: serious
Justification: §12.5 copyright must say where the upstream sources were obtained

We were looking at this package as a result of a question on #debian and
realised that, on the basis of the information in debian/copyright, we had
no idea where these themes had actually come from and that there was no
evidence that these themes were indeed licensed under the GPL-2 as asserted.

Currently, debian/copyright points to

  http://www.icewm.org/index.php?page=download

for tarballs, but none are apparent on this page, just a link to a generic
theme download site box-look.org. I looked for a few of the themes there and
didn't find them.

There is then a pretty vague statement that "most themes have been downloaded
or updated" from

  http://themes.freshmeat.net/

This website no longer exists and redirects to a generic software archive
page. I tried to find a few of these themes in this generic archive and
was not able to do so. "Most" is also not sufficient for me to work out which
themes are from this site or perhaps some other site.

Next is a statement that some themes were obtained from:

  http://samael.k.pl/~michal/aeteria.html

which is a webserver that doesn't appear to ever respond. Also, which themes
were from there? grep gives me a list of a few, but is that all of them? I
guess I would expect debian/copyright to tell me this in an aggregated work
like this.


I then moved on from debian/copyright and looked for more information to work
out where these themes had come from. The package comes with a README.source
that looked promising as a way of documenting where the themes came from...
excellent... except:

  "modifications are applied through the dpatch mechanism."

A minor thing -- this package no longer uses dpatch as of the last upload.

  "The currently available themes (and those that are processed by Makefile)
  are listed in THEME.list."

What THEME.list?

  "They are either downloadable from the mentioned location"

Mentioned where? Is this in the missing THEME.list? It's certainly not in
copyright. It's not in the default.theme file in the theme directories.

  "apt-get source icewm-themes"

That doesn't really sound like instructions for where the upstream sources
were obtained... it's a bit self-referential!

  "make getfromdeb" gets them only from the source package.
  "make shownew" shows new dirs, looking like theme dirs and
  "make checkin" adds all new dirs to the THEME.list.

None of these targets exist in the Makefile.


I understand that debian/copyright for a package that is assembled from
multiple sources like this is a complicated thing to write and maintain.
I would, however, expect to see the information required by policy to be
listed and the information required by the ftp team to be listed. For example,
the ftp team has previously offered the following advice on what should be
in a copyright file:

  http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html

Based on that, it would be nice to clearly describe EACH theme:

Theme: blah
URL: http://example.org/themes/blah
Copyright: 2001-2003 Jane Smith
Licence: This is free software blah blah...

(the copyright format 1.0 (formerly known as DEP-5) may be of use here too,
but doesn't handle multi-component sources like this gracefully)

Ideally, each directory would have some sort of README or AUTHORS as some of
them already do. In this files, the creator of the theme is stating that the
licence is as claimed in debian/copyright. I realise that this is not always
possible though. Shame. Being able to demonstrate that the licence is what you
say it is wins over an assertion without evidence.

For your information, the visitor to #debian who brought this up stated that he
believed that a number of these themes were NOT GPLv2 as asserted and that some
were undistributable. I guess you can expect him to file a separate bug report
about that.

cheers
Stuart


--- End Message ---
--- Begin Message ---
Version: 1.2.26-2+rm

Dear submitter,

as the package icewm-themes has just 

Bug#818121: marked as done (consul-migrate: FTBFS in stretch)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 04:48:49 +
with message-id 
and subject line Bug#869543: Removed package(s) from unstable
has caused the Debian Bug report #818121,
regarding consul-migrate: FTBFS in stretch
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.)


-- 
818121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:consul-migrate
Version: 0.1.0-1
Severity: serious

Dear maintainer:

This package currently FTBFS in stretch:


=== RUN   TestMigrator_migrate
--- FAIL: TestMigrator_migrate (2.01s)
panic: runtime error: cgo argument has Go pointer to Go pointer [recovered]
panic: runtime error: cgo argument has Go pointer to Go pointer


The full build log is attached.

Thanks.

consul-migrate_0.1.0-1_amd64-20160313-2249.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.1.0-1+rm

Dear submitter,

as the package consul-migrate has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/869543

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#784619: marked as done ([creepy] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 04:45:41 +
with message-id 
and subject line Bug#869366: Removed package(s) from unstable
has caused the Debian Bug report #784619,
regarding [creepy] Qt4's WebKit removal
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.)


-- 
784619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: creepy
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Hi! As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce]. Your package seems to be using it via PyQt4's
QtWebKit module.

[announce] 


Basically we are about to get the last Qt4 point release and upstream is
migrating from WebKit to Blink in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit (Qt5's WebKit is expected to stay supported
until Qt6).

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5 
  port of your application
- if there are no activities regarding porting, investigate whether there are 
  suitable alternatives for your users
- if there is a Qt5/PyQt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian 
  archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] and the
PyQt4 vs PyQt5 differences page [pyqtchanges] whenever you start porting
your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html
[pyqtchanges] http://pyqt.sourceforge.net/Docs/PyQt5/pyqt4_differences.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE 
team at debian-qt-...@lists.debian.org.

--
Dmitry Shachnev,
on behalf of the Qt4 and PyQt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 1.4.1-5+rm

Dear submitter,

as the package creepy has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/869366

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#844997: marked as done (creepy: Depends on PyQt4.QtWebKit)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 04:45:41 +
with message-id 
and subject line Bug#869366: Removed package(s) from unstable
has caused the Debian Bug report #784619,
regarding creepy: Depends on PyQt4.QtWebKit
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.)


-- 
784619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: creepy
Version: 1.4.1-5
Severity: serious
Justification: Policy 3.5

Hi,

creepy depends on PyQt4.QtWebKit:

  % creepy
  Traceback (most recent call last):
File "/usr/bin/creepy", line 19, in 
  from PyQt4.QtWebKit import QWebPage, QWebSettings
  ImportError: No module named QtWebKit

The package only depends on python-qt4 which does not seem sufficient to
satisfy this. In unstable python-pyqt5.qtwebkit is available but no
PyQt4 variant thereof.

Cheers,
Sebastian

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x2F1FFCC7 +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.4.1-5+rm

Dear submitter,

as the package creepy has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/869366

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: notfixed 859577 in 0.0~git20170302.0.3c5717c-1

[Debian Bug Tracking System]

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

> notfixed 859577 0.0~git20170302.0.3c5717c-1
Bug #859577 {Done: Michael Lustfield } 
[golang-github-syndtr-goleveldb-dev] golang-github-syndtr-goleveldb-dev: file 
conflict with golang-goleveldb-dev
No longer marked as fixed in versions 
golang-github-syndtr-goleveldb/0.0~git20170302.0.3c5717c-1.
> thanks
Stopping processing here.

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

Bug#654939: marked as done (mtpfs: broken overnight)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 04:35:21 +
with message-id 
and subject line Bug#868982: Removed package(s) from unstable
has caused the Debian Bug report #654939,
regarding mtpfs: broken overnight
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.)


-- 
654939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mtpfs
Version: 1.0-1
Severity: grave
Justification: renders package unusable

Just stopped working.  I could use it yesterday, but not today.
The only thing I can recall, which may or may not be related is an
upgrade of util-linux and mount.

The command 'mtpfs /media/mountpoint' returns exit status succes.
But 'ls' shows something odd:

d?  ? ??   ?? /media/mountpoint

and, of course, the remote file system is not accessible.
I can use 'fusermount -u /media/mountpoint' to return things to normal,
though.

Also, attempted to rebuild the mtpfs package, hoping that compiling
against fresher dependencies would return things to a functional state.
But no joy :(  FTBFS (and a few other warnings too):

...
configure: WARNING: unrecognized options: --disable-maintainer-mode
...
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: 
ignored.
...
dh_pysupport: This program is deprecated, you should use dh_python2 instead. 
Migration guide: http://deb.li/dhs2p
...
dpkg-shlibdeps: error: no dependency information found for /lib/libusb-0.1.so.4 
(used by debian/mtpfs/usr/bin/mtpfs).
dh_shlibdeps: dpkg-shlibdeps -Tdebian/mtpfs.substvars 
debian/mtpfs/usr/bin/mtpfs returned exit code 2


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages mtpfs depends on:
ii  fuse-utils2.8.6-4
ii  libc6 2.13-24
ii  libfuse2  2.8.6-4
ii  libglib2.0-0  2.30.2-4
ii  libid3tag00.15.1b-10
ii  libmad0   0.15.1b-6
ii  libmtp9   1.1.1-1
ii  libusb-0.1-4  2:0.1.12-20
ii  zlib1g1:1.2.3.4.dfsg-3

mtpfs recommends no packages.

mtpfs suggests no packages.

-- no debconf information


Cheers,

-- 
Cristian


--- End Message ---
--- Begin Message ---
Version: 1.1-5+rm

Dear submitter,

as the package mtpfs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/868982

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#868774: marked as done (rabbit FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2017 04:18:54 +
with message-id 
and subject line Bug#868774: fixed in rabbit 2.2.0-1
has caused the Debian Bug report #868774,
regarding rabbit FTBFS: test failures
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.)


-- 
868774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rabbit
Version: 2.1.9-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes rabbit FTBFS:

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

...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/1st/rabbit-2.1.9/debian/rabbit/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/rabbit/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 debian/ruby-tests.rb
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous 

Processed: tagging 870299

[Debian Bug Tracking System]

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

> tags 870299 + patch
Bug #870299 [src:links2] links: CVE-2017-4
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#870299: Fwd: Bug#870299: links: CVE-2017-11114 [origin: g...@debian.org]

[Mikulas Patocka]

On Mon, 31 Jul 2017, Axel Beckert wrote:

> Hi Mikulas,
> 
> not sure if you received that bug report already, too.
> 
>   Regards, Axel

Hi

Here I send a patch for this bug.

Mikulas



commit fee5dca79a93a37024e494b985386a5fe60bc1b7
Author: Mikulas Patocka 
Date:   Wed Aug 2 20:13:29 2017 +0200

Fix read out of memory in case of corrupted UTF-8 data

---
 charsets.c |   37 +
 links.h|9 -
 2 files changed, 5 insertions(+), 41 deletions(-)

Index: links-2.14/charsets.c
===
--- links-2.14.orig/charsets.c
+++ links-2.14/charsets.c
@@ -215,41 +215,6 @@ static struct conv_table *get_translatio
return utf_table;
 }
 
-unsigned short int utf8_2_uni_table[0x200] = {
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 128,   0, 0, 0, 192,   0,
-   0, 0, 256,  0, 0, 0, 320,   0, 0, 0, 384,   0, 0, 0, 448,   0,
-   0, 0, 512,  0, 0, 0, 576,   0, 0, 0, 640,   0, 0, 0, 704,   0,
-   0, 0, 768,  0, 0, 0, 832,   0, 0, 0, 896,   0, 0, 0, 960,   0,
-   0, 0, 1024, 0, 0, 0, 1088,  0, 0, 0, 1152,  0, 0, 0, 1216,  0,
-   0, 0, 1280, 0, 0, 0, 1344,  0, 0, 0, 1408,  0, 0, 0, 1472,  0,
-   0, 0, 1536, 0, 0, 0, 1600,  0, 0, 0, 1664,  0, 0, 0, 1728,  0,
-   0, 0, 1792, 0, 0, 0, 1856,  0, 0, 0, 1920,  0, 0, 0, 1984,  0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-   0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
-};
-
 unsigned char utf_8_1[256] = {
6, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7,
7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7,
@@ -269,7 +234,7 @@ unsigned char utf_8_1[256] = {
3, 3, 3, 3, 3, 3, 3, 3, 2, 2, 2, 2, 1, 1, 6, 6,
 };
 
-static_const unsigned min_utf_8[9] = {
+static_const unsigned min_utf_8[8] = {
0, 0x400, 0x20, 0x1, 0x800, 0x80, 0x100, 0x1,
 };
 
Index: links-2.14/links.h
===
--- links-2.14.orig/links.h
+++ links-2.14/links.h
@@ -3906,15 +3906,14 @@ unsigned char *cp_strchr(int charset, un
 void init_charset(void);
 
 unsigned get_utf_8(unsigned char **p);
-extern unsigned short int utf8_2_uni_table[0x200];
 #define GET_UTF_8(s, c)
\
 do {   \
if ((unsigned char)(s)[0] < 0x80)   \
(c) = (s)++[0]; \
-   else if (((c) = utf8_2_uni_table[((unsigned char)(s)[0] << 2) + \
-   ((unsigned char)(s)[1] >> 6) - 0x200])) \
-   (c) += (unsigned char)(s)[1] & 0x3f, (s) += 2;  \
-   else\
+   else if ((unsigned char)(s)[0] >= 0xc2 && (unsigned char)(s)[0] < 0xe0 
&&\
+((unsigned char)(s)[1] & 0xc0) == 0x80) {  \
+   (c) = (unsigned char)(s)[0] * 0x40 + (unsigned char)(s)[1], (c) 
-= 0x3080, (s) += 2;\
+   } else  \
(c) = get_utf_8(&(s));  \
 } while 

Bug#853575: marked as done (nomacs: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 23:03:51 +
with message-id 
and subject line Bug#853575: fixed in nomacs 3.4.1+dfsg-9
has caused the Debian Bug report #853575,
regarding nomacs: 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.)


-- 
853575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nomacs
Version: 3.4.1+dfsg-5
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
  (c++)"QtSharedPointer::ExternalRefCountWithCustomDeleter::deleter(QtSharedPointer::ExternalRefCountData*)@Base"
 3.2.0
  (c++)"QtSharedPointer::ExternalRefCountWithCustomDeleter::deleter(QtSharedPointer::ExternalRefCountData*)@Base"
 3.2.0
  (c++)"VTT for QtConcurrent::MapKernel >@Base" 3.2.0
+ _ZN5QListI7QStringE10removeLastEv@Base 3.4.1+dfsg-5
+ _ZN7QVectorI14QSharedPointerIN3nmc17DkImageContainerTEEE6resizeEi@Base 
3.4.1+dfsg-5
+ _ZN7QVectorI6QImageE6resizeEi@Base 3.4.1+dfsg-5
+ 
_ZNSt6vectorIN3nmc11DkThumbNailESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 3.4.1+dfsg-5
  (c++)"cv::Mat::~Mat()@Base" 3.2.0
  (c++)"guard variable for 
QtPrivate::MetaTypeSmartPointerHelper::registerConverter(int)::f@Base" 3.2.0
  (c++)"guard variable for 
QtPrivate::ValueTypeIsMetaType, true>::registerConverter(int)::f@Base" 3.2.0
@@ -494,7 +498,7 @@
  (c++)"nmc::DkBasicLoader::undo()@Base" 3.2.0
  (c++)"nmc::DkBasicLoader::writeBufferToFile(QString const&, 
QSharedPointer) const@Base" 3.2.0
  (c++)"nmc::DkBasicLoader::~DkBasicLoader()@Base" 3.2.0
- (c++)"nmc::DkBatchConfig::DkBatchConfig()@Base" 3.4.1
+#MISSING: 3.4.1+dfsg-5# (c++)"nmc::DkBatchConfig::DkBatchConfig()@Base" 3.4.1
  (c++)"nmc::DkBatchConfig::DkBatchConfig(QStringList const&, QString const&, 
QString const&)@Base" 3.2.0
  (c++)"nmc::DkBatchConfig::isOk() const@Base" 3.2.0
  (c++)"nmc::DkBatchConfig::loadSettings(QSettings&)@Base" 3.4.1
@@ -1266,7 +1270,7 @@
  (c++)"non-virtual thunk to 
QtConcurrent::RunFunctionTask::run()@Base" 3.2.0
  (c++)"non-virtual thunk to 
QtConcurrent::RunFunctionTask::~RunFunctionTask()@Base" 3.2.0
  (c++)"non-virtual thunk to 
QtConcurrent::RunFunctionTask 
>::run()@Base" 3.2.0
- (c++)"non-virtual thunk to 
QtConcurrent::RunFunctionTask 
>::~RunFunctionTask()@Base" 3.2.0
+#MISSING: 3.4.1+dfsg-5# (c++)"non-virtual thunk to 
QtConcurrent::RunFunctionTask 
>::~RunFunctionTask()@Base" 3.2.0
  (c++)"non-virtual thunk to QtConcurrent::RunFunctionTask::run()@Base" 
3.2.0
  (c++)"non-virtual thunk to 
QtConcurrent::RunFunctionTaskBase::run()@Base" 3.2.0
  (c++)"non-virtual thunk to 
QtConcurrent::RunFunctionTaskBase::run()@Base" 
3.2.0
@@ -1314,7 +1318,7 @@
  (optional|c++)"std::__cxx11::basic_string std::operator+(char const*, std::__cxx11::basic_string const&)@Base" 3.2.0
  (optional|c++)"std::__cxx11::basic_stringbuf

Bug#853449: marked as done (icedove: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 18:38:33 -0400
with message-id <20170805223833.zncqcen6h6pxm...@x260.cruise.homelinux.net>
and subject line Re: GCC 7 now the default in unstable: bumping the priority of 
the ftbfs issues
has caused the Debian Bug report #853449,
regarding icedove: 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.)


-- 
853449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:icedove
Version: 1:45.6.0-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
make[6]: Leaving directory '/<>/obj-icedove/layout/tables'
make[6]: Leaving directory '/<>/obj-icedove/layout/generic'
/<>/mozilla/config/recurse.mk:71: recipe for target 
'layout/generic/target' failed
make[5]: *** [layout/generic/target] Error 2
In file included from 
/<>/obj-icedove/editor/libeditor/Unified_cpp_editor_libeditor1.cpp:11:0:
/<>/mozilla/editor/libeditor/nsEditor.cpp: In member function 
'nsresult nsEditor::JoinNodes(nsINode&, nsINode&)':
/<>/mozilla/editor/libeditor/nsEditor.cpp:1496:10: warning: 
'result' may be used uninitialized in this function [-Wmaybe-uninitialized]
   return result;
  ^~
In file included from ../../dist/include/mozilla/dom/Selection.h:12:0,
 from 
/<>/mozilla/editor/libeditor/TypeInState.cpp:10,
 from 
/<>/obj-icedove/editor/libeditor/Unified_cpp_editor_libeditor1.cpp:2:
../../dist/include/mozilla/AutoRestore.h: In member function 'virtual nsresult 
nsHTMLEditor::SelectAll()':
../../dist/include/mozilla/AutoRestore.h:45:17: warning: '*((void*)& 
userSelection +16)' may be used uninitialized in this function 
[-Wmaybe-uninitialized]
 mLocation = mValue;
 ^~
In file included from 
/<>/obj-icedove/editor/libeditor/Unified_cpp_editor_libeditor1.cpp:110:0:
/<>/mozilla/editor/libeditor/nsHTMLEditor.cpp:3567:53: note: 
'*((void*)& userSelection +16)' was declared here
   Maybe userSelection;
 ^
In file included from ../../dist/include/mozilla/dom/Selection.h:12:0,
 from 
/<>/mozilla/editor/libeditor/TypeInState.cpp:10,
 from 
/<>/obj-icedove/editor/libeditor/Unified_cpp_editor_libeditor1.cpp:2:
../../dist/include/mozilla/AutoRestore.h:45:5: warning: '*((void*)(& 
userSelection)+8).mozilla::AutoRestore::mLocation' may be used 
uninitialized in this function [-Wmaybe-uninitialized]
 mLocation = mValue;
 ^
In file included from 
/<>/obj-icedove/editor/libeditor/Unified_cpp_editor_libeditor1.cpp:110:0:
/<>/mozilla/editor/libeditor/nsHTMLEditor.cpp:3567:53: note: 
'*((void*)(& userSelection)+8).mozilla::AutoRestore::mLocation' was 
declared here
   Maybe userSelection;
 ^
libeditor_libeditor.a.desc
rm -f libeditor_libeditor.a
/<>/obj-icedove/_virtualenv/bin/python 
/<>/mozilla/config/expandlibs_gen.py -o libeditor_libeditor.a.desc 
Unified_cpp_editor_libeditor0.o Unified_cpp_editor_libeditor1.o 
Unified_cpp_editor_libeditor2.o  
make[6]: Leaving directory '/<>/obj-icedove/editor/libeditor'
make[5]: Leaving directory '/<>/obj-icedove'
/<>/mozilla/config/recurse.mk:32: recipe for target 'compile' 
failed
make[4]: *** [compile] Error 2
make[4]: Leaving directory '/<>/obj-icedove'

Bug#750946: Upstream dev of HTML::HTML5::Parser

[Kjetil Kjernsmo]

Hi all!

I just noticed https://bugs.debian.org/750946 since my Test::RDF depends on 
HTML::HTML5::Parser (though, I don't quite understand how that dependency 
arises) and I would be affected by a removal. 

I haven't looked at the problem itself, but I would just like to report 
that the upstream dev, Toby Inkster has recently resumed development after  
a hiatus, so all hope isn't lost. 

Best,

Kjetil

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 853440 src:capnproto
Bug #853440 [src:harvest-tools] harvest-tools: ftbfs with GCC-7
Bug reassigned from package 'src:harvest-tools' to 'src:capnproto'.
No longer marked as found in versions harvest-tools/1.3-1.
Ignoring request to alter fixed versions of bug #853440 to the same values 
previously set
> forcemerge 853342 853440
Bug #853342 [src:capnproto] capnproto: ftbfs with GCC-7
Bug #853539 [src:capnproto] mash: ftbfs with GCC-7
Bug #853440 [src:capnproto] harvest-tools: ftbfs with GCC-7
Set Bug forwarded-to-address to 'https://github.com/marbl/Mash/issues/47'.
Added indication that 853440 affects src:mash
Marked as found in versions capnproto/0.5.3-2.
Added tag(s) fixed-upstream.
Bug #853539 [src:capnproto] mash: ftbfs with GCC-7
Merged 853342 853440 853539
> affects 853440 src:harvest-tools
Bug #853440 [src:capnproto] harvest-tools: ftbfs with GCC-7
Bug #853342 [src:capnproto] capnproto: ftbfs with GCC-7
Bug #853539 [src:capnproto] mash: ftbfs with GCC-7
Added indication that 853440 affects src:harvest-tools
Added indication that 853342 affects src:harvest-tools
Added indication that 853539 affects src:harvest-tools
> thanks
Stopping processing here.

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

Bug#853669: marked as done (stella: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 21:55:38 +
with message-id 
and subject line Bug#853669: fixed in stella 5.0.1-1
has caused the Debian Bug report #853669,
regarding stella: 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.)


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

[...]
dpkg-buildpackage: info: source version 4.7.3-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Stephen Kitt 
 dpkg-source --before-build stella-4.7.3
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_testdir
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
test -f config.mak || echo "RM_REC := rm -f -r" > config.mak
dh_auto_clean
make -j64 distclean
make[2]: Entering directory '/<>'
rm -f src/emucore/AtariVox.o src/emucore/Booster.o src/emucore/Cart.o 
src/emucore/Cart0840.o src/emucore/Cart2K.o src/emucore/Cart3E.o 
src/emucore/Cart3EPlus.o src/emucore/Cart3F.o src/emucore/Cart4A50.o 
src/emucore/Cart4K.o src/emucore/Cart4KSC.o src/emucore/CartAR.o 
src/emucore/CartCM.o src/emucore/CartCTY.o src/emucore/CartCV.o 
src/emucore/CartCVPlus.o src/emucore/CartDASH.o src/emucore/CartDPC.o 
src/emucore/CartDPCPlus.o src/emucore/CartE0.o src/emucore/CartE7.o 
src/emucore/CartEF.o src/emucore/CartEFSC.o src/emucore/CartBF.o 
src/emucore/CartBFSC.o src/emucore/CartDF.o src/emucore/CartDFSC.o 
src/emucore/CartF0.o src/emucore/CartF4.o src/emucore/CartF4SC.o 
src/emucore/CartF6.o src/emucore/CartF6SC.o src/emucore/CartF8.o 
src/emucore/CartF8SC.o src/emucore/CartFA.o src/emucore/CartFA2.o 
src/emucore/CartFE.o src/emucore/CartMC.o src/emucore/CartMDM.o 
src/emucore/CartSB.o src/emucore/CartUA.o src/emucore/CartWD.o 
src/emucore/CartX07.o src/emucore/CompuMate.o src/emucore/Console.o src/
 emucore/Control.o src/emucore/Driving.o src/emucore/EventHandler.o 
src/emucore/EventJoyHandler.o src/emucore/FrameBuffer.o src/emucore/FBSurface.o 
src/emucore/FSNode.o src/emucore/Genesis.o src/emucore/Joystick.o 
src/emucore/Keyboard.o src/emucore/KidVid.o src/emucore/MindLink.o 
src/emucore/M6502.o src/emucore/M6532.o src/emucore/MT24LC256.o 
src/emucore/MD5.o src/emucore/OSystem.o src/emucore/Paddles.o 
src/emucore/Props.o src/emucore/PropsSet.o src/emucore/SaveKey.o 
src/emucore/Serializer.o src/emucore/Settings.o src/emucore/Switches.o 
src/emucore/StateManager.o src/emucore/System.o src/emucore/TIA.o 
src/emucore/TIASnd.o src/emucore/TIATables.o src/emucore/TIASurface.o 
src/emucore/TrackBall.o src/emucore/Thumbulator.o src/emucore/libemucore.a 
rm -f src/gui/AboutDialog.o src/gui/AudioDialog.o src/gui/BrowserDialog.o 
src/gui/ComboDialog.o src/gui/CommandDialog.o src/gui/CommandMenu.o 
src/gui/ContextMenu.o src/gui/DialogContainer.o src/gui/Dialog.o 
src/gui/EditableWidget.o src/gui/EditTextWidget.o src/gui/EventMappingWidget.o 
src/gui/FileListWidget.o src/gui/ConfigPathDialog.o src/gui/SnapshotDialog.o 
src/gui/Font.o src/gui/GameInfoDialog.o src/gui/GameList.o 
src/gui/GlobalPropsDialog.o src/gui/HelpDialog.o src/gui/InputDialog.o 
src/gui/InputTextDialog.o src/gui/JoystickDialog.o src/gui/Launcher.o 

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 853617 src:insighttoolkit4
Bug #853617 [src:plastimatch] plastimatch: ftbfs with GCC-7
Bug reassigned from package 'src:plastimatch' to 'src:insighttoolkit4'.
No longer marked as found in versions plastimatch/1.6.5+dfsg.1-1.
Ignoring request to alter fixed versions of bug #853617 to the same values 
previously set
> forcemerge 853386 853617
Bug #853386 [src:insighttoolkit4] elastix: ftbfs with GCC-7
Bug #853419 [src:insighttoolkit4] ginkgocadx: ftbfs with GCC-7
Bug #853454 [src:insighttoolkit4] insighttoolkit4: ftbfs with GCC-7
Bug #853460 [src:insighttoolkit4] itksnap: ftbfs with GCC-7
Bug #853602 [src:insighttoolkit4] otb: ftbfs with GCC-7
Bug #853460 [src:insighttoolkit4] itksnap: ftbfs with GCC-7
Removed indication that 853460 affects src:otb, src:elastix, src:ginkgocadx, 
and src:itksnap
Added indication that 853460 affects 
src:itksnap,src:ginkgocadx,src:elastix,src:otb
Removed indication that 853386 affects src:itksnap, src:otb, src:elastix, and 
src:ginkgocadx
Added indication that 853386 affects 
src:itksnap,src:ginkgocadx,src:elastix,src:otb
Removed indication that 853419 affects src:otb, src:elastix, src:ginkgocadx, 
and src:itksnap
Added indication that 853419 affects 
src:itksnap,src:ginkgocadx,src:elastix,src:otb
Removed indication that 853454 affects src:ginkgocadx, src:elastix, src:otb, 
and src:itksnap
Added indication that 853454 affects 
src:itksnap,src:ginkgocadx,src:elastix,src:otb
Removed indication that 853602 affects src:ginkgocadx, src:otb, src:elastix, 
and src:itksnap
Added indication that 853602 affects 
src:itksnap,src:ginkgocadx,src:elastix,src:otb
Bug #853617 [src:insighttoolkit4] plastimatch: ftbfs with GCC-7
Set Bug forwarded-to-address to 
'https://bugs.orfeo-toolbox.org/view.php?id=1354'.
Added indication that 853617 affects 
src:itksnap,src:ginkgocadx,src:elastix,src:otb
Marked as found in versions insighttoolkit4/4.10.1-dfsg1-1.1.
Added tag(s) upstream.
Bug #853419 [src:insighttoolkit4] ginkgocadx: ftbfs with GCC-7
Bug #853454 [src:insighttoolkit4] insighttoolkit4: ftbfs with GCC-7
Bug #853602 [src:insighttoolkit4] otb: ftbfs with GCC-7
Merged 853386 853419 853454 853460 853602 853617
> affects 853386 src:plastimatch
Bug #853386 [src:insighttoolkit4] elastix: ftbfs with GCC-7
Bug #853419 [src:insighttoolkit4] ginkgocadx: ftbfs with GCC-7
Bug #853454 [src:insighttoolkit4] insighttoolkit4: ftbfs with GCC-7
Bug #853460 [src:insighttoolkit4] itksnap: ftbfs with GCC-7
Bug #853602 [src:insighttoolkit4] otb: ftbfs with GCC-7
Bug #853617 [src:insighttoolkit4] plastimatch: ftbfs with GCC-7
Added indication that 853386 affects src:plastimatch
Added indication that 853419 affects src:plastimatch
Added indication that 853454 affects src:plastimatch
Added indication that 853460 affects src:plastimatch
Added indication that 853602 affects src:plastimatch
Added indication that 853617 affects src:plastimatch
> thanks
Stopping processing here.

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

Processed: Re: Bug#870678: winff autopkgtests fail with ffmpeg 3.3.3: No such filter: 'asyncts'

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #870678 [src:winff] winff autopkgtests fail with ffmpeg 3.3.3: No such 
filter: 'asyncts'
Severity set to 'normal' from 'grave'

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

Bug#870678: winff autopkgtests fail with ffmpeg 3.3.3: No such filter: 'asyncts'

[Paul Gevers]

Control: severity -1 normal

On 03-08-17 21:32, Steve Langasek wrote:
> I've confirmed that this autopkgtest is testing the same presets.xml which
> is installed by winff in the winff-data package, so it appears that this
> will genuinely cause winff to fail at runtime (i.e., this is not just a bug
> in the test).  I'm therefore marking it 'grave'.  Feel free to downgrade if
> you think this is wrong - it looks like only the presets for three Nokia
> devices are affected.

The autopkgtest is meant to catch changes in ffmpeg/libav. As it affects
only a very limited set of presets, and the user can relatively easy
work around this, I downgrade this to normal. Winff will not fail, the
conversion using this preset will fail.

This is more severe for Ubuntu though, as I do recognize, but for Debian
this is a normal bug.

> I would tag this bug 'sid', except that since autopkgtests don't gate
> testing in Debian, this autopkgtest regression does not stop the new ffmpeg
> from migrating to testing and breaking winff there.

Ack.

> I don't know the fix for this issue, as I'm not conversant with ffmpeg and
> so am not sure how to map the existing asyncts filter settings to the
> recommended af_aresample filter.  There does not appear to be a fix upstream
> for this yet in the winff github repo.

The most trivial way to fix it quickly is by just dropping the argument.
I'll try to fix it smarter. Upstream is basically in maintenance only
mode. Debian is one of the main reasons for changes (I make them). This
ffmpeg change is such a change.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#853616: marked as done (plasma-desktop: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 6 Aug 2017 00:45:08 +0300
with message-id <20170805214508.qercxntrw3362u4f@localhost>
and subject line plasma-desktop builds with gcc 7
has caused the Debian Bug report #853616,
regarding plasma-desktop: 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.)


-- 
853616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:plasma-desktop
Version: 4:5.8.4-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/plasma-desktop_5.8.4-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

[...]
/usr/bin/c++  -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fno-exceptions 
-Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -Wl,--no-undefined -Wl,--fatal-warnings 
-Wl,--enable-new-dtags -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined -shared  
-o kcm_style.so CMakeFiles/kcm_style.dir/__/krdb/krdb.cpp.o 
CMakeFiles/kcm_style.dir/styleconfdialog.cpp.o 
CMakeFiles/kcm_style.dir/kcmstyle.cpp.o 
CMakeFiles/kcm_style.dir/klauncher_iface.cpp.o 
CMakeFiles/kcm_style.dir/kcm_style_automoc.cpp.o 
/usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Plasma.so.5.28.0 -lSM -lICE -lX11 -lXext 
/usr/lib/x86_64-linux-gnu/libKF5KDELibs4Support.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5.28.0 /usr/lib/x86_64-linux-gnu/
 libKF5Package.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Crash.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Bookmarks.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Solid.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5UnitConversion.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Parts.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libKF5TextWidgets.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5SonnetUi.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Attica.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Completion.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Service.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5I18
 n.so.5.28.0 /usr/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5Codecs.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigGui.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libQt5Xml.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libKF5Auth.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libQt5X11Extras.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libKF5ItemViews.so.5.28.0 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.7.1 

Processed: Re: Bug#853533: magics++ FTBFS with g++ 7.1 -- compiler bug, fixed in 7.2 branch

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 g++-7 7-20170126-1
Bug #853533 [src:magics++] magics++: ftbfs with GCC-7
Bug reassigned from package 'src:magics++' to 'g++-7'.
No longer marked as found in versions magics++/2.30.0-4.
Ignoring request to alter fixed versions of bug #853533 to the same values 
previously set
Bug #853533 [g++-7] magics++: ftbfs with GCC-7
There is no source info for the package 'g++-7' at version '7-20170126-1' with 
architecture ''
Unable to make a source version for version '7-20170126-1'
Marked as found in versions 7-20170126-1.
> affects -1 src:magics++
Bug #853533 [g++-7] magics++: ftbfs with GCC-7
Added indication that 853533 affects src:magics++
> fixed -1 7.1.0-10
Bug #853533 [g++-7] magics++: ftbfs with GCC-7
Marked as fixed in versions gcc-7/7.1.0-10.
> close -1
Bug #853533 [g++-7] magics++: ftbfs with GCC-7
Marked Bug as done

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

Bug#853533: magics++ FTBFS with g++ 7.1 -- compiler bug, fixed in 7.2 branch

[Adrian Bunk]

Control: reassign -1 g++-7 7-20170126-1
Control: affects -1 src:magics++
Control: fixed -1 7.1.0-10
Control: close -1


On Wed, Jul 12, 2017 at 02:59:05PM +0100, Alastair McKinstry wrote:
> Hi,
> 
> This FTBFS with g++-7 is a known bug in gcc 7.1 ;
> 
> see: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81204
> 
> Resolved in gcc-7 branch. Either a cherry-pick of the patch, or 7.2
> release of gcc needed.

Confirmed that it is fixed with the latest gcc-7:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/magics++.html

> Best regards
> 
> Alastair

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

Bug#869884: marked as done (chemical-mime-data: Local copy of intltool-* fails with perl 5.26)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 21:34:46 +
with message-id 
and subject line Bug#869884: fixed in chemical-mime-data 0.1.94-6.1
has caused the Debian Bug report #869884,
regarding chemical-mime-data: Local copy of intltool-* fails with perl 5.26
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.)


-- 
869884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chemical-mime-data
Version: 0.1.94-6
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/chemical-mime-data.html

...
Making check in po
make[2]: Entering directory '/build/1st/chemical-mime-data-0.1.94/po'
INTLTOOL_EXTRACT=../intltool-extract srcdir=. ../intltool-update 
--gettext-package chemical-mime-data --pot
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in 
m/^(.*)\${ <-- HERE ?([A-Z_]+)}?(.*)$/ at ../intltool-update line 875.
Makefile:95: recipe for target 'chemical-mime-data.pot' failed
make[2]: *** [chemical-mime-data.pot] Error 2
--- End Message ---
--- Begin Message ---
Source: chemical-mime-data
Source-Version: 0.1.94-6.1

We believe that the bug you reported is fixed in the latest version of
chemical-mime-data, 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 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated chemical-mime-data 
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: Mon, 31 Jul 2017 16:48:01 -0400
Source: chemical-mime-data
Binary: chemical-mime-data
Architecture: source
Version: 0.1.94-6.1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: gregor herrmann 
Closes: 869884
Description: 
 chemical-mime-data - chemical MIME and file type support for desktops
Changes:
 chemical-mime-data (0.1.94-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "Local copy of intltool-* fails with perl 5.26":
 Add patch 869884_perl-5.26.patch to fix errors caused by unescaped left
 braces in embedded intltool-update copy.
 (Closes: #869884)
Checksums-Sha1: 
 d83c485e9eff1a30228e7c5d99cd8fcef5616413 2345 chemical-mime-data_0.1.94-6.1.dsc
 4f1cf89ba485935cf664b01d9dbd197126cf1062 4596 
chemical-mime-data_0.1.94-6.1.debian.tar.xz
Checksums-Sha256: 
 3bd8f8bd9b55eadfe34c756067261173e5491ad81df97ee73a560b2f5b8f2969 2345 
chemical-mime-data_0.1.94-6.1.dsc
 72a93ccc58bbcc18d6ef049ddd6341ffd2560bd25e63404617ef76b0a249d23d 4596 
chemical-mime-data_0.1.94-6.1.debian.tar.xz
Files: 
 effb74dc83ce6e9a0fe6602e6ff65fda 2345 misc optional 
chemical-mime-data_0.1.94-6.1.dsc
 020156962c03cd8cb8afd6cd97e5 4596 misc optional 
chemical-mime-data_0.1.94-6.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAll/mIxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbjUQ/9H4L82aGTOm2M0FHp2dswDyW0y6171v5NGLsFmDVMOOHGtSNS3VFr4qAg
1MnWeTSRL94pvOZUZK+3z3dbCLypMGH/lwsupeszQgq/+DkxLg6zZ9BjYLLzaPjV
ZX+vfMhTGZA4uRJqom3e2iDvjN2/uW+dqTvRSJu6AqYm6vgvwz0O8LUlnVOhfOaZ
H3Wtf0YrxLKucicAgw9OjytNx4MVicDlJBvlruinyRHJ+5HM8SeShSGB0ZS+4eqT
w94ADvcNkuvVOD67z4VMK+Qr07PQqtA04SvtysEwtkcZXk8qDBPwTLBlFnven1G1
zuB1i6WQ3ivoQQVfq0rolTtv4I30a9xT17FNhiW1iDhLp41FMoYPxdKRl71SGimh
g3qKf3mp8cJ/bCFCdwMUpqSU12OEdLS8bOWgcaiRl5No0dvN1OMa9pKwoWjy6/80
/94wycc5OjsPoLEcT60B5Hf1U3gs+xtIBEpRkjboBvYmrfcu8/t2vNl38SWwWI45
jBEGd6Qa+KHjyrJvE1gUj/bC+eSkKxPle3JGudXw/Alh+VYrS2eyRjeDlVflwfmP
pG9OOMykErR/6GW6TzCeZUJmX8vrUYknlwqSjC+6cpwzMCBvrpyd95nYpOi/TQ1T
1YwQWkH0HmS7CB3Z1MaxvF4tH6BCOUACtX09blh+O6XrJNOFW0o=
=oxYf
-END PGP SIGNATURE End Message ---

Bug#870873: exiv2: FTBFS: some symbols or patterns disappeared in the symbols file

[Jakub Wilk]

Source: exiv2
Version: 0.26-1
Severity: serious
Justification: fails to build from source

exiv2 FTBFS on i386:
|dh_makeshlibs -a -O--parallel -O--buildsystem=cmake
| dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
| dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
| dpkg-gensymbols: warning: debian/libexiv2-26/DEBIAN/symbols doesn't match 
completely debian/libexiv2-26.symbols
| --- debian/libexiv2-26.symbols (libexiv2-26_0.26-1_i386)
| +++ dpkg-gensymbolsVBtVbw 2017-07-17 10:37:38.321705782 +
| @@ -135,8 +135,10 @@
|   _Z12xdefaultNameB5cxx11@Base 0.26
|   _Z13DetectAltTextP8XMP_Node@Base 0.26
|   
_Z13FindChildNodeP8XMP_NodePKcbPN9__gnu_cxx17__normal_iteratorIPS0_St6vectorIS0_SaIS0_@Base
 0.26
| - 
_Z13ToUTF16NativePKhmPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
0.26
| - 
_Z13ToUTF32NativePKhmPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
0.26
| + 
_Z13ToUTF16NativePKhjPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
0.26-1
| +#MISSING: 0.26-1# 
_Z13ToUTF16NativePKhmPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
0.26
| + 
_Z13ToUTF32NativePKhjPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
0.26-1
| +#MISSING: 0.26-1# 
_Z13ToUTF32NativePKhmPNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
0.26
[snip - lot's of other symbols missing]
| dh_makeshlibs: failing due to earlier errors
| debian/rules:6: recipe for target 'binary-arch' failed
| make: *** [binary-arch] Error 2

Full build log:
https://buildd.debian.org/status/fetch.php?pkg=exiv2=i386=0.26-1=1500287864

--
Jakub Wilk

Bug#853613: pinfo: ftbfs with GCC-7

[Adrian Bunk]

Control: reassign -1 gcc-7 7.1.0-12
Control: affects -1 src:pinfo
Control: retitle -1 gcc-7 with -Os: undefined references to inline functions

On Tue, Jan 31, 2017 at 09:35:06AM +, Matthias Klose wrote:
>...
> /bin/bash ../libtool --tag=CC --mode=link x86_64-linux-gnu-gcc  -Wall -g -Os  
>  -o pinfo  pinfo-pinfo.o pinfo-colors.o pinfo-datatypes.o 
> pinfo-filehandling_functions.o pinfo-mainfunction.o pinfo-manual.o 
> pinfo-menu_and_note_utils.o pinfo-parse_config.o pinfo-regexp_search.o 
> pinfo-signal_handler.o pinfo-utils.o pinfo-video.o pinfo-initializelinks.o 
> pinfo-printinfo.o-lreadline  -L/usr/lib -lncursesw  -L/usr/lib -lncursesw
> mkdir .libs
> x86_64-linux-gnu-gcc -Wall -g -Os -o pinfo pinfo-pinfo.o pinfo-colors.o 
> pinfo-datatypes.o pinfo-filehandling_functions.o pinfo-mainfunction.o 
> pinfo-manual.o pinfo-menu_and_note_utils.o pinfo-parse_config.o 
> pinfo-regexp_search.o pinfo-signal_handler.o pinfo-utils.o pinfo-video.o 
> pinfo-initializelinks.o pinfo-printinfo.o  -lreadline -L/usr/lib -lncursesw
> pinfo-filehandling_functions.o: In function `opendirfile':
> /<>/pinfo-0.6.9/src/filehandling_functions.c:620: undefined 
> reference to `builddircommand'
> /<>/pinfo-0.6.9/src/filehandling_functions.c:649: undefined 
> reference to `builddircommand'
> pinfo-filehandling_functions.o: In function `openinfo':
> /<>/pinfo-0.6.9/src/filehandling_functions.c:818: undefined 
> reference to `buildcommand'
> pinfo-initializelinks.o: In function `initializelinks':
> /<>/pinfo-0.6.9/src/initializelinks.c:466: undefined reference 
> to `exists_in_tag_table'
> /<>/pinfo-0.6.9/src/initializelinks.c:743: undefined reference 
> to `exists_in_tag_table'
> collect2: error: ld returned 1 exit status
> Makefile:356: recipe for target 'pinfo' failed
> make[3]: *** [pinfo] Error 1
>...

This looks like a gcc bug, testcase:

$ cat test4.c
int a;

inline void builddircommand(void)
{
a++;
}

int main()
{
builddircommand();
return 0;
}
$ gcc-6 -O2 -Wall test4.c
$ gcc-6 -Os -Wall test4.c
$ gcc -O2 -Wall test4.c
$ gcc -Os -Wall test4.c
/tmp/ccbei4dK.o: In function `main':
test4.c:(.text.startup+0x5): undefined reference to `builddircommand'
collect2: error: ld returned 1 exit status
$ 

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

Processed: Re: Bug#853613: pinfo: ftbfs with GCC-7

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 gcc-7 7.1.0-12
Bug #853613 [src:pinfo] pinfo: ftbfs with GCC-7
Bug reassigned from package 'src:pinfo' to 'gcc-7'.
No longer marked as found in versions pinfo/0.6.9-5.1.
Ignoring request to alter fixed versions of bug #853613 to the same values 
previously set
Bug #853613 [gcc-7] pinfo: ftbfs with GCC-7
Marked as found in versions gcc-7/7.1.0-12.
> affects -1 src:pinfo
Bug #853613 [gcc-7] pinfo: ftbfs with GCC-7
Added indication that 853613 affects src:pinfo
> retitle -1 gcc-7 with -Os: undefined references to inline functions
Bug #853613 [gcc-7] pinfo: ftbfs with GCC-7
Changed Bug title to 'gcc-7 with -Os: undefined references to inline functions' 
from 'pinfo: ftbfs with GCC-7'.

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

Processed: forwarded gcc issue

[Debian Bug Tracking System]

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

> forwarded 853613 https://gcc.gnu.org/PR81734
Bug #853613 [gcc-7] gcc-7 with -Os: undefined references to inline functions
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR81734'.
> tags 853613 + upstream
Bug #853613 [gcc-7] gcc-7 with -Os: undefined references to inline functions
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#869856: openssl: FTBFS: Testsuite failures

[Kurt Roeckx]

On Sat, Aug 05, 2017 at 09:03:41PM +0200, Sebastian Andrzej Siewior wrote:
> control: tags -1 patch fixed-upstream pending
> control: forwaded -1 https://github.com/openssl/openssl/issues/3562
> 
> On 2017-07-27 19:06:19 [-0700], Daniel Schepler wrote:
> > It appears so.  (Though I did have to apply it by hand as there was no
> > "clientsession" line for patch to sync to in hunk #2.)
> 
> okay. So we have fix a which will be part of 1.1.0g and I don't see a reason
> to upload it right away. So I suggest to wait until upstream releases
> something new.

I planned to break things by disabling TLS 1.0 and 1.1, which I
might upload soon. I guess I can fix that at the same time.


Kurt

Processed: Re: aptitude: ftbfs with GCC-7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #853316 [src:aptitude] aptitude: ftbfs with GCC-7
Added tag(s) pending.

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

Bug#853316: aptitude: ftbfs with GCC-7

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


Hi,

2017-01-31 10:29 Matthias Klose:

Package: src:aptitude
Version: 0.8.5-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7


Fix applied and pending to upload, thanks!

--
Manuel A. Fernandez Montecelo 

Bug#869357: marked as done (libdigest-whirlpool-perl FTBFS on s390x: test failure)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 21:19:13 +
with message-id 
and subject line Bug#869357: fixed in libdigest-whirlpool-perl 1.09-1.1
has caused the Debian Bug report #869357,
regarding libdigest-whirlpool-perl FTBFS on s390x: test 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.)


-- 
869357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdigest-whirlpool-perl
Version: 1.09-1
Severity: serious
Tags: buster sid

The perl 5.26 binNMU did FTBFS on s390x:

https://buildd.debian.org/status/fetch.php?pkg=libdigest-whirlpool-perl=s390x=1.09-1%2Bb8=1500689456=0

...
"/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/whirlpoolsum
Manifying 1 pod document
Manifying 1 pod document
make[1]: Leaving directory '/<>'
/usr/bin/make test
make[1]: Entering directory '/<>'
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- Whirlpool.bs 
blib/arch/auto/Digest/Whirlpool/Whirlpool.bs 644
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
"-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" 
t/*.t
t/00-use.t  ok
t/01-whirlpool.t .. ok
t/02-pod.t  skipped: Test::Pod 1.14 required
t/add.t ... ok
t/addfile.t ... 
All 1 subtests passed 
t/b64digest.t . ok
t/clone.t . ok
t/digest.t  ok
t/hashsize.t .. ok
t/hexdigest.t . ok
t/new.t ... ok
t/reset.t . ok
t/rt-50620.t .. ok

Test Summary Report
---
t/addfile.t (Wstat: 11 Tests: 1 Failed: 0)
  Non-zero wait status: 11
Files=13, Tests=40,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.35 cusr  0.04 
csys =  0.41 CPU)
Result: FAIL
Failed 1/13 test programs. 0/40 subtests failed.
Makefile:1044: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255
--- End Message ---
--- Begin Message ---
Source: libdigest-whirlpool-perl
Source-Version: 1.09-1.1

We believe that the bug you reported is fixed in the latest version of
libdigest-whirlpool-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 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libdigest-whirlpool-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: Mon, 31 Jul 2017 16:32:36 -0400
Source: libdigest-whirlpool-perl
Binary: libdigest-whirlpool-perl
Architecture: source
Version: 1.09-1.1
Distribution: unstable
Urgency: medium
Maintainer: James Bromberger 
Changed-By: gregor herrmann 
Closes: 869357
Description: 
 libdigest-whirlpool-perl - A 512-bit, collision-resistant, one-way hash 
function
Changes:
 libdigest-whirlpool-perl (1.09-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "libdigest-whirlpool-perl FTBFS on s390x: test failure":
 cherry-pick 66405ec from upstream git:
 
https://github.com/avar/digest-whirlpool/commit/66405ec9ca44492a38a82c2d7fa98c291d46eef1
 (Closes: #869357)
Checksums-Sha1: 
 88c9c1b74a7778a0a62b6b6adfb6045873a6eb99 1983 
libdigest-whirlpool-perl_1.09-1.1.dsc
 5b707f32ac55854e66f421fb8aecca33cd2af3bb 2549 
libdigest-whirlpool-perl_1.09-1.1.diff.gz
Checksums-Sha256: 
 8284923677ea328f7378a6f13f2375fd289cc77f6a04ed6bd63117f9ea0a0302 1983 
libdigest-whirlpool-perl_1.09-1.1.dsc
 f487d04c569ef8c38296adfddde2da55f1c4245a60707c0d60e0cc31b34067fe 2549 
libdigest-whirlpool-perl_1.09-1.1.diff.gz
Files: 
 13454411aeb4fede71ef0f7f0caf3aae 1983 perl optional 
libdigest-whirlpool-perl_1.09-1.1.dsc
 95fe8b517028415f69085fc758025139 2549 perl optional 
libdigest-whirlpool-perl_1.09-1.1.diff.gz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAll/lFZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZteA//RRU2DNn1vvZyXqToamSzo5h05yipKZICy5WzlVT+GJv9Ia3er8XLQ7f6
E4+cHwL/xvE+0aem0JyLXuqRiPsTmin92ZmWbO+8zgZoS74BkrbztovNGJbqKUQE

Bug#855118: marked as done (wrk: only loops and burns CPU)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 20:53:45 +
with message-id 
and subject line Bug#855118: fixed in wrk 4.0.2-2
has caused the Debian Bug report #855118,
regarding wrk: only loops and burns CPU
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.)


-- 
855118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wrk
Version: 4.0.2-1+b1
Severity: normal

This version of "wrk" is broken.
Running it eg. via 

# wrk  http://127.0.0.1:3309/static

just makes it loop and burn some CPU; it never terminates, and doesn't even 
do many HTTP requests.

Version 4.0.1-2 (from yakkety) works as expected.


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages wrk depends on:
ii  libc62.24-9
ii  libluajit-5.1-2  2.0.4+dfsg-1
ii  libssl1.11.1.0d-2

wrk recommends no packages.

wrk suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: wrk
Source-Version: 4.0.2-2

We believe that the bug you reported is fixed in the latest version of
wrk, 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 855...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Robert Edmonds  (supplier of updated wrk 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, 05 Aug 2017 16:04:19 -0400
Source: wrk
Binary: wrk
Architecture: source amd64
Version: 4.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Robert Edmonds 
Changed-By: Robert Edmonds 
Description:
 wrk- HTTP benchmarking tool
Closes: 801881 855118
Changes:
 wrk (4.0.2-2) unstable; urgency=medium
 .
   [ Christos Trochalakis ]
   * Modify previous mips FTBFS patch rendering wrk unusable in all
 architectures. Thanks to Rinat Ibragimov (Closes: #855118)
   * Fix build on mips architectures (Closes: #801881)
Checksums-Sha1:
 a1051bd5b6dea03ed3b9c6da95f0359cf567772e 1829 wrk_4.0.2-2.dsc
 09c8e3d8cee8318c73220cc8e1b8360a7457ae41 8018 wrk_4.0.2-2.debian.tar.gz
 c69f23b4a498319bd5bf4ecbbb745d14c0a35f09 67250 wrk-dbgsym_4.0.2-2_amd64.deb
 38fc768e4397558c7e483e8adc47a698f868778d 5652 wrk_4.0.2-2_amd64.buildinfo
 fd9c664ee40a81ba258bc9eefee57893b8b2f141 39084 wrk_4.0.2-2_amd64.deb
Checksums-Sha256:
 a9aba21b285643be2d5e423799832e367be285658630829854a8d9f8c74f1a4d 1829 
wrk_4.0.2-2.dsc
 bb26ca45df5bf09e9cffd9ced07a2487b55db6355e6360f408977c257016c25b 8018 
wrk_4.0.2-2.debian.tar.gz
 3ff77fc6f690ac2e6a74e9488b2a1dbd172a7b3451db0d090c9fbec53df0f07a 67250 
wrk-dbgsym_4.0.2-2_amd64.deb
 91a7d65a755b4a39c21debf2833b02fb1edc8e232c135565829a850a7fbf3dc5 5652 
wrk_4.0.2-2_amd64.buildinfo
 428795e95b6f18634dc244f538410d2d09d4dc87354be15800f2b84ca56f3c49 39084 
wrk_4.0.2-2_amd64.deb
Files:
 916f7b2875f048036879bf9dddaa718b 1829 web optional wrk_4.0.2-2.dsc
 7e9cbfebb5e0d7bf4d315661b2664615 8018 web optional wrk_4.0.2-2.debian.tar.gz
 fd9114a386f5f386de915df295054e98 67250 debug extra wrk-dbgsym_4.0.2-2_amd64.deb
 cf3b67d95e11da0a5bc815c4d5d4dab4 5652 web optional wrk_4.0.2-2_amd64.buildinfo
 9fe0752f63ca16459da3ced78994be99 39084 web optional wrk_4.0.2-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE3z2W7rOCeCDzAmZcAYF6sKr2za4FAlmGJnAACgkQAYF6sKr2
za6jBg//U7xaQ3Z/LL807pg7dAfh6wBNFFeKT+MlxceOs8WluDDY8nnvI7c7c4NS
q1hzg3A7U52i73anbmS+JIftIGXdrtix4pTduBol9Utahb+9Pv+azrzx0ezxCqex
xZj/Xir8C9znwbz6ymP3YzIN2Grq6QUXcIPDNNPYUhQofte4QVshQJDitvOtEfTB
CSPK72eK6hyPZF5tQyp4x0U0cPUupH6exa1fm1fTkTra/VpJJ1tKM1LG3rA6PHVL
nhq0iAQBAXl5UYkcfMHaLUhFWt/SvM69GLkiQxj85cpErTVgRh/CAemZimh4T8kV
NO7lQXaCD6b3CQT0P1nKmeJt1g+rpXz1AaYvfntIzcx5XGkg9CRc3oavJ+Cd9XJn
Cz4p7jz6+Z51djZgAcP+SoobzVHrzyNFxFdYysSNQ5NA7D+xjbmSZ6sRaBitSY4V

Bug#853427: marked as done (gnurobbo: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 20:51:56 +
with message-id 
and subject line Bug#853427: fixed in gnurobbo 0.68+dfsg-3
has caused the Debian Bug report #853427,
regarding gnurobbo: 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.)


-- 
853427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnurobbo
Version: 0.68+dfsg-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
SCHROOT_CHROOT_NAME=unstable-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=unstable-amd64-sbuild-9b4f3b89-b4f5-4730-bd2c-91667babae9c
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

dpkg-buildpackage: info: source package gnurobbo
dpkg-buildpackage: info: source version 0.68+dfsg-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Stephen Kitt 
 dpkg-source --before-build gnurobbo-0.68+dfsg
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_testdir
   dh_auto_clean
make -j1 clean
make[1]: Entering directory '/<>/gnurobbo-0.68+dfsg'
rm -f *.o gnurobbo
make[1]: Leaving directory '/<>/gnurobbo-0.68+dfsg'
   dh_clean
 dpkg-source -b gnurobbo-0.68+dfsg
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building gnurobbo using existing 
./gnurobbo_0.68+dfsg.orig.tar.bz2
dpkg-source: info: building gnurobbo in gnurobbo_0.68+dfsg-2.debian.tar.xz
dpkg-source: info: building gnurobbo in gnurobbo_0.68+dfsg-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 '/<>/gnurobbo-0.68+dfsg'
cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>/gnurobbo-0.68+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -d -Wall  `sdl-config --cflags` -DPLATFORM_PC 
-DVERSION=\"0.68\" -D_SMOOTH_SCRL_=\"yes\" -DLIGHTNINGENABLED=\"yes\" 
-DPACKAGE_DATA_DIR=\"/usr/share/games/gnurobbo\"   -DHAVE_DESIGNER -c 
ROB_engine.c -o ROB_engine.o
cc: error: missing argument to '-d'
Makefile:88: recipe for target 'ROB_engine.o' failed
make[1]: *** [ROB_engine.o] Error 1
make[1]: Leaving directory '/<>/gnurobbo-0.68+dfsg'
dh_auto_build: make -j1 returned exit code 2
debian/rules:10: 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: gnurobbo
Source-Version: 0.68+dfsg-3

We believe that the bug you reported is fixed in the latest version of
gnurobbo, 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,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated gnurobbo 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#869889: marked as done (bladerf FTBFS with cmake 3.9.0)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 20:49:42 +
with message-id 
and subject line Bug#869889: fixed in bladerf 0.2016.06-2
has caused the Debian Bug report #869889,
regarding bladerf FTBFS with cmake 3.9.0
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.)


-- 
869889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bladerf
Version: 0.2016.06-1
Severity: serious
Tags: buster sid

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

...
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
-- libbladeRF version: 1.7.2-0.2016.06-1
-- Found Doxygen: /usr/bin/doxygen (found version "1.8.13") found components:  
doxygen missing components:  dot
-- Configured to build libbladeRF API documentation.
-- nuand bladeRF udev rules will be installed to '/lib/udev/rules.d' upon 
running 'make install'
CMake Error at host/misc/udev/CMakeLists.txt:44 (else):
  A duplicate ELSE command was found inside an IF block.


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: bladerf
Source-Version: 0.2016.06-2

We believe that the bug you reported is fixed in the latest version of
bladerf, 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 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated bladerf 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, 05 Aug 2017 14:31:27 -0400
Source: bladerf
Binary: libbladerf1 libbladerf-dev bladerf bladerf-fpga-hostedx40 
bladerf-fpga-hostedx115 bladerf-firmware-fx3
Architecture: source amd64
Version: 0.2016.06-2
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Description:
 bladerf- nuand bladeRF software-defined radio device (tools)
 bladerf-firmware-fx3 - nuand bladeRF firmware downloader (FX3)
 bladerf-fpga-hostedx115 - nuand bladeRF FPGA bitstream downloader (hostedx115)
 bladerf-fpga-hostedx40 - nuand bladeRF FPGA bitstream downloader (hostedx40)
 libbladerf-dev - nuand bladeRF software-defined radio device (header files)
 libbladerf1 - nuand bladeRF software-defined radio device
Closes: 853332 869889
Changes:
 bladerf (0.2016.06-2) unstable; urgency=medium
 .
   * Upstream AGC CMake, and gcc7 patches (closes: #869889, #853332)
   * Added support for Automatic Gain Control
Checksums-Sha1:
 5480591f48f5769b4c735bb675e5c36bd9bd22e9 2424 bladerf_0.2016.06-2.dsc
 26fdaa88ec0ace6bdad129a228fe6a0dfcb998e2 134664 
bladerf_0.2016.06-2.debian.tar.xz
 33934e01327c5516f9dfdb0477b6f3ba90686ecf 242906 
bladerf-dbgsym_0.2016.06-2_amd64.deb
 6810906fe331c7457e5c16105df171e68c48e941 19554 
bladerf-firmware-fx3_0.2016.06-2_amd64.deb
 bb07a23655f4fa632268532a25de4c49638cd145 19626 
bladerf-fpga-hostedx115_0.2016.06-2_amd64.deb
 91e1d418834f26cdeda782b71a64a7431fadf47e 19626 
bladerf-fpga-hostedx40_0.2016.06-2_amd64.deb
 2725dbdd5b669fbf794f5dd31612c0ae41f1ee6e 9122 
bladerf_0.2016.06-2_amd64.buildinfo
 b7ff27b431f0bf0a64500a5c957839b6426ea914 118268 bladerf_0.2016.06-2_amd64.deb
 f0667809b71fbcfa68526d400856848b1d10504c 51082 
libbladerf-dev_0.2016.06-2_amd64.deb
 c4e853996bce8436b45abcbf0e752beeae367f8d 250590 
libbladerf1-dbgsym_0.2016.06-2_amd64.deb
 3d2325c4b4d5c199fe7a0f1e46305067a45d8207 95388 
libbladerf1_0.2016.06-2_amd64.deb
Checksums-Sha256:
 2055f45098c9fdb0d73bc533ee1344d8cc883ceec0c0cdd9bd38b08c1f0e7776 2424 
bladerf_0.2016.06-2.dsc
 726b6a478d43734b30f08764b003886a596f231db47ebe37ff00700a4afe054a 134664 
bladerf_0.2016.06-2.debian.tar.xz
 4796fe72dbed02bba902283d3e46c7d7c9428341a8d81b539837b295e442f647 242906 
bladerf-dbgsym_0.2016.06-2_amd64.deb
 

Bug#867899: marked as pending

[Neil Muller]

tag 867899 pending
thanks

Hello,

Bug #867899 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/python-modules/packages/sqlobject.git/commit/?id=28af124

---
commit 28af1242d64524d4e5057b8d4311ba41e1140d23
Author: Neil Muller 
Date:   Thu Aug 3 16:45:13 2017 +0200

Update for sqlobject 3.3.0

Drop obsolete patches.
Change to using sphinx to build docs.
Backport upstream patch needed to run tests with python 3.6.

diff --git a/debian/changelog b/debian/changelog
index 1dff06e..2286d12 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,19 @@
+sqlobject (3.3.0+dfsg-1) UNRELEASED; urgency=low
+
+  * Update to the latest upstream release.
+ - Adds support for python 3.6 (Closes: #867899)
+ - Documentation is now built using sphinx.
+ - Fix pytest warnings by renaming the helper classes.
+  * Drop obsolete fix_sqlite_vacuum_cmd patch.
+  * Backport patch to fix additional test failure with python 3.6.
+  * Update package to use sphinx to build the html documentation.
+  * Drop obsolete change_doc_build_script patch.
+  * Remove the dh_clean override from debian/rules, since it's no longer
+needed with the new documentation build system.
+  * Drop debian/clean for the same reason.
+
+ -- Neil Muller   Thu, 03 Aug 2017 16:39:32 +0200
+
 sqlobject (3.1.0+dfsg-2) unstable; urgency=low
 
   * Fix build failure with sqlite 3.15: new patch fix_sqlite_vacuum_cmd

Processed: Bug#867899 marked as pending

[Debian Bug Tracking System]

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

> tag 867899 pending
Bug #867899 [src:sqlobject] sqlobject FTBFS with python 3.6 as supported version
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#853332: marked as done (bladerf: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 20:49:42 +
with message-id 
and subject line Bug#853332: fixed in bladerf 0.2016.06-2
has caused the Debian Bug report #853332,
regarding bladerf: 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.)


-- 
853332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bladerf
Version: 0.2016.06-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/bladerf_0.2016.06-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 '/<>/obj-x86_64-linux-gnu'
make -f host/libraries/libbladeRF/CMakeFiles/libbladerf_shared.dir/build.make 
host/libraries/libbladeRF/CMakeFiles/libbladerf_shared.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  1%] Building C object 
host/libraries/libbladeRF/CMakeFiles/libbladerf_shared.dir/src/async.c.o
cd /<>/obj-x86_64-linux-gnu/host/libraries/libbladeRF && 
/usr/bin/cc  -DENABLE_USB_DEV_RESET_ON_OPEN=1 -DHAVE_LIBUSB_GET_VERSION 
-DLIBBLADERF_SEARCH_PREFIX=\"/usr\" -DLOGGING_ENABLED -DLOG_INCLUDE_FILE_INFO 
-Dlibbladerf_shared_EXPORTS 
-I/<>/host/libraries/libbladeRF/include 
-I/<>/host/libraries/libbladeRF/src 
-I/<>/host/common/include 
-I/<>/obj-x86_64-linux-gnu/host/common/include 
-I/<>/host/../firmware_common 
-I/<>/host/../fpga_common/include 
-I/<>/obj-x86_64-linux-gnu/host/libraries/libbladeRF/src 
-I/usr/include/libusb-1.0  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility=hidden -fPIC   -Wall -Wextra 
-Wno-unused-parameter -Werror -DSHORT_FILE_="async.c" -o 
CMakeFiles/libbladerf_shared.dir/src/async.c.o   -c 
/<>/host/libraries/libbladeRF/src/async.c
[  1%] Building C object 
host/libraries/libbladeRF/CMakeFiles/libbladerf_shared.dir/src/backend/backend.c.o
cd /<>/obj-x86_64-linux-gnu/host/libraries/libbladeRF && 
/usr/bin/cc  -DENABLE_USB_DEV_RESET_ON_OPEN=1 -DHAVE_LIBUSB_GET_VERSION 
-DLIBBLADERF_SEARCH_PREFIX=\"/usr\" -DLOGGING_ENABLED -DLOG_INCLUDE_FILE_INFO 
-Dlibbladerf_shared_EXPORTS 
-I/<>/host/libraries/libbladeRF/include 
-I/<>/host/libraries/libbladeRF/src 
-I/<>/host/common/include 
-I/<>/obj-x86_64-linux-gnu/host/common/include 
-I/<>/host/../firmware_common 
-I/<>/host/../fpga_common/include 
-I/<>/obj-x86_64-linux-gnu/host/libraries/libbladeRF/src 
-I/usr/include/libusb-1.0  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility=hidden -fPIC   -Wall -Wextra 
-Wno-unused-parameter -Werror -DSHORT_FILE_="backend.c" -o 
CMakeFiles/libbladerf_shared.dir/src/backend/backend.c.o   -c 
/<>/host/libraries/libbladeRF/src/backend/backend.c
[  2%] Building C object 
host/libraries/libbladeRF/CMakeFiles/libbladerf_shared.dir/src/bladerf.c.o
cd /<>/obj-x86_64-linux-gnu/host/libraries/libbladeRF && 
/usr/bin/cc  -DENABLE_USB_DEV_RESET_ON_OPEN=1 -DHAVE_LIBUSB_GET_VERSION 
-DLIBBLADERF_SEARCH_PREFIX=\"/usr\" -DLOGGING_ENABLED -DLOG_INCLUDE_FILE_INFO 
-Dlibbladerf_shared_EXPORTS 
-I/<>/host/libraries/libbladeRF/include 
-I/<>/host/libraries/libbladeRF/src 
-I/<>/host/common/include 
-I/<>/obj-x86_64-linux-gnu/host/common/include 
-I/<>/host/../firmware_common 
-I/<>/host/../fpga_common/include 
-I/<>/obj-x86_64-linux-gnu/host/libraries/libbladeRF/src 
-I/usr/include/libusb-1.0  -g -O2 

Bug#853553: marked as done (mkvtoolnix: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 16:30:58 -0400
with message-id 
and subject line Bug#853553: mkvtoolnix: ftbfs with GCC-7
has caused the Debian Bug report #853553,
regarding mkvtoolnix: 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.)


-- 
853553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mkvtoolnix
Version: 9.8.0-dmo1
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/mkvtoolnix_9.8.0-dmo1_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

[...]
 CXX src/extract/xtr_tta.cpp
 CXX src/extract/xtr_vobsub.cpp
 CXX src/extract/xtr_wav.cpp
 CXX src/extract/xtr_webvtt.cpp
 CXX src/propedit/segment_info_target.cpp
 CXX src/propedit/tag_target.cpp
 CXX src/propedit/target.cpp
 CXX src/propedit/track_target.cpp
  AR src/input/libmtxinput.a
  RANLIB src/input/libmtxinput.a
  AR src/propedit/libmtxpropedit.a
  RANLIB src/propedit/libmtxpropedit.a
  AR src/extract/libmtxextract.a
  RANLIB src/extract/libmtxextract.a
  AR src/common/libmtxcommon.a
  RANLIB src/common/libmtxcommon.a
LINK src/mkvmerge
LINK src/mkvextract
LINK src/mkvinfo
LINK src/tools/ebml_validator
LINK src/mkvtoolnix-gui/mkvtoolnix-gui
LINK src/mkvpropedit
src/propedit/libmtxpropedit.a(attachment_target.o): In function 
`attachment_target_c::matches_by_uid_name_or_mime_type(libmatroska::KaxAttached&)':
attachment_target.cpp:(.text+0x2d6b): undefined reference to 
`libebml::EbmlString::operator std::__cxx11::basic_string const&() const'
src/common/libmtxcommon.a(ebml_chapters_converter.o): In function 
`mtx::xml::ebml_chapters_converter_c::fix_display(libmatroska::KaxChapterDisplay&)
 const':
ebml_chapters_converter.cpp:(.text+0x3f75): undefined reference to 
`libebml::EbmlString::operator std::__cxx11::basic_string const&() const'
ebml_chapters_converter.cpp:(.text+0x417b): undefined reference to 
`libebml::EbmlString::operator std::__cxx11::basic_string const&() const'
collect2: error: ld returned 1 exit status
src/extract/libmtxextract.a(xtr_textsubs.o): In function 
`xtr_usf_c::create_file(xtr_base_c*, libmatroska::KaxTrackEntry&)':
xtr_textsubs.cpp:(.text+0x1169): undefined reference to 
`libebml::EbmlString::operator std::__cxx11::basic_string const&() const'
src/common/libmtxcommon.a(ebml_chapters_converter.o): In function 
`mtx::xml::ebml_chapters_converter_c::fix_display(libmatroska::KaxChapterDisplay&)
 const':
ebml_chapters_converter.cpp:(.text+0x3f75): undefined reference to 
`libebml::EbmlString::operator std::__cxx11::basic_string const&() const'
ebml_chapters_converter.cpp:(.text+0x417b): undefined reference to 
`libebml::EbmlString::operator std::__cxx11::basic_string const&() const'
collect2: error: ld returned 1 exit status
src/info/mkvinfo.o: In function `handle_ebml_head(libebml::EbmlElement*, 
std::shared_ptr, libebml::EbmlStream*)':
mkvinfo.cpp:(.text+0xf1f1): undefined reference to 
`libebml::EbmlString::operator std::__cxx11::basic_string

Bug#853604: marked as done (pbsim: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 23:15:12 +0300
with message-id <20170805201512.26a2zxhyxlyv776w@localhost>
and subject line Fixed in 1.0.3-3
has caused the Debian Bug report #853604,
regarding pbsim: 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.)


-- 
853604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pbsim
Version: 1.0.3-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/pbsim_1.0.3-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

[...]
 fprintf(fp_maf, " %d %s\n", ref.len, mut.maf_ref_seq);
 ~~~ ^
pbsim.cpp:1527:50: warning: format '%d' expects argument of type 'int', but 
argument 3 has type 'long int' [-Wformat=]
 fprintf(fp_maf, " %d %c", len, mut.seq_strand);
  ^
pbsim.cpp:1531:51: warning: format '%d' expects argument of type 'int', but 
argument 3 has type 'long int' [-Wformat=]
 fprintf(fp_maf, " %d %s\n\n", len, mut.maf_seq);
   ^
pbsim.cpp: In function 'void print_sim_param()':
pbsim.cpp:1608:48: warning: format '%d' expects argument of type 'int', but 
argument 3 has type 'long int' [-Wformat=]
 sim.sub_ratio, sim.ins_ratio, sim.del_ratio);
 ~  ^
pbsim.cpp:1608:48: warning: format '%d' expects argument of type 'int', but 
argument 4 has type 'long int' [-Wformat=]
pbsim.cpp:1608:48: warning: format '%d' expects argument of type 'int', but 
argument 5 has type 'long int' [-Wformat=]
pbsim.cpp: In function 'int set_mut()':
pbsim.cpp:1618:18: warning: ISO C++ forbids converting a string constant to 
'char*' [-Wwrite-strings]
   mut.sub_nt_a = "TGC";
  ^
pbsim.cpp:1619:18: warning: ISO C++ forbids converting a string constant to 
'char*' [-Wwrite-strings]
   mut.sub_nt_t = "AGC";
  ^
pbsim.cpp:1620:18: warning: ISO C++ forbids converting a string constant to 
'char*' [-Wwrite-strings]
   mut.sub_nt_g = "ATC";
  ^
pbsim.cpp:1621:18: warning: ISO C++ forbids converting a string constant to 
'char*' [-Wwrite-strings]
   mut.sub_nt_c = "ATG";
  ^
pbsim.cpp:1622:18: warning: ISO C++ forbids converting a string constant to 
'char*' [-Wwrite-strings]
   mut.sub_nt_n = "ATGC";
  ^~
pbsim.cpp:1623:16: warning: ISO C++ forbids converting a string constant to 
'char*' [-Wwrite-strings]
   mut.ins_nt = "ATGC";
^~
pbsim.cpp: In function 'void print_simulation_stats()':
pbsim.cpp:1816:69: warning: format '%d' expects argument of type 'int', but 
argument 3 has type 'long int' [-Wformat=]
   fprintf(stderr, " Simulation stats (ref.%d) \n\n", ref.num);
  ~~~^
Makefile:224: recipe for target 'pbsim.o' failed
make[3]: *** [pbsim.o] Error 1
make[3]: Leaving directory '/<>/src'
Makefile:222: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:161: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End 

Bug#870672: cdimage.debian.org: Cannot install packages from update DVD for Stretch 9.1.0

[Nicholas Dreyer]

On Sat, 5 Aug 2017 20:57:04 +0100 Steve McIntyre <st...@einval.com>
wrote:
> [ Hint: Please CC 870...@bugs.debian.org so that other people can see
>   responses in tbe BTS too... ]

Sorry, I failed to because I somehow erroneously thought you had
replied to me privately.  Am attaching (again) the logs I sent to you
before, hoping they will be visible to all.  Will see soon enough . . .Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/1,263 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 cdrom://[Debian GNU/Linux 9.1.1 Update DVD 20170805: i386 DVD 1] stretch/main i386 apt i386 1.4.7 [1,263 kB]
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 145357 files and directories currently installed.)
Preparing to unpack .../main/a/apt/apt_1.4.7_i386.deb ...
Unpacking apt (1.4.7) over (1.4.7) ...
Setting up apt (1.4.7) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Ign:1 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-1 20170617-14:24] stretch InRelease
Ign:2 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch InRelease
Ign:3 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-3 20170617-14:24] stretch InRelease
Ign:4 cdrom://[Debian GNU/Linux 9.1.1 Update DVD 20170805: i386 DVD 1] stretch InRelease
Ign:5 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-1 20170617-14:24] stretch Release
Ign:6 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch Release
Ign:7 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-3 20170617-14:24] stretch Release
Ign:8 cdrom://[Debian GNU/Linux 9.1.1 Update DVD 20170805: i386 DVD 1] stretch Release
Hit:9 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-1 20170617-14:24] stretch/main i386 Packages
Ign:10 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-1 20170617-14:24] stretch/main all Packages
Ign:11 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-1 20170617-14:24] stretch/main Translation-en_US
Hit:12 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-1 20170617-14:24] stretch/main Translation-en
Hit:13 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/contrib i386 Packages
Ign:14 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/contrib all Packages
Ign:15 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/contrib Translation-en_US
Hit:16 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/contrib Translation-en
Ign:9 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-1 20170617-14:24] stretch/main i386 Packages
Hit:17 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/main i386 Packages
Ign:12 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-1 20170617-14:24] stretch/main Translation-en
Ign:18 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/main all Packages
Ign:13 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/contrib i386 Packages
Ign:19 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/main Translation-en_US
Ign:16 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/contrib Translation-en
Hit:20 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/main Translation-en
Ign:17 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/main i386 Packages
Ign:21 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-3 20170617-14:24] stretch/contrib all Packages
Ign:20 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-2 20170617-14:24] stretch/main Translation-en
Hit:22 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-3 20170617-14:24] stretch/contrib i386 Packages
Ign:22 cdrom://[Debian GNU/Linux 9.0.0 _Stretch_ - Official i386 DVD Binary-3 20

Bug#853704: marked as done (w1retap: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 23:19:01 +0300
with message-id <20170805201901.4xvg2choqiwocrj2@localhost>
and subject line w1retap builds with gcc 7
has caused the Debian Bug report #853704,
regarding w1retap: 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.)


-- 
853704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:w1retap
Version: 1.4.4-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
make[5]: Leaving directory '/<>/src/pgsql'
Making all in odbc
make[5]: Entering directory '/<>/src/odbc'
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -Wall -D_GNU_SOURCE=1 -I  ../libusblinux300/ -I../ -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wno-unused-result  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -c -o w1odbc.lo w1odbc.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -D_GNU_SOURCE=1 -I 
../libusblinux300/ -I../ -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 
-Werror -Wno-unused-result -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c w1odbc.c  
-fPIC -DPIC -o .libs/w1odbc.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -D_GNU_SOURCE=1 -I 
../libusblinux300/ -I../ -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 
-Werror -Wno-unused-result -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c w1odbc.c -o 
w1odbc.o >/dev/null 2>&1
/bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-Wl,--disable-new-dtags -o libw1odbc.la -rpath 
/usr/lib/x86_64-linux-gnu/w1retap w1odbc.lo -lodbc -lxml2 -lrt -lm 
libtool: link: gcc -shared  -fPIC -DPIC  .libs/w1odbc.o   -lodbc -lxml2 -lrt 
-lm  -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now 
-Wl,--as-needed -Wl,--disable-new-dtags   -Wl,-soname -Wl,libw1odbc.so.0 -o 
.libs/libw1odbc.so.0.0.0
libtool: link: (cd ".libs" && rm -f "libw1odbc.so.0" && ln -s 
"libw1odbc.so.0.0.0" "libw1odbc.so.0")
libtool: link: (cd ".libs" && rm -f "libw1odbc.so" && ln -s 
"libw1odbc.so.0.0.0" "libw1odbc.so")
libtool: link: ar cru .libs/libw1odbc.a  w1odbc.o
ar: `u' modifier ignored since `D' is the default (see `U')
libtool: link: ranlib .libs/libw1odbc.a
libtool: link: ( cd ".libs" && rm -f "libw1odbc.la" && ln -s "../libw1odbc.la" 
"libw1odbc.la" )
make[5]: Leaving directory '/<>/src/odbc'
Making all in mongo
make[5]: Entering directory '/<>/src/mongo'
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -Wall -D_GNU_SOURCE=1 -I  ../libusblinux300/ -I../ -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/mongo-client -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 
-Werror -Wno-unused-result  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o 
w1mongo.lo w1mongo.c
libtool: 

Bug#853580: marked as done (nvme-cli: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 23:13:04 +0300
with message-id <20170805201304.pxziqhjk2hryg2ll@localhost>
and subject line nvme-cli builds with gcc 7
has caused the Debian Bug report #853580,
regarding nvme-cli: 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.)


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

[...]
   dh_update_autotools_config
   dh_auto_configure
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
NVME_VERSION = 1.0
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu99 -O2 -g -Wall -Werror -DLIBUDEV_EXISTS 
-DNVME_VERSION='"1.0"' -c argconfig.c
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu99 -O2 -g -Wall -Werror -DLIBUDEV_EXISTS 
-DNVME_VERSION='"1.0"' -c suffix.c
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu99 -O2 -g -Wall -Werror -DLIBUDEV_EXISTS 
-DNVME_VERSION='"1.0"' -c parser.c
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu99 -O2 -g -Wall -Werror -DLIBUDEV_EXISTS 
-DNVME_VERSION='"1.0"' -c nvme-print.c
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu99 -O2 -g -Wall -Werror -DLIBUDEV_EXISTS 
-DNVME_VERSION='"1.0"' -c nvme-ioctl.c
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu99 -O2 -g -Wall -Werror -DLIBUDEV_EXISTS 
-DNVME_VERSION='"1.0"' -c nvme-lightnvm.c
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu99 -O2 -g -Wall -Werror -DLIBUDEV_EXISTS 
-DNVME_VERSION='"1.0"' -c fabrics.c
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu99 -O2 -g -Wall -Werror -DLIBUDEV_EXISTS 
-DNVME_VERSION='"1.0"' -c json.c
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu99 -O2 -g -Wall -Werror -DLIBUDEV_EXISTS 
-DNVME_VERSION='"1.0"' -c plugin.c
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu99 -O2 -g -Wall -Werror -DLIBUDEV_EXISTS 
-DNVME_VERSION='"1.0"' -c intel-nvme.c
cc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__CHECK_ENDIAN__ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu99 -O2 -g -Wall -Werror -DLIBUDEV_EXISTS 
-DNVME_VERSION='"1.0"' -c lnvm-nvme.c
cc -Wdate-time 

Bug#853413: marked as done (gazebo: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 23:11:36 +0300
with message-id <20170805201136.2uds4ysttj4imndc@localhost>
and subject line gazebo builds with gcc 7
has caused the Debian Bug report #853413,
regarding gazebo: ftbfs with GCC-7
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

Bug#855118: wrk: only loops and burns CPU

[Robert Edmonds]

Christos Trochalakis wrote:
> I plan to upload it as an nmu on Monday unless Robert wants to prepare
> the upload himself. I have just pushed those fixes to the packaging repo
> (nmu branch).
> 
> https://anonscm.debian.org/cgit/collab-maint/wrk.git/log/?h=nmu

Thanks, just uploaded these changes as 4.0.2-2.

-- 
Robert Edmonds
edmo...@debian.org

Bug#870861: polari FTBFS: test failure

[Adrian Bunk]

Source: polari
Version: 3.22.2-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes polari FTBFS:

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

...
   dh_auto_test
make -j16 check VERBOSE=1
make[1]: Entering directory '/build/1st/polari-3.22.2'
Making check in src
make[2]: Entering directory '/build/1st/polari-3.22.2/src'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/build/1st/polari-3.22.2/src'
Making check in data
make[2]: Entering directory '/build/1st/polari-3.22.2/data'
Making check in appdata
make[3]: Entering directory '/build/1st/polari-3.22.2/data/appdata'
/usr/bin/msgfmt --xml --template org.gnome.Polari.appdata.xml.in -d ../../po -o 
org.gnome.Polari.appdata.xml
if test -f "org.gnome.Polari.appdata.xml"; then d=; else d="./"; fi; \
if test -n "/usr/bin/appstream-util"; \
then /usr/bin/appstream-util --nonet validate 
${d}org.gnome.Polari.appdata.xml; fi \
&& touch org.gnome.Polari.appdata.valid
org.gnome.Polari.appdata.xml: 
(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.

(appstream-util:23509): dconf-CRITICAL **: unable to create directory 
'/nonexistent/first-build/.cache/dconf': Permission denied.  dconf will not 
work properly.
FAILED:
? attribute-invalid :  is invalid [HighContast]
Validation of files failed
Makefile:513: recipe for target 'org.gnome.Polari.appdata.valid' failed
make[3]: *** [org.gnome.Polari.appdata.valid] Error 1
make[3]: Leaving directory '/build/1st/polari-3.22.2/data/appdata'
Makefile:563: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/build/1st/polari-3.22.2/data'
Makefile:463: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/build/1st/polari-3.22.2'
dh_auto_test: make -j16 check VERBOSE=1 returned exit code 2
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2

Bug#853364: marked as done (cython: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 23:09:16 +0300
with message-id <20170805200916.hwkwi6ukk333d2m3@localhost>
and subject line cython builds with gcc 7
has caused the Debian Bug report #853364,
regarding cython: 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.)


-- 
853364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cython
Version: 0.25.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/cython_0.25.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

[...]
ALL DONE (19/64)
ALL DONE (50/64)
ALL DONE (61/64)
ALL DONE (62/64)
ALL DONE (9/64)
ALL DONE (43/64)
ALL DONE (35/64)
ALL DONE (3/64)
ALL DONE (54/64)
ALL DONE (33/64)
ALL DONE (21/64)
ALL DONE (5/64)
FAILED (8/64)
ALL DONE (8/64)
ALL DONE (39/64)
ALL DONE (40/64)
ALL DONE (13/64)
ALL DONE (36/64)
ALL DONE (20/64)
ALL DONE (38/64)
ALL DONE (60/64)
ALL DONE (44/64)
ALL DONE (0/64)
ALL DONE (12/64)
ALL DONE (16/64)
ALL DONE (55/64)
ALL DONE (45/64)
ALL DONE (14/64)
ALL DONE (1/64)
ALL DONE (15/64)
ALL DONE (41/64)
ALL DONE (63/64)
FAILED (23/64)
ALL DONE (23/64)
ALL DONE (26/64)
ALL DONE (17/64)
ALL DONE (10/64)
ALL DONE (29/64)
ALL DONE (47/64)
ALL DONE (52/64)
ALL DONE (49/64)
ALL DONE (56/64)
Errors for shards 58, 8, 23
ALL DONE
debian/rules:112: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:25: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
cython builds with gcc 7:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cython.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#853711: marked as done (xlog: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 23:02:55 +0300
with message-id <20170805200255.u4cwsm33zbl2e6tc@localhost>
and subject line xlog builds with gcc 7
has caused the Debian Bug report #853711,
regarding xlog: 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.)


-- 
853711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xlog
Version: 2.0.14-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/xlog_2.0.14-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

[...]
xlog_enum.c:165:26: note: using the range [1, -2147483648] for directive 
argument
snprintf(temp_mhz, 6, "%d", (int)freq1);
  ^~~~
In file included from /usr/include/stdio.h:938:0,
 from /usr/include/pango-1.0/pango/pango-utils.h:25,
 from /usr/include/pango-1.0/pango/pango.h:46,
 from /usr/include/gtk-2.0/gdk/gdktypes.h:37,
 from /usr/include/gtk-2.0/gdk/gdkscreen.h:32,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from xlog_enum.c:28:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: format output between 
2 and 12 bytes into a destination of size 6
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  ^~~~
__bos (__s), __fmt, __va_arg_pack ());
~
xlog_enum.c:169:27: error: '%d' directive output may be truncated writing 
between 1 and 11 bytes into a region of size 6 [-Werror=format-truncation=]
snprintf(temp_mhz, 6, "%d", (int)freq1);
   ^~
xlog_enum.c:169:26: note: using the range [1, -2147483648] for directive 
argument
snprintf(temp_mhz, 6, "%d", (int)freq1);
  ^~~~
In file included from /usr/include/stdio.h:938:0,
 from /usr/include/pango-1.0/pango/pango-utils.h:25,
 from /usr/include/pango-1.0/pango/pango.h:46,
 from /usr/include/gtk-2.0/gdk/gdktypes.h:37,
 from /usr/include/gtk-2.0/gdk/gdkscreen.h:32,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from xlog_enum.c:28:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: format output between 
2 and 12 bytes into a destination of size 6
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  ^~~~
__bos (__s), __fmt, __va_arg_pack ());
~
cc1: all warnings being treated as errors
Makefile:569: recipe for target 'xlog_enum.o' failed
make[3]: *** [xlog_enum.o] Error 1
make[3]: Leaving directory '/<>/src'
Makefile:589: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>/src'
Makefile:370: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/<>'
debian/rules:49: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit 

Bug#853676: marked as done (systemtap: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 22:56:31 +0300
with message-id <20170805195631.jyufrocbr5ysxr23@localhost>
and subject line Fixed in 3.1
has caused the Debian Bug report #853676,
regarding systemtap: 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.)


-- 
853676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:systemtap
Version: 3.0-7
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/systemtap_3.0-7_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

[...]
   ^
dwflpp.cxx:3732:5: note: here
 case DW_TAG_enumeration_type:
 ^~~~
translate.cxx: In member function 'void c_unparser::emit_compiled_printfs()':
translate.cxx:1305:5: error: this statement may fall through 
[-Werror=implicit-fallthrough=]
 if (strverscmp(session->compatible.c_str(), "1.3") < 0)
 ^~
translate.cxx:1318:3: note: here
   case print_format::conv_number:
   ^~~~
translate.cxx:1410:8: error: this statement may fall through 
[-Werror=implicit-fallthrough=]
if (strverscmp(session->compatible.c_str(), "1.3") < 0)
^~
translate.cxx:1423:6: note: here
  case print_format::conv_number:
  ^~~~
tapsets.cxx: In function 'void validate_module_elf(Dwfl_Module*, const char*, 
base_query*)':
tapsets.cxx:2466:7: error: this statement may fall through 
[-Werror=implicit-fallthrough=]
   if (! q->has_process) break; // 32-bit kernel/module
   ^~
tapsets.cxx:2468:5: note: here
 case EM_X86_64:
 ^~~~
cc1plus: all warnings being treated as errors
Makefile:1156: recipe for target 'stap-staptree.o' failed
make[4]: *** [stap-staptree.o] Error 1
cc1plus: all warnings being treated as errors
Makefile:1422: recipe for target 'stap-dwflpp.o' failed
make[4]: *** [stap-dwflpp.o] Error 1
cc1plus: all warnings being treated as errors
Makefile:1184: recipe for target 'stap-translate.o' failed
make[4]: *** [stap-translate.o] Error 1
cc1plus: all warnings being treated as errors
Makefile:1198: recipe for target 'stap-tapsets.o' failed
make[4]: *** [stap-tapsets.o] Error 1
make[4]: Leaving directory '/<>'
Makefile:1907: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>'
Makefile:684: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>'
dh_auto_build: make -j64 returned exit code 2
debian/rules:38: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:28: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 3.1-1

This bug has been fixed upstream in version 3.1:
https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commit;h=575fe913f6b6b81421f7bfda7c72ab8c15ecb8e3

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#870860: openjfx: CVE-2017-10086 CVE-2017-10114

[Salvatore Bonaccorso]

Source: openjfx
Version: 8u131-b11-1
Severity: grave
Tags: upstream security

Hi,

the following vulnerabilities were published for openjfx.

CVE-2017-10086[0] and CVE-2017-10114[1].

Unfortunately it's no more details possilby know as shared via [2],
which states that the supported versions vulnerable are 7u141 and
8u131. The severity is probably as well overrated for this bugreport
and a DSA not deserved. But bug should help tracking the fix for
future unstable upload.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-10086
[1] https://security-tracker.debian.org/tracker/CVE-2017-10114
[2] 
http://www.oracle.com/technetwork/security-advisory/cpujul2017verbose-3236625.html#JAVA

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#870672: cdimage.debian.org: Cannot install packages from update DVD for Stretch 9.1.0

[Steve McIntyre]

[ Hint: Please CC 870...@bugs.debian.org so that other people can see
  responses in tbe BTS too... ]

On Sat, Aug 05, 2017 at 12:47:01PM -0700, Nicholas Dreyer wrote:
>Hi Steve:
>
>Your fix looks good for the i386 test I just did, the details of which
>are attached.

Cool, thanks for verifying!

>I do not understand the (apparently bogus) warnings about non-existent
>Release files, but they do not seem represent any real trouble.

ACK. AFAICS that's most likely due to the DVDs not including
signatures. That's a separate issue and a much harder change...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Google-bait:   http://www.debian.org/CD/free-linux-cd
  Debian does NOT ship free CDs. Please do NOT contact the mailing
  lists asking us to send them to you.

Bug#853660: marked as done (simbody: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 22:58:09 +0300
with message-id <20170805195809.62lpak2lrsn3vvo5@localhost>
and subject line simbody builds with gcc 7
has caused the Debian Bug report #853660,
regarding simbody: ftbfs with GCC-7
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
853660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:simbody
Version: 3.5.4+dfsg-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

Bug#869774: marked as done (thunderbird 52 needs enigmail 1.9.8.1 or later)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 19:50:03 +
with message-id 
and subject line Bug#869774: fixed in enigmail 2:1.9.8.1-1~deb8u1
has caused the Debian Bug report #869774,
regarding thunderbird 52 needs enigmail 1.9.8.1 or later
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.)


-- 
869774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: enigmail
Version: 2:1.8.2-4~deb8u1
Severity: critical
Justification: breaks unrelated software

Detailed description:
* When clicking on encrypted mails, thunderbird says "This is an encrypted 
OpenPGP message. In order to decrypt this mail, you need to install an OpenPGP 
add-on" although enigmail is installed and shows up in the menu and in addons
* Similiarly, the enigmail encryption symbol is shown (greyd-out) but no longer 
works when writing mails
* Enigmail settings can no longer be accessed via the menu only via addons 
(clicking on menu and hovering over enigmail no longer shows a submenu, 
clicking on enigmail -> preferences in the menu bar 
* Clicking on Enigmail buttons is no longer processed (yields no results)
* In Preferences -> Basic settings, the message beneath "Files and
Directories" is "(error)". Since clicking on enigmail buttons is no longer 
processed, it is impossible to activate "Override with" to /usr/bin/gpg2 ("Ok" 
button does not work, "Browse" button does not work, "Display Expert Settings 
and Menus" does not work)

Further info:
* gpg and gpg2 exist (both in /usr/bin/) and both work flawlessly on the 
command line
* all current upgrades have been installed
* I have been informed that the same error also occurs on at least one other
system of a colleague with a debian standard install

-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages enigmail depends on:
ii  gnupg  1.4.18-7+deb8u3
ii  gnupg2 2.0.26-6+deb8u1
ii  icedove1:52.2.1-4~deb8u1
ii  libc6  2.19-18+deb8u10
ii  thunderbird [icedove]  1:52.2.1-4~deb8u1

Versions of packages enigmail recommends:
ii  gnupg-agent   2.0.26-6+deb8u1
ii  gnupg22.0.26-6+deb8u1
ii  pinentry-gtk2 [pinentry-x11]  0.8.3-2

enigmail suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: enigmail
Source-Version: 2:1.9.8.1-1~deb8u1

We believe that the bug you reported is fixed in the latest version of
enigmail, 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 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated enigmail 
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: Thu, 27 Jul 2017 10:17:26 -0400
Source: enigmail
Binary: enigmail
Architecture: source all
Version: 2:1.9.8.1-1~deb8u1
Distribution: jessie-security
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Daniel Kahn Gillmor 
Description:
 enigmail   - GPG support for Thunderbird and Debian Icedove
Closes: 794627 842212 863273 869774
Changes:
 enigmail (2:1.9.8.1-1~deb8u1) jessie-security; urgency=medium
 .
   * Rebuild for jessie-security (Closes: #869774)
 .
 enigmail (2:1.9.8.1-1) unstable; urgency=medium
 .
   * new upstream release
 .
 enigmail (2:1.9.8-1) unstable; urgency=medium
 .
   * New upstream release.
   * Standards-Version to 4.0.0 (no changes needed)
   * use dpkg/pkg-info.mk instead of dpkg-parsechangelog
   * use wrap-and-sort -ast
 .
 enigmail (2:1.9.7-2) unstable; urgency=medium
 .
   * enable re-certifying keys with expired certs (Closes: #863273)
 .
 enigmail (2:1.9.7-1) unstable; urgency=medium
 .
 

Bug#869880: marked as done (CVE-2017-2834 CVE-2017-2835 CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 CVE-2017-2839)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 19:48:01 +
with message-id 
and subject line Bug#869880: fixed in freerdp 
1.1.0~git20140921.1.440916e+dfsg1-13+deb9u1
has caused the Debian Bug report #869880,
regarding CVE-2017-2834 CVE-2017-2835 CVE-2017-2836 CVE-2017-2837 CVE-2017-2838 
CVE-2017-2839
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.)


-- 
869880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freerdp
Severity: grave
Tags: security

Hi,
please see:
https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0341
https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0340
https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0339
https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0338
https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0337
https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0336

Fix is here:
https://github.com/FreeRDP/FreeRDP/pull/4055/commits/8292b4558f0684065ce1f58db7783cc426099223

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: freerdp
Source-Version: 1.1.0~git20140921.1.440916e+dfsg1-13+deb9u1

We believe that the bug you reported is fixed in the latest version of
freerdp, 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 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated freerdp 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: Thu, 27 Jul 2017 23:53:25 +0200
Source: freerdp
Binary: freerdp-x11 libfreerdp-cache1.1 libfreerdp-client1.1 
libfreerdp-codec1.1 libfreerdp-common1.1.0 libfreerdp-core1.1 
libfreerdp-crypto1.1 libfreerdp-gdi1.1 libfreerdp-locale1.1 
libfreerdp-primitives1.1 libfreerdp-rail1.1 libfreerdp-utils1.1 
libwinpr-asn1-0.1 libwinpr-bcrypt0.1 libwinpr-credentials0.1 libwinpr-credui0.1 
libwinpr-crt0.1 libwinpr-crypto0.1 libwinpr-dsparse0.1 libwinpr-environment0.1 
libwinpr-error0.1 libwinpr-file0.1 libwinpr-handle0.1 libwinpr-heap0.1 
libwinpr-input0.1 libwinpr-interlocked0.1 libwinpr-io0.1 libwinpr-library0.1 
libwinpr-path0.1 libwinpr-pipe0.1 libwinpr-pool0.1 libwinpr-registry0.1 
libwinpr-rpc0.1 libwinpr-sspi0.1 libwinpr-sspicli0.1 libwinpr-synch0.1 
libwinpr-sysinfo0.1 libwinpr-thread0.1 libwinpr-timezone0.1 libwinpr-utils0.1 
libwinpr-winhttp0.1 libwinpr-winsock0.1 libxfreerdp-client1.1 
libfreerdp-plugins-standard libfreerdp-dev libwinpr-dev freerdp-x11-dbg 
libxfreerdp-client-dbg libfreerdp-dbg libwinpr-dbg
 libfreerdp-plugins-standard-dbg
Architecture: source
Version: 1.1.0~git20140921.1.440916e+dfsg1-13+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Description:
 freerdp-x11 - RDP client for Windows Terminal Services (X11 client)
 freerdp-x11-dbg - RDP client for Windows Terminal Services (X11 client, debug 
symbo
 libfreerdp-cache1.1 - Free Remote Desktop Protocol library (cache library)
 libfreerdp-client1.1 - Free Remote Desktop Protocol library (client library)
 libfreerdp-codec1.1 - Free Remote Desktop Protocol library (codec library)
 libfreerdp-common1.1.0 - Free Remote Desktop Protocol library (common library)
 libfreerdp-core1.1 - Free Remote Desktop Protocol library (core library)
 libfreerdp-crypto1.1 - Free Remote Desktop Protocol library (freerdp-crypto 
library)
 libfreerdp-dbg - Free Remote Desktop Protocol library (debug symbols)
 libfreerdp-dev - Free Remote Desktop Protocol library (development files)
 libfreerdp-gdi1.1 - Free Remote Desktop Protocol library (GDI library)
 libfreerdp-locale1.1 - Free Remote Desktop Protocol library (locale library)
 libfreerdp-plugins-standard - RDP client for Windows Terminal Services 
(plugins)
 libfreerdp-plugins-standard-dbg - RDP client for Windows Terminal Services 
(plugins debug)
 libfreerdp-primitives1.1 - Free Remote Desktop Protocol library (primitives 
library)
 libfreerdp-rail1.1 - Free 

Bug#868788: marked as done (Security fixes from the July 2017 CPU)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 19:50:03 +
with message-id 
and subject line Bug#868788: fixed in mysql-5.5 5.5.57-0+deb8u1
has caused the Debian Bug report #868788,
regarding Security fixes from the July 2017 CPU
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.)


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

Source: mysql-5.5
Version: 5.5.55-0+deb8u1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for July 2017 will be released on
Tuesday, July 18. According to the pre-release announcement [1], it
will contain information about CVEs fixed in MySQL 5.5.57.

We will update the bug with CVE numbers when they become available, and 
test the update to ensure there are no packaging issues that need 
addressing.


Regards,

Lars Tangvald

[1] 
http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html
--- End Message ---
--- Begin Message ---
Source: mysql-5.5
Source-Version: 5.5.57-0+deb8u1

We believe that the bug you reported is fixed in the latest version of
mysql-5.5, 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 868...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated mysql-5.5 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: Thu, 20 Jul 2017 07:03:49 +0200
Source: mysql-5.5
Binary: libmysqlclient18 libmysqld-pic libmysqld-dev libmysqlclient-dev 
mysql-common mysql-client-5.5 mysql-server-core-5.5 mysql-server-5.5 
mysql-server mysql-client mysql-testsuite mysql-testsuite-5.5 mysql-source-5.5
Architecture: all source
Version: 5.5.57-0+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Debian MySQL Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 868788
Description: 
 libmysqlclient-dev - MySQL database development files
 libmysqlclient18 - MySQL database client library
 libmysqld-dev - MySQL embedded database development files
 libmysqld-pic - PIC version of MySQL embedded server development files
 mysql-client - MySQL database client (metapackage depending on the latest 
versio
 mysql-client-5.5 - MySQL database client binaries
 mysql-common - MySQL database common files, e.g. /etc/mysql/my.cnf
 mysql-server - MySQL database server (metapackage depending on the latest 
versio
 mysql-server-5.5 - MySQL database server binaries and system database setup
 mysql-server-core-5.5 - MySQL database server binaries
 mysql-source-5.5 - MySQL source
 mysql-testsuite - MySQL testsuite
 mysql-testsuite-5.5 - MySQL testsuite
Changes:
 mysql-5.5 (5.5.57-0+deb8u1) jessie-security; urgency=high
 .
   * Imported upstream version 5.5.57 to fix security issues:
 - 
http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html
 - CVE-2017-3635 CVE-2017-3636 CVE-2017-3641 CVE-2017-3648
 - CVE-2017-3651 CVE-2017-3652 CVE-2017-3653
 (Closes: #868788)
Checksums-Sha1: 
 3ddca18597306e8b9161a2159b55f685223da8db 3262 mysql-5.5_5.5.57-0+deb8u1.dsc
 4652b6bbc6b0dbb763ffa778c29e8cb4ea6a9f7f 21044615 mysql-5.5_5.5.57.orig.tar.gz
 14bc13cdebda591e99d5d1810b61906843f19bf5 232520 
mysql-5.5_5.5.57-0+deb8u1.debian.tar.xz
 8f91515ae83079689436b4b968e1b4dfca7c3ad1 84234 
mysql-common_5.5.57-0+deb8u1_all.deb
 e61afe57cba22a3ec2aae4464eee5af8b3f63231 82470 
mysql-server_5.5.57-0+deb8u1_all.deb
 09b92efa14be559a4b8e6c0a17337038952258be 82338 
mysql-client_5.5.57-0+deb8u1_all.deb
 b1ddfb25eacc1360c0a74ac892f52abaa4703e10 82314 
mysql-testsuite_5.5.57-0+deb8u1_all.deb
Checksums-Sha256: 
 a0a622fb7e7f91e87bbee01510d193034121d645628ba5dc8fe3e8b5977959ef 3262 
mysql-5.5_5.5.57-0+deb8u1.dsc
 c1c2bd321e524f92e43fe73d0d6745badd538c984c7561b273ae10e9aef57384 21044615 
mysql-5.5_5.5.57.orig.tar.gz
 b11423f6e61e804c768b677f68e286f97bce008769f9735d7e593ab8e4ed8889 232520 
mysql-5.5_5.5.57-0+deb8u1.debian.tar.xz
 8e88095a88261a4984fe66ed7489cbed5af2bd82aaa67d41f6ccfbfd5765193c 84234 

Bug#867717: marked as done (CVE-2017-11110)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 19:49:59 +
with message-id 
and subject line Bug#867717: fixed in catdoc 0.94.4-1.1+deb8u1
has caused the Debian Bug report #867717,
regarding CVE-2017-0
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.)


-- 
867717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: catdoc
Severity: grave
Tags: security

This was assigned CVE-2017-0:
https://bugzilla.redhat.com/show_bug.cgi?id=1468471

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: catdoc
Source-Version: 0.94.4-1.1+deb8u1

We believe that the bug you reported is fixed in the latest version of
catdoc, 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.
Salvatore Bonaccorso  (supplier of updated catdoc 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, 21 Jul 2017 12:34:24 +0200
Source: catdoc
Binary: catdoc
Architecture: source
Version: 0.94.4-1.1+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Nick Bane 
Changed-By: Salvatore Bonaccorso 
Closes: 867717
Description: 
 catdoc - MS-Word to TeX or plain text converter
Changes:
 catdoc (0.94.4-1.1+deb8u1) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * CVE-2017-0: Heap buffer overflow in ole_init (Closes: #867717)
Checksums-Sha1: 
 053041814b050ab5348e58b53515fbe37e210e1a 1845 catdoc_0.94.4-1.1+deb8u1.dsc
 26c9addb221543288c013ecadf4f6fb0c9eca13e 679156 catdoc_0.94.4.orig.tar.gz
 6a8f019cd401679d35cef555cf10b2f8f39100aa 6984 
catdoc_0.94.4-1.1+deb8u1.debian.tar.xz
Checksums-Sha256: 
 d78e4d84e9bc6437ebb090e49fdeb8f16b406c10b02bef2bde72de383de1b4f6 1845 
catdoc_0.94.4-1.1+deb8u1.dsc
 c06fd69d2a218fcc2ed1320988cef07a67cfa12f25752766d746e25758ee 679156 
catdoc_0.94.4.orig.tar.gz
 acd91ed2cfc4a539d8713656fa67baf8963c9b355a6e64f03e8d16cc84a5cca5 6984 
catdoc_0.94.4-1.1+deb8u1.debian.tar.xz
Files: 
 5b8964cf584d5b5150b470c557ef8272 1845 text optional 
catdoc_0.94.4-1.1+deb8u1.dsc
 4820680e3611392caf2b4dd2413bfae5 679156 text optional catdoc_0.94.4.orig.tar.gz
 5616790078d53ef94d42290a3f587be8 6984 text optional 
catdoc_0.94.4-1.1+deb8u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAllx2UZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EgZwP/0bxSnAiA42e7ZQjhmN2fFysMK1QrhKD
Cfg8JNcBolkg6D8MRt83giS1a58gXARWqysBzAyuusiA8zNw840+zQHKsW16xxXT
6GfffCHrSFeDl9pM7Te1Ebd6qYhO3K7cMaf47hE6Y8hXidbU16qeaeTJcY64e8WK
RZmLAHOZ4wyfRMnGQxTqE5/xqLjgRm7/3Sx7xhevPBojmvhwVtzoeaaXlzNxC0Ls
5921nZlQPsP9xSvA1JIMwBxOhQvXN0ka0vsKy1KjjS9GL4zm73ysWRXAMzGOmWwW
MhlspsG/RAUZ/lmEVCCwCR9pO5qUGT/Zqo0rD8/3TX32b+i8aEZzAXjrThtdryH1
ZDN66icws9lqh7uJ5SLsfKQiTW6vxt01+zrIxXkd7sU7m6L0jBdTMwZEZmqnKQ9Z
cgGqSQN1uGXYPxolpqAq+CfZPDSld/Z5nmw5W2ZyJI16bdI3X5kjzScaO2gvQq1P
FTshwtjOLznM5fzvhzG+sByzL49NKfCCmji6oVTedOrX0aaV1U5QzUNwoFaMMZfT
tWvo+uWgLGJTw6Yr7oYFtbtFldQVIXnTbc6OV8fT6dAHE+y+P7hOt/vXilcXoWYh
c8x/1MTHEfOwhloheBoR/IUzCfpxepBUMR7pRSbLp3v9HBoeS2ZFEB8FDVSDPsBT
fVNGLEj+w3S0
=gVKV
-END PGP SIGNATURE End Message ---

Bug#868952: marked as done (bind9: regression introduced in DSA-3904-1 can cause problems with zone transfers from some non-BIND servers)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 19:49:40 +
with message-id 
and subject line Bug#868952: fixed in bind9 1:9.9.5.dfsg-9+deb8u13
has caused the Debian Bug report #868952,
regarding bind9: regression introduced in DSA-3904-1 can cause problems with 
zone transfers from some non-BIND servers
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.)


-- 
868952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind9
Version: 1:9.10.3.dfsg.P4-12.4
Severity: serious
Tags: upstream fixed-upstream
Justification: regression relative to DSA-3904-1
Control: affects -1 security.debian.org,release.debian.org
Control: found -1 1:9.9.5.dfsg-9+deb8u12
Control: found -1 1:9.10.3.dfsg.P4-12.3+deb9u1

Hi

DSA-3904-1 (and the respective DLA) introduced a regression as
described in:

https://lists.isc.org/pipermail/bind-announce/2017-July/001054.html

"Problems may occur when transferring from another server if
TSIG is used *and* the AXFR or IXFR is more than two messages
in length *and* the master server does not sign every message.
NSD is an example of a popular DNS product that behaves in this
manner [note: NSD's behavior is in compliance with the requirements
of the RFC; it is BIND that has introduced a problem here.]"

Commit in master:
https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commitdiff;h=58f0fb325bbd9258d06431281eb8fdea2b126305

Commit cherry-picked to v9_9_10_P3
https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commitdiff;h=6fcdcabc11f18eb128167f7f7eca4a244bf75c52

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.9.5.dfsg-9+deb8u13

We believe that the bug you reported is fixed in the latest version of
bind9, 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 868...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated bind9 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: Sun, 23 Jul 2017 15:15:58 +0200
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 
libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd 
libbind-export-dev libdns-export100 libdns-export100-udeb libisc-export95 
libisc-export95-udeb libisccfg-export90 libisccfg-export90-udeb libirs-export91 
libirs-export91-udeb
Architecture: source all amd64
Version: 1:9.9.5.dfsg-9+deb8u13
Distribution: jessie-security
Urgency: high
Maintainer: LaMont Jones 
Changed-By: Yves-Alexis Perez 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-90 - BIND9 Shared Library used by BIND
 libdns-export100 - Exported DNS Shared Library
 libdns-export100-udeb - Exported DNS library for debian-installer (udeb)
 libdns100  - DNS Shared Library used by BIND
 libirs-export91 - Exported IRS Shared Library
 libirs-export91-udeb - Exported IRS library for debian-installer (udeb)
 libisc-export95 - Exported ISC Shared Library
 libisc-export95-udeb - Exported ISC library for debian-installer (udeb)
 libisc95   - ISC Shared Library used by BIND
 libisccc90 - Command Channel Library used by BIND
 libisccfg-export90 - Exported ISC CFG Shared Library
 libisccfg-export90-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg90 - Config File Handling Library used by BIND
 liblwres90 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 868952
Changes:
 bind9 (1:9.9.5.dfsg-9+deb8u13) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Add patch to fix regression introduced by patch for CVE-2017-3042.
   

Bug#867717: marked as done (CVE-2017-11110)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 19:47:56 +
with message-id 
and subject line Bug#867717: fixed in catdoc 
1:0.94.3~git20160113.dbc9ec6+dfsg-1+deb9u1
has caused the Debian Bug report #867717,
regarding CVE-2017-0
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.)


-- 
867717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: catdoc
Severity: grave
Tags: security

This was assigned CVE-2017-0:
https://bugzilla.redhat.com/show_bug.cgi?id=1468471

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: catdoc
Source-Version: 1:0.94.3~git20160113.dbc9ec6+dfsg-1+deb9u1

We believe that the bug you reported is fixed in the latest version of
catdoc, 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.
Salvatore Bonaccorso  (supplier of updated catdoc 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, 21 Jul 2017 12:38:52 +0200
Source: catdoc
Binary: catdoc
Architecture: source
Version: 1:0.94.3~git20160113.dbc9ec6+dfsg-1+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Martín Ferrari 
Changed-By: Salvatore Bonaccorso 
Closes: 867717
Description: 
 catdoc - Convert Word, Excel, and PowerPoint files to plain text
Changes:
 catdoc (1:0.94.3~git20160113.dbc9ec6+dfsg-1+deb9u1) stretch-security; 
urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * CVE-2017-0: Heap buffer overflow in ole_init (Closes: #867717)
Checksums-Sha1: 
 7dea28839964b0612eee7af135777fb2d0b165a3 2148 
catdoc_0.94.3~git20160113.dbc9ec6+dfsg-1+deb9u1.dsc
 c48049682cb06b398d7ca863b6cce4a6b19e4b3b 141753 
catdoc_0.94.3~git20160113.dbc9ec6+dfsg.orig.tar.gz
 8e30a7d3274e66d5f437d1824425c1d37bb7175b 52752 
catdoc_0.94.3~git20160113.dbc9ec6+dfsg-1+deb9u1.debian.tar.xz
Checksums-Sha256: 
 35c69500d0ead9335789b222304c74c267102916218876a25b26ed275abb5916 2148 
catdoc_0.94.3~git20160113.dbc9ec6+dfsg-1+deb9u1.dsc
 3f98fb577a45925f853257f2a4b4caeab258f06c1056941335c9fb8d9eb712b6 141753 
catdoc_0.94.3~git20160113.dbc9ec6+dfsg.orig.tar.gz
 f7b5a6bcdaf0ec26d8acc65f73640cdeb00d0cbe7a10df7040cc55cde9bb052a 52752 
catdoc_0.94.3~git20160113.dbc9ec6+dfsg-1+deb9u1.debian.tar.xz
Files: 
 99bda9a60f2dbaa66b996170f8c7aac1 2148 text optional 
catdoc_0.94.3~git20160113.dbc9ec6+dfsg-1+deb9u1.dsc
 86d8e0308681817904a3cb68d6b62771 141753 text optional 
catdoc_0.94.3~git20160113.dbc9ec6+dfsg.orig.tar.gz
 6f2c69d79fef810332d90c23e247a382 52752 text optional 
catdoc_0.94.3~git20160113.dbc9ec6+dfsg-1+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAllx2qtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E2HEQAJb8KF5/Mw/bgcbIlQWSqf4zwcT845c4
7D7Vn0n2Mv1ixbljVVkheOrbmr3Mdh5T5bOiEEXaVaKrTes6RoxsZ4fQ/mywWZyh
vfdGVIruUcQ3sfJfzslkjL1/j7sQE6C9ZdpTi3oS+iRowaPMo3PZTywOUzDjGTvU
4bzgGQdoQIo/q+AvLwy5vRDFO/iD7E8E46+kHjkBQTL2J8cWhHlESCZvyCC6CziH
mPVXav+7EkU/cnFBzTQ/JEfctKW7l7rLFHbDGqGa9EZY9R7TcZ5zsayc2aKHioA5
ZCamhq8FSMbvir14Tqp2nueLs9+6UQVa/MaJXn0QbSqLsbq90l2/ocAmGqIOiZK4
OZcSfF22668/8XQRjtH+/aTzc86P+JIgHEHSqY4ehEJ868swNh18Avp/nOxLYdtm
gtD1HjOhWaD9+0gF0HkLdQf8oIdaJIsqEcKnb4x6CJmIORsE1defAIKTbehhEk1R
oXWHceNzP6vFhJ5g9dUj7/Q1+T9kRAnV/HLU6cHmt+7YoWGklfkcL9ldDDzzyqG7
ML2uODpjkT7k6pOHMYSVoJflMU92ftkJngUKNWLlhut45yEwiOhqTARKSnWgxZ8N
mZxPiko980bRbxoMMhVNsG8dsNGO69X92TqfYml1ZatwWMWN8M8MuNvTq+IuwBbS
KxCTQPTym3Yv
=IwiR
-END PGP SIGNATURE End Message ---

Bug#853421: marked as done (glib2.0: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 22:45:41 +0300
with message-id <20170805194541.vmy3avudcij6vo77@localhost>
and subject line glib2.0 builds with gcc 7
has caused the Debian Bug report #853421,
regarding glib2.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.)


-- 
853421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glib2.0
Version: 2.50.2-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/<>/./glib -I.. -I.. 
-I../glib -I/<>/./glib -I/<>/. 
-DG_LOG_DOMAIN=\"GLib\" -DG_DISABLE_CAST_CHECKS -DGLIB_COMPILATION 
-DPCRE_STATIC -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall 
-Wstrict-prototypes -Werror=declaration-after-statement 
-Werror=missing-prototypes -Werror=implicit-function-declaration 
-Werror=pointer-arith -Werror=init-self -Werror=format=2 
-Werror=missing-include-dirs -fvisibility=hidden -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c /<>/./glib/gvariant-core.c -o 
libglib_2_0_la-gvariant-core.o >/dev/null 2>&1
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/<>/./glib -I.. -I.. 
-I../glib -I/<>/./glib -I/<>/. 
-DG_LOG_DOMAIN=\"GLib\" -DG_DISABLE_CAST_CHECKS -DGLIB_COMPILATION 
-DPCRE_STATIC -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall 
-Wstrict-prototypes -Werror=declaration-after-statement 
-Werror=missing-prototypes -Werror=implicit-function-declaration 
-Werror=pointer-arith -Werror=init-self -Werror=format=2 
-Werror=missing-include-dirs -fvisibility=hidden -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c /<>/./glib/gdate.c -o 
libglib_2_0_la-gdate.o >/dev/null 2>&1
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/<>/./glib -I.. -I.. 
-I../glib -I/<>/./glib -I/<>/. 
-DG_LOG_DOMAIN=\"GLib\" -DG_DISABLE_CAST_CHECKS -DGLIB_COMPILATION 
-DPCRE_STATIC -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall 
-Wstrict-prototypes -Werror=declaration-after-statement 
-Werror=missing-prototypes -Werror=implicit-function-declaration 
-Werror=pointer-arith -Werror=init-self -Werror=format=2 
-Werror=missing-include-dirs -fvisibility=hidden -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c /<>/./glib/gregex.c -o 
libglib_2_0_la-gregex.o >/dev/null 2>&1
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/<>/./glib -I.. -I.. 
-I../glib -I/<>/./glib -I/<>/. 
-DG_LOG_DOMAIN=\"GLib\" -DG_DISABLE_CAST_CHECKS -DGLIB_COMPILATION 
-DPCRE_STATIC -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall 
-Wstrict-prototypes -Werror=declaration-after-statement 
-Werror=missing-prototypes -Werror=implicit-function-declaration 
-Werror=pointer-arith -Werror=init-self -Werror=format=2 
-Werror=missing-include-dirs -fvisibility=hidden -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c /<>/./glib/giochannel.c -o 
libglib_2_0_la-giochannel.o >/dev/null 2>&1
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I/<>/./glib -I.. -I.. 
-I../glib -I/<>/./glib -I/<>/. 
-DG_LOG_DOMAIN=\"GLib\" -DG_DISABLE_CAST_CHECKS -DGLIB_COMPILATION 
-DPCRE_STATIC -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wall 
-Wstrict-prototypes -Werror=declaration-after-statement 
-Werror=missing-prototypes -Werror=implicit-function-declaration 
-Werror=pointer-arith -Werror=init-self 

Bug#870852: rubocop: CVE-2017-8418

[Salvatore Bonaccorso]

Source: rubocop
Version: 0.48.1+dfsg-1
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/bbatsov/rubocop/issues/4336

Hi,

the following vulnerability was published for rubocop.

CVE-2017-8418[0]:
| RuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing
| local users to exploit this to tamper with cache files belonging to
| other users.

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-8418
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8418
[1] https://github.com/bbatsov/rubocop/issues/4336

Regards,
Salvatore

Bug#853661: marked as done (simulavr: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 22:26:24 +0300
with message-id <20170805192624.knq3o4r7fo5ot6qh@localhost>
and subject line simulavr builds with gcc 7
has caused the Debian Bug report #853661,
regarding simulavr: 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.)


-- 
853661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:simulavr
Version: 0.1.2.2-7
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/simulavr_0.1.2.2-7_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

[...]
then mv -f ".deps/avrcore.Tpo" ".deps/avrcore.Po"; else rm -f 
".deps/avrcore.Tpo"; exit 1; fi
if x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.-Wall -Winline -Werror 
-I../src/getopt -Wall -g -std=gnu89 -O2 -MT avrerror.o -MD -MP -MF 
".deps/avrerror.Tpo" -c -o avrerror.o avrerror.c; \
then mv -f ".deps/avrerror.Tpo" ".deps/avrerror.Po"; else rm -f 
".deps/avrerror.Tpo"; exit 1; fi
if x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.-Wall -Winline -Werror 
-I../src/getopt -Wall -g -std=gnu89 -O2 -MT avrmalloc.o -MD -MP -MF 
".deps/avrmalloc.Tpo" -c -o avrmalloc.o avrmalloc.c; \
then mv -f ".deps/avrmalloc.Tpo" ".deps/avrmalloc.Po"; else rm -f 
".deps/avrmalloc.Tpo"; exit 1; fi
if x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.-Wall -Winline -Werror 
-I../src/getopt -Wall -g -std=gnu89 -O2 -MT callback.o -MD -MP -MF 
".deps/callback.Tpo" -c -o callback.o callback.c; \
then mv -f ".deps/callback.Tpo" ".deps/callback.Po"; else rm -f 
".deps/callback.Tpo"; exit 1; fi
if x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.-Wall -Winline -Werror 
-I../src/getopt -Wall -g -std=gnu89 -O2 -MT decoder.o -MD -MP -MF 
".deps/decoder.Tpo" -c -o decoder.o decoder.c; \
then mv -f ".deps/decoder.Tpo" ".deps/decoder.Po"; else rm -f 
".deps/decoder.Tpo"; exit 1; fi
if x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.-Wall -Winline -Werror 
-I../src/getopt -Wall -g -std=gnu89 -O2 -MT device.o -MD -MP -MF 
".deps/device.Tpo" -c -o device.o device.c; \
then mv -f ".deps/device.Tpo" ".deps/device.Po"; else rm -f ".deps/device.Tpo"; 
exit 1; fi
if x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.-Wall -Winline -Werror 
-I../src/getopt -Wall -g -std=gnu89 -O2 -MT devsupp.o -MD -MP -MF 
".deps/devsupp.Tpo" -c -o devsupp.o devsupp.c; \
then mv -f ".deps/devsupp.Tpo" ".deps/devsupp.Po"; else rm -f 
".deps/devsupp.Tpo"; exit 1; fi
if x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.-Wall -Winline -Werror 
-I../src/getopt -Wall -g -std=gnu89 -O2 -MT display.o -MD -MP -MF 
".deps/display.Tpo" -c -o display.o display.c; \
then mv -f ".deps/display.Tpo" ".deps/display.Po"; else rm -f 
".deps/display.Tpo"; exit 1; fi
display.c: In function 'display_open':
display.c:144:45: error: '%d' directive output may be truncated writing between 
1 and 11 bytes into a region of size 9 [-Werror=format-truncation=]
 snprintf (spfd, sizeof (spfd) - 1, "%d", pfd[0]);
 ^~
display.c:144:44: note: using the range [1, -2147483648] for directive argument
 snprintf (spfd, sizeof (spfd) - 1, "%d", pfd[0]);
^~~~
display.c:144:9: note: format output between 2 and 12 bytes into a destination 
of size 9
 snprintf (spfd, sizeof (spfd) - 1, "%d", pfd[0]);
 ^~~~
display.c:147:59: error: '%d' directive 

Processed: Re: Processed (with 1 error): Re: Bug#869856: openssl: FTBFS: Testsuite failures

[Debian Bug Tracking System]

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

> forwarded 869856 https://github.com/openssl/openssl/issues/3562
Bug #869856 [src:openssl] openssl: FTBFS: Testsuite failures
Set Bug forwarded-to-address to 
'https://github.com/openssl/openssl/issues/3562'.
>
End of message, stopping processing here.

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

Bug#870850: ruby-pkg-config FTBFS: Failure: test_libs_only_l(PkgConfigTest)

[Adrian Bunk]

Source: ruby-pkg-config
Version: 1.2.3-2
Severity: serious

Some recent change in unstable makes ruby-pkg-config FTBFS:

https://tests.reproducible-builds.org/debian/history/ruby-pkg-config.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-pkg-config.html

...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/1st/ruby-pkg-config-1.2.3/debian/ruby-pkg-config/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-pkg-config/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 debian/ruby-tests.rb
Loaded suite debian/ruby-tests
Started
Did not match, retry with sorting
.Did not match, retry with sorting
F
===
Failure: test_libs_only_l(PkgConfigTest)
/build/1st/ruby-pkg-config-1.2.3/test/test_pkg_config.rb:50:in 
`test_libs_only_l'
 47: result = pkg_config("cairo-png", "--libs-only-l")
 48: msvc_result = result.gsub(/-l(cairo|png[0-9]+)\b/, '\1.lib')
 49: assert_not_equal(msvc_result, result)
  => 50: assert_equal(msvc_result, @cairo_png.libs_only_l)
 51:   end
 52: 
 53:   def test_libs_only_L
<"cairo.lib png16.lib -lz">(US-ASCII) expected but was
<"cairo.lib png16.lib z.lib">(UTF-8)

diff:
? cairo.lib png16.lib - lz 
? z. ib
  
? Encoding: US -ASCII
?TF 8
===
.

Finished in 11.707630081 seconds.
--
11 tests, 30 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
90.9091% passed
--
0.94 tests/s, 2.56 assertions/s
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-pkg-config-1.2.3/debian/ruby-pkg-config returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1

Bug#870849: ruby-kramdown-rfc2629 FTBFS with ruby-kramdown 1.14.0-1

[Adrian Bunk]

Source: ruby-kramdown-rfc2629
Version: 1.0.36-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-kramdown-rfc2629.html

...
GEM_PATH=debian/ruby-kramdown-rfc2629/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -e gem\ \"kramdown-rfc2629\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'kramdown' (~> 1.12.0) - did find: [kramdown-1.14.0] (Gem::LoadError)
...

Bug#870772: libgsl misses some breaks/replaces

[Dirk Eddelbuettel]

On 5 August 2017 at 06:49, Dirk Eddelbuettel wrote:
| On 5 August 2017 at 12:35, Guillem Jover wrote:
| | Strictly speaking, libgslcblas does have a SONAME:
| | 
| |   $ objdump -p /usr/lib/x86_64-linux-gnu/libgslcblas.so.0 | grep SONAME
| | SONAME   libgslcblas.so.0
| | 
| | which means to me that it should guarantee some ABI stability,
| 
| Yes. I have never seen it change its soname in all these years.
| 
| | otherwise this library should become a private library by using RPATH,
| | or be folded into the main libgsl library?
| | 
| | And IMO, splitting this library appears as the only correct solution
| | here, because:
| | 
| |   - Both shared libraries have different SONAMEs that's (I'm assuming)
| | why you've had to keep adding Replaces against the old packages when
| | bumping the SONAME for the main library.
| |   - This causes transition problems, as both old and new main library
| | packages cannot be installed at the same time, even though by
| | themselves alone there would be no filesystem conflicts. Which in
| | turn means we cannot have a mix of packages linking against the
| | old and new libraries, or in worse conditions a mix of a new -dev
| | using the new librs with some other packages using the old libs.
| |   - If (but I'm not sure if that's possible) one can link only against
| | the libgslcblas library, that would cause breakage in case the
| | SONAME gets bumped as as the package is not keyed on that, and
| | programs linked against the old SONAME would stop working.
| 
| I agree. It's a bit more work, but the better fix.
|  
| | > But it is probably
| | > easier to go with 'Breaks: ' as you suggest.
| | 
| | I'd consider that the wrong fix TBH.
| | 
| | > The thing that is unpleasant is that we probably need to keep adding the 
old
| | > soname libraries to debian/control as this progresses.
| | 
| | Not anymore after the libraries have been split. Or perhaps I don't
| | understand your concern?
| 
| Yes, it should help with that.
| 
| Thanks for the input!

Now done, and upgrade tested on Debian testing and unstable. Seems to work.

Let's hope it doesn't longer in NEW for too long.

Thanks for the suggestions and discussion; this was really helpful.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#870848: jackson-databind: CVE-2017-7525: Deserialization vulnerability via readValue method of ObjectMapper

[Salvatore Bonaccorso]

Source: jackson-databind
Version: 2.8.6-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/FasterXML/jackson-databind/issues/1599

Hi,

the following vulnerability was published for jackson-databind.

CVE-2017-7525[0]:
Deserialization vulnerability via readValue method of ObjectMapper

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

Upstream tracking is at [2].

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-7525
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7525
[1] https://github.com/FasterXML/jackson-databind/issues/1599
[2] https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7525

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: user debian...@lists.debian.org, usertagging 870772, affects 870772, affects 870455

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 870772 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 870772 + libgsl-dev gsl-bin libgsl-dbg
Bug #870772 [libgsl23] libgsl misses some breaks/replaces
Added indication that 870772 affects libgsl-dev, gsl-bin, and libgsl-dbg
> affects 870455 + libsane1
Bug #870455 [libsane-common] libsane-common: fails to purge: rmdir: failed to 
remove '/etc/sane.d/': No such file or directory
Added indication that 870455 affects libsane1
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#869856: openssl: FTBFS: Testsuite failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream pending
Bug #869856 [src:openssl] openssl: FTBFS: Testsuite failures
Added tag(s) patch, pending, and fixed-upstream.
> forwaded -1 https://github.com/openssl/openssl/issues/3562
Unknown command or malformed arguments to command.


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

Bug#869856: openssl: FTBFS: Testsuite failures

[Sebastian Andrzej Siewior]

control: tags -1 patch fixed-upstream pending
control: forwaded -1 https://github.com/openssl/openssl/issues/3562

On 2017-07-27 19:06:19 [-0700], Daniel Schepler wrote:
> It appears so.  (Though I did have to apply it by hand as there was no
> "clientsession" line for patch to sync to in hunk #2.)

okay. So we have fix a which will be part of 1.1.0g and I don't see a reason
to upload it right away. So I suggest to wait until upstream releases
something new.

Sebastian

Bug#853576: marked as done (nss: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 21:57:13 +0300
with message-id <20170805185713.qttk2mpvm4ln7uuu@localhost>
and subject line nss builds with gcc 7
has caused the Debian Bug report #853576,
regarding nss: 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.)


-- 
853576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nss
Version: 2:3.26.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/nss_3.26.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

[...]
make[6]: Leaving directory '/<>/nss/lib/libpkix/pkix/util'
make[5]: Leaving directory '/<>/nss/lib/libpkix/pkix'
cd pkix_pl_nss; /usr/bin/make libs
make[5]: Entering directory '/<>/nss/lib/libpkix/pkix_pl_nss'
cd pki; /usr/bin/make libs
make[6]: Entering directory '/<>/nss/lib/libpkix/pkix_pl_nss/pki'
gcc -o OBJS/pkix_pl_basicconstraints.o -c -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-DLINUX2_1 -m64 -pipe -ffunction-sections -fdata-sections -DHAVE_STRERROR 
-DLINUX -Dlinux -Wall -Werror -DXP_UNIX -UDEBUG -DNDEBUG -D_REENTRANT 
-DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 
-DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/usr/include/nspr 
-I/<>/dist/include -I/<>/dist/public/nss 
-I/<>/dist/private/nss  pkix_pl_basicconstraints.c
gcc -o OBJS/pkix_pl_cert.o -c -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pipe 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DLINUX2_1 -m64 -pipe -ffunction-sections 
-fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -Wall -Werror -DXP_UNIX -UDEBUG 
-DNDEBUG -D_REENTRANT -DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY 
-DNO_NSPR_10_SUPPORT -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES 
-I/usr/include/nspr -I/<>/dist/include 
-I/<>/dist/public/nss -I/<>/dist/private/nss  
pkix_pl_cert.c
gcc -o OBJS/pkix_pl_certpolicyinfo.o -c -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-DLINUX2_1 -m64 -pipe -ffunction-sections -fdata-sections -DHAVE_STRERROR 
-DLINUX -Dlinux -Wall -Werror -DXP_UNIX -UDEBUG -DNDEBUG -D_REENTRANT 
-DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 
-DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/usr/include/nspr 
-I/<>/dist/include -I/<>/dist/public/nss 
-I/<>/dist/private/nss  pkix_pl_certpolicyinfo.c
gcc -o OBJS/pkix_pl_certpolicymap.o -c -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-DLINUX2_1 -m64 -pipe -ffunction-sections -fdata-sections -DHAVE_STRERROR 
-DLINUX -Dlinux -Wall -Werror -DXP_UNIX -UDEBUG -DNDEBUG -D_REENTRANT 
-DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 
-DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/usr/include/nspr 
-I/<>/dist/include -I/<>/dist/public/nss 
-I/<>/dist/private/nss  pkix_pl_certpolicymap.c
gcc -o OBJS/pkix_pl_certpolicyqualifier.o -c -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-DLINUX2_1 -m64 -pipe -ffunction-sections -fdata-sections -DHAVE_STRERROR 
-DLINUX -Dlinux -Wall -Werror -DXP_UNIX -UDEBUG -DNDEBUG -D_REENTRANT 
-DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 853541 src:tbb
Bug #853541 [src:mathicgb] mathicgb: ftbfs with GCC-7
Bug reassigned from package 'src:mathicgb' to 'src:tbb'.
No longer marked as found in versions mathicgb/1.0~git20170104-1.
Ignoring request to alter fixed versions of bug #853541 to the same values 
previously set
> forcemerge 853403 853541
Bug #853403 {Done: Steve Capper } [src:tbb] flexbar: 
ftbfs with GCC-7
Bug #853679 {Done: Steve Capper } [src:tbb] tbb: ftbfs 
with GCC-7
Bug #853541 [src:tbb] mathicgb: ftbfs with GCC-7
Unset Bug forwarded-to-address
Severity set to 'important' from 'serious'
Marked Bug as done
Added indication that 853541 affects src:flexbar
Marked as fixed in versions tbb/2017~U7-2.
Marked as found in versions tbb/4.3~20150611-2.
Bug #853679 {Done: Steve Capper } [src:tbb] tbb: ftbfs 
with GCC-7
Merged 853403 853541 853679
> affects 853403 src:mathicgb
Bug #853403 {Done: Steve Capper } [src:tbb] flexbar: 
ftbfs with GCC-7
Bug #853541 {Done: Steve Capper } [src:tbb] mathicgb: 
ftbfs with GCC-7
Bug #853679 {Done: Steve Capper } [src:tbb] tbb: ftbfs 
with GCC-7
Added indication that 853403 affects src:mathicgb
Added indication that 853541 affects src:mathicgb
Added indication that 853679 affects src:mathicgb
> thanks
Stopping processing here.

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

Bug#853529: lordsawar: ftbfs with GCC-7

[Markus Koschany]

Control: tags -1 pending patch

This issue is fixed in Git. I will upload a new revision next week.

Bug#853463: marked as done (juce: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 21:53:38 +0300
with message-id <20170805185338.lhvcdoxsvirzp532@localhost>
and subject line juce builds with gcc 7
has caused the Debian Bug report #853463,
regarding juce: 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.)


-- 
853463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:juce
Version: 4.3.0~repack-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/juce_4.3.0~repack-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

[...]
g++  -MMD  -D "LINUX=1" -D "JUCE_DLL_BUILD=1" -D 
'JUCE_APP_CONFIG_HEADER="AppConfig.h"'  -DJUCE_INCLUDE_FLAC_CODE=0 
-DJUCE_INCLUDE_JPEGLIB_CODE=0 -DJUCE_INCLUDE_PNGLIB_CODE=0 
-DPNG_SKIP_SETJMP_CHECK -DJUCE_INCLUDE_OGGVORBIS_CODE=0 
-DJUCE_INCLUDE_ZLIB_CODE=0 -I. -Ibuild -I../../modules  -D "DEBUG=1" -D 
"_DEBUG=1" -g -ggdb -O0  -fPIC -fpermissive  -I/usr/include/libpng16 
-I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/alsa 
-I/usr/include/x86_64-linux-gnu -std=c++11 -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -o build/intermediate/Debug/juce_audio_basics.o -c 
build/juce_audio_basics.cpp
echo '#include "../../modules/juce_audio_devices/juce_audio_devices.cpp"' > 
build/juce_audio_devices.cpp
g++  -MMD  -D "LINUX=1" -D "JUCE_DLL_BUILD=1" -D 
'JUCE_APP_CONFIG_HEADER="AppConfig.h"'  -DJUCE_INCLUDE_FLAC_CODE=0 
-DJUCE_INCLUDE_JPEGLIB_CODE=0 -DJUCE_INCLUDE_PNGLIB_CODE=0 
-DPNG_SKIP_SETJMP_CHECK -DJUCE_INCLUDE_OGGVORBIS_CODE=0 
-DJUCE_INCLUDE_ZLIB_CODE=0 -I. -Ibuild -I../../modules  -D "DEBUG=1" -D 
"_DEBUG=1" -g -ggdb -O0  -fPIC -fpermissive  -I/usr/include/libpng16 
-I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/alsa 
-I/usr/include/x86_64-linux-gnu -std=c++11 -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -o build/intermediate/Debug/juce_audio_devices.o -c 
build/juce_audio_devices.cpp
echo '#include "../../modules/juce_audio_formats/juce_audio_formats.cpp"' > 
build/juce_audio_formats.cpp
g++  -MMD  -D "LINUX=1" -D "JUCE_DLL_BUILD=1" -D 
'JUCE_APP_CONFIG_HEADER="AppConfig.h"'  -DJUCE_INCLUDE_FLAC_CODE=0 
-DJUCE_INCLUDE_JPEGLIB_CODE=0 -DJUCE_INCLUDE_PNGLIB_CODE=0 
-DPNG_SKIP_SETJMP_CHECK -DJUCE_INCLUDE_OGGVORBIS_CODE=0 
-DJUCE_INCLUDE_ZLIB_CODE=0 -I. -Ibuild -I../../modules  -D "DEBUG=1" -D 
"_DEBUG=1" -g -ggdb -O0  -fPIC -fpermissive  -I/usr/include/libpng16 
-I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/alsa 
-I/usr/include/x86_64-linux-gnu -std=c++11 -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -o build/intermediate/Debug/juce_audio_formats.o -c 
build/juce_audio_formats.cpp
echo '#include "../../modules/juce_audio_processors/juce_audio_processors.cpp"' 
> build/juce_audio_processors.cpp
g++  -MMD  -D "LINUX=1" -D "JUCE_DLL_BUILD=1" -D 
'JUCE_APP_CONFIG_HEADER="AppConfig.h"'  -DJUCE_INCLUDE_FLAC_CODE=0 
-DJUCE_INCLUDE_JPEGLIB_CODE=0 -DJUCE_INCLUDE_PNGLIB_CODE=0 
-DPNG_SKIP_SETJMP_CHECK -DJUCE_INCLUDE_OGGVORBIS_CODE=0 
-DJUCE_INCLUDE_ZLIB_CODE=0 -I. -Ibuild -I../../modules  -D "DEBUG=1" -D 
"_DEBUG=1" -g -ggdb -O0  -fPIC -fpermissive  -I/usr/include/libpng16 
-I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/alsa 

Processed: Re: lordsawar: ftbfs with GCC-7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending patch
Bug #853529 [src:lordsawar] lordsawar: ftbfs with GCC-7
Added tag(s) patch and pending.

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

Processed: bug 870832 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=122718

[Debian Bug Tracking System]

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

> forwarded 870832 https://rt.cpan.org/Ticket/Display.html?id=122718
Bug #870832 [src:libmath-prime-util-gmp-perl] libmath-prime-util-gmp-perl FTBFS 
on big endian: Failed 2/31 test programs. 8/2885 subtests failed.
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=122718'.
> thanks
Stopping processing here.

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

Bug#867516: marked as done (pytest-xdist FTBFS with python 3.6 as supported version)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 18:19:36 +
with message-id 
and subject line Bug#867516: fixed in pytest-xdist 1.18.2-1
has caused the Debian Bug report #867516,
regarding pytest-xdist 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.)


-- 
867516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-xdist
Version: 1.15.0-3
Severity: serious
Tags: buster sid

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

...
I: pybuild base:184: python3.6 -m pytest -x -v
= test session starts ==
platform linux -- Python 3.6.2rc1, pytest-3.0.6, py-1.4.34, pluggy-0.4.0 -- 
/usr/bin/python3.6
cachedir: .cache
rootdir: /build/1st/pytest-xdist-1.15.0, inifile: tox.ini
plugins: xdist-1.15.0
collecting ... collected 110 items

testing/acceptance_test.py::TestDistribution::test_n1_pass PASSED
testing/acceptance_test.py::TestDistribution::test_n1_fail PASSED
testing/acceptance_test.py::TestDistribution::test_n1_import_error FAILED
=== short test summary info 
FAIL testing/acceptance_test.py::TestDistribution::()::test_n1_import_error

=== FAILURES ===
 TestDistribution.test_n1_import_error _

self = 
testdir = 

def test_n1_import_error(self, testdir):
p1 = testdir.makepyfile("""
import __import_of_missing_module
def test_import():
pass
""")
result = testdir.runpytest(p1, "-n1")
assert result.ret == 1
result.stdout.fnmatch_lines([
>   "E   ImportError: *__import_of_missing_module*",
])
E   Failed: nomatch: 'E   ImportError: *__import_of_missing_module*'
E   and: '= test session starts 
=='
E   and: 'platform linux -- Python 3.6.2rc1, pytest-3.0.6, py-1.4.34, 
pluggy-0.4.0'
E   and: 'rootdir: 
/tmp/pytest-of-pbuilder1/pytest-3/testdir/test_n1_import_error0, inifile: '
E   and: 'plugins: xdist-1.15.0'
E   and: 'gw0 I'
E   and: 'gw0 [0]'
E   and: ''
E   and: 'scheduling tests via LoadScheduling'
E   and: ''
E   and: ' ERRORS 
'
E   and: '___ ERROR collecting test_n1_import_error.py 
___'
E   and: "ImportError while importing test module 
'/tmp/pytest-of-pbuilder1/pytest-3/testdir/test_n1_import_error0/test_n1_import_error.py'."
E   and: 'Hint: make sure your test modules/packages have valid Python 
names.'
E   and: 'Traceback:'
E   and: 'test_n1_import_error.py:1: in '
E   and: 'import __import_of_missing_module'
E   and: "E   ModuleNotFoundError: No module named 
'__import_of_missing_module'"
E   and: '=== 1 error in 0.60 seconds 
'
E   and: ''
E   remains unmatched: 'E   ImportError: *__import_of_missing_module*'

/build/1st/pytest-xdist-1.15.0/testing/acceptance_test.py:33: Failed
- Captured stdout call -
= test session starts ==
platform linux -- Python 3.6.2rc1, pytest-3.0.6, py-1.4.34, pluggy-0.4.0
rootdir: /tmp/pytest-of-pbuilder1/pytest-3/testdir/test_n1_import_error0, 
inifile: 
plugins: xdist-1.15.0
gw0 I
gw0 [0]

scheduling tests via LoadScheduling

 ERRORS 
___ ERROR collecting test_n1_import_error.py ___
ImportError while importing test module 
'/tmp/pytest-of-pbuilder1/pytest-3/testdir/test_n1_import_error0/test_n1_import_error.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
test_n1_import_error.py:1: in 
import __import_of_missing_module
E   ModuleNotFoundError: No module named '__import_of_missing_module'
=== 1 error in 0.60 seconds 
 Interrupted: stopping after 1 failures 
== 1 failed, 2 passed in 3.22 seconds ==
E: pybuild pybuild:283: test: 

Bug#869094: marked as done (pytest-xdist: TestLooponFailing::test_looponfail_removed_test FAILED)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 18:19:36 +
with message-id 
and subject line Bug#869094: fixed in pytest-xdist 1.18.2-1
has caused the Debian Bug report #869094,
regarding pytest-xdist: TestLooponFailing::test_looponfail_removed_test FAILED
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.)


-- 
869094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-xdist
Version: 1.15.0-3
Severity: serious
Justification: fails to build from source
Control: forwarded -1 https://github.com/pytest-dev/pytest-xdist/issues/163

There is a new test failure with Pytest >= 3.1.0, during the build it appears
the first time with Python 2.7:


=== FAILURES ===
 TestLooponFailing.test_looponfail_removed_test 

self = 
testdir = 

def test_looponfail_removed_test(self, testdir):
modcol = testdir.getmodulecol("""
def test_one():
assert 0
def test_two():
assert 0
""")
remotecontrol = RemoteControl(modcol.config)
remotecontrol.loop_once()
assert len(remotecontrol.failures) == 2

modcol.fspath.write(py.code.Source("""
def test_xxx(): # renamed test
assert 0
def test_two():
assert 1 # pass now
"""))
removepyc(modcol.fspath)
remotecontrol.loop_once()
>   assert len(remotecontrol.failures) == 0
E   AssertionError: assert 1 == 0
E+  where 1 = len(['test_looponfail_removed_test.py::test_xxx'])
E+where ['test_looponfail_removed_test.py::test_xxx'] = 
.failures


The failure takes place also with the latest version 0.18.1, it isn't yet solved
upstream.

DS

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: pytest-xdist
Source-Version: 1.18.2-1

We believe that the bug you reported is fixed in the latest version of
pytest-xdist, 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 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated pytest-xdist 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: Sat, 05 Aug 2017 19:53:17 +0200
Source: pytest-xdist
Binary: python-pytest-xdist python3-pytest-xdist
Architecture: source all
Version: 1.18.2-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Stender 
Changed-By: Daniel Stender 
Description:
 python-pytest-xdist - xdist plugin for py.test
 python3-pytest-xdist - xdist plugin for py.test (Python 3)
Closes: 864360 867516 869094
Changes:
 pytest-xdist (1.18.2-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #864360, #867516):
 + drop fix-acceptance_test-for-pytest3.patch (solved upstream).
   * deb/control:
 + add DPMT as Uploaders.
 + update build-deps (put version for python-pytest packages).
 + update Vcs fields (Git repo moved to /git/python-modules).
 + bump standards to 4.0.0 (no changes needed).
   * deb/copyright:
 + expand copyright spans.
   * deb/gbp.conf:
 + change debian-branch to meet DEP-14.
 + add sign-tags field switched to True.
   * deb/tests/python{,3}-pytest-xdist:
 * don't stop after first failure in DEP-8 testing (remove -x).
   * use debhelper level 10 (changes in deb/control and deb/compat).
   * add temporarily-disable-test_looponfail_removed_test.patch
 (Closes: #869094).
Checksums-Sha1:
 bd27a78bdd60783053d370324ae175be03bf1af1 2426 pytest-xdist_1.18.2-1.dsc
 752c35d2be0d0f4ff8da2a63840c9e0714cd446a 40864 

Bug#870843: golang-github-armon-go-metrics-dev: unhandled symlink to directory conversion: /usr/share/gocode/src/github.com/sirupsen/logrus -> ../Sirupsen/logrus

[Andreas Beckmann]

Package: golang-github-armon-go-metrics-dev
Version: 0.0~git20170601.0.f036747-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  testing -> sid

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (scroll to the bottom...):

0m33.8s INFO: dirname part contains a symlink:
  /usr/share/gocode/src/github.com/sirupsen/logrus/alt_exit.go 
(golang-github-sirupsen-logrus-dev) != 
/usr/share/gocode/src/github.com/Sirupsen/logrus/alt_exit.go (?)
/usr/share/gocode/src/github.com/sirupsen/logrus -> ../Sirupsen/logrus
  /usr/share/gocode/src/github.com/sirupsen/logrus/alt_exit_test.go 
(golang-github-sirupsen-logrus-dev) != 
/usr/share/gocode/src/github.com/Sirupsen/logrus/alt_exit_test.go (?)
/usr/share/gocode/src/github.com/sirupsen/logrus -> ../Sirupsen/logrus
  /usr/share/gocode/src/github.com/sirupsen/logrus/doc.go 
(golang-github-sirupsen-logrus-dev) != 
/usr/share/gocode/src/github.com/Sirupsen/logrus/doc.go (?)
/usr/share/gocode/src/github.com/sirupsen/logrus -> ../Sirupsen/logrus
  /usr/share/gocode/src/github.com/sirupsen/logrus/entry.go 
(golang-github-sirupsen-logrus-dev) != 
/usr/share/gocode/src/github.com/Sirupsen/logrus/entry.go (?)
/usr/share/gocode/src/github.com/sirupsen/logrus -> ../Sirupsen/logrus
[...]
  /usr/share/gocode/src/github.com/sirupsen/logrus/terminal_windows.go 
(golang-github-sirupsen-logrus-dev) != 
/usr/share/gocode/src/github.com/Sirupsen/logrus/terminal_windows.go (?)
/usr/share/gocode/src/github.com/sirupsen/logrus -> ../Sirupsen/logrus
  /usr/share/gocode/src/github.com/sirupsen/logrus/text_formatter.go 
(golang-github-sirupsen-logrus-dev) != 
/usr/share/gocode/src/github.com/Sirupsen/logrus/text_formatter.go (?)
/usr/share/gocode/src/github.com/sirupsen/logrus -> ../Sirupsen/logrus
  /usr/share/gocode/src/github.com/sirupsen/logrus/text_formatter_test.go 
(golang-github-sirupsen-logrus-dev) != 
/usr/share/gocode/src/github.com/Sirupsen/logrus/text_formatter_test.go (?)
/usr/share/gocode/src/github.com/sirupsen/logrus -> ../Sirupsen/logrus
  /usr/share/gocode/src/github.com/sirupsen/logrus/writer.go 
(golang-github-sirupsen-logrus-dev) != 
/usr/share/gocode/src/github.com/Sirupsen/logrus/writer.go (?)
/usr/share/gocode/src/github.com/sirupsen/logrus -> ../Sirupsen/logrus


cheers,

Andreas


golang-github-armon-go-metrics-dev_0.0~git20170601.0.f036747-1.log.gz
Description: application/gzip

Bug#869094: marked as pending

[Daniel Stender]

tag 869094 pending
thanks

Hello,

Bug #869094 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/python-modules/packages/pytest-xdist.git/commit/?id=868f5d6

---
commit 868f5d6e0c37f6a420e2189f21496f14ada607a3
Author: Daniel Stender 
Date:   Sat Aug 5 19:29:04 2017 +0200

add temporarily-disable-test_looponfail_removed_test.patch

diff --git a/debian/changelog b/debian/changelog
index d1a63db..6506fe7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,8 +10,9 @@ pytest-xdist (1.15.0-4) UNRELEASED; urgency=medium
 + change debian-branch to meet DEP-14.
 + add sign-tags field switched to True.
   * use debhelper level 10 (changes in deb/control and deb/compat).
+  * add temporarily-disable-test_looponfail_removed_test.patch (Closes: 
#869094).
 
- -- Daniel Stender   Sat, 05 Aug 2017 19:16:09 +0200
+ -- Daniel Stender   Sat, 05 Aug 2017 19:28:10 +0200
 
 pytest-xdist (1.15.0-3) unstable; urgency=medium
 

Processed: Bug#867516 marked as pending

[Debian Bug Tracking System]

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

> tag 867516 pending
Bug #867516 [src:pytest-xdist] pytest-xdist FTBFS with python 3.6 as supported 
version
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#867516: marked as pending

[Daniel Stender]

tag 867516 pending
thanks

Hello,

Bug #867516 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/python-modules/packages/pytest-xdist.git/commit/?id=cddf44e

---
commit cddf44ea0ffdf8f4a7fc005023073452a90da60f
Author: Daniel Stender 
Date:   Sat Aug 5 19:47:43 2017 +0200

deb/changelog: add another bug to close

diff --git a/debian/changelog b/debian/changelog
index 39f1ffa..8c310ef 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
 pytest-xdist (1.18.2-1) UNRELEASED; urgency=medium
 
-  * New upstream release (Closes: #864360):
+  * New upstream release (Closes: #864360, #867516):
 + drop fix-acceptance_test-for-pytest3.patch (solved upstream).
   * deb/control:
 + add DPMT as Uploaders.
@@ -16,7 +16,7 @@ pytest-xdist (1.18.2-1) UNRELEASED; urgency=medium
   * use debhelper level 10 (changes in deb/control and deb/compat).
   * add temporarily-disable-test_looponfail_removed_test.patch (Closes: 
#869094).
 
- -- Daniel Stender   Sat, 05 Aug 2017 19:43:41 +0200
+ -- Daniel Stender   Sat, 05 Aug 2017 19:46:43 +0200
 
 pytest-xdist (1.15.0-3) unstable; urgency=medium
 

Processed: Bug#869094 marked as pending

[Debian Bug Tracking System]

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

> tag 869094 pending
Bug #869094 [src:pytest-xdist] pytest-xdist: 
TestLooponFailing::test_looponfail_removed_test FAILED
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#870841: obs-server: fails to install: ln: failed to create symbolic link '/etc/systemd/system/multi-user.target.wants/obsscheduler@i586.service': No such file or directory

[Andreas Beckmann]

Package: obs-server
Version: 2.7.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package obs-server.
  (Reading database ... 
(Reading database ... 9640 files and directories currently installed.)
  Preparing to unpack .../obs-server_2.7.4-1_all.deb ...
  Unpacking obs-server (2.7.4-1) ...
  Setting up obs-server (2.7.4-1) ...
  ln: failed to create symbolic link 
'/etc/systemd/system/multi-user.target.wants/obsscheduler@i586.service': No 
such file or directory
  dpkg: error processing package obs-server (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   obs-server


cheers,

Andreas


obs-server_2.7.4-1.log.gz
Description: application/gzip

Bug#870043: marked as done (ruby-psych FTBFS: It seems your ruby installation is missing psych (for YAML output).)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 18:38:07 +0100
with message-id <20170805173807.ga28...@alice.nomadium.lan>
and subject line Re: ruby-psych FTBFS: It seems your ruby installation is 
missing psych (for YAML output).
has caused the Debian Bug report #870043,
regarding ruby-psych FTBFS: It seems your ruby installation is missing psych 
(for YAML output).
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.)


-- 
870043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-psych
Version: 2.2.4-2
Severity: serious

https://buildd.debian.org/status/package.php?p=ruby-psych=sid

...
dh_auto_clean
dh_ruby --clean
   dh_ruby --clean
jruby -S rake clean
/usr/share/jruby/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in 
`require':
It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.
rake aborted!
LoadError: no such file to load -- psych
/<>/Rakefile:1:in `(root)'
/<>/Rakefile:13:in `block in (root)'
(See full trace by running task with --trace)
debian/rules:24: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-psych
Source-Version: 2.2.4-3

On Sat, Jul 29, 2017 at 11:30:50AM +0300, Adrian Bunk wrote:
> Source: ruby-psych
> Version: 2.2.4-2
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=ruby-psych=sid
> 
> ...
> dh_auto_clean
>   dh_ruby --clean
>dh_ruby --clean
> jruby -S rake clean
> /usr/share/jruby/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in 
> `require':
> It seems your ruby installation is missing psych (for YAML output).
> To eliminate this warning, please install libyaml and reinstall your ruby.
> rake aborted!
> LoadError: no such file to load -- psych
> /<>/Rakefile:1:in `(root)'
> /<>/Rakefile:13:in `block in (root)'
> (See full trace by running task with --trace)
> debian/rules:24: recipe for target 'override_dh_auto_clean' failed
> make[1]: *** [override_dh_auto_clean] Error 1
> 

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature
--- End Message ---

Bug#870838: sugar-write-activity: Please fix depends on abiword gir package

[Jeremy Bicha]

Package: sugar-write-activity
Version: 98-1
Severity: serious

Please depend on gir1.2-abi-3.0 instead of gir1.2-abiword-3.0 since
the package was renamed to fix a lintian warning.

Thanks,
Jeremy Bicha

Bug#841624: libcdio: FTBFS: ../../include/cdio/iso9660.h:277:45: error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'

[Andreas Metzler]

On 2016-10-21 Lucas Nussbaum  wrote:
> Source: libcdio
> Version: 0.83-4.2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161021 qa-ftbfs
> Justification: FTBFS on amd64

> Hi,

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


This seems to be fixed in experimental's 0.92. Afaict this was fixed in
http://git.savannah.gnu.org/gitweb/?p=libcdio.git;a=commitdiff;h=0bdb015d47b95abaa79fc2b83ffacdd63429a992
with
diff --git a/include/cdio/iso9660.h b/include/cdio/iso9660.h
index 45ece74..942c52d 100644 (file)
--- a/include/cdio/iso9660.h
+++ b/include/cdio/iso9660.h
@@ -60,7 +60,7 @@ typedef uint64_t iso733_t; /*! See section 7.3.3 */
 typedef char achar_t;  /*! See section 7.4.1 */
 typedef char dchar_t;  /*! See section 7.4.1 */
 
-#ifndef  EMPTY_ARRAY_SIZE
+#ifndef EMPTY_ARRAY_SIZE
 #define EMPTY_ARRAY_SIZE 0
 #endif
 
@@ -273,8 +273,18 @@ struct iso9660_dir_s {
   the Extent described by this
   Directory Record is
   recorded. (9.1.9) */
-  iso711_t filename_len;  /*! number of bytes in filename field */
-  char filename[EMPTY_ARRAY_SIZE];
+/*! MSVC compilers cannot handle a zero sized array in the middle
+of a struct, and iso9660_dir_s is reused within iso9660_pvd_s.
+Therefore, instead of defining:
+   iso711_t filename_len;
+   char filename[];
+we leverage the fact that iso711_t and char are the same size
+and use an union. The only gotcha is that the actual string
+payload of filename.str[] starts at 1, not 0. */
+  union { 
+iso711_tlen;
+charstr[1];
+  } filename;
 } GNUC_PACKED;
 
 /*! 

and the related changes.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#853555: marked as done (mongo-tools: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2017 20:21:44 +0300
with message-id <20170805172144.jodcezniaimxcfwv@localhost>
and subject line mongo-tools builds with gcc 7
has caused the Debian Bug report #853555,
regarding mongo-tools: 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.)


-- 
853555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mongo-tools
Version: 3.2.11-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/mongo-tools_3.2.11-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

[...]
gopkg.in/mgo.v2/internal/scram
gopkg.in/mgo.v2/internal/sasl
github.com/spacemonkeygo/spacelog
golang.org/x/crypto/ssh/terminal
github.com/howeyc/gopass
github.com/mongodb/mongo-tools/common/password
github.com/spacemonkeygo/openssl
# github.com/spacemonkeygo/openssl
_build/src/github.com/spacemonkeygo/openssl/bio.go:313:18: call of non-function 
C.BIO_s_readBio
gopkg.in/mgo.v2/bson
github.com/mongodb/mongo-tools/common/util
gopkg.in/mgo.v2
github.com/mongodb/mongo-tools/common/json
github.com/mongodb/mongo-tools/common/signals
github.com/mongodb/mongo-tools/common/bsonutil
github.com/mongodb/mongo-tools/common/intents
github.com/spacemonkeygo/openssl
github.com/mongodb/mongo-tools/common/text
github.com/mongodb/mongo-tools/common/progress
# github.com/spacemonkeygo/openssl
_build/src/github.com/spacemonkeygo/openssl/bio.go:313:18: call of non-function 
C.BIO_s_readBio
github.com/spacemonkeygo/openssl
# github.com/spacemonkeygo/openssl
_build/src/github.com/spacemonkeygo/openssl/bio.go:313:18: call of non-function 
C.BIO_s_readBio
github.com/spacemonkeygo/openssl
# github.com/spacemonkeygo/openssl
_build/src/github.com/spacemonkeygo/openssl/bio.go:313:18: call of non-function 
C.BIO_s_readBio
github.com/spacemonkeygo/openssl
github.com/mongodb/mongo-tools/mongoimport/csv
gopkg.in/tomb.v2
# github.com/spacemonkeygo/openssl
_build/src/github.com/spacemonkeygo/openssl/bio.go:313:18: call of non-function 
C.BIO_s_readBio
github.com/spacemonkeygo/openssl
# github.com/spacemonkeygo/openssl
_build/src/github.com/spacemonkeygo/openssl/bio.go:313:18: call of non-function 
C.BIO_s_readBio
github.com/spacemonkeygo/openssl
# github.com/spacemonkeygo/openssl
_build/src/github.com/spacemonkeygo/openssl/bio.go:313:18: call of non-function 
C.BIO_s_readBio
github.com/spacemonkeygo/openssl
# github.com/spacemonkeygo/openssl
_build/src/github.com/spacemonkeygo/openssl/bio.go:313:18: call of non-function 
C.BIO_s_readBio
github.com/spacemonkeygo/openssl
# github.com/spacemonkeygo/openssl
_build/src/github.com/spacemonkeygo/openssl/bio.go:313:18: call of non-function 
C.BIO_s_readBio
debian/rules:41: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:23: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
mongo-tools builds with gcc 7:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mongo-tools.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#868972: marked as done (alembic: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 17:19:06 +
with message-id 
and subject line Bug#868972: fixed in alembic 0.8.8-3
has caused the Debian Bug report #868972,
regarding alembic: FTBFS: Test failures
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.)


-- 
868972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alembic
Version: 0.8.8-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 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):
> 
> tests/test_oracle.py::OpTest::()::test_alter_column_rename_oracle
>   /<>/alembic/util/langhelpers.py:122: UserWarning: Argument 
> 'name' is now named 'new_column_name' for method alter_column().
> oldname, newname, fn_name
> 
> tests/test_oracle.py::OpTest::()::test_alter_do_everything
>   /<>/alembic/util/langhelpers.py:122: UserWarning: Argument 
> 'name' is now named 'new_column_name' for method alter_column().
> oldname, newname, fn_name
> 
> tests/test_sqlite.py::SQLiteTest::()::test_add_column_implicit_constraint
>   /<>/alembic/util/messaging.py:69: UserWarning: Skipping 
> unsupported ALTER for creation of implicit constraint
> warnings.warn(msg)
> 
> -- Docs: http://doc.pytest.org/en/latest/warnings.html
>  2 failed, 805 passed, 160 skipped, 17 warnings in 6.18 seconds 
> 
> debian/rules:20: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/alembic_0.8.8-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: alembic
Source-Version: 0.8.8-3

We believe that the bug you reported is fixed in the latest version of
alembic, 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 868...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated alembic 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: Sat, 05 Aug 2017 18:57:50 +0200
Source: alembic
Binary: alembic python-alembic python3-alembic
Architecture: source
Version: 0.8.8-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 alembic- lightweight database migration tool for SQLAlchemy
 python-alembic - lightweight database migration tool for SQLAlchemy - Python 
2.x
 python3-alembic - lightweight database migration tool for SQLAlchemy - Python 
3.x
Closes: 868972
Changes:
 alembic (0.8.8-3) unstable; urgency=medium
 .
   * Maintainer: DPMT team
   * Vcs-* move to DPMT
   * Standards-Version is 4.0.0 now
   * d/copyright
 - Use https in format URL
 - Bump my copyright years
   * Use pybuild
   * Remove openstack-pkg-tools from B-D, not needed anymore
   * Fix FTBFS with Python 3.6 (Closes: #868972)
   * Remove alternatives for alembic CLI and always use Python 3 version
   * d/s/options: Remove extend-diff-ignore of .gitreview
   * Use autopkgtest-pkg-python testsuite and test alembic CLI
   * Refresh manpage
Checksums-Sha1:
 748d04ffa1c5e91dd1fdac9a726f1cdf9a0164e5 2466 alembic_0.8.8-3.dsc
 ced74c38a18a5849f813cf32034665b080e6e610 7372 alembic_0.8.8-3.debian.tar.xz
 98a2f5e96522f711b737862a6008bd2434b5 8187 alembic_0.8.8-3_amd64.buildinfo
Checksums-Sha256:
 2320465f1796369c00546588443909187cef778f2830a14ed299680cfc527894 2466 
alembic_0.8.8-3.dsc
 1ce33787c281b9b278c1718a9d32f94d564ac812bc37c8208f242bbaaacf277b 7372 
alembic_0.8.8-3.debian.tar.xz
 c45e18c85f85eb8205c9d57c5a969d67ee4eba2573ead53fb272628d3bc330cc 8187 

Processed: tagging 853427

[Debian Bug Tracking System]

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

> tags 853427 + pending
Bug #853427 [src:gnurobbo] gnurobbo: ftbfs with GCC-7
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: /usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: error: no previous prototype for '_regress_test_fundamental_hidden_sub_object_get_type'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:pygobject
Bug #870837 [src:gobject-introspection] 
/usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: error: no previous 
prototype for '_regress_test_fundamental_hidden_sub_object_get_type'
Added indication that 870837 affects src:pygobject

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

Bug#870837: /usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: error: no previous prototype for '_regress_test_fundamental_hidden_sub_object_get_type'

[Adrian Bunk]

Source: gobject-introspection
Version: 1.53.2-4
Severity: serious
Control: affects -1 src:pygobject

pygobject FTBFS:

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

...
/usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: error: no previous 
prototype for '_regress_test_fundamental_hidden_sub_object_get_type' 
[-Werror=missing-prototypes]
   _regress_test_fundamental_hidden_sub_object_get_type
   ^
/usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: note: in 
definition of macro 'regress_test_fundamental_hidden_sub_object_get_type'
   _regress_test_fundamental_hidden_sub_object_get_type
   ^~~~
/usr/include/glib-2.0/gobject/gtype.h:1994:3: note: in expansion of macro 
'_G_DEFINE_TYPE_EXTENDED_BEGIN_PRE'
   _G_DEFINE_TYPE_EXTENDED_BEGIN_PRE(TypeName, type_name, TYPE_PARENT) \
   ^
/usr/include/glib-2.0/gobject/gtype.h:1737:60: note: in expansion of macro 
'_G_DEFINE_TYPE_EXTENDED_BEGIN'
 #define G_DEFINE_TYPE_EXTENDED(TN, t_n, T_P, _f_, _C_) 
_G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, _f_) {_C_;} 
_G_DEFINE_TYPE_EXTENDED_END()

^
/usr/include/glib-2.0/gobject/gtype.h:1595:43: note: in expansion of macro 
'G_DEFINE_TYPE_EXTENDED'
 #define G_DEFINE_TYPE(TN, t_n, T_P)   G_DEFINE_TYPE_EXTENDED (TN, t_n, 
T_P, 0, {})
   ^~
/usr/share/gobject-introspection-1.0/tests/regress.c:3456:1: note: in expansion 
of macro 'G_DEFINE_TYPE'
 G_DEFINE_TYPE (RegressTestFundamentalHiddenSubObject,
 ^
cc1: some warnings being treated as errors
...


This is only a FTBFS due to -Werror, but it looks like a bug in
gobject-introspection that should be fixed (and this is also a
warning when building src:gobject-introspection).

Bug#870834: lua-lgi FTBFS: test failures

[Adrian Bunk]

Source: lua-lgi
Version: 0.9.1-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes lua-lgi FTBFS:

https://tests.reproducible-builds.org/debian/history/lua-lgi.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lua-lgi.html

...
Making target test for debian/lua5.1.dh-lua.conf
# tests
Copying lgi.lua lgi/package.lua lgi/init.lua lgi/component.lua lgi/log.lua 
lgi/core.lua lgi/class.lua lgi/version.lua lgi/namespace.lua lgi/record.lua 
lgi/enum.lua lgi/ffi.lua lgi/override/GLib-Source.lua 
lgi/override/GObject-Object.lua lgi/override/GLib.lua lgi/override/Clutter.lua 
lgi/override/Pango.lua lgi/override/GObject-Type.lua 
lgi/override/GLib-Markup.lua lgi/override/GLib-Bytes.lua 
lgi/override/GLib-Timer.lua lgi/override/Gio.lua 
lgi/override/GObject-Closure.lua lgi/override/Gtk.lua lgi/override/Gdk.lua 
lgi/override/cairo.lua lgi/override/Gst.lua lgi/override/GObject-Value.lua 
lgi/override/GLib-Error.lua lgi/override/Gio-DBus.lua 
lgi/override/GLib-Variant.lua lgi/override/PangoCairo.lua in 
/build/1st/lua-lgi-0.9.1/5.1-lgi for test
** lua dynamic (5.1) *
Test: tests/test.lua
gireg   : 94:obj_create FAIL
 ...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: bad 
argument #4 to 'object_new' (table expected, got nil)
stack traceback:
[C]: in function 'object_new'
...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: in 
function <...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:52>
(tail call): ?
(tail call): ?
tests/gireg.lua:1112: in function 
[C]: in function 'xpcall'
tests/test.lua:50: in function 'runfunc'
tests/test.lua:73: in function 'run'
tests/test.lua:141: in main chunk
[C]: ?
gireg   : 95:obj_methodsFAIL
 ...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: bad 
argument #4 to 'object_new' (table expected, got nil)
stack traceback:
[C]: in function 'object_new'
...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: in 
function <...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:52>
(tail call): ?
(tail call): ?
tests/gireg.lua:1131: in function 
[C]: in function 'xpcall'
tests/test.lua:50: in function 'runfunc'
tests/test.lua:73: in function 'run'
tests/test.lua:141: in main chunk
[C]: ?
gireg   : 97:obj_virtual_methodsFAIL
 ...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: bad 
argument #4 to 'object_new' (table expected, got nil)
stack traceback:
[C]: in function 'object_new'
...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: in 
function <...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:52>
(tail call): ?
(tail call): ?
tests/gireg.lua:1159: in function 
[C]: in function 'xpcall'
tests/test.lua:50: in function 'runfunc'
tests/test.lua:73: in function 'run'
tests/test.lua:141: in main chunk
[C]: ?
gireg   : 98:obj_prop_int   FAIL
 ...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: bad 
argument #4 to 'object_new' (table expected, got nil)
stack traceback:
[C]: in function 'object_new'
...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: in 
function <...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:52>
(tail call): ?
(tail call): ?
tests/gireg.lua:1165: in function 
[C]: in function 'xpcall'
tests/test.lua:50: in function 'runfunc'
tests/test.lua:73: in function 'run'
tests/test.lua:141: in main chunk
[C]: ?
gireg   : 99:obj_prop_float FAIL
 ...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: bad 
argument #4 to 'object_new' (table expected, got nil)
stack traceback:
[C]: in function 'object_new'
...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: in 
function <...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:52>
(tail call): ?
(tail call): ?
tests/gireg.lua:1178: in function 
[C]: in function 'xpcall'
tests/test.lua:50: in function 'runfunc'
tests/test.lua:73: in function 'run'
tests/test.lua:141: in main chunk
[C]: ?
gireg   :100:obj_prop_doubleFAIL
 ...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: bad 
argument #4 to 'object_new' (table expected, got nil)
stack traceback:
[C]: in function 'object_new'
...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:100: in 
function <...ua-lgi-0.9.1/5.1-lgi/lgi/override/GObject-Object.lua:52>
(tail call): ?
(tail call): ?
tests/gireg.lua:1191: in function 
[C]: in function 'xpcall'
tests/test.lua:50: in function 

Bug#853297: marked as done (abinit: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 17:04:25 +
with message-id 
and subject line Bug#853297: fixed in abinit 8.0.8-2
has caused the Debian Bug report #853297,
regarding abinit: 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.)


-- 
853297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:abinit
Version: 8.0.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/abinit_8.0.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.

  apt-get -t=experimental install g++ 

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

[...]
gfortran -DHAVE_CONFIG_H -I. -I../..  -I../../src/54_abiutil 
-I../../src/54_abiutil -I../../src/61_ionetcdf -I../../src/61_ionetcdf 
-I../../src/27_toolbox_oop -I../../src/27_toolbox_oop -I../../src/42_libpaw 
-I../../src/42_libpaw -I../../src/65_paw -I../../src/65_paw 
-I../../src/62_wvl_wfs -I../../src/62_wvl_wfs -I../../src/66_nonlocal 
-I../../src/66_nonlocal -I../../src/45_geomoptim -I../../src/45_geomoptim 
-I../../src/49_gw_toolbox_oop -I../../src/49_gw_toolbox_oop 
-I../../src/62_iowfdenpot -I../../src/62_iowfdenpot -I../../src/18_timing 
-I../../src/18_timing -I../../src/12_hide_mpi -I../../src/12_hide_mpi 
-I../../src/56_mixing -I../../src/56_mixing -I../../src/56_io_mpi 
-I../../src/56_io_mpi -I../../src/14_hidewrite -I../../src/14_hidewrite 
-I../../src/20_datashare -I../../src/20_datashare -I../../src/64_psp 
-I../../src/64_psp -I../../src/32_util -I../../src/32_util 
-I../../src/28_numeric_noabirule -I../../src/28_numeric_noabirule 
-I../../src/44_abitypes_defs -I../../src/44_abityp
 es_defs -I../../src/51_manage_mpi -I../../src/51_manage_mpi 
-I../../src/43_wvl_wrappers -I../../src/43_wvl_wrappers -I../../src/62_poisson 
-I../../src/62_poisson -I../../src/16_hideleave -I../../src/16_hideleave 
-I../../src/56_recipspace -I../../src/56_recipspace -I../../src/61_occeig 
-I../../src/61_occeig -I../../src/52_fft_mpi_noabirule 
-I../../src/52_fft_mpi_noabirule -I../../src/56_xc -I../../src/56_xc 
-I../../src/66_wfs -I../../src/66_wfs -I../../src/41_xc_lowlevel 
-I../../src/41_xc_lowlevel -I../../src/41_geometry -I../../src/41_geometry 
-I../../src/01_linalg_ext -I../../src/01_linalg_ext -I../../src/53_spacepar 
-I../../src/53_spacepar -I../../src/11_memory_mpi -I../../src/11_memory_mpi 
-I../../src/10_defs -I../../src/10_defs -I../../src/53_ffts -I../../src/53_ffts 
-I../../src/incs -I../../src/incs -I/<>/fallbacks/exports/include  
 -ffree-form -J/<>/src/mods  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -c -o 
make_grad_berry.o
  make_grad_berry.F90
gfortran -DHAVE_CONFIG_H -I. -I../..  -I../../src/54_abiutil 
-I../../src/54_abiutil -I../../src/61_ionetcdf -I../../src/61_ionetcdf 
-I../../src/27_toolbox_oop -I../../src/27_toolbox_oop -I../../src/42_libpaw 
-I../../src/42_libpaw -I../../src/65_paw -I../../src/65_paw 
-I../../src/62_wvl_wfs -I../../src/62_wvl_wfs -I../../src/66_nonlocal 
-I../../src/66_nonlocal -I../../src/45_geomoptim -I../../src/45_geomoptim 
-I../../src/49_gw_toolbox_oop -I../../src/49_gw_toolbox_oop 
-I../../src/62_iowfdenpot -I../../src/62_iowfdenpot -I../../src/18_timing 
-I../../src/18_timing -I../../src/12_hide_mpi -I../../src/12_hide_mpi 
-I../../src/56_mixing -I../../src/56_mixing -I../../src/56_io_mpi 
-I../../src/56_io_mpi -I../../src/14_hidewrite -I../../src/14_hidewrite 
-I../../src/20_datashare -I../../src/20_datashare -I../../src/64_psp 
-I../../src/64_psp -I../../src/32_util 

Bug#870832: libmath-prime-util-gmp-perl FTBFS on big endian: Failed 2/31 test programs. 8/2885 subtests failed.

[Adrian Bunk]

Source: libmath-prime-util-gmp-perl
Version: 0.46-1
Severity: serious

https://buildd.debian.org/status/package.php?p=libmath-prime-util-gmp-perl=sid

...
Test Summary Report
---
t/28-randomprime.t (Wstat: 1536 Tests: 181 Failed: 6)
  Failed tests:  176-181
  Non-zero exit status: 6
t/28-urandom.t (Wstat: 512 Tests: 46 Failed: 2)
  Failed tests:  44-45
  Non-zero exit status: 2
Files=31, Tests=2885, 38 wallclock secs ( 1.56 usr  0.20 sys + 36.32 cusr  0.82 
csys = 38.90 CPU)
Result: FAIL
Failed 2/31 test programs. 8/2885 subtests failed.
Makefile:1089: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255

Bug#853397: marked as done (fcgiwrap: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2017 16:50:17 +
with message-id 
and subject line Bug#853397: fixed in fcgiwrap 1.1.0-10
has caused the Debian Bug report #853397,
regarding fcgiwrap: 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.)


-- 
853397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fcgiwrap
Version: 1.1.0-9
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for pid_t... yes
checking for size_t... yes
checking for ssize_t... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking whether lstat correctly handles trailing slash... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for strchr... yes
checking for strdup... yes
checking for strrchr... yes
checking for dup2... yes
checking for putenv... yes
checking for select... yes
checking for setenv... yes
checking for strerror... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
cc -std=gnu99 -Wall -Wextra -Werror -pedantic -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now 
 fcgiwrap.c  -lfcgi -lsystemd -o fcgiwrap
fcgiwrap.c: In function 'handle_fcgi_request':
fcgiwrap.c:573:4: error: this statement may fall through 
[-Werror=implicit-fallthrough=]
cgi_error("502 Bad Gateway", "Cannot execute script", filename);
^~~
fcgiwrap.c:575:3: note: here
   default: /* parent */
   ^~~
cc1: all warnings being treated as errors
: recipe for target 'fcgiwrap' failed
make[1]: *** [fcgiwrap] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:6: 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: fcgiwrap
Source-Version: 1.1.0-10

We believe that the bug you reported is fixed in the latest version of
fcgiwrap, 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,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Colberg  (supplier of updated fcgiwrap 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