Processed: 957430 is forwarded

[Debian Bug Tracking System]

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

> forwarded 957430 ccp4-...@dl.ac.uk
Bug #957430 [src:libccp4] libccp4: ftbfs with GCC-10
Set Bug forwarded-to-address to 'ccp4-...@dl.ac.uk'.
> thanks
Stopping processing here.

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

Bug#957147: marked as done (docopt.cpp: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jul 2020 06:48:31 +
with message-id 
and subject line Bug#957147: fixed in docopt.cpp 0.6.2-2.1
has caused the Debian Bug report #957147,
regarding docopt.cpp: 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.)


-- 
957147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:docopt.cpp
Version: 0.6.2-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/docopt.cpp_0.6.2-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

[...]
/<>/docopt.h:46:9: note:   no known conversion for argument 1 from 
‘const char [43]’ to ‘docopt::DocoptLanguageError&&’
/<>/docopt.cpp: In function 
‘std::map, docopt::value> 
docopt::docopt_parse(const string&, const 
std::vector >&, bool, bool, bool)’:
/<>/docopt.cpp:622:41: error: no matching function for call to 
‘docopt::DocoptLanguageError::DocoptLanguageError(const char*)’
  622 |   throw DocoptLanguageError(error.what());
  | ^
In file included from /<>/docopt.cpp:9:
/<>/docopt.h:46:9: note: candidate: ‘constexpr 
docopt::DocoptLanguageError::DocoptLanguageError()’
   46 |  struct DocoptLanguageError : std::runtime_error { using 
runtime_error::runtime_error; };
  | ^~~
/<>/docopt.h:46:9: note:   candidate expects 0 arguments, 1 
provided
/<>/docopt.h:46:9: note: candidate: ‘constexpr 
docopt::DocoptLanguageError::DocoptLanguageError(const 
docopt::DocoptLanguageError&)’
/<>/docopt.h:46:9: note:   no known conversion for argument 1 from 
‘const char*’ to ‘const docopt::DocoptLanguageError&’
/<>/docopt.h:46:9: note: candidate: ‘constexpr 
docopt::DocoptLanguageError::DocoptLanguageError(docopt::DocoptLanguageError&&)’
/<>/docopt.h:46:9: note:   no known conversion for argument 1 from 
‘const char*’ to ‘docopt::DocoptLanguageError&&’
/<>/docopt.cpp:629:41: error: no matching function for call to 
‘docopt::DocoptArgumentError::DocoptArgumentError(const char*)’
  629 |   throw DocoptArgumentError(error.what());
  | ^
In file included from /<>/docopt.cpp:9:
/<>/docopt.h:49:9: note: candidate: ‘constexpr 
docopt::DocoptArgumentError::DocoptArgumentError()’
   49 |  struct DocoptArgumentError : std::runtime_error { using 
runtime_error::runtime_error; };
  | ^~~
/<>/docopt.h:49:9: note:   candidate expects 0 arguments, 1 
provided
/<>/docopt.h:49:9: note: candidate: ‘constexpr 
docopt::DocoptArgumentError::DocoptArgumentError(const 
docopt::DocoptArgumentError&)’
/<>/docopt.h:49:9: note:   no known conversion for argument 1 from 
‘const char*’ to ‘const docopt::DocoptArgumentError&’
/<>/docopt.h:49:9: note: candidate: ‘constexpr 
docopt::DocoptArgumentError::DocoptArgumentError(docopt::DocoptArgumentError&&)’
/<>/docopt.h:49:9: note:   no known conversion for argument 1 from 
‘const char*’ to ‘docopt::DocoptArgumentError&&’
/<>/docopt.cpp:653:63: error: no matching function for call to 
‘docopt::DocoptArgumentError::DocoptArgumentError(std::__cxx11::basic_string)’
  653 |   throw DocoptArgumentError("Unexpected argument: " + leftover);
  |   ^
In file included from /<>/docopt.cpp:9:
/<>/docopt.h:49:9: note: candidate: ‘constexpr 
docopt::DocoptArgumentError::DocoptArgumentError()’
   49 |  struct DocoptArgumentError : std::runtime_error { using 
runt

Bug#966432: marked as done (wcslib test failures with GCC 10)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jul 2020 06:35:03 +
with message-id 
and subject line Bug#966432: fixed in wcslib 7.3+ds-3
has caused the Debian Bug report #966432,
regarding wcslib test failures 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.)


-- 
966432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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)
--- End Message ---
--- Begin Message ---
Source: wcslib
Source-Version: 7.3+ds-3
Done: Ole Streicher 

We believe that the bug you reported is fixed in the latest version of
wcslib, 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.
Ole Streicher  (supplier of updated wcslib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 29 Jul 2020 16:02:43 +0200
Source: wcslib
Architecture: source
Version: 7.3+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Closes: 966432
Changes:
 wcslib (7.3+ds-3) unstable; urgency=medium
 .
   * Update Fortran CI test to pass on gcc-10. Closes: #966432
Checksums-Sha1:
 0f0d88dcd404a94d55f11c44be01c999e1b25711 2286 wcslib_7.3+ds-3.dsc
 a070c9ef4828bb16313595281acee3b09b83273e 12496 wcslib_7.3+ds-3.debian.tar.xz
Checksums-Sha256:
 4529f2c713439346ad9306231da7ad50a8ef4c4852704b9fb0434ea99c5ca0fa 2286 
wcslib_7.3+ds-3.dsc
 e13a33a52455c3bf28affefed02c96775140ab280d612847efb47d307bc51119 12496 
wcslib_7.3+ds-3.debian.tar.xz
Files:
 69f91f4ecbff351d76fa08d0e17f9e38 2286 science optional wcslib_7.3+ds-3.dsc
 f0d5b3537dc54a5d0b8d791d9b8fad07 12496 science optional 
wcslib_7.3+ds-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl8iZUAACgkQcRWv0HcQ
3Pf2Rw/9EvvUf+xi+hv/n00nvUTkzc3kA3DIEjA8Hnd4NwrCg6VO7XdAI4PN+7AT
+/90GrRSB3Z74cShTwwArherDKwmOdnIkYotftiAiW//AlsaUC5GWiN6s2QlMShQ
5tJOiC9OVhKBYsLFul8MPHYFIM9ydd0iQtV/Ud1+7Ax0Js4XHjWXyZ+sKcyerq74
IBbNgU6IICH+v3+U6YXzMQ5jww66JSLsgNgHHVpXSKLgcNyol/0Wj+gNuSBoap11
lxjuq1SHnV1LiW0IR5JSmc2We10iEDWB1Fpm4mVIE4hyqzqSD9XZhAZg3USBYV0A
oM10L/Y5Ui91fyZlGF/gsUnlUJgIKtIqOlydQPB0lhRXfehTrkyxURcTUIY/teWz
oiaFVn/ZyJUP6zjtVGlVrq3/AYPx+ZVd5BzZhhU3c6FqiJj1XJFpJ32yWeYaH0YX
kgxK7kEkwcT71goSxAEAS18dAoiixBx5yppuGak0FCT0ayDlzWMrq0zHCYVHx+3Z
KOjv9x5HEIMwiPtybetq7+77a9wFcthhqs9LUEo12r0/TpPgDo260rMK0XCIFBeI
re7Uo9KONUbTXEwn3W9V3CZTluWTxddZEe00XaQI739+lxlSN/HY31HQlETncdEv
KiCe45AbyofWMzEHl6tfEcSEjrEgB6x4dnLM5F9b0HPD7lmIP28=
=7010
-END PGP SIGNATURE End Message ---

Bug#957042: marked as done (biometric-authentication: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jul 2020 06:33:54 +
with message-id 
and subject line Bug#957042: fixed in biometric-authentication 0.9.63-1
has caused the Debian Bug report #957042,
regarding biometric-authentication: 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.)


-- 
957042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:biometric-authentication
Version: 0.9.62-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/biometric-authentication_0.9.62-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

[...]
/bin/bash ../../../../libtool  --tag=CC   --mode=link gcc -Wall -g -shared 
-fpic -I../../../../src/lib/ -I../../../../src/drivers/community-multidevice/ 
-DLOCALEDIR=\""/usr/share/locale"\" 
-DBIOMETRIC_DRIVER_COMMUNITY_MULTIDEVICE_DOMAIN_NAME=\""biometric-authentication"\"
  -I/usr/include/libfprint -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libusb-1.0   -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -lfprint -lglib-2.0 -lusb-1.0 -lsqlite3 
../../../lib/libbiometric.la -module -avoid-version -Wl,-z,now  -Wl,-z,relro 
-Wl,-z,now -o aes4000.la -rpath /usr/lib/biometric-authentication/drivers 
../../../../src/drivers/community-multidevice/aes4000_la-community_ops.lo 
../../../../src/drivers/community-multidevice/aes4000_la-aes_128_cfb.lo 
aes4000_la-aes4000.lo  -luuid -lglib-2.0 -lusb-1.0 -lsqlite3 -lpthread -lm -ldl 
libtool: link: gcc -shared  -fPIC -DPIC  
../../../../src/drivers/community-multidevice/.libs/elan_la-community_ops.o 
../../../../src/drivers/community-multidevice/.libs/elan_la-aes_128_cfb.o 
.libs/elan_la-elan.o   -Wl,-rpath -Wl,/<>/src/lib/.libs -lfprint 
../../../lib/.libs/libbiometric.so -luuid -lglib-2.0 -lusb-1.0 
/usr/lib/x86_64-linux-gnu/libsqlite3.so -lpthread -lm -ldl  -g -g -O2 
-fstack-protector-strong -Wl,-z -Wl,now -Wl,-z -Wl,relro -Wl,-z -Wl,now   
-pthread -Wl,-soname -Wl,elan.so -o .libs/elan.so
libtool: link: ( cd ".libs" && rm -f "elan.la" && ln -s "../elan.la" "elan.la" )
libtool: link: gcc -shared  -fPIC -DPIC  
../../../../src/drivers/community-multidevice/.libs/upekts_la-community_ops.o 
../../../../src/drivers/community-multidevice/.libs/upekts_la-aes_128_cfb.o 
.libs/upekts_la-upekts.o   -Wl,-rpath -Wl,/<>/src/lib/.libs 
-lfprint ../../../lib/.libs/libbiometric.so -luuid -lglib-2.0 -lusb-1.0 
/usr/lib/x86_64-linux-gnu/libsqlite3.so -lpthread -lm -ldl  -g -g -O2 
-fstack-protector-strong -Wl,-z -Wl,now -Wl,-z -Wl,relro -Wl,-z -Wl,now   
-pthread -Wl,-soname -Wl,upekts.so -o .libs/upekts.so
/bin/bash ../../../../libtool  --tag=CC   --mode=link gcc -Wall -g -shared 
-fpic -I../../../../src/lib/ -I../../../../src/drivers/community-multidevice/ 
-DLOCALEDIR=\""/usr/share/locale"\" 
-DBIOMETRIC_DRIVER_COMMUNITY_MULTIDEVICE_DOMAIN_NAME=\""biometric-authentication"\"
  -I/usr/include/libfprint -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libusb-1.0   -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -lfprint -lglib-2.0 -lusb-1.0 -lsqlite3 
../../../lib/libbiometric.la -module -avoid-version -Wl,-z,now  -Wl,-z,relro 
-Wl,-z,now -o aes2501.la -rpath /usr/lib/biometric-authentication/drivers 
../../../../src/drivers/community-multidevice/aes2501_la-community_ops.lo 
../../../../src/drivers/community-multid

Bug#966526: casacore: baseline violation on i386

[Adrian Bunk]

Source: casacore
Version: 2.2.0-1
Severity: serious
Tags: patch

SSE is not part of the baseline of the i386 port,
the following fixes the baseline violation:

--- debian/rules.old2020-07-28 15:12:17.759357834 +0300
+++ debian/rules2020-07-28 15:12:30.855360420 +0300
@@ -5,7 +5,7 @@
 
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 ifeq ($(DEB_HOST_ARCH_CPU),i386)
-export DEB_CXXFLAGS_MAINT_APPEND = -msse -msse2 -mfpmath=sse
+export DEB_CXXFLAGS_MAINT_APPEND = -ffloat-store
 endif
 ifeq ($(DEB_HOST_ARCH_OS),hurd)
 THREADS=OFF

Bug#966525: dmagnetic FTBFS on i386: check-sixel failed

[Adrian Bunk]

Source: dmagnetic
Version: 0.25-1
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/fetch.php?pkg=dmagnetic&arch=i386&ver=0.25-1&stamp=1595804868&raw=0

...
Initializing the 68K version 0 VM
check-high_ansi OK
*** dMagnetic 0.25
*** Use at your own risk
*** (C)opyright 2020 by det...@dettus.net
*

Using .ini file: dMagnetic.ini
Warning! -mag given, but not -gfx. Deducing filename
Initializing the 68K version 0 VM
check-sixel failed
make[1]: *** [checks.mk:104: check-sixel] Error 1


If exact floating points are required, the following fixes it:

--- debian/rules.old2020-07-30 09:01:53.400678013 +0300
+++ debian/rules2020-07-30 09:02:37.400712152 +0300
@@ -3,6 +3,9 @@
 export DH_VERBOSE = 1
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export DEB_CFLAGS_MAINT_APPEND  = -Wall -pedantic
+ifneq (,$(filter $(DEB_HOST_ARCH), i386))
+  export DEB_CFLAGS_MAINT_APPEND += -ffloat-store
+endif
 export SHA256_CMD=sha256sum
 #export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 #export DEB_RULES_REQUIRES_ROOT = ""

Bug#966523: r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’

[Adrian Bunk]

Source: r-bioc-rsubread
Version: 2.2.5-1
Severity: serious
Tags: ftbfs

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

...
In file included from /usr/lib/gcc/i686-linux-gnu/10/include/stdint.h:9,
 from HelperFunctions.h:139,
 from R_wrapper.c:35:
/usr/include/stdint.h:96:23: error: conflicting types for ‘uintptr_t’
   96 | typedef unsigned int  uintptr_t;
  |   ^
In file included from R_wrapper.c:30:
/usr/share/R/include/Rinterface.h:110:24: note: previous declaration of 
‘uintptr_t’ was here
  110 |  typedef unsigned long uintptr_t;
  |^
make[1]: *** [/usr/lib/R/etc/Makeconf:167: R_wrapper.o] Error 1

Bug#966522: libgetdata: binary-all FTBFS

[Adrian Bunk]

Source: libgetdata
Version: 0.10.0-8
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libgetdata&arch=all&ver=0.10.0-8&stamp=1596045626&raw=0

...
   dh_missing -i
dh_missing: warning: usr/include/getdata.mod exists in debian/tmp but is not 
installed to anywhere 
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: libf95getdata7 (2), libfgetdata6 (2), libgetdata++7 (2), 
libgetdata-dev (27), libgetdata-doc (190), libgetdata-perl (1), 
libgetdata-tools (4), libgetdata8 (2), python3-pygetdata (1)
 * dh_installdocs: libf95getdata7 (0), libfgetdata6 (0), libgetdata++7 
(0), libgetdata-dev (0), libgetdata-doc (3), libgetdata-perl (0), 
libgetdata-tools (0), libgetdata8 (0), python3-pygetdata (0)
 * dh_installman: libf95getdata7 (0), libfgetdata6 (0), libgetdata++7 
(0), libgetdata-dev (0), libgetdata-doc (0), libgetdata-perl (0), 
libgetdata-tools (0), libgetdata8 (0), python3-pygetdata (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make: *** [debian/rules:28: binary-indep] Error 25

Bug#957641: marked as done (openoverlayrouter: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jul 2020 04:03:35 +
with message-id 
and subject line Bug#957641: fixed in openoverlayrouter 1.3.0+ds1-3
has caused the Debian Bug report #957641,
regarding openoverlayrouter: 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.)


-- 
957641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openoverlayrouter
Version: 1.3.0+ds1-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/openoverlayrouter_1.3.0+ds1-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

[...]
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror=switch -std=gnu89 -g 
-I/usr/include/libxml2 -D_GNU_SOURCE -D_FORTIFY_SOURCE=2 -I. -Iliblisp -Ielibs 
-Ilib -Icontrol -Idata-tun -Ifwd_balancing -Ifwd_policies/flow_balancing 
-Inet_mgr -Inet_mgr/kernel -Inet_mgr/vpp -c -o liblisp/liblisp.o 
liblisp/liblisp.c 
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror=switch -std=gnu89 -g 
-I/usr/include/libxml2 -D_GNU_SOURCE -D_FORTIFY_SOURCE=2 -I. -Iliblisp -Ielibs 
-Ilib -Icontrol -Idata-tun -Ifwd_balancing -Ifwd_policies/flow_balancing 
-Inet_mgr -Inet_mgr/kernel -Inet_mgr/vpp -c -o liblisp/lisp_address.o 
liblisp/lisp_address.c 
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror=switch -std=gnu89 -g 
-I/usr/include/libxml2 -D_GNU_SOURCE -D_FORTIFY_SOURCE=2 -I. -Iliblisp -Ielibs 
-Ilib -Icontrol -Idata-tun -Ifwd_balancing -Ifwd_policies/flow_balancing 
-Inet_mgr -Inet_mgr/kernel -Inet_mgr/vpp -c -o liblisp/lisp_data.o 
liblisp/lisp_data.c 
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror=switch -std=gnu89 -g 
-I/usr/include/libxml2 -D_GNU_SOURCE -D_FORTIFY_SOURCE=2 -I. -Iliblisp -Ielibs 
-Ilib -Icontrol -Idata-tun -Ifwd_balancing -Ifwd_policies/flow_balancing 
-Inet_mgr -Inet_mgr/kernel -Inet_mgr/vpp -c -o liblisp/lisp_ip.o 
liblisp/lisp_ip.c 
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror=switch -std=gnu89 -g 
-I/usr/include/libxml2 -D_GNU_SOURCE -D_FORTIFY_SOURCE=2 -I. -Iliblisp -Ielibs 
-Ilib -Icontrol -Idata-tun -Ifwd_balancing -Ifwd_policies/flow_balancing 
-Inet_mgr -Inet_mgr/kernel -Inet_mgr/vpp -c -o liblisp/lisp_lcaf.o 
liblisp/lisp_lcaf.c 
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror=switch -std=gnu89 -g 
-I/usr/include/libxml2 -D_GNU_SOURCE -D_FORTIFY_SOURCE=2 -I. -Iliblisp -Ielibs 
-Ilib -Icontrol -Idata-tun -Ifwd_balancing -Ifwd_policies/flow_balancing 
-Inet_mgr -Inet_mgr/kernel -Inet_mgr/vpp -c -o liblisp/lisp_locator.o 
liblisp/lisp_locator.c 
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror=switch -std=gnu89 -g 
-I/usr/include/libxml2 -D_GNU_SOURCE -D_FORTIFY_SOURCE=2 -I. -Iliblisp -Ielibs 
-Ilib -Icontrol -Idata-tun -Ifwd_balancing -Ifwd_policies/flow_balancing 
-Inet_mgr -Inet_mgr/kernel -Inet_mgr/vpp -c -o liblisp/lisp_mapping.o 
liblisp/lisp_mapping.c 
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror=switch -std=gnu89 -g 
-I/usr/include/libxml2 -D_GNU_SOURCE -D_FORTIFY_SOURCE=2 -I. -Iliblisp -Ielibs 
-Ilib -Icontrol -Idata-tun -Ifwd_balanc

Bug#965064: pkg-haskell-tools: FTBFS in unstable

[Clint Adams]

On Wed, Jul 15, 2020 at 03:09:24PM +0100, Iain Lane wrote:
> Upgrading shake will fix this, or it can be worked around in the 

In theory we can upgrade shake once js-dgtable clears NEW.  It's
been sitting there for 3 months.

Bug#966393: pandas: FTBFS: TypeError: use() got an unexpected keyword argument 'warn'

[Rebecca N. Palmer]

Control: found -1 0.25.3+dfsg2-3
Control: tags -1 fixed-upstream patch
(untested)

Probably matplotlib 3.3:
https://github.com/pandas-dev/pandas/pull/35323

Bug#965299: marked as done (haskell-incremental-parser no longer buildable on many architectures.)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jul 2020 01:47:45 +
with message-id <20200730014745.ga20...@scru.org>
and subject line rank2classes
has caused the Debian Bug report #965299,
regarding haskell-incremental-parser no longer buildable on many architectures.
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.)


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

Package: haskell-incremental-parser
Version: 0.4.0.2-1
Severity: serious

haskell-incremental-parser 0.4.0.2-1 added a build-dependency on 
libghc-rank2classes-dev (>= 1.0)
however this package is only available on four out of the ten release 
archictures.

Potential ways forward:

1. fix haskell-rank2classes so it builds on the remaining release architectures.
2. If the dependency is in some way optional, restrict it to the arhictures 
where it
   is available.
3. (last resort) declare that haskell-incremental-parser is not supportable on 
those
   architecutures and request that the ftp-masters remove the package and it's
   reverse-dependencies (haskell-hopenpgp and haskell-hopenpgp-tools).
--- End Message ---
--- Begin Message ---
Looks like Ilias fixed this last week.--- End Message ---

Bug#936628: marked as done (gnucap-python: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jul 2020 01:48:27 +
with message-id 
and subject line Bug#936628: fixed in gnucap-python 0.0.2-1.2
has caused the Debian Bug report #936628,
regarding gnucap-python: Python2 removal in sid/bullseye
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.)


-- 
936628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnucap-python
Version: 0.0.2-1.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:gnucap-python

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: gnucap-python
Source-Version: 0.0.2-1.2
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated gnucap-python 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: Wed, 29 Jul 2020 21:27:14 -0400
Source: gnucap-python
Architecture: source
Version: 0.0.2-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Sandro Tosi 
Closes: 936628
Changes:
 gnucap-python (0.0.2-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #936628
Checksums-Sha1:
 465f01d6c910143a32bd7f1915c847ecc569d482 2229 gnucap-python_0.0.2-1.2.dsc
 cbb974f1ff61b92dbab33a692c2ff0ab21126bd3 7996 
gnucap-python_0.0.2-1.2.debian.tar.xz
 237856f0b4209b806dfae6725fcf23925ba75313 8820 
gnucap-python_0.0.2-1.2_amd64.buildinfo
Checksums-Sha256:
 b49536047d9fb6e82235c6cba8a88091ae796615fc3a87fbe11cd28a0389a853 2229 
gnucap-python_0.0.2-1.2.dsc
 e2588b5ca7c7a31e09ecd4fe0afdc7d7b4e49d6a9fabc4558cbbe92a573cab84 7996 
gnucap-python_0.0.2-1.2.debian.tar.xz
 d64e744498748605c626bc81209c706e8aaa30e7bc257ca73b53efe70e4b5901 8820 
gnucap-py

Bug#966392: [pkg-php-pear] Bug#966392: php-codecoverage: FTBFS 4 tests failed

[Robin Gustafsson]

> -Setting up php-token-stream (4.0.1-1) ...
> +Setting up php-token-stream (4.0.3-1) ...
> [...]
>-Setting up php-phpdocumentor-reflection-docblock (4.3.3-1) ...
>+Setting up php-phpdocumentor-reflection-docblock (5.1.0-1) ...

One or both of these seem to be the cause.

The tests pass if I specifically depend on php-token-stream (4.0.1-1).
Doing so also brings in php-phpdocumentor-reflection-docblock
(4.3.3-1).

Diff in installed packages for my successful build:
-Setting up php-token-stream (4.0.3-1) ...
+Setting up php-token-stream (4.0.1-1) ...
-Setting up php-phpdocumentor-reflection-docblock (5.1.0-1) ...
+Setting up php-phpdocumentor-reflection-docblock (4.3.3-1) ...

Upstream dropped the dependency on php-token-stream recently. There's
no new upstream release (tag) since then yet.

Regards,
Robin

Bug#936288: cfv

[Sandro Tosi]

On Mon, 27 Jul 2020 01:19:52 +0200 Stefan Alfredsson  wrote:
>
> Closing since cfv is being removed due to python2 dependency.
>
> (removal request - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966332 )

please dont close bugs for packages that are still in the archive. the
RM process takes care of closing them when the package is actually
removed

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#965001: strange version 2.1.0 beta4 fails tests with mpfr4 4.1.0

[Martin Kelly]

On Wed, Jul 15, 2020, 4:27 PM Martin Kelly  wrote:

> On Tue, Jul 14, 2020, 3:15 AM Vincent Lefevre  wrote:
>
>> On 2020-07-14 09:48:18 +0200, Matthias Klose wrote:
>> > There is no 2.1.0 beta4, just a beta1, so I don't know what was
>> packaged in
>> > February 2020.  However the tests now fail with mpfr 4.1.0, seems to be
>> > consistent across all architectures:
>> >
>> > **
>> > File "test/test_gmpy2_format.txt", line 157, in test_gmpy2_format.txt
>> > Failed example:
>> > c.__format__('e')
>> > Differences (ndiff with -expected +actual):
>> > - '3.3331e-01+5e+00j'
>> > + '3.3331e-01+5.e+00j'
>> > ?  +
>>
>> FYI, the old MPFR behavior was regarded as a bug:
>>
>>
>> https://gforge.inria.fr/tracker/index.php?func=detail&aid=21816&group_id=136&atid=619
>>
>> There were 2 reasonable interpretations of the description in the
>> MPFR manual that did not leave the output partly unspecified, and
>> for each of them, some outputs were incorrect. The one that has
>> been chosen is the one that is closer to ISO C's %e and it does
>> not change the numerical output value (the only difference is
>> trailing zeros).
>>
>> --
>> Vincent Lefèvre  - Web: 
>> 100% accessible validated (X)HTML - Blog: 
>> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
>>
>
> Hi all,
>
> Thanks for the bug report. Unfortunately I'm on a long hiking vacation
> with no computer access until October and won't be able to look at this
> until then. I welcome a non-maintainer upload if this needs a fix sooner.
>
> I'm also CCing the upstream maintainer, who may have an opinion on that to
> do here.
>

The beta4 version is this one:
https://github.com/aleaxit/gmpy/releases/tag/gmpy2-2.1.0b4

It looks like it may be a tag but not a release? In any case, I assume
that's what I packaged (I can't check as I don't have computer access right
now, just phone).

Apparently this bug is going to cause autoremoval from testing soon. Is the
severity really high enough for that?

Again, I'd like to take a closer look at this but am away from a computer
until October on an extended trip

>

Bug#936628: gnucap-python: diff for NMU version 0.0.2-1.2

[Sandro Tosi]

Control: tags 936628 + patch


Dear maintainer,

I've prepared an NMU for gnucap-python (versioned as 0.0.2-1.2). The diff
is attached to this message.

Regards.

diff -Nru gnucap-python-0.0.2/debian/changelog gnucap-python-0.0.2/debian/changelog
--- gnucap-python-0.0.2/debian/changelog	2019-01-20 07:38:13.0 -0500
+++ gnucap-python-0.0.2/debian/changelog	2020-07-29 21:27:14.0 -0400
@@ -1,3 +1,10 @@
+gnucap-python (0.0.2-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #936628
+
+ -- Sandro Tosi   Wed, 29 Jul 2020 21:27:14 -0400
+
 gnucap-python (0.0.2-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gnucap-python-0.0.2/debian/control gnucap-python-0.0.2/debian/control
--- gnucap-python-0.0.2/debian/control	2019-01-20 07:38:13.0 -0500
+++ gnucap-python-0.0.2/debian/control	2020-07-29 21:20:12.0 -0400
@@ -11,10 +11,6 @@
gnucap,
gnucap-default-plugins0,
libgnucap-dev,
-   python,
-   python-numpy,
-   python-scipy,
-   python2.7-dev,
python3-all-dev,
python3-numpy,
python3-scipy,
@@ -27,30 +23,13 @@
 Package: gnucap-python
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
-Suggests: gnucap, python
+Suggests: gnucap, python3
 Description: GNU Circuit Analysis package, Python command plugin
  This package contains a plugin with a command to load extensions written in
  the Python language.
  .
  Gnucap is a general purpose circuit simulator. It performs nonlinear
  dc and transient analyses, Fourier analysis, and ac analysis
- linearized at an operating point. It is fully interactive and
- command driven. It can also be run in batch mode or as a server.
-
-Package: python-gnucap
-Section: python
-Architecture: any
-Depends: ${dlopen:Depends},
- ${misc:Depends},
- ${python:Depends},
- ${shlibs:Depends}
-Recommends: gnucap-default-plugins0
-Suggests: gnucap-devel
-Description: Python 2 bindings for the GNU Circuit Analysis Package
- This package contains Python2 bindings for the GNU Circuit Analysis Package.
- .
- Gnucap is a general purpose circuit simulator. It performs nonlinear
- dc and transient analyses, Fourier analysis, and ac analysis
  linearized at an operating point. It is fully interactive and
  command driven. It can also be run in batch mode or as a server.
 
diff -Nru gnucap-python-0.0.2/debian/python-gnucap.install gnucap-python-0.0.2/debian/python-gnucap.install
--- gnucap-python-0.0.2/debian/python-gnucap.install	2018-12-20 06:25:09.0 -0500
+++ gnucap-python-0.0.2/debian/python-gnucap.install	1969-12-31 19:00:00.0 -0500
@@ -1,2 +0,0 @@
-/usr/lib/python2*/*/gnucap/*.so*
-/usr/lib/python2*/*/gnucap/*py
diff -Nru gnucap-python-0.0.2/debian/rules gnucap-python-0.0.2/debian/rules
--- gnucap-python-0.0.2/debian/rules	2019-01-20 07:38:13.0 -0500
+++ gnucap-python-0.0.2/debian/rules	2020-07-29 21:21:24.0 -0400
@@ -1,7 +1,6 @@
 #!/usr/bin/make -f
 
-PYVERS:= $(shell pyversions -v -r debian/control) \
-  $(shell py3versions -v -r debian/control)
+PYVERS:= $(shell py3versions -v -r debian/control)
 
 PYDEF:= $(shell py3versions -d -v)
 
@@ -19,7 +18,7 @@
 
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3
 
 build: build-arch build-indep
 
@@ -65,11 +64,9 @@
 
 override_dh_shlibdeps: debian/tmp.lib
 	dh_shlibdeps
-	dh_numpy
 	dh_numpy3
 
 	# inject extra library dependency
-	cat $< >> debian/python-gnucap.substvars
 	cat $< >> debian/python3-gnucap.substvars
 
 # dpkg-shlibdeps misses the dlopen in gnucap/__init__.py

Processed: gnucap-python: diff for NMU version 0.0.2-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 936628 + patch
Bug #936628 [src:gnucap-python] gnucap-python: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#966515: scons: Some upstream sources are missing

[Bill Deegan]

So what is this issue?
Which tarball debian packages are using as their source?

On Wed, Jul 29, 2020 at 4:23 PM Ben Hutchings 
wrote:

> On Wed, 2020-07-29 at 16:11 -0700, Bill Deegan wrote:
> > Note there's a bug for this on SCons tracker.
> > https://github.com/SCons/scons/issues/3759
> >
> > Please add any comments there.
>
> No, that's an entirely different issue.
>
> Ben.
>
> --
> Ben Hutchings, Software Developer Codethink Ltd
> https://www.codethink.co.uk/ Dale House, 35 Dale Street
>  Manchester, M1 2HF, United Kingdom
>
>

Processed: Re: Bug#963932: Unversioned symbol json_object_iter_next is in all of json-c, jansson, json-glib

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #963932 [src:json-c] json-c: Exports symbols in json_* namespace without 
symbol-versioning
Severity set to 'important' from 'serious'

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

Bug#966515: scons: Some upstream sources are missing

[Ben Hutchings]

On Wed, 2020-07-29 at 16:11 -0700, Bill Deegan wrote:
> Note there's a bug for this on SCons tracker.
> https://github.com/SCons/scons/issues/3759
> 
> Please add any comments there.

No, that's an entirely different issue.

Ben.

-- 
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
 Manchester, M1 2HF, United Kingdom

Bug#963932: Unversioned symbol json_object_iter_next is in all of json-c, jansson, json-glib

[Chris Hofstaedtler]

Control: severity -1 important

* Simon McVittie  [200728 00:21]:
> On Sun, 28 Jun 2020 at 22:06:13 +0200, Chris Hofstaedtler wrote:
> > your libraries BOTH export a symbol named json_object_iter_next,
> > causing crashes for binaries that end up loading both (possibly
> > transitively).

[..]

> Because util-linux (libmount) has taken steps to avoid pulling json-c
> into unsuspecting processes' namespaces, I don't think this should be
> treated as RC any more - I think important would now be a more reasonable
> severity. Chris, do you agree?

>From libmount PoV, I agree. Have lowered severity for #963932 now,
but this should not be seen as overriding jansson,json-c Maintainers
preference.

Chris

Bug#966515: scons: Some upstream sources are missing

[Bill Deegan]

Note there's a bug for this on SCons tracker.
https://github.com/SCons/scons/issues/3759

Please add any comments there.

On Wed, Jul 29, 2020 at 4:06 PM Ben Hutchings 
wrote:

> Source: scons
> Version: 3.1.2-2
> Severity: serious
>
> Dear Maintainer,
>
> The current source package uses the 'production' tarballs
> (scons-.tar.gz) as the orig tarball, whereas the upstream
> source tarballs are released as scons-src-.tar.gz.
>
> The 'production' tarballs contain many generated or preprocessed files.
> In particular, the manual pages there are generated from the doc/man/
> subdirectory of the upstream source, which is *not* included in the
> production tarballs.
>
> Ben.
>
> -- System Information:
> Debian Release: 10.4
>   APT prefers stable
>   APT policy: (990, 'stable'), (500, 'stable-updates')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, armhf, arm64
>
> Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> --
> Ben Hutchings, Software Developer Codethink Ltd
> https://www.codethink.co.uk/ Dale House, 35 Dale Street
>  Manchester, M1 2HF, United Kingdom
>
>

Bug#966515: scons: Some upstream sources are missing

[Ben Hutchings]

Source: scons
Version: 3.1.2-2
Severity: serious

Dear Maintainer,

The current source package uses the 'production' tarballs
(scons-.tar.gz) as the orig tarball, whereas the upstream
source tarballs are released as scons-src-.tar.gz.

The 'production' tarballs contain many generated or preprocessed files.
In particular, the manual pages there are generated from the doc/man/
subdirectory of the upstream source, which is *not* included in the
production tarballs.

Ben.

-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
 Manchester, M1 2HF, United Kingdom

Processed: Re: Bug#966393: pandas: FTBFS: TypeError: use() got an unexpected keyword argument 'warn'

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.25.3+dfsg2-3
Bug #966393 [src:pandas] pandas: FTBFS: TypeError: use() got an unexpected 
keyword argument 'warn'
Marked as found in versions pandas/0.25.3+dfsg2-3.
> tags -1 fixed-upstream patch
Bug #966393 [src:pandas] pandas: FTBFS: TypeError: use() got an unexpected 
keyword argument 'warn'
Added tag(s) fixed-upstream and patch.

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

Bug#966199: nastran: FTBFS with GCC 10: Error: BOZ constant at (1) uses nonstandard postfix syntax

[Andreas Beckmann]

Hi Sylvestre,

you sponsored the nastran upload some years ago, could you take a look
again?

Thanks

Andreas

On 7/25/20 11:50 AM, Luca Dall'Olio wrote:
> Hi,
> 
> Thank you for reporting: I just fixed the issue by adding a check in
> configure.ac and defining -fallow-invalid-boz if present. I checked with
> both gfortran-10 and gfortran-7 and tests are passing.
> 
> I had to add autoconf-archive in Buld-Depends to have
> the AX_CHECK_COMPILE_FLAG macro
> 
> My tests are passing
>  with
> this revision
> 
> .
> 
> Honestly, I do not remember well the procedure to push these changes into
> the Debian build system, could you please point me in the right direction?
> 
> Thank you very much in advance, all the best
> 
> Luca
> 
> Il giorno ven 24 lug 2020 alle ore 18:09 Andreas Beckmann 
> ha scritto:
> 
>> Source: nastran
>> Version: 0.1.95-1
>> Severity: serious
>> Tags: ftbfs sid bullseye
>> Justification: fails to build from source
>> User: debian-...@lists.debian.org
>> Usertags: ftbfs-gcc-10
>>
>> Hi,
>>
>> nastran started to FTBFS when GCC 10 was made the default compiler:
>>
>> f77  -g -w -fno-range-check -fno-automatic -fcray-pointer -std=legacy -c
>> -o bufchk.o bufchk.f
>> bufchk.f:16:28:
>>
>>16 |  1 '1'X,  '2'X , '3'X, '4'X  ,
>> '8'X   /
>>   |1
>> Error: BOZ constant at (1) uses nonstandard postfix syntax [see
>> '-fno-allow-invalid-boz']
>> bufchk.f:18:32:
>>
>>18 |  1 'F'X,  'F'X , 'F'X, 'F'X /
>>   |1
>> Error: BOZ constant at (1) uses nonstandard postfix syntax [see
>> '-fno-allow-invalid-boz']
>> bufchk.f:20:32:
>>
>>20 |  1 'F'X,  'F'X , 'F'X, 'F'X /
>>   |1
>> Error: BOZ constant at (1) uses nonstandard postfix syntax [see
>> '-fno-allow-invalid-boz']
>> make[2]: *** [Makefile:390: bufchk.o] Error 1
>>
>> More information about the corresponding GCC changes can be found here:
>> https://gcc.gnu.org/gcc-10/porting_to.html
>>
>>
>> Andreas
>>
> 

Bug#957004: marked as done (argus-clients: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 21:04:00 +
with message-id 
and subject line Bug#957004: fixed in argus-clients 1:3.0.8.2-6
has caused the Debian Bug report #957004,
regarding argus-clients: 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.)


-- 
957004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:argus-clients
Version: 1:3.0.8.2-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/argus-clients_3.0.8.2-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

[...]
./rasqlinsert.c:1437:35: warning: ‘%s’ directive writing up to 4095 bytes into 
a region of size 1001 [-Wformat-overflow=]
 1437 |sprintf (sbuf, "%s %s interval accepted", RAGETTINGuSTR, 
RaCommandInputStr);
  |   ^~
~
In file included from /usr/include/stdio.h:867,
 from ../../include/argus_util.h:223,
 from ./rasqlinsert.h:40,
 from ./rasqlinsert.c:49:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output between 42 and 4137 bytes into a destination 
of size 1024
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
./rasqlinsert.c:774:35: warning: ‘%s’ directive writing up to 4095 bytes into a 
region of size 1007 [-Wformat-overflow=]
  774 |sprintf (sbuf, "%s %s filter accepted", RAGETTINGfSTR, 
RaCommandInputStr);
  |   ^~  
~
In file included from /usr/include/stdio.h:867,
 from ../../include/argus_util.h:223,
 from ./rasqlinsert.h:40,
 from ./rasqlinsert.c:49:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output between 34 and 4129 bytes into a destination 
of size 1024
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
./rasqlinsert.c:774:35: warning: ‘%s’ directive writing up to 4095 bytes into a 
region of size 1007 [-Wformat-overflow=]
  774 |sprintf (sbuf, "%s %s filter accepted", RAGETTINGfSTR, 
RaCommandInputStr);
  |   ^~  
~
In file included from /usr/include/stdio.h:867,
 from ../../include/argus_util.h:223,
 from ./rasqlinsert.h:40,
 from ./rasqlinsert.c:49:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output between 34 and 4129 bytes into a destination 
of size 1024
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
./rasqlinsert.c:770:35: warning: ‘%s’ directive writing up to 4095 bytes into a 
region of size 1007 [-Wformat-overflow=]
  770 |sprintf (sbuf, "%s %s syntax 

Bug#951990: marked as done (willow: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 21:05:14 +
with message-id 
and subject line Bug#951990: fixed in willow 1.4-1
has caused the Debian Bug report #951990,
regarding willow: FTBFS: dh_auto_test: error: pybuild --test -i python{version} 
-p "3.8 3.7" returned exit code 13
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.)


-- 
951990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: willow
Version: 1.1-4
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.8 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_willow/build/willow
> copying willow/registry.py -> 
> /<>/.pybuild/cpython3_3.8_willow/build/willow
> copying willow/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_willow/build/willow
> copying willow/image.py -> 
> /<>/.pybuild/cpython3_3.8_willow/build/willow
> creating /<>/.pybuild/cpython3_3.8_willow/build/willow/utils
> copying willow/utils/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_willow/build/willow/utils
> copying willow/utils/deprecation.py -> 
> /<>/.pybuild/cpython3_3.8_willow/build/willow/utils
> creating /<>/.pybuild/cpython3_3.8_willow/build/willow/plugins
> copying willow/plugins/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_willow/build/willow/plugins
> copying willow/plugins/opencv.py -> 
> /<>/.pybuild/cpython3_3.8_willow/build/willow/plugins
> copying willow/plugins/pillow.py -> 
> /<>/.pybuild/cpython3_3.8_willow/build/willow/plugins
> copying willow/plugins/wand.py -> 
> /<>/.pybuild/cpython3_3.8_willow/build/willow/plugins
> running egg_info
> creating Willow.egg-info
> writing Willow.egg-info/PKG-INFO
> writing dependency_links to Willow.egg-info/dependency_links.txt
> writing top-level names to Willow.egg-info/top_level.txt
> writing manifest file 'Willow.egg-info/SOURCES.txt'
> reading manifest file 'Willow.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '__pycache__' found anywhere 
> in distribution
> warning: no previously-included files matching '*.py[co]' found anywhere in 
> distribution
> warning: no previously-included files matching '*.swp' found anywhere in 
> distribution
> writing manifest file 'Willow.egg-info/SOURCES.txt'
> creating /<>/.pybuild/cpython3_3.8_willow/build/willow/data
> creating 
> /<>/.pybuild/cpython3_3.8_willow/build/willow/data/cascades
> copying willow/data/cascades/haarcascade_frontalface_alt2.xml -> 
> /<>/.pybuild/cpython3_3.8_willow/build/willow/data/cascades
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.7_willow/build/willow
> copying willow/registry.py -> 
> /<>/.pybuild/cpython3_3.7_willow/build/willow
> copying willow/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_willow/build/willow
> copying willow/image.py -> 
> /<>/.pybuild/cpython3_3.7_willow/build/willow
> creating /<>/.pybuild/cpython3_3.7_willow/build/willow/utils
> copying willow/utils/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_willow/build/willow/utils
> copying willow/utils/deprecation.py -> 
> /<>/.pybuild/cpython3_3.7_willow/build/willow/utils
> creating /<>/.pybuild/cpython3_3.7_willow/build/willow/plugins
> copying willow/plugins/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_willow/build/willow/plugins
> copying willow/plugins/opencv.py -> 
> /<>/.pybuild/cpython3_3.7_willow/build/willow/plugins
> copying willow/plugins/pillow.py -> 
> /<>/.pybuild/cpython3_3.7_willow/build/willow/plugins
> copying willow/plugins/wand.py -> 
> /<>/.pybuild/cpython3_3.7_willow/build/willow/plugins
> running egg_info
> writing Willow.egg-info/PKG-INFO
> writing dependency_links to Willow.egg-info/dependency_links.txt
> writing top-level names to Willow.egg-info/top_level.txt
> reading manifest file 'Willow.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '__pycache__' found anywhere 
> in distribution
> warning: no previously-included files matching '*.py[co]' found anywhere in 
> distribution
> warning: no previously-included files matching '*.swp' found anywhere in 
> distribution
> writing manifest file 'Willow.egg-info/SOURCES.txt'
> creating /<>/.pybuild/cpython3_3.7_willow/build/willow/data
> creating 
> /<>/.pybuild/c

Bug#957532: marked as done (mes: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 20:39:33 +
with message-id 
and subject line Bug#957532: fixed in mes 0.22-3
has caused the Debian Bug report #957532,
regarding mes: 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.)


-- 
957532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mes
Version: 0.22-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/mes_0.22-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: gcc-lib/libc.a(isatty.o):./gcc-lib/../include/mes/lib-mini.h:43: 
multiple definition of `environ'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:43: first defined here
/usr/bin/ld: gcc-lib/libc.a(isatty.o):./gcc-lib/../include/mes/lib-mini.h:44: 
multiple definition of `__stdin'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:44: first defined here
/usr/bin/ld: gcc-lib/libc.a(isatty.o):./gcc-lib/../include/mes/lib-mini.h:45: 
multiple definition of `__stdout'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:45: first defined here
/usr/bin/ld: gcc-lib/libc.a(isatty.o):./gcc-lib/../include/mes/lib-mini.h:46: 
multiple definition of `__stderr'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:46: first defined here
/usr/bin/ld: gcc-lib/libc.a(isatty.o):./gcc-lib/../include/mes/lib-mini.h:90: 
multiple definition of `errno'; crt1.o:./gcc-lib/../include/mes/lib-mini.h:90: 
first defined here
/usr/bin/ld: 
gcc-lib/libc.a(buffered-read.o):./gcc-lib/../include/mes/lib-mini.h:43: 
multiple definition of `environ'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:43: first defined here
/usr/bin/ld: 
gcc-lib/libc.a(buffered-read.o):./gcc-lib/../include/mes/lib-mini.h:44: 
multiple definition of `__stdin'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:44: first defined here
/usr/bin/ld: 
gcc-lib/libc.a(buffered-read.o):./gcc-lib/../include/mes/lib-mini.h:45: 
multiple definition of `__stdout'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:45: first defined here
/usr/bin/ld: 
gcc-lib/libc.a(buffered-read.o):./gcc-lib/../include/mes/lib-mini.h:46: 
multiple definition of `__stderr'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:46: first defined here
/usr/bin/ld: 
gcc-lib/libc.a(buffered-read.o):./gcc-lib/../include/mes/lib-mini.h:90: 
multiple definition of `errno'; crt1.o:./gcc-lib/../include/mes/lib-mini.h:90: 
first defined here
/usr/bin/ld: gcc-lib/libc.a(setenv.o):./gcc-lib/../include/mes/lib-mini.h:43: 
multiple definition of `environ'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:43: first defined here
/usr/bin/ld: gcc-lib/libc.a(setenv.o):./gcc-lib/../include/mes/lib-mini.h:44: 
multiple definition of `__stdin'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:44: first defined here
/usr/bin/ld: gcc-lib/libc.a(setenv.o):./gcc-lib/../include/mes/lib-mini.h:45: 
multiple definition of `__stdout'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:45: first defined here
/usr/bin/ld: gcc-lib/libc.a(setenv.o):./gcc-lib/../include/mes/lib-mini.h:46: 
multiple definition of `__stderr'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:46: first defined here
/usr/bin/ld: gcc-lib/libc.a(setenv.o):./gcc-lib/../include/mes/lib-mini.h:90: 
multiple definition of `errno'; crt1.o:./gcc-lib/../include/mes/lib-mini.h:90: 
first defined here
/usr/bin/ld: gcc-lib/libc.a(malloc.o):./gcc-lib/../include/mes/lib-mini.h:43: 
multiple definition of `environ'; 
crt1.o:./gcc-lib/../include/mes/lib-mini.h:43: first defined here
/usr/bin/ld: gcc-lib/

Bug#925745: marked as done (libgtextutils: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 20:36:53 +
with message-id 
and subject line Bug#925745: fixed in libgtextutils 0.7-7
has caused the Debian Bug report #925745,
regarding libgtextutils: ftbfs with GCC-9
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.)


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

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-9/g++-9, but succeeds to build with gcc-8/g++-8. 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/gcc9-20190321/libgtextutils_0.7-6_unstable_gcc9.log
The last lines of the build log are at the end of this report.

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

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
make[3]: Leaving directory '/<>/src'
Making all in doc
make[3]: Entering directory '/<>/doc'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/doc'
Making all in tests
make[3]: Entering directory '/<>/tests'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/tests'
make[3]: Entering directory '/<>'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_auto_test -a
make -j4 check VERBOSE=1
make[1]: Entering directory '/<>'
Making check in m4
make[2]: Entering directory '/<>/m4'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/<>/m4'
Making check in src
make[2]: Entering directory '/<>/src'
Making check in gtextutils
make[3]: Entering directory '/<>/src/gtextutils'
make[3]: Nothing to be done for 'check'.
make[3]: Leaving directory '/<>/src/gtextutils'
make[3]: Entering directory '/<>/src'
make[3]: Nothing to be done for 'check-am'.
make[3]: Leaving directory '/<>/src'
make[2]: Leaving directory '/<>/src'
Making check in doc
make[2]: Entering directory '/<>/doc'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/<>/doc'
Making check in tests
make[2]: Entering directory '/<>/tests'
make  test_container_join test_natural_sort test_input_stream_wrapper 
test_text_reader test_text_reader_unget test_fd_outbuf test_fd_inbuf 
test_in_out_buf test_pipe_fitter test_string_tokenize 
make[3]: Entering directory '/<>/tests'
g++ -DHAVE_CONFIG_H -I. -I..  -I../src -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wextra -Wformat-nonliteral -Wformat-security 
-Wswitch-default -Wswitch-enum -Wunused-parameter -Wfloat-equal -Werror -DDEBUG 
-g -O1 -DDEBUG -g -O1 -c -o test_container_join.o test_container_join.cpp
printf "first line\nsecond line\nthird line\nfourth line\n" > test.txt
g++ -DHAVE_CONFIG_H -I. -I..  -I../src -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wextra -Wformat-nonliteral -Wformat-security 
-Wswitch-default -Wswitch-enum -Wunused-parameter -Wfloat-equal -Werror -DDEBUG 
-g -O1 -DDEBUG -g -O1 -c -o test_natural_sort.o test_natural_sort.cpp
g++ -DHAVE_CONFIG_H -I. -I..  -I../src -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wextra -Wformat-nonliteral -Wformat-security 
-Wswitch-default -Wswitch-enum -Wunused-parameter -Wfloat-equal -Werror -DDEBUG 
-g -O1 -DDEBUG -g -O1 -c -o test_input_stream_wrapper.o 
test_input_stream_wrapper.cpp
g++ -DHAVE_CONFIG_H -I. -I..  -I../src

Bug#966500: python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)

[Andreas Beckmann]

Control: tag -1 pending

On 7/29/20 2:32 PM, Nick Black wrote:
> Thank you for filing my first Debian bug! How exciting, and at
> the same time embarrassing. I should have caught this before
> uploading. A fix is obvious, and I ought be able to accomplish
> it within the Debian packaging proper, rather than requiring a
> new release (I'm the upstream author).

Yes, the fix is only in the Debian packaging part (perhaps unless you
decide to move around stuff again).
Don't feel too embarrassed, I forgot Breaks+Replaces when I renamed a
package yesterday, too. And noticed it two minutes after the upload.

On 7/29/20 6:44 PM, Nick Black wrote:
> pending
> thanks

See above for the correct syntax to tag the bug as pending by simply
sending a mail to the bug ;-)

> Andreas, if a fix tomorrow or the next day isn't fast enough,
> let me know and I can push on the 1.6.9+dfsg.1-3. thanks!

I don't mind when this gets fixed, it's fine to bundle it with more
fixes/new upstream releases ;-)
This RC (release critical) bug will prevent the buggy version from
migrating to testing.
(Only if the package gets out-of-sync between testing and unstable for
more than two months you are risking removal from testing.)

Andreas

Processed: Re: Bug#966500: python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #966500 [python3-notcurses] python3-notcurses: missing Breaks+Replaces: 
notcurses-bin (<< 1.6)
Added tag(s) pending.

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

Bug#837123: marked as done ([anna] segfault in wheezy installer)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 22:02:30 +0200
with message-id <20200729200230.ga14...@aurel32.net>
and subject line Re: Bug#837123: [anna] segfault in wheezy installer
has caused the Debian Bug report #837123,
regarding [anna] segfault in wheezy installer
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.)


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

Package: libc6-udeb
Version: 2.13-38+deb7u10
Severity: grave
Justification: breaks installation entirely

The wheezy installer fails with anna reporting a segfault:

...
anna[5033]: DEBUG: retrieving libc6-udeb 2.13-38+deb7u10
anna[5033]: DEBUG: retrieving finish-install 2.41wheezy1
anna[5033]: DEBUG: Segmentation fault
anna[5033]: WARNING **: package retrieval failed
kernel: [   66.427372] wget[5382]: segfault a 0 ip 7176c922c0ca sp 
7ffc8ca83890 error 6 in libresolv-2.13.so[7f76c9222000+13000]

This occurs shortly after libc6-udev is downloaded,
according to the installer interactive display.

Background
--
I was trying to reinstall an older system with wheezy.
I was using the PXE install image available on 2016-09-08 UTC, at
ftp.au.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/netboot

The mirror shows the last update timestamp as 2016-05-31.
debian-installer/amd64/boot-screens/f1.txt has the fairly useless
build date stamp 20130613+deb7u3+b2.

This installation method was working fine with earlier installer
versions. The breakage has been there some months I'd say.
I only became fully aware of it yesterday.

I don't think the mirror is out of date; I got the same result
with the netboot installer image downloaded from ftp.us.debian.org.


The log above was copied by eye from the console,
I was unable to install the openssh-client=udeb to copy the logs,
thanks to the segfault.

The core of the issue is probably screwed up libc6 versions,
see bugs 740068, 833432

Other package versions that may be of interest
 base-installer: 1.130
 cdebconf-udeb: 0.182
 di-utils: 1.92+deb7u1
 libc6-udeb: 2.13-38+deb7u10
 anna: 1.44+deb7u1

It's really unfortunate to have the oldstable installer break like this.
I hope it can be fixed, age notwithstanding.

Kind regards
Vince
-- 
--- End Message ---
--- Begin Message ---
Hi,

It happens this bug has been forgotten in the bts as it is somehow
considered to be reported about the libc6-udeb *source* package. I
believe that since the time the problem is not reproducible anymore.

I am therefore closing the bug, if it can still be reproduced with
recent releases, feel free to reopen the bug.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---

Bug#957465: marked as done (libosmocore: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 19:48:56 +
with message-id 
and subject line Bug#957465: fixed in libosmocore 0.12.1-3.1
has caused the Debian Bug report #957465,
regarding libosmocore: 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.)


-- 
957465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libosmocore
Version: 0.12.1-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/libosmocore_0.12.1-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

[...]
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -I../../include -I../../include   -I/usr/include/p11-kit-1 -Wdate-time 
-D_FORTIFY_SOURCE=2 -DBUILDING_LIBOSMOCORE -Wall -Wall  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DBUILDING_LIBOSMOCORE -Wall -c -o gan.lo gan.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include 
-I../../include -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 
-DBUILDING_LIBOSMOCORE -Wall -Wall -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-DBUILDING_LIBOSMOCORE -Wall -c gan.c  -fPIC -DPIC -o .libs/gan.o
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -I../../include -I../../include   -I/usr/include/p11-kit-1 -Wdate-time 
-D_FORTIFY_SOURCE=2 -DBUILDING_LIBOSMOCORE -Wall -Wall  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DBUILDING_LIBOSMOCORE -Wall -c -o ipa.lo ipa.c
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -I../../include -I../../include   -I/usr/include/p11-kit-1 -Wdate-time 
-D_FORTIFY_SOURCE=2 -DBUILDING_LIBOSMOCORE -Wall -Wall  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DBUILDING_LIBOSMOCORE -Wall -c -o gsm0341.lo gsm0341.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include 
-I../../include -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 
-DBUILDING_LIBOSMOCORE -Wall -Wall -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-DBUILDING_LIBOSMOCORE -Wall -c ipa.c  -fPIC -DPIC -o .libs/ipa.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include 
-I../../include -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 
-DBUILDING_LIBOSMOCORE -Wall -Wall -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-DBUILDING_LIBOSMOCORE -Wall -c gsm0341.c  -fPIC -DPIC -o .libs/gsm0341.o
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -I../../include -I../../include   -I/usr/include/p11-kit-1 -Wdate-time 
-D_FORTIFY_SOURCE=2 -DBUILDING_LIBOSMOCORE -Wall -Wall  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DBUILDING_LIBOSMOCORE -Wall -c -o apn.lo apn.c
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -I../../include -I../../include   -I/usr/include/p11-kit-1 -Wdate-time 
-D_FORTIFY_SOURCE=2 -DBUILDING_LIBOSMOCORE -Wall -Wall  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DBUILDING_LIBOSMOCORE -Wall -c -o gsup.lo gsup.c
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -I../../include -I../../incl

Bug#957006: marked as done (argus: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 19:03:50 +
with message-id 
and subject line Bug#957006: fixed in argus 2:3.0.8.2-2
has caused the Debian Bug report #957006,
regarding argus: 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.)


-- 
957006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:argus
Version: 2:3.0.8.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/argus_3.0.8.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

[...]
### Making in /<>/argus
make[2]: Entering directory '/<>/argus'
gcc -O -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I. -I/usr/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./../include  -DHAVE_CONFIG_H -c argus.c
gcc -O -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I. -I/usr/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./../include  -DHAVE_CONFIG_H -c ArgusModeler.c
gcc -O -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I. -I/usr/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./../include  -DHAVE_CONFIG_H -c ArgusSource.c
ArgusSource.c: In function ‘setArgusDevice’:
ArgusSource.c:870:19: warning: ‘pcap_lookupdev’ is deprecated: use 
'pcap_findalldevs' and use the first device [-Wdeprecated-declarations]
  870 |   setArgusDevice (src, pcap_lookupdev (errbuf), 
ARGUS_LIVE_DEVICE, 0);
  |   ^~
In file included from /usr/include/pcap.h:43,
 from ./ArgusOutput.h:66,
 from ./ArgusUtil.h:129,
 from ./ArgusModeler.h:331,
 from ./argus.h:40,
 from ArgusSource.c:67:
/usr/include/pcap/pcap.h:328:16: note: declared here
  328 | PCAP_API char *pcap_lookupdev(char *)
  |^~
gcc -O -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I. -I/usr/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./../include  -DHAVE_CONFIG_H -c ArgusUtil.c
gcc -O -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I. -I/usr/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./../include  -DHAVE_CONFIG_H -c ArgusOutput.c
gcc -O -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I. -I/usr/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./../include  -DHAVE_CONFIG_H -c ArgusUdp.c
gcc -O -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I. -I/usr/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./../include  -DHAVE_CONFIG_H -c ArgusTcp.c
gcc -O -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I. -I/usr/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./../include  -DHAVE_CONFIG_H -c ArgusIcmp.c
gcc -O -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I. -I/usr/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./../include  -DHAVE_CONFIG_H -c ArgusIgmp.c
gcc -O -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I. -I/usr/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./../include  -DHAVE_CONFIG_H -c ArgusEsp.c
gcc -O -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I. -I/usr/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./../include  -DHAVE_CONFI

Bug#957440: marked as done (libgetdata: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 17:49:18 +
with message-id 
and subject line Bug#957440: fixed in libgetdata 0.10.0-8
has caused the Debian Bug report #957440,
regarding libgetdata: 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.)


-- 
957440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgetdata
Version: 0.10.0-6
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/libgetdata_0.10.0-6_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

[...]
  435 |   GD_COMPLEX128, data_out)
  | 2   
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(COMPLEX(4)/COMPLEX(8)).
getdata.f90:406:66:

  406 |   first_frame, first_sample, num_frames, num_samples, GD_FLOAT64, 
data_out)
  |  1
..
  435 |   GD_COMPLEX128, data_out)
  | 2 
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(REAL(8)/COMPLEX(8)).
getdata.f90:392:66:

  392 |   first_frame, first_sample, num_frames, num_samples, GD_FLOAT32, 
data_out)
  |  1
..
  435 |   GD_COMPLEX128, data_out)
  | 2 
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(REAL(4)/COMPLEX(8)).
getdata.f90:378:64:

  378 |   first_frame, first_sample, num_frames, num_samples, GD_INT64, 
data_out)
  |1
..
  435 |   GD_COMPLEX128, data_out)
  | 2   
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(8)/COMPLEX(8)).
getdata.f90:364:64:

  364 |   first_frame, first_sample, num_frames, num_samples, GD_INT32, 
data_out)
  |1
..
  435 |   GD_COMPLEX128, data_out)
  | 2   
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(4)/COMPLEX(8)).
getdata.f90:350:64:

  350 |   first_frame, first_sample, num_frames, num_samples, GD_INT16, 
data_out)
  |1
..
  435 |   GD_COMPLEX128, data_out)
  | 2   
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(2)/COMPLEX(8)).
getdata.f90:336:63:

  336 |   first_frame, first_sample, num_frames, num_samples, GD_INT8, data_out)
  |   1
..
  435 |   GD_COMPLEX128, data_out)
  | 2  
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(1)/COMPLEX(8)).
getdata.f90:322:63:

  322 |   first_frame, first_sample, num_frames, num_samples, GD_NULL, 0)
  |   1
..
  435 |   GD_COMPLEX128, data_out)
  | 2  
Error: Type mismatch betw

Bug#957289: marked as done (gnss-sdr: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 17:33:41 +
with message-id 
and subject line Bug#957289: fixed in gnss-sdr 0.0.13-1
has caused the Debian Bug report #957289,
regarding gnss-sdr: 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.)


-- 
957289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnss-sdr
Version: 0.0.11-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/gnss-sdr_0.0.11-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 
/<>/src/algorithms/signal_source/adapters/osmosdr_signal_source.cc:32:
/usr/include/boost/format/alt_sstream_impl.hpp: In instantiation of 
‘boost::io::basic_altstringbuf::int_type 
boost::io::basic_altstringbuf::overflow(boost::io::basic_altstringbuf::int_type) [with 
Ch = char; Tr = std::char_traits; Alloc = std::allocator; 
boost::io::basic_altstringbuf::int_type = int]’:
/usr/include/boost/format/alt_sstream_impl.hpp:227:9:   required from here
/usr/include/boost/format/alt_sstream_impl.hpp:261:45: error: no matching 
function for call to ‘std::allocator::allocate(std::size_t&, char*)’
  261 | newptr = alloc_.allocate(new_size, is_allocated_? 
oldptr : 0);
  |  
~~~^
In file included from /usr/include/c++/10/string:41,
 from /usr/include/c++/10/stdexcept:39,
 from /usr/include/c++/10/system_error:41,
 from /usr/include/c++/10/bits/std_mutex.h:39,
 from /usr/include/c++/10/condition_variable:40,
 from /<>/src/core/receiver/concurrent_queue.h:35,
 from 
/<>/src/algorithms/signal_source/adapters/osmosdr_signal_source.h:36,
 from 
/<>/src/algorithms/signal_source/adapters/osmosdr_signal_source.cc:32:
/usr/include/c++/10/bits/allocator.h:171:7: note: candidate: ‘constexpr _Tp* 
std::allocator<  >::allocate(std::size_t) [with _Tp = 
char; std::size_t = long unsigned int]’
  171 |   allocate(size_t __n)
  |   ^~~~
/usr/include/c++/10/bits/allocator.h:171:7: note:   candidate expects 1 
argument, 2 provided
make[3]: *** 
[src/algorithms/signal_source/adapters/CMakeFiles/signal_source_adapters.dir/build.make:170:
 
src/algorithms/signal_source/adapters/CMakeFiles/signal_source_adapters.dir/osmosdr_signal_source.cc.o]
 Error 1
make[3]: *** Waiting for unfinished jobs
[ 95%] Building CXX object 
src/algorithms/acquisition/adapters/CMakeFiles/acquisition_adapters.dir/beidou_b3i_pcps_acquisition.cc.o
cd /<>/obj-x86_64-linux-gnu/src/algorithms/acquisition/adapters && 
/usr/bin/c++  -DGNSSSDR_INSTALL_DIR=\"/usr\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGE_FILES -I/<>/src/core/interfaces 
-I/<>/src/algorithms/libs/gsl/include 
-I/<>/src/algorithms/libs 
-I/<>/src/algorithms/acquisition/gnuradio_blocks 
-I/<>/src/algorithms/libs/opencl 
-I/<>/src/algorithms/acquisition/libs 
-I/<>/src/core/receiver 
-I/<>/src/algorithms/channel/libs 
-I/<>/src/core/system_parameters -isystem /usr/include/glog 
-isystem 
/<>/obj-x86_64-linux-gnu/volk_gnsssdr_module/build/include 
-isystem 
/<>/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/include  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
-fvisibility-inlines-hidden   -Wall -

Bug#957507: marked as done (lsmount: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 17:19:19 +
with message-id 
and subject line Bug#957507: fixed in lsmount 0.2.4-1
has caused the Debian Bug report #957507,
regarding lsmount: 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.)


-- 
957507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lsmount
Version: 0.2.3-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/lsmount_0.2.3-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 clean
make[1]: Entering directory '/<>'
rm -f lsmount lsmount.o lsmgrid.o options.o lsmcolors.o helper.o
rm -f doc/lsmount.1.gz
make[1]: Leaving directory '/<>'
   dh_clean
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
make -j4 "INSTALL=install --strip-program=true"
make[2]: Entering directory '/<>'
/usr/bin/gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 -lconfig 
-D_GNU_SOURCE `pkg-config --cflags libconfig` -O2 -Wall -pedantic -fPIE 
-D_FORTIFY_SOURCE=1 -c -o lsmount.o src/lsmount.c
/usr/bin/gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 -lconfig 
-D_GNU_SOURCE `pkg-config --cflags libconfig` -O2 -Wall -pedantic -fPIE 
-D_FORTIFY_SOURCE=1 -c -o lsmgrid.o src/lsmgrid.c
/usr/bin/gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 -lconfig 
-D_GNU_SOURCE `pkg-config --cflags libconfig` -O2 -Wall -pedantic -fPIE 
-D_FORTIFY_SOURCE=1 -c -o options.o src/options.c
/usr/bin/gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 -lconfig 
-D_GNU_SOURCE `pkg-config --cflags libconfig` -O2 -Wall -pedantic -fPIE 
-D_FORTIFY_SOURCE=1 -c -o lsmcolors.o src/lsmcolors.c
/usr/bin/gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 -lconfig 
-D_GNU_SOURCE `pkg-config --cflags libconfig` -O2 -Wall -pedantic -fPIE 
-D_FORTIFY_SOURCE=1 -c -o helper.o src/helper.c
In file included from /usr/include/string.h:495,
 from src/helper.c:5:
In function ‘strncat’,
inlined from ‘read_file_to_buf’ at src/helper.c:64:13:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:136:10: warning: 
‘__builtin_strncat’ output may be truncated copying 1 byte from a string of 
length 1 [-Wstringop-truncation]
  136 |   return __builtin___strncat_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
In file included from /usr/include/string.h:495,
 from src/lsmgrid.c:3:
In function ‘strncpy’,
inlined from ‘grid_load_from_buf’ at src/lsmgrid.c:153:7:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
src/lsmgrid.c: In function ‘grid_load_from_buf’:
src/lsmgrid.c:153:32: note: length computed here
  153 |   strncpy(dest, resolvBuf, strlen(resolvBuf)+1);
  |   

Bug#957371: marked as done (ipmitool: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 16:48:59 +
with message-id 
and subject line Bug#957371: fixed in ipmitool 1.8.18-9
has caused the Debian Bug report #957371,
regarding ipmitool: 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.)


-- 
957371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ipmitool
Version: 1.8.18-8
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/ipmitool_1.8.18-8_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

[...]
../../include/ipmitool/ipmi_sdr.h:312:23: warning: ISO C99 doesn’t support 
unnamed structs/unions [-Wpedantic]
  312 |} ATTRIBUTE_PACKING;
  |   ^
/bin/bash ../../libtool --silent  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wextra -std=gnu99 -pedantic -Wformat 
-Wformat-nonliteral -I /lib/modules/4.19.0-6-cloud-amd64/build/include 
-export-dynamic -Wl,-z,relro -Wl,-z,now -o libintf.la  ipmi_intf.lo 
lan/libintf_lan.la usb/libintf_usb.la lanplus/libintf_lanplus.la 
serial/libintf_serial.la free/libintf_free.la open/libintf_open.la 
imb/libintf_imb.la dummy/libintf_dummy.la -lreadline -lncurses -ltinfo 
-lreadline -lncurses -ltinfo  -lcrypto
copying selected object files to avoid basename conflicts...
make[5]: Leaving directory '/<>/src/plugins'
make[4]: Leaving directory '/<>/src/plugins'
make[4]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wextra -std=gnu99 -pedantic -Wformat 
-Wformat-nonliteral -I /lib/modules/4.19.0-6-cloud-amd64/build/include -c -o 
ipmitool.o ipmitool.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wextra -std=gnu99 -pedantic -Wformat 
-Wformat-nonliteral -I /lib/modules/4.19.0-6-cloud-amd64/build/include -c -o 
ipmishell.o ipmishell.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wextra -std=gnu99 -pedantic -Wformat 
-Wformat-nonliteral -I /lib/modules/4.19.0-6-cloud-amd64/build/include -c -o 
ipmievd.o ipmievd.c
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/stdio.h:27,
 from ipmievd.c:35:
/usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/stdio.h:27,
 from ipmishell.c:36:
/usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
In file included from ../include/ipmitool/ipmi_sel.h:38,
 from ipmievd.c:81:
../include/ipmitool/ipmi_sdr.h:312:23: warning: ISO C99 doesn’t support unnamed 
structs/unions [-Wpedantic]
  312 |} ATTRIBUTE_PACKING;

Bug#957364: marked as done (iotjs: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 16:48:54 +
with message-id 
and subject line Bug#957364: fixed in iotjs 1.0-2
has caused the Debian Bug report #957364,
regarding iotjs: 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.)


-- 
957364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:iotjs
Version: 1.0-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/iotjs_1.0-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[6]: Entering directory 
'/<>/obj-x86_64-linux-gnu/deps/jerry-host'
Scanning dependencies of target jerry-ext
make[6]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/deps/jerry-host'
make[6]: Entering directory 
'/<>/obj-x86_64-linux-gnu/deps/jerry-host'
Scanning dependencies of target jerry-port-default
Scanning dependencies of target jerry-port-default-minimal
make[6]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/deps/jerry-host'
make[6]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/deps/jerry-host'
make[6]: Entering directory 
'/<>/obj-x86_64-linux-gnu/deps/jerry-host'
make[6]: Entering directory 
'/<>/obj-x86_64-linux-gnu/deps/jerry-host'
[ 88%] Building C object 
jerry-ext/CMakeFiles/jerry-ext.dir/arg/arg-transform-functions.c.o
[ 88%] Building C object 
jerry-ext/CMakeFiles/jerry-ext.dir/arg/arg-js-iterator-helper.c.o
[ 89%] Building C object 
jerry-port/default/CMakeFiles/jerry-port-default.dir/default-date.c.o
[ 89%] Building C object 
jerry-port/default/CMakeFiles/jerry-port-default-minimal.dir/default-date.c.o
[ 90%] Building C object 
jerry-port/default/CMakeFiles/jerry-port-default.dir/default-external-context.c.o
[ 91%] Building C object jerry-ext/CMakeFiles/jerry-ext.dir/arg/arg.c.o
[ 92%] Building C object 
jerry-port/default/CMakeFiles/jerry-port-default-minimal.dir/default-fatal.c.o
[ 92%] Building C object 
jerry-port/default/CMakeFiles/jerry-port-default-minimal.dir/default-external-context.c.o
[ 92%] Building C object 
jerry-port/default/CMakeFiles/jerry-port-default.dir/default-fatal.c.o
[ 92%] Building C object 
jerry-ext/CMakeFiles/jerry-ext.dir/handler/handler-assert.c.o
[ 92%] Building C object 
jerry-port/default/CMakeFiles/jerry-port-default-minimal.dir/default-io.c.o
[ 93%] Building C object 
jerry-port/default/CMakeFiles/jerry-port-default-minimal.dir/defaultx-handler.c.o
[ 94%] Building C object 
jerry-ext/CMakeFiles/jerry-ext.dir/handler/handler-gc.c.o
[ 95%] Building C object 
jerry-port/default/CMakeFiles/jerry-port-default.dir/default-io.c.o
[ 96%] Building C object 
jerry-ext/CMakeFiles/jerry-ext.dir/handler/handler-print.c.o
[ 97%] Linking C static library ../../lib/libjerry-port-default-minimal.a
[ 97%] Building C object 
jerry-ext/CMakeFiles/jerry-ext.dir/handler/handler-register.c.o
[ 97%] Building C object 
jerry-port/default/CMakeFiles/jerry-port-default.dir/defaultx-handler.c.o
[ 98%] Linking C static library ../lib/libjerry-ext.a
[ 99%] Linking C static library ../../lib/libjerry-port-default.a
make[6]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/deps/jerry-host'
[ 99%] Built target jerry-port-default-minimal
make[6]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/deps/jerry-host'
[ 99%] Built target jerry-port-default
make[6]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/deps/jerry-host'
[ 99%] Built target jerry-ext
make[6]: Entering directory 
'/<>/obj-x86_64-linux-gnu/deps/jerry-host'
Scanning dependencies of target jerry
make[6]: Leavi

Bug#966500: python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)

[Nick Black]

pending
thanks

ok, I believe i have solved this. the problem arose when i moved
notcurses-pydemo from notcurses-bin to python3-notcurses
sometime since 1.5.1. so:

 * i've added the necessary Breaks+Replace to debian/control,
   and have built this as 1.6.9+dfsg.1-3. it ought remedy the
   reported problem. i have made them available at:

   https://www.dsscaw.com/repos/apt/debian/pool/main/n/notcurses/

i'll almost certainly be cutting 1.6.10 today or tomorrow, so
i'm inclined to wait until then, and get this all into one
release (especially since I can't yet upload my own packages,
and must harass my Sponsor to do so). if a DD would like to
upload the 1.6.9+dfsg.1-3 packages i've prepared before then,
email me, and we can do that.

Andreas, if a fix tomorrow or the next day isn't fast enough,
let me know and I can push on the 1.6.9+dfsg.1-3. thanks!

Bug#957532: mes: ftbfs with GCC-10

[Vagrant Cascadian]

On 2020-07-27, Vagrant Cascadian wrote:
> Debian has switched to gcc 10 by default for the development releases,
> and that currently breaks building mes.

Apparently, Adding -fcommon to CFLAGS does allow the build to complete.

from https://gcc.gnu.org/gcc-10/porting_to.html:

  C language issues
  Default to -fno-common

  A common mistake in C is omitting extern when declaring a global
  variable in a header file. If the header is included by several files
  it results in multiple definitions of the same variable. In previous
  GCC versions this error is ignored. GCC 10 defaults to -fno-common,
  which means a linker error will now be reported. To fix this, use
  extern in header files when declaring global variables, and ensure
  each global is defined in exactly one C file. If tentative definitions
  of particular variables need to be placed in a common block,
  __attribute__((__common__)) can be used to force that behavior even in
  code compiled without -fcommon. As a workaround, legacy C code where
  all tentative definitions should be placed into a common block can be
  compiled with -fcommon.


I'm thinking it's appropriate for mes to use -fcommon in this case,
since it uses it's own headers and libc.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#966093: Error: default OCI runtime "runc" not found: invalid argument -Workaround for wrong regular-user defaults

[Lorenzo M. Catucci]

Package: podman
Version: 2.0.3+dfsg1-1
Followup-For: Bug #966093

Dear Robby and Maintainer,

to avoid the described failure in running podman *as a regular user*, it's
enough to execute the command:

$ echo 'runtime = "crun"' > ~/.config/containers/libpod.conf

afterwards, both

$ podman info

and

$ podman run -it debian:sid

work correctly.

As a side note, I think a note about the need for sysctl
kernel.unprivileged_userns_clone=1 should be present also in podman's
README.Debian, and not only in buildah's



-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (777, 'testing'), (666, 'stable'), (333, 'oldstable'), (222, 
'unstable'), (1, 'experimental')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages podman depends on:
ii conmon 2.0.9-1
ii containernetworking-plugins 0.8.6-2
ii crun 0.14.1+dfsg-1
ii init-system-helpers 1.58
ii libc6 2.31-2
ii libdevmapper1.02.1 2:1.02.167-1+b1
ii libgpgme11 1.13.1-9
ii libseccomp2 2.4.3-1+b1

Versions of packages podman recommends:
ii buildah 1.15.0-4
ii fuse-overlayfs 1.0.0-1
ii slirp4netns 1.0.1-1
ii tini 0.18.0-1+b1
ii uidmap 1:4.8.1-1

Versions of packages podman suggests:
ii containers-storage 1.21.2+dfsg1-1

Bug#966093: Error: default OCI runtime "runc" not found: invalid argument - Workaround

[Lorenzo M. Catucci]

Package: podman
Version: 2.0.3+dfsg1-1
Followup-For: Bug #966093

Dear Robby and Maintainer,

while I can confirm `podman` doesn't correctly execute the `crun` runtime when
started from a regular user, after executing the following command from the
user's shell:

  $ echo 'runtime = "crun"' >  ~/.config/containers/libpod.conf

both

  $ podman info

and the suggested

  $ podman run -it debian:sid

run correctly for a regular user, only if the administrator correctly enabled
the  kernel.unprivileged_userns_clone sysctl via manually running

  $ sudo sysctl -w kernel.unprivileged_userns_clone=1

or setting it in /etc/sysctl.conf or in a /etc/sysctl.d/ snippet (I think this
should be documented also in podman's README.Debian as well as in buildah's)

Thank you all.



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (777, 'testing'), (666, 'stable'), (333, 'oldstable'), (222, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages podman depends on:
ii  conmon   2.0.9-1
ii  containernetworking-plugins  0.8.6-2
ii  crun 0.14.1+dfsg-1
ii  init-system-helpers  1.58
ii  libc62.31-2
ii  libdevmapper1.02.1   2:1.02.167-1+b1
ii  libgpgme11   1.13.1-9
ii  libseccomp2  2.4.3-1+b1
ii  runc 1.0.0~rc10+dfsg2-1

Versions of packages podman recommends:
ii  buildah 1.15.0-4
ii  fuse-overlayfs  1.0.0-1
ii  slirp4netns 1.0.1-1
ii  tini0.18.0-1+b1
ii  uidmap  1:4.8.1-1

Versions of packages podman suggests:
ii  containers-storage  1.21.2+dfsg1-1

-- debconf-show failed

Processed: retitle 966436 to scrambled property in identify -verbose output

[Debian Bug Tracking System]

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

> retitle 966436 scrambled property in identify -verbose output
Bug #966436 [src:imagemagick] ruby-mini-magick FTBFS with imagemagick 
8:6.9.11.24+dfsg-1
Changed Bug title to 'scrambled property in identify -verbose output' from 
'ruby-mini-magick FTBFS with imagemagick 8:6.9.11.24+dfsg-1'.
> thanks
Stopping processing here.

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

Processed: found 966436 in 8:6.9.11.24+dfsg-1

[Debian Bug Tracking System]

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

> found 966436 8:6.9.11.24+dfsg-1
Bug #966436 [src:imagemagick] ruby-mini-magick FTBFS with imagemagick 
8:6.9.11.24+dfsg-1
Marked as found in versions imagemagick/8:6.9.11.24+dfsg-1.
> thanks
Stopping processing here.

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

Bug#966175: marked as done (libopenblas0-pthread: segfault in scipy tests: calls Haswell)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 15:36:13 +
with message-id 
and subject line Bug#966175: fixed in openblas 0.3.10+ds-2
has caused the Debian Bug report #966175,
regarding libopenblas0-pthread: segfault in scipy tests: calls Haswell
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.)


-- 
966175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenblas0-pthread
Version: 0.3.10+ds-1
Severity: normal

Two (or at least 2) tests in scipy are segfaulting specifically with
libopenblas0-pthread.  If I configure alternatives to set
libblas.so.3-x86_64-linux-gnu and liblapack.so.3-x86_64-linux-gnu to
generic reference blas then the tests pass.

The libblas.so segfault occurs with both scipy 1.4.1-2 (unstable) and
1.5.2-1 (experimental).  The liblapack.so segfault occurs with scipy
1.5.2-1 but passes in 1.4.1-2

The segfaults can be reproduced manually (with python3-scipy installed
and blas/lapack configured to libopenblas0-pthread):
  python3 -m pytest 
/usr/lib/python3/dist-packages/scipy/cluster/tests/test_vq.py -k "krandinit" -v
  python3 -m pytest 
/usr/lib/python3/dist-packages/scipy/linalg/tests/test_decomp.py -v
(the second test here is the one that fails with scipy 1.5.2-1 in
test_orth_memory_efficiency, passes with 1.4.1-2. It also passes when
run on its own with  -k "test_orth_memory_efficiency")

gdb backtraces show libopenblas0-pthread is inculpated:

$ gdb python3
> run  -m pytest /usr/lib/python3/dist-packages/scipy/cluster/tests/test_vq.py 
> -k "krandinit" -v
../../../../../../usr/lib/python3/dist-packages/scipy/cluster/tests/test_vq.py::TestKMean::test_krandinit
 
Thread 2 "python3" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x74b6a700 (LWP 1589273)]
0x75c8d284 in dgemm_oncopy_HASWELL () from 
/lib/x86_64-linux-gnu/libblas.so.3
(gdb) bt
#0  0x75c8d284 in dgemm_oncopy_HASWELL () from 
/lib/x86_64-linux-gnu/libblas.so.3
#1  0x74d2a7c5 in ?? () from /lib/x86_64-linux-gnu/libblas.so.3
#2  0x74e3098d in ?? () from /lib/x86_64-linux-gnu/libblas.so.3
#3  0x77f62ea7 in start_thread (arg=) at 
pthread_create.c:477
#4  0x77cf7daf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


$ gdb python3
> run  -m pytest 
> /usr/lib/python3/dist-packages/scipy/linalg/tests/test_decomp.py -v
...
../../../../../../usr/lib/python3/dist-packages/scipy/linalg/tests/test_decomp.py::TestOverwrite::test_svd
 PASSED 
  [ 92%]
../../../../../../usr/lib/python3/dist-packages/scipy/linalg/tests/test_decomp.py::TestOverwrite::test_svdvals
 PASSED 
  [ 92%]
../../../../../../usr/lib/python3/dist-packages/scipy/linalg/tests/test_decomp.py::test_orth_memory_efficiency
 
Thread 9 "python3" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe0e10700 (LWP 1589405)]
0x7fffe27cc284 in dgemm_oncopy_HASWELL () from 
/lib/x86_64-linux-gnu/liblapack.so.3
(gdb) bt
#0  0x7fffe27cc284 in dgemm_oncopy_HASWELL () from 
/lib/x86_64-linux-gnu/liblapack.so.3
#1  0x7fffe18aeb62 in ?? () from /lib/x86_64-linux-gnu/liblapack.so.3
#2  0x7fffe1943c4d in ?? () from /lib/x86_64-linux-gnu/liblapack.so.3
#3  0x77f62ea7 in start_thread (arg=) at 
pthread_create.c:477
#4  0x77cf7daf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

In both cases the segfault happens at dgemm_oncopy_HASWELL.  Probably
worth mentioned I'm not using a haswell system:
  $ cat /proc/cpuinfo | grep 'model name' | uniq
  model name: Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz

So looks like the bug is that libopenblas0-pthread is invoking haswell
code on non-haswell systems. cpu.userbenchmark.com tells me that
i5-8365U is Whiskey Lake not Haswell

For completeness I tested other BLAS:
  openblas-openmp:  FAIL  (calls dgemm_oncopy_HASWELL)
  openblas-serial:  PASS
  blis-pthread: PASS
  blis-openmp:  PASS
  atlas:PASS


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

Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libopen

Bug#952673: marked as done (does not start automatically anymore on fresh installs)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 15:35:05 +
with message-id 
and subject line Bug#952673: fixed in knot-resolver 5.1.2-1
has caused the Debian Bug report #952673,
regarding does not start automatically anymore on fresh installs
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.)


-- 
952673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: knot-resolver
Severity: important
Version: 5.0.1-1

Hi,

thank you so much for uploading knot-resover 5 to sid, much appreciated.

While the upgrade from 3 works flawlessly, installing version 5 on a
system does not start a kresd instance in the system-kresd slice
automatically.

Hence no DNS resolution is active which leaves system in a non-working
state when relying upon the local dns resolver.

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: knot-resolver
Source-Version: 5.1.2-1
Done: =?utf-8?q?Santiago_Ruano_Rinc=C3=B3n?= 

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

Debian distribution maintenance software
pp.
Santiago Ruano Rincón  (supplier of updated knot-resolver 
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: Wed, 29 Jul 2020 17:07:51 +0200
Source: knot-resolver
Architecture: source
Version: 5.1.2-1
Distribution: unstable
Urgency: low
Maintainer: knot-resolver packagers 
Changed-By: Santiago Ruano Rincón 
Closes: 952673 966077
Changes:
 knot-resolver (5.1.2-1) unstable; urgency=low
 .
   * Team upload.
   * New upstream release. (Closes: #966077)
   * preinst, postinst maintainer scripts: base upgrade-4-to-5-related code
 from upstream distro/deb/.
   * Update debian/copyright to include CZ.NIC in debian/ files
   * Document changes and manual action required when upgrading from 3.x, in
 debian/NEWS and through debconf. (Closes: #952673)
 Thanks to Justin B Rye for reviewing the English template.
   * Add Build-Dep on po-debconf
   * Add debian/po
Checksums-Sha1:
 81825580f55884d808f5e24af2e0eed892f6 2393 knot-resolver_5.1.2-1.dsc
 1e1033e90d4d3dfcd6363d8837193f9e09cc49ad 1749236 
knot-resolver_5.1.2.orig.tar.xz
 060a0a2b454ff87a0b729836b0750f1c0de98a4d 833 
knot-resolver_5.1.2.orig.tar.xz.asc
 cbcaedf1890dc26a57433f198763a7e105591094 407320 
knot-resolver_5.1.2-1.debian.tar.xz
 b7c31e01c96adbcdb6c66267b980e44a6b878be2 9215 
knot-resolver_5.1.2-1_amd64.buildinfo
Checksums-Sha256:
 054a31725dfcbeb7e0718b09cda2ac799d77498ce1b5879c8a4ad34103ff8b95 2393 
knot-resolver_5.1.2-1.dsc
 caa4f941caf39080184554fb1310f383eba4b30d9c4c2215670d6b0a2de8f836 1749236 
knot-resolver_5.1.2.orig.tar.xz
 30ab349d682a126369dc678b384341ab30fbe4fcc02bed1e74af914c86a186b4 833 
knot-resolver_5.1.2.orig.tar.xz.asc
 7284908de599ea885697b2679e6ae6801f1bae5e4ae9b1728805500dcd3287ed 407320 
knot-resolver_5.1.2-1.debian.tar.xz
 bfd937051ec0aa613fe9453e39d18c385650dfd091b1ca3c7431aaf5fc5c444b 9215 
knot-resolver_5.1.2-1_amd64.buildinfo
Files:
 ff7397e41759ea43de51dc8f367d8a6f 2393 net optional knot-resolver_5.1.2-1.dsc
 1ca8828acae446f565f9d4c44813a8c0 1749236 net optional 
knot-resolver_5.1.2.orig.tar.xz
 5759177ff84d5723a2b6499eec7976ab 833 net optional 
knot-resolver_5.1.2.orig.tar.xz.asc
 23e997964ab9e1acf513cf9ff08caaee 407320 net optional 
knot-resolver_5.1.2-1.debian.tar.xz
 65d4ec6a974c38ee502e5d9fe6ed26a8 9215 net optional 
knot-resolver_5.1.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYIADIWIQRZVjztY8b+Ty43oH1itBCJKh26HQUCXyGRohQcc2FudGlhZ29A
ZGViaWFuLm9yZwAKCRBitBCJKh26HWkDAQC5SnYGtdFYVNmiz5fDRaOjMGuJ7Ebx
tXqs6dfyDKWp0AD/e984DWDfmNCEOVSg9oQHdrS3ET4af8oS4PBY73VwfAI=
=6goA
-END PGP SIGNATURE End Message ---

Bug#966463: marked as done (openblas breaks scipy autopkgtest: tests/test_vq.py::TestKMean::test_krandinit Segmentation fault)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 15:36:13 +
with message-id 
and subject line Bug#966175: fixed in openblas 0.3.10+ds-2
has caused the Debian Bug report #966175,
regarding openblas breaks scipy autopkgtest: 
tests/test_vq.py::TestKMean::test_krandinit Segmentation fault
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.)


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

Bug#966498: marked as done (libgd-perl: Dropped libgd-gd2-perl breaks a Recommends in lcov and prevents a clean upgrade)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 15:04:46 +
with message-id 
and subject line Bug#966498: fixed in libgd-perl 2.72-2
has caused the Debian Bug report #966498,
regarding libgd-perl: Dropped libgd-gd2-perl breaks a Recommends in lcov and 
prevents a clean upgrade
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.)


-- 
966498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgd-perl
Version: 2.72-1
Severity: important

libgd-perl (2.72-1) unstable; urgency=medium
[...]
  * Drop ancient Breakes/Replaces/Provides on libgd-gd2-{,noxpm-}perl.
[...]
 -- gregor herrmann   Wed, 22 Jul 2020 19:58:57 +0200

libgd-gd2-perl is not ancient. It is still used by lcov at least:

Package: lcov
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 456
Maintainer: Alastair McKinstry 
Architecture: all
Version: 1.14-2
Depends: perl:any, gcc, libjson-perl, libperlio-gzip-perl
Recommends: libgd-gd2-perl

signing-party 2.11-1 also has:
Recommends: default-mta | mail-transport-agent, dialog | whiptail, 
libgd-gd2-noxpm-perl | libgd-gd2-perl, libpaper-utils

This prevents a clean upgrade with aptitude, which checks Recommends.

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

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgd-perl depends on:
ii  libc6   2.31-2
ii  libgd3  2.3.0-2
ii  perl5.30.3-4
ii  perl-base [perlapi-5.30.3]  5.30.3-4

libgd-perl recommends no packages.

libgd-perl suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: libgd-perl
Source-Version: 2.72-2
Done: gregor herrmann 

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libgd-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 29 Jul 2020 16:33:47 +0200
Source: libgd-perl
Architecture: source
Version: 2.72-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 966498
Changes:
 libgd-perl (2.72-2) unstable; urgency=medium
 .
   * Team upload.
   * Add back Breaks/Replaces/Provides an libgd-gd2-perl and
 libgd-gd2-noxpm-perl.
 Apparently there are still at least 13 packages in the archive depending
 on them. This fact was unfortunately missed in the previous upload.
 (Closes: #966498)
Checksums-Sha1:
 a96a598a66604e06f6d140e6056bbb3f499268fb 2552 libgd-perl_2.72-2.dsc
 618e2afb61be69c6d64f77da0ccd810a6df97bfa 12328 libgd-perl_2.72-2.debian.tar.xz
Checksums-Sha256:
 ad62919cc6cc155171d28e5feea499b13e2ad7999a0ea8eb55a55102548453b2 2552 
libgd-perl_2.72-2.dsc
 d1a39c7459724bacb1b4c70a5216ad67f4955fc097f4103df62fa0c7ec56a5ce 12328 
libgd-perl_2.72-2.debian.tar.xz
Files:
 3fb595ac7a0a19fdbc3b61d0dd7c3827 2552 perl optional libgd-perl_2.72-2.dsc
 ac1cd9360d4a4f562eaf37808f045d81 12328 perl optional 
libgd-perl_2.72-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl8hiclfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZmIxAAoRmh5gkH0n+EvNp/3UwmecUQf3NW/VtaekiLv7U2MRR/Lrre/7++GsBZ
ijYOTRH2TBzNDsgaX7QSpNgErLb

Bug#966365: marked as done (shanty: Uninstallable due to removal of libgd-gd2-{,noxpm-}perl Provides in libgd-perl)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 15:04:46 +
with message-id 
and subject line Bug#966498: fixed in libgd-perl 2.72-2
has caused the Debian Bug report #966498,
regarding shanty: Uninstallable due to removal of libgd-gd2-{,noxpm-}perl 
Provides in libgd-perl
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.)


-- 
966498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shanty
Version: 3-4
Severity: serious
X-Debbugs-Cc: none, Axel Beckert , 
libgd-p...@packages.debian.org

shanty has become uninstallable on Debian Unstable because libgd-perl no
more provides the ancient package names libgd-gd2-noxpm-perl and
libgd-gd2-perl on which shanty still depends:

  Depends: perl, libgd-gd2-perl | libgd-gd2-noxpm-perl

Please change thisto the following"

  Depends: perl, libgd-perl

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages shanty depends on:
ii  libgd-perl [libgd-gd2-perl]  2.71-2+b1
ii  perl 5.30.3-4

shanty recommends no packages.

shanty suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libgd-perl
Source-Version: 2.72-2
Done: gregor herrmann 

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libgd-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 29 Jul 2020 16:33:47 +0200
Source: libgd-perl
Architecture: source
Version: 2.72-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 966498
Changes:
 libgd-perl (2.72-2) unstable; urgency=medium
 .
   * Team upload.
   * Add back Breaks/Replaces/Provides an libgd-gd2-perl and
 libgd-gd2-noxpm-perl.
 Apparently there are still at least 13 packages in the archive depending
 on them. This fact was unfortunately missed in the previous upload.
 (Closes: #966498)
Checksums-Sha1:
 a96a598a66604e06f6d140e6056bbb3f499268fb 2552 libgd-perl_2.72-2.dsc
 618e2afb61be69c6d64f77da0ccd810a6df97bfa 12328 libgd-perl_2.72-2.debian.tar.xz
Checksums-Sha256:
 ad62919cc6cc155171d28e5feea499b13e2ad7999a0ea8eb55a55102548453b2 2552 
libgd-perl_2.72-2.dsc
 d1a39c7459724bacb1b4c70a5216ad67f4955fc097f4103df62fa0c7ec56a5ce 12328 
libgd-perl_2.72-2.debian.tar.xz
Files:
 3fb595ac7a0a19fdbc3b61d0dd7c3827 2552 perl optional libgd-perl_2.72-2.dsc
 ac1cd9360d4a4f562eaf37808f045d81 12328 perl optional 
libgd-perl_2.72-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl8hiclfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZmIxAAoRmh5gkH0n+EvNp/3UwmecUQf3NW/VtaekiLv7U2MRR/Lrre/7++GsBZ
ijYOTRH2TBzNDsgaX7QSpNgErLbQEJx+4dy3SeAF1Cpwu+OpilLiAdvq1RKgX30t
p7TPN7fQcBIea+tprgZw//1Cr8ta4FidGpkk+VTrllbdumpMANUHW2bVV5OQWfW5
BEzFGqoJTAvGzN45EoS2ff0eYuv0OsNqrlMHhQyZV/w8MtB/ZnKWZ04TgvFlKPP/
atAZLvqSQ9ykqWCsMeM/OKMpBJz0x2GzlDnssGXd+Lze3NqFI+hsOuKRQ9btLlf4
FcdGdrTaxoBgqsXGvvB/eOQCM+SZFUUjVjUvqXxY1EbqlpxYpPX7WjeH9FrA5JNt
71ikNIRYY8ScHcbhxx0LBKcL3tJQIfeiWrYxvP4eRpYBpplwVjblIUs6onyDsRz0
n5zoaTUgwyrOLXPQBEnILrIvq4dTsOnhlIGBQPIbwzHEBNGTzzzXviqTIs1Z94AS
p+b4afiYVtN2F3RdnTP1L31GBeMWMqtkYG4OValBClJPZatq3nj+ladjoI+bYws9
5C/FvWJTS6P1pykXlnDVyxRD2B8VOaH/ODsoV9uEPwFqsVs85w5zDVWR5aZ2W9Hj
wl6XLSCmOjLr3AoFX9cW/vpetvlYIR/DYqFxN3vLESR5+IrarWQ=
=6hPp
-END PGP S

Bug#966436: files

[Cédric Boutillier]

Here are the promised files
Image: spec/fixtures/clipping_path.jpg
  Format: JPEG (Joint Photographic Experts Group JFIF format)
  Mime type: image/jpeg
  Class: DirectClass
  Geometry: 200x120+0+0
  Resolution: 72x72
  Print size: 2.8x1.7
  Units: PixelsPerInch
  Colorspace: sRGB
  Type: Palette
  Base type: Undefined
  Endianess: Undefined
  Depth: 8-bit
  Channel depth:
red: 8-bit
green: 8-bit
blue: 8-bit
  Channel statistics:
Pixels: 24000
Red:
  min: 208  (0.815686)
  max: 208 (0.815686)
  mean: 208 (0.815686)
  standard deviation: 0 (0)
  kurtosis: 4.19021e+54
  skewness: 0
  entropy: 0
Green:
  min: 176  (0.690196)
  max: 176 (0.690196)
  mean: 176 (0.690196)
  standard deviation: 0 (0)
  kurtosis: -1.73261e+54
  skewness: 0
  entropy: 0
Blue:
  min: 177  (0.694118)
  max: 177 (0.694118)
  mean: 177 (0.694118)
  standard deviation: 0 (0)
  kurtosis: 1.47046e+54
  skewness: -1.39375e+37
  entropy: 0
  Image statistics:
Overall:
  min: 176  (0.690196)
  max: 208 (0.815686)
  mean: 187 (0.73)
  standard deviation: 0 (0)
  kurtosis: -1.50004
  skewness: 0.70469
  entropy: 0
  Colors: 1
  Histogram:
 24000: (208,176,177) #D0B0B1 srgb(208,176,177)
  Rendering intent: Perceptual
  Gamma: 0.454545
  Chromaticity:
red primary: (0.64,0.33)
green primary: (0.3,0.6)
blue primary: (0.15,0.06)
white point: (0.3127,0.329)
  Background color: white
  Border color: srgb(223,223,223)
  Matte color: grey74
  Transparent color: black
  Interlace: None
  Intensity: Undefined
  Compose: Over
  Page geometry: 200x120+0+0
  Dispose: Undefined
  Iterations: 0
  Compression: JPEG
  Quality: 99
  Orientation: TopLeft
  Properties:
date:create: 2018-03-18T06:54:04+01:00
date:modify: 2018-03-18T06:54:04+01:00
exif:ColorSpace: 1
exif:DateTime: 2016:01:20 19:28:30
exif:ExifOffset: 172
exif:Orientation: 1
exif:PixelXDimension: 200
exif:PixelYDimension: 120
exif:ResolutionUnit: 2
exif:Software: Adobe Photoshop CC 2014 (Macintosh)
exif:thumbnail:Compression: 6
exif:thumbnail:JPEGInterchangeFormat: 310
exif:thumbnail:JPEGInterchangeFormatLength: 814
exif:thumbnail:ResolutionUnit: 2
exif:thumbnail:XResolution: 72/1
exif:thumbnail:YResolution: 72/1
exif:XResolution: 72/1
exif:YResolution: 72/1
icc:copyright: Copyright (c) 1998 Hewlett-Packard Company
icc:description: sRGB IEC61966-2.1
icc:manufacturer: IEC http://www.iec.ch
icc:model: IEC 61966-2.1 Default RGB colour space - sRGB
jpeg:colorspace: 2
jpeg:sampling-factor: 1x1,1x1,1x1
signature: 44f62c0b59893193d132f211e53e1d4fc8d92b27d5699d1ccdb340c97f9e6d12
  Clipping path: 

http://www.w3.org/2000/svg"; width="200" height="120">





  Profiles:
Profile-8bim: 3720 bytes
Profile-exif: 1130 bytes
Profile-icc: 3144 bytes
Profile-xmp: 4273 bytes
  Artifacts:
filename: spec/fixtures/clipping_path.jpg
verbose: true
  Tainted: False
  Filesize: 14616B
  Number pixels: 24000
  Pixels per second: 2.4MB
  User time: 0.010u
  Elapsed time: 0:01.009
  Version: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
Image:
  Filename: spec/fixtures/clipping_path.jpg
  Format: JPEG (Joint Photographic Experts Group JFIF format)
  Mime type: image/jpeg
  Class: DirectClass
  Geometry: 200x120+0+0
  Resolution: 72x72
  Print size: 2.8x1.7
  Units: PixelsPerInch
  Colorspace: sRGB
  Type: Palette
  Base type: Undefined
  Endianness: Undefined
  Depth: 8-bit
  Channel depth:
red: 8-bit
green: 8-bit
blue: 8-bit
  Channel statistics:
Pixels: 24000
Red:
  min: 208  (0.815686)
  max: 208 (0.815686)
  mean: 208 (0.815686)
  standard deviation: 0 (0)
  kurtosis: 4.19021e+54
  skewness: 0
  entropy: 0
Green:
  min: 176  (0.690196)
  max: 176 (0.690196)
  mean: 176 (0.690196)
  standard deviation: 0 (0)
  kurtosis: -1.73261e+54
  skewness: 0
  entropy: 0
Blue:
  min: 177  (0.694118)
  max: 177 (0.694118)
  mean: 177 (0.694118)
  standard deviation: 0 (0)
  kurtosis: 1.47046e+54
  skewness: -1.39375e+37
  entropy: 0
  Image statistics:
Overall:
  min: 176  (0.690196)
  max: 208 (0.815686)
  mean: 187 (0.73)
  standard deviation: 0 (0)
  kurtosis: -1.50004
  skewness: 0.70469
  entropy: 0
  Colors: 1
  Histogram:
24000: (208,176,177) #D0B0B1 srgb(208,176,177)
  Rendering intent: Perceptual
  Gamma: 0.454545
  Chromaticity:
red primary: (0.64,0.33)
green primary: (0.3,0.6)
blue primary: (0.15,0.06)
white point: (0.3127,0.329)
  Background color: white
  Border color: srgb(223,223,223)
  Matte color: grey74
  Transparent color: black
  Interlace: None
  Intensity: Undefined
  Compose: Over
  Page geometry: 200x120+0+0
  Di

Processed: found 966498 in libgd-perl/2.72-1

[Debian Bug Tracking System]

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

> found 966498 libgd-perl/2.72-1
Bug #966498 [libgd-perl] libgd-perl: Dropped libgd-gd2-perl breaks a Recommends 
in lcov and prevents a clean upgrade
Bug #966365 [libgd-perl] shanty: Uninstallable due to removal of 
libgd-gd2-{,noxpm-}perl Provides in libgd-perl
Ignoring request to alter found versions of bug #966498 to the same values 
previously set
Ignoring request to alter found versions of bug #966365 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#966436: reassign to imagemagick 8:6.9.11.24+dfsg-1

[Cédric Boutillier]

reassign 966436 src:imagemagick
found 966436 8:6.9.11.24+dfsg-1n
retitle scrambled property in identify -verbose output
affects 966436 ruby-mini-magick
thanks


ruby-mini-magick relies (too) heavily on a parsing of output of
imagemagick tools like identify.
The issue discussed here is caused by a change in the output of the
`identify -verbose` command from the version in testing
(8:6.9.10.23+dfsg-2.1+b2) and unstable (8:6.9.11.24+dfsg-1).

Attached are the corresponding outputs of the above command on the file
from ruby-mini-magick specs (spec/fixtures/clipping_path.jpg).

In the "unstable" version, the field Properties: has first subfield (on
line 96) with a strange name, which makes regexp filtering from
ruby-mini-magick choke. The content seems to be the same as the
"Clipping path:" field.

This subfield does not appear in the version of testing.

It is mentionned as a warning on newer versions of ruby-mini-magick that
the `details` method reading the output of `identify -verbose` in a
specific way, has become unreliable for newer versions of ImageMagick.
I am therefore disabling the corresping test in that code.

However, I believe that the output of identify -verbose should not
contain such cryptic field names, therefore, I am reassigning the but to
imagemagick package.

Thanks,

Cédric





signature.asc
Description: PGP signature

Processed (with 1 error): reassign to imagemagick 8:6.9.11.24+dfsg-1

[Debian Bug Tracking System]

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

> reassign 966436 src:imagemagick
Bug #966436 [src:ruby-mini-magick] ruby-mini-magick FTBFS with imagemagick 
8:6.9.11.24+dfsg-1
Bug reassigned from package 'src:ruby-mini-magick' to 'src:imagemagick'.
No longer marked as found in versions ruby-mini-magick/4.9.5-2.
Ignoring request to alter fixed versions of bug #966436 to the same values 
previously set
> found 966436 8:6.9.11.24+dfsg-1n
Bug #966436 [src:imagemagick] ruby-mini-magick FTBFS with imagemagick 
8:6.9.11.24+dfsg-1
The source 'imagemagick' and version '8:6.9.11.24+dfsg-1n' do not appear to 
match any binary packages
Marked as found in versions imagemagick/8:6.9.11.24+dfsg-1n.
> retitle scrambled property in identify -verbose output
Unknown command or malformed arguments to command.
> affects 966436 ruby-mini-magick
Bug #966436 [src:imagemagick] ruby-mini-magick FTBFS with imagemagick 
8:6.9.11.24+dfsg-1
Added indication that 966436 affects ruby-mini-magick
> thanks
Stopping processing here.

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

Bug#957700: marked as done (postgresql-mysql-fdw: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 14:45:01 +
with message-id 
and subject line Bug#957700: fixed in postgresql-mysql-fdw 2.5.3-2
has caused the Debian Bug report #957700,
regarding postgresql-mysql-fdw: 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.)


-- 
957700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:postgresql-mysql-fdw
Version: 2.5.3-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/postgresql-mysql-fdw_2.5.3-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: deparse.o:./build-12/./mysql_fdw.h:140: multiple definition of 
`_mysql_stmt_execute'; connection.o:./build-12/./mysql_fdw.h:140: first defined 
here
/usr/bin/ld: deparse.o:./build-12/./mysql_fdw.h:139: multiple definition of 
`_mysql_stmt_prepare'; connection.o:./build-12/./mysql_fdw.h:139: first defined 
here
/usr/bin/ld: deparse.o:./build-12/./mysql_fdw.h:138: multiple definition of 
`_mysql_options'; connection.o:./build-12/./mysql_fdw.h:138: first defined here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:178: multiple definition of 
`_mysql_num_rows'; connection.o:./build-12/./mysql_fdw.h:178: first defined here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:177: multiple definition of 
`_mysql_num_fields'; connection.o:./build-12/./mysql_fdw.h:177: first defined 
here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:176: multiple definition of 
`_mysql_errno'; connection.o:./build-12/./mysql_fdw.h:176: first defined here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:175: multiple definition of 
`_mysql_stmt_errno'; connection.o:./build-12/./mysql_fdw.h:175: first defined 
here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:173: multiple definition of 
`_mysql_get_proto_info'; connection.o:./build-12/./mysql_fdw.h:173: first 
defined here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:172: multiple definition of 
`_mysql_get_server_info'; connection.o:./build-12/./mysql_fdw.h:172: first 
defined here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:171: multiple definition of 
`_mysql_get_host_info'; connection.o:./build-12/./mysql_fdw.h:171: first 
defined here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:162: multiple definition of 
`_mysql_real_connect'; connection.o:./build-12/./mysql_fdw.h:162: first defined 
here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:161: multiple definition of 
`_mysql_ssl_set'; connection.o:./build-12/./mysql_fdw.h:161: first defined here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:160: multiple definition of 
`_mysql_init'; connection.o:./build-12/./mysql_fdw.h:160: first defined here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:158: multiple definition of 
`_mysql_store_result'; connection.o:./build-12/./mysql_fdw.h:158: first defined 
here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:157: multiple definition of 
`_mysql_close'; connection.o:./build-12/./mysql_fdw.h:157: first defined here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:156: multiple definition of 
`_mysql_error'; connection.o:./build-12/./mysql_fdw.h:156: first defined here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:155: multiple definition of 
`_mysql_fetch_fields'; connection.o:./build-12/./mysql_fdw.h:155: first defined 
here
/usr/bin/ld: mysql_query.o:./build-12/./mysql_fdw.h:154: multiple definition of 
`_mysql_fe

Bug#966498: marked as pending in libgd-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #966498 in libgd-perl 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/perl-team/modules/packages/libgd-perl/-/commit/ef0f4a08e2ab83646b82526d739796cfe0fdab64


Add back Breaks/Replaces/Provides an libgd-gd2-perl and libgd-gd2-noxpm-perl.

Apparently there are still at least 13 packages in the archive depending on
them. This fact was unfortunately missed in the previous upload.

Closes: #966498


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/966498

Processed (with 1 error): Re: Processed (with 5 errors): Re: Bug#966498: libgd-perl: Dropped libgd-gd2-perl breaks a Recommends in lcov and prevents a clean upgrade

[Debian Bug Tracking System]

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

> reassign 966365 libgd-perl
Bug #966365 [shanty] shanty: Uninstallable due to removal of 
libgd-gd2-{,noxpm-}perl Provides in libgd-perl
Bug reassigned from package 'shanty' to 'libgd-perl'.
No longer marked as found in versions shanty/3-4.
Ignoring request to alter fixed versions of bug #966365 to the same values 
previously set
> forcemerge 966498 966365
Bug #966498 [libgd-perl] libgd-perl: Dropped libgd-gd2-perl breaks a Recommends 
in lcov and prevents a clean upgrade
Bug #966365 [libgd-perl] shanty: Uninstallable due to removal of 
libgd-gd2-{,noxpm-}perl Provides in libgd-perl
Severity set to 'important' from 'serious'
Marked as found in versions libgd-perl/2.72-1.
Bug #966498 [libgd-perl] libgd-perl: Dropped libgd-gd2-perl breaks a Recommends 
in lcov and prevents a clean upgrade
Added tag(s) bullseye and sid.
Merged 966365 966498
> severity 966498 serious
Bug #966498 [libgd-perl] libgd-perl: Dropped libgd-gd2-perl breaks a Recommends 
in lcov and prevents a clean upgrade
Bug #966365 [libgd-perl] shanty: Uninstallable due to removal of 
libgd-gd2-{,noxpm-}perl Provides in libgd-perl
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> found 966498 libgd-perl 2.72966498
Unknown command or malformed arguments to command.
> tag 966498 + sid bullseye confirmed
Bug #966498 [libgd-perl] libgd-perl: Dropped libgd-gd2-perl breaks a Recommends 
in lcov and prevents a clean upgrade
Bug #966365 [libgd-perl] shanty: Uninstallable due to removal of 
libgd-gd2-{,noxpm-}perl Provides in libgd-perl
Added tag(s) confirmed.
Added tag(s) confirmed.
> affects 966498 + circos gbrowse ircmarkers libbio-graphics-perl 
> libcatalyst-view-gd-perl libchado-perl libchart-strip-perl libgd-svg-perl 
> libtemplate-plugin-gd-perl libtest-image-gd-perl lightsquid otrs2 shanty
Bug #966498 [libgd-perl] libgd-perl: Dropped libgd-gd2-perl breaks a Recommends 
in lcov and prevents a clean upgrade
Bug #966365 [libgd-perl] shanty: Uninstallable due to removal of 
libgd-gd2-{,noxpm-}perl Provides in libgd-perl
Added indication that 966498 affects circos, gbrowse, ircmarkers, 
libbio-graphics-perl, libcatalyst-view-gd-perl, libchado-perl, 
libchart-strip-perl, libgd-svg-perl, libtemplate-plugin-gd-perl, 
libtest-image-gd-perl, lightsquid, otrs2, and shanty
Added indication that 966365 affects circos, gbrowse, ircmarkers, 
libbio-graphics-perl, libcatalyst-view-gd-perl, libchado-perl, 
libchart-strip-perl, libgd-svg-perl, libtemplate-plugin-gd-perl, 
libtest-image-gd-perl, lightsquid, otrs2, and shanty
> thanks
Stopping processing here.

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

Bug#957099: marked as done (comskip: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 14:41:53 +
with message-id 
and subject line Bug#957099: fixed in comskip 0.82.009+ds.1-2
has caused the Debian Bug report #957099,
regarding comskip: 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.)


-- 
957099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:comskip
Version: 0.82.009+ds.1-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/comskip_0.82.009+ds.1-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

[...]
 from comskip.c:16:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output 4 or more bytes (assuming 4099) into a 
destination of size 4096
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
comskip.c:9158:39: warning: ‘comskip.ini’ directive writing 11 bytes into a 
region of size between 0 and 255 [-Wformat-overflow=]
 9158 | sprintf(inifilename, "%s%ccomskip.ini", HomeDir, 
PATH_SEPARATOR);
  |   ^~~
In file included from /usr/include/stdio.h:867,
 from platform.h:15,
 from comskip.c:16:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output between 13 and 268 bytes into a destination of 
size 256
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
comskip.c:9161:35: warning: ‘comskip.exe’ directive writing 11 bytes into a 
region of size between 0 and 255 [-Wformat-overflow=]
 9161 | sprintf(exefilename, "%s%ccomskip.exe", HomeDir, 
PATH_SEPARATOR);
  |   ^~~
In file included from /usr/include/stdio.h:867,
 from platform.h:15,
 from comskip.c:16:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output between 13 and 268 bytes into a destination of 
size 256
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
comskip.c:9162:36: warning: ‘comskip.dictionary’ directive writing 18 bytes 
into a region of size between 0 and 255 [-Wformat-overflow=]
 9162 | sprintf(dictfilename, "%s%ccomskip.dictionary", HomeDir, 
PATH_SEPARATOR);
  |^~
In file included from /usr/include/stdio.h:867,
 from platform.h:15,
 from comskip.c:16:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: 
‘__builtin___sprintf_chk’ output between 20 and 275 bytes into a destination of 
size 256
   36 |   return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
  |  ^~
   37 |   __bos (__s), __fmt, __va_arg_pack ());
  |   ~
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:47

Processed: Bug#966498 marked as pending in libgd-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #966498 [libgd-perl] libgd-perl: Dropped libgd-gd2-perl breaks a Recommends 
in lcov and prevents a clean upgrade
Bug #966365 [libgd-perl] shanty: Uninstallable due to removal of 
libgd-gd2-{,noxpm-}perl Provides in libgd-perl
Added tag(s) pending.
Added tag(s) pending.

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

Processed (with 5 errors): Re: Bug#966498: libgd-perl: Dropped libgd-gd2-perl breaks a Recommends in lcov and prevents a clean upgrade

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 966365
Bug #966498 [libgd-perl] libgd-perl: Dropped libgd-gd2-perl breaks a Recommends 
in lcov and prevents a clean upgrade
Unable to merge bugs because:
package of #966365 is 'shanty' not 'libgd-perl'
Failed to forcibly merge 966498: Did not alter merged bugs.

> severity -1 serious
Failed to set severity of Bug 966498 to serious: failed to get lock on 
/srv/bugs.debian.org/spool/lock/966498 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/966498 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

> found -1 libgd-perl 2.72-1
Unknown command or malformed arguments to command.

> tag -1 + sid bullseye confirmed
Failed to alter tags of Bug 966498: failed to get lock on 
/srv/bugs.debian.org/spool/lock/966498 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/966498 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

> affects -1 + circos gbrowse ircmarkers libbio-graphics-perl 
> libcatalyst-view-gd-perl libchado-perl libchart-strip-perl libgd-svg-perl 
> libtemplate-plugin-gd-perl libtest-image-gd-perl lightsquid otrs2 shanty
Failed to mark 966498 as affecting package(s): failed to get lock on 
/srv/bugs.debian.org/spool/lock/966498 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/966498 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/966498 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.de

Bug#957700: marked as pending in postgresql-mysql-fdw

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #957700 in postgresql-mysql-fdw 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/postgresql-mysql-fdw/-/commit/02b2d13bb2d0158e315ea4e0efcf967eef7edc1f


Fix build failure with gcc 10. (Closes: #957700)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/957700

Processed: Bug#957700 marked as pending in postgresql-mysql-fdw

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #957700 [src:postgresql-mysql-fdw] postgresql-mysql-fdw: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#957815: marked as done (slony1-2: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 13:52:12 +
with message-id 
and subject line Bug#957815: fixed in slony1-2 2.2.8-4
has caused the Debian Bug report #957815,
regarding slony1-2: 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.)


-- 
957815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:slony1-2
Version: 2.2.8-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/slony1-2_2.2.8-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

[...]
/usr/bin/ld: cleanup_thread.o:./src/slon/confoptions.h:54: multiple definition 
of `sql_on_connection'; slon.o:./src/slon/confoptions.h:54: first defined here
/usr/bin/ld: cleanup_thread.o:./src/slon/confoptions.h:53: multiple definition 
of `log_timestamp_format'; slon.o:./src/slon/confoptions.h:53: first defined 
here
/usr/bin/ld: cleanup_thread.o:./src/slon/confoptions.h:52: multiple definition 
of `drop_indices'; slon.o:./src/slon/confoptions.h:52: first defined here
/usr/bin/ld: cleanup_thread.o:./src/slon/confoptions.h:51: multiple definition 
of `logtimestamp'; slon.o:./src/slon/confoptions.h:51: first defined here
/usr/bin/ld: cleanup_thread.o:./src/slon/confoptions.h:50: multiple definition 
of `logpid'; slon.o:./src/slon/confoptions.h:50: first defined here
/usr/bin/ld: cleanup_thread.o:./src/slon/confoptions.h:48: multiple definition 
of `Use_syslog'; slon.o:./src/slon/confoptions.h:48: first defined here
/usr/bin/ld: cleanup_thread.o:./src/slon/confoptions.h:47: multiple definition 
of `Syslog_facility'; slon.o:./src/slon/confoptions.h:47: first defined here
/usr/bin/ld: cleanup_thread.o:./src/slon/confoptions.h:46: multiple definition 
of `Syslog_ident'; slon.o:./src/slon/confoptions.h:46: first defined here
/usr/bin/ld: scheduler.o:./src/slon/confoptions.h:56: multiple definition of 
`command_on_logarchive'; slon.o:./src/slon/confoptions.h:56: first defined here
/usr/bin/ld: scheduler.o:./src/slon/confoptions.h:55: multiple definition of 
`lag_interval'; slon.o:./src/slon/confoptions.h:55: first defined here
/usr/bin/ld: scheduler.o:./src/slon/confoptions.h:54: multiple definition of 
`sql_on_connection'; slon.o:./src/slon/confoptions.h:54: first defined here
/usr/bin/ld: scheduler.o:./src/slon/confoptions.h:53: multiple definition of 
`log_timestamp_format'; slon.o:./src/slon/confoptions.h:53: first defined here
/usr/bin/ld: scheduler.o:./src/slon/confoptions.h:52: multiple definition of 
`drop_indices'; slon.o:./src/slon/confoptions.h:52: first defined here
/usr/bin/ld: scheduler.o:./src/slon/confoptions.h:51: multiple definition of 
`logtimestamp'; slon.o:./src/slon/confoptions.h:51: first defined here
/usr/bin/ld: scheduler.o:./src/slon/confoptions.h:50: multiple definition of 
`logpid'; slon.o:./src/slon/confoptions.h:50: first defined here
/usr/bin/ld: scheduler.o:./src/slon/confoptions.h:48: multiple definition of 
`Use_syslog'; slon.o:./src/slon/confoptions.h:48: first defined here
/usr/bin/ld: scheduler.o:./src/slon/confoptions.h:47: multiple definition of 
`Syslog_facility'; slon.o:./src/slon/confoptions.h:47: first defined here
/usr/bin/ld: scheduler.o:./src/slon/confoptions.h:46: multiple definition of 
`Syslog_ident'; slon.o:./src/slon/confoptions.h:46: first defined here
/usr/bin/ld: dbutils.o:./src/slon/confoptions.h:54: multiple definition of 
`sql_on_connection'; slon.o:./src/slon/confoptions.h:54: first defined here
/usr/bin/ld: dbuti

Bug#957815: marked as pending in slony1-2

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #957815 in slony1-2 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/slony1-2/-/commit/c4759164a59c85eecab00e6abb73565db524fdb7


Pull patch from upstream to fix compiling with -fno-common. (Closes: #957815)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/957815

Processed: Bug#957815 marked as pending in slony1-2

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#957627: marked as done (octave-optiminterp: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 13:20:04 +
with message-id 
and subject line Bug#957627: fixed in octave-optiminterp 0.3.6-3
has caused the Debian Bug report #957627,
regarding octave-optiminterp: 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.)


-- 
957627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:octave-optiminterp
Version: 0.3.6-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/octave-optiminterp_0.3.6-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

[...]
   dh_octave_version -O--buildsystem=octave
Checking the Octave version... ok
   dh_auto_configure -O--buildsystem=octave
   dh_auto_build -O--buildsystem=octave
   dh_auto_test -O--buildsystem=octave
   create-stamp debian/debhelper-build-stamp
   dh_testroot -O--buildsystem=octave
   dh_prep -O--buildsystem=octave
   dh_auto_install -O--buildsystem=octave
octave --no-gui --no-history --silent --no-init-file --no-window-system 
/usr/share/dh-octave/install-pkg.m
warning: creating installation directory 
/<>/debian/octave-optiminterp/usr/share/octave/packages
warning: called from
install at line 30 column 5
pkg at line 441 column 9
/usr/share/dh-octave/install-pkg.m at line 43 column 1
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for mkoctfile... /usr/bin/mkoctfile --verbose
checking for octave-config... /usr/bin/octave-config
checking for F77_FUNC... g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/octave-5.2.0/octave/.. -I/usr/include/octave-5.2.0/octave  
-pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-securityconftest.cc -o 
conftest.o
yes
checking for octave... /usr/bin/octave
checking for VERSION in octave-config... 5.2.0
checking for mkoctfile... mkoctfile
checking whether we are using the GNU Fortran compiler... yes
checking whether mkoctfile accepts -g... yes
checking for Fortran flag to compile .F90 files... none
checking whether mkoctfile accepts Fortran 90... yes
configure: creating ./config.status
config.status: creating Makefile

octave optiminterp is configured with
   octave:  /usr/bin/octave (version 5.2.0)
   mkoctfile:   /usr/bin/mkoctfile --verbose for Octave 5.2.0
   octave-config: /usr/bin/octave-config for Octave 5.2.0
   optiminterp toolbox: yes

make[1]: Entering directory '/<>/src'
warning: LFLAGS is deprecated and will be removed in a future version of 
Octave, use LDFLAGS instead
/usr/bin/mkoctfile --verbose -DHAVE_OCTAVE_52 -v -c optiminterp.cc
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/octave-5.2.0/octave/.. -I/usr/include/octave-5.2.0/octave  
-pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security-DHAVE_OCTAVE_52 
optiminterp.cc -o optiminterp.o
FFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong" 
/usr/bin/mkoctfile --verbose -DHAVE_OCTAVE_52 -v -c optimal_interpolation.F90
gfortran -c -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong-DHA

Processed: Bug#957627 marked as pending in octave-optiminterp

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#957627: marked as pending in octave-optiminterp

[Rafael Laboissiere]

Control: tag -1 pending

Hello,

Bug #957627 in octave-optiminterp 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-octave-team/octave-optiminterp/-/commit/f8dc3a7958377be990cabfd445318d26129cf0b9


d/p/compile-with-gfortran-10.patch: New patch

Closes: #957627


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/957627

Bug#957289: gnss-sdr: ftbfs with GCC-10

[Carles Fernandez]

Dear all,


this should be fixed in

   https://mentors.debian.net/package/gnss-sdr/ 


The respective dsc file can be found at:

   https://mentors.debian.net/debian/pool/main/g/gnss-sdr/gnss-sdr_0.0.13-1.dsc 



I’ve asked Christoph Berg to kindly sponsor the upload.

Best regards,
Carles


> El 29 jul 2020, a las 12:26, Gianfranco Costamagna  
> escribió:
> 
> control: tags -1 fixed-upstream
> 
> The new release is out, and might be fixing also this issue...
> 
> I tried a build and resulted in
> https://github.com/gnss-sdr/gnss-sdr/issues/414
> 
> but this looks like more a gnuradio issue, not sure who is to blame...
> (even boost might be faulty)
> 
> 
> G.
> 
> On Fri, 17 Apr 2020 11:01:35 + Matthias Klose  wrote:
>> Package: src:gnss-sdr
>> Version: 0.0.11-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/gnss-sdr_0.0.11-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 
>> /<>/src/algorithms/signal_source/adapters/osmosdr_signal_source.cc:32:
>> /usr/include/boost/format/alt_sstream_impl.hpp: In instantiation of 
>> ‘boost::io::basic_altstringbuf::int_type 
>> boost::io::basic_altstringbuf> Alloc>::overflow(boost::io::basic_altstringbuf::int_type) 
>> [with Ch = char; Tr = std::char_traits; Alloc = std::allocator; 
>> boost::io::basic_altstringbuf::int_type = int]’:
>> /usr/include/boost/format/alt_sstream_impl.hpp:227:9:   required from here
>> /usr/include/boost/format/alt_sstream_impl.hpp:261:45: error: no matching 
>> function for call to ‘std::allocator::allocate(std::size_t&, char*)’
>>  261 | newptr = alloc_.allocate(new_size, is_allocated_? 
>> oldptr : 0);
>>  |  
>> ~~~^
>> In file included from /usr/include/c++/10/string:41,
>> from /usr/include/c++/10/stdexcept:39,
>> from /usr/include/c++/10/system_error:41,
>> from /usr/include/c++/10/bits/std_mutex.h:39,
>> from /usr/include/c++/10/condition_variable:40,
>> from 
>> /<>/src/core/receiver/concurrent_queue.h:35,
>> from 
>> /<>/src/algorithms/signal_source/adapters/osmosdr_signal_source.h:36,
>> from 
>> /<>/src/algorithms/signal_source/adapters/osmosdr_signal_source.cc:32:
>> /usr/include/c++/10/bits/allocator.h:171:7: note: candidate: ‘constexpr _Tp* 
>> std::allocator<  >::allocate(std::size_t) [with _Tp 
>> = char; std::size_t = long unsigned int]’
>>  171 |   allocate(size_t __n)
>>  |   ^~~~
>> /usr/include/c++/10/bits/allocator.h:171:7: note:   candidate expects 1 
>> argument, 2 provided
>> make[3]: *** 
>> [src/algorithms/signal_source/adapters/CMakeFiles/signal_source_adapters.dir/build.make:170:
>>  
>> src/algorithms/signal_source/adapters/CMakeFiles/signal_source_adapters.dir/osmosdr_signal_source.cc.o]
>>  Error 1
>> make[3]: *** Waiting for unfinished jobs
>> [ 95%] Building CXX object 
>> src/algorithms/acquisition/adapters/CMakeFiles/acquisition_adapters.dir/beidou_b3i_pcps_acquisition.cc.o
>> cd /<>/obj-x86_64-linux-gnu/src/algorithms/acquisition/adapters 
>> && /usr/bin/c++  -DGNSSSDR_INSTALL_DIR=\"/usr\" -D_FILE_OFFSET_BITS=64 
>> -D_LARGEFILE_SOURCE -D_LARGE_FILES -I/<>/src/core/interfaces 
>> -I/<>/src/algorithms/libs/gsl/include 
>> -I/<>/src/algorithms/libs 
>> -I/<>/src/algorithms/acquisition/gnuradio_blocks 
>> -I/<>/src/algorithms/libs/opencl 
>> -I/<>/src/algorithms/acquisition/libs 
>> -I/<>/src/core/receiver 
>> -I/<>/src/algorithms/channel/libs 
>> -I/<>/src/core/system_parameters -isystem /usr/include/glog 
>> -isystem 
>> 

Bug#966501: 2.0.3 REST API regression: Failed to parse parameters for /v1.12/libpod/events: unexpected end of JSON input

[Martin Pitt]

Package: podman
Version: 2.0.3+dfsg1-1
Severity: serious
Tags: upsteam fixed-upstream

Version 2.0.3 breaks the REST API really hard, which breaks cockpit-podman and
any other API user. This is tracked here:

  https://github.com/containers/podman/issues/7078

This has been fixed upstream and will be in 2.0.4. I'd like to block this
version from testing to avoid the regression.

If you disagree and would rather get this in ASAP (given how young the package
is still), I'm fine with that as well, and disable the cockpit-podman test on
debian-testing for a while.

Thanks,

Martin

Bug#966500: python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)

[Nick Black]

#thanks

Thank you for filing my first Debian bug! How exciting, and at
the same time embarrassing. I should have caught this before
uploading. A fix is obvious, and I ought be able to accomplish
it within the Debian packaging proper, rather than requiring a
new release (I'm the upstream author).

Expect a +dfsg.1-3 built very soon. I'm not yet even a DM, so
I'll have to wait on a DD to upload the new build to the
archive. I'll provide a link here, and poke one of my sponsors.

Bug#966500: python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)

[Andreas Beckmann]

Package: python3-notcurses
Version: 1.6.9+dfsg.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../python3-notcurses_1.6.9+dfsg.1-2_amd64.deb ...
  Unpacking python3-notcurses (1.6.9+dfsg.1-2) over (1.5.1+dfsg.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-notcurses_1.6.9+dfsg.1-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/notcurses-pydemo', which is also in package 
notcurses-bin 1.5.1+dfsg.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-notcurses_1.6.9+dfsg.1-2_amd64.deb


cheers,

Andreas


notcurses-bin=1.5.1+dfsg.1-1_python3-notcurses=1.6.9+dfsg.1-2.log.gz
Description: application/gzip

Bug#957785: marked as done (see: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 11:33:55 +
with message-id 
and subject line Bug#957785: fixed in see 0.72-7
has caused the Debian Bug report #957785,
regarding see: 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.)


-- 
957785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:see
Version: 0.72-6
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/see_0.72-6_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

[...]
server.c:326:2: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  326 |  write(remote,"SS LAUNCH\n",10);
  |  ^~
gcc -DHAVE_CONFIG_H -I. -I.. `pkg-config --cflags gtk+-2.0`  -Wdate-time 
-D_FORTIFY_SOURCE=2 -D SDIR=\"/usr/share/seetxt-runtime\" -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -D_FILE_OFFSET_BITS=64 -c -o 
seetxt-util.o `test -f 'util.c' || echo './'`util.c
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
 from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
 from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
 from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
 from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
 from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:33,
 from main.h:21,
 from util.c:11:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is 
deprecated [-Wdeprecated-declarations]
  236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
  | ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from main.h:21,
 from util.c:11:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
  679 | {
  | ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126,
 from main.h:21,
 from util.c:11:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: 
Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #933031 [pristine-tar] pristine-tar: unable to unpack some deltas of 
version 2
Added tag(s) patch.

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

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

[Steve McIntyre]

Control: tags -1 +patch

On Tue, Jul 28, 2020 at 04:17:08PM +0100, Steve McIntyre wrote:
>Control: severity -1 grave

...

>IMHO this has to be a grave bug - without reimporting this repo we
>can't get our older revisions back. Then I'm worried that this will
>break things if we need to go back and rebuild older versions (using
>older tooling). pristine-tar needs to be safe for data here. :-(
>
>I've done a git bisect of the pristine-tar repo to see where things
>broke, and that clearly tells me:
>
>...
>f287f10b48c3ca5a30db13dbf3ba918c47a943bb is the first bad commit
>commit f287f10b48c3ca5a30db13dbf3ba918c47a943bb
>Author: Tomasz Buchert 
>Date:   Fri Jan 13 23:28:04 2017 +0100
>
>fix #851286
>
>:100755 100755 1a34e953ba363ae1e284b97f83f63f6ef80ea544 
>3ba76f79d376d011451b8c572b20e185b715bed1 M  pristine-tar
>:04 04 84bc809be6b4dcf81cfce71f0550858957a3e92f 
>f8eb72beb458cbd9770f88f0f4efc00f0c75a299 M  test
>bisect run success
>...
>
>I hope that helps the maintainers - shout if you'd like more help debugging.

I've carried on and looked at the code. The attached patch makes
things work for me, at the expense of YA thing added to the @try
loop. But I'll take that over failure!

Having looked at this code a little, I'm now also a little concerned
about the way the fallbacks work, i.e. applied one at a time
independently. I'm thinking that there could well be cases where a
stored tarball might need more than one of the workaround/retry
options. Maybe I'm over-thinking it.

Also submitted this as an MR:

  https://salsa.debian.org/debian/pristine-tar/-/merge_requests/7

in case you'd prefer that.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< sladen> I actually stayed in a hotel and arrived to find a post-it
  note stuck to the mini-bar saying "Paul: This fridge and
  fittings are the correct way around and do not need altering"
diff --git a/pristine-tar b/pristine-tar
index 0fe132e..081dca1 100755
--- a/pristine-tar
+++ b/pristine-tar
@@ -560,6 +560,33 @@ sub recreatetarball_broken_numeric_owner {
   return recreatetarball_helper();
 }
 
+sub recreatetarball_broken_verbatim {
+  # To fix #851286, the option --verbatim-files-from was added by
+  # default. But now some older older stored tarballs won't reproduce
+  # (#933031). Try again *without* that option to tar.
+  my %options = @_;
+  my $tempdir = $recreatetarball_tempdir;
+
+  my $ret = "$tempdir/recreatetarball";
+  my @cmd = (
+$tar_program, "cf",
+$ret, "--owner",
+0,"--group",
+0,"--numeric-owner",
+"-C", "$tempdir/workdir",
+"--no-recursion", "--mode",
+"0644",
+"--files-from",   "$tempdir/manifest"
+  );
+  if (exists $options{tar_format}) {
+push @cmd, ("-H", $options{tar_format});
+  }
+
+  doit(@cmd);
+
+  return $ret;
+}
+
 sub gentar {
   my $deltafile = shift;
   my $tarball   = shift;
@@ -614,6 +641,7 @@ sub gentar {
   %opts
 );
   };
+  push @try, \&recreatetarball_broken_verbatim;
   push @try, \&recreatetarball_broken_numeric_owner;
 
   my $ok;

Bug#960680: marked as done (ruby-actionpack-page-caching: CVE-2020-8159)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 16:02:40 +0530
with message-id <1596018760.438...@onenetbeyond.org>
and subject line close already fixed bug
has caused the Debian Bug report #960680,
regarding ruby-actionpack-page-caching: CVE-2020-8159
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.)


-- 
960680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-actionpack-page-caching
Version: 1.1.0-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for ruby-actionpack-page-caching.

CVE-2020-8159[0]:
| There is a vulnerability in actionpack_page-caching gem < v1.2.1
| that allows an attacker to write arbitrary files to a web server,
| potentially resulting in remote code execution if the attacker can
| write unescaped ERB to a view.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-8159
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8159
[1] https://groups.google.com/forum/#!topic/rubyonrails-security/CFRVkEytdP8

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---

Fixed in version ruby-actionpack-page-caching/1.2.2-1--- End Message ---

Processed: Re: gnss-sdr: ftbfs with GCC-10

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #957289 [src:gnss-sdr] gnss-sdr: ftbfs with GCC-10
Added tag(s) fixed-upstream.

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

Bug#957289: gnss-sdr: ftbfs with GCC-10

[Gianfranco Costamagna]

control: tags -1 fixed-upstream

The new release is out, and might be fixing also this issue...

I tried a build and resulted in
https://github.com/gnss-sdr/gnss-sdr/issues/414

but this looks like more a gnuradio issue, not sure who is to blame...
(even boost might be faulty)


G.

On Fri, 17 Apr 2020 11:01:35 + Matthias Klose  wrote:
> Package: src:gnss-sdr
> Version: 0.0.11-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/gnss-sdr_0.0.11-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 
> /<>/src/algorithms/signal_source/adapters/osmosdr_signal_source.cc:32:
> /usr/include/boost/format/alt_sstream_impl.hpp: In instantiation of 
> ‘boost::io::basic_altstringbuf::int_type 
> boost::io::basic_altstringbuf Alloc>::overflow(boost::io::basic_altstringbuf::int_type) 
> [with Ch = char; Tr = std::char_traits; Alloc = std::allocator; 
> boost::io::basic_altstringbuf::int_type = int]’:
> /usr/include/boost/format/alt_sstream_impl.hpp:227:9:   required from here
> /usr/include/boost/format/alt_sstream_impl.hpp:261:45: error: no matching 
> function for call to ‘std::allocator::allocate(std::size_t&, char*)’
>   261 | newptr = alloc_.allocate(new_size, is_allocated_? 
> oldptr : 0);
>   |  
> ~~~^
> In file included from /usr/include/c++/10/string:41,
>  from /usr/include/c++/10/stdexcept:39,
>  from /usr/include/c++/10/system_error:41,
>  from /usr/include/c++/10/bits/std_mutex.h:39,
>  from /usr/include/c++/10/condition_variable:40,
>  from 
> /<>/src/core/receiver/concurrent_queue.h:35,
>  from 
> /<>/src/algorithms/signal_source/adapters/osmosdr_signal_source.h:36,
>  from 
> /<>/src/algorithms/signal_source/adapters/osmosdr_signal_source.cc:32:
> /usr/include/c++/10/bits/allocator.h:171:7: note: candidate: ‘constexpr _Tp* 
> std::allocator<  >::allocate(std::size_t) [with _Tp = 
> char; std::size_t = long unsigned int]’
>   171 |   allocate(size_t __n)
>   |   ^~~~
> /usr/include/c++/10/bits/allocator.h:171:7: note:   candidate expects 1 
> argument, 2 provided
> make[3]: *** 
> [src/algorithms/signal_source/adapters/CMakeFiles/signal_source_adapters.dir/build.make:170:
>  
> src/algorithms/signal_source/adapters/CMakeFiles/signal_source_adapters.dir/osmosdr_signal_source.cc.o]
>  Error 1
> make[3]: *** Waiting for unfinished jobs
> [ 95%] Building CXX object 
> src/algorithms/acquisition/adapters/CMakeFiles/acquisition_adapters.dir/beidou_b3i_pcps_acquisition.cc.o
> cd /<>/obj-x86_64-linux-gnu/src/algorithms/acquisition/adapters 
> && /usr/bin/c++  -DGNSSSDR_INSTALL_DIR=\"/usr\" -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_LARGE_FILES -I/<>/src/core/interfaces 
> -I/<>/src/algorithms/libs/gsl/include 
> -I/<>/src/algorithms/libs 
> -I/<>/src/algorithms/acquisition/gnuradio_blocks 
> -I/<>/src/algorithms/libs/opencl 
> -I/<>/src/algorithms/acquisition/libs 
> -I/<>/src/core/receiver 
> -I/<>/src/algorithms/channel/libs 
> -I/<>/src/core/system_parameters -isystem /usr/include/glog 
> -isystem 
> /<>/obj-x86_64-linux-gnu/volk_gnsssdr_module/build/include 
> -isystem 
> /<>/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/include 
>  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -fvisibility=hidden -fvisibility-inlines-hidden   -Wall -Wextra -std=c++2a -o 
> CMakeFiles/acquisition_adapters.dir/beidou_b3i_pcps_acquisition.cc.o -c 
> /<>/src/algorithms/acquisition/adapters/beidou_b3i_pcps_acquisition.cc
> [ 95%] Building CXX object 
> src/algorithms/acquisition/adapters/CMakeFiles/acquisition_a

Processed: Re: [Aptitude-devel] Bug#966488: aptitude corrupts package install selection after dpkg error

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #966488 [aptitude] aptitude corrupts package install selection after dpkg 
error
Severity set to 'important' from 'grave'

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

Bug#945467: marked as done (fix build for python 3.8)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 09:55:03 +
with message-id 
and subject line Bug#945467: fixed in veusz 3.2.1-1
has caused the Debian Bug report #945467,
regarding fix build for python 3.8
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.)


-- 
945467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:veusz
Version: 3.0.1-1
Severity: serious
Tags: sid bullseye ftbfs patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

+  * Fix installation of Python 3.8 extensions.
+  * Use unsigned long for widget ids, to fix OverflowError.

patch at
https://patches.ubuntu.com/v/veusz/veusz_3.0.1-1ubuntu3.patch
--- End Message ---
--- Begin Message ---
Source: veusz
Source-Version: 3.2.1-1
Done: Jeremy Sanders 

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

Debian distribution maintenance software
pp.
Jeremy Sanders  (supplier of updated veusz 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: Sun, 17 May 2020 11:12:00 +0200
Source: veusz
Architecture: source
Version: 3.2.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 

Changed-By: Jeremy Sanders 
Closes: 945467
Changes:
 veusz (3.2.1-1) unstable; urgency=low
 .
   [ Jeremy Sanders ]
   * Update to Veusz 3.2.1 (Closes: #945467)
   * Standards-Version: 4.5.0
   * Copy icon files rather than symlink, to fix icon-not-found appsteam
 generator error
   * Fix glob for .so files in python3-veusz.helpers
   * Fix linitan warnings for rules-requires-root,
 uses-debhelper-compat-file, sphinxdoc-but-no-sphinxdoc-depends,
 duplicate-short-description
Checksums-Sha1:
 2a75fdded47f72e402a3981adb19dea06f9fd83d 2638 veusz_3.2.1-1.dsc
 b01cae68c36e03601d4edeb7014e5d452c20db9b 2529051 veusz_3.2.1.orig.tar.gz
 f7eff2db373458e3ab9e56255a13f2afde1ad49d 195 veusz_3.2.1.orig.tar.gz.asc
 08a1a0987d21e1c5f67edff1ebfaf3515baa19ce 10436 veusz_3.2.1-1.debian.tar.xz
 d94e7a93c75c5e97cbebd4d03a936e02111a1af9 14068 veusz_3.2.1-1_amd64.buildinfo
Checksums-Sha256:
 4a650da8e39a989e0383bd8a9a8dd7dd7d954e3ff8728ff02c43eb772ea6de06 2638 
veusz_3.2.1-1.dsc
 9eaf95a2a8cae2d317e7ee47e73f5cf58d191b16c051ae0a1dc399e6f7757503 2529051 
veusz_3.2.1.orig.tar.gz
 f1f16e7006007312794c56c890f0846ba7a108187cbf6bcfe910bd15b3b98f62 195 
veusz_3.2.1.orig.tar.gz.asc
 5804d626974f03fe70b03f95cea5f198bf192600b65d9f464c45f2bbc260de1a 10436 
veusz_3.2.1-1.debian.tar.xz
 2608ab3502a6169d9ff1775fba5cbdde244d9a99008796514ecb5fe3fae3ed67 14068 
veusz_3.2.1-1_amd64.buildinfo
Files:
 603eaa425e97ecdffd9c153c639fb87b 2638 science optional veusz_3.2.1-1.dsc
 f341ea793208818088926612bde53d09 2529051 science optional 
veusz_3.2.1.orig.tar.gz
 894d5f48d70630c41e56334eb2c39e81 195 science optional 
veusz_3.2.1.orig.tar.gz.asc
 ba9377c36279be6d3e26b19419f3615a 10436 science optional 
veusz_3.2.1-1.debian.tar.xz
 0aeace5b6ff4dc3cc825f70f58027af4 14068 science optional 
veusz_3.2.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl8hQT4RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHoCw//SoGf65lr8WobwbGZmm8qUCUxUXdBMuSP
omKj+7vGbWbWWOTiVPD3T6RFSPNCUq9DD07Y4lwi+L3m3XmjDKkhP1mpUVogRS3B
ORPQvjD6uOhBECzVWMsGfR1+pFUpfxYaEtlso6uztMQeZ+B1X7u4IEIB/wN/652N
iCxU8LlInUDIUouUlBhxXQV3zZfM4hq/yOLV0yI5c4cNG8Rx02Pj6O8qzlWRA0Xj
lInLLnJaUGbz1PtlcJd/mOEwTDuzhmmeDrVA2dD5DifHZ8B6WowTywoGeSZBnnhH
OXBTcUd7RtLT3WydrbKbH6KF5OI49f4Ac8GhUUrCiC6pGyGvQ+1IhAJOqT1e6nfA
LrXs5WD3t60eocjELFn551hHtPfY2if1UnYY2MWtwsHOS9+ds7x1M9JJxkGLnNAR
wVM2XDEAagR8wbp4eNKolbLBDAbi2SVAW7EwMGmS/cdTES/GDud8eeUsDSlD0Us3
ErZd1xl4/hZAe6O0U5u+f3jrtT28QY6/vUJzWTY06hd/Z8wp5MZtWxC9ogp0fFdg
4geIxwlpmNGWKhTvlfI3/dGsflwRixAPgO11C44CVXCnycvjrK+LxybcUzN/ENTq
Sz9tgaVL+eLQKuA8Oz5kdQAoZUnWsBb44JmP/6sv06EEk6C9SQWY1K+/4ypXjj1X
STFFAQBvYr8=
=nZi4
-END PGP SIGNATURE End Message ---

Bug#966488: [Aptitude-devel] Bug#966488: aptitude corrupts package install selection after dpkg error

[Axel Beckert]

Control: severity -1 important

Dear Vincent,

Vincent Lefevre wrote:
> Severity: grave
> Justification: causes non-serious data loss

while I agree that this is "data loss" and that it's anything but
"serious" (and serious is less than grave btw. ;-), I disagree that
this validates the "grave" severity. IMHO it's at most "minor
data-loss". Hence downgrading the severity to important. (My gut
feeling would even say this is "normal" at most.)

Besides that, aptitude for quite a long time, like decades, has the
issue that it saves not all details of actions, e.g. it does only save
that you want to upgrade, but not to which version. Not sure what
happens if that version has a lower preference, it might even ignore
it as it can't find a version to upgrade to with higher preference.

Also not sure if there's even a bug report for that.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#957772: marked as done (saint: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 09:54:56 +
with message-id 
and subject line Bug#957772: fixed in saint 2.5.0+dfsg-4
has caused the Debian Bug report #957772,
regarding saint: 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.)


-- 
957772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:saint
Version: 2.5.0+dfsg-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/saint_2.5.0+dfsg-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

[...]
/usr/bin/ld: 
/<>/build/initdata.o:././src/SAINTspc-noctrl/saint.h:246: multiple 
definition of `iter'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:246: first 
defined here
/usr/bin/ld: 
/<>/build/initdata.o:././src/SAINTspc-noctrl/saint.h:245: multiple 
definition of `burn'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:245: first 
defined here
/usr/bin/ld: 
/<>/build/likelihood.o:././src/SAINTspc-noctrl/saint.h:250: 
multiple definition of `NORMALIZE'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:250: first 
defined here
/usr/bin/ld: 
/<>/build/likelihood.o:././src/SAINTspc-noctrl/saint.h:249: 
multiple definition of `modelvar'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:249: first 
defined here
/usr/bin/ld: 
/<>/build/likelihood.o:././src/SAINTspc-noctrl/saint.h:248: 
multiple definition of `freqgroup'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:248: first 
defined here
/usr/bin/ld: 
/<>/build/likelihood.o:././src/SAINTspc-noctrl/saint.h:247: 
multiple definition of `freq'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:247: first 
defined here
/usr/bin/ld: 
/<>/build/likelihood.o:././src/SAINTspc-noctrl/saint.h:246: 
multiple definition of `iter'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:246: first 
defined here
/usr/bin/ld: 
/<>/build/likelihood.o:././src/SAINTspc-noctrl/saint.h:245: 
multiple definition of `burn'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:245: first 
defined here
/usr/bin/ld: /<>/build/mcmc.o:././src/SAINTspc-noctrl/saint.h:250: 
multiple definition of `NORMALIZE'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:250: first 
defined here
/usr/bin/ld: /<>/build/mcmc.o:././src/SAINTspc-noctrl/saint.h:249: 
multiple definition of `modelvar'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:249: first 
defined here
/usr/bin/ld: /<>/build/mcmc.o:././src/SAINTspc-noctrl/saint.h:248: 
multiple definition of `freqgroup'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:248: first 
defined here
/usr/bin/ld: /<>/build/mcmc.o:././src/SAINTspc-noctrl/saint.h:247: 
multiple definition of `freq'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:247: first 
defined here
/usr/bin/ld: /<>/build/mcmc.o:././src/SAINTspc-noctrl/saint.h:246: 
multiple definition of `iter'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:246: first 
defined here
/usr/bin/ld: /<>/build/mcmc.o:././src/SAINTspc-noctrl/saint.h:245: 
multiple definition of `burn'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:245: first 
defined here
/usr/bin/ld: 
/<>/build/meancounts.o:././src/SAINTspc-noctrl/saint.h:250: 
multiple definition of `NORMALIZE'; 
/<>/build/dpalphaIP.o:././src/SAINTspc-noctrl/saint.h:250: first 
defined here
/usr/bin/ld: 
/<>/build/meancounts.o:././src/SAINTspc-noctrl/saint.h:249: 
multiple definition of `modelvar'; 
/<>/build/dpalphaIP.o:././s

Bug#966488: aptitude corrupts package install selection after dpkg error

[Vincent Lefevre]

On 2020-07-29 11:06:16 +0200, Vincent Lefevre wrote:
> An upgrade with aptitude failed due to a dpkg lock error (bug 95).
> Then I noticed that not all packages were upgraded, so that I started
> aptitude again to complete the upgrade. I typed 'g', but got:
> 
> [1(1)/...] Actions: no changes
> e: Examine  !: Apply  .: Next  ,: Previous
> 
> and 'e' gives:
> 
>   --\ Leave the following recommendations unresolved: 
>   
> lcov recommends libgd-gd2-perl
> 
> Since lcov recommends libgd-gd2-perl, this means that it was in
> the package install selection before the initial upgrade (note
> that I didn't have such a warning in the initial upgrade). But
> now libgd-gd2-perl is no longer proposed for installation!

Actually I don't even understand this message as libgd-perl is
already installed and provides libgd-gd2-perl:

cventin:~> dpkg -s libgd-perl
Package: libgd-perl
Status: purge ok installed
Priority: optional
Section: perl
Installed-Size: 392
Maintainer: Debian Perl Group 
Architecture: amd64
Source: libgd-perl (2.71-2)
Version: 2.71-2+b1
Replaces: libgd-gd2-noxpm-perl (<= 1:2.46-2.1), libgd-gd2-perl (<= 1:2.46-3.1)
Provides: libgd-gd2-noxpm-perl, libgd-gd2-perl
[...]

But in the aptitude log (see below), I see that aptitude wanted to
remove libgd-perl (this package is still installed as the upgrade
did not complete due to the dpkg error).

Now, the real issue may be that in its initial dependency resolution,
aptitude missed the Recommends satisfied by the "Provides:", and chose
to remove libgd-perl, breaking the "Recommends:" by doing that.

Aptitude 0.8.13: log report
Wed, Jul 29 2020 10:44:18 +0200

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 340 packages, and remove 10 packages.
583 MB of disk space will be freed

[REMOVE, NOT USED] g++-9:amd64 9.3.0-15
[REMOVE, NOT USED] gfortran-9:amd64 9.3.0-15
[REMOVE, NOT USED] libflint-2.6.0:amd64 2.6.0-3
[REMOVE, NOT USED] libgc1c2:amd64 1:7.6.4-0.4
[REMOVE, NOT USED] libgd-perl:amd64 2.71-2+b1
[REMOVE, NOT USED] libgfortran-9-dev:amd64 9.3.0-15
[REMOVE, NOT USED] libre2-7:amd64 20200601+dfsg-1
[REMOVE, NOT USED] libssl1.0.2:amd64 1.0.2s-1~deb9u1
[REMOVE, NOT USED] libx264-159:amd64 2:0.159.2999+git296494a-2
[REMOVE, NOT USED] libx264-159:i386 2:0.159.2999+git296494a-2
[HOLD, DEPENDENCIES] linux-compiler-gcc-9-x86:amd64 5.7.6-1
[HOLD, DEPENDENCIES] linux-doc-5.7:amd64 5.7.6-1
[HOLD, DEPENDENCIES] linux-kbuild-5.7:amd64 5.7.6-1
[HOLD, DEPENDENCIES] linux-libc-dev:amd64 5.7.6-1
[INSTALL, DEPENDENCIES] fonts-unifont:amd64 1:13.0.03-1
[INSTALL, DEPENDENCIES] g++-10:amd64 10.2.0-3
[INSTALL, DEPENDENCIES] gfortran-10:amd64 10.2.0-3
[INSTALL, DEPENDENCIES] libaliased-perl:amd64 0.34-1
[INSTALL, DEPENDENCIES] libcompress-raw-bzip2-perl:amd64 2.095-1
[INSTALL, DEPENDENCIES] libcompress-raw-lzma-perl:amd64 2.095-1
[INSTALL, DEPENDENCIES] libcompress-raw-zlib-perl:amd64 2.095-1
[INSTALL, DEPENDENCIES] libdata-dpath-perl:amd64 0.58-1
[INSTALL, DEPENDENCIES] libflint-2.6.1:amd64 2.6.1-1
[INSTALL, DEPENDENCIES] libgc1:amd64 1:8.0.4-1
[INSTALL, DEPENDENCIES] libgfortran-10-dev:amd64 10.2.0-3
[INSTALL, DEPENDENCIES] libio-compress-lzma-perl:amd64 2.095-1
[INSTALL, DEPENDENCIES] libio-compress-perl:amd64 2.095-1
[INSTALL, DEPENDENCIES] libiterator-perl:amd64 0.03+ds1-1
[INSTALL, DEPENDENCIES] libiterator-util-perl:amd64 0.02+ds1-1
[INSTALL, DEPENDENCIES] libre2-8:amd64 20200706+dfsg-2
[INSTALL, DEPENDENCIES] libstdc++-10-dev:amd64 10.2.0-3
[INSTALL, DEPENDENCIES] libtirpc-common:amd64 1.2.6-1
[INSTALL, DEPENDENCIES] libtirpc3:amd64 1.2.6-1
[INSTALL, DEPENDENCIES] libx264-160:amd64 2:0.160.3011+gitcde9a93-2
[INSTALL, DEPENDENCIES] libx264-160:i386 2:0.160.3011+gitcde9a93-2
[HOLD] firefox-esr:amd64 52.9.0esr-1~deb9u1
[HOLD] linux-doc:amd64 5.7.6-1
[HOLD] linux-headers-amd64:amd64 5.7.6-1
[HOLD] linux-image-amd64:amd64 5.7.6-1
[HOLD] linux-libc-dev:i386 5.7.6-1
[HOLD] unison:amd64 2.48.4-1+b1
[HOLD] xterm:amd64 351-1+local1
[UPGRADE] asymptote:amd64 2.66-1 -> 2.66-1+b1
[UPGRADE] binutils:amd64 2.34.90.20200706-1 -> 2.35-1
[UPGRADE] binutils-common:amd64 2.34.90.20200706-1 -> 2.35-1
[UPGRADE] binutils-doc:amd64 2.34.90.20200706-1 -> 2.35-1
[UPGRADE] binutils-i686-linux-gnu:amd64 2.34.90.20200706-1 -> 2.35-1
[UPGRADE] binutils-x86-64-linux-gnu:amd64 2.34.90.20200706-1 -> 2.35-1
[UPGRADE] bison:amd64 2:3.6.3+dfsg-1 -> 2:3.7+dfsg-1
[UPGRADE] bsdextrautils:amd64 2.35.2-7 -> 2.36-1
[UPGRADE] bsdutils:amd64 1:2.35.2-7 -> 1:2.36-1
[UPGRADE] bzip2:amd64 1.0.8-3 -> 1.0.8-4
[UPGRADE] bzip2-doc:amd64 1.0.8-3 -> 1.0.8-4
[UPGRADE] calendar:amd64 12.1.5 -> 12.1.6
[UPGRADE] coreutils:amd64 8.32-2 -> 8.32-3
[UPGRADE] cpp:amd64 4:9.2.1-3.1 -> 4:10.1.0-1
[UPGRADE] cpp-10:amd64 10.1.0-6 -> 10.2.0-3
[UPGRADE] cpp-9:amd64 9.3.0-15 -> 9.3.0-16
[UPGRADE] dictionaries-common:amd64 1.28.1 -> 1.28.2
[UPGRADE] dkms:amd64 2.8.2-2 -> 2.8.3-1
[UPGRADE] dms

Bug#966488: aptitude corrupts package install selection after dpkg error

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-1+b1
Severity: grave
Justification: causes non-serious data loss

An upgrade with aptitude failed due to a dpkg lock error (bug 95).
Then I noticed that not all packages were upgraded, so that I started
aptitude again to complete the upgrade. I typed 'g', but got:

[1(1)/...] Actions: no changes
e: Examine  !: Apply  .: Next  ,: Previous

and 'e' gives:

  --\ Leave the following recommendations unresolved:   
lcov recommends libgd-gd2-perl

Since lcov recommends libgd-gd2-perl, this means that it was in
the package install selection before the initial upgrade (note
that I didn't have such a warning in the initial upgrade). But
now libgd-gd2-perl is no longer proposed for installation!

-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.13
Compiler: g++ 9.3.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.2
  libsigc++ version: 2.10.2
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.2.20200212
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffd39bec000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f0d243ae000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f0d24373000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f0d24344000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f0d2433b000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f0d24235000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f0d24109000)
libboost_iostreams.so.1.71.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.71.0 (0x7f0d240e)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f0d23ec6000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f0d23ea4000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f0d23cd7000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f0d23b93000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f0d23b79000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f0d239b2000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f0d23998000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f0d2397b000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f0d23968000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f0d2393f000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f0d2391d000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f0d2383e000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f0d23812000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f0d23764000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f0d23646000)
/lib64/ld-linux-x86-64.so.2 (0x7f0d24a06000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f0d2364)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f0d23633000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7f0d2362a000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f0d23604000)

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

Kernel: Linux 5.7.0-1-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-1
ii  libapt-pkg6.0 2.1.7
ii  libboost-iostreams1.71.0  1.71.0-6+b2
ii  libc6 2.31-2
ii  libcwidget4   0.5.18-5
ii  libgcc-s1 10.2.0-3
ii  libncursesw6  6.2-1
ii  libsigc++-2.0-0v5 2.10.2-1
ii  libsqlite3-0  3.32.3-1
ii  libstdc++610.2.0-3
ii  libtinfo6 6.2-1
ii  libxapian30   1.4.15-1

Versions of packages aptitude recommends:
ii  libdpkg-perl1.20.5
ii  sensible-utils  0.0.12+nmu1

Versions of packages aptitude suggests:
pn  apt-xapian-index
ii  aptitude-doc-en [aptitude-doc]  0.8.13-1
pn  debtags 
ii  tasksel 3.59

-- no debconf information

-- 
Vincent Lefèvre  - Web: 

Processed: reassign 964810 to libllvm7,libllvm9,libllvm10, forcibly merging 852746 964810, affects 852746

[Debian Bug Tracking System]

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

> reassign 964810 libllvm7,libllvm9,libllvm10
Bug #964810 [libllvm10,libllvm9,libllvm7] gimp: Failure to start - GTK problem
Bug reassigned from package 'libllvm10,libllvm9,libllvm7' to 
'libllvm7,libllvm9,libllvm10'.
Ignoring request to alter found versions of bug #964810 to the same values 
previously set
Ignoring request to alter fixed versions of bug #964810 to the same values 
previously set
> forcemerge 852746 964810
Bug #852746 [libllvm7,libllvm9,libllvm10] crash if multiple ICDs dynamically 
linked to LLVM: LLVM ERROR: inconsistency in registered CommandLine options
Bug #964810 [libllvm7,libllvm9,libllvm10] gimp: Failure to start - GTK problem
Set Bug forwarded-to-address to 'https://bugs.llvm.org/show_bug.cgi?id=30587'.
Severity set to 'important' from 'grave'
Added indication that 964810 affects 
mesa-opencl-icd,libreoffice,darktable,libreoffice-calc,src:pocl,beignet-opencl-icd
Added tag(s) upstream.
Merged 852746 964810
> affects 852746 + gimp
Bug #852746 [libllvm7,libllvm9,libllvm10] crash if multiple ICDs dynamically 
linked to LLVM: LLVM ERROR: inconsistency in registered CommandLine options
Bug #964810 [libllvm7,libllvm9,libllvm10] gimp: Failure to start - GTK problem
Added indication that 852746 affects gimp
Added indication that 964810 affects gimp
> thanks
Stopping processing here.

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

Bug#966483: iptables-netflow: sourcing of external scripts in dkms file?

[Gianfranco Costamagna]

Source: iptables-netflow
Version: 2.5-2
Severity: serious
tags: patch

Hello, looks like your dkms ship file is sourcing external stuff with 
pushd/popd and so on.
I don't think this is a sane idea, specially because in Debian we don't even 
use version.sh script to fill the dkms.conf file.

Can you please remove the two lines?

this is what we do to test dkms packages:
if ! dkms_conf=$(dpkg -L $pkg | grep '/usr/src' | grep '/dkms.conf$'); then
 echo "I: Package $pkg has no dkms.conf, skipping"
 return
fi
echo "I: Testing binary package $pkg"

dkms_pkg=$(bash -c ". $dkms_conf; echo \$PACKAGE_NAME" 2>/dev/null)
dkms_ver=$(bash -c ". $dkms_conf; echo \$PACKAGE_VERSION" 2>/dev/null)


bash -c ". dkms.conf; echo \$PACKAGE_NAME"
/tmp/iptables-netflow-2.5 /tmp/iptables-netflow-2.5
/tmp/iptables-netflow-2.5
ipt-netflow


I think dkms.conf files are meant to be sourced from outside, and launching 
scripts is a bad idea.

this is the trivial patch:

Description: Don't print useless stuff and change directory in dkms file, it is 
meant to be sourced from outside.

Author: Gianfranco Costamagna 
Bug-Debian: https://bugs.debian.org/-1
Last-Update: 2020-07-29

--- iptables-netflow-2.5.orig/dkms.conf
+++ iptables-netflow-2.5/dkms.conf
@@ -1,7 +1,5 @@
 PACKAGE_NAME="ipt-netflow"
-pushd `dirname $BASH_SOURCE`
 PACKAGE_VERSION=`./version.sh`
-popd
 BUILT_MODULE_NAME[0]=ipt_NETFLOW
 DEST_MODULE_LOCATION[0]=/kernel/extra
 STRIP[0]=no

Processed: found 966409 in 1:1.5.1-2

[Debian Bug Tracking System]

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

> found 966409 1:1.5.1-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.1-2.
Marked as found in versions libjpeg-turbo/1:1.5.1-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 (with 2 errors): Re: Bug#964810: gimp: Unable to start gimp in debian unstable

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libllvm10,libllvm9,libllvm7
Bug #964810 [gimp] gimp: Failure to start - GTK problem
Bug reassigned from package 'gimp' to 'libllvm10,libllvm9,libllvm7'.
No longer marked as found in versions gimp/2.10.18-1.
Ignoring request to alter fixed versions of bug #964810 to the same values 
previously set
> forcemerge 852746 -1
Bug #852746 [libllvm7,libllvm9,libllvm10] crash if multiple ICDs dynamically 
linked to LLVM
Unable to merge bugs because:
package of #964810 is 'libllvm10,libllvm9,libllvm7' not 
'libllvm7,libllvm9,libllvm10'
Failed to forcibly merge 852746: Did not alter merged bugs.

> affects 852746 + gimp
Failed to mark 852746 as affecting package(s): failed to get lock on 
/srv/bugs.debian.org/spool/lock/852746 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/852746 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/852746 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/852746 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/852746 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/852746 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/852746 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/852746 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/852746 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/852746 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/852746 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.


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

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

[Simon McVittie]

Control: reassign -1 libllvm10,libllvm9,libllvm7
Control: forcemerge 852746 -1
Control: affects 852746 + gimp

On Thu, 16 Jul 2020 at 12:26:26 -0300, zeden wrote:
> $ gimp
> : CommandLine Error: Option 'polly' registered more than once!
> LLVM ERROR: inconsistency in registered CommandLine options

On Wed, 29 Jul 2020 at 00:55:02 -0300, felipe wrote:
> After investigating further, I found the problematic package to be 
> mesa-opencl-icd.
> 
> After removing the package above, gimp works again.

This looks like the same issue as #852746. The workaround appears to be
to avoid installing more than one OpenCL implementation at the same time:

- If you have an AMD GPU, install mesa-opencl-icd
- If you have an NVIDIA GPU and are using the proprietary driver,
  install nvidia-opencl-icd or one of the nvidia-*-opencl-icd packages
- If you have an Intel integrated GPU, install beignet-opencl-icd or
  intel-opencl-icd

On Sat, 11 Jul 2020 at 03:53:22 +1000, Nikolai Lusan wrote:
>   nikolai@poltava:~$ gimp
>   Gtk-Message: 03:50:02.309: Failed to load module "topmenu-gtk-module"
>   Gtk-Message: 03:50:02.310: Failed to load module "topmenu-gtk-module"
>   : CommandLine Error: Option 'polly' registered more than once!
>   LLVM ERROR: inconsistency in registered CommandLine options
> 
> A search on packages.debian.org shows that the gtk topmenu module has
> fallen out of the reposistory. The topmenu-gtk packages are no longer
> available, and the files don't seem to have been rolled into any of the
> other GTK packages.

The first two lines that you quoted (prefixed with Gtk-Message) do not
appear to be related to the crash: you will probably get those when
attempting to run any GTK application.

topmenu-gtk was removed from Debian in early 2018. Its removal was
requested in https://bugs.debian.org/888324 by its maintainer due to
several serious bugs.

To avoid messages about trying to load it, remove topmenu-gtk-module
from your GTK_MODULES environment variable or desktop configuration
(in GNOME this would mean removing it from the dconf key
/org/gnome/settings-daemon/plugins/xsettings/enabled-gtk-modules or adding
it to /org/gnome/settings-daemon/plugins/xsettings/disabled-gtk-modules,
but the procedure might be different for other desktop environments).

smcv

Bug#957230: Bug#966370: bsdmainutils: 12.1.3 removal of lorder breaks rdeps

[Michael Meskes]

On Mon, Jul 27, 2020 at 03:01:31PM +0100, Jessica Clarke wrote:
> Package: bsdmainutils
> Version: 12.1.3
> Severity: serious
> Control: affects -1 src:freebsd-buildutils src:freebsd-glue src:freebsd-libs
> 
> Hi,
> The removal of lorder in 12.1.3 causes various freebsd-* packages to
> FTBFS which are now scheduled for autoremoval from testing. Please
> restore this shell script; it's not deprecated, it's still widely used
> by the BSDs and maintained in at least FreeBSD.

I'm surprised it is actually used as it was pointed out to me that the script
has been non-functional for quite a while. Anyway, it cannot easily be 
"restored"
because the old bsdmainutils package does not exist anymore. All tools except
ncal and calendar, which are now in their own package, are now build out of
util-linux. Would it be possible to include lorder.sh in one of the affected
freebsd packages?

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De
Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org

Processed: Re: Bug#962553: gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:gffread 0.11.8-1
Bug #962553 [src:gff2aplot] gffread: autopkgtest needs update for new version 
of gff2aplot: warning on stderr
Bug reassigned from package 'src:gff2aplot' to 'src:gffread'.
Ignoring request to alter found versions of bug #962553 to the same values 
previously set
Ignoring request to alter fixed versions of bug #962553 to the same values 
previously set
Bug #962553 [src:gffread] gffread: autopkgtest needs update for new version of 
gff2aplot: warning on stderr
Marked as found in versions gffread/0.11.8-1.
> severity -1 serious
Bug #962553 [src:gffread] gffread: autopkgtest needs update for new version of 
gff2aplot: warning on stderr
Severity set to 'serious' from 'important'
> tags -1 - moreinfo unreproducible
Bug #962553 [src:gffread] gffread: autopkgtest needs update for new version of 
gff2aplot: warning on stderr
Removed tag(s) moreinfo and unreproducible.

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

Processed: fixed 965317 in 3.36.4-1

[Debian Bug Tracking System]

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

> fixed 965317 3.36.4-1
Bug #965317 {Done: debian-edid } [gnome-shell] 
gnome-shell: failed to write to XWayland
Marked as fixed in versions gnome-shell/3.36.4-1.
> thanks
Stopping processing here.

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

Bug#963290: e-antic: FTBFS: error: #error FLINT 2.5.2 or 2.5.3 required

[Jerome BENOIT]

Hello Lucas, thanks for the report. I am working on it. Jerome
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature

Bug#966216: marked as done (libxrdesktop-0.15-0: missing Breaks+Replaces: libxrdesktop-0.14-0)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jul 2020 07:49:19 +
with message-id 
and subject line Bug#966216: fixed in xrdesktop 0.15.1-4
has caused the Debian Bug report #966216,
regarding libxrdesktop-0.15-0: missing Breaks+Replaces: libxrdesktop-0.14-0
to be marked as done.

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

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


-- 
966216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxrdesktop-0.15-0
Version: 0.15.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libxrdesktop-0.15-0:amd64.
  Preparing to unpack .../libxrdesktop-0.15-0_0.15.1-2_amd64.deb ...
  Unpacking libxrdesktop-0.15-0:amd64 (0.15.1-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libxrdesktop-0.15-0_0.15.1-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/glib-2.0/schemas/org.xrdesktop.gschema.xml', 
which is also in package libxrdesktop-0.14-0:amd64 0.14.1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libxrdesktop-0.15-0_0.15.1-2_amd64.deb


cheers,

Andreas


libxrdesktop-0.14-0=0.14.1-2_libxrdesktop-0.15-0=0.15.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: xrdesktop
Source-Version: 0.15.1-4
Done: =?utf-8?b?QW5kcmV3IExlZSAo5p2O5YGl56eLKQ==?= 

We believe that the bug you reported is fixed in the latest version of
xrdesktop, 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.
Andrew Lee (李健秋)  (supplier of updated xrdesktop 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: Wed, 29 Jul 2020 15:27:06 +0800
Source: xrdesktop
Architecture: source
Version: 0.15.1-4
Distribution: unstable
Urgency: high
Maintainer: Andrew Lee (李健秋) 
Changed-By: Andrew Lee (李健秋) 
Closes: 966216
Changes:
 xrdesktop (0.15.1-4) unstable; urgency=high
 .
   * Correct the versioned Breaks and Replaces. (Closes: #966216)
Checksums-Sha1:
 5b2369176dce9f7f586be04c22bacb0070bed4a8 2156 xrdesktop_0.15.1-4.dsc
 f63f206c4fc329b9d5c2bce9152f64308c356efc 740050 xrdesktop_0.15.1.orig.tar.bz2
 9a8221416e8bc0525c003962037fba57d24807ea 8256 xrdesktop_0.15.1-4.debian.tar.xz
 c4b95c29347ce7a984340aaedc999c0fc5f6b255 6036 
xrdesktop_0.15.1-4_source.buildinfo
Checksums-Sha256:
 86ee9fd9149f45842616c4800f21c7836069e1f6ab3c3501fed8e57052da9045 2156 
xrdesktop_0.15.1-4.dsc
 be59c5bd0a4b44677f208684ba5c132c2ebde64b416b0f562a2cc1faa13aaab3 740050 
xrdesktop_0.15.1.orig.tar.bz2
 cfefd845dc4e8287efffc4d98592140690bd12a5f99ff5b6e546329ee60e5d43 8256 
xrdesktop_0.15.1-4.debian.tar.xz
 fa71b1b3cda3e5f4e693dff2492eb739fa19be526779accfbb50da66454b7f29 6036 
xrdesktop_0.15.1-4_source.buildinfo
Files:
 7b5d50545ae903b965135baacca343fe 2156 libs optional xrdesktop_0.15.1-4.dsc
 57277f04486049388afd5285c6293aa7 740050 libs optional 
xrdesktop_0.15.1.orig.tar.bz2
 8ee161b1c407a2ca65a0042f09beda17 8256 libs optional 
xrdesktop_0.15.1-4.debian.tar.xz
 6e350712c2584aa3b5ea08d06a5f97d6 6036 libs optional 
xrdesktop_0.15.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE703UlH90QYpfEyJV58vhUqwX+XMFAl8hJPAACgkQ58vhUqwX
+XMgMg/+OFjLNdsDGLOQUL1iMqK/E1CRjRYvaxuBXAXbNCuXb2R5XlIQ8dic4wgJ
jQdfo674anJWpf35yL6volM32cnx22gN8wJh7cbgbO6qA2nl6hPh+4VCtvCd4kSB
wSd3tjW4ew1DOuVFZsxDT2FaJa0LkfQ1NQyeSLqynIcuiB0OAyTop/Pq6bsZBI5m
TxHhEFFNX0Ij75b+/liQxyhKuSBnVvNm7gBAs48xdEiUNrXfE+JxKPzcaHqlmJpn
Xyx2F4mCFFerii031dW8dsKnF/TFDD72eCmzBZ/xNbeLIfcAj/AKd5A8wQPNo561
0JvyEcw2ZBduu+Cqjn/Zkm90Ci4UFFMWC8Zs2EPPyRTGoOswmVKulDaTwsqPFBlX
UuOgMRilIBLF4wfUUN/7z6S9gJ/MTzjL8I1C5X4LM/gq0GUWitfo1YkESB/eGW7o
M+Fos0V9iO0SkcYnmdBvo2i47BNNCkb2aOsjSiaaS+4b5gE1QfrGHmP0DWEmBMwI
Zyt7SaHSApiAbwc5LZw0aDYltHnFhsGgpMlgM9+19EbWGnvW5kbkQXux6

Bug#966479: sysdig: broken support on 32 bit kernels?

[Gianfranco Costamagna]

Source: sysdig
Version: 0.26.7-2
Severity: serious
Forwarded: https://github.com/draios/sysdig/issues/1669

Hello, I don't know if this happens also in Debian, but there is no reason for 
it not happening there.

I asked upstream for help, this is what happens:
  CC [M]  /var/lib/dkms/sysdig/0.26.7/build/ppm_cputime.o
  LD [M]  /var/lib/dkms/sysdig/0.26.7/build/sysdig-probe.o
  Building modules, stage 2.
  MODPOST 1 modules
ERROR: "__aeabi_uldivmod" [/var/lib/dkms/sysdig/0.26.7/build/sysdig-probe.ko] 
undefined!
make[1]: *** [scripts/Makefile.modpost:94: __modpost] Error 1

thanks for having a look

Gianfranco