Bug#968030: marked as done (e17: FTBFS during combined arch+indep build)

[Debian Bug Tracking System]

Your message dated Fri, 07 Aug 2020 05:33:27 +
with message-id 
and subject line Bug#968030: fixed in e17 0.24.2-4
has caused the Debian Bug report #968030,
regarding e17: FTBFS during combined arch+indep build
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.)


-- 
968030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: e17
Version: 0.24.2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

e17/experimental FTBFS during a combined binary arch+indep build (i.e. the
default dpkg-buildpackage mode), while it succeeds during separate arch and
indep builds (dpkg-buildpackage -B, dpkg-buildpackage -A; as done by the
buildds). I know no other package having such a failure mode ;-)

   debian/rules execute_before_dh_install-indep
make[1]: Entering directory '/build/e17-0.24.2'
rm -f debian/tmp/usr/share/enlightenment/COPYING
gzip -9n debian/tmp/usr/share/enlightenment/doc/*.txt
gzip: debian/tmp/usr/share/enlightenment/doc/*.txt: No such file or directory
make[1]: *** [debian/rules:30: execute_before_dh_install-indep] Error 1
make[1]: Leaving directory '/build/e17-0.24.2'
make: *** [debian/rules:11: binary] Error 2



Andreas


e17_0.24.2-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: e17
Source-Version: 0.24.2-4
Done: Ross Vandegrift 

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

Debian distribution maintenance software
pp.
Ross Vandegrift  (supplier of updated e17 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Aug 2020 22:20:31 -0700
Source: e17
Architecture: source
Version: 0.24.2-4
Distribution: experimental
Urgency: medium
Maintainer: Debian Pkg-e Team 
Changed-By: Ross Vandegrift 
Closes: 968030
Changes:
 e17 (0.24.2-4) experimental; urgency=medium
 .
   * Recombine arch & indep build steps.  Fixes FTBFS without -A or -B.
 (Closes: #968030)
Checksums-Sha1:
 c360342178e78efcd61de08baeec9c9daa70204a 2460 e17_0.24.2-4.dsc
 849ee44f3af5b685d83db41f48b01729fca6753e 18436 e17_0.24.2-4.debian.tar.xz
Checksums-Sha256:
 ef5c44701ca5e861b41da2770bcfc993ba07936e2736aed211259311479ac89c 2460 
e17_0.24.2-4.dsc
 f5c8dc89868d45c6e36d2497ad9b6e43336f0c409f02efac15d71f81345ea6ef 18436 
e17_0.24.2-4.debian.tar.xz
Files:
 ffe5f96c3ad2c83779ab3d99b5d41bf9 2460 x11 optional e17_0.24.2-4.dsc
 73197ad09ba42b407f9bf6806bf2ade2 18436 x11 optional e17_0.24.2-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsAjXULa3g2HtU1bw2rOJMppM+hYFAl8s5W8ACgkQ2rOJMppM
+haE2hAAtLOUk5JG6HYQ5qqJTs4LftCD6cCPXD10lhEa5e3MpC6uqPKz3xs8o9JE
ansoLz/higZQpUfzqwYbftlpGHXXq9IAKI6QTYSlr2YtS6wbcZaRBhh2dQOVgV7w
OOcInhUDQZaqH+z7jePPGo7CQkJvNp9Rmp4hn863ts21mu3NZa7Apy2sAAz3h6Nk
27FkpkWAARXqDtCLrJ+3cs28S3ovtSN5wEo7OH8ZRsLnz8D/tVxyn5+fX9BTcB7j
w3bA7v4o+5wuzLklh/FGAI9GKGxY0ZmumRM8Fnp/SKcCvy+l9mTtFKA5mzPk0Y9C
z3S0pY3p2tFOYaBa9qiaD2dbUYGqgiugfxaMRGvHxkO19FAlVbe2am/bsdlxgja0
OoQgjUPsZWCpGRBV2thHdBiNMd6NFnU+KQQd4hEjzvgUB6vl4PsLBPSK7UrAgvOB
WMHSakL2PIBMoNBloRfnilxifK1tES0WZzzoMLcrESBHDOWIaj56YU1Km7IhOcWM
RuxDndEkYKu7x30kmIQqmI7wzMJ9ZQ1Bn/1RqmR6/Qy8PopVjW+oH6Q9tsouwP+h
og+JISIGdm5FjpEYulcQuqPbtyJSDQKlx/egt+X+LDbirdQksbGmnXsr9FFE8sIS
vB8m+D/+Ar8zErqbHz4suYGbt7mP9U5OJqdunO5J8UE5FSjIq7k=
=aVH4
-END PGP SIGNATURE End Message ---

Bug#968030: e17: FTBFS during combined arch+indep build

[Ross Vandegrift]

On Fri, Aug 07, 2020 at 01:17:29AM +0200, Andreas Beckmann wrote:
> e17/experimental FTBFS during a combined binary arch+indep build (i.e. the
> default dpkg-buildpackage mode), while it succeeds during separate arch and
> indep builds (dpkg-buildpackage -B, dpkg-buildpackage -A; as done by the
> buildds). I know no other package having such a failure mode ;-)

Hah, I swear I finally had all combinations working- but looks like I just
moved the bump in the rug around.  At least I got a totally unique failure out
for my time! :)

Ross

Bug#957710: marked as done (proxychains: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Fri, 07 Aug 2020 04:49:08 +
with message-id 
and subject line Bug#957710: fixed in proxychains 3.1-9
has caused the Debian Bug report #957710,
regarding proxychains: 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.)


-- 
957710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:proxychains
Version: 3.1-8.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/proxychains_3.1-8.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[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in proxychains
make[3]: Entering directory '/<>/proxychains'
Making all in docs
make[4]: Entering directory '/<>/proxychains/docs'
Making all in en
make[5]: Entering directory '/<>/proxychains/docs/en'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/<>/proxychains/docs/en'
make[5]: Entering directory '/<>/proxychains/docs'
make[5]: Nothing to be done for 'all-am'.
make[5]: Leaving directory '/<>/proxychains/docs'
make[4]: Leaving directory '/<>/proxychains/docs'
make[4]: Entering directory '/<>/proxychains'
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
libproxychains.lo libproxychains.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o core.lo core.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c core.c  -fPIC -DPIC -o .libs/core.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c libproxychains.c  -fPIC -DPIC -o 
.libs/libproxychains.o
core.c: In function ‘proxy_gethostbyname’:
core.c:657:4: warning: ignoring return value of ‘read’ declared with attribute 
‘warn_unused_result’ [-Wunused-result]
  657 |read(pipe_fd[0],,sizeof(buff));
  |^~~
In file included from /usr/include/string.h:495,
 from /usr/include/memory.h:29,
 from core.c:24:
In function ‘strncpy’,
inlined from ‘tunnel_to’ at core.c:314:6:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin___strncpy_chk’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
core.c: In function ‘tunnel_to’:
core.c:312:8: note: length computed here
  312 |  c=strlen(user);
  |^~~~
In file included from /usr/include/string.h:495,
 from /usr/include/memory.h:29,
 from core.c:24:
In function ‘strncpy’,
inlined from ‘tunnel_to’ at core.c:318:6:
/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, 

Processed: owner 957122

[Debian Bug Tracking System]

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

> owner 957122 woodrow.s...@gmail.com
Bug #957122 [src:davfs2] davfs2: ftbfs with GCC-10
Owner recorded as woodrow.s...@gmail.com.
> thanks
Stopping processing here.

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

Bug#957347: marked as done (hydra: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Fri, 07 Aug 2020 03:04:09 +
with message-id 
and subject line Bug#957347: fixed in hydra 9.1-1
has caused the Debian Bug report #957347,
regarding hydra: 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.)


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

[...]
 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 callbacks.c:12:
/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 callbacks.c:12:
/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 callbacks.c:12:
/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.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 callbacks.c:12:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
callbacks.c: In function ‘on_btnSave_clicked’:
callbacks.c:694:7: warning: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  694 |   write(fd, text, strlen(text));
  |   ^
gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o 
xhydra  main.o support.o interface.o callbacks.o -lgtk-x11-2.0 -lgdk-x11-2.0 
-lpangocairo-1.0 

Bug#957355: ifplugd: ftbfs with GCC-10

[Luis Paulo Linares]

Control: tags -1 + patch

Hi,

the attached patch fixes the FTBFS with GCC 10.

Regards,
-- 
Luis Paulo (lpfll)
diff -Nru ifplugd-0.28/debian/patches/09_fix-ftbfs-with-gcc10.patch ifplugd-0.28/debian/patches/09_fix-ftbfs-with-gcc10.patch
--- ifplugd-0.28/debian/patches/09_fix-ftbfs-with-gcc10.patch	1969-12-31 21:00:00.0 -0300
+++ ifplugd-0.28/debian/patches/09_fix-ftbfs-with-gcc10.patch	2020-08-06 19:46:15.0 -0300
@@ -0,0 +1,17 @@
+Description: Fix FTBFS with GCC 10.
+Author: Luis Paulo Linares 
+Bug-Debian: https://bugs.debian.org/957355
+
+--- ifplugd-0.28.orig/src/interface.h
 ifplugd-0.28/src/interface.h
+@@ -24,8 +24,8 @@
+ /* From  */
+ #define ETH_ALEN 6
+ 
+-int interface_auto_up;
+-int interface_do_message;
++extern int interface_auto_up;
++extern int interface_do_message;
+ 
+ typedef enum { IFSTATUS_UP, IFSTATUS_DOWN, IFSTATUS_ERR } interface_status_t;
+ 
diff -Nru ifplugd-0.28/debian/patches/series ifplugd-0.28/debian/patches/series
--- ifplugd-0.28/debian/patches/series	2018-06-23 07:22:26.0 -0300
+++ ifplugd-0.28/debian/patches/series	2020-08-06 19:46:15.0 -0300
@@ -6,3 +6,4 @@
 06_509015_better_delays.patch
 07_add_fractional_delays.patch
 08_allow_ipv4_less.patch
+09_fix-ftbfs-with-gcc10.patch

Processed: Re: ifplugd: ftbfs with GCC-10

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #957355 [src:ifplugd] ifplugd: ftbfs with GCC-10
Added tag(s) patch.

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

Bug#963871: marked as done (emacs-websocket: FTBFS without external DNS)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 23:18:30 +
with message-id 
and subject line Bug#963871: fixed in emacs-websocket 1.12+18.g5aaf9d1-1
has caused the Debian Bug report #963871,
regarding emacs-websocket: FTBFS without external DNS
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.)


-- 
963871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs-websocket
Version:  1.12+8.g31e122a-1
Severity: serious
Tags: ftbfs

This package fails to build when DNS lookups are not available.

  Test websocket-client-with-remote-server condition:
  (error "echo.websocket.org/443 Temporary failure in name resolution")

  [...]

  1 unexpected results:
FAILED  websocket-client-with-remote-server

See 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/emacs-websocket.html
for a full build log.

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: emacs-websocket
Source-Version: 1.12+18.g5aaf9d1-1
Done: Nicholas D Steeves 

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

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

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

Debian distribution maintenance software
pp.
Nicholas D Steeves  (supplier of updated emacs-websocket 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Aug 2020 18:50:35 -0400
Source: emacs-websocket
Architecture: source
Version: 1.12+18.g5aaf9d1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Nicholas D Steeves 
Closes: 963871
Changes:
 emacs-websocket (1.12+18.g5aaf9d1-1) unstable; urgency=medium
 .
   * Import new upstream snapshot.
 - this snapshot includes collaborative work that makes it possible to run
   the functional tests using a localhost Tornado program rather than
   echo.websocket.org using the elisp interface introduced between
   commit:74e4b82 and commit:31e122a (Closes: #963871).
   * Add python3-tornado as a build-dep to run these tests.
   * debian/elpa-test: Activate the use of the local server for functional
 tests.
   * Drop 0001-Drop-unused-wstest-server-proc.patch (it has been fixed and is
 now used).
   * Migrate to debhelper-compat 13.
Checksums-Sha1:
 dd332c23d36c589acee318b496eeb0b1519623f4 2129 
emacs-websocket_1.12+18.g5aaf9d1-1.dsc
 27e76fa385caec34d18881a3aa4a7d7a3c5a6f21 27526 
emacs-websocket_1.12+18.g5aaf9d1.orig.tar.gz
 063ff2b8ca3a1405e5e1fb3c713a40480764a93a 2304 
emacs-websocket_1.12+18.g5aaf9d1-1.debian.tar.xz
 459a45a9138a4e99dd6e7c50e70037494bb50937 8079 
emacs-websocket_1.12+18.g5aaf9d1-1_amd64.buildinfo
Checksums-Sha256:
 adb9667a14c76caae7fad8a82edc836f6a605e6f1f4083e0a65f287e662865e6 2129 
emacs-websocket_1.12+18.g5aaf9d1-1.dsc
 eb7c4aacc2b18c48fd9a507f2577ad4690bfe8d9ee8d26a4efb6bd89c0135792 27526 
emacs-websocket_1.12+18.g5aaf9d1.orig.tar.gz
 c66657004712fc3c1748c7edb787334a6897bcc55fab718913f129bcbe80b622 2304 
emacs-websocket_1.12+18.g5aaf9d1-1.debian.tar.xz
 04cb4aaf9be810a5a5b58afb879dd91e0771b182e36e7e15220029c92c55dc35 8079 
emacs-websocket_1.12+18.g5aaf9d1-1_amd64.buildinfo
Files:
 5b9af3ae0196d43008a9a4193bb7fe4d 2129 lisp optional 
emacs-websocket_1.12+18.g5aaf9d1-1.dsc
 78ed754c97cb155d9fe7839dd816a462 27526 lisp optional 
emacs-websocket_1.12+18.g5aaf9d1.orig.tar.gz
 0b25a146d680ee68ff7d02be058d1302 2304 lisp optional 
emacs-websocket_1.12+18.g5aaf9d1-1.debian.tar.xz
 0f609298c131f611c2fa02dcbee9c119 8079 lisp optional 
emacs-websocket_1.12+18.g5aaf9d1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAl8sizsACgkQWogwR199
EGEhqhAAzQTEqPyZYc+E1tIuaYgNN4gO10Dkkewf+uzo6HLja0e09j/crmJs37Zt
S68tExbkUlA6EyNkTnc+T/SK8ErM20rbj3SofmbY6gmNAZHkIXuLapj82pb4kpnx
S0pn3t3b8vY0MpOqOF7zTQy02jQ/6dYiKHQRouNFhKgAvLJAxV5/ALWbjk858xUc
7M4WE70BU0GYnqwAaUX1EbOHjJ7fMDRvYf2YY5P2BaD6h+MgUj87rmDXaWjtyH6G
cp52nQLqJOCZ9AgHPH3AUhojpsiWchKNOvu8Fp/kzuC0qnUxgXYstktNs9Vpw4PN
Btc01FuwT1XTd2b6meYUJ98o3D+OB07TZaOwebSiIBnU/Dk4mu5cSmAlYTNW5bb9

Bug#968030: e17: FTBFS during combined arch+indep build

[Andreas Beckmann]

Source: e17
Version: 0.24.2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

e17/experimental FTBFS during a combined binary arch+indep build (i.e. the
default dpkg-buildpackage mode), while it succeeds during separate arch and
indep builds (dpkg-buildpackage -B, dpkg-buildpackage -A; as done by the
buildds). I know no other package having such a failure mode ;-)

   debian/rules execute_before_dh_install-indep
make[1]: Entering directory '/build/e17-0.24.2'
rm -f debian/tmp/usr/share/enlightenment/COPYING
gzip -9n debian/tmp/usr/share/enlightenment/doc/*.txt
gzip: debian/tmp/usr/share/enlightenment/doc/*.txt: No such file or directory
make[1]: *** [debian/rules:30: execute_before_dh_install-indep] Error 1
make[1]: Leaving directory '/build/e17-0.24.2'
make: *** [debian/rules:11: binary] Error 2



Andreas


e17_0.24.2-3.log.gz
Description: application/gzip

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

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 23:19:29 +
with message-id 
and subject line Bug#966500: fixed in notcurses 1.6.11+dfsg.1-1
has caused the Debian Bug report #966500,
regarding python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)
to be marked as done.

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

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


-- 
966500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: notcurses
Source-Version: 1.6.11+dfsg.1-1
Done: Nick Black 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 03 Aug 2020 02:56:22 -0400
Source: notcurses
Architecture: source
Version: 1.6.11+dfsg.1-1
Distribution: unstable
Urgency: medium
Maintainer: Nick Black 
Changed-By: Nick Black 
Closes: 966500
Changes:
 notcurses (1.6.11+dfsg.1-1) unstable; urgency=medium
 .
   * Add Breaks+Replaces for notcurses-bin << 1.6 (Closes: #966500)
   * New notcurses-demo phase "zoo" available
   * Add python3-pypandoc dependency
   * Don't install notcurses-pydemo nor notcurses-pydemo.1 as part of
 notcurses-bin; these both belong in python3-notcurses.
Checksums-Sha1:
 c4014b2a1d015926c2140d65c81460e3070921c2 2994 notcurses_1.6.11+dfsg.1-1.dsc
 459eb7c8c845d4e04407edd105177c57f8398d09 5172948 
notcurses_1.6.11+dfsg.1.orig.tar.xz
 76b2d7ae79317580c9786bc30b1c59b835defa25 833 
notcurses_1.6.11+dfsg.1.orig.tar.xz.asc
 47a2e07007b7d563368af9ad51b3a40181a9c758 12084 
notcurses_1.6.11+dfsg.1-1.debian.tar.xz
 f473033d963eece7fd2333af4e1a071f431c97ea 13544 
notcurses_1.6.11+dfsg.1-1_amd64.buildinfo
Checksums-Sha256:
 d86b911912d1bb2373d9bb7961eeb91879cb6a4fe0002f2056e2420d05b4a3e7 2994 
notcurses_1.6.11+dfsg.1-1.dsc
 9c0169afdbb87c2bff15f882aff6316ba179c33cd4144e3aa5d1967de50381f8 5172948 
notcurses_1.6.11+dfsg.1.orig.tar.xz
 da381d2b9553a37421b6ce97e6000c5c9b4aaff3b04dfc2835d82a86d6d5378c 833 
notcurses_1.6.11+dfsg.1.orig.tar.xz.asc
 73c19fb047b60bfd3f45d7a2393c48a8f5e10839c42c45ee445f9de9d35f5a56 12084 
notcurses_1.6.11+dfsg.1-1.debian.tar.xz
 65ba0c992c5753f64ac57b1f3160cf8c1f584bb15c25977c3f104a3b320140b5 13544 
notcurses_1.6.11+dfsg.1-1_amd64.buildinfo
Files:
 e1ee4c1a23e22d91eacc21365e9a87f2 2994 libs optional 
notcurses_1.6.11+dfsg.1-1.dsc
 159e35442dd261aedbf7e81bba13728a 5172948 libs optional 
notcurses_1.6.11+dfsg.1.orig.tar.xz
 ab9a27493eb2300ec8346b89d61873a3 833 libs optional 
notcurses_1.6.11+dfsg.1.orig.tar.xz.asc
 845701818f902193119a4009e51b9f64 12084 libs optional 
notcurses_1.6.11+dfsg.1-1.debian.tar.xz
 8f4a7c87d118815a949d92acc05b9651 13544 libs optional 
notcurses_1.6.11+dfsg.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#954189: Upload approval for acmetool 0.2 in buster-backports

[Ralph Giles]

Hi,

I wanted to request approval from the maintainer team to upload the
acmetool 0.2.1-2 package currently in testing/unstable to buster-
backports.

The version currently in buster (0.0.63) only supports the deprecated
ACME v1 protocol, which no longer works for new registrations, and will
stop working even for renewals in 2021. As such, the package isn't
usable for deploying new sites on buster installs.

The 0.2.1 package from unstable works fine on buster, providing ACME v2
support, and also fixes issues with the systemd unit file provided by
the package.

I think having the newer package available in backports would be a
better situation for users.

Thanks for your time an effort supporting letsencrypt,

Ralph


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

Bug#964541: marked as done (flatpak: Wrong argument order for clone syscall seccomp filter on s390x)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 22:33:39 +
with message-id 
and subject line Bug#964541: fixed in flatpak 1.8.1-2
has caused the Debian Bug report #964541,
regarding flatpak: Wrong argument order for clone syscall seccomp filter on 
s390x
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.)


-- 
964541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: make-dfsg
Version: 4.3-4
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy ubuntu-patch

In Ubuntu, the attached patch was applied to achieve the following:

The autopkgtests for flatpak-builder/s390x where failing with

  echo Building
  make: echo: Operation not permitted
  make: *** [Makefile:2: all] Error 127


git bisect lead to

commit 749a54d7a458dc6779936138caf40ce600a80052 (refs/bisect/bad)
Author: Aron Barath 
Date:   Mon Jul 9 09:05:31 2018 +0200

* job.c (child_execute_job): Prefer posix_spawn() over fork()/exec()

and I can confirm that disabling posix_spawn makes the autopkgtest
work again.

Earlier research also indicated that this is a heisenbug, if I try
to print to stderr before printing to stdout, no issue occurs.


  * Pass --disable-posix-spawn to configure, as use of posix_spawn()
causes a regression on s390x, with commands getting EPERM when
writing to stdout.


Thanks for considering the patch.

*** /tmp/tmp79xr4v61/make-dfsg_4.3-4ubuntu1.debdiff
diff -u make-dfsg-4.3/debian/rules make-dfsg-4.3/debian/rules
--- make-dfsg-4.3/debian/rules
+++ make-dfsg-4.3/debian/rules
@@ -28,13 +28,13 @@
mkdir -p $(BUILDDIR_GUILE)
ac_cv_lib_util_getloadavg=no dh_auto_configure --parallel \
-B$(BUILDDIR_GUILE) -- --prefix=$(PREFIX) $(confflags) \
-  --with-guile
+  --with-guile --disable-posix-spawn
 endif
 ifneq (,$(filter make, $(shell dh_listpackages)))
mkdir -p $(BUILDDIR_NORMAL)
ac_cv_lib_util_getloadavg=no dh_auto_configure --parallel  \
-B$(BUILDDIR_NORMAL) -- --prefix=$(PREFIX) $(confflags) \
-  --with-guile=no
+  --with-guile=no --disable-posix-spawn
 endif
 
 override_dh_auto_build:


-- System Information:
Debian Release: bullseye/sid
  APT prefers groovy
  APT policy: (991, 'groovy'), (500, 'groovy'), (500, 'focal-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1018-oem (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
--- End Message ---
--- Begin Message ---
Source: flatpak
Source-Version: 1.8.1-2
Done: Simon McVittie 

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated flatpak package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 06 Aug 2020 22:45:21 +0100
Source: flatpak
Architecture: source
Version: 1.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Closes: 964541
Changes:
 flatpak (1.8.1-2) unstable; urgency=medium
 .
   * Include flatpak-bisect and flatpak-coredumpctl in libflatpak-dev
 - Depends: python3, to be able to run the scripts themselves
 - Recommends: flatpak, for both scripts
 - Suggests: gdb and systemd-coredump, for flatpak-coredumpctl
 - Suggests: python3-gi and ostree, for flatpak-bisect
   * d/p/Fix-argument-order-of-clone-for-s390x-in-seccomp-filter.patch:
 Add proposed patch to fix seccomp filtering on s390x.
 Thanks to Julian Andres Klode. (Closes: #964541, LP: #1886814)
Checksums-Sha1:
 

Processed: Bug#964541 marked as pending in flatpak

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964541 [flatpak] flatpak: Wrong argument order for clone syscall seccomp 
filter on s390x
Added tag(s) pending.

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

Bug#964541: marked as pending in flatpak

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #964541 in flatpak 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/debian/flatpak/-/commit/e8239c622541273adf3a3b7f24e8f232206566ef


Add proposed patch to fix seccomp filtering on s390x

Thanks: Julian Andres Klode
Closes: #964541, LP: #1886814


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964541

Bug#957841: squidguard: diff for NMU version 1.6.0-1.1

[Sudip Mukherjee]

Control: tags 957841 + patch
Control: tags 957841 + pending

Dear maintainer,

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

--
Regards
Sudip

diff -Nru squidguard-1.6.0/debian/changelog squidguard-1.6.0/debian/changelog
--- squidguard-1.6.0/debian/changelog   2019-02-02 17:13:22.0 +
+++ squidguard-1.6.0/debian/changelog   2020-08-06 22:42:00.0 +0100
@@ -1,3 +1,10 @@
+squidguard (1.6.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957841)
+
+ -- Sudip Mukherjee   Thu, 06 Aug 2020 22:42:00 
+0100
+
 squidguard (1.6.0-1) unstable; urgency=medium
 
   * New upstream release with many fixes and updates (see CHANGELOG).
diff -Nru squidguard-1.6.0/debian/patches/fix_ftbfs.patch 
squidguard-1.6.0/debian/patches/fix_ftbfs.patch
--- squidguard-1.6.0/debian/patches/fix_ftbfs.patch 1970-01-01 
01:00:00.0 +0100
+++ squidguard-1.6.0/debian/patches/fix_ftbfs.patch 2020-08-06 
22:41:24.0 +0100
@@ -0,0 +1,50 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957841
+Forwarded: no
+
+---
+
+--- squidguard-1.6.0.orig/src/main.c.in
 squidguard-1.6.0/src/main.c.in
+@@ -71,6 +71,8 @@ int sgtime = 0;
+ char *globalLogDir = NULL;
+ int globalSyslog = 0;
+ 
++char *progname;
++int lineno;
+ 
+ #if __STDC__
+ int main(intargc,
+--- squidguard-1.6.0.orig/src/sg.h.in
 squidguard-1.6.0/src/sg.h.in
+@@ -115,7 +115,7 @@ int tolower();
+ #define REDIRECT_PERMANENT   "301:"
+ #define REDIRECT_TEMPORARILY "302:"
+ 
+-char *progname;
++extern char *progname;
+ 
+ struct LogFileStat {
+   char *name;
+@@ -337,7 +337,7 @@ struct AclDest {
+   struct AclDest *next;
+ };
+ 
+-int lineno;
++extern int lineno;
+ 
+ char   *sgParseRedirect   __P((char *, struct SquidInfo *, struct Acl *, 
struct AclDest *));
+ char   *sgAclAccess __P((struct Source *, struct Acl *, struct SquidInfo *));
+--- squidguard-1.6.0.orig/src/sg.y.in
 squidguard-1.6.0/src/sg.y.in
+@@ -35,7 +35,7 @@ extern int globalSyslog;
+ 
+ #include "sgEx.h"
+ 
+-FILE *yyin, *yyout;
++extern FILE *yyin, *yyout;
+ char *configFile;
+ 
+ int numTimeElements;
diff -Nru squidguard-1.6.0/debian/patches/series 
squidguard-1.6.0/debian/patches/series
--- squidguard-1.6.0/debian/patches/series  2019-02-02 17:13:22.0 
+
+++ squidguard-1.6.0/debian/patches/series  2020-08-06 22:39:49.0 
+0100
@@ -1 +1 @@
-
+fix_ftbfs.patch

Processed: squidguard: diff for NMU version 1.6.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957841 + patch
Bug #957841 [src:squidguard] squidguard: ftbfs with GCC-10
Added tag(s) patch.
> tags 957841 + pending
Bug #957841 [src:squidguard] squidguard: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#885265: marked as done (chirp: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 21:18:33 +
with message-id 
and subject line Bug#885265: fixed in chirp 1:20200227+py3+20200213-1
has caused the Debian Bug report #885265,
regarding chirp: Depends on unmaintained pygtk
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.)


-- 
885265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chirp
Version: 1:20170714-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: chirp
Source-Version: 1:20200227+py3+20200213-1
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated chirp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 06 Aug 2020 22:59:46 +0200
Source: chirp
Architecture: source
Version: 1:20200227+py3+20200213-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 885265 936299
Changes:
 chirp (1:20200227+py3+20200213-1) unstable; urgency=medium
 .
   * Switch to upstream py3 branch based on python3-wxgtk4.0.
 (Closes: #885265, #936299)
   * Lots of python3 porting missing, tested so far: Baofeng UV-5R.
Checksums-Sha1:
 89e008df68c1376761b8a2549a21bc35efd8b7b4 2193 chirp_20200227+py3+20200213-1.dsc
 aeba1b24682bc62765386988fca317a7a7a0a5ee 1198525 
chirp_20200227+py3+20200213.orig.tar.gz
 e81437a37e483eb7970153020f025c34eac18140 11760 
chirp_20200227+py3+20200213-1.debian.tar.xz
Checksums-Sha256:
 18e70711e5489de4ca75aa580a6e95eab811ce10886cd44ee45ede66ba2395d5 2193 
chirp_20200227+py3+20200213-1.dsc
 898bc3359716dad537ef2f74c3e08c07ddf83c4ce325a33dfc1b45abcd991628 1198525 
chirp_20200227+py3+20200213.orig.tar.gz
 be493d1babc0ea6bf72399fedaf331b8692ffa88573686009235b953eefcf6b7 11760 
chirp_20200227+py3+20200213-1.debian.tar.xz
Files:
 a4adfb0ec790927a42e1520c126bbb66 2193 hamradio optional 
chirp_20200227+py3+20200213-1.dsc
 d3b68c04be9b401d629352f77a6835be 1198525 hamradio optional 
chirp_20200227+py3+20200213.orig.tar.gz
 ea204a4426b0d1a5b3dff8aec0286073 11760 hamradio optional 
chirp_20200227+py3+20200213-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl8scRMACgkQTFprqxLS
p64Wvg//a1RMcgo6hV/u+CxYzMu0W/KX7WTogvgWzRdiVyPto+zoFpTY34UOQEfj
+161D8+qwljnu2rGXkWtNk09uC+BP/gXTwm/gauBvLt0Nayc1dLcT/My8eqrpVM2
rVl2m+Sdp4sW91XSKkfToW4/1MlBshAp6earrviI3fUH7bhotIP2KTqA7jJN3McD
84P/E9QUwaHsHKY4sDTCdwHtUa2aZAzEZ2dD3P7zA9QLrBBrjgFzKEraMO5FS5LV
vOakC9rYI5MuxcRXtrRGVqhcWnmrP1bjPn1yM+NFmYL2A/NLFRkjW/4Hn9wuGfgY
g1+T2qHBkjQAbjiJ5QePsNkM847okR8Ida3/zK/SsvYauj/VSAS7PDNyVjliEue3
KSOGDz5N7Bz4zKsOxUuMr/HdZFK9tZfvmYPK46g75zjipcD8irTPE1YBEfu1LRLC
TMntdMZq8dDxDVQ4hgE0k69Mv85pN7Xjm/E9ODIzk9V43ZRiDWLMmuRWm7vKrIbi
z2XYIMDO+DN0BCjSz2/jw1mCY9lWJwAcW/+tBgyJsMzUrDTtaC/4awo4NN3S+6hd
1+DIovoMSC/1cBh0gUhzJ6ySLRLcjI3AF0okPbR6iMNKm9aUY9S4fCM7kjf0vmD+
AmOrL4h61iM1omm3spmHzmnpFP4JNmV5yjfEKbbNcs4ZBQ1tcR4=
=mq0M
-END PGP SIGNATURE End Message ---

Bug#957034: marked as done (bandwidthd: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 21:18:27 +
with message-id 
and subject line Bug#957034: fixed in bandwidthd 2.0.1+cvs20090917-12
has caused the Debian Bug report #957034,
regarding bandwidthd: 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.)


-- 
957034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bandwidthd
Version: 2.0.1+cvs20090917-11
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/bandwidthd_2.0.1+cvs20090917-11_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

[...]
In file included from conf.y:12:
bandwidthd.h:250:17: warning: inline function ‘DstCredit’ declared but never 
defined
  250 | inline void DstCredit(uint32_t ipaddr, unsigned int psize);
  | ^
In file included from conf.y:12:
bandwidthd.h:237:23: warning: inline function ‘FindIp’ declared but never 
defined
  237 | inline struct IPData *FindIp(uint32_t ipaddr);
  |   ^~
bandwidthd.h:234:17: warning: inline function ‘Credit’ declared but never 
defined
  234 | inline void Credit(struct Statistics *Stats, const struct ip *ip);
  | ^~
bandwidthd.h:231:17: warning: inline function ‘IpAddr’ declared but never 
defined
  231 | inline uint32_t IpAddr(unsigned char q1, unsigned char q2, unsigned 
char q3, unsigned char q4);
  | ^~
flex -Pbdconfig_ -s -i -t -I conf.l > conf.l.c
gcc -g -O2  -I/usr/local/include -DHAVE_CONFIG_H -c -o conf.l.o conf.l.c
gcc -Wall -g -O2  -I/usr/local/include -DHAVE_CONFIG_H   -c -o pgsql.o pgsql.c
In file included from pgsql.c:1:
bandwidthd.h:250:17: warning: inline function ‘DstCredit’ declared but never 
defined
  250 | inline void DstCredit(uint32_t ipaddr, unsigned int psize);
  | ^
In file included from pgsql.c:1:
bandwidthd.h:237:23: warning: inline function ‘FindIp’ declared but never 
defined
  237 | inline struct IPData *FindIp(uint32_t ipaddr);
  |   ^~
bandwidthd.h:234:17: warning: inline function ‘Credit’ declared but never 
defined
  234 | inline void Credit(struct Statistics *Stats, const struct ip *ip);
  | ^~
bandwidthd.h:231:17: warning: inline function ‘IpAddr’ declared but never 
defined
  231 | inline uint32_t IpAddr(unsigned char q1, unsigned char q2, unsigned 
char q3, unsigned char q4);
  | ^~
pgsql.c:418:13: warning: ‘pgsqllngjmp’ defined but not used [-Wunused-function]
  418 | static void pgsqllngjmp(int signal)
  | ^~~
gcc -Wall -g -O2  -I/usr/local/include -DHAVE_CONFIG_H   -c -o extensions.o 
extensions.c
In file included from extensions.c:1:
bandwidthd.h:250:17: warning: inline function ‘DstCredit’ declared but never 
defined
  250 | inline void DstCredit(uint32_t ipaddr, unsigned int psize);
  | ^
In file included from extensions.c:1:
bandwidthd.h:237:23: warning: inline function ‘FindIp’ declared but never 
defined
  237 | inline struct IPData *FindIp(uint32_t ipaddr);
  |   ^~
bandwidthd.h:234:17: warning: inline function ‘Credit’ declared but never 
defined
  234 | inline void Credit(struct Statistics *Stats, const struct ip *ip);
  | ^~
bandwidthd.h:231:17: warning: inline function ‘IpAddr’ declared but never 
defined
  231 | 

Bug#936299: marked as done (chirp: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 21:18:33 +
with message-id 
and subject line Bug#936299: fixed in chirp 1:20200227+py3+20200213-1
has caused the Debian Bug report #936299,
regarding chirp: 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.)


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

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: chirp
Source-Version: 1:20200227+py3+20200213-1
Done: Christoph Berg 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 06 Aug 2020 22:59:46 +0200
Source: chirp
Architecture: source
Version: 1:20200227+py3+20200213-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 885265 936299
Changes:
 chirp (1:20200227+py3+20200213-1) unstable; urgency=medium
 .
   * Switch to upstream py3 branch based on python3-wxgtk4.0.
 (Closes: #885265, #936299)
   * Lots of python3 porting missing, tested so far: Baofeng UV-5R.
Checksums-Sha1:
 89e008df68c1376761b8a2549a21bc35efd8b7b4 2193 chirp_20200227+py3+20200213-1.dsc
 aeba1b24682bc62765386988fca317a7a7a0a5ee 1198525 
chirp_20200227+py3+20200213.orig.tar.gz
 e81437a37e483eb7970153020f025c34eac18140 11760 
chirp_20200227+py3+20200213-1.debian.tar.xz
Checksums-Sha256:
 18e70711e5489de4ca75aa580a6e95eab811ce10886cd44ee45ede66ba2395d5 2193 
chirp_20200227+py3+20200213-1.dsc
 

Bug#885265: [py3] some fixes to get chirpw running with python3, Fixes #7431

[Christoph Berg]

Re: Arturo Borrero Gonzalez
> I tested chirp from the upstream mercurial repository (py3 branch) today in
> Debian testing bullseye, and I got it working with python3 with the attached 
> patch.

Hi Arturo,

thanks for picking this up. I had done some python3 hacking on chirp
earlier this year, but apparently never pushed the changes anywhere
since they weren't working.

> I was able to download the image from a baofeng UV-5RA, modify it and the 
> upload
> it again.

I confirm that my UV-5R works now as well. Cool.

Fwiw, I've tried to submit changes to the tracker on danplanet for
about half a dozen times and it always failed, so no idea where to
send my patches. If this mail gets through, the python3 patches are
there:

https://salsa.debian.org/debian-hamradio-team/chirp/-/tree/master/debian/patches

py3-print: print foo => print(foo) changes
py3-except: except Exception, e => except Exception as e changes
py3-fixes: the (small) rest

Only the UV-5R module is tested, there are many other issues remaining
in the other modules, but this is a start.

Thanks,
Christoph

Processed: Bug#936299 marked as pending in chirp

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #936299 [src:chirp] chirp: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #936299 to the same tags previously set

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

Bug#885265: marked as pending in chirp

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #885265 in chirp 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/debian-hamradio-team/chirp/-/commit/2615a86f332fd119e52ee2e82a78b14d0c5a334f


Switch to upstream py3 branch based on python3-wxgtk4.0. (Closes: #885265, 
#936299)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/885265

Bug#936299: marked as pending in chirp

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #936299 in chirp 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/debian-hamradio-team/chirp/-/commit/2615a86f332fd119e52ee2e82a78b14d0c5a334f


Switch to upstream py3 branch based on python3-wxgtk4.0. (Closes: #885265, 
#936299)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/936299

Processed: Bug#885265 marked as pending in chirp

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #885265 [src:chirp] chirp: Depends on unmaintained pygtk
Ignoring request to alter tags of bug #885265 to the same tags previously set

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

Bug#968027: dino-im: FTBFS: error: [...]/xmpp-vala/src/glib_fixes.vapi not found

[Andreas Beckmann]

Source: dino-im
Version: 0.1.0+20200623.717d0b7-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

dino-im/experimental FTBFS on all architectures:
https://buildd.debian.org/status/package.php?p=dino-im=experimental

   dh_auto_build -a -O--buildsystem=cmake\+ninja
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v
[1/642] cd /<>/obj-x86_64-linux-gnu/xmpp-vala && echo -e 
"gdk-pixbuf-2.0\ngee-0.8\ngio-2.0\nglib-2.0\ngobject-2.0\nicu-uc\n" > 
/<>/obj-x86_64-linux-gnu/exports/xmpp-vala.deps
[2/642] cd /<>/obj-x86_64-linux-gnu/qlite && echo -e 
"gee-0.8\nglib-2.0\ngobject-2.0\nsqlite3\n" > 
/<>/obj-x86_64-linux-gnu/exports/qlite.deps
[3/642] cd /<>/obj-x86_64-linux-gnu/libdino && echo -e 
"gdk-pixbuf-2.0\ngee-0.8\nglib-2.0\ngmodule-2.0\ngobject-2.0\nxmpp-vala\nqlite" 
> /<>/obj-x86_64-linux-gnu/exports/dino.deps
[4/642] cd /<>/obj-x86_64-linux-gnu/libdino && cp 
/<>/libdino/src/dino_i18n.h 
/<>/obj-x86_64-linux-gnu/exports/dino_i18n.h
[5/642] cd /<>/obj-x86_64-linux-gnu/xmpp-vala && /usr/bin/valac 
--color=always -C 
--header=/<>/obj-x86_64-linux-gnu/exports/xmpp-vala.h 
--internal-header=/<>/obj-x86_64-linux-gnu/exports/xmpp-vala_internal.h
 --vapi=/<>/obj-x86_64-linux-gnu/exports/xmpp-vala.vapi 
--internal-vapi=/<>/obj-x86_64-linux-gnu/exports/xmpp-vala_internal.vapi
 -b /<>/xmpp-vala -d 
/<>/obj-x86_64-linux-gnu/xmpp-vala --pkg=gdk-pixbuf-2.0 
--pkg=gee-0.8 --pkg=gio-2.0 --pkg=glib-2.0 --pkg=gobject-2.0 --pkg=icu-uc 
--define=ALPN_SUPPORT --vapidir=/<>/xmpp-vala/vapi -g 
--target-glib=2.38 /<>/xmpp-vala/src/core/namespace_state.vala 
/<>/xmpp-vala/src/core/stanza_attribute.vala 
/<>/xmpp-vala/src/core/stanza_node.vala 
/<>/xmpp-vala/src/core/stanza_reader.vala 
/<>/xmpp-vala/src/core/stanza_writer.vala 
/<>/xmpp-vala/src/core/xmpp_log.vala 
/<>/xmpp-vala/src/core/xmpp_stream.vala 
/<>/xmpp-vala/src/module/bind.vala 
/<>/xmpp-vala/src/module/bookmarks_provider.vala 
/<>/xmpp-vala/src/module/conference.vala 
/<>/xmpp-vala/src/module/iq/module.vala 
/<>/xmpp-vala/src/module/iq/stanza.vala 
/<>/xmpp-vala/src/module/jid.vala 
/<>/xmpp-vala/src/module/message/module.vala 
/<>/xmpp-vala/src/module/message/stanza.vala 
/<>/xmpp-vala/src/module/presence/flag.vala 
/<>/xmpp-vala/src/module/presence/module.vala 
/<>/xmpp-vala/src/module/presence/stanza.vala 
/<>/xmpp-vala/src/module/roster/flag.vala 
/<>/xmpp-vala/src/module/roster/item.vala 
/<>/xmpp-vala/src/module/roster/module.vala 
/<>/xmpp-vala/src/module/roster/versioning_module.vala 
/<>/xmpp-vala/src/module/sasl.vala 
/<>/xmpp-vala/src/module/session.vala 
/<>/xmpp-vala/src/module/stanza.vala 
/<>/xmpp-vala/src/module/stanza_error.vala 
/<>/xmpp-vala/src/module/stream_error.vala 
/<>/xmpp-vala/src/module/tls.vala 
/<>/xmpp-vala/src/module/util.vala 
/<>/xmpp-vala/src/module/xep/0048_bookmarks.vala 
/<>/xmpp-vala/src/module/xep/0048_conference.vala 
/<>/xmpp-vala/src/module/xep/0402_bookmarks2.vala 
/<>/xmpp-vala/src/module/xep/0004_data_forms.vala 
/<>/xmpp-vala/src/module/xep/0030_service_discovery/flag.vala 
/<>/xmpp-vala/src/module/xep/0030_service_discovery/identity.vala 
/<>/xmpp-vala/src/module/xep/0030_service_discovery/info_result.vala
 /<>/xmpp-vala/src/module/xep/0030_service_discovery/item.vala 
/<>/xmpp-vala/src/module/xep/0030_service_discovery/items_result.vala
 /<>/xmpp-vala/src/module/xep/0030_service_discovery/module.vala 
/<>/xmpp-vala/src/module/xep/0045_muc/flag.vala 
/<>/xmpp-vala/src/module/xep/0045_muc/module.vala 
/<>/xmpp-vala/src/module/xep/0045_muc/status_code.vala 
/<>/xmpp-vala/src/module/xep/0047_in_band_bytestreams.vala 
/<>/xmpp-vala/src/module/xep/0049_private_xml_storage.vala 
/<>/xmpp-vala/src/module/xep/0054_vcard/module.vala 
/<>/xmpp-vala/src/module/xep/0060_pubsub.vala 
/<>/xmpp-vala/src/module/xep/0065_socks5_bytestreams.vala 
/<>/xmpp-vala/src/module/xep/0066_out_of_band_data.vala 
/<>/xmpp-vala/src/module/xep/0077_in_band_registration.vala 
/<>/xmpp-vala/src/module/xep/0082_date_time_profiles.vala 
/<>/xmpp-vala/src/module/xep/0084_user_avatars.vala 
/<>/xmpp-vala/src/module/xep/0085_chat_state_notifications.vala 
/<>/xmpp-vala/src/module/xep/0115_entitiy_capabilities.vala 
/<>/xmpp-vala/src/module/xep/0166_jingle.vala 
/<>/xmpp-vala/src/module/xep/0184_message_delivery_receipts.vala 
/<>/xmpp-vala/src/module/xep/0191_blocking_command.vala 
/<>/xmpp-vala/src/module/xep/0198_stream_management.vala 
/<>/xmpp-vala/src/module/xep/0199_ping.vala 
/<>/xmpp-vala/src/module/xep/0203_delayed_delivery.vala 
/<>/xmpp-vala/src/module/xep/0234_jingle_file_transfer.vala 
/<>/xmpp-vala/src/module/xep/0260_jingle_socks5_bytestreams.vala 
/<>/xmpp-vala/src/module/xep/0261_jingle_in_band_bytestreams.vala 
/<>/xmpp-vala/src/module/xep/0280_message_carbons.vala 
/<>/xmpp-vala/src/module/xep/0308_last_message_correction.vala 
/<>/xmpp-vala/src/module/xep/0313_message_archive_management.vala 
/<>/xmpp-vala/src/module/xep/0333_chat_markers.vala 

Bug#957698: marked as done (pommed: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 20:25:57 +
with message-id 
and subject line Bug#957698: fixed in pommed 1.39~dfsg-5.1
has caused the Debian Bug report #957698,
regarding pommed: 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.)


-- 
957698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pommed
Version: 1.39~dfsg-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/pommed_1.39~dfsg-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

[...]
  679 | {
  | ^
gcc -g -O2 -Wall -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -DDBUS_API_SUBJECT_TO_CHANGE 
-I/usr/include/x86_64-linux-gnu -Wdate-time -D_FORTIFY_SOURCE=2  -c -o evloop.o 
evloop.c
gcc -g -O2 -Wall -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -DDBUS_API_SUBJECT_TO_CHANGE 
-I/usr/include/x86_64-linux-gnu -Wdate-time -D_FORTIFY_SOURCE=2  -c -o dbus.o 
dbus.c
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 gpomme.h:8,
 from conffile.c:39:
/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.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 gpomme.h:8,
 from conffile.c:39:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
gcc -g -O2 -Wall -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -DDBUS_API_SUBJECT_TO_CHANGE 
-I/usr/include/x86_64-linux-gnu -Wdate-time -D_FORTIFY_SOURCE=2  -c -o power.o 
power.c
evloop.c: In function ‘evloop_timer_callback’:
evloop.c:141:3: warning: ignoring return value of ‘read’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  141 |   read(fd, , sizeof(ticks));
  |   ^~~
power.c: In function ‘sysfs_check_ac_state’:
power.c:54:3: warning: ignoring return value of ‘fread’ declared with attribute 
‘warn_unused_result’ [-Wunused-result]
   54 |   fread(_state, 1, 1, fp);
  |   ^~
In file included from /usr/include/string.h:495,
 from conffile.c:22:
In function ‘strncpy’,
inlined from ‘config_load’ at conffile.c:129: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));
  |  

Bug#968024: netpbm-free: Unversioned Python removal in sid/bullseye

[Andreas Beckmann]

Source: netpbm-free
Version: 2:10.78.05-0.1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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.

Processed: tagging 967173, tagging 968019, tagging 957599, tagging 967032, found 967032 in 14.4.0~dfsg-2

[Debian Bug Tracking System]

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

> tags 967173 + experimental
Bug #967173 [src:mediaelement] mediaelement: Unversioned Python removal in 
sid/bullseye
Added tag(s) experimental.
> tags 968019 =
Bug #968019 [src:enhanceio] enhanceio: Unversioned Python removal in 
sid/bullseye
Removed tag(s) bullseye and sid.
> tags 957599 + experimental
Bug #957599 [src:netpbm-free] netpbm-free: ftbfs with GCC-10
Added tag(s) experimental.
> tags 967032 + experimental
Bug #967032 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } 
[src:nodejs] nodejs: Unversioned Python removal in sid/bullseye
Added tag(s) experimental.
> found 967032 14.4.0~dfsg-2
Bug #967032 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } 
[src:nodejs] nodejs: Unversioned Python removal in sid/bullseye
Marked as found in versions nodejs/14.4.0~dfsg-2 and reopened.
> thanks
Stopping processing here.

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

Bug#968023: munin: Unversioned Python removal in sid/bullseye

[Andreas Beckmann]

Source: munin
Version: 2.999.14-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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.

Bug#967997: rdiff-backup: maintainer address invalid

[Otto Kekäläinen]

While researching this I only found packages that list the old group email:

Maintainer: Python Applications Packaging Team

- 
https://salsa.debian.org/python-team/applications/nitrotool/-/blob/master/debian/control
- 
https://salsa.debian.org/python-team/applications/terminator/-/blob/debian/master/debian/control
- 
https://salsa.debian.org/python-team/applications/protonvpn-cli/-/blob/debian/master/debian/control
- 
https://salsa.debian.org/python-team/applications/pyflakes/-/blob/debian/master/debian/control
- 
https://salsa.debian.org/python-team/applications/gnome-authenticator/-/blob/debian/master/debian/control

This package does not list any group mailing list at all:
- 
https://salsa.debian.org/python-team/applications/commit-helper/-/blob/master/debian/control

I am not sure what to do here. Maybe just remove myself as uploader
and make myself the maintainer alone, but that is kind of semantically
wrong, since this is team maintained.



-- 
- Otto

Bug#968022: sequitur-g2p: Unversioned Python removal in sid/bullseye

[Andreas Beckmann]

Source: sequitur-g2p
Version: 0+r1668.r3-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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.

Bug#968019: enhanceio: Unversioned Python removal in sid/bullseye

[Andreas Beckmann]

Source: enhanceio
Version: 0+git20190417.5815670-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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.

Bug#957995: marked as done (xscorch: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 19:34:06 +
with message-id 
and subject line Bug#957995: fixed in xscorch 0.2.1-1+nmu4
has caused the Debian Bug report #957995,
regarding xscorch: 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.)


-- 
957995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xscorch
Version: 0.2.1-1+nmu2
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/xscorch_0.2.1-1+nmu2_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[4]: Leaving directory '/<>/libj/jreg'
Making all in jstr
make[4]: Entering directory '/<>/libj/jstr'
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_arg.o -MD 
-MP -MF .deps/libjstr_a-str_arg.Tpo -c -o libjstr_a-str_arg.o `test -f 
'str_arg.c' || echo './'`str_arg.c
mv -f .deps/libjstr_a-str_arg.Tpo .deps/libjstr_a-str_arg.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_case.o 
-MD -MP -MF .deps/libjstr_a-str_case.Tpo -c -o libjstr_a-str_case.o `test -f 
'str_case.c' || echo './'`str_case.c
mv -f .deps/libjstr_a-str_case.Tpo .deps/libjstr_a-str_case.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_cgi.o -MD 
-MP -MF .deps/libjstr_a-str_cgi.Tpo -c -o libjstr_a-str_cgi.o `test -f 
'str_cgi.c' || echo './'`str_cgi.c
mv -f .deps/libjstr_a-str_cgi.Tpo .deps/libjstr_a-str_cgi.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_comp.o 
-MD -MP -MF .deps/libjstr_a-str_comp.Tpo -c -o libjstr_a-str_comp.o `test -f 
'str_comp.c' || echo './'`str_comp.c
mv -f .deps/libjstr_a-str_comp.Tpo .deps/libjstr_a-str_comp.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_con.o -MD 
-MP -MF .deps/libjstr_a-str_con.Tpo -c -o libjstr_a-str_con.o `test -f 
'str_con.c' || echo './'`str_con.c
mv -f .deps/libjstr_a-str_con.Tpo .deps/libjstr_a-str_con.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_copy.o 
-MD -MP -MF .deps/libjstr_a-str_copy.Tpo -c -o libjstr_a-str_copy.o `test -f 
'str_copy.c' || echo './'`str_copy.c
mv -f .deps/libjstr_a-str_copy.Tpo .deps/libjstr_a-str_copy.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_creat.o 
-MD -MP -MF .deps/libjstr_a-str_creat.Tpo -c -o libjstr_a-str_creat.o `test -f 
'str_creat.c' || echo './'`str_creat.c
mv -f .deps/libjstr_a-str_creat.Tpo .deps/libjstr_a-str_creat.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_info.o 
-MD -MP -MF .deps/libjstr_a-str_info.Tpo -c -o libjstr_a-str_info.o `test -f 
'str_info.c' || echo './'`str_info.c
mv -f .deps/libjstr_a-str_info.Tpo .deps/libjstr_a-str_info.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_io.o -MD 
-MP -MF .deps/libjstr_a-str_io.Tpo -c -o libjstr_a-str_io.o `test -f 'str_io.c' 
|| echo './'`str_io.c
mv -f .deps/libjstr_a-str_io.Tpo .deps/libjstr_a-str_io.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_num.o -MD 
-MP -MF .deps/libjstr_a-str_num.Tpo -c -o libjstr_a-str_num.o `test -f 
'str_num.c' || echo './'`str_num.c
mv -f .deps/libjstr_a-str_num.Tpo .deps/libjstr_a-str_num.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_printf.o 
-MD -MP -MF .deps/libjstr_a-str_printf.Tpo -c -o libjstr_a-str_printf.o `test 
-f 'str_printf.c' || echo './'`str_printf.c
mv -f .deps/libjstr_a-str_printf.Tpo .deps/libjstr_a-str_printf.Po
gcc 

Processed: Re: zsnapd: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #943302 [src:zsnapd] zsnapd: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'

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

Bug#964637: [Pkg-javascript-devel] Bug#964637: node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1

[Xavier]

Le 06/08/2020 à 20:51, Xavier a écrit :
> Control: reassign -1 node-typescript-types
> 
> FTBFS is due to @types/node which was upgraded to version 14.0.14 while
> we run nodejs 12

It's time to move @types/node from src:typescript-types to src:nodejs

Bug#957645: marked as done (oroborus: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 19:19:58 +
with message-id 
and subject line Bug#957645: fixed in oroborus 2.0.20+nmu1
has caused the Debian Bug report #957645,
regarding oroborus: 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.)


-- 
957645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:oroborus
Version: 2.0.20
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/oroborus_2.0.20_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

[...]
then mv -f ".deps/frame.Tpo" ".deps/frame.Po"; else rm -f ".deps/frame.Tpo"; 
exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT getopt1.o -MD -MP -MF ".deps/getopt1.Tpo" -c -o getopt1.o 
getopt1.c; \
then mv -f ".deps/getopt1.Tpo" ".deps/getopt1.Po"; else rm -f 
".deps/getopt1.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT getopt.o -MD -MP -MF ".deps/getopt.Tpo" -c -o getopt.o 
getopt.c; \
then mv -f ".deps/getopt.Tpo" ".deps/getopt.Po"; else rm -f ".deps/getopt.Tpo"; 
exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT globals.o -MD -MP -MF ".deps/globals.Tpo" -c -o globals.o 
globals.c; \
then mv -f ".deps/globals.Tpo" ".deps/globals.Po"; else rm -f 
".deps/globals.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT hints.o -MD -MP -MF ".deps/hints.Tpo" -c -o hints.o hints.c; \
then mv -f ".deps/hints.Tpo" ".deps/hints.Po"; else rm -f ".deps/hints.Tpo"; 
exit 1; fi
hints.c: In function ‘initGnomeHints’:
hints.c:152:10: warning: variable ‘root’ set but not used 
[-Wunused-but-set-variable]
  152 |   Window root;
  |  ^~~~
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT i18n.o -MD -MP -MF ".deps/i18n.Tpo" -c -o i18n.o i18n.c; \
then mv -f ".deps/i18n.Tpo" ".deps/i18n.Po"; else rm -f ".deps/i18n.Tpo"; exit 
1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT keyboard.o -MD -MP -MF ".deps/keyboard.Tpo" -c -o keyboard.o 
keyboard.c; \
then mv -f ".deps/keyboard.Tpo" ".deps/keyboard.Po"; else rm -f 
".deps/keyboard.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT misc.o -MD -MP -MF ".deps/misc.Tpo" -c -o misc.o misc.c; \
then mv -f ".deps/misc.Tpo" ".deps/misc.Po"; else rm -f ".deps/misc.Tpo"; exit 
1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT oroborus.o -MD -MP -MF ".deps/oroborus.Tpo" -c -o oroborus.o 
oroborus.c; \
then mv -f ".deps/oroborus.Tpo" ".deps/oroborus.Po"; else rm -f 
".deps/oroborus.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT parserc.o -MD -MP -MF ".deps/parserc.Tpo" -c -o parserc.o 
parserc.c; \
then mv -f ".deps/parserc.Tpo" ".deps/parserc.Po"; else rm -f 
".deps/parserc.Tpo"; exit 1; fi
parserc.c: In function ‘parseRc’:
parserc.c:47:5: warning: ‘strncpy’ specified bound 512 equals destination size 
[-Wstringop-truncation]
   47 | strncpy (filename, file, sizeof (filename));
  | ^~~
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  

Bug#966702: marked as done (mongo-cxx-driver: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Thu, 6 Aug 2020 15:13:22 -0400
with message-id <20200806191322.gf13...@connexer.com>
and subject line Re: Bug#966702: mongo-cxx-driver: maintainer address bounces
has caused the Debian Bug report #966702,
regarding mongo-cxx-driver: maintainer address bounces
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.)


-- 
966702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongo-cxx-driver
Version: 3.6.0-1
Severity: serious
X-Debbugs-Cc: Roberto C. Sanchez 

The maintainer address bounces, see below.

Ansgar

 Forwarded Message 
From: Mail Delivery Subsystem 
To: envel...@ftp-master.debian.org
Subject: Delivery Status Notification (Failure)
Date: Fri, 31 Jul 2020 17:34:08 -0700 (PDT)
Authentication-Results: tsukuyomi; dkim=pass (Good 2048 bit rsa-sha256 

   signature) header.d=googlemail.com header.a=rsa-sha256
X-Spam-Status: No, score=-101.9 required=5.0 
tests=BAYES_00,RCVD_IN_DNSWL_NONE,
SHORTCIRCUIT shortcircuit=ham 
autolearn=disabled version=3.4.2

Hello ftpmas...@ftp-master.debian.org,

We're writing to let you know that the group you tried to contact 
(mongo-cxx-driver-debian) may not exist, or you may not have permission to post 
messages to the group. A few more details on why you weren't able to post:

 * You might have spelled or formatted the group name incorrectly.
 * The owner of the group may have removed this group.
 * You may need to join the group before receiving permission to post.
 * This group may not be open to posting.

If you have questions related to this or any other Google Group, visit the Help 
Center at https://groups.google.com/support/.

Thanks,

Google Groups



- Original message -

X-Google-Smtp-Source: 
ABdhPJwHRCOrpgXWjZI0cNO0Ut5Nj9NtgTlkcmjDB98t1jmqaLbiHNDnltvm43img0BhMZV+q8Ge
X-Received: by 2002:a1c:9a02:: with SMTP id c2mr6501743wme.16.1596242048316;
Fri, 31 Jul 2020 17:34:08 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1596242048; cv=none;
d=google.com; s=arc-20160816;
b=OZWP0X/e1+poO0/njPMgEzl7xxplS38kGNFAuif7twjiehuLOF8jsGy4GuQGY0XU7+
 BEEpeLzkmglqMnRMafEO+Oj6UMwCBkViZX4QbnNtsHSCJcCCGMHvryooPVNf4cxFxEB7
 1bAhCDUYkXDoiy8Hzqg/TgfV4pVCSTNu/TLyF+dxpnuDZi/LLu8WAZYWDn2y/s5j6blu
 8NtbvyrhN14O4LAO+WMfIv/SqOlS96IExeJnguLFOZ+mJZEKi3e8JBLPLnCn740o7GP2
 ylZ4+xI8Vf5pOGUo+uLVZWNYXBJgTWupnkO20YdhIiCWGTBkBvL+2EoVp+qzkdNfGK3e
 TxAA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; 
s=arc-20160816;
h=date:message-id:subject:content-transfer-encoding:mime-version
 :auto-submitted:precedence:to:from;
bh=pMWByNUUOJCpAwm8HG7BWG7fSKEVM2pWZL7v1quA8lg=;
b=UdeOpVXBU2fecAcbIVR7fOjwF0gaBOc5xlV96I9clq36fj9dTN/vmpdkNKIe0v7/hy
 QfJOBCNi3mE3MVDHx8m81j6W8emDOMn0FZPH5+C5WcpcCR0LX6ARS/EWOFpv7fJp+K0j
 q0F41n7dkaz/m2AFhelLyemYHpxC75+cw/h1Hd94vb+Nrjh931nSE6PfMQqoVyqkuPgk
 CoUjQEOS/ZFYSJFDsZuwLRdP3SB8iMTDBwBgFaqR900nfpeAH3OJuJPhxgkFkbjScjq6
 /0e9SCWJbkWvrjtQ3NzovTG+Uw+Ts3mYUrrXYY5vxLlUKCiGO9B/xNyiDP15OzfOb3O2
 51Uw==
ARC-Authentication-Results: i=1; gmr-mx.google.com;
   spf=pass (google.com: best guess record for domain of 
envel...@ftp-master.debian.org designates 2001:41b8:202:deb:6564:a62:52c3:4b72 
as permitted sender) smtp.mailfrom=envel...@ftp-master.debian.org
Return-Path: 
Received: from mailly.debian.org (mailly.debian.org. 
[2001:41b8:202:deb:6564:a62:52c3:4b72])
by gmr-mx.google.com with ESMTPS id m3si648598wme.0.2020.07.31.17.34.08
for 
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Fri, 31 Jul 2020 17:34:08 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of 
envel...@ftp-master.debian.org designates 2001:41b8:202:deb:6564:a62:52c3:4b72 
as permitted sender) client-ip=2001:41b8:202:deb:6564:a62:52c3:4b72;
Authentication-Results: gmr-mx.google.com;
   spf=pass (google.com: best guess record for domain of 
envel...@ftp-master.debian.org designates 2001:41b8:202:deb:6564:a62:52c3:4b72 
as permitted sender) smtp.mailfrom=envel...@ftp-master.debian.org
Received: from fasolo.debian.org ([138.16.160.17]:44886)
from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP 
CA,CN=fasolo.debian.org,EMAIL=hostmas...@fasolo.debian.org (verified)
by mailly.debian.org with esmtps 
(TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.92)
(envelope-from )
id 1k1fTT-0006aS-VU; Sat, 01 Aug 2020 00:34:07 +

Bug#957360: RFS: Bug#957360: insighttoolkit4: ftbfs with GCC-10

[Étienne Mollier]

Control: tag -1 pending

Good day,

This night's build of insighttoolkit 4.13.3 in the clean chroot
went through, and test suite validated without particular
issues.  I pushed the part of my work fixing #957360 on Salsa:

https://salsa.debian.org/med-team/insighttoolkit

As is, it may not be lintian clean, but I only managed to start
a gbp run only a few moments ago, so will have the .dsc to
scan against tomorrow.

If someone else attempts a run with git buildpackage, note the
external data fetched by debian/rules get-orig-source, which
need to be put into an appropriate archive .orig-data.tar.gz;
something specific to format 3.0 (quilt) if I understood
correctly dpkg-source(1).  I'm not comfortable with this format,
so haven't marked the release as ready for upload yet, by fear
of having screwed the branch named "upstream", but maybe it is.

Kind Regards,
-- 
Étienne Mollier 
Old rsa/3072: 5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d
New rsa/4096: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/3, please excuse my verbosity.


signature.asc
Description: PGP signature

Processed: RFS: Bug#957360: insighttoolkit4: ftbfs with GCC-10

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#957820: marked as done (snap: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 19:03:55 +
with message-id 
and subject line Bug#957820: fixed in snap 2013-11-29-10
has caused the Debian Bug report #957820,
regarding snap: 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.)


-- 
957820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:snap
Version: 2013-11-29-9
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/snap_2013-11-29-9_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: zoeDNA.o:./Zoe/zoeTools.h:45: multiple definition of `zoeMethod'; 
zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeDNA.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeDNA.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeDistribution.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeDistribution.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeDistribution.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeDuration.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeDuration.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeDuration.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeFastaFile.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeFastaFile.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeFastaFile.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeFeature.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeFeature.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeFeature.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeFeatureFactory.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeFeatureFactory.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeFeatureFactory.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeFeatureTable.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeFeatureTable.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeFeatureTable.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: 

Bug#964637: node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1

[Xavier]

Control: reassign -1 node-typescript-types

FTBFS is due to @types/node which was upgraded to version 14.0.14 while
we run nodejs 12

Processed: Re: node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 node-typescript-types
Bug #964637 [src:node-rollup] node-rollup: FTBFS: dh_auto_build: error: cd ./. 
&& sh -ex debian/nodejs/./build returned exit code 1
Bug reassigned from package 'src:node-rollup' to 'node-typescript-types'.
No longer marked as found in versions node-rollup/1.12.0-2.
Ignoring request to alter fixed versions of bug #964637 to the same values 
previously set

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

Processed: affects 964637

[Debian Bug Tracking System]

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

> affects 964637 rollup
Bug #964637 [src:node-rollup] node-rollup: FTBFS: dh_auto_build: error: cd ./. 
&& sh -ex debian/nodejs/./build returned exit code 1
Added indication that 964637 affects rollup
> thanks
Stopping processing here.

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

Bug#957798: marked as done (silversearcher-ag: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 18:18:30 +
with message-id 
and subject line Bug#957798: fixed in silversearcher-ag 2.2.0+git20200805-1
has caused the Debian Bug report #957798,
regarding silversearcher-ag: 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.)


-- 
957798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:silversearcher-ag
Version: 2.2.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/silversearcher-ag_2.2.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

[...]
gcc -DHAVE_CONFIG_H -I. -I./src   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -pthread  -Wall -Wextra -Wformat=2 
-Wno-format-nonliteral -Wshadow -Wpointer-arith -Wcast-qual 
-Wmissing-prototypes -Wno-missing-braces -std=gnu89 -D_GNU_SOURCE -c -o 
src/main.o src/main.c
gcc -DHAVE_CONFIG_H -I. -I./src   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -pthread  -Wall -Wextra -Wformat=2 
-Wno-format-nonliteral -Wshadow -Wpointer-arith -Wcast-qual 
-Wmissing-prototypes -Wno-missing-braces -std=gnu89 -D_GNU_SOURCE -c -o 
src/zfile.o src/zfile.c
gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -pthread  -Wall -Wextra -Wformat=2 
-Wno-format-nonliteral -Wshadow -Wpointer-arith -Wcast-qual 
-Wmissing-prototypes -Wno-missing-braces -std=gnu89 -D_GNU_SOURCE  -Wl,-z,relro 
-o ag src/ignore.o src/log.o src/options.o src/print.o src/print_w32.o 
src/scandir.o src/search.o src/lang.o src/util.o src/decompress.o src/main.o 
src/zfile.o -lpcre -llzma   -lz  
/usr/bin/ld: src/log.o:./src/log.h:12: multiple definition of `print_mtx'; 
src/ignore.o:./src/log.h:12: first defined here
/usr/bin/ld: src/log.o:./src/util.h:15: multiple definition of `out_fd'; 
src/ignore.o:./src/util.h:15: first defined here
/usr/bin/ld: src/log.o:./src/util.h:54: multiple definition of `stats'; 
src/ignore.o:./src/util.h:54: first defined here
/usr/bin/ld: src/log.o:./src/options.h:94: multiple definition of `opts'; 
src/ignore.o:./src/options.h:94: first defined here
/usr/bin/ld: src/options.o:./src/options.h:94: multiple definition of `opts'; 
src/ignore.o:./src/options.h:94: first defined here
/usr/bin/ld: src/options.o:./src/ignore.h:32: multiple definition of 
`root_ignores'; src/ignore.o:./src/ignore.h:32: first defined here
/usr/bin/ld: src/options.o:./src/util.h:15: multiple definition of `out_fd'; 
src/ignore.o:./src/util.h:15: first defined here
/usr/bin/ld: src/options.o:./src/util.h:54: multiple definition of `stats'; 
src/ignore.o:./src/util.h:54: first defined here
/usr/bin/ld: src/options.o:./src/log.h:12: multiple definition of `print_mtx'; 
src/ignore.o:./src/log.h:12: first defined here
/usr/bin/ld: src/print.o:./src/options.h:94: multiple definition of `opts'; 
src/ignore.o:./src/options.h:94: first defined here
/usr/bin/ld: src/print.o:./src/util.h:15: multiple definition of `out_fd'; 
src/ignore.o:./src/util.h:15: first defined here
/usr/bin/ld: src/print.o:./src/util.h:54: multiple definition of `stats'; 
src/ignore.o:./src/util.h:54: first defined here
/usr/bin/ld: src/print.o:./src/log.h:12: multiple definition of `print_mtx'; 
src/ignore.o:./src/log.h:12: first defined here
/usr/bin/ld: src/print.o:./src/ignore.h:32: multiple 

Bug#960120: different error during build

[Paolo Greppi]

With this build:
https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/915568#L2420

I get a different error while building:
[17:58:12] Starting 'build'...
2420[17:58:13] Error: [BABEL] 
/builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.22.4/src/api.js: 
Cannot find module 'babel-plugin-transform-strict-mode'

?

Paolo

Bug#899676: marked as done (python-omniorb: Invalid maintainer address pkg-corba-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:35:07 +
with message-id 
and subject line Bug#967054: Removed package(s) from unstable
has caused the Debian Bug report #899676,
regarding python-omniorb: Invalid maintainer address 
pkg-corba-de...@lists.alioth.debian.org
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.)


-- 
899676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-omniorb
Version: 3.6-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of python-omniorb,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package python-omniorb since the list address
pkg-corba-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-corba-de...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 4.2.2-0.2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:35:07 +
with message-id 
and subject line Bug#967054: Removed package(s) from unstable
has caused the Debian Bug report #937970,
regarding python-omniorb: 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.)


-- 
937970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-omniorb
Version: 4.2.2-0.2
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:python-omniorb

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 ---
Version: 4.2.2-0.2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966779: marked as done (python-ntlm: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:33:22 +
with message-id 
and subject line Bug#966802: Removed package(s) from unstable
has caused the Debian Bug report #937959,
regarding python-ntlm: Unversioned Python 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.)


-- 
937959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-ntlm
Version: 1.1.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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 ---
Version: 1.1.0-1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:33:22 +
with message-id 
and subject line Bug#966802: Removed package(s) from unstable
has caused the Debian Bug report #937959,
regarding python-ntlm: 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.)


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

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 ---
Version: 1.1.0-1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#956975: marked as done (acfax: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:31:13 +
with message-id 
and subject line Bug#966658: Removed package(s) from unstable
has caused the Debian Bug report #956975,
regarding acfax: 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.)


-- 
956975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:acfax
Version: 981011-17
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/acfax_981011-17_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

[...]
FChooser.c: In function ‘ChildrenUpdate’:
FChooser.c:502:34: warning: unused variable ‘child_idea’ [-Wunused-variable]
  502 | XtWidgetGeometry parent_idea,child_idea;
  |  ^~
FChooser.c:502:22: warning: unused variable ‘parent_idea’ [-Wunused-variable]
  502 | XtWidgetGeometry parent_idea,child_idea;
  |  ^~~
FChooser.c: In function ‘DirectoryCallback’:
FChooser.c:596:17: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  596 | int index = (int)client_data;
  | ^
FChooser.c: In function ‘UpdateLists’:
FChooser.c:855:62: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
  855 | 
XtAddCallback(menuItem,XtNcallback,DirectoryCallback,(XtPointer)i);
  |  ^
gcc -g -O2 -fno-strict-aliasing-I. -Dlinux -D__amd64__ 
-D_POSIX_C_SOURCE=199309L-D_POSIX_SOURCE 
-D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE
 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
  -DFUNCPROTO=15 
-DNARROWPROTO   -DSBL_16 -DDSP_SELECT -O2 -Wall-c -o Directory.o Directory.c
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/stdio.h:27,
 from Directory.h:29,
 from Directory.c:26:
/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"
  |   ^~~
Directory.c: In function ‘DirEntryDump’:
Directory.c:209:27: warning: format ‘%d’ expects argument of type ‘int’, but 
argument 4 has type ‘long int’ [-Wformat=]
  209 |  fprintf(fp,"%20s, Size %7d, Prot %3o\n",
  | ~~^
  |   |
  |   int
  | %7ld
gcc -g -O2 -fno-strict-aliasing-I. -Dlinux -D__amd64__ 
-D_POSIX_C_SOURCE=199309L-D_POSIX_SOURCE 
-D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE
 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
  -DFUNCPROTO=15 
-DNARROWPROTO   -DSBL_16 -DDSP_SELECT -O2 -Wall-c -o DirMgr.o DirMgr.c
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/stdlib.h:25,
 from DirMgr.c:25:
/usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  185 | # warning 

Bug#949478: marked as done (browser-plugin-freshplayer-pepperflash might be useless now)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:21:14 +
with message-id 
and subject line Bug#966474: Removed package(s) from unstable
has caused the Debian Bug report #949478,
regarding browser-plugin-freshplayer-pepperflash might be useless now
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.)


-- 
949478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: browser-plugin-freshplayer-pepperflash
Version: 0.3.9-2
Severity: serious

All major browsers (including Firefox) have dropped support for NPAPI.
--- End Message ---
--- Begin Message ---
Version: 0.3.9-2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#885265: [py3] some fixes to get chirpw running with python3, Fixes #7431

[Arturo Borrero Gonzalez]

Hi there!

I tested chirp from the upstream mercurial repository (py3 branch) today in
Debian testing bullseye, and I got it working with python3 with the attached 
patch.

I was able to download the image from a baofeng UV-5RA, modify it and the upload
it again.

Please, consider merging the attached patch. If the patch requires any mangling
please do so yourself, I'm on vacations and I don't plan to follow-up on this.

regards.
# HG changeset patch
# User Arturo Borrero Gonzalez 
# Date 1596733882 -7200
#  Thu Aug 06 19:11:22 2020 +0200
# Branch py3
# Node ID 16906193cd4089786be642ce0af684a72e29cae9
# Parent  68534f20c1418ae8e4cc09f3ff468d0375ba843a
[py3] some fixes to get chirpw running with python3, Fixes #7431

This patch contains a couple of small changes to get chirpw running with
python3.

Signed-off-by: Arturo Borrero Gonzalez 

diff -r 68534f20c141 -r 16906193cd40 chirp/drivers/uv5r.py
--- a/chirp/drivers/uv5r.py	Thu Feb 13 16:35:52 2020 -0800
+++ b/chirp/drivers/uv5r.py	Thu Aug 06 19:11:22 2020 +0200
@@ -587,7 +587,7 @@
 data += _read_block(radio, i, 0x40, False)
 
 if append_model:
-data += radio.MODEL.ljust(8)
+data += bytes(radio.MODEL.ljust(8), 'utf-8')
 
 LOG.debug("done.")
 return memmap.MemoryMapBytes(data)
diff -r 68534f20c141 -r 16906193cd40 chirp/drivers/vx6.py
--- a/chirp/drivers/vx6.py	Thu Feb 13 16:35:52 2020 -0800
+++ b/chirp/drivers/vx6.py	Thu Aug 06 19:11:22 2020 +0200
@@ -871,5 +871,5 @@
 elif setting == "password":
 newval = self._encode_chars(newval, 4)
 setattr(_settings, setting, newval)
-except Exception, e:
+except:
 raise
diff -r 68534f20c141 -r 16906193cd40 chirp/ui/mainapp.py
--- a/chirp/ui/mainapp.py	Thu Feb 13 16:35:52 2020 -0800
+++ b/chirp/ui/mainapp.py	Thu Aug 06 19:11:22 2020 +0200
@@ -1137,7 +1137,7 @@
 
 query = "http://chirp.danplanet.com/query/rb/1.0/app_direct; \
 "?loc=%s=%s=%s" % (loc, band, dist)
-print query
+print(query)
 
 # Do this in case the import process is going to take a while
 # to make sure we process events leading up to this

Bug#947288: marked as done (freshplayerplugin: FTBFS: No package 'libdrm' found)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:21:14 +
with message-id 
and subject line Bug#966474: Removed package(s) from unstable
has caused the Debian Bug report #947288,
regarding freshplayerplugin: FTBFS: No package 'libdrm' found
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.)


-- 
947288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freshplayerplugin
Version: 0.3.9-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

freshplayerplugin cannot be built in a current sid environment any more:

-- Checking for modules 
'alsa;gio-2.0;x11;xrandr;xrender;xcursor;gl;libdrm;libevent;libevent_pthreads;cairo;pango;pangocairo;pangoft2;freetype2;openssl;icu-uc'
--   No package 'libdrm' found
CMake Error at /usr/share/cmake-3.15/Modules/FindPkgConfig.cmake:458 (message):
  A required package was not found
Call Stack (most recent call first):
  /usr/share/cmake-3.15/Modules/FindPkgConfig.cmake:637 
(_pkg_check_modules_internal)
  CMakeLists.txt:45 (pkg_check_modules)


-- Configuring incomplete, errors occurred!


Andreas


freshplayerplugin_0.3.9-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.3.9-2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967956: marked as done (golang-github-unknwon-cae: CVE-2020-7668)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:19:32 +
with message-id 
and subject line Bug#966453: Removed package(s) from unstable
has caused the Debian Bug report #967956,
regarding golang-github-unknwon-cae: CVE-2020-7668
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.)


-- 
967956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-unknwon-cae
Version: 0.0~git20160715.0.c6aac99-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for golang-github-unknwon-cae.

CVE-2020-7668[0]:
| In all versions of the package github.com/unknwon/cae/tz, the
| ExtractTo function doesn't securely escape file paths in zip archives
| which include leading or non-leading "..". This allows an attacker to
| add or replace files system-wide.


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-7668
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7668

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 0.0~git20160715.0.c6aac99-4+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967955: marked as done (golang-github-unknwon-cae: CVE-2020-7664)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:19:32 +
with message-id 
and subject line Bug#966453: Removed package(s) from unstable
has caused the Debian Bug report #967955,
regarding golang-github-unknwon-cae: CVE-2020-7664
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.)


-- 
967955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-unknwon-cae
Version: 0.0~git20160715.0.c6aac99-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for golang-github-unknwon-cae.

CVE-2020-7664[0]:
| In all versions of the package github.com/unknwon/cae/zip, the
| ExtractTo function doesn't securely escape file paths in zip archives
| which include leading or non-leading "..". This allows an attacker to
| add or replace files system-wide.


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-7664
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7664
[1] https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAEZIP-570383

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 0.0~git20160715.0.c6aac99-4+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#968013: swi-prolog: time bomb in swi-prolog-test, and failing autopkgtest

[Julien Cristau]

Package: swi-prolog
Severity: serious
X-Debbugs-Cc: jcris...@debian.org

Hi,

swi-prolog autopkgtests are currently failing:
https://ci.debian.net/data/autopkgtest/testing/amd64/s/swi-prolog/6535300/log.gz

>From what I can tell, there's a step in the build process to generate
test certs, which are then shipped in the swi-prolog-test package.
Among those files is rootCA-crl.pem which is valid for 30 days, so
running the tests more than 30 days after the package was built fails.
I guess the certs should be generated as part of the test procedure
instead.

Cheers,
Julien

Bug#967232: xscreensaver: Unversioned Python removal in sid/bullseye

[Tormod Volden]

I think this is solely through the build dependency on libglade2-dev
so this will be solved by xscreensaver getting rid of this dependency
(bug #967892) or by libglade2 getting rid of its python dependency
(bug #895517):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895517#14

Processed: Bug#957587 marked as pending in ncrack

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#957587: marked as pending in ncrack

[Marcos Fouces]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/pkg-security-team/ncrack/-/commit/bb895ff9194ceaf3a9054fbd2898d731b9373eb9


Fix build with gcc-10 (Closes: #957587)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/957587

Bug#967121: marked as done (bitz-server: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:23:45 +
with message-id 
and subject line Bug#966418: Removed package(s) from unstable
has caused the Debian Bug report #967121,
regarding bitz-server: Unversioned Python 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.)


-- 
967121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bitz-server
Version: 2.0.3-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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 ---
Version: 2.0.3-1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#957043: marked as done (bitz-server: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:23:45 +
with message-id 
and subject line Bug#966418: Removed package(s) from unstable
has caused the Debian Bug report #957043,
regarding bitz-server: 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.)


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

[...]
   debian/rules override_dh_installdocs-indep
make[1]: Entering directory '/<>'
cp -r /<>/doc/doxygen/html/* 
/<>/debian/bitz-server-doc/usr/share/doc/bitz-server-doc/docs/
dh_installdocs
make[1]: Leaving directory '/<>'
   dh_installdocs -Nbitz-server-doc
   dh_installchangelogs
   dh_installman
   dh_installinit
   debian/rules override_dh_installsystemd
make[1]: Entering directory '/<>'
dh_installsystemd -pbitz-server --no-enable --name=bitz-server 
bitz-server.service
make[1]: Leaving directory '/<>'
   dh_lintian
   dh_perl
   dh_link
   dh_strip_nondeterminism
   dh_compress
   dh_fixperms
   dh_missing
   dh_strip
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/<>'
dh_makeshlibs
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libicap1/DEBIAN/symbols doesn't match 
completely debian/libicap1.symbols.amd64
--- debian/libicap1.symbols.amd64 (libicap1_2.0.3-1_amd64)
+++ dpkg-gensymbolsWrdG5i   2020-02-26 12:40:21.761012747 +
@@ -1,6 +1,6 @@
 libicap.so.1 libicap1 #MINVER#
  (regex|optional)"^_ZN?K?S" 1.0.0
- (c++)"__gnu_cxx::__normal_iterator, std::allocator > > 
std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > 
>, 
__gnu_cxx::__ops::_Iter_pred > > >(__gnu_cxx::__normal_iterator, std::allocator > 
>, __gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__ops::_Iter_pred > >, std::random_access_iterator_tag)@Base" 1.0.0
+#MISSING: 2.0.3-1# (c++)"__gnu_cxx::__normal_iterator, std::allocator > 
> std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > 
>, 
__gnu_cxx::__ops::_Iter_pred > > >(__gnu_cxx::__normal_iterator, std::allocator > 
>, __gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__ops::_Iter_pred > >, std::random_access_iterator_tag)@Base" 1.0.0
  (c++)"icap::Header::Header()@Base" 1.0.0
  (c++)"icap::Header::attach(std::__cxx11::basic_string, std::allocator >, 
std::__cxx11::basic_string, std::allocator 
>)@Base" 1.0.0
  (c++)"icap::Header::attach_encapsulated(std::__cxx11::basic_string, std::allocator >)@Base" 1.0.0
@@ -64,14 +64,14 @@
  (c++)"icap::util::send_response(icap::Response*, 
psocksxx::iosockstream*)@Base" 1.0.0
  (c++)"icap::util::split(std::__cxx11::basic_string, std::allocator > const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.0.0
  (c++)"icap::util::trim(std::__cxx11::basic_string, std::allocator >&)@Base" 1.0.0
- (c++)"std::_Rb_tree, std::allocator > 
>, std::_Select1st, std::allocator > 
> >, std::less, 
std::allocator, std::allocator > 
> > >::_M_erase(std::_Rb_tree_node, 
std::allocator > > >*)@Base" 1.0.0
+#MISSING: 2.0.3-1# (c++)"std::_Rb_tree, std::allocator > 
>, std::_Select1st, std::allocator > 
> >, std::less, 
std::allocator, std::allocator > 
> > >::_M_erase(std::_Rb_tree_node, 
std::allocator > > >*)@Base" 1.0.0
  

Bug#967178: marked as done (mrtrix: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:16:43 +
with message-id 
and subject line Bug#966326: Removed package(s) from unstable
has caused the Debian Bug report #967178,
regarding mrtrix: Unversioned Python 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.)


-- 
967178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mrtrix
Version: 0.2.13-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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 ---
Version: 0.2.13-2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Processed: tagging 966853

[Debian Bug Tracking System]

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

> tags 966853 + fixed-upstream
Bug #966853 [src:gophernicus] gophernicus: FTBFS: ld: 
file.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; 
gophernicus.o:/usr/include/tcpd.h:115: first defined here
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#966870: marked as done (nsis: FTBFS: ld: build/urelease/halibut/bk_xhtml.o:./Docs/src/bin/halibut/halibut.h:272: multiple definition of `version'; build/urelease/halibut/biblio.o:./Docs/src/bin/ha

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:04:25 +
with message-id 
and subject line Bug#966870: fixed in nsis 3.05-4
has caused the Debian Bug report #966870,
regarding nsis: FTBFS: ld: 
build/urelease/halibut/bk_xhtml.o:./Docs/src/bin/halibut/halibut.h:272: 
multiple definition of `version'; 
build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
defined here
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.)


-- 
966870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nsis
Version: 3.05-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> gcc -o build/urelease/halibut/halibut -Wl,-z,relro -Wl,-z,now 
> build/urelease/halibut/biblio.o build/urelease/halibut/bk_xhtml.o 
> build/urelease/halibut/contents.o build/urelease/halibut/error.o 
> build/urelease/halibut/help.o build/urelease/halibut/index.o 
> build/urelease/halibut/input.o build/urelease/halibut/keywords.o 
> build/urelease/halibut/licence.o build/urelease/halibut/main.o 
> build/urelease/halibut/malloc.o build/urelease/halibut/misc.o 
> build/urelease/halibut/style.o build/urelease/halibut/tree234.o 
> build/urelease/halibut/ustring.o build/urelease/halibut/version.o
> /usr/bin/ld: 
> build/urelease/halibut/bk_xhtml.o:./Docs/src/bin/halibut/halibut.h:272: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/contents.o:./Docs/src/bin/halibut/halibut.h:272: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/error.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/help.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/index.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/input.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/keywords.o:./Docs/src/bin/halibut/halibut.h:272: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/main.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/malloc.o:./Docs/src/bin/halibut/halibut.h:272: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/misc.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/style.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/ustring.o:./Docs/src/bin/halibut/halibut.h:272: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/version.o:./Docs/src/bin/halibut/version.c:19: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/nsis_3.05-3_unstable.log

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

About the 

Bug#963291: marked as done (nss-pem: FTBFS: pfind.c:279:10: error: ‘CKO_NETSCAPE_TRUST’ undeclared (first use in this function); did you mean ‘CKO_NSS_TRUST’?)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 15:50:16 +
with message-id 
and subject line Bug#963291: fixed in nss-pem 1.0.6-1
has caused the Debian Bug report #963291,
regarding nss-pem: FTBFS: pfind.c:279:10: error: ‘CKO_NETSCAPE_TRUST’ 
undeclared (first use in this function); did you mean ‘CKO_NSS_TRUST’?
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.)


-- 
963291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nss-pem
Version: 1.0.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/cc -DHAVE_LOWKEYTI_H -Dnsspem_EXPORTS -I/usr/include/nss 
> -I/usr/include/nspr  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -I../nss/dist/private/nss -fPIC   -o CMakeFiles/nsspem.dir/pinst.c.o   -c 
> /<>/src/pinst.c
> /<>/src/pfind.c: In function ‘collect_objects’:
> /<>/src/pfind.c:279:10: error: ‘CKO_NETSCAPE_TRUST’ undeclared 
> (first use in this function); did you mean ‘CKO_NSS_TRUST’?
>   279 | case CKO_NETSCAPE_TRUST:
>   |  ^~
>   |  CKO_NSS_TRUST
> /<>/src/pfind.c:279:10: note: each undeclared identifier is 
> reported only once for each function it appears in
> /<>/src/pfind.c:283:10: error: ‘CKO_NETSCAPE_CRL’ undeclared 
> (first use in this function); did you mean ‘CKO_NSS_CRL’?
>   283 | case CKO_NETSCAPE_CRL:
>   |  ^~~~
>   |  CKO_NSS_CRL
> /<>/src/pfind.c:286:10: error: ‘CKO_NETSCAPE_SMIME’ undeclared 
> (first use in this function); did you mean ‘CKO_NSS_SMIME’?
>   286 | case CKO_NETSCAPE_SMIME:
>   |  ^~
>   |  CKO_NSS_SMIME
> [ 50%] Building C object CMakeFiles/nsspem.dir/pobject.c.o
> /usr/bin/cc -DHAVE_LOWKEYTI_H -Dnsspem_EXPORTS -I/usr/include/nss 
> -I/usr/include/nspr  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -I../nss/dist/private/nss -fPIC   -o CMakeFiles/nsspem.dir/pobject.c.o   -c 
> /<>/src/pobject.c
> /<>/src/pfind.c:289:10: error: ‘CKO_NETSCAPE_BUILTIN_ROOT_LIST’ 
> undeclared (first use in this function); did you mean 
> ‘CKO_NSS_BUILTIN_ROOT_LIST’?
>   289 | case CKO_NETSCAPE_BUILTIN_ROOT_LIST:
>   |  ^~
>   |  CKO_NSS_BUILTIN_ROOT_LIST
> make[4]: *** [CMakeFiles/nsspem.dir/build.make:118: 
> CMakeFiles/nsspem.dir/pfind.c.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/nss-pem_1.0.5-1_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated nss-pem package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Aug 2020 18:35:59 +0300
Source: nss-pem
Architecture: source
Version: 1.0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 932639 963291
Changes:
 nss-pem (1.0.6-1) unstable; urgency=medium
 .
   * New upstream release.
   * control: Bump policy to 4.5.0.
   * nss: Refreshed to 3.55-1.
   * migrate-to-nss-names.diff: Migrate from NETSCAPE to NSS attributes.
 (Closes: #963291)
   * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake. Thanks,
 Helmut Grohne! (Closes: #932639)
Checksums-Sha1:
 

Processed: tagging 966171

[Debian Bug Tracking System]

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

> tags 966171 + fixed-upstream
Bug #966171 [src:ydpdict] ydpdict: FTBFS with GCC 10: multiple definition of 
... due to -fno-common
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#967953: ifupdown2

[Julien Fortin]

Hi Christoph,


On Thu, Aug 6, 2020 at 12:27 PM Christoph Egger  wrote:
>
> Hi
>
> > We are now looking for a new debian sponsor to upload our latest
> > version to the debian repository.
>
> I guess I can help there for now but better don't rely on me for long-term
> sponsoring. What exactly would you want uploaded? Do you have the package
> somewhere? or github HEAD?

It would be awesome if you could help us out with this new release
(https://packages.debian.org/sid/ifupdown2).
We want to upload ifupdown2 3.0: it adds python3 support, new features
and fixes a bunch of bugs

The package is available on github, master branch:
http://github.com/CumulusNetworks/ifupdown2/

git clone https://github.com/CumulusNetworks/ifupdown2.git -b master

git tag 3.0.0-1

ifupdown2 (3.0.0-1) unstable; urgency=medium

   * New: python3 support
   * New: attribute alias support
   * New: bridge-always-up attribute
   * New: set bridge mtu with policy default
   * New: ES bond with "es-sys-mac" attribute
   * New: vxlan attribute: vxlan-mcastgrp-map
   * New: support for "veth-peer-name" attribute
   * New: dhcp policy: dhclient_retry_on_failure
   * New: support for marking interfaces as mgmt interfaces
   * New: bridge-vlan-vni-map attribute (single vxlan device)
   * New: dhcp: skipping dhcp configuration if link-down yes
   * New: vrf-slave: keep vlan down if lower device has "link-down yes"
   * New: vxlan: support for vxlan-svcnodeip6 and vxlan-mcastgrp6 (fixes #43)
   * New: support for add ovs-ports-condone-regex attribute (openvswitch)
   * Fix: dry-run exceptions
   * Fix: bond enslavement ordering
   * Fix: process MTU before addrgen
   * Fix: set bridge MTU after bridge creation
   * Fix: ifquery-running: incorrect displayed data
   * Fix: tunnel configuration compatibility with ifupdown1
   * Fix: start-networking script is back to handle mgmt & hotplug cases
   * Fix: devices matching with ".{0,13}\-v" could get removed by ifreload
   * Fix: mstpctl: check mstpctl-stp and bridge-stp and fix bridge cache update
   * Removing python-argcomplete dependency

 -- Julien Fortin   Tue, 04 Aug 2020 23:42:42 +0200

Let me know if that's all good and can proceed with the upload.

Best regards
Julien

>
> Christoph

Bug#963737: ilias...@debian.org

[Ilias Tsitsimpis]

On Thu, Aug 06, 2020 at 11:42AM, peter green wrote:
> hi, highlighting-kate was just removed from testing at your request, but
> carettah still build-depends on it in both testing and
> unstable.
> 
> Should I go ahead and file a rc bug against carettah

Good catch. I open an RC bug against carettah (#968008).

Thanks,

-- 
Ilias

Bug#964150: marked as done (petsc: autopkgtest regression: mpiexec was unable to launch the specified application)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 22:48:53 +0800
with message-id <51821f06f2134c07a730dfc53328c...@debian.org>
and subject line Re: Bug#964150 petsc: autopkgtest regression: mpiexec was 
unable to launch the specified application
has caused the Debian Bug report #964150,
regarding petsc: autopkgtest regression: mpiexec was unable to launch the 
specified application
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.)


-- 
964150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: petsc
Version: 3.13.2+dfsg1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
petsc  from testing3.13.2+dfsg1-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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=petsc

https://ci.debian.net/data/autopkgtest/testing/amd64/p/petsc/6099581/log.gz

autopkgtest [10:18:49]: test test-petsc64: [---
Running test examples to verify correct 64-bit installation
Using PETSC_DIR=/usr/lib/petsc64
run SNES testex19
make: [/usr/lib/petsc64/lib/petsc/conf/rules:288: ex19.PETSc] Error 127
(ignored)
skip test HYPRE
test MUMPS
1,9c1,10
< lid velocity = 0.0625, prandtl # = 1., grashof # = 1.
<   0 SNES Function norm 0.239155
< 0 KSP Residual norm 0.239155
< 1 KSP Residual norm < 1.e-11
<   1 SNES Function norm 6.81968e-05
< 0 KSP Residual norm 6.81968e-05
< 1 KSP Residual norm < 1.e-11
<   2 SNES Function norm < 1.e-11
< Number of SNES iterations = 2
---
> --
> mpiexec was unable to launch the specified application as it could not
access
> or execute an executable:
>
> Executable: ./ex19
> Node: ci-184-96ecc70b
>
> while attempting to start process rank 0.
> --
> 2 total processes failed to start
/tmp/autopkgtest-lxc.wz1s0v5n/downtmp/build.ViQ/src/src/snes/tutorials
Possible problem with ex19 running with mumps, diffs above
=
run testex5f
make: [/usr/lib/petsc64/lib/petsc/conf/rules:340: ex5f.PETSc] Error 127
(ignored)
Completed test examples
src/snes/tutorials/mumps.diff:1,9c1,10
src/snes/tutorials/mumps.diff:< lid velocity = 0.0625, prandtl # = 1.,
grashof # = 1.
src/snes/tutorials/mumps.diff:<   0 SNES Function norm 0.239155
src/snes/tutorials/mumps.diff:< 0 KSP Residual norm 0.239155
src/snes/tutorials/mumps.diff:< 1 KSP Residual norm < 1.e-11
src/snes/tutorials/mumps.diff:<   1 SNES Function norm 6.81968e-05
src/snes/tutorials/mumps.diff:< 0 KSP Residual norm 6.81968e-05
src/snes/tutorials/mumps.diff:< 1 KSP Residual norm < 1.e-11
src/snes/tutorials/mumps.diff:<   2 SNES Function norm < 1.e-11
src/snes/tutorials/mumps.diff:< Number of SNES iterations = 2
src/snes/tutorials/mumps.diff:---
src/snes/tutorials/mumps.diff:>
--
src/snes/tutorials/mumps.diff:> mpiexec was unable to launch the
specified application as it could not access
src/snes/tutorials/mumps.diff:> or execute an executable:
src/snes/tutorials/mumps.diff:>
src/snes/tutorials/mumps.diff:> Executable: ./ex19
src/snes/tutorials/mumps.diff:> Node: ci-184-96ecc70b
src/snes/tutorials/mumps.diff:>
src/snes/tutorials/mumps.diff:> while attempting to start process rank 0.
src/snes/tutorials/mumps.diff:>
--
src/snes/tutorials/mumps.diff:> 2 total processes failed to start
src/snes/tutorials/mumps.diff:/tmp/autopkgtest-lxc.wz1s0v5n/downtmp/build.ViQ/src/src/snes/tutorials
src/snes/tutorials/mumps.diff:Possible problem with ex19 running with
mumps, diffs above
src/snes/tutorials/mumps.diff:=
Tests failed
autopkgtest [10:18:49]: test test-petsc64: 

Bug#968008: carettah: Removal notice: unmaintained

[Ilias Tsitsimpis]

Package: carettah
Version: 0.5.1-2
Severity: grave
Justification: renders package unusable

This package appears to be unmaintained (last upstream upload in 2016).
It depends on deprecated software (gtk2 #967282 and highlighting-kate
#963737), is not part of Stackage and has no rev dependencies.

Unless someone fixes the above, I intend to remove it from Debian.

-- 
Ilias

Bug#957463: marked as done (libosmo-sccp: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 14:48:59 +
with message-id 
and subject line Bug#957463: fixed in libosmo-sccp 0.10.0-5
has caused the Debian Bug report #957463,
regarding libosmo-sccp: 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.)


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

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

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

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

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

  apt-get -t=experimental install g++ 

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

[...]
libtool: compile:  gcc -DPACKAGE_NAME=\"libosmo-sccp\" 
-DPACKAGE_TARNAME=\"libosmo-sccp\" -DPACKAGE_VERSION=\"0.10.0\" 
"-DPACKAGE_STRING=\"libosmo-sccp 0.10.0\"" 
-DPACKAGE_BUGREPORT=\"open...@lists.osmocom.org\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"libosmo-sccp\" -DVERSION=\"0.10.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBSCTP=1 -I. 
-I../include -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wall -I/usr/include/ 
-I/usr/include/ -I/usr/include/ -I/usr/include/ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -c sccp_user.c -o sccp_user.o >/dev/null 2>&1
libtool: compile:  gcc -DPACKAGE_NAME=\"libosmo-sccp\" 
-DPACKAGE_TARNAME=\"libosmo-sccp\" -DPACKAGE_VERSION=\"0.10.0\" 
"-DPACKAGE_STRING=\"libosmo-sccp 0.10.0\"" 
-DPACKAGE_BUGREPORT=\"open...@lists.osmocom.org\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"libosmo-sccp\" -DVERSION=\"0.10.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBSCTP=1 -I. 
-I../include -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wall -I/usr/include/ 
-I/usr/include/ -I/usr/include/ -I/usr/include/ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -c sccp_scoc.c -o sccp_scoc.o >/dev/null 2>&1
libtool: compile:  gcc -DPACKAGE_NAME=\"libosmo-sccp\" 
-DPACKAGE_TARNAME=\"libosmo-sccp\" -DPACKAGE_VERSION=\"0.10.0\" 
"-DPACKAGE_STRING=\"libosmo-sccp 0.10.0\"" 
-DPACKAGE_BUGREPORT=\"open...@lists.osmocom.org\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"libosmo-sccp\" -DVERSION=\"0.10.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBSCTP=1 -I. 
-I../include -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wall -I/usr/include/ 
-I/usr/include/ -I/usr/include/ -I/usr/include/ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -c xua_rkm.c -o xua_rkm.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CC   --mode=compile gcc 
-DPACKAGE_NAME=\"libosmo-sccp\" -DPACKAGE_TARNAME=\"libosmo-sccp\" 
-DPACKAGE_VERSION=\"0.10.0\" -DPACKAGE_STRING=\"libosmo-sccp\ 0.10.0\" 
-DPACKAGE_BUGREPORT=\"open...@lists.osmocom.org\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"libosmo-sccp\" -DVERSION=\"0.10.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 

Bug#957818: marked as done (smstools: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 14:40:28 +
with message-id 
and subject line Bug#957818: fixed in smstools 3.1.21-4
has caused the Debian Bug report #957818,
regarding smstools: 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.)


-- 
957818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:smstools
Version: 3.1.21-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/smstools_3.1.21-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: charshift.o:./smsd_cfg.h:340: multiple definition of `shell'; 
/tmp/ccYmxK2M.o:./smsd_cfg.h:340: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:339: multiple definition of 
`ic_purge_interval'; /tmp/ccYmxK2M.o:./smsd_cfg.h:339: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:338: multiple definition of 
`ic_purge_read'; /tmp/ccYmxK2M.o:./smsd_cfg.h:338: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:337: multiple definition of 
`ic_purge_minutes'; /tmp/ccYmxK2M.o:./smsd_cfg.h:337: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:336: multiple definition of 
`ic_purge_hours'; /tmp/ccYmxK2M.o:./smsd_cfg.h:336: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:335: multiple definition of 
`priviledged_numbers'; /tmp/ccYmxK2M.o:./smsd_cfg.h:335: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:334: multiple definition of 
`keep_messages'; /tmp/ccYmxK2M.o:./smsd_cfg.h:334: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:333: multiple definition of 
`executable_check'; /tmp/ccYmxK2M.o:./smsd_cfg.h:333: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:332: multiple definition of 
`log_single_lines'; /tmp/ccYmxK2M.o:./smsd_cfg.h:332: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:331: multiple definition of 
`log_charconv'; /tmp/ccYmxK2M.o:./smsd_cfg.h:331: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:330: multiple definition of 
`outgoing_utf8'; /tmp/ccYmxK2M.o:./smsd_cfg.h:330: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:329: multiple definition of 
`incoming_utf8'; /tmp/ccYmxK2M.o:./smsd_cfg.h:329: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:328: multiple definition of 
`filename_preview'; /tmp/ccYmxK2M.o:./smsd_cfg.h:328: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:327: multiple definition of `admin_to'; 
/tmp/ccYmxK2M.o:./smsd_cfg.h:327: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:326: multiple definition of 
`regular_run_interval'; /tmp/ccYmxK2M.o:./smsd_cfg.h:326: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:325: multiple definition of 
`regular_run'; /tmp/ccYmxK2M.o:./smsd_cfg.h:325: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:324: multiple definition of 
`date_filename'; /tmp/ccYmxK2M.o:./smsd_cfg.h:324: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:322: multiple definition of 
`store_original_filename'; /tmp/ccYmxK2M.o:./smsd_cfg.h:322: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:321: multiple definition of 
`keep_filename'; /tmp/ccYmxK2M.o:./smsd_cfg.h:321: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:320: multiple definition of 
`internal_combine_binary'; /tmp/ccYmxK2M.o:./smsd_cfg.h:320: first defined here
/usr/bin/ld: charshift.o:./smsd_cfg.h:319: multiple definition of 
`internal_combine'; /tmp/ccYmxK2M.o:./smsd_cfg.h:319: first defined here

Bug#957074: cdrkit: ftbfs with GCC-10

[Sebastien Bacher]

Fedora has a patch for gcc-10

https://src.fedoraproject.org/rpms/cdrkit/blob/master/f/cdrkit-1.1.11-gcc10.patch

Bug#963396: jimfs: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project jimfs: Compilation failure

[Thorsten Glaser]

On Thu, 6 Aug 2020, Andreas Tille wrote:

> [ERROR] 
> /build/jimfs-1.1/jimfs/src/main/java/com/google/common/jimfs/PathService.java:[290,30]
>  error:  is not abstract and 
> does not override abstract method test(Object) in Predicate

Change apply to test in line 292 (or let the IDE convert it to lambda).

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#966938: marked as done (ruby-devise: FTBFS: build-dependency not installable: ruby-bson-ext)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 13:22:18 +
with message-id 
and subject line Bug#966938: fixed in ruby-devise 4.7.1-3
has caused the Debian Bug report #966938,
regarding ruby-devise: FTBFS: build-dependency not installable: ruby-bson-ext
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.)


-- 
966938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-devise
Version: 4.7.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), gem2deb, ruby-bcrypt (>= 
> 3.0.1), ruby-bson-ext, ruby-omniauth-openid, ruby-orm-adapter (>= 0.5.0), 
> ruby-railties (>= 2:3.2.6), ruby-responders, ruby-thor, ruby-thread-safe, 
> ruby-warden (>= 1.2.1), build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), gem2deb, ruby-bcrypt (>= 
> 3.0.1), ruby-bson-ext, ruby-omniauth-openid, ruby-orm-adapter (>= 0.5.0), 
> ruby-railties (>= 2:3.2.6), ruby-responders, ruby-thor, ruby-thread-safe, 
> ruby-warden (>= 1.2.1), build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [470 B]
> Get:5 copy:/<>/apt_archive ./ Packages [552 B]
> Fetched 1979 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: ruby-bson-ext but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/ruby-devise_4.7.1-2_unstable.log

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Aug 2020 18:23:42 +0530
Source: ruby-devise
Architecture: source
Version: 4.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Closes: 966938
Changes:
 ruby-devise (4.7.1-3) unstable; urgency=medium
 .
   * Drop unnecessary build dependencies (Closes: #966938)
Checksums-Sha1:
 0129dbcb5b9433da71f07637ea06cc8912dc7454 2193 ruby-devise_4.7.1-3.dsc
 3992c393cd2c6a89916e132f6e37147a72a521a3 3940 

Bug#967965: marked as done (astropy: FTBFS with scipy 1.5: [doctest] astropy.stats.funcs.binom_conf_interval failed)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 13:03:29 +
with message-id 
and subject line Bug#967965: fixed in astropy 4.0.1+post1-4
has caused the Debian Bug report #967965,
regarding astropy: FTBFS with scipy 1.5: [doctest] 
astropy.stats.funcs.binom_conf_interval failed
to be marked as done.

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

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


-- 
967965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astropy
Version: 4.0.1+post1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: found -1 4.1~rc1-2

Hi,

astropy recently started to FTBFS in sid (and experimental, but not yet
in bullseye). I could reproduce the failure in bullseye with python3-scipy/sid:

=== FAILURES ===
__ [doctest] astropy.stats.funcs.binom_conf_interval ___
631 
632 Integer inputs return an array with shape (2,):
633 
634 >>> binom_conf_interval(4, 5, interval='wilson')
635 array([0.57921724, 0.92078259])
636 
637 Arrays of arbitrary dimension are supported. The Wilson and Jeffreys
638 intervals give similar results, even for small k, N:
639 
640 >>> binom_conf_interval([0, 1, 2, 5], 5, interval='wilson')
Expected:
array([[0., 0.07921741, 0.21597328, 0.8304],
   [0.1696, 0.42078276, 0.61736012, 1.]])
Got:
array([[1.38777878e-17, 7.92174125e-02, 2.15973276e-01, 8.3042e-01],
   [1.6958e-01, 4.20782762e-01, 6.17360116e-01, 1.e+00]])

/build/astropy-4.0.1+post1/.pybuild/cpython3_3.8/build/astropy/stats/funcs.py:640:
 DocTestFailure
= 1 failed, 13907 passed, 412 skipped, 49 xfailed, 12 xpassed in 169.79 seconds 
=


Andreas


astropy_bullseye+scipy_sid.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: astropy
Source-Version: 4.0.1+post1-4
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated astropy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Aug 2020 14:30:26 +0200
Source: astropy
Architecture: source
Version: 4.0.1+post1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Ole Streicher 
Closes: 967965
Changes:
 astropy (4.0.1+post1-4) unstable; urgency=medium
 .
   * Fix stats doctest failures due to upstream changes. (Closes: #967965)
Checksums-Sha1:
 61386e0ce25c372c330bb9e81f4ae4c8c3c2f293 2845 astropy_4.0.1+post1-4.dsc
 fb8ac617ee2f2ec4bb5bb1d2bd1318cbfba7ea41 29176 
astropy_4.0.1+post1-4.debian.tar.xz
Checksums-Sha256:
 c12ed410bc39671861fc5386ad69f5ae878d80f4a962c1234d8733053f43ba84 2845 
astropy_4.0.1+post1-4.dsc
 4fd51c528a0b8bca268ecc013564ce6fa7437fb3b56487a34f54caba67ef25d5 29176 
astropy_4.0.1+post1-4.debian.tar.xz
Files:
 71328a9ba93cab80811ab41b3336d789 2845 python optional astropy_4.0.1+post1-4.dsc
 13a6f5e6abc8a6c140f95bffa3b683c0 29176 python optional 
astropy_4.0.1+post1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAl8r+5sACgkQmk9WvbkO
GL0GQA//YgqgVPdV0tuVO5uJa/myuhwDpxeQHYytPyoAnKRlcmxKFoaSev8BIbaQ
phONbTMKM2g8EV52WNwc7y2Hr9uJxzVaYHXeRwyv3eip+M1ETFDT1ngbNZYV2ORP
Z4Pop05RJXnR6fuvxak1Tg/rJnYC3AnUUFeV7umc77phP3YirmOobDF9fyJM8mE+
6ZMCqT+cGE4SVuPavIH/q54OpSNuhFHy248tVtccD8iesY+UE63m9wavVqPwoP4B
AVivpdHxEPB+biMKO0a5Us0q/LdC6oOy7XnB4LAG8nS7Zq3qGE1LWpOMpCar2Lw9
DSzMHTVQHKqCLb57KKoGtYle8+4DC48TmjFI/tZPwcFO/9gyGJBkLPqF/2aE5Td2
6P0AHfLtrj7R5M1WjEGhxTOyhXOZ/HqhQq/nYDd5LPdV72RjZv6/e/ZLJjbY6sgm
CG+EtX8+wwzv8cjq7AoAgItZc7erapBt4/HWaeE2HM99LiOQxPxlPbLxIhtcLqeJ
Uxxip8YOnGSyMee8lBEo+6dx7Eh9CBMLNgIUfMvKBF7DXSHX42Z47SltAi00jh8u
WxCISPFsTio9PyDZhLPRvMOqGDkNabAio1DNHW+DRv8AVfS0+NC0fXc764cAyrQ6
UsxqyRf7i7QDcUkNOo0fVATdG/e+4pEWRkDiOkGHYKXSkuGSovs=
=PV+B
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#967991: glirc, build-depends on package which is not in testing

[Debian Bug Tracking System]

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

> notfound 967991 2.35-1
Bug #967991 [glirc] glirc, build-depends on package which is not in testing
No longer marked as found in versions glirc/2.35-1.
> found 967991 2.32-1
Bug #967991 [glirc] glirc, build-depends on package which is not in testing
Marked as found in versions glirc/2.32-1.
> close 967991 2.35-1
Bug #967991 [glirc] glirc, build-depends on package which is not in testing
Marked as fixed in versions glirc/2.35-1.
Bug #967991 [glirc] glirc, build-depends on package which is not in testing
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#967991: glirc, build-depends on package which is not in testing

[peter green]

notfound 967991 2.35-1
found 967991 2.32-1
close 967991 2.35-1
thanks

On 06/08/2020 13:20, Clint Adams wrote:

On Thu, Aug 06, 2020 at 11:20:00AM +0100, peter green wrote:

glirc can no longer be built in testing because haskell-regex-tdfa is no longer
present in testing. Ilias Tsitsimpis has filed a bug report against the package
saying he intends to remove it and asked the release team to remove it from
testing ( https://lists.debian.org/debian-haskell/2020/08/msg2.html ) .
which the release team did.


That list appears to have haskell-regex-tdfa-text, not haskell-regex-tdfa?


Apologies, I clearly mixed up haskell-regex-tdfa and haskell-regex-tdfa-text
it seems I also missed that there were different versions of glirc
in testing and unstable.

It seems that testing's version of glirc build-depends on binary package's
built from haskell-regex-tdfa-text, but unstable's version does not.

Updating the bug metadata accordingly

Bug#936146: archivemail - Python 3 porting

[Martin Steigerwald]

Hi!

I used this frequently enough to be hesitant to let apt dist-upgrade 
remove it on my system currently.

But I understand it may not make sense to port it as its hard and 
upstream is not active anymore.

Is there an alternative in Debian repository?

Best,
-- 
Martin

Processed: Bug#966938 marked as pending in ruby-devise

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #966938 [src:ruby-devise] ruby-devise: FTBFS: build-dependency not 
installable: ruby-bson-ext
Added tag(s) pending.

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

Bug#966938: marked as pending in ruby-devise

[Praveen Arimbrathodiyil]

Control: tag -1 pending

Hello,

Bug #966938 in ruby-devise 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/ruby-team/ruby-devise/-/commit/676e61cc919d115ec8844769b97ffdae78162193


Drop unnecessary build dependencies (Closes: #966938)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/966938

Bug#957032: marked as done (ayatana-indicator-printers: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 12:48:31 +
with message-id 
and subject line Bug#957032: fixed in ayatana-indicator-printers 0.1.10-1
has caused the Debian Bug report #957032,
regarding ayatana-indicator-printers: 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.)


-- 
957032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ayatana-indicator-printers
Version: 0.1.9-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/ayatana-indicator-printers_0.1.9-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

[...]
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-3.0/gdk/gdkapplaunchcontext.h:28,
 from /usr/include/gtk-3.0/gdk/gdk.h:32,
 from /usr/include/gtk-3.0/gtk/gtk.h:30,
 from 
/usr/include/libayatana-indicator3-0.4/libayatana-indicator/indicator-object.h:27,
 from indicator-printers.h:22,
 from indicator-printers.c:21:
/usr/include/glib-2.0/gobject/gtype.h:1308:10: note: declared here
 1308 | void g_type_class_add_private   (gpointer
g_class,
  |  ^~~~
indicator-printers.c: In function ‘indicator_printers_init’:
indicator-printers.c:275:13: warning: G_ADD_PRIVATE
  275 | IndicatorPrintersPrivate);
  | ^  
indicator-menu-item.c: In function ‘gtk_widget_get_font_size’:
indicator-menu-item.c:54:5: warning: ‘gtk_style_context_get_font’ is 
deprecated: Use 'gtk_style_context_get' instead [-Wdeprecated-declarations]
   54 | font = gtk_style_context_get_font (gtk_widget_get_style_context 
(widget),
  | ^~~~
In file included from /usr/include/gtk-3.0/gtk/gtkicontheme.h:27,
 from /usr/include/gtk-3.0/gtk/gtk.h:127,
 from indicator-menu-item.h:22,
 from indicator-menu-item.c:19:
/usr/include/gtk-3.0/gtk/gtkstylecontext.h:1211:6: note: declared here
 1211 |  gtk_style_context_get_font (GtkStyleContext *context,
  |  ^~
indicator-menu-item.c: In function ‘indicator_menu_item_class_init’:
indicator-menu-item.c:219:5: warning: ‘g_type_class_add_private’ is deprecated 
[-Wdeprecated-declarations]
  219 | g_type_class_add_private (klass, sizeof (IndicatorMenuItemPrivate));
  | ^~~~
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-3.0/gdk/gdkapplaunchcontext.h:28,
 from /usr/include/gtk-3.0/gdk/gdk.h:32,
 from /usr/include/gtk-3.0/gtk/gtk.h:30,
 from indicator-menu-item.h:22,
 from 

Processed: Bug#967965 marked as pending in astropy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #967965 [src:astropy] astropy: FTBFS with scipy 1.5: [doctest] 
astropy.stats.funcs.binom_conf_interval failed
Added tag(s) pending.

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

Bug#967965: marked as pending in astropy

[Ole Streicher]

Control: tag -1 pending

Hello,

Bug #967965 in astropy 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/debian-astro-team/astropy/-/commit/d4c28b296760a332d2236b840d4ba5f443121c73


Fix stats doctest failures due to upstream changes.

Closes: #967965


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/967965

Bug#957555: marked as done (mocassin: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 12:35:14 +
with message-id 
and subject line Bug#957555: fixed in mocassin 2.02.73-3
has caused the Debian Bug report #957555,
regarding mocassin: 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.)


-- 
957555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mocassin
Version: 2.02.73-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/mocassin_2.02.73-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

[...]
f951: Warning: Nonexistent include directory ‘/usr/include/mpich’ 
[-Wmissing-include-dirs]
source/iteration_mod.f90:313:36:

  143 |  call mpi_allreduce(grid(iG)%opacity, opacityTemp, 
size, &
  |2
..
  313 |  call mpi_allreduce(BjumpTemp, Bjump, 1, mpi_real&
  |1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) 
(rank-1 and scalar)
source/iteration_mod.f90:441:36:

  143 |  call mpi_allreduce(grid(iG)%opacity, opacityTemp, 
size, &
  |2
..
  441 |  call mpi_allreduce(grid(iG)%resLinePackets, 
resLinePacketsTemp, size, &
  |1
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(4)/REAL(4)).
source/iteration_mod.f90:563:33:

  143 |  call mpi_allreduce(grid(iG)%opacity, opacityTemp, 
size, &
  |2
..
  563 |   call mpi_allreduce(planeIonDistribution, 
planeIonDistributionTemp, size, &
  | 1
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(INTEGER(4)/REAL(4)).
source/iteration_mod.f90:847:33:

  143 |  call mpi_allreduce(grid(iG)%opacity, opacityTemp, 
size, &
  |2
..
  847 |   call mpi_allreduce(grid(iG)%noHit, noHitPercent(iG), 
size, &
  | 1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) 
(rank-1 and scalar)
source/iteration_mod.f90:851:36:

  143 |  call mpi_allreduce(grid(iG)%opacity, opacityTemp, 
size, &
  |2
..
  851 |  call mpi_allreduce(grid(iG)%noIonBal, 
noIonBalPercent(iG), size, &
  |1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) 
(rank-1 and scalar)
source/iteration_mod.f90:854:36:

  143 |  call mpi_allreduce(grid(iG)%opacity, opacityTemp, 
size, &
  |2
..
  854 |  call mpi_allreduce(grid(iG)%noTeBal, 
noTeBalPercent(iG), size, &
  |1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) 
(rank-1 and scalar)
source/iteration_mod.f90:860:33:

  143 |  call mpi_allreduce(grid(iG)%opacity, opacityTemp, 
size, &
  |2
..
  860 |   call mpi_allreduce(grid(iG)%lgConverged, lgConvergedTemp, 
size, &
  | 1
Error: Type mismatch between actual argument at (1) and actual argument at (2) 

Bug#957379: debdiff with the fix for Unstable

[Leonidas S. Barbosa]

Please test it.
diff -Nru isc-dhcp-4.4.1/debian/changelog isc-dhcp-4.4.1/debian/changelog
--- isc-dhcp-4.4.1/debian/changelog	2020-01-22 18:35:14.0 -0300
+++ isc-dhcp-4.4.1/debian/changelog	2020-08-05 23:08:47.0 -0300
@@ -1,3 +1,12 @@
+isc-dhcp (4.4.1-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS due gcc 10 compilation issues in client/dhclient.c,
+common/discover.c, relay/dhcrelay.c, server/mdb.c, server/mdb6.c
+(closes: 957379).
+
+ -- Leonidas S. Barbosa   Wed, 05 Aug 2020 23:08:47 -0300
+
 isc-dhcp (4.4.1-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru isc-dhcp-4.4.1/debian/patches/Fixed_gcc_10_compilation_issues.patch isc-dhcp-4.4.1/debian/patches/Fixed_gcc_10_compilation_issues.patch
--- isc-dhcp-4.4.1/debian/patches/Fixed_gcc_10_compilation_issues.patch	1969-12-31 21:00:00.0 -0300
+++ isc-dhcp-4.4.1/debian/patches/Fixed_gcc_10_compilation_issues.patch	2020-08-05 23:08:34.0 -0300
@@ -0,0 +1,99 @@
+From 129b7e402bd6e7278854e5a8935fce460552b5f4 Mon Sep 17 00:00:00 2001
+From: Thomas Markwalder 
+Date: Thu, 30 Jul 2020 10:01:36 -0400
+Subject: [PATCH] [#117] Fixed gcc 10 compilation issues
+
+client/dhclient.c
+relay/dhcrelay.c
+extern'ed local_port,remote_port
+
+common/discover.c
+init local_port,remote_port to 0
+
+server/mdb.c
+extern'ed dhcp_type_host
+
+server/mdb6.c
+create_prefix6() - eliminated memcpy string overflow error
+---
+ RELNOTES  | 5 +
+ client/dhclient.c | 5 +++--
+ common/discover.c | 4 ++--
+ relay/dhcrelay.c  | 4 ++--
+ server/mdb.c  | 2 +-
+ server/mdb6.c | 2 +-
+ 6 files changed, 14 insertions(+), 8 deletions(-)
+
+#diff --git a/RELNOTES b/RELNOTES
+#index 9d0a0414..6919dba7 100644
+#--- a/RELNOTES
+#+++ b/RELNOTES
+#@@ -103,6 +103,11 @@ ISC DHCP is open source software maintained by Internet Systems
+# Consortium.  This product includes cryptographic software written
+# by Eric Young (e...@cryptsoft.com).
+# 
+#+		Changes since 4.4.2 (Bug Fixes)
+#+
+#+- Minor corrections to allow compilation under gcc 10.
+#+  [Gitlab #117]
+#+
+# 		Changes since 4.4.2b1 (Bug Fixes)
+# 
+# - Added a clarification on DHCPINFORMs and server authority to
+Index: isc-dhcp-4.4.1/client/dhclient.c
+===
+--- isc-dhcp-4.4.1.orig/client/dhclient.c
 isc-dhcp-4.4.1/client/dhclient.c
+@@ -81,8 +81,9 @@ static const char message [] = "Internet
+ static const char url [] = "For info, please visit https://www.isc.org/software/dhcp/;;
+ #endif /* UNIT_TEST */
+ 
+-u_int16_t local_port = 0;
+-u_int16_t remote_port = 0;
++extern u_int16_t local_port;
++extern u_int16_t remote_port;
++
+ #if defined(DHCPv6) && defined(DHCP4o6)
+ int dhcp4o6_state = -1; /* -1 = stopped, 0 = polling, 1 = started */
+ #endif
+Index: isc-dhcp-4.4.1/relay/dhcrelay.c
+===
+--- isc-dhcp-4.4.1.orig/relay/dhcrelay.c
 isc-dhcp-4.4.1/relay/dhcrelay.c
+@@ -95,8 +95,8 @@ enum { forward_and_append,	/* Forward an
+forward_untouched,	/* Forward without changes. */
+discard } agent_relay_mode = forward_and_replace;
+ 
+-u_int16_t local_port;
+-u_int16_t remote_port;
++extern u_int16_t local_port;
++extern u_int16_t remote_port;
+ 
+ /* Relay agent server list. */
+ struct server_list {
+Index: isc-dhcp-4.4.1/server/mdb.c
+===
+--- isc-dhcp-4.4.1.orig/server/mdb.c
 isc-dhcp-4.4.1/server/mdb.c
+@@ -67,7 +67,7 @@ static host_id_info_t *host_id_info = NU
+ 
+ int numclasseswritten;
+ 
+-omapi_object_type_t *dhcp_type_host;
++extern omapi_object_type_t *dhcp_type_host;
+ 
+ isc_result_t enter_class(cd, dynamicp, commit)
+ 	struct class *cd;
+Index: isc-dhcp-4.4.1/server/mdb6.c
+===
+--- isc-dhcp-4.4.1.orig/server/mdb6.c
 isc-dhcp-4.4.1/server/mdb6.c
+@@ -1943,7 +1943,7 @@ create_prefix6(struct ipv6_pool *pool, s
+ 		}
+ 		new_ds.data = new_ds.buffer->data;
+ 		memcpy(new_ds.buffer->data, ds.data, ds.len);
+-		memcpy(new_ds.buffer->data + ds.len, , sizeof(tmp));
++		memcpy(_ds.buffer->data[0] + ds.len, , sizeof(tmp));
+ 		data_string_forget(, MDL);
+ 		data_string_copy(, _ds, MDL);
+ 		data_string_forget(_ds, MDL);
diff -Nru isc-dhcp-4.4.1/debian/patches/series isc-dhcp-4.4.1/debian/patches/series
--- isc-dhcp-4.4.1/debian/patches/series	2020-01-22 18:35:14.0 -0300
+++ isc-dhcp-4.4.1/debian/patches/series	2020-08-05 23:08:47.0 -0300
@@ -16,3 +16,4 @@
 bind-includes.patch
 
 configure.patch
+Fixed_gcc_10_compilation_issues.patch


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

Bug#967999: ruby-data-migrate: ftbfs and autopkgtest failure with rails 6

[Pirate Praveen]

Package: ruby-data-migrate
Version: 5.3.1-1
Severity: serious
User: pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: rails6-transition


Hi,

This package's autopkgtest and rebuilds failed with rails 6. There is 
new upstream version which fixes this issue.


Relevant errors,

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

RUBYLIB=/<>/debian/ruby-data-migrate/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=/<>/debian/ruby-data-migrate/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 
ruby2.7 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.7 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib 
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
--pattern ./spec/\*\*/\*_spec.rb --format documentation


An error occurred while loading ./spec/data_migrate/config_spec.rb.
Failure/Error:
   class Migration < ::ActiveRecord::Migration

 class << self
   def check_pending!(connection = ::ActiveRecord::Base.connection)
 raise ActiveRecord::PendingMigrationError if 
DataMigrator::Migrator.needs_migration?(connection)

   end

   def migrate(direction)
 new.migrate direction
   end

StandardError:
 Directly inheriting from ActiveRecord::Migration is not supported. 
Please specify the Rails release the migration was written for:


   class DataMigrate::Migration < ActiveRecord::Migration[4.2]
# 
/usr/share/rubygems-integration/all/gems/activerecord-6.0.3.1/lib/active_record/migration.rb:536:in 
`inherited'

# ./lib/data_migrate/migration.rb:2:in `'
# ./lib/data_migrate/migration.rb:1:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in 
`block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:291:in 
`load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in 
`require'

# ./lib/data_migrate.rb:27:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in 
`block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:291:in 
`load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in 
`require'

# ./spec/spec_helper.rb:3:in `'
# ./spec/data_migrate/config_spec.rb:1:in `'

Finished in 0.9 seconds (files took 5.76 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

/usr/bin/ruby2.7 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib 
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
--pattern ./spec/\*\*/\*_spec.rb --format documentation failed


Full log 
https://people.debian.org/~praveen/rails6-meta-build/buildlogs/ruby-data-migrate.log

Bug#967991: glirc, build-depends on package which is not in testing

[Clint Adams]

On Thu, Aug 06, 2020 at 11:20:00AM +0100, peter green wrote:
> glirc can no longer be built in testing because haskell-regex-tdfa is no 
> longer
> present in testing. Ilias Tsitsimpis has filed a bug report against the 
> package
> saying he intends to remove it and asked the release team to remove it from
> testing ( https://lists.debian.org/debian-haskell/2020/08/msg2.html ) .
> which the release team did.

That list appears to have haskell-regex-tdfa-text, not haskell-regex-tdfa?

Bug#966972: [in-toto-dev] Bug#966972: in-toto: FTBFS: ValueError: SSH supports only 1024 bit DSA keys

[Holger Levsen]

hey Lukas,

On Thu, Aug 06, 2020 at 02:03:00PM +0200, Lukas Puehringer wrote:
> FYI: https://github.com/secure-systems-lab/securesystemslib/pull/264 fixes the
> issue upstream.

nice. once it's released we should get this new version into unstable!


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

"... the premise [is] that privacy is about hiding a wrong. It's not.
 Privacy is an inherent human right, and a requirement for maintaining
 the human condition with dignity and respect." (Bruce Schneier)


signature.asc
Description: PGP signature

Bug#966972: [in-toto-dev] Bug#966972: in-toto: FTBFS: ValueError: SSH supports only 1024 bit DSA keys

[Lukas Puehringer]

FYI: https://github.com/secure-systems-lab/securesystemslib/pull/264 fixes the
issue upstream.

On 04.08.2020 3:11 PM, Lukas Puehringer wrote:
> Thanks for the report!
> 
> It looks like a recent update to pyca/cryptography v3.0 causes our test code
> (only) to break. I just filed an issue upstream, because I am not fully sure 
> if
> the change was made intentionally:
> https://github.com/pyca/cryptography/issues/5373
> 
> If it was, I will update our test code.
> 
> Cheers,
> Lukas
> 
> On 03.08.2020 10:32 AM, Lucas Nussbaum wrote:
>> Source: in-toto
>> Version: 0.4.0-2
>> Severity: serious
>> Justification: FTBFS on amd64
>> Tags: bullseye sid ftbfs
>> Usertags: ftbfs-20200802 ftbfs-bullseye
>>
>> Hi,
>>
>> During a rebuild of all packages in sid, your package failed to build
>> on amd64.
>>
>> Relevant part (hopefully):
>>> make[1]: Entering directory '/<>'
>>> python3 tests/runtests.py
>>> gpg (GnuPG) 2.2.20
>>> libgcrypt 1.8.6
>>> Copyright (C) 2020 Free Software Foundation, Inc.
>>> License GPLv3+: GNU GPL version 3 or later 
>>> >>  >
>>> This is free software: you are free to change and redistribute it.
>>> There is NO WARRANTY, to the extent permitted by law.
>>>
>>> Home: /sbuild-nonexistent/.gnupg
>>> Supported algorithms:
>>> Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
>>> Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
>>> CAMELLIA128, CAMELLIA192, CAMELLIA256
>>> Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
>>> Compression: Uncompressed, ZIP, ZLIB, BZIP2
>>> /<>/in_toto/gpg/functions.py:101: SyntaxWarning: "is not" with 
>>> a literal. Did you mean "!="?
>>>   if process.returncode is not 0:
>>> test_load_repr_string_as_json (tests.models.test_common.TestSignable)
>>> Test load string returned by `Signable.repr` as JSON ... ok
>>> test_set_run_from_string 
>>> (tests.models.test_inspection.TestInspectionValidator)
>>> Test shelx parse command string to list. ... ok
>>> test_wrong_run (tests.models.test_inspection.TestInspectionValidator)
>>> Test that the run validators catch malformed values. ... ok
>>> test_wrong_type (tests.models.test_inspection.TestInspectionValidator)
>>> Test the type field within Validate(). ... ok
>>> test_functionary_keys (tests.models.test_layout.TestLayoutMethods)
>>> Test adding and listing functionary keys (securesystemslib and gpg). ... ok
>>> test_get_inspection_by_name (tests.models.test_layout.TestLayoutMethods)
>>> Test getting inspection by name. ... ok
>>> test_get_inspection_name_list (tests.models.test_layout.TestLayoutMethods)
>>> Test getting list of inspection names. ... ok
>>> test_get_step_by_name (tests.models.test_layout.TestLayoutMethods)
>>> Test getting step by name. ... ok
>>> test_get_step_name_list (tests.models.test_layout.TestLayoutMethods)
>>> Test getting list of step names. ... ok
>>> test_remove_inspection_by_name (tests.models.test_layout.TestLayoutMethods)
>>> Test removing inspection by name. ... ok
>>> test_remove_step_by_name (tests.models.test_layout.TestLayoutMethods)
>>> Test removing step by name. ... ok
>>> test_set_relative_expiration (tests.models.test_layout.TestLayoutMethods)
>>> Test adding expiration date relative from today. ... ok
>>> test_import_step_metadata_wrong_type 
>>> (tests.models.test_layout.TestLayoutValidator) ... ok
>>> test_repeated_step_names (tests.models.test_layout.TestLayoutValidator)
>>> Check that only unique names exist in the steps and inspect lists ... ok
>>> test_validate_readme_field (tests.models.test_layout.TestLayoutValidator)
>>> Tests the readme field data type validator. ... ok
>>> test_wrong_expires (tests.models.test_layout.TestLayoutValidator)
>>> Test the expires field is properly populated. ... ok
>>> test_wrong_inspect_list (tests.models.test_layout.TestLayoutValidator)
>>> Check that the validate method checks the inspections' correctness. ... ok
>>> test_wrong_key_dictionary (tests.models.test_layout.TestLayoutValidator)
>>> Test that the keys dictionary is properly populated. ... ok
>>> test_wrong_pubkeys (tests.models.test_layout.TestLayoutValidator)
>>> Check validate pubkeys fails with wrong keys. ... ok
>>> test_wrong_steps_list (tests.models.test_layout.TestLayoutValidator)
>>> Check that the validate method checks the steps' correctness. ... ok
>>> test_wrong_type (tests.models.test_layout.TestLayoutValidator)
>>> Test that the type field is validated properly. ... ok
>>> test_validate_byproducts (tests.models.test_link.TestLinkValidator)
>>> Test `byproducts` field. Must be a `dict` ... ok
>>> test_validate_command (tests.models.test_link.TestLinkValidator)
>>> Test `command` field. Must be either a `list` ... ok
>>> test_validate_environment (tests.models.test_link.TestLinkValidator)
>>> Test 

Bug#967997: rdiff-backup: maintainer address invalid

[Ansgar]

Source: rdiff-backup
Version: 2.0.5-1
Severity: serious
X-Debbugs-Cc: o...@debian.org

The maintainer address is invalid, see below.

Ansgar

 Forwarded Message 
> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
> 
>   python-apps-t...@lists.alioth.debian.net
> Unrouteable address

Processed: Re: Bug#964541: flatpak: Wrong argument order for clone syscall seccomp filter on s390x

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + upstream
Bug #964541 [flatpak] flatpak: Wrong argument order for clone syscall seccomp 
filter on s390x
Added tag(s) upstream.
> clone -1 -2 -3
Bug #964541 [flatpak] flatpak: Wrong argument order for clone syscall seccomp 
filter on s390x
Bug 964541 cloned as bugs 967992-967993
964150 was blocked by: 964541
964150 was not blocking any bugs.
Added blocking bug(s) of 964150: 967992
964150 was blocked by: 967992 964541
964150 was not blocking any bugs.
Added blocking bug(s) of 964150: 967993
> unblock 964150 by -2
Bug #964150 [src:petsc] petsc: autopkgtest regression: mpiexec was unable to 
launch the specified application
964150 was blocked by: 967993 964541 967992
964150 was not blocking any bugs.
Removed blocking bug(s) of 964150: 967992
> unblock 964150 by -3
Bug #964150 [src:petsc] petsc: autopkgtest regression: mpiexec was unable to 
launch the specified application
964150 was blocked by: 964541 967993
964150 was not blocking any bugs.
Removed blocking bug(s) of 964150: 967993
> forwarded -1 https://github.com/flatpak/flatpak/pull/3777
Bug #964541 [flatpak] flatpak: Wrong argument order for clone syscall seccomp 
filter on s390x
Set Bug forwarded-to-address to 'https://github.com/flatpak/flatpak/pull/3777'.
> severity -2 normal
Bug #967992 [flatpak] flatpak: Wrong argument order for clone syscall seccomp 
filter on s390x
Severity set to 'normal' from 'serious'
> reassign -2 src:webkit2gtk 2.28.4-1
Bug #967992 [flatpak] flatpak: Wrong argument order for clone syscall seccomp 
filter on s390x
Bug reassigned from package 'flatpak' to 'src:webkit2gtk'.
Ignoring request to alter found versions of bug #967992 to the same values 
previously set
Ignoring request to alter fixed versions of bug #967992 to the same values 
previously set
Bug #967992 [src:webkit2gtk] flatpak: Wrong argument order for clone syscall 
seccomp filter on s390x
Marked as found in versions webkit2gtk/2.28.4-1.
> retitle -2 webkit2gtk: Wrong argument order for clone syscall seccomp filter 
> on s390x
Bug #967992 [src:webkit2gtk] flatpak: Wrong argument order for clone syscall 
seccomp filter on s390x
Changed Bug title to 'webkit2gtk: Wrong argument order for clone syscall 
seccomp filter on s390x' from 'flatpak: Wrong argument order for clone syscall 
seccomp filter on s390x'.
> severity -3 normal
Bug #967993 [flatpak] flatpak: Wrong argument order for clone syscall seccomp 
filter on s390x
Severity set to 'normal' from 'serious'
> reassign -3 src:gnome-desktop3 3.36.4-1
Bug #967993 [flatpak] flatpak: Wrong argument order for clone syscall seccomp 
filter on s390x
Bug reassigned from package 'flatpak' to 'src:gnome-desktop3'.
Ignoring request to alter found versions of bug #967993 to the same values 
previously set
Ignoring request to alter fixed versions of bug #967993 to the same values 
previously set
Bug #967993 [src:gnome-desktop3] flatpak: Wrong argument order for clone 
syscall seccomp filter on s390x
Marked as found in versions gnome-desktop3/3.36.4-1.
> forwarded -3 https://gitlab.gnome.org/GNOME/gnome-desktop/-/merge_requests/82
Bug #967993 [src:gnome-desktop3] flatpak: Wrong argument order for clone 
syscall seccomp filter on s390x
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gnome-desktop/-/merge_requests/82'.
> retitle -3 gnome-desktop3: Wrong argument order for clone syscall seccomp 
> filter on s390x
Bug #967993 [src:gnome-desktop3] flatpak: Wrong argument order for clone 
syscall seccomp filter on s390x
Changed Bug title to 'gnome-desktop3: Wrong argument order for clone syscall 
seccomp filter on s390x' from 'flatpak: Wrong argument order for clone syscall 
seccomp filter on s390x'.

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

Bug#964541: flatpak: Wrong argument order for clone syscall seccomp filter on s390x

[Simon McVittie]

Control: tags -1 + upstream
Control: clone -1 -2 -3
Control: unblock 964150 by -2
Control: unblock 964150 by -3
Control: forwarded -1 https://github.com/flatpak/flatpak/pull/3777
Control: severity -2 normal
Control: reassign -2 src:webkit2gtk 2.28.4-1
Control: retitle -2 webkit2gtk: Wrong argument order for clone syscall seccomp 
filter on s390x
Control: severity -3 normal
Control: reassign -3 src:gnome-desktop3 3.36.4-1
Control: forwarded -3 
https://gitlab.gnome.org/GNOME/gnome-desktop/-/merge_requests/82
Control: retitle -3 gnome-desktop3: Wrong argument order for clone syscall 
seccomp filter on s390x

On Thu, 06 Aug 2020 at 10:56:27 +0100, Simon McVittie wrote:
> I think for completeness we should also be testing __CRIS__

I've sent a patch upstream with that change and some extra comments.
https://github.com/flatpak/flatpak/pull/3777

If you have any suggested changes, please send them there.

> * gnome-desktop3_3.36.4-1/libgnome-desktop/gnome-desktop-thumbnail-script.c

Sent to https://gitlab.gnome.org/GNOME/gnome-desktop/-/merge_requests/82

> * systemd_246-2/src/shared/seccomp-util.c

On closer examination, this one is fine.

> * 
> webkit2gtk_2.28.4-1/Source/WebKit/UIProcess/Launcher/glib/BubblewrapLauncher.cpp

I would appreciate it if a WebKit maintainer could look at this - the
code is not identical and I don't have the resources to compile WebKit.

Context for WebKit maintainers: see
https://github.com/flatpak/flatpak/pull/3777.

I've also pinged Sandstorm as requested in the Flatpak source code.
https://github.com/sandstorm-io/sandstorm/issues/3402

smcv

Bug#963737: ilias...@debian.org

[peter green]

Ilias Tsitsimpis wrote:

We should make sure that anyone using this package has migrated to
skylighting and then remove it.


hi, highlighting-kate was just removed from testing at your request, but
carettah still build-depends on it in both testing and
unstable.

Should I go ahead and file a rc bug against carettah

Bug#963443: marked as done (apache-curator: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project curator-framework: Compilati

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 10:33:28 +
with message-id 
and subject line Bug#963443: fixed in apache-curator 2.7.1-3
has caused the Debian Bug report #963443,
regarding apache-curator: FTBFS: [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) 
on project curator-framework: Compilation failure: Compilation failure:
to be marked as done.

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

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


-- 
963443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apache-curator
Version: 2.7.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Regenerate the Java classes from the Thrift files
> sed -i 's/^namespace java.swift/\/\/namespace java.swift/g' 
> curator-x-rpc/src/main/thrift/curator.thrift
> cd curator-x-rpc/src/main/scripts && bash apply-thrift.sh java
> dh_auto_build
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Apache Curator 
> [pom]
> [INFO] Curator Testing
> [jar]
> [INFO] Curator Client 
> [jar]
> [INFO] Curator Framework  
> [jar]
> [INFO] Curator Recipes
> [jar]
> [INFO] Curator Service Discovery   
> [bundle]
> [INFO] 
> [INFO] -< org.apache.curator:apache-curator 
> >--
> [INFO] Building Apache Curator 2.7.1  
> [1/6]
> [INFO] [ pom 
> ]-
> [WARNING] The artifact org.testng:testng:jar:6.x has been relocated to 
> org.testng:testng:jar:debian
> [INFO] 
> [INFO] --- maven-bundle-plugin:3.5.1:manifest (bundle-manifest) @ 
> apache-curator ---
> [WARNING] Ignoring project type pom - supportedProjectTypes = [jar, war, 
> bundle]
> [INFO] 
> [INFO] --< org.apache.curator:curator-test 
> >---
> [INFO] Building Curator Testing 2.7.1 
> [2/6]
> [INFO] [ jar 
> ]-
> [WARNING] The artifact javassist:javassist:jar:debian has been relocated to 
> org.javassist:javassist:jar:debian
> [WARNING] The artifact org.testng:testng:jar:6.x has been relocated to 
> org.testng:testng:jar:debian
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> curator-test ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources to META-INF
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ 
> curator-test ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 14 source files to 
> /<>/curator-test/target/classes
> [INFO] 
> [INFO] --- maven-bundle-plugin:3.5.1:manifest (bundle-manifest) @ 
> curator-test ---
> 

Bug#967953: ifupdown2

[Christoph Egger]

Hi

> We are now looking for a new debian sponsor to upload our latest
> version to the debian repository.

I guess I can help there for now but better don't rely on me for long-term 
sponsoring. What exactly would you want uploaded? Do you have the package 
somewhere? or github HEAD?

Christoph

Bug#967991: glirc, build-depends on package which is not in testing

[peter green]

Package: glirc
Version: 2.35-1
Severity: serious
Justification: rc policy: "packages must be buildable within the same release"

glirc can no longer be built in testing because haskell-regex-tdfa is no longer
present in testing. Ilias Tsitsimpis has filed a bug report against the package
saying he intends to remove it and asked the release team to remove it from
testing ( https://lists.debian.org/debian-haskell/2020/08/msg2.html ) .
which the release team did.

Bug#963385: marked as done (airlift-airline: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project airline: Compilation failur

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 10:18:46 +
with message-id 
and subject line Bug#963385: fixed in airlift-airline 0.7-3
has caused the Debian Bug report #963385,
regarding airlift-airline: FTBFS: [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) 
on project airline: Compilation failure
to be marked as done.

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

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


-- 
963385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: airlift-airline
Version: 0.7-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>   mh_patchpoms -plibairline-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] -< io.airlift:airline 
> >-
> [INFO] Building airline 0.7
> [INFO] [ jar 
> ]-
> [WARNING] The artifact org.testng:testng:jar:6.x has been relocated to 
> org.testng:testng:jar:debian
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> airline ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /<>/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ airline ---
> [INFO] Changes detected - recompiling the module!
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> [INFO] Compiling 40 source files to /<>/target/classes
> [INFO] 
> /<>/src/main/java/io/airlift/airline/GlobalUsageSummary.java: 
> /<>/src/main/java/io/airlift/airline/GlobalUsageSummary.java 
> uses or overrides a deprecated API.
> [INFO] 
> /<>/src/main/java/io/airlift/airline/GlobalUsageSummary.java: 
> Recompile with -Xlint:deprecation for details.
> [INFO] /<>/src/main/java/io/airlift/airline/Accessor.java: Some 
> input files use unchecked or unsafe operations.
> [INFO] /<>/src/main/java/io/airlift/airline/Accessor.java: 
> Recompile with -Xlint:unchecked for details.
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /<>/src/main/java/io/airlift/airline/model/OptionMetadata.java:[234,48]
>   is not abstract and 
> does not override abstract method 
> test(io.airlift.airline.model.OptionMetadata) in java.util.function.Predicate
> [INFO] 1 error
> [INFO] -
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 

Processed: bug 966889 is forwarded to https://github.com/java-native-access/jna/issues/1244

[Debian Bug Tracking System]

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

> forwarded 966889 https://github.com/java-native-access/jna/issues/1244
Bug #966889 [src:libjna-java] libjna-java: FTBFS:  [exec] 
dispatch.c:1770:23: error: ‘alloca’ bound is unknown 
[-Werror=alloca-larger-than=]
Set Bug forwarded-to-address to 
'https://github.com/java-native-access/jna/issues/1244'.
> thanks
Stopping processing here.

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

Bug#963443: marked as pending in apache-curator

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #963443 in apache-curator 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/java-team/apache-curator/-/commit/18d45d4cbf3c5f55de16233657761c770f1c3a9d


Set the source/target level to Java 8 (Closes: #963443)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963443