Bug#957914: marked as done (viking: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 05:33:31 +
with message-id 
and subject line Bug#957914: fixed in viking 1.8-3
has caused the Debian Bug report #957914,
regarding viking: ftbfs with GCC-10
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.)


-- 
957914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:viking
Version: 1.7-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/viking_1.7-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
 from misc/gtkhtml-private.h:27,
 from misc/gtkhtml.c:24:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
rm -f libviking.a
ar cru libviking.a modules.o curl_download.o compression.o degrees_converters.o 
globals.o viktrwlayer.o vik_compat.o viktrack.o vikwaypoint.o clipboard.o 
coords.o gpsmapper.o gpspoint.o geojson.o dir.o file.o fileutils.o file_magic.o 
dialog.o util.o ui_util.o download.o jpg.o vikenumtypes.o viktreeview.o 
viklayer.o viklayerspanel.o vikcoordlayer.o vikstatus.o vikwindow.o 
vikviewport.o vikaggregatelayer.o vikgobjectbuilder.o vikgpslayer.o 
vikgeoreflayer.o vikfileentry.o vikgototool.o vikgotoxmltool.o vikgoto.o 
viktrwlayer_export.o viktrwlayer_tpwin.o viktrwlayer_wpwin.o 
viktrwlayer_propwin.o viktrwlayer_analysis.o viktrwlayer_tracklist.o 
viktrwlayer_waypointlist.o vikrouting.o vikroutingengine.o 
vikroutingwebengine.o vikutils.o toolbar.o thumbnails.o md5_hash.o background.o 
vikradiogroup.o vikcoord.o mapcache.o maputils.o vikmapsource.o 
vikmapsourcedefault.o vikmapslayer.o vikmapslayer_compat.o vikmaptype.o 
vikslippymapsource.o vikwmscmapsource.o viktmsmapsource.o metatile.o gpx.o gar
 minsymbols.o acquire.o babel.o babel_ui.o datasource_file.o 
datasource_geojson.o datasource_gps.o datasource_routing.o datasource_gc.o 
datasource_bfilter.o datasource_wikipedia.o datasource_url.o googlesearch.o 
dem.o vikdemlayer.o vikdatetime_edit_dialog.o vikfilelist.o vikexttool.o 
vikexttools.o vikwebtool.o vikwebtoolcenter.o vikwebtoolbounds.o 
vikwebtoolformat.o vikexttool_datasources.o vikwebtool_datasource.o dems.o 
srtm_continent.o uibuilder.o print-preview.o print.o kmz.o viklayer_defaults.o 
settings.o preferences.o misc/fpconv.o misc/strtod.o misc/kdtree.o 
misc/gtkhtml.o bingmapsource.o bing.o google.o   osm.o osm-traces.o 
datasource_osm_my_traces.o datasource_osm.o bluemarble.o geonames.o 
geonamessearch.o datasource_geotag.o geotag_exif.o viktrwlayer_geotag.o  
vikmapniklayer.o mapnik_interface.o libgeoclue.o 
ar: `u' modifier ignored since `D' is the default (see `U')
ranlib libviking.a
gcc -Wall -g -D_GNU_SOURCE -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/libgeoclue-2.0 -I/usr/include/gio-unix-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 

Bug#964810: gimp: Unable to start gimp in debian unstable

[felipe]

After investigating further, I found the problematic package to be 
mesa-opencl-icd.

After removing the package above, gimp works again.

Bug#957518: marked as done (makedumpfile: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 02:34:55 +
with message-id 
and subject line Bug#957518: fixed in makedumpfile 1:1.6.7-3
has caused the Debian Bug report #957518,
regarding makedumpfile: ftbfs with GCC-10
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.)


-- 
957518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:makedumpfile
Version: 1:1.6.6-4
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/makedumpfile_1.6.6-4_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
dh clean --with=systemd
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
rm -f debian/kdump-tools.maintscript
rm -f debian/kdump-config debian/kdump-tools.conf debian/kdump-tools.5
dh_auto_clean
make -j1 clean
make[2]: Entering directory '/<>'
rm -f  print_info.o dwarf_info.o elf_info.o erase_info.o sadump_info.o cache.o 
tools.o arch/arm.o arch/arm64.o arch/x86.o arch/x86_64.o arch/ia64.o 
arch/ppc64.o arch/s390x.o arch/ppc.o arch/sparc64.o makedumpfile
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_clean
 debian/rules binary
dh binary --with=systemd
   dh_update_autotools_config
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- LINKTYPE=dynamic USELZO=on
make -j1 LINKTYPE=dynamic USELZO=on
make[2]: Entering directory '/<>'
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -Wall -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVERSION='"1.6.6"' 
-DRELEASE_DATE='"27 Jun 2019"' -D__x86_64__  -DUSELZO -c -o ./print_info.o 
print_info.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -Wall -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVERSION='"1.6.6"' 
-DRELEASE_DATE='"27 Jun 2019"' -D__x86_64__  -DUSELZO -c -o ./dwarf_info.o 
dwarf_info.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -Wall -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVERSION='"1.6.6"' 
-DRELEASE_DATE='"27 Jun 2019"' -D__x86_64__  -DUSELZO -c -o ./elf_info.o 
elf_info.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -Wall -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVERSION='"1.6.6"' 
-DRELEASE_DATE='"27 Jun 2019"' -D__x86_64__  -DUSELZO -c -o ./erase_info.o 
erase_info.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -Wall -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVERSION='"1.6.6"' 
-DRELEASE_DATE='"27 Jun 2019"' -D__x86_64__  -DUSELZO -c -o ./sadump_info.o 
sadump_info.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -Wall -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVERSION='"1.6.6"' 
-DRELEASE_DATE='"27 Jun 2019"' -D__x86_64__  -DUSELZO -c -o ./cache.o cache.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -Wall -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVERSION='"1.6.6"' 
-DRELEASE_DATE='"27 Jun 2019"' -D__x86_64__  -DUSELZO -c -o ./tools.o tools.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat 

Bug#966475: rspamd ftbfs with gcc-10

[Steve Langasek]

Package: rspamd
Version: 2.5-2
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy ubuntu-patch

Dear maintainers,

In Ubuntu, we've found that rspamd fails to build from source with the
current toolchain due to a missing C++ include file.  The attached patch
fixes the build failure in unstable.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru rspamd-2.5/debian/patches/gcc10-ftbfs.patch 
rspamd-2.5/debian/patches/gcc10-ftbfs.patch
--- rspamd-2.5/debian/patches/gcc10-ftbfs.patch 1969-12-31 16:00:00.0 
-0800
+++ rspamd-2.5/debian/patches/gcc10-ftbfs.patch 2020-07-28 16:51:48.0 
-0700
@@ -0,0 +1,16 @@
+Description: fix ftbfs with gcc 10 due to missing C++ header include
+Author: Steve Langasek 
+Last-Update: 2020-07-28
+
+Index: rspamd-2.5/contrib/replxx/src/io.cxx
+===
+--- rspamd-2.5.orig/contrib/replxx/src/io.cxx
 rspamd-2.5/contrib/replxx/src/io.cxx
+@@ -3,6 +3,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #ifdef _WIN32
+ 
diff -Nru rspamd-2.5/debian/patches/series rspamd-2.5/debian/patches/series
--- rspamd-2.5/debian/patches/series2020-05-01 07:40:43.0 -0700
+++ rspamd-2.5/debian/patches/series2020-07-28 16:49:55.0 -0700
@@ -3,3 +3,4 @@
 0004-drop-js-scripts-packaged-by-Debian.patch
 0006-do-not-install-fonts-packaged-by-Debian.patch
 0007-license-problem-convert-utf-code.patch
+gcc10-ftbfs.patch

Bug#966424: marked as done (inxi: Running latest sid version I get many "Global symbol (did you forget to declare " errors)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 23:07:06 +
with message-id 
and subject line Bug#966424: fixed in inxi 3.1.05-2-1
has caused the Debian Bug report #966424,
regarding inxi: Running latest sid version I get many "Global symbol (did you 
forget to declare " errors
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.)


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

Dear maintainer,

Running inxi I get:

$ inxi -F
Global symbol "%row" requires explicit package name (did you forget to declare 
"my %row"?) at /bin/inxi line 8749.
[...]
Global symbol "@rows" requires explicit package name (did you forget to declare 
"my @rows"?) at /bin/inxi line 8817.
Global symbol "$smartctl_missing" requires explicit package name (did you 
forget to declare "my $smartctl_missing"?) at /bin/inxi line 8856.
Global symbol "@by_id" requires explicit package name (did you forget to 
declare "my @by_id"?) at /bin/inxi line 8938.
[...]
Global symbol "@by_path" requires explicit package name (did you forget to 
declare "my @by_path"?) at /bin/inxi line 8946.
Global symbol "@by_id" requires explicit package name (did you forget to 
declare "my @by_id"?) at /bin/inxi line 8999.
[...]
Global symbol "@by_path" requires explicit package name (did you forget to 
declare "my @by_path"?) at /bin/inxi line 9570.
Global symbol "@by_id" requires explicit package name (did you forget to 
declare "my @by_id"?) at /bin/inxi line 9683.
Global symbol "@vendors" requires explicit package name (did you forget to 
declare "my @vendors"?) at /bin/inxi line 9709.
[...]
Global symbol "$b_nvme" requires explicit package name (did you forget to 
declare "my $b_nvme"?) at /bin/inxi line 10049.
Global symbol "$nvme" requires explicit package name (did you forget to declare 
"my $nvme"?) at /bin/inxi line 10052.
[...]
Global symbol "$b_hddtemp" requires explicit package name (did you forget to 
declare "my $b_hddtemp"?) at /bin/inxi line 10071.
Global symbol "$hddtemp" requires explicit package name (did you forget to 
declare "my $hddtemp"?) at /bin/inxi line 10074.
[...]
Unmatched right curly bracket at /bin/inxi line 10203, at end of line
/bin/inxi has too many errors.


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

Kernel: Linux 5.4.53-toy-lxtec-amd64 (SMP w/8 CPU threads)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages inxi depends on:
ii  pciutils  1:3.7.0-2
ii  perl  5.30.3-4
ii  procps2:3.3.16-5

Versions of packages inxi recommends:
ii  bind9-dnsutils [dnsutils]  1:9.16.4-1
ii  dmidecode  3.2-3
ii  dnsutils   1:9.16.4-1
ii  file   1:5.38-5
ii  hddtemp0.3-beta15-53
ii  iproute2   5.7.0-1
ii  kmod   27+20200310-2
ii  lm-sensors 1:3.6.0-2
pn  mesa-utils 
ii  net-tools  1.60+git20180626.aebd88e-1
ii  sudo   1.9.1-2
pn  tree   
ii  usbutils   1:012-2
pn  x11-utils  
pn  x11-xserver-utils  

Versions of packages inxi suggests:
ii  curl  7.68.0-1+b1
pn  libcpanel-json-xs-perl | libjson-xs-perl  
pn  libxml-dumper-perl
ii  perl [libhttp-tiny-perl]  5.30.3-4
ii  wget  1.20.3-1+b3

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: inxi
Source-Version: 3.1.05-2-1
Done: Unit 193 

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

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated inxi 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#957924: marked as done (waylandpp: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 22:19:13 +
with message-id 
and subject line Bug#957924: fixed in waylandpp 0.2.5-2.1
has caused the Debian Bug report #957924,
regarding waylandpp: ftbfs with GCC-10
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.)


-- 
957924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:waylandpp
Version: 0.2.5-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/waylandpp_0.2.5-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
[ 59%] Building CXX object 
CMakeFiles/wayland-client-unstable++.dir/wayland-client-protocol-unstable.cpp.o
/usr/bin/c++  -Dwayland_client_unstable___EXPORTS -I/<>/include 
-I/<>/obj-x86_64-linux-gnu  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -std=gnu++11 -o 
CMakeFiles/wayland-client-unstable++.dir/wayland-client-protocol-unstable.cpp.o 
-c /<>/obj-x86_64-linux-gnu/wayland-client-protocol-unstable.cpp
In file included from /<>/include/wayland-client.hpp:38,
 from 
/<>/obj-x86_64-linux-gnu/wayland-client-protocol.hpp:9,
 from /<>/include/wayland-cursor.hpp:32,
 from /<>/src/wayland-cursor.cpp:26:
/<>/include/wayland-util.hpp: In member function ‘native_t* 
wayland::detail::basic_wrapper::c_ptr() const’:
/<>/include/wayland-util.hpp:96:22: error: ‘runtime_error’ is not 
a member of ‘std’
   96 |   throw std::runtime_error("Tried to access empty object");
  |  ^
/<>/include/wayland-util.hpp: In member function ‘native_t* 
wayland::detail::refcounted_wrapper::c_ptr() const’:
/<>/include/wayland-util.hpp:181:22: error: ‘runtime_error’ is not 
a member of ‘std’
  181 |   throw std::runtime_error("Tried to access empty object");
  |  ^
In file included from /<>/include/wayland-client.hpp:38,
 from 
/<>/obj-x86_64-linux-gnu/wayland-client-protocol-extra.hpp:9,
 from 
/<>/obj-x86_64-linux-gnu/wayland-client-protocol-extra.cpp:1:
/<>/include/wayland-util.hpp: In member function ‘native_t* 
wayland::detail::basic_wrapper::c_ptr() const’:
/<>/include/wayland-util.hpp:96:22: error: ‘runtime_error’ is not 
a member of ‘std’
   96 |   throw std::runtime_error("Tried to access empty object");
  |  ^
/<>/include/wayland-util.hpp: In member function ‘native_t* 
wayland::detail::refcounted_wrapper::c_ptr() const’:
/<>/include/wayland-util.hpp:181:22: error: ‘runtime_error’ is not 
a member of ‘std’
  181 |   throw std::runtime_error("Tried to access empty object");
  |  ^
/<>/src/wayland-cursor.cpp: In constructor 
‘wayland::cursor_theme_t::cursor_theme_t(std::string, int, wayland::shm_t)’:
/<>/src/wayland-cursor.cpp:40:16: error: ‘runtime_error’ is not a 
member of ‘std’
   40 | throw std::runtime_error("wl_cursor_theme_load failed.");
  |^
/<>/src/wayland-cursor.cpp: In member function ‘wayland::cursor_t 
wayland::cursor_theme_t::get_cursor(std::string) const’:
/<>/src/wayland-cursor.cpp:47:16: error: ‘runtime_error’ is not a 
member of ‘std’
   47 | throw std::runtime_error("wl_cursor_theme_cursor failed.");
  |^
/<>/src/wayland-cursor.cpp: In member function 

Bug#966472: bcbio: B-D biobambam2 not available in testing

[Andreas Beckmann]

Source: bcbio
Version: 1.2.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Control: block -1 with 966470

bcbio cannot be rebuilt in testing because the build-dependency biobambam2
is not in testing.


Andreas

Processed: bcbio: B-D biobambam2 not available in testing

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 966470
Bug #966472 [src:bcbio] bcbio: B-D biobambam2 not available in testing
966472 was not blocked by any bugs.
966472 was not blocking any bugs.
Added blocking bug(s) of 966472: 966470

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

Processed: bug 957866 is forwarded to https://github.com/tcsh-org/tcsh/commit/6974bc35a5cda6eab748e364bd76a860ca66968b

[Debian Bug Tracking System]

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

> forwarded 957866 
> https://github.com/tcsh-org/tcsh/commit/6974bc35a5cda6eab748e364bd76a860ca66968b
Bug #957866 [src:tcsh] tcsh: ftbfs with GCC-10
Set Bug forwarded-to-address to 
'https://github.com/tcsh-org/tcsh/commit/6974bc35a5cda6eab748e364bd76a860ca66968b'.
> thanks
Stopping processing here.

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

Processed: tagging 957866

[Debian Bug Tracking System]

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

> tags 957866 + fixed-upstream
Bug #957866 [src:tcsh] tcsh: ftbfs with GCC-10
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#957701: marked as done (postgresql-numeral: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 23:26:19 +0200
with message-id <20200728212619.ga342...@msg.df7cb.de>
and subject line Re: Bug#957701: postgresql-numeral: ftbfs with GCC-10
has caused the Debian Bug report #957701,
regarding postgresql-numeral: ftbfs with GCC-10
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.)


-- 
957701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:postgresql-numeral
Version: 1.0-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/postgresql-numeral_1.0-3_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
HOME=/sbuild-nonexistent
LANG=C.UTF-8
LC_ALL=C.UTF-8
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-9fe3764b-8bf3-4b5d-9cb8-a50277a1e3b4
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package postgresql-numeral
dpkg-buildpackage: info: source version 1.0-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Christoph Berg 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
pg_buildext checkcontrol
dh clean
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
pg_buildext clean build-%v
### clean 12 ###
make[1]: Leaving directory '/<>'
   dh_clean
 debian/rules build
dh build
   dh_update_autotools_config
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pg_buildext build build-%v
### build 12 ###
make[2]: Entering directory '/<>/build-12'
gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement 
-Werror=vla -Wendif-labels -Wmissing-format-attribute -Wformat-security 
-fno-strict-aliasing -fwrapv -fexcess-precision=standard -Wno-format-truncation 
-Wno-stringop-truncation -g -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -fno-omit-frame-pointer -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -I. -I/<> 
-I/usr/include/postgresql/12/server -I/usr/include/postgresql/internal  
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2  
-I/usr/include/mit-krb5  -c -o numeral.o /<>/numeral.c
gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement 
-Werror=vla -Wendif-labels -Wmissing-format-attribute -Wformat-security 
-fno-strict-aliasing -fwrapv -fexcess-precision=standard -Wno-format-truncation 
-Wno-stringop-truncation -g -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -fno-omit-frame-pointer -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -I. -I/<> 
-I/usr/include/postgresql/12/server -I/usr/include/postgresql/internal  
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2  
-I/usr/include/mit-krb5  -c -o numeralfuncs.o /<>/numeralfuncs.c
flex -o numerallexer.yy.c /<>/numerallexer.l
bison -d /<>/numeralparser.y
gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement 
-Werror=vla -Wendif-labels -Wmissing-format-attribute -Wformat-security 
-fno-strict-aliasing -fwrapv 

Bug#957760: marked as pending in rfdump

[Marcos Fouces]

Control: tag -1 pending

Hello,

Bug #957760 in rfdump reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/pkg-security-team/rfdump/-/commit/2db10d68e75a4490eb62f61ec88b3c64196f38a5


Add bug to close. (Closes: #957760)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/957760

Processed: Bug#957760 marked as pending in rfdump

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #957760 [src:rfdump] rfdump: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#966470: biobambam2: autopkgtest failures: Segmentation fault bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam

[Andreas Beckmann]

Package: biobambam2
Version: 2.0.164+ds-1
Severity: serious

Hi,

biobambam2 fails its autopkg tests:

https://ci.debian.net/packages/b/biobambam2/testing/amd64/

autopkgtest [17:40:54]: test run-unit-test: [---
[93m[1mTest 1[0m
/tmp/autopkgtest-lxc.hkbkydv5/downtmp/build.3IE/src/debian/tests/run-unit-test: 
line 20:   794 Segmentation fault  bamsormadup < SRR11728627.bam > 
SRR11728627.sorted.bam
autopkgtest [17:40:55]: test run-unit-test: ---]
autopkgtest [17:40:55]: test run-unit-test:  - - - - - - - - - - results - - - 
- - - - - - -
run-unit-testFAIL non-zero exit status 139

Andreas

Processed: Re: libmaus2 FTBFS (mostly 32bit): error: no matching function for call

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #934619 [src:libmaus2] libmaus2 FTBFS (mostly 32bit): error: no matching 
function for call
Severity set to 'normal' from 'serious'

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

Bug#934619: libmaus2 FTBFS (mostly 32bit): error: no matching function for call

[Andreas Beckmann]

Followup-For: Bug #934619
Control: severity -1 normal

The outdated 32-bit binaries have been removed from the archive,
so this is no longer a regression.


Andreas

Processed: Re: Bug#957914: Patch to fix linking with gcc-10

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #957914 [src:viking] viking: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#957914: Patch to fix linking with gcc-10

[Paul Gevers]

Control: tags -1 pending

Hi arnold,

On 28-07-2020 21:52, arnold metselaar wrote:
> Below and attached is a patch to make viking compile and link properly
> with gcc-10.

Awesome. Building right now.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#925745: libgtextutils is marked for autoremoval from testing

[Pierre Gruet]

Hello,

C++11 introduced references on rvalues, which basically allows to use a
non-constant reference on a temporary object (ie waiting for
affectation). Before, temporary objects could only be references by a
const reference.

Thus, from there, it becomes a problem to have two implicit conversion
operators defined in the class TextLineReader (text_line_reader.h):

operator const std::string& () const { return line_string() ; }
operator std::string() const { return line_string(); }

A call such that

TextLineReader r(...);
std::string str=r;

becomes ambiguous as the compiler could use the affectation operator of
std::string that take a const std::string& as input (thus calling the
first above operator) *or* the affectation operator of std::string that
takes a reference on a rvalue as input (thus calling the second above
operator, which returns a temporary object).

I suggest removing the second one. The first one is needed, for instance, in

const std::string& str=r;

which is non-ambiguous, whereas

std::string str=r;

and

std::string str(r);

are ambiguous and can work with either of the two implicit conversion
operators of TextLineReader.


I will prepare an upload.

Bye,
Pierre

Bug#964982: marked as done (src:biojava4-live: fails to migrate to testing for too long: maintainer built arch:all binary)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 20:37:56 +
with message-id 
and subject line Bug#964982: fixed in biojava4-live 4.2.12+dfsg-3.1
has caused the Debian Bug report #964982,
regarding src:biojava4-live: fails to migrate to testing for too long: 
maintainer built arch:all binary
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.)


-- 
964982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: biojava4-live
Version: 4.2.12+dfsg-2
Severity: serious
Control: close -1 4.2.12+dfsg-3
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:biojava4-live
in its current version in unstable has been trying to migrate for 60
days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=biojava4-live




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: biojava4-live
Source-Version: 4.2.12+dfsg-3.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated biojava4-live 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: Mon, 13 Jul 2020 21:28:31 +0200
Source: biojava4-live
Architecture: source
Version: 4.2.12+dfsg-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Paul Gevers 
Closes: 964982
Changes:
 biojava4-live (4.2.12+dfsg-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #964982)
Checksums-Sha1:
 eeda704e97af1e10040fbcf1028e4a269825d80d 2489 biojava4-live_4.2.12+dfsg-3.1.dsc
 5d32fa4d241ce1c0f2c8ebaff3cf670c65ea715b 15776 
biojava4-live_4.2.12+dfsg-3.1.debian.tar.xz
Checksums-Sha256:
 faf4a47569cd1cc46c7572b97a59243748671f1e46e3019bae31a7883a709467 2489 
biojava4-live_4.2.12+dfsg-3.1.dsc
 d6201590a2ef181415f9f6b9cde4a78f3a01052ab380a0cb8832f73d6e905f49 15776 
biojava4-live_4.2.12+dfsg-3.1.debian.tar.xz
Files:
 07f4e3e42d0040b6708aa2feb6e0efe0 2489 java optional 
biojava4-live_4.2.12+dfsg-3.1.dsc
 eef7582b381a1ac71c95e27de7bd1026 15776 java optional 
biojava4-live_4.2.12+dfsg-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl8MthQACgkQnFyZ6wW9
dQrJcAf/SJEeE6akwYiHittRGKISE7D9ZcgLlAQc8SD1Ldrab5gdtWdBanjlgTkF
P0oq7PipJHwoBTn9Vr7R3ns/xN34UNNL3l+Az+SRbFdiVS/rTpjfNS8ksSeVgYmC

Bug#957155: marked as done (dune-grid: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 22:38:12 +0200
with message-id <03352a5835f2086832b46ffeadf50da58bb8ee01.ca...@43-1.org>
and subject line Re: Bug#957155: dune-grid: ftbfs with GCC-10
has caused the Debian Bug report #957155,
regarding dune-grid: ftbfs with GCC-10
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.)


-- 
957155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dune-grid
Version: 2.6.0-5
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/dune-grid_2.6.0-5_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
  Start 61: vertexordertest
61/61 Test #61: vertexordertest ...   
Passed0.32 sec

98% tests passed, 1 tests failed out of 61

Total Test time (real) =  47.08 sec

The following tests did not run:
  6 - printgridtest (Skipped)
 11 - amirameshtest (Skipped)
 34 - test-loadbalancing (Skipped)

The following tests FAILED:
 23 - test-geogrid-yaspgrid (Failed)
Errors while running CTest
==
Name:  printgridtest
FullName:  ./dune/grid/io/file/test/printgridtest
Status:NOTRUN
Output:
   sh: 1: gnuplot: not found
   GNUplot was not found.

==
Name:  amirameshtest
FullName:  ./dune/grid/io/file/test/amirameshtest
Status:NOTRUN
Output:
   This test was skipped because it failed the following CMake 
Conditions:
 AMIRAMESH_FOUND

==
Name:  test-geogrid-yaspgrid
FullName:  ./dune/grid/test/test-geogrid-yaspgrid
Status:FAILED
Output:
   Checking grid...
   0061
   0061
   Lifetime / consistency check for entities, codim 2
   WARNING! Requested check of first 32 entities, but grid view only 
contains 25 entities
   Lifetime / consistency check for entities, codim 1
   Lifetime / consistency check for entities, codim 0
   WARNING! Requested check of first 32 entities, but grid view only 
contains 16 entities
   Intersection Lifetime / consistency check
   WARNING! Requested check of intersections for first 32 elements, but 
grid view only contains 16 elements
   Lifetime / consistency check for entities, codim 2
   WARNING! Requested check of first 32 entities, but grid view only 
contains 25 entities
   Lifetime / consistency check for entities, codim 1
   Lifetime / consistency check for entities, codim 0
   WARNING! Requested check of first 32 entities, but grid view only 
contains 16 entities
   Intersection Lifetime / consistency check
   WARNING! Requested check of intersections for first 32 elements, but 
grid view only contains 16 elements
   Checking geometry... 
   Checking geometry in father...
   Checking intersections...
   Dune::GridError 
[checkIntersectionIterator:/<>/dune/grid/test/checkintersectionit.hh:518]:
 Could not find inside entity through intersection iterator on outside entity.

==
Name:  test-loadbalancing
FullName:  ./dune/grid/test/test-loadbalancing
Status:NOTRUN
Output:
   This 

Bug#957914: Patch to fix linking with gcc-10

[arnold metselaar]

Dear maintainer,

Below and attached is a patch to make viking compile and link properly with
gcc-10.

Suggested changelog entry:

src/babel.h (a_babel_file_list, a_babel_device_list): declare global
variables as extern, closes #957914

Kind regards,
Arnold Metselaar
---

diff --git a/src/babel.h b/src/babel.h
index ae2fa959..e2c18e6c 100644
--- a/src/babel.h
+++ b/src/babel.h
@@ -109,8 +109,8 @@ typedef struct {
 gchar *label;
 } BabelFile;

-GList *a_babel_file_list;
-GList *a_babel_device_list;
+extern GList *a_babel_file_list;
+extern GList *a_babel_device_list;

 void a_babel_foreach_file_with_mode (BabelMode mode, GFunc func, gpointer
user_data);
 void a_babel_foreach_file_read_any (GFunc func, gpointer user_data);
diff --git a/src/babel.h b/src/babel.h
index ae2fa959..e2c18e6c 100644
--- a/src/babel.h
+++ b/src/babel.h
@@ -109,8 +109,8 @@ typedef struct {
 gchar *label;
 } BabelFile;
 
-GList *a_babel_file_list;
-GList *a_babel_device_list;
+extern GList *a_babel_file_list;
+extern GList *a_babel_device_list;
 
 void a_babel_foreach_file_with_mode (BabelMode mode, GFunc func, gpointer user_data);
 void a_babel_foreach_file_read_any (GFunc func, gpointer user_data);

Processed: affects 966463

[Debian Bug Tracking System]

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

> affects 966463 + src:scipy
Bug #966463 [src:openblas] openblas breaks scipy autopkgtest: 
tests/test_vq.py::TestKMean::test_krandinit Segmentation fault
Bug #966175 [src:openblas] libopenblas0-pthread: segfault in scipy tests: calls 
Haswell
Added indication that 966463 affects src:scipy
Added indication that 966175 affects src:scipy
> thanks
Stopping processing here.

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

Processed: reassign 966463 to src:openblas, reassign 966175 to src:openblas, forcibly merging 966463 966175 ...

[Debian Bug Tracking System]

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

> reassign 966463 src:openblas 0.3.10+ds-1
Bug #966463 [src:openblas, src:scipy] openblas breaks scipy autopkgtest: 
tests/test_vq.py::TestKMean::test_krandinit Segmentation fault
Bug reassigned from package 'src:openblas, src:scipy' to 'src:openblas'.
No longer marked as found in versions openblas/0.3.10+ds-1 and scipy/1.4.1-2.
Ignoring request to alter fixed versions of bug #966463 to the same values 
previously set
Bug #966463 [src:openblas] openblas breaks scipy autopkgtest: 
tests/test_vq.py::TestKMean::test_krandinit Segmentation fault
Marked as found in versions openblas/0.3.10+ds-1.
> reassign 966175 src:openblas 0.3.10+ds-1
Bug #966175 [libopenblas0-pthread] libopenblas0-pthread: segfault in scipy 
tests: calls Haswell
Bug reassigned from package 'libopenblas0-pthread' to 'src:openblas'.
No longer marked as found in versions openblas/0.3.10+ds-1.
Ignoring request to alter fixed versions of bug #966175 to the same values 
previously set
Bug #966175 [src:openblas] libopenblas0-pthread: segfault in scipy tests: calls 
Haswell
Marked as found in versions openblas/0.3.10+ds-1.
> forcemerge 966463 966175
Bug #966463 [src:openblas] openblas breaks scipy autopkgtest: 
tests/test_vq.py::TestKMean::test_krandinit Segmentation fault
Bug #966175 [src:openblas] libopenblas0-pthread: segfault in scipy tests: calls 
Haswell
Severity set to 'serious' from 'normal'
Removed indication that 966175 affects src:scipy
Added tag(s) bullseye and sid.
Merged 966175 966463
> tags 966463 + upstream fixed-upstream
Bug #966463 [src:openblas] openblas breaks scipy autopkgtest: 
tests/test_vq.py::TestKMean::test_krandinit Segmentation fault
Bug #966175 [src:openblas] libopenblas0-pthread: segfault in scipy tests: calls 
Haswell
Added tag(s) fixed-upstream and upstream.
Added tag(s) fixed-upstream and upstream.
> forwarded 966463 https://github.com/xianyi/OpenBLAS/issues/2728
Bug #966463 [src:openblas] openblas breaks scipy autopkgtest: 
tests/test_vq.py::TestKMean::test_krandinit Segmentation fault
Bug #966175 [src:openblas] libopenblas0-pthread: segfault in scipy tests: calls 
Haswell
Set Bug forwarded-to-address to 
'https://github.com/xianyi/OpenBLAS/issues/2728'.
Set Bug forwarded-to-address to 
'https://github.com/xianyi/OpenBLAS/issues/2728'.
> thanks
Stopping processing here.

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

Bug#957734: marked as done (qtwebengine-opensource-src: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 19:33:56 +
with message-id 
and subject line Bug#957734: fixed in qtwebengine-opensource-src 5.14.2+dfsg1-4
has caused the Debian Bug report #957734,
regarding qtwebengine-opensource-src: ftbfs with GCC-10
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.)


-- 
957734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qtwebengine-opensource-src
Version: 5.12.5+dfsg-7
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/qtwebengine-opensource-src_5.12.5+dfsg-7_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
[5348/14726] /usr/bin/gcc -MMD -MF 
obj/third_party/webrtc/common_audio/common_audio_c/filter_ma_fast_q12.o.d 
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 
-DUSE_OZONE=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD 
-DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD 
-DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-DWEBRTC_ENABLE_PROTOBUF=1 -DHAVE_SCTP -DENABLE_EXTERNAL_AUTH 
-DUSE_BUILTIN_SW_CODECS -DHAVE_WEBRTC_VIDEO -DHAVE_WEBRTC_VOICE 
-DLOGGING_INSIDE_WEBRTC -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 
-DGTEST_RELATIVE_PATH -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX 
-DABSL_ALLOCATOR_NOTHROW=1 -Igen -I../../3rdparty/chromium 
-I../../3rdparty/chromium/third_party/webrtc_overrides 
-I../../3rdparty/chromium/third_party/webrtc 
-I../../3rdparty/chromium/third_party/webrtc/common_audio
 /resampler/include 
-I../../3rdparty/chromium/third_party/webrtc/common_audio/signal_processing/include
 -I../../3rdparty/chromium/third_party/webrtc/common_audio/vad/include -Igen 
-Igen -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector 
-funwind-tables -fPIC -pipe -pthread -m64 -Wall -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments 
-Wno-dangling-else -Wno-packed-not-aligned -Wno-missing-field-initializers 
-Wno-unused-parameter -O2 -fno-ident -fdata-sections -ffunction-sections 
-fno-omit-frame-pointer -g0 -fvisibility=hidden -isystem 
../../3rdparty/chromium/third_party/abseil-cpp -std=gnu11 -c 
../../3rdparty/chromium/third_party/webrtc/common_audio/signal_processing/filter_ma_fast_q12.c
 -o obj/third_party/webrtc/common_audio/common_audio_c/filter_ma_fast_q12.o
[5349/14726] /usr/bin/gcc -MMD -MF 
obj/third_party/webrtc/common_audio/common_audio_c/get_hanning_window.o.d 
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 
-DUSE_OZONE=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD 
-DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD 
-DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
-DWEBRTC_ENABLE_PROTOBUF=1 -DHAVE_SCTP -DENABLE_EXTERNAL_AUTH 
-DUSE_BUILTIN_SW_CODECS -DHAVE_WEBRTC_VIDEO -DHAVE_WEBRTC_VOICE 
-DLOGGING_INSIDE_WEBRTC -DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 
-DGTEST_RELATIVE_PATH -DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX 
-DABSL_ALLOCATOR_NOTHROW=1 -Igen -I../../3rdparty/chromium 

Processed: openblas breaks scipy autopkgtest: tests/test_vq.py::TestKMean::test_krandinit Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> found -1 openblas/0.3.10+ds-1
Bug #966463 [src:openblas, src:scipy] openblas breaks scipy autopkgtest: 
tests/test_vq.py::TestKMean::test_krandinit Segmentation fault
Marked as found in versions openblas/0.3.10+ds-1.
> found -1 scipy/1.4.1-2
Bug #966463 [src:openblas, src:scipy] openblas breaks scipy autopkgtest: 
tests/test_vq.py::TestKMean::test_krandinit Segmentation fault
Marked as found in versions scipy/1.4.1-2.

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

Bug#966463: openblas breaks scipy autopkgtest: tests/test_vq.py::TestKMean::test_krandinit Segmentation fault

[Paul Gevers]

Source: openblas, scipy
Control: found -1 openblas/0.3.10+ds-1
Control: found -1 scipy/1.4.1-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of openblas the autopkgtest of scipy fails in
testing when that autopkgtest is run with the binary packages of
openblas from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
openblas   from testing0.3.10+ds-1
scipy  from testing1.4.1-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of openblas to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=openblas

https://ci.debian.net/data/autopkgtest/testing/amd64/s/scipy/6418132/log.gz

=== Testing: python3.8 scipy.cluster ===
= test session starts
==
platform linux -- Python 3.8.5, pytest-4.6.11, py-1.8.1, pluggy-0.13.0
-- /usr/bin/python3.8
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.5e7uwcse/downtmp/autopkgtest_tmp
collecting ... collected 111 items

tests/test_hierarchy.py::TestLinkage::test_linkage_non_finite_elements_in_distance_matrix
PASSED [  0%]
tests/test_hierarchy.py::TestLinkage::test_linkage_empty_distance_matrix
PASSED [  1%]
tests/test_hierarchy.py::TestLinkage::test_linkage_tdist PASSED
[  2%]
tests/test_hierarchy.py::TestLinkage::test_linkage_X PASSED
[  3%]
tests/test_hierarchy.py::TestLinkage::test_compare_with_trivial PASSED
[  4%]
tests/test_hierarchy.py::TestLinkage::test_optimal_leaf_ordering PASSED
[  5%]
tests/test_hierarchy.py::TestLinkageTies::test_linkage_ties PASSED
[  6%]
tests/test_hierarchy.py::TestInconsistent::test_inconsistent_tdist
PASSED [  7%]
tests/test_hierarchy.py::TestCopheneticDistance::test_linkage_cophenet_tdist_Z
PASSED [  8%]
tests/test_hierarchy.py::TestCopheneticDistance::test_linkage_cophenet_tdist_Z_Y
PASSED [  9%]
tests/test_hierarchy.py::TestMLabLinkageConversion::test_mlab_linkage_conversion_empty
PASSED [  9%]
tests/test_hierarchy.py::TestMLabLinkageConversion::test_mlab_linkage_conversion_single_row
PASSED [ 10%]
tests/test_hierarchy.py::TestMLabLinkageConversion::test_mlab_linkage_conversion_multiple_rows
PASSED [ 11%]
tests/test_hierarchy.py::TestFcluster::test_fclusterdata PASSED
[ 12%]
tests/test_hierarchy.py::TestFcluster::test_fcluster PASSED
[ 13%]
tests/test_hierarchy.py::TestFcluster::test_fcluster_monocrit PASSED
[ 14%]
tests/test_hierarchy.py::TestLeaders::test_leaders_single PASSED
[ 15%]
tests/test_hierarchy.py::TestIsIsomorphic::test_is_isomorphic_1 PASSED
[ 16%]
tests/test_hierarchy.py::TestIsIsomorphic::test_is_isomorphic_2 PASSED
[ 17%]
tests/test_hierarchy.py::TestIsIsomorphic::test_is_isomorphic_3 PASSED
[ 18%]
tests/test_hierarchy.py::TestIsIsomorphic::test_is_isomorphic_4A PASSED
[ 18%]
tests/test_hierarchy.py::TestIsIsomorphic::test_is_isomorphic_4B PASSED
[ 19%]
tests/test_hierarchy.py::TestIsIsomorphic::test_is_isomorphic_4C PASSED
[ 20%]
tests/test_hierarchy.py::TestIsIsomorphic::test_is_isomorphic_5 PASSED
[ 21%]
tests/test_hierarchy.py::TestIsIsomorphic::test_is_isomorphic_6 PASSED
[ 22%]
tests/test_hierarchy.py::TestIsIsomorphic::test_is_isomorphic_7 PASSED
[ 23%]
tests/test_hierarchy.py::TestIsValidLinkage::test_is_valid_linkage_various_size
PASSED [ 24%]
tests/test_hierarchy.py::TestIsValidLinkage::test_is_valid_linkage_int_type
PASSED [ 25%]
tests/test_hierarchy.py::TestIsValidLinkage::test_is_valid_linkage_empty
PASSED [ 26%]
tests/test_hierarchy.py::TestIsValidLinkage::test_is_valid_linkage_4_and_up
PASSED [ 27%]
tests/test_hierarchy.py::TestIsValidLinkage::test_is_valid_linkage_4_and_up_neg_index_left
PASSED [ 27%]
tests/test_hierarchy.py::TestIsValidLinkage::test_is_valid_linkage_4_and_up_neg_index_right
PASSED [ 28%]
tests/test_hierarchy.py::TestIsValidLinkage::test_is_valid_linkage_4_and_up_neg_dist
PASSED [ 29%]
tests/test_hierarchy.py::TestIsValidLinkage::test_is_valid_linkage_4_and_up_neg_counts
PASSED [ 30%]
tests/test_hierarchy.py::TestIsValidInconsistent::test_is_valid_im_int_type
PASSED [ 31%]
tests/test_hierarchy.py::TestIsValidInconsistent::test_is_valid_im_various_size
PASSED [ 32%]
tests/test_hierarchy.py::TestIsValidInconsistent::test_is_valid_im_empty
PASSED [ 33%]
tests/test_hierarchy.py::TestIsValidInconsistent::test_is_valid_im_4_and_up
PASSED [ 34%]
tests/test_hierarchy.py::TestIsValidInconsistent::test_is_valid_im_4_and_up_neg_index_left
PASSED [ 35%]

Processed: Re: Bug#963062: fixed in node-formidable 1.2.1+20200129git8231ea6-1

[Debian Bug Tracking System]

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

> # fix metadata
> reassign 963062 src:node-formidable 1.2.1-4
Bug #963062 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } 
[src:node-formidable] nodejs breaks node-formidable autopkgtest: Cannot call 
write after a stream was destroyed
Bug #963358 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } 
[src:node-formidable] node-formidable: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
Ignoring request to reassign bug #963062 to the same package
Ignoring request to reassign bug #963358 to the same package
Bug #963062 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } 
[src:node-formidable] nodejs breaks node-formidable autopkgtest: Cannot call 
write after a stream was destroyed
Bug #963358 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } 
[src:node-formidable] node-formidable: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
Ignoring request to alter found versions of bug #963062 to the same values 
previously set
Ignoring request to alter found versions of bug #963358 to the same values 
previously set
> fixed 963062 1.2.1+20200129git8231ea6-1
Bug #963062 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } 
[src:node-formidable] nodejs breaks node-formidable autopkgtest: Cannot call 
write after a stream was destroyed
Bug #963358 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } 
[src:node-formidable] node-formidable: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
Ignoring request to alter fixed versions of bug #963062 to the same values 
previously set
Ignoring request to alter fixed versions of bug #963358 to the same values 
previously set
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was elb...@debian.org).
> usertag 963062 - breaks
Usertags were: breaks needs-update.
Usertags are now: needs-update.
> thanks
Stopping processing here.

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

Bug#957714: marked as done (psqlodbc: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 18:18:54 +
with message-id 
and subject line Bug#957714: fixed in psqlodbc 1:12.02.-2
has caused the Debian Bug report #957714,
regarding psqlodbc: ftbfs with GCC-10
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.)


-- 
957714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:psqlodbc
Version: 1:12.01.-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/psqlodbc_12.01.-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
cc -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include/postgresql 
-I/usr/include/postgresql/internal -I..  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-pointer-sign  -Wl,-z,relro -L/usr/lib 
-L/usr/lib/x86_64-linux-gnu src/arraybinding-test.c exe/common.o -o 
exe/arraybinding-test -lodbc
cc -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include/postgresql 
-I/usr/include/postgresql/internal -I..  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-pointer-sign  -Wl,-z,relro -L/usr/lib 
-L/usr/lib/x86_64-linux-gnu src/insertreturning-test.c exe/common.o -o 
exe/insertreturning-test -lodbc
cc -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include/postgresql 
-I/usr/include/postgresql/internal -I..  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-pointer-sign  -Wl,-z,relro -L/usr/lib 
-L/usr/lib/x86_64-linux-gnu src/dataatexecution-test.c exe/common.o -o 
exe/dataatexecution-test -lodbc
cc -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include/postgresql 
-I/usr/include/postgresql/internal -I..  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-pointer-sign  -Wl,-z,relro -L/usr/lib 
-L/usr/lib/x86_64-linux-gnu src/boolsaschar-test.c exe/common.o -o 
exe/boolsaschar-test -lodbc
cc -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include/postgresql 
-I/usr/include/postgresql/internal -I..  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-pointer-sign  -Wl,-z,relro -L/usr/lib 
-L/usr/lib/x86_64-linux-gnu src/cvtnulldate-test.c exe/common.o -o 
exe/cvtnulldate-test -lodbc
cc -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include/postgresql 
-I/usr/include/postgresql/internal -I..  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-pointer-sign  -Wl,-z,relro -L/usr/lib 
-L/usr/lib/x86_64-linux-gnu src/alter-test.c exe/common.o -o exe/alter-test 
-lodbc
cc -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include/postgresql 
-I/usr/include/postgresql/internal -I..  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-pointer-sign  -Wl,-z,relro -L/usr/lib 
-L/usr/lib/x86_64-linux-gnu src/quotes-test.c exe/common.o -o exe/quotes-test 
-lodbc
cc -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include/postgresql 
-I/usr/include/postgresql/internal -I..  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-pointer-sign  -Wl,-z,relro -L/usr/lib 
-L/usr/lib/x86_64-linux-gnu src/cursors-test.c exe/common.o -o exe/cursors-test 
-lodbc
cc -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include/postgresql 

Bug#957714: marked as pending in psqlodbc

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #957714 in psqlodbc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/postgresql/psqlodbc/-/commit/50cec2ad39cd47ab77f690d9ef1deb3a973c92ec


Fix build failure with gcc 10, thanks Paul Wise! (Closes: #957714)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/957714

Processed: Bug#957714 marked as pending in psqlodbc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #957714 [src:psqlodbc] psqlodbc: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#963062: marked as done (nodejs breaks node-formidable autopkgtest: Cannot call write after a stream was destroyed)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 16:21:03 +
with message-id 
and subject line Bug#963062: fixed in node-formidable 1.2.1+20200129git8231ea6-1
has caused the Debian Bug report #963062,
regarding nodejs breaks node-formidable autopkgtest: Cannot call write after a 
stream was destroyed
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.)


-- 
963062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs, node-formidable
Control: found -1 nodejs/12.18.0~dfsg-3
Control: found -1 node-formidable/1.2.1-4
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of nodejs the autopkgtest of node-formidable fails
in testing when that autopkgtest is run with the binary packages of
nodejs from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
nodejs from testing12.18.0~dfsg-3
node-formidablefrom testing1.2.1-4
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of nodejs to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=nodejs

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-formidable/5930268/log.gz

not ok 5 test/standalone/test-content-transfer-encoding.js
  (node:13770) [DEP0005] DeprecationWarning: Buffer() is deprecated due
to security and usability issues. Please use the Buffer.alloc(),
Buffer.allocUnsafe(), or Buffer.from() methods instead.
  events.js:292
throw er; // Unhandled 'error' event
^

  Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was
destroyed
  at WriteStream._write (internal/fs/streams.js:394:33)
  at WriteStream. (internal/fs/streams.js:390:12)
  at Object.onceWrapper (events.js:422:26)
  at WriteStream.emit (events.js:327:22)
  at internal/fs/streams.js:381:10
  at FSReqCallback.oncomplete (fs.js:155:23)
  Emitted 'error' event on WriteStream instance at:
  at errorOrDestroy (internal/streams/destroy.js:108:12)
  at onwriteError (_stream_writable.js:424:5)
  at onwrite (_stream_writable.js:445:5)
  at WriteStream._write (internal/fs/streams.js:394:30)
  at WriteStream. (internal/fs/streams.js:390:12)
  [... lines matching original stack trace ...]
  at FSReqCallback.oncomplete (fs.js:155:23) {
code: 'ERR_STREAM_DESTROYED'
  }




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-formidable
Source-Version: 1.2.1+20200129git8231ea6-1
Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= 

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated node-formidable 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: Tue, 28 Jul 2020 17:50:02 +0200
Source: node-formidable
Architecture: source
Version: 1.2.1+20200129git8231ea6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Closes: 963062
Changes:
 node-formidable (1.2.1+20200129git8231ea6-1) unstable; urgency=medium
 .
   * New upstream version, between 1.2.1 and 2.0.0-alpha
 This has been cut so that it works reasonably well on node 12
 without api changes or major packaging changes.
   * Additionally, some upstream changes have been added manually,
 to fix tests, and pass them:
 + upstream-test-fixes.patch
 + 

Bug#963358: marked as done (node-formidable: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 16:21:03 +
with message-id 
and subject line Bug#963062: fixed in node-formidable 1.2.1+20200129git8231ea6-1
has caused the Debian Bug report #963062,
regarding node-formidable: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 1
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.)


-- 
963062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-formidable
Version: 1.2.1-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-formidable
> dpkg-buildpackage: info: source version 1.2.1-4
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Xavier Guimard 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with nodejs
>dh_auto_clean --buildsystem=nodejs
>   rm -rf ./node_modules/.cache
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-formidable using existing 
> ./node-formidable_1.2.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building node-formidable in 
> node-formidable_1.2.1-4.debian.tar.xz
> dpkg-source: info: building node-formidable in node-formidable_1.2.1-4.dsc
>  debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../debian/tests/test_modules/urun node_modules/urun
>   ln -s ../debian/tests/test_modules/utest node_modules/utest
>   ln -s ../debian/tests/test_modules/chainsaw node_modules/chainsaw
>   ln -s ../debian/tests/test_modules/findit node_modules/findit
>   ln -s ../debian/tests/test_modules/seq node_modules/seq
>   ln -s ../debian/tests/test_modules/gently node_modules/gently
>   /bin/sh -ex debian/tests/pkg-js/test
> + node -e require("urun")(__dirname+"/test", {reporter: 
> "BashTapReporter",include:/test-.+\.js$/});
> 1..14
> ok 1 test/integration/test-fixtures.js
> ok 2 test/integration/test-json.js
> ok 3 test/integration/test-octet-stream.js
> ok 4 test/standalone/test-connection-aborted.js
> not ok 5 test/standalone/test-content-transfer-encoding.js
>   (node:30242) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
>   events.js:292
> throw er; // Unhandled 'error' event
> ^
>   
>   Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
>   at WriteStream._write (internal/fs/streams.js:394:33)
>   at WriteStream. (internal/fs/streams.js:390:12)
>   at Object.onceWrapper (events.js:422:26)
>   at WriteStream.emit (events.js:327:22)
>   at internal/fs/streams.js:381:10
>   at FSReqCallback.oncomplete (fs.js:155:23)
>   Emitted 'error' event on WriteStream instance at:
>   at errorOrDestroy (internal/streams/destroy.js:108:12)
>   at onwriteError (_stream_writable.js:424:5)
>   at onwrite (_stream_writable.js:445:5)
>   at WriteStream._write (internal/fs/streams.js:394:30)
>   at WriteStream. (internal/fs/streams.js:390:12)
>   [... lines matching original stack trace ...]
>   at FSReqCallback.oncomplete (fs.js:155:23) {
> code: 'ERR_STREAM_DESTROYED'
>   }
>   
> ok 6 test/standalone/test-keep-alive-error.js
> ok 7 test/unit/test-file.js
> ok 8 test/unit/test-incoming-form.js
> ok 9 test/legacy/integration/test-multipart-parser.js
> ok 10 test/legacy/simple/test-file.js
> ok 11 test/legacy/simple/test-incoming-form.js
> ok 12 test/legacy/simple/test-multipart-parser.js
> ok 13 test/legacy/simple/test-querystring-parser.js
> ok 14 test/legacy/system/test-multi-video-upload.js
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/node-formidable_1.2.1-4_unstable.log

A 

Bug#957783: marked as done (seaview: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 16:04:26 +
with message-id 
and subject line Bug#957783: fixed in seaview 1:5.0.2-3
has caused the Debian Bug report #957783,
regarding seaview: ftbfs with GCC-10
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.)


-- 
957783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:seaview
Version: 1:4.7-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/seaview_4.7-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
g++  -c -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DUSE_XFT -I/usr/include/freetype2 -DFLTK1 -Dunix 
-Icsrc -I. -DNO_PDF -DDEFAULT_HELPFILE=\"/usr/share/seaview/seaview.html\" 
-DPHYMLNAME=\"phyml\" -fPIC -Dunix -O3 -I.  -Icsrc-DNO_PDF 
FL/Fl_Native_File_Chooser_FLTK.cxx
gcc -c  -O3 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DUSE_XFT 
-I/usr/include/freetype2 -DFLTK1 -Dunix -Icsrc -I. -DNO_PDF 
-DDEFAULT_HELPFILE=\"/usr/share/seaview/seaview.html\" -DPHYMLNAME=\"phyml\" 
-fPIC -Dunix -Icsrc csrc/raa_acnuc.c
gcc -c  -O3 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DUSE_XFT 
-I/usr/include/freetype2 -DFLTK1 -Dunix -Icsrc -I. -DNO_PDF 
-DDEFAULT_HELPFILE=\"/usr/share/seaview/seaview.html\" -DPHYMLNAME=\"phyml\" 
-fPIC -Dunix -Icsrc csrc/parser.c
gcc -c  -O3 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DUSE_XFT 
-I/usr/include/freetype2 -DFLTK1 -Dunix -Icsrc -I. -DNO_PDF 
-DDEFAULT_HELPFILE=\"/usr/share/seaview/seaview.html\" -DPHYMLNAME=\"phyml\" 
-fPIC -Dunix -Icsrc csrc/md5.c
gcc -c  -O3 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DUSE_XFT 
-I/usr/include/freetype2 -DFLTK1 -Dunix -Icsrc -I. -DNO_PDF 
-DDEFAULT_HELPFILE=\"/usr/share/seaview/seaview.html\" -DPHYMLNAME=\"phyml\" 
-fPIC -Dunix -Icsrc csrc/zsockr.c
gcc -c  -O3 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DUSE_XFT 
-I/usr/include/freetype2 -DFLTK1 -Dunix -Icsrc -I. -DNO_PDF 
-DDEFAULT_HELPFILE=\"/usr/share/seaview/seaview.html\" -DPHYMLNAME=\"phyml\" 
-fPIC -Dunix -Icsrc csrc/misc_acnuc.c
gcc -c  -O3 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DUSE_XFT 
-I/usr/include/freetype2 -DFLTK1 -Dunix -Icsrc -I. -DNO_PDF 
-DDEFAULT_HELPFILE=\"/usr/share/seaview/seaview.html\" -DPHYMLNAME=\"phyml\" 
-fPIC -Dunix -Icsrc csrc/dnapars.c
gcc -c  -O3 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DUSE_XFT 
-I/usr/include/freetype2 -DFLTK1 -Dunix -Icsrc -I. -DNO_PDF 
-DDEFAULT_HELPFILE=\"/usr/share/seaview/seaview.html\" -DPHYMLNAME=\"phyml\" 
-fPIC -Dunix -Icsrc csrc/protpars.c
gcc -c  -O3 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DUSE_XFT 
-I/usr/include/freetype2 -DFLTK1 -Dunix -Icsrc -I. -DNO_PDF 
-DDEFAULT_HELPFILE=\"/usr/share/seaview/seaview.html\" -DPHYMLNAME=\"phyml\" 
-fPIC -Dunix -Icsrc csrc/seq.c
gcc -c  -O3 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DUSE_XFT 
-I/usr/include/freetype2 -DFLTK1 -Dunix -Icsrc -I. -DNO_PDF 
-DDEFAULT_HELPFILE=\"/usr/share/seaview/seaview.html\" -DPHYMLNAME=\"phyml\" 
-fPIC 

Bug#966421: libjpeg-turbo FTBFS on alpha/mips64el/powerpc/sparc64: test failures

[Mike Gabriel]

Hi Adrian,

On  Di 28 Jul 2020 13:43:34 CEST, Adrian Bunk wrote:


Source: libjpeg-turbo
Version: 1:2.0.2-1~exp1
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/package.php?p=libjpeg-turbo

...
177/302 Test  #83: djpeg-shared-3x2-float-prog-cmp  
...***Failed0.01 sec

testout_3x2_float.ppm: FAILED.  Checksum is f6bfab038438ed8f5522fbd33595dcdc
...
267/302 Test #234: djpeg-static-3x2-float-prog-cmp  
...***Failed0.01 sec

testout_3x2_float.ppm: FAILED.  Checksum is f6bfab038438ed8f5522fbd33595dcdc
...
99% tests passed, 2 tests failed out of 302

Total Test time (real) = 186.96 sec

The following tests FAILED:
 83 - djpeg-shared-3x2-float-prog-cmp (Failed)
234 - djpeg-static-3x2-float-prog-cmp (Failed)
Errors while running CTest
make[1]: *** [Makefile:121: test] Error 8


For determining the correct md5 of expected test results
libjpeg-turbo wrongly guesses for some architectures.

This is fixed by the first commit in
https://salsa.debian.org/debian/libjpeg-turbo/-/merge_requests/2


Thanks for finding patches for these issues. I will be on VAC over the  
next two weeks. Please NMU (ideally with commits to the packaging  
Git). Also coordinate with Paul Wise (see #966419).


I'll look into this in the second week of August, otherwise.

Thanks
Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpS0UcrqDZgc.pgp
Description: Digitale PGP-Signatur

Bug#966409: libjpeg-turbo: versions in debian/*.symbols files are missing the epochs

[Mike Gabriel]

Hi Pabs,

On  Di 28 Jul 2020 09:04:08 CEST, Paul Wise wrote:


Source: libjpeg-turbo
Version: 1:2.0.5-1
Severity: serious

The versions in the debian/*.symbols files are missing the epochs. This
means that packages using symbols newer than buster will not upgrade
libjpeg62-turbo and libturbojpeg0 when being upgraded to bullseye.

For example if I install bullseye libjpeg-turbo-progs on buster, the
programs will not work as libjpeg62-turbo and libturbojpeg0 will not be
upgraded so the new symbols like jpeg_write_icc_profile are missing.

$ rmadison -u debian libjpeg-turbo
libjpeg-turbo | 1:1.3.1-12| oldoldstable   | source
libjpeg-turbo | 1:1.5.1-2 | oldstable  | source
libjpeg-turbo | 1:1.5.2-2 | stable | source
libjpeg-turbo | 1:1.5.2-2 | testing| source
libjpeg-turbo | 1:1.5.2-2 | unstable   | source
libjpeg-turbo | 1:1.5.2-2 | unstable-debug | source
libjpeg-turbo | 1:2.0.5-1 | unstable   | source
libjpeg-turbo | 1:2.0.5-1 | unstable-debug | source

$ grep -v 1.3.1 debian/*.symbols | grep -v 1.2.90 | grep -v 1.4.0 |  
grep -v 1.5.0

debian/libjpeg62-turbo.symbols:libjpeg.so.62 libjpeg62-turbo #MINVER#
debian/libjpeg62-turbo.symbols:* Build-Depends-Package: libjpeg62-turbo-dev
debian/libjpeg62-turbo.symbols: jpeg_read_icc_profile@LIBJPEG_6.2 2.0.2
debian/libjpeg62-turbo.symbols: jpeg_write_icc_profile@LIBJPEG_6.2 2.0.2
debian/libturbojpeg0.symbols:libturbojpeg.so.0 libturbojpeg0 #MINVER#
debian/libturbojpeg0.symbols:* Build-Depends-Package: libturbojpeg0-dev
debian/libturbojpeg0.symbols: TURBOJPEG_2.0@TURBOJPEG_2.0 2.0.2
debian/libturbojpeg0.symbols: tjGetErrorCode@TURBOJPEG_2.0 2.0.2
debian/libturbojpeg0.symbols: tjGetErrorStr2@TURBOJPEG_2.0 2.0.2
debian/libturbojpeg0.symbols: tjLoadImage@TURBOJPEG_2.0 2.0.2
debian/libturbojpeg0.symbols: tjSaveImage@TURBOJPEG_2.0 2.0.2

# cat /etc/apt/sources.list
deb https://deb.debian.org/debian buster main

# apt -qq install libjpeg-turbo-progs
The following additional packages will be installed:
  libjpeg62-turbo libturbojpeg0
The following NEW packages will be installed:
  libjpeg-turbo-progs libjpeg62-turbo libturbojpeg0
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 266 kB/399 kB of archives.
After this operation, 1275 kB of additional disk space will be used.
Do you want to continue? [Y/n]
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libjpeg62-turbo:amd64.
(Reading database ... 12518 files and directories currently installed.)
Preparing to unpack .../libjpeg62-turbo_1%3a1.5.2-2+b1_amd64.deb ...
Unpacking libjpeg62-turbo:amd64 (1:1.5.2-2+b1) ...
Selecting previously unselected package libturbojpeg0:amd64.
Preparing to unpack .../libturbojpeg0_1%3a1.5.2-2+b1_amd64.deb ...
Unpacking libturbojpeg0:amd64 (1:1.5.2-2+b1) ...
Selecting previously unselected package libjpeg-turbo-progs.
Preparing to unpack .../libjpeg-turbo-progs_1%3a1.5.2-2+b1_amd64.deb ...
Unpacking libjpeg-turbo-progs (1:1.5.2-2+b1) ...
Setting up libturbojpeg0:amd64 (1:1.5.2-2+b1) ...
Setting up libjpeg62-turbo:amd64 (1:1.5.2-2+b1) ...
Setting up libjpeg-turbo-progs (1:1.5.2-2+b1) ...
Processing triggers for libc-bin (2.28-10) ...

# cat /etc/apt/sources.list | grep buster | sed s/buster/sid/ >>  
/etc/apt/sources.list


# cat /etc/apt/sources.list
deb https://deb.debian.org/debian buster main
deb https://deb.debian.org/debian sid main

# apt update
Hit:1 https://deb.debian.org/debian buster InRelease
Get:2 https://deb.debian.org/debian sid InRelease [146 kB]
Get:3 https://deb.debian.org/debian sid/main amd64 Packages [8345 kB]
Fetched 8491 kB in 6s (1365 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
126 packages can be upgraded. Run 'apt list --upgradable' to see them.

# apt policy libjpeg-turbo-progs
libjpeg-turbo-progs:
  Installed: 1:1.5.2-2+b1
  Candidate: 1:2.0.5-1
  Version table:
 1:2.0.5-1 500
500 https://deb.debian.org/debian sid/main amd64 Packages
 *** 1:1.5.2-2+b1 500
500 https://deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status

# apt install libjpeg-turbo-progs=1:2.0.5-1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  libjpeg-turbo-progs
1 upgraded, 0 newly installed, 0 to remove and 125 not upgraded.
Need to get 131 kB of archives.
After this operation, 51.2 kB of additional disk space will be used.
Get:1 https://deb.debian.org/debian sid/main amd64  
libjpeg-turbo-progs amd64 1:2.0.5-1 [131 kB]

Fetched 131 kB in 1s (227 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 12558 files and directories currently installed.)
Preparing to unpack .../libjpeg-turbo-progs_1%3a2.0.5-1_amd64.deb ...
Unpacking libjpeg-turbo-progs (1:2.0.5-1) over (1:1.5.2-2+b1) ...
Setting up libjpeg-turbo-progs (1:2.0.5-1) 

Bug#966449: coreutils 8.32-3 FTBFS on arm64 (and proposed fix)

[Sergio Durigan Junior]

Package: coreutils
Version: 8.32-3
Severity: serious
Tags: patch ftbfs

Hi,

The current coreutils version FTBFS on arm64:

src/ls.c: In function 'print_dir':
src/ls.c:3026:24: error: 'SYS_getdents' undeclared (first use in this 
function); did you mean 'SYS_getdents64'?
 3026 |   if (syscall (SYS_getdents, dirfd (dirp), NULL, 0) == -1
  |^~~~
  |SYS_getdents64
src/ls.c:3026:24: note: each undeclared identifier is reported only once for 
each function it appears in

This has been reported upstream in
.
The fix upstream adopted is to restore the behaviour of ls on removed
directories back to what it was on 8.31.

I've backported the patches needed to fix the issue, so I'm proposing
them here.  Ubuntu coreutils is already carrying these patches and the
ARM64 build passes there.

Thanks!

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

diff -Nru coreutils-8.32/debian/changelog coreutils-8.32/debian/changelog
--- coreutils-8.32/debian/changelog	2020-07-20 14:09:06.0 -0400
+++ coreutils-8.32/debian/changelog	2020-07-28 10:50:52.0 -0400
@@ -1,3 +1,16 @@
+coreutils (8.32-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS on ARM64.
+- d/p/restore-ls-behavior-8.31.patch: Upstream patch to restore
+  coreutils ls' 8.31 behavior on removed directories, which is
+  necessary to prevent using SYS_getdents that doesn't exist on
+  ARM64.
+- d/p/improve-removed-directory-test.patch: Upstream patch to
+  improve ls' removed-directory test.
+
+ -- Sergio Durigan Junior   Tue, 28 Jul 2020 10:50:52 -0400
+
 coreutils (8.32-3) unstable; urgency=low
 
   * build with libgmp now that apt pulls it in anyway (Closes: #64527)
diff -Nru coreutils-8.32/debian/patches/improve-removed-directory-test.patch coreutils-8.32/debian/patches/improve-removed-directory-test.patch
--- coreutils-8.32/debian/patches/improve-removed-directory-test.patch	1969-12-31 19:00:00.0 -0500
+++ coreutils-8.32/debian/patches/improve-removed-directory-test.patch	2020-07-28 10:50:23.0 -0400
@@ -0,0 +1,49 @@
+From: Paul Eggert 
+Date: Sat, 7 Mar 2020 10:29:51 -0800
+Subject: ls: improve removed-directory test
+
+* tests/ls/removed-directory.sh: Remove host_triplet test.
+Skip this test if one cannot remove the working directory.
+From a suggestion by Bernhard Voelker (Bug#39929).
+
+Author: Paul Eggert 
+Origin: upstream, https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=672819c73f2e94e61386dc0584bddf9da860cc26
+Bug: https://lists.gnu.org/archive/html/bug-coreutils/2020-03/msg5.html
+Last-Updated: 2020-07-24
+Reviewed-By: Sergio Durigan Junior 
+---
+ tests/ls/removed-directory.sh | 13 -
+ 1 file changed, 4 insertions(+), 9 deletions(-)
+
+diff --git a/tests/ls/removed-directory.sh b/tests/ls/removed-directory.sh
+index fe8f929..63b209d 100755
+--- a/tests/ls/removed-directory.sh
 b/tests/ls/removed-directory.sh
+@@ -1,7 +1,7 @@
+ #!/bin/sh
+-# If ls is asked to list a removed directory (e.g. the parent process's
+-# current working directory that has been removed by another process), it
+-# emits an error message.
++# If ls is asked to list a removed directory (e.g., the parent process's
++# current working directory has been removed by another process), it
++# should not emit an error message merely because the directory is removed.
+ 
+ # Copyright (C) 2020 Free Software Foundation, Inc.
+ 
+@@ -21,15 +21,10 @@
+ . "${srcdir=.}/tests/init.sh"; path_prepend_ ./src
+ print_ver_ ls
+ 
+-case $host_triplet in
+-  *linux*) ;;
+-  *) skip_ 'non linux kernel' ;;
+-esac
+-
+ cwd=$(pwd)
+ mkdir d || framework_failure_
+ cd d || framework_failure_
+-rmdir ../d || framework_failure_
++rmdir ../d || skip_ "can't remove working directory on this platform"
+ 
+ ls >../out 2>../err || fail=1
+ cd "$cwd" || framework_failure_
diff -Nru coreutils-8.32/debian/patches/restore-ls-behavior-8.31.patch coreutils-8.32/debian/patches/restore-ls-behavior-8.31.patch
--- coreutils-8.32/debian/patches/restore-ls-behavior-8.31.patch	1969-12-31 19:00:00.0 -0500
+++ coreutils-8.32/debian/patches/restore-ls-behavior-8.31.patch	2020-07-28 10:50:23.0 -0400
@@ -0,0 +1,126 @@
+From: Paul Eggert 
+Date: Thu, 5 Mar 2020 17:25:29 -0800
+Subject: ls: restore 8.31 behavior on removed directories
+
+* NEWS: Mention this.
+* src/ls.c: Do not include 
+(print_dir): Don't worry about whether the directory is removed.
+* tests/ls/removed-directory.sh: Adjust to match new (i.e., old)
+behavior.
+
+This patch is needed because coreutils 8.32 fails to build on ARM64
+with:
+
+src/ls.c: In function 'print_dir':
+src/ls.c:3026:24: error: 'SYS_getdents' undeclared (first use in this function); did you mean 'SYS_getdents64'?
+ 3026 |   if (syscall 

Bug#966437: bambam: autopkgtest failure with imagemagick 8:6.9.11.24+dfsg-1

[Marcin Owsiany]

Just a quick note before I get a chance to look at this closer, in case
anyone else wants to take a stab at it.
It's one thing that the color output format changed in a way that the test
program does not know how to parse it. That's easy to fix.

It's more worrying that the reported average color stays at
"srgb(98.0209%,98.0209%,98.0209%)"
for 40 attempts. This means that either the screen color isn't in fact
changing (i.e. the game is broken) or that the way the average color is
calculated by imagemagick has changed in a way which makes it unusable :-/

wt., 28 lip 2020 o 16:36 Adrian Bunk  napisał(a):

> Source: bambam
> Version: 1.0.1+dfsg-1
> Severity: serious
> Tags: bullseye sid
>
> https://ci.debian.net/packages/b/bambam/unstable/amd64/
>
> Test success with imagemagick < 8:6.9.11.24+dfsg-1:
> ...
> On attempt 5 the average screen color was too close to white: 233,230,235.
> On attempt 6 the average screen color was too close to white: 225,223,231.
> On attempt 7 the average screen color was too close to white: 223,220,226.
> ...
>
> Test failure with imagemagick 8:6.9.11.24+dfsg-1:
> ...
> On attempt 37 the average screen color was
> srgb(98.0209%,98.0209%,98.0209%).
> On attempt 38 the average screen color was
> srgb(98.0209%,98.0209%,98.0209%).
> On attempt 39 the average screen color was
> srgb(98.0209%,98.0209%,98.0209%).
> Traceback (most recent call last):
>   File "./debian/tests/smoke-meat", line 101, in 
> main()
>   File "./debian/tests/smoke-meat", line 24, in main
> await_startup()
>   File "./debian/tests/smoke-meat", line 45, in await_startup
> raise Exception('Failed to see bambam start after %d attempts.' %
> attempt_count)
> Exception: Failed to see bambam start after 40 attempts.
>
>
> I suspect the output of convert changed that is parsed in
>
> https://sources.debian.org/src/bambam/1.0.1+dfsg-1/debian/tests/smoke-meat/#L83
>

Bug#966447: node-trust-jwa: FTBFS: Error: Cannot find module 'babel-helper-function-name'

[Andreas Beckmann]

Source: node-trust-jwa
Version: 0.4.6-1~exp1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

node-trust-jwa started to FTBFS after some changes in the node-babel ecosystem:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/node-trust-jwa-0.4.6'
pandoc --from gfm-raw_html --to html --standalone --output README.html README.md
[WARNING] This document format requires a nonempty  element.
  Defaulting to 'README' as the title.
  To specify a title, use 'title' in metadata or --metadata title="...".
pandoc --from gfm-raw_html --to plain --output README.txt README.md
babeljs src -d lib
Error: Cannot find module 'babel-helper-function-name'
Require stack:
- /usr/share/nodejs/babel-plugin-transform-es2015-function-name/lib/index.js
- /usr/share/nodejs/babel-preset-es2015/lib/index.js
- /usr/share/nodejs/babel-core/lib/transformation/file/options/option-manager.js
- /usr/share/nodejs/babel-core/lib/transformation/file/index.js
- /usr/share/nodejs/babel-core/lib/api/node.js
- /usr/share/nodejs/babel-core/index.js
- /usr/share/nodejs/babel-cli/lib/babel/index.js
- /usr/share/nodejs/babel-cli/bin/babel.js (While processing preset: 
"/usr/share/nodejs/babel-preset-es2015/lib/index.js")
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15)
at Function.Module._load (internal/modules/cjs/loader.js:842:27)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object. 
(/usr/share/nodejs/babel-plugin-transform-es2015-function-name/lib/index.js:28:32)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19)
make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1
make[1]: Leaving directory '/build/node-trust-jwa-0.4.6'
make: *** [debian/rules:33: binary] Error 2


Andreas


node-trust-jwa_0.4.6-1~exp1.log.gz
Description: application/gzip

Bug#966446: node-solid-jose: FTBFS Error: Cannot find module 'babel-helper-function-name'

[Andreas Beckmann]

Source: node-solid-jose
Version: 0.4.0+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

node-solid-jose started to FTBFS after some changes in the node-babel ecosystem:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/node-solid-jose-0.4.0+dfsg'
pandoc --from gfm-raw_html --to html --standalone --output README.html README.md
[WARNING] This document format requires a nonempty  element.
  Defaulting to 'README' as the title.
  To specify a title, use 'title' in metadata or --metadata title="...".
pandoc --from gfm-raw_html --to plain --output README.txt README.md
babeljs src -d lib
Error: Cannot find module 'babel-helper-function-name'
Require stack:
- /usr/share/nodejs/babel-plugin-transform-es2015-function-name/lib/index.js
- /usr/share/nodejs/babel-preset-es2015/lib/index.js
- /usr/share/nodejs/babel-core/lib/transformation/file/options/option-manager.js
- /usr/share/nodejs/babel-core/lib/transformation/file/index.js
- /usr/share/nodejs/babel-core/lib/api/node.js
- /usr/share/nodejs/babel-core/index.js
- /usr/share/nodejs/babel-cli/lib/babel/index.js
- /usr/share/nodejs/babel-cli/bin/babel.js (While processing preset: 
"/usr/share/nodejs/babel-preset-es2015/lib/index.js")
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15)
at Function.Module._load (internal/modules/cjs/loader.js:842:27)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object. 
(/usr/share/nodejs/babel-plugin-transform-es2015-function-name/lib/index.js:28:32)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19)
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1
make[1]: Leaving directory '/build/node-solid-jose-0.4.0+dfsg'
make: *** [debian/rules:30: binary] Error 2


Andreas


node-solid-jose_0.4.0+dfsg-1.log.gz
Description: application/gzip

Bug#957126: marked as done (dealer: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 15:18:27 +
with message-id 
and subject line Bug#957126: fixed in dealer 20190529+ds-2
has caused the Debian Bug report #957126,
regarding dealer: ftbfs with GCC-10
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.)


-- 
957126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dealer
Version: 20190529+ds-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/dealer_20190529+ds-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
make -j4 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
flex -t scan.l >scan.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DSTD_RAND   
-c -o pbn.o pbn.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DSTD_RAND   
-c -o c4.o c4.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DSTD_RAND   
-c -o pointcount.o pointcount.c
pod2man --section=6 --release="Dealer" --center="User Documentation" dealer.pod 
> dealer.6
pod2man --section=6 --release="Dealer" --center="User Documentation" 
dealer.dpp.pod > dealer.dpp.6
yacc defs.y
defs.y: warning: 16 shift/reduce conflicts [-Wconflicts-sr]
mv -f y.tab.c defs.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DSTD_RAND   
-c -o dealer.o dealer.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DSTD_RAND   
-c -o defs.o defs.c
y.tab.c: In function ‘yyparse’:
y.tab.c:1674:16: warning: implicit declaration of function ‘yylex’ 
[-Wimplicit-function-declaration]
defs.y:237:35: warning: implicit declaration of function ‘d2n’ 
[-Wimplicit-function-declaration]
  237 | { $$ = d2n($1); }
  |   ^  
defs.y: In function ‘insertshape’:
defs.y:520:6: warning: type of ‘any’ defaults to ‘int’ [-Wimplicit-int]
  520 | void insertshape(s, any, neg_shape)
  |  ^~~
defs.y:520:6: warning: type of ‘neg_shape’ defaults to ‘int’ [-Wimplicit-int]
defs.y: In function ‘predeal_holding’:
defs.y:634:6: warning: type of ‘compass’ defaults to ‘int’ [-Wimplicit-int]
  634 | void predeal_holding(compass, holding)
  |  ^~~
dealer.c: In function ‘true_dd’:
dealer.c:331:5: warning: ignoring return value of ‘tmpnam’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  331 | tmpnam (tn2);
  | ^~~~
dealer.c:333:5: warning: ignoring return value of ‘system’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  333 | system (cmd);
  | ^~~~
dealer.c:336:5: warning: ignoring return value of ‘fscanf’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  336 | fscanf (f, "%*[^\n]\n%c", );
  | ^~~
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DSTD_RAND  
-Wl,-z,relro  -o dealer dealer.o defs.o pbn.o c4.o pointcount.o
/usr/bin/ld: defs.o:./dealer.h:54: multiple definition of `maxvuln'; 
dealer.o:./dealer.h:54: first defined here
/usr/bin/ld: 

Processed: Re: Bug#933031: pristine-tar: unable to unpack some deltas of version 2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #933031 [pristine-tar] pristine-tar: unable to unpack some deltas of 
version 2
Severity set to 'grave' from 'important'

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

Processed: bug 957615 is forwarded to https://bugs.ntp.org/show_bug.cgi?id=3688

[Debian Bug Tracking System]

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

> forwarded 957615 https://bugs.ntp.org/show_bug.cgi?id=3688
Bug #957615 [src:ntp] ntp: ftbfs with GCC-10
Set Bug forwarded-to-address to 'https://bugs.ntp.org/show_bug.cgi?id=3688'.
> thanks
Stopping processing here.

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

Processed: forcibly merging 966437 966438

[Debian Bug Tracking System]

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

> forcemerge 966437 966438
Bug #966437 [src:bambam] bambam: autopkgtest failure with imagemagick 
8:6.9.11.24+dfsg-1
Bug #966438 [src:bambam] src:bambam: Autopkgtest fail wiht newer imagemagick*
Added tag(s) sid and bullseye.
Merged 966437 966438
> thanks
Stopping processing here.

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

Bug#957314: marked as done (gst-plugins-bad1.0: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 15:03:54 +
with message-id 
and subject line Bug#957314: fixed in gst-plugins-bad1.0 1.16.2-2.3
has caused the Debian Bug report #957314,
regarding gst-plugins-bad1.0: ftbfs with GCC-10
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.)


-- 
957314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gst-plugins-bad1.0
Version: 1.16.2-2.1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/gst-plugins-bad1.0_1.16.2-2.1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:43: multiple 
definition of `integer_prop'; 
.libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:43: first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:41: multiple 
definition of `state_uri'; .libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:41: 
first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:40: multiple 
definition of `state_iface'; .libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:40: 
first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:39: multiple 
definition of `preset_class'; 
.libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:39: first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:38: multiple 
definition of `output_class'; 
.libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:38: first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:37: multiple 
definition of `input_class'; .libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:37: 
first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:36: multiple 
definition of `event_class'; .libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:36: 
first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:35: multiple 
definition of `cv_class'; .libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:35: 
first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:34: multiple 
definition of `control_class'; 
.libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:34: first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:33: multiple 
definition of `audio_class'; .libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:33: 
first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:32: multiple 
definition of `atom_class'; .libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:32: 
first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2filter.o:./ext/lv2/gstlv2.h:31: multiple 
definition of `world'; .libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:31: first 
defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2source.o:./ext/lv2/gstlv2.h:64: multiple 
definition of `lv2_meta_all'; 
.libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:64: first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2source.o:./ext/lv2/gstlv2.h:62: multiple 
definition of `side_right_role'; 
.libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:62: first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2source.o:./ext/lv2/gstlv2.h:61: multiple 
definition of `side_left_role'; 
.libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:61: first defined here
/usr/bin/ld: .libs/libgstlv2_la-gstlv2source.o:./ext/lv2/gstlv2.h:60: multiple 
definition of `center_right_role'; 
.libs/libgstlv2_la-gstlv2.o:./ext/lv2/gstlv2.h:60: 

Bug#965298: marked as done (gst-plugins-bad1.0 cannot be built in testing.)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 15:03:54 +
with message-id 
and subject line Bug#965298: fixed in gst-plugins-bad1.0 1.16.2-2.3
has caused the Debian Bug report #965298,
regarding gst-plugins-bad1.0 cannot be built in testing.
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.)


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

Package: gst-plugins-bad1.0
Version: 1.16.2-2.1
Severity: serious
x-debbugs-cc: sramac...@debian.org, locutusofb...@debian.org

Neither version 1.16.2-2.1 (from bullseye) or version 1.16.2-2.2 (from sid) can 
be built in testing.

1.16.2-2.1 cannot be built because libsrt-dev has been removed.

1.16.2-2.2 cannot be built because Gianfranco's patch for make 4.3 breaks the 
build with make 4.2.

I intend to wait unil 1.16.2-2.2 migrates to testing ( because as I stated in 
my earlier mail I
consider it an improvement over 1.16.2-2.1 ). If at that point make 4.3 has not 
migrated to testing
(and I don't receive any objections) then I intend to prepare a NMU, similar to 
the one I already
did for baresip.
--- End Message ---
--- Begin Message ---
Source: gst-plugins-bad1.0
Source-Version: 1.16.2-2.3
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated 
gst-plugins-bad1.0 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, 23 Jul 2020 12:47:21 +
Source: gst-plugins-bad1.0
Architecture: source
Version: 1.16.2-2.3
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of GStreamer packages 

Changed-By: Peter Michael Green 
Closes: 957314 965298
Changes:
 gst-plugins-bad1.0 (1.16.2-2.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Adjust make 4.3 patch to also work with make 4.2 (Closes: 965298 )
   * Apply upstream patch to make "lv2" plugin build with gcc-10 (Closes: 
957314 )
Checksums-Sha1:
 4eb17e07336c9c9fb4f97e3ff90027e1dafa32c6 4905 gst-plugins-bad1.0_1.16.2-2.3.dsc
 2c5ce7b2975c5d21c6107d1a192e4f13bcbe460a 36912 
gst-plugins-bad1.0_1.16.2-2.3.debian.tar.xz
 8bf4f8b023d6dc652eff59e02c298a62074af8d3 27472 
gst-plugins-bad1.0_1.16.2-2.3_source.buildinfo
Checksums-Sha256:
 58fc41815a5193210caddaed0e8753b8bbc9e6d7e59c1698be26736ffcc850d9 4905 
gst-plugins-bad1.0_1.16.2-2.3.dsc
 7846e0bd67afc524b864b6812e3e2435a2bcc8fb5afe0a4e70845c6445c92ab4 36912 
gst-plugins-bad1.0_1.16.2-2.3.debian.tar.xz
 73e5d788ec6b8f294bb1c0034d1143490bc44c885d1d6343ee550fae36313f01 27472 
gst-plugins-bad1.0_1.16.2-2.3_source.buildinfo
Files:
 001a546bb81e836b0524929b7d884be4 4905 libs extra 
gst-plugins-bad1.0_1.16.2-2.3.dsc
 a7d66fc38ba4a4200df9e1660fb5b38d 36912 libs extra 
gst-plugins-bad1.0_1.16.2-2.3.debian.tar.xz
 2c01db4850fa1c22f5b118ad7133 27472 libs extra 
gst-plugins-bad1.0_1.16.2-2.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl8ZnUkUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvR/xAAiPjYrveihM7wqHmra8R9js2nXmDf
QU2c9Gps8Rm4OsMZfYN/Di0juIEYcqkozv+hPWTZymuy+ezmxMWR6/C/dC6ju7Wy
R+xcNcH4xH0Q7OkOwPpFUcEsL1soEc9rhUyMKucMPDXlbmKO3rgYofUgvzBlEM38
jwcv8c3BddWsgwvsw+f6nXqjQ/oV11otO5Y1Fu9jnoL7XzVATwD8E3IHwYSbVHfH
mcWqb5OGdKndWwfw7wE7DDtPPTsmhb97NphSRvgjlzi1uVBb/oiMUiQV7sDWBc5D
4C9ly8JNQHnvdIhYbe39hXBWanjnHNvg7YRCG+XoTJZSLnSRFMfPmyaBNNPVdYKw
nXW0LKdjsSaQGpIcYmoVVoi0sGdcBT8dOL8oxPvsj9E+IFzeDkh5vFi3v6GcLwCq
ugCZJasmIJQgjRbZ69yAtcX+1wuDnkn4MlD1WUnZtY219i6TXsy7Lxc9DpM1MKwL
pn7+TQV0r5kyl87OcTE/sYgzBqWBmYJBhG6iB2SWWeBUdQYinRS4e+ex0fbwq7AX
dzhEZcjtBP0aeLGt9qMpiaKf87jB0itKiChYHBkl4Tfc2um581mFk0zZgooB6t+E
OfQssGkpbX0Y03P9IyegmoPs4wjuEpNgEBU/L8Hyqwy6M0BowlTrMFj8MaPzyGv4
BY7IxmhLd5YvkiU=
=JRXn
-END PGP SIGNATURE End Message ---

Bug#966439: clickhouse ftbfs with gcc-10

[Steve Langasek]

Package: clickhouse
Version: 18.16.1+ds-7.1
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy ubuntu-patch

Hi Alexander,

In Ubuntu, we've found that clickhouse fails to build from source with the
current toolchain due to a missing C++ include file.  The attached patch
fixes the build failure in unstable.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru clickhouse-18.16.1+ds/debian/control 
clickhouse-18.16.1+ds/debian/control
--- clickhouse-18.16.1+ds/debian/control2020-07-27 08:39:42.0 
-0700
+++ clickhouse-18.16.1+ds/debian/control2020-07-27 17:59:57.0 
-0700
@@ -1,8 +1,7 @@
 Source: clickhouse
 Section: database
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Alexander GQ Gerasiov 
+Maintainer: Alexander GQ Gerasiov 
 Build-Depends: cmake,
curl ,
debhelper (>= 10),
diff -Nru clickhouse-18.16.1+ds/debian/patches/gcc10-ftbfs.patch 
clickhouse-18.16.1+ds/debian/patches/gcc10-ftbfs.patch
--- clickhouse-18.16.1+ds/debian/patches/gcc10-ftbfs.patch  1969-12-31 
16:00:00.0 -0800
+++ clickhouse-18.16.1+ds/debian/patches/gcc10-ftbfs.patch  2020-07-27 
17:59:46.0 -0700
@@ -0,0 +1,16 @@
+Description: fix missing C++ include, exposed by toolchain changes
+Author: Steve Langasek 
+Last-Update: 2020-07-27
+
+Index: clickhouse-18.16.1+ds/dbms/src/Interpreters/addMissingDefaults.h
+===
+--- clickhouse-18.16.1+ds.orig/dbms/src/Interpreters/addMissingDefaults.h
 clickhouse-18.16.1+ds/dbms/src/Interpreters/addMissingDefaults.h
+@@ -1,6 +1,7 @@
+ #pragma once
+ 
+ #include 
++#include 
+ 
+ 
+ namespace DB
diff -Nru clickhouse-18.16.1+ds/debian/patches/series 
clickhouse-18.16.1+ds/debian/patches/series
--- clickhouse-18.16.1+ds/debian/patches/series 2020-03-29 19:55:51.0 
-0700
+++ clickhouse-18.16.1+ds/debian/patches/series 2020-07-27 16:26:21.0 
-0700
@@ -17,3 +17,4 @@
 0017-gcc9-mitigation-for-conditional-bug.patch
 fix-ftbfs.patch
 python3.patch
+gcc10-ftbfs.patch

Bug#966438: src:bambam: Autopkgtest fail wiht newer imagemagick*

[Bastien Roucariès]

Package: src:bambam
Version: 1.0.1+dfsg-1
Severity: serious
Justification: block imagemagick

Dear Maintainer,

Upgrading imagemagick fail due to autopkg test failling for your package. See 
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bambam/6448023/log.gz

Could you :
1. Fix the failure
2. Please in case of error take a screenshot convert it to png and print the 
png as base64 (help debugging)

Bastien

Bug#965307: marked as done (sssd-ad: Login issues with SSSD 2.3 for AD back end)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 14:36:49 +
with message-id 
and subject line Bug#965307: fixed in sssd 2.3.1-1
has caused the Debian Bug report #965307,
regarding sssd-ad: Login issues with SSSD 2.3 for AD back end
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.)


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

This locks me out of my systems.

$ sudo -l
[sudo] password for sam.morris@ad.domain.example: 
Sorry, try again.
[sudo] password for sam.morris@ad.domain.example: 
Sorry, try again.
[sudo] password for sam.morris@ad.domain.example: 
sudo: 3 incorrect password attempts

Each authentication attempt logs the following in sssd_pam.log:

(2020-07-16 18:08:38): [pam] [sysdb_search_user_by_upn_res] (0x0040): 
Search for upn [sam.morris@ad.domain.example] returns more than one result. One 
of the possible reasons can be that several users share the same email address.
(2020-07-16 18:08:38): [pam] [sysdb_search_user_by_upn] (0x0040): Error: 22 
(Invalid argument)
(2020-07-16 18:08:38): [pam] [sysdb_initgroups_by_upn] (0x0040): 
sysdb_search_user_by_upn() failed.
(2020-07-16 18:08:38): [pam] [cache_req_search_cache] (0x0020): CR #12: 
Unable to lookup [sam.morris@ad.domain.example] in cache [22]: Invalid argument
(2020-07-16 18:08:38): [pam] [pam_check_user_search_next] (0x0020): Fatal 
error, killing connection!

My user exists in an Active Directory domain that has a one-way trust
established via FreeIPA.

We do indeed have several users with the same email address. That's
(until now) been a perfectly valid setup (one human has several accounts
for performing different roles and they all have the same email
address).

Downgrading to 2.2.3-3 fixes the problem. It's necessary to remove the
sssd database after downgrading.

I've had a quick scan of the commits between 2.2.3 and 2.3.0 and
nothing's jumped out at me yet. I'll take another look later...

-- System Information:
Debian Release: 10.3
  APT prefers stable-debug
  APT policy: (570, 'stable-debug'), (570, 'stable'), (550, 'testing-debug'), 
(550, 'testing'), (530, 'unstable-debug'), (530, 'unstable'), (500, 
'stable-updates'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: default

Versions of packages sssd depends on:
ii  python3-sss  2.3.0-2
ii  sssd-ad  2.3.0-2
ii  sssd-common  2.3.0-2
ii  sssd-ipa 2.3.0-2
ii  sssd-krb52.3.0-2
ii  sssd-ldap2.3.0-2
ii  sssd-proxy   2.3.0-2

sssd recommends no packages.

sssd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sssd
Source-Version: 2.3.1-1
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated sssd 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: Tue, 28 Jul 2020 17:14:55 +0300
Source: sssd
Architecture: source
Version: 2.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian SSSD Team 
Changed-By: Timo Aaltonen 
Closes: 965143 965307
Changes:
 sssd (2.3.1-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #965307, #965143)
   * source: Extend diff-ignore.
   * rules: Set --with-libwbclient.
   * control: Add libsofthsm2 to build-depends for tests.
Checksums-Sha1:
 d2e05108cde8b08ff386d6a6d30889802b7f37bb 4928 sssd_2.3.1-1.dsc
 1353876df07b64254bb3019e0911b540a060cc21 7186526 sssd_2.3.1.orig.tar.gz
 ba5b24781b3a2dfcb195e36d1cd55795b71bc674 488 sssd_2.3.1.orig.tar.gz.asc
 

Bug#965143: marked as done (sssd: SSSD 2.3 won't let log in or use sudo)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 14:36:49 +
with message-id 
and subject line Bug#965143: fixed in sssd 2.3.1-1
has caused the Debian Bug report #965143,
regarding sssd: SSSD 2.3 won't let log in or use sudo
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.)


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

This locks me out of my systems.

$ sudo -l
[sudo] password for sam.morris@ad.domain.example: 
Sorry, try again.
[sudo] password for sam.morris@ad.domain.example: 
Sorry, try again.
[sudo] password for sam.morris@ad.domain.example: 
sudo: 3 incorrect password attempts

Each authentication attempt logs the following in sssd_pam.log:

(2020-07-16 18:08:38): [pam] [sysdb_search_user_by_upn_res] (0x0040): 
Search for upn [sam.morris@ad.domain.example] returns more than one result. One 
of the possible reasons can be that several users share the same email address.
(2020-07-16 18:08:38): [pam] [sysdb_search_user_by_upn] (0x0040): Error: 22 
(Invalid argument)
(2020-07-16 18:08:38): [pam] [sysdb_initgroups_by_upn] (0x0040): 
sysdb_search_user_by_upn() failed.
(2020-07-16 18:08:38): [pam] [cache_req_search_cache] (0x0020): CR #12: 
Unable to lookup [sam.morris@ad.domain.example] in cache [22]: Invalid argument
(2020-07-16 18:08:38): [pam] [pam_check_user_search_next] (0x0020): Fatal 
error, killing connection!

My user exists in an Active Directory domain that has a one-way trust
established via FreeIPA.

We do indeed have several users with the same email address. That's
(until now) been a perfectly valid setup (one human has several accounts
for performing different roles and they all have the same email
address).

Downgrading to 2.2.3-3 fixes the problem. It's necessary to remove the
sssd database after downgrading.

I've had a quick scan of the commits between 2.2.3 and 2.3.0 and
nothing's jumped out at me yet. I'll take another look later...

-- System Information:
Debian Release: 10.3
  APT prefers stable-debug
  APT policy: (570, 'stable-debug'), (570, 'stable'), (550, 'testing-debug'), 
(550, 'testing'), (530, 'unstable-debug'), (530, 'unstable'), (500, 
'stable-updates'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: default

Versions of packages sssd depends on:
ii  python3-sss  2.3.0-2
ii  sssd-ad  2.3.0-2
ii  sssd-common  2.3.0-2
ii  sssd-ipa 2.3.0-2
ii  sssd-krb52.3.0-2
ii  sssd-ldap2.3.0-2
ii  sssd-proxy   2.3.0-2

sssd recommends no packages.

sssd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sssd
Source-Version: 2.3.1-1
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated sssd 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: Tue, 28 Jul 2020 17:14:55 +0300
Source: sssd
Architecture: source
Version: 2.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian SSSD Team 
Changed-By: Timo Aaltonen 
Closes: 965143 965307
Changes:
 sssd (2.3.1-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #965307, #965143)
   * source: Extend diff-ignore.
   * rules: Set --with-libwbclient.
   * control: Add libsofthsm2 to build-depends for tests.
Checksums-Sha1:
 d2e05108cde8b08ff386d6a6d30889802b7f37bb 4928 sssd_2.3.1-1.dsc
 1353876df07b64254bb3019e0911b540a060cc21 7186526 sssd_2.3.1.orig.tar.gz
 ba5b24781b3a2dfcb195e36d1cd55795b71bc674 488 sssd_2.3.1.orig.tar.gz.asc
 

Bug#966437: bambam: autopkgtest failure with imagemagick 8:6.9.11.24+dfsg-1

[Adrian Bunk]

Source: bambam
Version: 1.0.1+dfsg-1
Severity: serious
Tags: bullseye sid

https://ci.debian.net/packages/b/bambam/unstable/amd64/

Test success with imagemagick < 8:6.9.11.24+dfsg-1:
...
On attempt 5 the average screen color was too close to white: 233,230,235.
On attempt 6 the average screen color was too close to white: 225,223,231.
On attempt 7 the average screen color was too close to white: 223,220,226.
...

Test failure with imagemagick 8:6.9.11.24+dfsg-1:
...
On attempt 37 the average screen color was srgb(98.0209%,98.0209%,98.0209%).
On attempt 38 the average screen color was srgb(98.0209%,98.0209%,98.0209%).
On attempt 39 the average screen color was srgb(98.0209%,98.0209%,98.0209%).
Traceback (most recent call last):
  File "./debian/tests/smoke-meat", line 101, in 
main()
  File "./debian/tests/smoke-meat", line 24, in main
await_startup()
  File "./debian/tests/smoke-meat", line 45, in await_startup
raise Exception('Failed to see bambam start after %d attempts.' % 
attempt_count)
Exception: Failed to see bambam start after 40 attempts.


I suspect the output of convert changed that is parsed in
https://sources.debian.org/src/bambam/1.0.1+dfsg-1/debian/tests/smoke-meat/#L83

Bug#966436: ruby-mini-magick FTBFS with imagemagick 8:6.9.11.24+dfsg-1

[Adrian Bunk]

Source: ruby-mini-magick
Version: 4.9.5-2
Severity: serious
Tags: ftbfs

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

...
Failures:

  1) With ImageMagick MiniMagick::Image#details when verbose information 
includes a clipping path does not hang when parsing verbose data
 Failure/Error: details_hash[last_key] << line

 NoMethodError:
   undefined method `<<' for #
   Did you mean?  <
 # ./lib/mini_magick/image/info.rb:139:in `block in details'
 # ./lib/mini_magick/image/info.rb:128:in `each'
 # ./lib/mini_magick/image/info.rb:128:in `each_with_object'
 # ./lib/mini_magick/image/info.rb:128:in `details'
 # ./lib/mini_magick/image/info.rb:31:in `[]'
 # ./lib/mini_magick/image.rb:141:in `block in attribute'
 # ./spec/lib/mini_magick/image_spec.rb:478:in `block (7 levels) in '
 # ./spec/lib/mini_magick/image_spec.rb:477:in `block (6 levels) in '
 # ./spec/spec_helper.rb:19:in `block (3 levels) in '

Finished in 1 minute 34.34 seconds (files took 21.52 seconds to load)
76 examples, 1 failure
...

Bug#966435: autopkg test fails on arm64, triggered by gcc-defaults

[Matthias Klose]

Package: sec:automake-1.16
Version: 1:1.16.2-3
Severity: serious
Tags: sid bullseye

Looking at the autopkg tests, I see:

FAIL: t/vala-mix2.sh

this looks unrelated to the gcc-defaults change

Bug#966433: seqan autopkg test failures triggered by gcc-defaults

[Matthias Klose]

Package: src:seqan
Version: 3.0.1+ds-10
Severity: serious
Tags: sid bullseye

seqan autopkg test failures triggered by gcc-defaults, this doesn't seem to be
related to GCC 10.

https://ci.debian.net/data/autopkgtest/testing/amd64/s/seqan3/6396315/log.gz

/usr/include/seqan3/alphabet/concept.hpp:441:62: error: wrong number of template
arguments (2, should be 3)
  441 | remove_cvref_t,
  |  ^

Bug#966432: wcslib test failures with GCC 10

[Matthias Klose]

Package: src:wcslib
Version: 7.3+ds-2
Severity: serious
Tags: sid bullseye

gcc-defaults triggers test failures for wcslib, both on amd64 and arm64:

autopkgtest [01:49:15]: test wcslib-test-Fortran: [---
+ Test: tlin +
Testing WCSLIB linear transformation routines (tlin.f)
--

PIX 1:  303.  265.  112.4000  144.5000   28.2000
PIX 2:   19.   57.2.   15.   42.

IMG 1:   61.8000   74.7500  164.5600   74.2500  152.3200
IMG 2: -403.8000 -730.2500 -210.8000 -508.5000  229.6000

PIX 1:  303.  265.  112.4000  144.5000   28.2000
PIX 2:   19.   57.2.   15.   42.

LINP2X/LINX2P: Maximum closure residual = 5.7E-14 pixel.

PASS: All closure residuals are within reporting tolerance.
tdis1.f:151:37:

  143 |   STATUS = WCSGTI (WCS, WCS_LIN, LIN)
  | 2
..
  151 |   STATUS = WCSGTI (WCS, WCS_LNG, ILNG)
  | 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2)
(rank-1 and scalar)
tdis1.f:152:37:

  143 |   STATUS = WCSGTI (WCS, WCS_LIN, LIN)
  | 2
..
  152 |   STATUS = WCSGTI (WCS, WCS_LAT, ILAT)
  | 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2)
(rank-1 and scalar)

Bug#963760: new upstream release (1.4.10)

[Daniel Baumann]

severity 963760 serious
thanks

Hi,

what's the status of this?

Regards,
Daniel

Processed: Re: new upstream release (1.4.10)

[Debian Bug Tracking System]

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

> severity 963760 serious
Bug #963760 [ceph] new upstream release (1.4.10)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: reassign 966428 to src:sbuild

[Debian Bug Tracking System]

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

> reassign 966428 src:sbuild 0.79.1-1
Bug #966428 [src_sbuild] sbuild autopkg test fails with dpkg 1.20.x
Warning: Unknown package 'src_sbuild'
Bug reassigned from package 'src_sbuild' to 'src:sbuild'.
No longer marked as found in versions 0.79.1-1.
Ignoring request to alter fixed versions of bug #966428 to the same values 
previously set
Bug #966428 [src:sbuild] sbuild autopkg test fails with dpkg 1.20.x
Marked as found in versions sbuild/0.79.1-1.
> thanks
Stopping processing here.

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

Bug#966428: sbuild autopkg test fails with dpkg 1.20.x

[Matthias Klose]

Package: src_sbuild
Version: 0.79.1-1
Severity: serious
Tags: sid bullseye patch

The sbuild autopkg test fails with dpkg 1.20.x, preventing migration of dpkg.

patch at
http://launchpadlibrarian.net/490472280/sbuild_0.79.1-1ubuntu1_0.79.1-1ubuntu2.diff.gz

Bug#966417: vg: FTBFS in sid, with new elfutils

[Gianfranco Costamagna]

tags: patch
Hello,


I confirm the patch works correctly, the build finished in Ubuntu

https://launchpad.net/ubuntu/+source/vg/1.25.0+ds-2ubuntu1/+build/19650765

G.

Bug#966406: pygame-sdl2: diff for NMU version 7.3.3-1.1

[Adrian Bunk]

On Tue, Jul 28, 2020 at 01:31:48PM +0200, Markus Koschany wrote:
> Hello Adrian,

Hello Markus,

> Am 28.07.20 um 07:42 schrieb Adrian Bunk:
> > Package: pygame-sdl2
> > Version: 7.3.3-1
> > Severity: normal
> > Tags: patch  pending
> > 
> > Dear maintainer,
> > 
> > I've prepared an NMU for pygame-sdl2 (versioned as 7.3.3-1.1) and 
> > uploaded it to DELAYED/14. Please feel free to tell me if I should 
> > cancel it.
>...
> I appreciate your general bug triaging work but I don't think a NMU was
> necessary in this case.
>...
> A simple message to a bug report would have sufficed.

an upload to DELAYED/14 is in practice the same as a message to the bug 
report, plus an NMU if no reply arrives within 2 weeks.

I've now cancelled the NMU from DELAYED.

> Markus

cu
Adrian

Bug#966424: inxi: Running latest sid version I get many "Global symbol (did you forget to declare " errors

[Elimar Riesebieter]

Package: inxi
Version: 3.1.05-1-1
Severity: grave
Justification: renders package unusable

Dear maintainer,

Running inxi I get:

$ inxi -F
Global symbol "%row" requires explicit package name (did you forget to declare 
"my %row"?) at /bin/inxi line 8749.
[...]
Global symbol "@rows" requires explicit package name (did you forget to declare 
"my @rows"?) at /bin/inxi line 8817.
Global symbol "$smartctl_missing" requires explicit package name (did you 
forget to declare "my $smartctl_missing"?) at /bin/inxi line 8856.
Global symbol "@by_id" requires explicit package name (did you forget to 
declare "my @by_id"?) at /bin/inxi line 8938.
[...]
Global symbol "@by_path" requires explicit package name (did you forget to 
declare "my @by_path"?) at /bin/inxi line 8946.
Global symbol "@by_id" requires explicit package name (did you forget to 
declare "my @by_id"?) at /bin/inxi line 8999.
[...]
Global symbol "@by_path" requires explicit package name (did you forget to 
declare "my @by_path"?) at /bin/inxi line 9570.
Global symbol "@by_id" requires explicit package name (did you forget to 
declare "my @by_id"?) at /bin/inxi line 9683.
Global symbol "@vendors" requires explicit package name (did you forget to 
declare "my @vendors"?) at /bin/inxi line 9709.
[...]
Global symbol "$b_nvme" requires explicit package name (did you forget to 
declare "my $b_nvme"?) at /bin/inxi line 10049.
Global symbol "$nvme" requires explicit package name (did you forget to declare 
"my $nvme"?) at /bin/inxi line 10052.
[...]
Global symbol "$b_hddtemp" requires explicit package name (did you forget to 
declare "my $b_hddtemp"?) at /bin/inxi line 10071.
Global symbol "$hddtemp" requires explicit package name (did you forget to 
declare "my $hddtemp"?) at /bin/inxi line 10074.
[...]
Unmatched right curly bracket at /bin/inxi line 10203, at end of line
/bin/inxi has too many errors.


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

Kernel: Linux 5.4.53-toy-lxtec-amd64 (SMP w/8 CPU threads)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages inxi depends on:
ii  pciutils  1:3.7.0-2
ii  perl  5.30.3-4
ii  procps2:3.3.16-5

Versions of packages inxi recommends:
ii  bind9-dnsutils [dnsutils]  1:9.16.4-1
ii  dmidecode  3.2-3
ii  dnsutils   1:9.16.4-1
ii  file   1:5.38-5
ii  hddtemp0.3-beta15-53
ii  iproute2   5.7.0-1
ii  kmod   27+20200310-2
ii  lm-sensors 1:3.6.0-2
pn  mesa-utils 
ii  net-tools  1.60+git20180626.aebd88e-1
ii  sudo   1.9.1-2
pn  tree   
ii  usbutils   1:012-2
pn  x11-utils  
pn  x11-xserver-utils  

Versions of packages inxi suggests:
ii  curl  7.68.0-1+b1
pn  libcpanel-json-xs-perl | libjson-xs-perl  
pn  libxml-dumper-perl
ii  perl [libhttp-tiny-perl]  5.30.3-4
ii  wget  1.20.3-1+b3

-- no debconf information

Processed: forcibly merging 964433 964662

[Debian Bug Tracking System]

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

> forcemerge 964433 964662
Bug #964433 {Done: Timo Aaltonen } [libtomcat9-java] 
libtomcat9-java: tomcatjss fails to build with the latest libtomcat9-java
Bug #964662 [libtomcat9-java] tomcatjss: FTBFS: [javac] 
/<>/tomcat-8.5/src/org/dogtagpki/tomcat/JSSImplementation.java:25: 
error: package org.apache.tomcat.util.net.jsse does not exist
Severity set to 'important' from 'serious'
Marked Bug as done
The source tomcat9 and version 9.0.37-2 do not appear to match any binary 
packages
Marked as fixed in versions tomcat9/9.0.37-2.
Marked as found in versions tomcat9/9.0.37-1.
Bug #964433 {Done: Timo Aaltonen } [libtomcat9-java] 
libtomcat9-java: tomcatjss fails to build with the latest libtomcat9-java
Added tag(s) experimental, ftbfs, sid, and bullseye.
Merged 964433 964662
> thanks
Stopping processing here.

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

Processed: reassign 964662 to libtomcat9-java

[Debian Bug Tracking System]

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

> reassign 964662 libtomcat9-java
Bug #964662 [src:tomcatjss] tomcatjss: FTBFS: [javac] 
/<>/tomcat-8.5/src/org/dogtagpki/tomcat/JSSImplementation.java:25: 
error: package org.apache.tomcat.util.net.jsse does not exist
Bug reassigned from package 'src:tomcatjss' to 'libtomcat9-java'.
No longer marked as found in versions tomcatjss/7.4.1-1.
Ignoring request to alter fixed versions of bug #964662 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#966421: libjpeg-turbo FTBFS on alpha/mips64el/powerpc/sparc64: test failures

[Adrian Bunk]

Source: libjpeg-turbo
Version: 1:2.0.2-1~exp1
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/package.php?p=libjpeg-turbo

...
177/302 Test  #83: djpeg-shared-3x2-float-prog-cmp ...***Failed 
   0.01 sec
testout_3x2_float.ppm: FAILED.  Checksum is f6bfab038438ed8f5522fbd33595dcdc
...
267/302 Test #234: djpeg-static-3x2-float-prog-cmp ...***Failed 
   0.01 sec
testout_3x2_float.ppm: FAILED.  Checksum is f6bfab038438ed8f5522fbd33595dcdc
...
99% tests passed, 2 tests failed out of 302

Total Test time (real) = 186.96 sec

The following tests FAILED:
 83 - djpeg-shared-3x2-float-prog-cmp (Failed)
234 - djpeg-static-3x2-float-prog-cmp (Failed)
Errors while running CTest
make[1]: *** [Makefile:121: test] Error 8


For determining the correct md5 of expected test results
libjpeg-turbo wrongly guesses for some architectures.

This is fixed by the first commit in
https://salsa.debian.org/debian/libjpeg-turbo/-/merge_requests/2

Processed: opensc: Fails to build due to missing bash_completion files

[Debian Bug Tracking System]

Processing control commands:

> tags 953533 patch
Bug #953533 [src:opensc] opensc: Fails to build due to missing bash_completion 
files
Added tag(s) patch.

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

Bug#953533: opensc: Fails to build due to missing bash_completion files

[Kentaro Hayashi]

Control: tags 953533 patch

Bug#966406: pygame-sdl2: diff for NMU version 7.3.3-1.1

[Markus Koschany]

Hello Adrian,

Am 28.07.20 um 07:42 schrieb Adrian Bunk:
> Package: pygame-sdl2
> Version: 7.3.3-1
> Severity: normal
> Tags: patch  pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for pygame-sdl2 (versioned as 7.3.3-1.1) and 
> uploaded it to DELAYED/14. Please feel free to tell me if I should 
> cancel it.
> 
> renpy has already been broken by several other removals.
> 
> cu
> Adrian

I appreciate your general bug triaging work but I don't think a NMU was
necessary in this case. The last time I checked renpy in unstable it was
playable with the version of pygame-sdl2 in unstable. If more Python 2
modules have been removed and renpy is unplayable now, then we can
upload pygame-sdl2 from experimental to unstable. However pygame-sdl2 is
only relevant in the context of renpy, there was no other reason to
package it for Debian. A simple message to a bug report would have sufficed.

Markus




signature.asc
Description: OpenPGP digital signature

Processed: found 966409 in 1:1.5.2-2

[Debian Bug Tracking System]

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

> found 966409 1:1.5.2-2
Bug #966409 [src:libjpeg-turbo] libjpeg-turbo: versions in debian/*.symbols 
files are missing the epochs
Bug #966419 [src:libjpeg-turbo] libjpeg-turbo: versions in debian/*.symbols 
files are missing the epochs
Marked as found in versions libjpeg-turbo/1:1.5.2-2.
Marked as found in versions libjpeg-turbo/1:1.5.2-2.
> thanks
Stopping processing here.

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

Processed: forcibly merging 966409 966419

[Debian Bug Tracking System]

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

> forcemerge 966409 966419
Bug #966409 [src:libjpeg-turbo] libjpeg-turbo: versions in debian/*.symbols 
files are missing the epochs
Bug #966419 [src:libjpeg-turbo] libjpeg-turbo: versions in debian/*.symbols 
files are missing the epochs
Bug #966419 [src:libjpeg-turbo] libjpeg-turbo: versions in debian/*.symbols 
files are missing the epochs
Merged 966409 966419
> thanks
Stopping processing here.

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

Processed: forcibly merging 966409 966419

[Debian Bug Tracking System]

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

> forcemerge 966409 966419
Bug #966409 [src:libjpeg-turbo] libjpeg-turbo: versions in debian/*.symbols 
files are missing the epochs
Bug #966419 [src:libjpeg-turbo] libjpeg-turbo: versions in debian/*.symbols 
files are missing the epochs
Merged 966409 966419
> thanks
Stopping processing here.

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

Processed: block 960684 with 960120

[Debian Bug Tracking System]

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

> block 960684 with 960120
Bug #960684 [ftp.debian.org] RM: node-babel-plugin-transform-builtin-extend -- 
ROM; Useless with node-babel7
960684 was not blocked by any bugs.
960684 was not blocking any bugs.
Added blocking bug(s) of 960684: 960120
> thanks
Stopping processing here.

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

Bug#957502: marked as done (logtool: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 10:48:43 +
with message-id 
and subject line Bug#957502: fixed in logtool 1.2.8-11
has caused the Debian Bug report #957502,
regarding logtool: ftbfs with GCC-10
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.)


-- 
957502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:logtool
Version: 1.2.8-10
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/logtool_1.2.8-10_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
/usr/bin/ld: mod_unknown.o:/<>/src/mods.h:51: multiple definition 
of `ltm_use_syslog'; readconf.o:/<>/src/mods.h:51: first defined 
here
/usr/bin/ld: mod_unknown.o:/<>/src/includes.h:41: multiple 
definition of `h'; readconf.o:/<>/src/includes.h:41: first defined 
here
/usr/bin/ld: mod_iptables.o:/<>/src/logtool.h:104: multiple 
definition of `event'; readconf.o:/<>/src/logtool.h:104: first 
defined here
/usr/bin/ld: mod_iptables.o:/<>/src/logtool.h:159: multiple 
definition of `cf'; readconf.o:/<>/src/logtool.h:159: first 
defined here
/usr/bin/ld: mod_iptables.o:/<>/src/mods.h:87: multiple definition 
of `it'; readconf.o:/<>/src/mods.h:87: first defined here
/usr/bin/ld: mod_iptables.o:/<>/src/logtool.h:243: multiple 
definition of `reg'; readconf.o:/<>/src/logtool.h:243: first 
defined here
/usr/bin/ld: mod_iptables.o:/<>/src/logtool.h:136: multiple 
definition of `color'; readconf.o:/<>/src/logtool.h:136: first 
defined here
/usr/bin/ld: mod_iptables.o:/<>/src/mods.h:69: multiple definition 
of `sn'; readconf.o:/<>/src/mods.h:69: first defined here
/usr/bin/ld: mod_iptables.o:/<>/src/mods.h:53: multiple definition 
of `ltm_use_sudo'; readconf.o:/<>/src/mods.h:53: first defined here
/usr/bin/ld: mod_iptables.o:/<>/src/mods.h:52: multiple definition 
of `ltm_use_snort'; readconf.o:/<>/src/mods.h:52: first defined 
here
/usr/bin/ld: mod_iptables.o:/<>/src/mods.h:51: multiple definition 
of `ltm_use_syslog'; readconf.o:/<>/src/mods.h:51: first defined 
here
/usr/bin/ld: mod_iptables.o:/<>/src/includes.h:41: multiple 
definition of `h'; readconf.o:/<>/src/includes.h:41: first defined 
here
/usr/bin/ld: mod_common.o:/<>/src/logtool.h:159: multiple 
definition of `cf'; readconf.o:/<>/src/logtool.h:159: first 
defined here
/usr/bin/ld: mod_common.o:/<>/src/logtool.h:104: multiple 
definition of `event'; readconf.o:/<>/src/logtool.h:104: first 
defined here
/usr/bin/ld: mod_common.o:/<>/src/logtool.h:243: multiple 
definition of `reg'; readconf.o:/<>/src/logtool.h:243: first 
defined here
/usr/bin/ld: mod_common.o:/<>/src/logtool.h:136: multiple 
definition of `color'; readconf.o:/<>/src/logtool.h:136: first 
defined here
/usr/bin/ld: mod_common.o:/<>/src/mods.h:87: multiple definition 
of `it'; readconf.o:/<>/src/mods.h:87: first defined here
/usr/bin/ld: mod_common.o:/<>/src/mods.h:69: multiple definition 
of `sn'; readconf.o:/<>/src/mods.h:69: first defined here
/usr/bin/ld: mod_common.o:/<>/src/mods.h:53: multiple definition 
of `ltm_use_sudo'; readconf.o:/<>/src/mods.h:53: first defined here
/usr/bin/ld: mod_common.o:/<>/src/mods.h:52: multiple definition 
of `ltm_use_snort'; readconf.o:/<>/src/mods.h:52: first defined 
here
/usr/bin/ld: mod_common.o:/<>/src/mods.h:51: multiple definition 
of `ltm_use_syslog'; readconf.o:/<>/src/mods.h:51: first defined 
here
/usr/bin/ld: mod_common.o:/<>/src/includes.h:41: multiple 
definition of `h'; 

Processed: severity of 960120 is serious

[Debian Bug Tracking System]

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

> severity 960120 serious
Bug #960120 [node-yarnpkg] node-yarnpkg: build with node-babel-loader 8.x 
(babel 7) fails
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#966417: vg: FTBFS in sid, with new elfutils

[Gianfranco Costamagna]

Source: vg
Version: 1.25.0+ds-2
Severity: serious

Hello, looks like elfutils dropped one library used by vg:

# We do not provide a libebl anymore, use libdw instead.
rm -f debian/tmp/usr/include/elfutils/libebl.h


causing now FTBFS in sid:
. ./source_me.sh && g++ -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now 
-I/usr/include/fastahack -I/<>/vg-1.25.0+ds/include -I. 
-I/<>/vg-1.25.0+ds/src -I/<>/vg-1.25.0+ds/src/unittest 
-I/<>/vg-1.25.0+ds/src/subcommand 
-I/<>/vg-1.25.0+ds/include/dynamic -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/smithwaterman -I/usr/include/vcflib 
-I/usr/include/smithwaterman -I/usr/include/fastahack -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -Werror=return-type -std=c++14 -ggdb -g -MMD -MP -g -O2 
-fdebug-prefix-map=/<>/vg-1.25.0+ds=. -fstack-protector-strong 
-Wformat -Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 
-msse4.1 -fopenmp -o test/build_graph test/build_graph.cpp -lvg 
-L/<>/vg-1.25.0+ds/lib /<>/vg-1.25.0+ds/lib/libvgio.a -lz 
-lgssw -lssw -lprotobuf -lsublinearLS -ldeflate -lpthread -ljansson -lncurses 
-lgcsa2 -lgbwtgraph -lgbwt -ldivsufsort -ldivsufsort64 -lraptor2 
-lpinchesandcacti -l3edgeconnected -lsonlib -lfml -llz4 -lstructures -lvw 
-lboost_program_options -lallreduce -lbdsg -lxg -lsdsl -lhandlegraph 
-lfastahack -lsmithwaterman -ldisorder -lvcflib -lsmithwaterman -ldisorder 
-lfastahack -lhts -ltabixpp -lcairo -ljansson -latomic -rdynamic -ldw -lelf 
-lebl -ldl -llzma -lrocksdb -lbz2 -ljemalloc 
/usr/bin/ld: cannot find -lebl


I don't know if this patch is enough to make it build correctly, it is still 
building here
diff -Nru vg-1.25.0+ds/debian/changelog vg-1.25.0+ds/debian/changelog
--- vg-1.25.0+ds/debian/changelog   2020-07-14 15:15:28.0 +0200
+++ vg-1.25.0+ds/debian/changelog   2020-07-28 12:11:33.0 +0200
@@ -1,3 +1,9 @@
+vg (1.25.0+ds-2.1) unstable; urgency=medium
+
+  * Fix build by not linking anymore libebl.a (Closes: #-1)
+
+ -- Gianfranco Costamagna   Tue, 28 Jul 2020 
12:11:33 +0200
+
 vg (1.25.0+ds-2) unstable; urgency=medium
 
   * Restrict architectures to build for. Closes: #964039.
diff -Nru vg-1.25.0+ds/debian/patches/use_packaged_elfutils 
vg-1.25.0+ds/debian/patches/use_packaged_elfutils
--- vg-1.25.0+ds/debian/patches/use_packaged_elfutils   2020-02-03 
13:26:00.0 +0100
+++ vg-1.25.0+ds/debian/patches/use_packaged_elfutils   2020-07-28 
12:11:25.0 +0200
@@ -7,7 +7,7 @@
  
  # We want to link against the elfutils libraries
 -LD_LIB_FLAGS += -ldwfl -ldw -ldwelf -lelf -lebl
-+LD_LIB_FLAGS += -ldw -lelf -lebl
++LD_LIB_FLAGS += -ldw -lelf
  
  # We get OpenMP the normal way, using whatever the compiler knows about
  CXXFLAGS += -fopenmp

Processed: Debian bug #957043

[Debian Bug Tracking System]

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

> forwarded 957043 https://github.com/uditha-atukorala/bitz-server/issues/19
Bug #957043 [src:bitz-server] bitz-server: ftbfs with GCC-10
Set Bug forwarded-to-address to 
'https://github.com/uditha-atukorala/bitz-server/issues/19'.
> --
Stopping processing here.

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

Processed: Debian bug #957371

[Debian Bug Tracking System]

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

> forwarded 957371 https://github.com/ipmitool/ipmitool/issues/220
Bug #957371 [src:ipmitool] ipmitool: ftbfs with GCC-10
Set Bug forwarded-to-address to 
'https://github.com/ipmitool/ipmitool/issues/220'.
> --
Stopping processing here.

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

Bug#957465: Upstream fix

[Harald Welte]

FYI: by now we also have tagged a number of 'gcc-10 compile fix' patch releases.

libosmocore 1.3.2
libosmo-sccp 1.2.1
osmo-bts 1.2.1
osmo-bsc 1.6.1
osmo-msc 1.6.2
osmo-iuh 0.6.1

So you have the choice of cherry-picking the gcc-10 compile fixes for those
pcakages, or to simply upgrade to those patch releases, which contain no changes
other than the gcc-10 compile fixes.

-- 
- Harald Weltehttp://laforge.gnumonks.org/

"Privacy in residential applications is a desirable marketing option."
  (ETSI EN 300 175-7 Ch. A6)

Bug#965353: marked as done (node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 08:34:59 +
with message-id 
and subject line Bug#965353: fixed in node-lodash 4.17.19+dfsg1-1
has caused the Debian Bug report #965353,
regarding node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: 
isArray is not defined
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.)


-- 
965353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-babel7
Version: 7.10.5+~cs65.71.38-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=node-babel7=all=7.10.5%2B~cs65.71.38-2=1595148206=0

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -f node_modules/@babel/code-frame
cd babel-plugin-dynamic-import-node && babeljs-7 src --out-dir lib
ReferenceError: /<>/babel-plugin-dynamic-import-node/src/index.js: 
isArray is not defined
at /usr/share/nodejs/lodash/_baseOrderBy.js:24:7
at arrayMap (/usr/share/nodejs/lodash/_arrayMap.js:19:21)
at baseOrderBy (/usr/share/nodejs/lodash/_baseOrderBy.js:23:17)
at /usr/share/nodejs/lodash/sortBy.js:48:10
at apply (/usr/share/nodejs/lodash/_apply.js:18:25)
at /usr/share/nodejs/lodash/_overRest.js:35:12
at PluginPass.exit 
(/usr/share/nodejs/@babel/core/lib/transformation/block-hoist-plugin.js:58:43)
at newFn (/usr/share/nodejs/@babel/traverse/lib/visitors.js:175:21)
at NodePath._call 
(/usr/share/nodejs/@babel/traverse/lib/path/context.js:55:20)
at NodePath.call 
(/usr/share/nodejs/@babel/traverse/lib/path/context.js:42:17) {
  code: 'BABEL_TRANSFORM_ERROR'
}
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: node-lodash
Source-Version: 4.17.19+dfsg1-1
Done: Pirate Praveen 

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-lodash 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: Tue, 28 Jul 2020 13:03:40 +0530
Source: node-lodash
Architecture: source
Version: 4.17.19+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Closes: 934706 965353
Changes:
 node-lodash (4.17.19+dfsg1-1) unstable; urgency=medium
 .
   * New upstream version 4.17.19+dfsg1 (manually update lodash-cli from git
 master as no upstream tag or no recent npm releases)
   * Include patch to add isArray as dependency of baseOrderBy in lodash-cli
 (Closes: #965353)
   * Update description to make it suitable for Debian (Closes: #934706)
Checksums-Sha1:
 0cdc50cb237d4f421ac484ec5a8e2d52b6e5eaf1 2598 node-lodash_4.17.19+dfsg1-1.dsc
 5a1dd444e6134e86e9442e0abb19b84249c08e4f 69460 
node-lodash_4.17.19+dfsg1.orig-lodash-cli.tar.xz
 ba3f4bb48bc3ca6e81a356fd97862ebcc6527239 666884 
node-lodash_4.17.19+dfsg1.orig.tar.xz
 39566eca5c6aeb8cda7e530762d3a33ef119fcde 6296 
node-lodash_4.17.19+dfsg1-1.debian.tar.xz
 184de845d6a406fd70c4a5fdd5cc8aea4c1b6c54 6833 
node-lodash_4.17.19+dfsg1-1_amd64.buildinfo
Checksums-Sha256:
 b002c0984adf667e78becc3a84711bc45b1501e197c804245b0bdd0dbc859348 2598 
node-lodash_4.17.19+dfsg1-1.dsc
 201e1be00f005378518688cb071ab76347d7e550caf73f5e1ee14546c2386ad1 69460 
node-lodash_4.17.19+dfsg1.orig-lodash-cli.tar.xz
 eefa45ae540e0946f74571d80d1e72daf290797270ad2173f39bf7d317c0a26d 666884 
node-lodash_4.17.19+dfsg1.orig.tar.xz
 cff1072a073b7a4ef58ac9cf806e89c88d966fe07cbc6bf93876453225bc6d7f 6296 
node-lodash_4.17.19+dfsg1-1.debian.tar.xz
 3abe8b5b1d0a056ec4b1ad65c5244761eadff3983e633bbdaab8a3245e518934 6833 
node-lodash_4.17.19+dfsg1-1_amd64.buildinfo
Files:
 b4cb5f79d78519d6fd80593bc131c2d2 2598 javascript optional 
node-lodash_4.17.19+dfsg1-1.dsc
 1b0550e6a89cab33930bf3d899666bcf 69460 javascript optional 
node-lodash_4.17.19+dfsg1.orig-lodash-cli.tar.xz
 5c333d30fee8a679cb5a957aaab23bf0 666884 javascript optional 
node-lodash_4.17.19+dfsg1.orig.tar.xz
 

Bug#966412: php-timer: FTBFS on i386: 16 test failures

[Andreas Beckmann]

Source: php-timer
Version: 5.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

php-timer/experimental FTBFS on i386 (but succeeds on amd64) while
php-timer/sid builds fine on both architectures.

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/php-timer-5.0.1'
phpunit --bootstrap src/autoload.php
PHPUnit 9.2.6 by Sebastian Bergmann and contributors.

Runtime:   PHP 7.4.5
Configuration: /build/php-timer-5.0.1/phpunit.xml

...FFF.F..42 / 42 (100%)

Time: 00:00.004, Memory: 4.00 MB

There were 16 failures:

1) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #18 ('59:59.900', -695067296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'59:59.900'
+'-12:3624.932'

/build/php-timer-5.0.1/tests/DurationTest.php:50

2) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #32 ('01:00:59.010', -635957296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'01:00:59.010'
+'-11:3624.042'

/build/php-timer-5.0.1/tests/DurationTest.php:50

3) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #31 ('01:00:59.001', -635966296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'01:00:59.001'
+'-11:3624.033'

/build/php-timer-5.0.1/tests/DurationTest.php:50

4) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #30 ('01:00:59.999', -634967396)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'01:00:59.999'
+'-11:3625.032'

/build/php-timer-5.0.1/tests/DurationTest.php:50

5) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #29 ('01:00:01.999', -692967396)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'01:00:01.999'
+'-12:3627.032'

/build/php-timer-5.0.1/tests/DurationTest.php:50

6) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #28 ('01:00:01.999', -692968296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'01:00:01.999'
+'-12:3627.031'

/build/php-timer-5.0.1/tests/DurationTest.php:50

7) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #27 ('01:00:01.990', -692977296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'01:00:01.990'
+'-12:3627.022'

/build/php-timer-5.0.1/tests/DurationTest.php:50

8) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #26 ('01:00:01.900', -693067296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'01:00:01.900'
+'-12:3626.932'

/build/php-timer-5.0.1/tests/DurationTest.php:50

9) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #25 ('01:00:01', -693967296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'01:00:01'
+'-12:3626.032'

/build/php-timer-5.0.1/tests/DurationTest.php:50

10) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #24 ('01:00:00', -694967296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'01:00:00'
+'-12:3625.032'

/build/php-timer-5.0.1/tests/DurationTest.php:50

11) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #23 ('59:59.010', -695957296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'59:59.010'
+'-12:3624.042'

/build/php-timer-5.0.1/tests/DurationTest.php:50

12) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #22 ('59:59.001', -695966296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'59:59.001'
+'-12:3624.033'

/build/php-timer-5.0.1/tests/DurationTest.php:50

13) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #21 ('59:59.999', -694967396)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'59:59.999'
+'-12:3625.032'

/build/php-timer-5.0.1/tests/DurationTest.php:50

14) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #20 ('59:59.999', -694968296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'59:59.999'
+'-12:3625.031'

/build/php-timer-5.0.1/tests/DurationTest.php:50

15) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #19 ('59:59.990', -694977296)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'59:59.990'
+'-12:3625.022'

/build/php-timer-5.0.1/tests/DurationTest.php:50

16) SebastianBergmann\Timer\DurationTest::testCanBeFormattedAsString with data 
set #33 ('01:59:59.999', -1389934692)
Failed asserting that two strings are identical.
--- Expected
+++ Actual
@@ @@
-'01:59:59.999'
+'-24:3650.065'

Bug#945467: Fix available (fwd)

[Jeremy Sanders]

Hi Andreas

Do you have time to look at this again? Sorry to bother you.

Thanks

Jeremy

PS Veusz plots timeseries data (referring to your question on the 
mailing list).


On 16/05/2020 21:23, Andreas Tille wrote:

Hi Jeremy,

please make sure to inject pristine-tar (according to Debian Science
policy).  I did so now.  Unfortunately the package does not build in
a pbuilder chroot:

...
dh_sip3
make[1]: Leaving directory '/build/veusz-3.2.1'
dh_install -O--buildsystem=pybuild
dh_install: warning: Cannot find (any matches for) 
"usr/lib/python3*/*-packages/veusz/helpers/*.cpython-[0-9]*[!d]m-*.so" (tried 
in ., debian/tmp)

dh_install: warning: python3-veusz.helpers missing files: 
usr/lib/python3*/*-packages/veusz/helpers/*.cpython-[0-9]*[!d]m-*.so
dh_install: error: missing files, aborting
make: *** [debian/rules:23: binary] Error 25
...

Kind regards

   Andreas.

On Sat, May 16, 2020 at 03:05:10PM +0300, Adrian Bunk wrote:

Andreas, could you sponssor that one?
You already sponsored the latest 2 uploads of this package.

Thanks
Adrian


- Forwarded message from Jeremy Sanders  -

Date: Fri, 17 Apr 2020 09:10:00 +0200
From: Jeremy Sanders 
To: 945...@bugs.debian.org
Subject: Bug#945467: Fix available
Resent-From: Jeremy Sanders 
Resent-To: debian-bugs-d...@lists.debian.org
Resent-Date: Fri, 17 Apr 2020 07:21:01 +

I've updated the version control to have the latest version of Veusz, 3.2.1,
which should fix this bug:
https://salsa.debian.org/science-team/veusz

It would be great if a developer with permissions could have a look and
consider uploading it.

Thanks

Jeremy

- End forwarded message -

Bug#964399: Should ganglia be removed?

[Raphael Hertzog]

Hi,

On Tue, 07 Jul 2020, Marcos Fouces wrote:
> I also done some work on ganglia-web and ganglia-linux-modules packages
> (also unpublished).
> 
> I believe that it is still a good piece of software that deserve its
> place on Debian so i would like to step up as uploader (co-uploaders
> welcome!) if needed.
> 
> I also would like to maintain it under pkg-security team umbrella.

Why pkg-security? It doesn't seem related to the team's purpose.

I can create you repositories in the "debian" namespace if you want but
I'd rather not add random packages to the pkg-security team...

Cheers,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS

Processed: Re: Bug#963822: numpy breaks scikit-learn autopkgtest: test_set_estimator_none[drop] fails

[Debian Bug Tracking System]

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

> reassign 963822 src:scikit-learn 0.22.2.post1+dfsg-7
Bug #963822 {Done: Christian Kastner } [src:numpy, 
src:scikit-learn] numpy breaks scikit-learn autopkgtest: 
test_set_estimator_none[drop] fails
Bug reassigned from package 'src:numpy, src:scikit-learn' to 'src:scikit-learn'.
No longer marked as found in versions numpy/1:1.19.0-1 and 
scikit-learn/0.22.2.post1+dfsg-7.
No longer marked as fixed in versions 0.23.1-1.
Bug #963822 {Done: Christian Kastner } [src:scikit-learn] 
numpy breaks scikit-learn autopkgtest: test_set_estimator_none[drop] fails
Marked as found in versions scikit-learn/0.22.2.post1+dfsg-7.
> fixed 963822 0.23.1-1
Bug #963822 {Done: Christian Kastner } [src:scikit-learn] 
numpy breaks scikit-learn autopkgtest: test_set_estimator_none[drop] fails
Marked as fixed in versions scikit-learn/0.23.1-1.
> affects 963822 numpy
Bug #963822 {Done: Christian Kastner } [src:scikit-learn] 
numpy breaks scikit-learn autopkgtest: test_set_estimator_none[drop] fails
Added indication that 963822 affects numpy
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was elb...@debian.org).
> usertag 963822 - breaks
Usertags were: breaks needs-update.
Usertags are now: needs-update.
> thanks
Stopping processing here.

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

Processed: Re: libxrdesktop-0.15-0: missing Breaks+Replaces: libxrdesktop-0.14-0

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.15.1-3
Bug #966216 {Done: =?utf-8?b?QW5kcmV3IExlZSAo5p2O5YGl56eLKQ==?= 
} [libxrdesktop-0.15-0] libxrdesktop-0.15-0: missing 
Breaks+Replaces: libxrdesktop-0.14-0
Marked as found in versions xrdesktop/0.15.1-3; no longer marked as fixed in 
versions xrdesktop/0.15.1-3 and reopened.

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

Bug#966216: libxrdesktop-0.15-0: missing Breaks+Replaces: libxrdesktop-0.14-0

[Andreas Beckmann]

Followup-For: Bug #966216
Control: found -1 0.15.1-3

Hi,

the Breaks+Replaces are wrongly versioned - you'll need (<< 0.15) to cover all 
the 0.14.* releases.


Andreas

Processed: add forwarded info

[Debian Bug Tracking System]

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

> forwarded 965353 https://github.com/lodash-archive/lodash-cli/pull/141
Bug #965353 [node-lodash] node-babel7 FTBFS: 
babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
Bug #966339 [node-lodash] node-babel7: FTBFS in sid
Set Bug forwarded-to-address to 
'https://github.com/lodash-archive/lodash-cli/pull/141'.
Set Bug forwarded-to-address to 
'https://github.com/lodash-archive/lodash-cli/pull/141'.
>
End of message, stopping processing here.

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

Processed: bug 957603 is forwarded to https://github.com/CanonicalLtd/netplan/pull/155

[Debian Bug Tracking System]

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

> forwarded 957603 https://github.com/CanonicalLtd/netplan/pull/155
Bug #957603 [src:netplan.io] netplan.io: ftbfs with GCC-10
Changed Bug forwarded-to-address to 
'https://github.com/CanonicalLtd/netplan/pull/155' from 
'https://bugs.launchpad.net/netplan/+bug/1875412'.
> thanks
Stopping processing here.

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

Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined

[Pirate Praveen]

Control: forwarded -1 
https://github.com/lodash-archive/lodash-cli/pull/141


On Sun, Jul 26, 2020 at 16:12, Nicolas Mora  
wrote:

I'm not sure yet if this would fix the bug but in all the build log
errors, I see that the file /usr/share/nodejs/lodash/_baseOrderBy.js 
is

always the source of the error.

The file _baseOrderBy.js in the package seems buggy for an unresolved 
reson.


File in node-lodash unstable package:
4.17.19+dfsg-1 _baseOrderBy.js https://paste.debian.net/1157886/

File in node-lodash bullseye package
4.17.15+dfsg-2 _baseOrderBy.js https://paste.debian.net/1157887/

In the unstable version, the call to isArray line 24 is the root of 
errors.


Also, I see that the upstream version 4.17.19 isn't tagged as latest
release, 4.17.16 is, maybe it's worth a try to package 4.17.16 
instead?


I think I found the correct way,

https://github.com/lodash-archive/lodash-cli/pull/141

and now node-babel7 built fine. I'll upload both now.

Bug#966236: marked as done (r-bioc-rsubread FTBFS with gcc 10)

[Debian Bug Tracking System]

Your message dated Tue, 28 Jul 2020 07:03:51 +
with message-id 
and subject line Bug#966236: fixed in r-bioc-rsubread 2.2.5-1
has caused the Debian Bug report #966236,
regarding r-bioc-rsubread FTBFS with gcc 10
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.)


-- 
966236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-rsubread
Version: 2.2.2-1
Severity: serious
Tags: ftbfs fixed-upstream

https://buildd.debian.org/status/package.php?p=r-bioc-rsubread

...
gcc -std=gnu99 -shared -L/usr/lib/R/lib -Wl,-z,relro -o Rsubread.so 
HelperFunctions.o LRMbase-index.o LRMchro-event.o LRMfile-io.o LRMhashtable.o 
LRMhelper.o LRMseek-zlib.o LRMsorted-hashtable.o R_wrapper.o RsimReads.o 
SNPCalling.o aligner.o atgcContent.o build-sam-index.o core-bigtable.o 
core-indel.o core-interface-aligner.o core-interface-subjunc.o core-junction.o 
core.o detection-calls.o detectionCall.o detectionCallAnnotation.o 
exon-algorithms.o exon-align-indel.o exon-align.o flattenAnnotations.o 
fullscan.o fusion-align.o gen_rand_reads.o gene-algorithms.o gene-value-index.o 
hashtable.o index-builder.o input-blc.o input-files.o interval_merge.o 
long-hashtable.o longread-mapping.o mergeVCF.o processExons.o propmapped.o 
qualityScores.o read-repair.o readSummary.o removeDupReads.o sam2bed.o 
sambam-file.o seek-zlib.o sorted-hashtable.o sublog.o tx-unique.o -lz -lpthread 
-DMAKE_FOR_EXON -L/usr/lib/R/lib -lR
/usr/bin/ld: 
detectionCallAnnotation.o:/<>/src/detectionCallAnnotation.c:54: 
multiple definition of `chr_num'; 
detectionCall.o:/<>/src/detectionCall.c:88: first defined here
/usr/bin/ld: 
detectionCallAnnotation.o:/<>/src/detectionCallAnnotation.c:51: 
multiple definition of `exon'; 
detectionCall.o:/<>/src/detectionCall.c:85: first defined here
/usr/bin/ld: 
detectionCallAnnotation.o:/<>/src/detectionCallAnnotation.c:52: 
multiple definition of `ir'; 
detectionCall.o:/<>/src/detectionCall.c:86: first defined here
/usr/bin/ld: 
detectionCallAnnotation.o:/<>/src/detectionCallAnnotation.c:55: 
multiple definition of `current_chr_id'; 
detectionCall.o:/<>/src/detectionCall.c:89: first defined here
/usr/bin/ld: processExons.o:/<>/src/processExons.c:62: multiple 
definition of `exon_file'; 
detectionCallAnnotation.o:/<>/src/detectionCallAnnotation.c:58: 
first defined here
collect2: error: ld returned 1 exit status
make[1]: *** [/usr/share/R/share/make/shlib.mk:6: Rsubread.so] Error 1


Upstream git says:
24 July 2020 - 2.2.5
(1) Fix errors reported by gcc-10.
--- End Message ---
--- Begin Message ---
Source: r-bioc-rsubread
Source-Version: 2.2.5-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-rsubread 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: Mon, 27 Jul 2020 11:44:20 +0200
Source: r-bioc-rsubread
Architecture: source
Version: 2.2.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 966236
Changes:
 r-bioc-rsubread (2.2.5-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #966236
   * debhelper-compat 13 (routine-update)
   * Remove trailing whitespace in debian/copyright (routine-update)
   * Trim trailing whitespace.
Checksums-Sha1:
 60e95cfdefa07f7d9555a2669969cea7d2df29c1 2090 r-bioc-rsubread_2.2.5-1.dsc
 933da69572d980307b8a7d25a60a30a74c733814 10826597 
r-bioc-rsubread_2.2.5.orig.tar.gz
 094fbefc8c83a0650901d5adc0cbe4dd0262ca79 3432 
r-bioc-rsubread_2.2.5-1.debian.tar.xz
 e7d68ecc695f0c9d48b356032b718355b403bb17 8903 
r-bioc-rsubread_2.2.5-1_amd64.buildinfo
Checksums-Sha256:
 27836f84f8c7d3b1ee9a89a38306a41a7b1d2c60bedd7e2136647ceb6873c45e 2090 
r-bioc-rsubread_2.2.5-1.dsc
 c4791391c471deca94dffbdd6d9982a1fa57ead724605d4198215870c52d 10826597 
r-bioc-rsubread_2.2.5.orig.tar.gz
 

Bug#966409: libjpeg-turbo: versions in debian/*.symbols files are missing the epochs

[Paul Wise]

Source: libjpeg-turbo
Version: 1:2.0.5-1
Severity: serious

The versions in the debian/*.symbols files are missing the epochs. This
means that packages using symbols newer than buster will not upgrade
libjpeg62-turbo and libturbojpeg0 when being upgraded to bullseye.

For example if I install bullseye libjpeg-turbo-progs on buster, the
programs will not work as libjpeg62-turbo and libturbojpeg0 will not be
upgraded so the new symbols like jpeg_write_icc_profile are missing.

$ rmadison -u debian libjpeg-turbo
libjpeg-turbo | 1:1.3.1-12| oldoldstable   | source
libjpeg-turbo | 1:1.5.1-2 | oldstable  | source
libjpeg-turbo | 1:1.5.2-2 | stable | source
libjpeg-turbo | 1:1.5.2-2 | testing| source
libjpeg-turbo | 1:1.5.2-2 | unstable   | source
libjpeg-turbo | 1:1.5.2-2 | unstable-debug | source
libjpeg-turbo | 1:2.0.5-1 | unstable   | source
libjpeg-turbo | 1:2.0.5-1 | unstable-debug | source

$ grep -v 1.3.1 debian/*.symbols | grep -v 1.2.90 | grep -v 1.4.0 | grep -v 
1.5.0
debian/libjpeg62-turbo.symbols:libjpeg.so.62 libjpeg62-turbo #MINVER#
debian/libjpeg62-turbo.symbols:* Build-Depends-Package: libjpeg62-turbo-dev
debian/libjpeg62-turbo.symbols: jpeg_read_icc_profile@LIBJPEG_6.2 2.0.2
debian/libjpeg62-turbo.symbols: jpeg_write_icc_profile@LIBJPEG_6.2 2.0.2
debian/libturbojpeg0.symbols:libturbojpeg.so.0 libturbojpeg0 #MINVER#
debian/libturbojpeg0.symbols:* Build-Depends-Package: libturbojpeg0-dev
debian/libturbojpeg0.symbols: TURBOJPEG_2.0@TURBOJPEG_2.0 2.0.2
debian/libturbojpeg0.symbols: tjGetErrorCode@TURBOJPEG_2.0 2.0.2
debian/libturbojpeg0.symbols: tjGetErrorStr2@TURBOJPEG_2.0 2.0.2
debian/libturbojpeg0.symbols: tjLoadImage@TURBOJPEG_2.0 2.0.2
debian/libturbojpeg0.symbols: tjSaveImage@TURBOJPEG_2.0 2.0.2

# cat /etc/apt/sources.list   
deb https://deb.debian.org/debian buster main

# apt -qq install libjpeg-turbo-progs
The following additional packages will be installed:
  libjpeg62-turbo libturbojpeg0
The following NEW packages will be installed:
  libjpeg-turbo-progs libjpeg62-turbo libturbojpeg0
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 266 kB/399 kB of archives.
After this operation, 1275 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libjpeg62-turbo:amd64.
(Reading database ... 12518 files and directories currently installed.)
Preparing to unpack .../libjpeg62-turbo_1%3a1.5.2-2+b1_amd64.deb ...
Unpacking libjpeg62-turbo:amd64 (1:1.5.2-2+b1) ...
Selecting previously unselected package libturbojpeg0:amd64.
Preparing to unpack .../libturbojpeg0_1%3a1.5.2-2+b1_amd64.deb ...
Unpacking libturbojpeg0:amd64 (1:1.5.2-2+b1) ...
Selecting previously unselected package libjpeg-turbo-progs.
Preparing to unpack .../libjpeg-turbo-progs_1%3a1.5.2-2+b1_amd64.deb ...
Unpacking libjpeg-turbo-progs (1:1.5.2-2+b1) ...
Setting up libturbojpeg0:amd64 (1:1.5.2-2+b1) ...
Setting up libjpeg62-turbo:amd64 (1:1.5.2-2+b1) ...
Setting up libjpeg-turbo-progs (1:1.5.2-2+b1) ...
Processing triggers for libc-bin (2.28-10) ...

# cat /etc/apt/sources.list | grep buster | sed s/buster/sid/ >> 
/etc/apt/sources.list

# cat /etc/apt/sources.list
deb https://deb.debian.org/debian buster main
deb https://deb.debian.org/debian sid main

# apt update
Hit:1 https://deb.debian.org/debian buster InRelease
Get:2 https://deb.debian.org/debian sid InRelease [146 kB]
Get:3 https://deb.debian.org/debian sid/main amd64 Packages [8345 kB]
Fetched 8491 kB in 6s (1365 kB/s)   


Reading package lists... Done
Building dependency tree   
Reading state information... Done
126 packages can be upgraded. Run 'apt list --upgradable' to see them.

# apt policy libjpeg-turbo-progs
libjpeg-turbo-progs:
  Installed: 1:1.5.2-2+b1
  Candidate: 1:2.0.5-1
  Version table:
 1:2.0.5-1 500
500 https://deb.debian.org/debian sid/main amd64 Packages
 *** 1:1.5.2-2+b1 500
500 https://deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status

# apt install libjpeg-turbo-progs=1:2.0.5-1
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  libjpeg-turbo-progs
1 upgraded, 0 newly installed, 0 to remove and 125 not upgraded.
Need to get 131 kB of archives.
After this operation, 51.2 kB of additional disk space will be used.
Get:1 https://deb.debian.org/debian sid/main amd64 libjpeg-turbo-progs amd64 
1:2.0.5-1 [131 kB]
Fetched 131 kB in 1s (227 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 12558 files and directories currently installed.)
Preparing to unpack .../libjpeg-turbo-progs_1%3a2.0.5-1_amd64.deb 

Bug#937442: pygame-sdl2: diff for NMU version 7.3.3-1.1

[Adrian Bunk]

Dear maintainer,

I've prepared an NMU for pygame-sdl2 (versioned as 7.3.3-1.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

renpy has already been broken by several other removals.

cu
Adrian
diff -Nru pygame-sdl2-7.3.3/debian/changelog pygame-sdl2-7.3.3/debian/changelog
--- pygame-sdl2-7.3.3/debian/changelog	2019-10-03 23:08:15.0 +0300
+++ pygame-sdl2-7.3.3/debian/changelog	2020-07-28 08:34:39.0 +0300
@@ -1,3 +1,10 @@
+pygame-sdl2 (7.3.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Upload to unstable.
+
+ -- Adrian Bunk   Tue, 28 Jul 2020 08:34:39 +0300
+
 pygame-sdl2 (7.3.3-1) experimental; urgency=medium
 
   * New upstream version 7.3.3.

Processed: forcibly merging 937442 966406

[Debian Bug Tracking System]

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

> forcemerge 937442 966406
Bug #937442 {Done: Markus Koschany } [src:pygame-sdl2] 
pygame-sdl2: Python2 removal in sid/bullseye
Bug #937442 {Done: Markus Koschany } [src:pygame-sdl2] 
pygame-sdl2: Python2 removal in sid/bullseye
Added tag(s) patch and pending.
Bug #966406 [src:pygame-sdl2] pygame-sdl2: diff for NMU version 7.3.3-1.1
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked as fixed in versions pygame-sdl2/7.3.3-1.
Marked as found in versions pygame-sdl2/7.3.2-1.
Added tag(s) fixed-in-experimental.
Merged 937442 966406
> thanks
Stopping processing here.

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

Processed: found 966346 in 0.8.2-2

[Debian Bug Tracking System]

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

> found 966346 0.8.2-2
Bug #966346 {Done: =?utf-8?q?St=C3=A9phane_Glondu?= } 
[libmlpost-ocaml-dev] libmlpost-ocaml-dev: impossible to install on debian sid 
due to unavailable dependency
Marked as found in versions mlpost/0.8.2-2.
> thanks
Stopping processing here.

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

Processed: tagging 966365

[Debian Bug Tracking System]

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

> tags 966365 + bullseye sid
Bug #966365 [shanty] shanty: Uninstallable due to removal of 
libgd-gd2-{,noxpm-}perl Provides in libgd-perl
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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