Bug#922129: filemanager-actions: Incomplete debian/copyright?

2020-08-31 Thread Chris Lamb
Hi darkdragon,

> > I just ACCEPTed filemanager-actions from NEW but noticed it was
> > missing attribution in debian/copyright for at least Red Hat, Novell,
> > etc.
>
> Can you please clarify the problem upstream in
> https://gitlab.gnome.org/GNOME/filemanager-actions/-/issues/17 ?

Two quick things:

 * You say: "filemanager-actions has been removed from Debian/Ubuntu
   because of incomplete license/copyright information". This is not
   really true. The package was removed for reasons listed in #961824
   as far as I can tell; ie. it was unmaintained.

 * I filed this bug (#922129) due to an incomplete debian/copyright
   file. In other words, the file under the debian/ subdirectory, and
   not something that upstream could clarify. This might be why they
   are confused.

I am no longer a member of the ftpmaster team, so I won't be able to
help you any further. Good luck...


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-



Processed: Bug #958621: schroot: Build-Depends on deprecated dh-systemd which is going away

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 958621 patch
Bug #958621 [src:schroot] schroot: Build-Depends on deprecated dh-systemd which 
is going away
Added tag(s) patch.
> thanks
Stopping processing here.

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



Bug#957224: marked as done (fped: ftbfs with GCC-10)

2020-08-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Aug 2020 21:05:22 +
with message-id 
and subject line Bug#957224: fixed in fped 0.1+201210-1.2
has caused the Debian Bug report #957224,
regarding fped: 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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
 from /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 gui_frame.c:15:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
  CCgui_frame_drag.o
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
 from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
 from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
 from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
 from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
 from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:33,
 from gui_frame_drag.c:15:
/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 gui_frame_drag.c:15:
/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 gui_frame_drag.c:15:
/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 

Processed: Re: Bug#969224: cdimage.debian.org: Error installing Debian 10.5 from flash stick with Extlinux

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 969224 Archive main/installer-*/current/ has outdated kernels?
Bug #969224 [cdimage.debian.org] cdimage.debian.org: Error installing Debian 
10.5 from flash stick with Extlinux
Changed Bug title to 'Archive main/installer-*/current/ has outdated kernels?' 
from 'cdimage.debian.org: Error installing Debian 10.5 from flash stick with 
Extlinux'.
> severity 969224 normal
Bug #969224 [cdimage.debian.org] Archive main/installer-*/current/ has outdated 
kernels?
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.

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



Bug#969224: cdimage.debian.org: Error installing Debian 10.5 from flash stick with Extlinux

2020-08-31 Thread J.A. Bezemer

retitle 969224 Archive main/installer-*/current/ has outdated kernels?
severity 969224 normal
thanks

Hi,

So the real problem is that the archive seems outdated w.r.t. DVD images. 
The DVD images themselves are consistent (since you report they work 
fine).


I'm doing customized usb sticks regularly, e.g. putting i386 and amd64 
installer DVD iso's plus several Live systems onto one big usb stick, with 
bootloader options to choose between them.


So I've bumped into this exact issue before, and I learned to always get 
everything from the same source. Specifically, get kernel and initrd 
directly from the .iso file that you use, by mounting it (-o loop), or 
extract them using isoinfo command (hint: -R option), or probably 7z will 
work too. While you're there, also study what the "official" bootloader is 
passing to the kernel commandline, and do something similar in your own 
bootloader config.


Best regards,
Anne Bezemer


On Sun, 30 Aug 2020,   wrote:

[..]


I think the problem is that the kernel versions for DVD and
installer-amd64/current/images/hd-media/ or
installer-amd64/current/images/hd-media/gtk/
ÿÿ initrd.gz
for Debian 10.4 and Debian 10.5
don't match.

for Debian 10.5
4.19.0-10 - the kernel versions for DVD
4.19.0-5  - the kernel versions for
http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/
or (for GTK)
http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/gtk/

ÿÿ Debian 10.4
4.19.0-9 - the kernel versions for ÿÿ DVD
4.19.0-5 - the kernel versions for
http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/
or (for GTK)
http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/gtk/

ÿÿ Debian 10.3
4.19.0-8 - the kernel versions for ÿÿ DVD
4.19.0-8 - the kernel versions for
http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/
or (for GTK)
http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/gtk/

For Debian 10.3 everything was established without problems.

Processed: Re: filemanager-actions: Incomplete debian/copyright?

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> unarchive 922129
Bug #922129 {Done: Debian FTP Masters } 
[src:filemanager-actions] filemanager-actions: Incomplete debian/copyright?
Warning: Unknown package 'src:filemanager-actions'
Unarchived Bug 922129
Warning: Unknown package 'src:filemanager-actions'
> thanks
Stopping processing here.

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



Bug#958013: marked as done (zfs-fuse: ftbfs with GCC-10)

2020-08-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Aug 2020 19:33:46 +
with message-id 
and subject line Bug#958013: fixed in zfs-fuse 0.7.0-21
has caused the Debian Bug report #958013,
regarding zfs-fuse: 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.)


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

[...]
gcc -o lib/libuutil/uu_ident.o -c -pipe -Wall -std=c99 -Wno-switch -Wno-unused 
-Wno-missing-braces -Wno-parentheses -Wno-uninitialized -fno-strict-aliasing 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DTEXT_DOMAIN=\"zfs-fuse\" 
-ggdb -DNDEBUG -O2 -DNATIVE_BUILD -DLINUX_AIO -Ilib/libuutil/include 
-Ilib/libavl/include -Ilib/libsolcompat/include lib/libuutil/uu_ident.c
gcc -o lib/libuutil/uu_list.o -c -pipe -Wall -std=c99 -Wno-switch -Wno-unused 
-Wno-missing-braces -Wno-parentheses -Wno-uninitialized -fno-strict-aliasing 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DTEXT_DOMAIN=\"zfs-fuse\" 
-ggdb -DNDEBUG -O2 -DNATIVE_BUILD -DLINUX_AIO -Ilib/libuutil/include 
-Ilib/libavl/include -Ilib/libsolcompat/include lib/libuutil/uu_list.c
gcc -o lib/libuutil/uu_misc.o -c -pipe -Wall -std=c99 -Wno-switch -Wno-unused 
-Wno-missing-braces -Wno-parentheses -Wno-uninitialized -fno-strict-aliasing 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DTEXT_DOMAIN=\"zfs-fuse\" 
-ggdb -DNDEBUG -O2 -DNATIVE_BUILD -DLINUX_AIO -Ilib/libuutil/include 
-Ilib/libavl/include -Ilib/libsolcompat/include lib/libuutil/uu_misc.c
gcc -o lib/libuutil/uu_open.o -c -pipe -Wall -std=c99 -Wno-switch -Wno-unused 
-Wno-missing-braces -Wno-parentheses -Wno-uninitialized -fno-strict-aliasing 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DTEXT_DOMAIN=\"zfs-fuse\" 
-ggdb -DNDEBUG -O2 -DNATIVE_BUILD -DLINUX_AIO -Ilib/libuutil/include 
-Ilib/libavl/include -Ilib/libsolcompat/include lib/libuutil/uu_open.c
gcc -o lib/libuutil/uu_pname.o -c -pipe -Wall -std=c99 -Wno-switch -Wno-unused 
-Wno-missing-braces -Wno-parentheses -Wno-uninitialized -fno-strict-aliasing 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DTEXT_DOMAIN=\"zfs-fuse\" 
-ggdb -DNDEBUG -O2 -DNATIVE_BUILD -DLINUX_AIO -Ilib/libuutil/include 
-Ilib/libavl/include -Ilib/libsolcompat/include lib/libuutil/uu_pname.c
gcc -o lib/libuutil/uu_strtoint.o -c -pipe -Wall -std=c99 -Wno-switch 
-Wno-unused -Wno-missing-braces -Wno-parentheses -Wno-uninitialized 
-fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT 
-DTEXT_DOMAIN=\"zfs-fuse\" -ggdb -DNDEBUG -O2 -DNATIVE_BUILD -DLINUX_AIO 
-Ilib/libuutil/include -Ilib/libavl/include -Ilib/libsolcompat/include 
lib/libuutil/uu_strtoint.c
gcc -o lib/libsolcompat/getmntany.o -c -pipe -Wall -std=c99 -Wno-switch 
-Wno-unused -Wno-missing-braces -Wno-parentheses -Wno-uninitialized 
-fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT 
-DTEXT_DOMAIN=\"zfs-fuse\" -ggdb -DNDEBUG -O2 -DLINUX_AIO 
-Ilib/libsolcompat/include -Ilib/libsolcompat/include/amd64 
lib/libsolcompat/getmntany.c
In file included from lib/libsolcompat/getmntany.c:35:
lib/libsolcompat/include/sys/sysmacros.h:217: warning: "howmany" redefined
  217 | #define howmany(x, y) (((x)+((y)-1))/(y))
  | 
In file included from lib/libsolcompat/include/sys/param.h:30,
 from 

Processed: hexcurse: diff for NMU version 1.58-1.3

2020-08-31 Thread Debian Bug Tracking System
Processing control commands:

> tags 966855 + patch
Bug #966855 [src:hexcurse] hexcurse: FTBFS: ld: 
llist.o:./src/../include/hex.h:129: multiple definition of `fpOUT'; 
file.o:./src/../include/hex.h:129: first defined here
Added tag(s) patch.
> tags 966855 + pending
Bug #966855 [src:hexcurse] hexcurse: FTBFS: ld: 
llist.o:./src/../include/hex.h:129: multiple definition of `fpOUT'; 
file.o:./src/../include/hex.h:129: first defined here
Added tag(s) pending.

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



Bug#966855: hexcurse: diff for NMU version 1.58-1.3

2020-08-31 Thread Sudip Mukherjee
Control: tags 966855 + patch
Control: tags 966855 + pending

Dear maintainer,

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

--
Regards
Sudip

diff -Nru hexcurse-1.58/debian/changelog hexcurse-1.58/debian/changelog
--- hexcurse-1.58/debian/changelog  2020-03-29 19:36:45.0 +0100
+++ hexcurse-1.58/debian/changelog  2020-08-31 19:44:26.0 +0100
@@ -1,3 +1,10 @@
+hexcurse (1.58-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with gcc-10. (Closes: #966855)
+
+ -- Sudip Mukherjee   Mon, 31 Aug 2020 19:44:26 
+0100
+
 hexcurse (1.58-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru hexcurse-1.58/debian/patches/gcc-10.patch 
hexcurse-1.58/debian/patches/gcc-10.patch
--- hexcurse-1.58/debian/patches/gcc-10.patch   1970-01-01 01:00:00.0 
+0100
+++ hexcurse-1.58/debian/patches/gcc-10.patch   2020-08-31 19:43:53.0 
+0100
@@ -0,0 +1,30 @@
+Description: Fix FTBFS
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/966855
+Forwarded: no
+
+---
+
+--- hexcurse-1.58.orig/include/hex.h
 hexcurse-1.58/include/hex.h
+@@ -126,7 +126,7 @@ extern char EBCDIC[256];
+ #define max(a,b) ((a) >(b) ? (a) : (b))
+ #endif
+ 
+-FILE *fpIN, *fpOUT;   /* global file ptrs   */
++extern FILE *fpIN, *fpOUT;/* global file ptrs 
  */
+ 
+ /* function prototypes */
+ 
+--- hexcurse-1.58.orig/src/file.c
 hexcurse-1.58/src/file.c
+@@ -18,6 +18,8 @@
+ 
\**/
+ #include "hex.h"
+ 
++FILE *fpIN, *fpOUT;
++
+ /***\
+  * Description: prints out a line of text to the screen*
+  *the current address line and both the  *
diff -Nru hexcurse-1.58/debian/patches/series 
hexcurse-1.58/debian/patches/series
--- hexcurse-1.58/debian/patches/series 2020-03-29 19:36:45.0 +0100
+++ hexcurse-1.58/debian/patches/series 2020-08-31 19:42:46.0 +0100
@@ -3,3 +3,4 @@
 0001-explicitly-mark-fallthrough-case.patch
 0001-fix-format-truncation-error-with-GCC-7.patch
 fix_ftbfs.patch
+gcc-10.patch



Bug#937255: pbgenomicconsensus: Python2 removal in sid/bullseye

2020-08-31 Thread Moritz Mühlenhoff
On Fri, Aug 30, 2019 at 07:30:23AM +, Matthias Klose wrote:
> Package: src:pbgenomicconsensus
> Version: 2.3.2-5
> 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

Upstream development seems to have stalled, let's remove?

Cheers,
Moritz



Bug#937102: mysql-workbench: Python2 removal in sid/bullseye

2020-08-31 Thread Moritz Mühlenhoff
On Fri, Aug 30, 2019 at 07:27:37AM +, Matthias Klose wrote:
> Package: src:mysql-workbench
> Version: 8.0.17+dfsg-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

There's radio silence on https://bugs.mysql.com/bug.php?id=98839,
let's remove?

Cheers,
Moritz



Bug#937940: python-nemu: Python2 removal in sid/bullseye

2020-08-31 Thread Moritz Mühlenhoff
On Fri, Mar 27, 2020 at 11:57:00PM +0100, Moritz Mühlenhoff wrote:
> On Fri, Aug 30, 2019 at 07:42:40AM +, Matthias Klose wrote:
> > Package: src:python-nemu
> > Version: 0.3.1-1
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
> > 
> > Python2 becomes end-of-live upstream, and Debian aims to remove
> > Python2 from the distribution, as discussed in
> > https://lists.debian.org/debian-python/2019/07/msg00080.html
> 
> Hi Martina,
> given that you're also the upstream of python-nemu, are you planning
> to port it to Python 3 or should it be removed?

Gentle ping

Cheers,
Moritz
 



Bug#969331: rviz: [rospack] Error: no such package media_export

2020-08-31 Thread Jochen Sprickerhof

* Johannes Schauer  [2020-08-31 18:43]:

The only difference between before and after are the additional dbgsym packages
as well as the upgrade of libogre-1.9.0v5 to the newer binNMU version.

Thus, I guess a version constraint is not tight enough somewhere?


Afaik Debian doesn't guarantee this.

* Johannes 'josch' Schauer  [2020-08-31 16:54]:

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


Uhm.. https://wiki.debian.org/DontBreakDebian

Please close if you agree.

Cheers Jochen


signature.asc
Description: PGP signature


Processed: tagging 963760

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 963760 + bullseye sid
Bug #963760 [ceph] new upstream release (1.4.11)
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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



Processed: tagging 967916

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 967916 + bullseye sid
Bug #967916 [easyspice] Depends on geda-gaf
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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



Processed: [bts-link] source package gnome-music

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package gnome-music
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #954195 (http://bugs.debian.org/954195)
> # Bug title: gnome-music fails to start: SyntaxError: invalid syntax ", /,"
> #  * https://gitlab.gnome.org/GNOME/gnome-music/-/issues/410
> #  * remote status changed: closed -> opened
> #  * reopen upstream
> tags 954195 - fixed-upstream
Bug #954195 [gnome-music] gnome-music fails to start: SyntaxError: invalid 
syntax ", /,"
Removed tag(s) fixed-upstream.
> usertags 954195 - status-closed
Usertags were: status-closed.
Usertags are now: .
> usertags 954195 + status-opened
There were no usertags set.
Usertags are now: status-opened.
> thanks
Stopping processing here.

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



Processed: [bts-link] source package src:python-flask-cors

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:python-flask-cors
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #950058 (http://bugs.debian.org/950058)
> # Bug title: python-flask-cors FTBFS with flask 1.1.1
> #  * https://github.com/corydolphin/flask-cors/issues/253
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 950058 + fixed-upstream
Bug #950058 [src:python-flask-cors] python-flask-cors FTBFS with flask 1.1.1
Added tag(s) fixed-upstream.
> usertags 950058 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 950058 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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



Bug#969331: rviz: [rospack] Error: no such package media_export

2020-08-31 Thread Jochen Sprickerhof

Hi josch,

* Johannes 'josch' Schauer  [2020-08-31 16:54]:

starting rviz on Debian unstable currently yields the following output:

[ INFO] [1598885512.042478573]: rviz version 1.14.1
[ INFO] [1598885512.042531596]: compiled against Qt version 5.14.2
[ INFO] [1598885512.042547093]: compiled against OGRE version 1.9.0 (Ghadamon)
[ INFO] [1598885512.052974842]: Forcing OpenGl version 0.
[ INFO] [1598885512.592152405]: Stereo is NOT SUPPORTED
[ INFO] [1598885512.592246596]: OpenGl version: 4.6 (GLSL 4.6).
[rospack] Error: no such package media_export
[librospack]: error while executing command


I get those as well.


zsh: segmentation fault  rviz


But I don't get this, but rviz starts normally for me. Can you attach 
gdb and get a backtrace?


Cheers Jochen


signature.asc
Description: PGP signature


Bug#965995: dnscrypt-proxy: Purging fails: rm: cannot remove '/etc/dnscrypt-proxy/dnscrypt-proxy.conf.dpkg-bak': Is a directory

2020-08-31 Thread Eric Dorland
* Axel Beckert (a...@debian.org) wrote:
> Package: dnscrypt-proxy
> Version: 2.0.44+ds1-2
> Severity: serious
> X-Debbugs-Cc: Axel Beckert 
> 
> Purging dnscrypt-proxy fails for me as follows (and IIRC I never changed
> anything from the default config, but the package might have a bit on
> history on that machine):
> 
> # dpkg --purge dnscrypt-proxy
> (Reading database ... 1190427 files and directories currently installed.)
> Purging configuration files for dnscrypt-proxy (2.0.44+ds1-2) ...
> rm: cannot remove '/etc/dnscrypt-proxy/dnscrypt-proxy.conf.dpkg-bak': Is a 
> directory
> dpkg: error processing package dnscrypt-proxy (--purge):
>  installed dnscrypt-proxy package post-removal script subprocess returned 
> error exit status 1
> Errors were encountered while processing:
>  dnscrypt-proxy
> 
> Might be just a missing "-r" to "rm" in the postrm script or so.

So this appears to be a bug related to a mess in the past where there
was a /etc/dnscrypt-proxy/dnscrypt-proxy.conf directory created at
some point. I'm using dpkg-maintscript-helper but it appears to
failing on this edge case.

-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: PGP signature


Processed (with 1 error): merging 969333 to 940205

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 969333 important
Bug #969333 {Done: Guilhem Moulin } 
[roundcube-plugins-extra] roundcube-plugins-extra: thunderbird_labels requires 
an upgrade
Severity set to 'important' from 'grave'
> forcemerge 940205 969333
Failed to forcibly merge 940205: Not altering archived bugs; see unarchive.

> thanks
Stopping processing here.

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



Bug#969331: rviz: [rospack] Error: no such package media_export

2020-08-31 Thread Johannes Schauer
Quoting Jochen Sprickerhof (2020-08-31 18:31:58)
> * Johannes 'josch' Schauer  [2020-08-31 16:54]:
> >starting rviz on Debian unstable currently yields the following output:
> >
> >[ INFO] [1598885512.042478573]: rviz version 1.14.1
> >[ INFO] [1598885512.042531596]: compiled against Qt version 5.14.2
> >[ INFO] [1598885512.042547093]: compiled against OGRE version 1.9.0 
> >(Ghadamon)
> >[ INFO] [1598885512.052974842]: Forcing OpenGl version 0.
> >[ INFO] [1598885512.592152405]: Stereo is NOT SUPPORTED
> >[ INFO] [1598885512.592246596]: OpenGl version: 4.6 (GLSL 4.6).
> >[rospack] Error: no such package media_export
> >[librospack]: error while executing command
> 
> I get those as well.
> 
> >zsh: segmentation fault  rviz
> 
> But I don't get this, but rviz starts normally for me. Can you attach gdb and
> get a backtrace?

aha, so that was a red herring! I thought the segfault was due to the
media_export error message.

To get a better backtrace, I installed the dbgsym packages for rviz, librviz5d
and libogre-1.9.0v5. In the process, the package libogre-1.9.0v5 with version
1.9.0+dfsg1-12+b1 got replaced by version 1.9.0+dfsg1-12+b2.

Now it works.

The only difference between before and after are the additional dbgsym packages
as well as the upgrade of libogre-1.9.0v5 to the newer binNMU version.

Thus, I guess a version constraint is not tight enough somewhere?

Thanks!

cheers, josch

signature.asc
Description: signature


Processed: Re: openjdk-13: FTBFS: tests failed, and then build hangs

2020-08-31 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo
Bug #967019 [src:openjdk-13] openjdk-13: FTBFS: tests failed, and then build 
hangs
Added tag(s) moreinfo.
> severity -1 important
Bug #967019 [src:openjdk-13] openjdk-13: FTBFS: tests failed, and then build 
hangs
Severity set to 'important' from 'serious'

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



Bug#967019: openjdk-13: FTBFS: tests failed, and then build hangs

2020-08-31 Thread Matthias Klose
Control: tags -1 + moreinfo
Control: severity -1 important

did a no-change build today in a fresh chroot on a local machine, which
succeeded.  Will recheck with the next upload.



Bug#969333: marked as done (roundcube-plugins-extra: thunderbird_labels requires an upgrade)

2020-08-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Aug 2020 18:15:01 +0200
with message-id <20200831161501.ga2590...@debian.org>
and subject line Re: Bug#969333: roundcube-plugins-extra: thunderbird_labels 
requires an upgrade
has caused the Debian Bug report #969333,
regarding roundcube-plugins-extra: thunderbird_labels requires an upgrade
to be marked as done.

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

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


-- 
969333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: roundcube-plugins-extra
Version: 1.3.8-20190219
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

When I activate thunderbird_labels (that come from
roundcube-plugins-extra debian package), I can't go to my
?_task=settings page anymore.  For example, in Inbox folder, if I try
to set a label, roundcube returns:
 "Internal Server Error".
In server logs, I've got this message: FastCGI sent in stderr: "PHP message: PHP
 Fatal error:  Uncaught Error: Call to undefined function
 get_input_value() in
 /usr/share/roundcube/plugins/thunderbird_labels/thunderbird_labels.php:341

To fix this issue, I've moved
/usr/share/roundcube/plugins/thunderbird_labels/ folder and replace it
by the latest version of this plugin (
https://github.com/mike-kfed/roundcube-thunderbird_labels - v1.4.8 ).

Is it possible to make this version available in a further stable
package version?

Thanks.

--
Ludo

-- System Information:
Debian Release: 10.5
Architecture: amd64 (x86_64)

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

Versions of packages roundcube-plugins-extra depends on:
ii  libjs-jquery-mousewheel  1:3.1.13-2
ii  roundcube-core   1.3.15+dfsg.1-1~deb10u1

roundcube-plugins-extra recommends no packages.

Versions of packages roundcube-plugins-extra suggests:
pn  fail2ban  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.4.0-20200423
Control: severity -1 important
Control: forcemerge 969333 -1

Hi,

On Mon, 31 Aug 2020 at 17:39:30 +0200, Ludovic CHEVALIER wrote:
> Severity: grave
> Justification: renders package unusable

Severity: grave is too high given not all plugins in
roundcube-plugins-extra are broken :-P  The package is fully usable if
one doesn't activate thunderbird_labels .

> To fix this issue, I've moved
> /usr/share/roundcube/plugins/thunderbird_labels/ folder and replace it
> by the latest version of this plugin (
> https://github.com/mike-kfed/roundcube-thunderbird_labels - v1.4.8 ).

This was fixed in 1.4.0-20200423, see https://bugs.debian.org/940205#12 .
 
> Is it possible to make this version available in a further stable
> package version?

I'm afraid that's beyond the scope of stable updates.  The bug was fixed
in unstable so I'm closing it.  You might want to install roundcube and
roundcube-plugins-extra from buster-backports if you need the recent
version.

Cheers,
-- 
Guilhem.


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


Bug#967101: marked as done (oscar: FTBFS: qvector.h:799:23: error: implicitly-declared ‘DottedLine& DottedLine::operator=(const DottedLine&)’ is deprecated [-Werror=deprecated-copy])

2020-08-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Aug 2020 15:48:38 +
with message-id 
and subject line Bug#967101: fixed in oscar 1.1.1-2
has caused the Debian Bug report #967101,
regarding oscar: FTBFS: qvector.h:799:23: error: implicitly-declared 
‘DottedLine& DottedLine::operator=(const DottedLine&)’ is deprecated 
[-Werror=deprecated-copy]
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.)


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

Hi,

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

Relevant part (hopefully):
> g++ -c -pipe -Werror -Wno-error=deprecated-declarations -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -frtti 
> -Wall -Wextra -D_REENTRANT -fPIC -Dhelpless -DQT_DEPRECATED_WARNINGS 
> -DNO_UPDATER -DLOCK_RESMED_SESSIONS -D_TTY_POSIX_ -DQT_NO_DEBUG 
> -DQT_PRINTSUPPORT_LIB -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB 
> -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SERIALPORT_LIB -DQT_CORE_LIB -I../../oscar 
> -I. -I/usr/include/x86_64-linux-gnu/qt5 
> -I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport 
> -I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
> -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui 
> -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
> -I/usr/include/x86_64-linux-gnu/qt5/QtXml 
> -I/usr/include/x86_64-linux-gnu/qt5/QtSerialPort 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o mainwindow.o 
> ../../oscar/mainwindow.cpp
> In file included from ../../oscar/SleepLib/profiles.h:18,
>  from ../../oscar/exportcsv.cpp:15:
> ../../oscar/SleepLib/machine.h: In member function ‘QString Machine::hexid()’:
> ../../oscar/SleepLib/machine.h:162:61: warning: ‘QString& 
> QString::sprintf(const char*, ...)’ is deprecated: Use asprintf(), arg() or 
> QTextStream instead [-Wdeprecated-declarations]
>   162 | QString hexid() { return QString().sprintf("%08lx", m_id); }
>   | ^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdir.h:43,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qfiledialog.h:44,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QFileDialog:1,
>  from ../../oscar/exportcsv.cpp:10:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:382:14: note: declared here
>   382 | QString (const char *format, ...) 
> Q_ATTRIBUTE_FORMAT_PRINTF(2, 3);
>   |  ^~~
> In file included from ../../oscar/SleepLib/profiles.h:18,
>  from ../../oscar/daily.h:25,
>  from ../../oscar/daily.cpp:27:
> ../../oscar/SleepLib/machine.h: In member function ‘QString Machine::hexid()’:
> ../../oscar/SleepLib/machine.h:162:61: warning: ‘QString& 
> QString::sprintf(const char*, ...)’ is deprecated: Use asprintf(), arg() or 
> QTextStream instead [-Wdeprecated-declarations]
>   162 | QString hexid() { return QString().sprintf("%08lx", m_id); }
>   | ^
> In file included from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qhashfunctions.h:44,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:47,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstringlist.h:41,
>  from /usr/include/x86_64-linux-gnu/qt5/QtGui/qcolor.h:46,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtGui/qtextformat.h:44,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtGui/QTextCharFormat:1,
>  from ../../oscar/daily.cpp:10:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:382:14: note: declared here
>   382 | QString (const char *format, ...) 
> Q_ATTRIBUTE_FORMAT_PRINTF(2, 3);
>   |  ^~~
> ../../oscar/exportcsv.cpp: In member function ‘void 
> ExportCSV::on_exportButton_clicked()’:
> ../../oscar/exportcsv.cpp:252:74: warning: ‘QString& QString::sprintf(const 
> char*, ...)’ is deprecated: Use asprintf(), arg() or QTextStream instead 
> [-Wdeprecated-declarations]
>   252 | data += sep + QString().sprintf("%02i:%02i:%02i", h, 
> m, s);
>   |  

Bug#969333: roundcube-plugins-extra: thunderbird_labels requires an upgrade

2020-08-31 Thread Ludovic CHEVALIER
Package: roundcube-plugins-extra
Version: 1.3.8-20190219
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

When I activate thunderbird_labels (that come from
roundcube-plugins-extra debian package), I can't go to my
?_task=settings page anymore.  For example, in Inbox folder, if I try
to set a label, roundcube returns:
 "Internal Server Error".
In server logs, I've got this message: FastCGI sent in stderr: "PHP message: PHP
 Fatal error:  Uncaught Error: Call to undefined function
 get_input_value() in
 /usr/share/roundcube/plugins/thunderbird_labels/thunderbird_labels.php:341

To fix this issue, I've moved
/usr/share/roundcube/plugins/thunderbird_labels/ folder and replace it
by the latest version of this plugin (
https://github.com/mike-kfed/roundcube-thunderbird_labels - v1.4.8 ).

Is it possible to make this version available in a further stable
package version?

Thanks.

--
Ludo

-- System Information:
Debian Release: 10.5
Architecture: amd64 (x86_64)

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

Versions of packages roundcube-plugins-extra depends on:
ii  libjs-jquery-mousewheel  1:3.1.13-2
ii  roundcube-core   1.3.15+dfsg.1-1~deb10u1

roundcube-plugins-extra recommends no packages.

Versions of packages roundcube-plugins-extra suggests:
pn  fail2ban  

-- no debconf information



Bug#969331: rviz: [rospack] Error: no such package media_export

2020-08-31 Thread Johannes 'josch' Schauer
Package: rviz
Version: 1.14.1+dfsg-1
Severity: grave
Justification: renders package unusable

Hi,

starting rviz on Debian unstable currently yields the following output:

[ INFO] [1598885512.042478573]: rviz version 1.14.1
[ INFO] [1598885512.042531596]: compiled against Qt version 5.14.2
[ INFO] [1598885512.042547093]: compiled against OGRE version 1.9.0 (Ghadamon)
[ INFO] [1598885512.052974842]: Forcing OpenGl version 0.
[ INFO] [1598885512.592152405]: Stereo is NOT SUPPORTED
[ INFO] [1598885512.592246596]: OpenGl version: 4.6 (GLSL 4.6).
[rospack] Error: no such package media_export
[librospack]: error while executing command
zsh: segmentation fault  rviz

Maybe triggered by this line?

https://sources.debian.org/src/ros-rviz/1.14.1+dfsg-1/src/rviz/ogre_helpers/render_system.cpp/?hl=316#L318

According to the package.xml, rviz depends on media_export but that one
is not packaged yet?

Thanks!

cheers, josch


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

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

Versions of packages rviz depends on:
ii  fonts-liberation   1:1.07.4-9
ii  libboost-filesystem1.71.0  1.71.0-6+b2
ii  libboost-thread1.71.0  1.71.0-6+b2
ii  libc6  2.31-2
ii  libclass-loader1d  0.5.0-1
ii  libconsole-bridge0.4   0.4.3+dfsg-1
ii  libgcc-s1  10.2.0-3
ii  libimage-transport0d   1.12.0-1+b1
ii  libinteractive-markers2d   1.12.0-3
ii  liblaser-geometry0d1.6.5-1+b1
ii  libmessage-filters1d   1.15.8+ds1-1
ii  libogre-1.9.0v51.9.0+dfsg1-12+b1
ii  libopengl0 1.3.1-1
ii  libqt5core5a   5.14.2+dfsg-4
ii  libqt5gui5 5.14.2+dfsg-4
ii  libqt5svg5 5.14.2-2
ii  libqt5widgets5 5.14.2+dfsg-4
ii  librosconsole3d1.14.2-1
ii  libroscpp-serialization0d  0.7.2-2
ii  libroscpp3d1.15.8+ds1-1
ii  libroslib0d1.15.4-2
ii  librostime1d   0.7.2-4
ii  librviz5d  1.14.1+dfsg-1
ii  libstdc++6 10.2.0-3
ii  libtf2-2d  0.7.2-3
ii  libtinyxml2-8  8.0.0+dfsg-2
ii  liburdf1d  1.13.2-2
ii  liburdfdom-world   1.0.3-1

rviz recommends no packages.

rviz suggests no packages.

-- no debconf information



Processed: tagging 933111

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 933111 + bullseye sid
Bug #933111 {Done: intrigeri } [libcgi-application-perl] 
libcgi-application-perl: build-depends on pkg-components that won't be in 
Bullseye unless it finds a new upstream maintainer
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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



Processed: tagging 967915

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 967915 + bullseye sid
Bug #967915 [gspiceui] Depends on geda-gaf
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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



Processed: tagging 933115

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 933115 + bullseye sid
Bug #933115 [libcgi-application-plugin-tt-perl] 
libcgi-application-plugin-tt-perl: build-depends on pkg-components that won't 
be in Bullseye unless it finds a new upstream maintainer
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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



Processed: tagging 933113

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 933113 + bullseye sid
Bug #933113 [libcgi-application-plugin-authorization-perl] 
libcgi-application-plugin-authorization-perl: build-depends on pkg-components 
that won't be in Bullseye unless it finds a new upstream maintainer
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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



Processed: tagging 933118

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 933118 + bullseye sid
Bug #933118 {Done: Nick Morrott } [libwww-search-perl] 
libwww-search-perl: build-depends on pkg-components that won't be in Bullseye 
unless it finds a new upstream maintainer
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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



Bug#962623: ImportError: cannot import name 'parse_qs' from 'cgi' (/usr/lib/python3.8/cgi.py)

2020-08-31 Thread Hermann Lauer
This is a multi-part MIME message sent by reportbug.


--===0522418674==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: graphite-web
Followup-For: Bug #962623

Dear Maintainer,

please upgrade to 1.1.7 available upstream and replace 
debian/patches/settings_debian.patch
with the appended version.

This makes 1.1.7 working in testing(bullseye).

Thanks a lot,
 greetings
   Hermann

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (40, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 5.7.8 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages graphite-web depends on:
ii  adduser 3.118
ii  python3 3.8.2-3
ii  python3-cairo   1.16.2-4
ii  python3-cairocffi   0.9.0-4
ii  python3-django  2:2.2.15-2
ii  python3-django-tagging  1:0.4.5-3
ii  python3-pyparsing   2.4.7-1
ii  python3-simplejson  3.17.0-1
ii  python3-six 1.15.0-1
ii  python3-tz  2020.1-2
ii  python3-urllib3 1.25.9-1
ii  python3-whisper 1.1.4-2

graphite-web recommends no packages.

Versions of packages graphite-web suggests:
pn  graphite-carbon  
pn  libapache2-mod-wsgi-py3  
pn  python3-ldap 
pn  python3-memcache 
pn  python3-mysqldb  

-- Configuration Files:
/etc/graphite/local_settings.py changed [not included]

-- no debconf information

--===0522418674==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="settings_debian.patch"

# HG changeset patch
# Parent  bc853f64d61b2a37516e59c5c8edff74c78feccd

diff --git a/webapp/graphite/settings.py b/webapp/graphite/settings.py
--- a/webapp/graphite/settings.py
+++ b/webapp/graphite/settings.py
@@ -20,6 +20,9 @@
 from warnings import warn
 from importlib import import_module
 
+# Debian add etc/graphite into path
+sys.path.append('/etc/graphite')
+
 from django import VERSION as DJANGO_VERSION
 try:
 from django.urls import reverse_lazy
@@ -221,7 +224,7 @@
 FLUSHRRDCACHED = ''
 
 ## Load our local_settings
-SETTINGS_MODULE = os.environ.get('GRAPHITE_SETTINGS_MODULE', 
'graphite.local_settings')
+SETTINGS_MODULE = os.environ.get('GRAPHITE_SETTINGS_MODULE', 'local_settings')
 try:
   globals().update(import_module(SETTINGS_MODULE).__dict__)
 except ImportError:

--===0522418674==--



Processed: tagging 933114

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 933114 + bullseye sid
Bug #933114 [libcgi-application-plugin-devpopup-perl] 
libcgi-application-plugin-devpopup-perl: build-depends on pkg-components that 
won't be in Bullseye unless it finds a new upstream maintainer
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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



Processed: tagging 933116

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 933116 + bullseye sid
Bug #933116 [libcgi-application-plugin-viewcode-perl] 
libcgi-application-plugin-viewcode-perl: build-depends on pkg-components that 
won't be in Bullseye unless it finds a new upstream maintainer
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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



Processed: tagging 933112

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 933112 + bullseye sid
Bug #933112 [libcgi-application-plugin-authentication-perl] 
libcgi-application-plugin-authentication-perl: build-depends on pkg-components 
that won't be in Bullseye unless it finds a new upstream maintainer
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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



Processed: found 966921 in 2.13.0+dfsg1-10

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 966921 2.13.0+dfsg1-10
Bug #966921 [src:openvswitch] openvswitch: FTBFS: configure: error: Could not 
find DPDK library in default search path, Use --with-dpdk to specify the DPDK 
library installed in non-standard location
Marked as found in versions openvswitch/2.13.0+dfsg1-10.
> thanks
Stopping processing here.

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



Bug#774149:

2020-08-31 Thread Barr Julian Marshall
Ich habe mich wegen der Dringlichkeit dieser Frage entschlossen, Sie zu
kontaktieren. Ich bin Julian Marshall, Rechtsanwalt. Ich persönlich bin ein
Treuhandagent von Dr. Edwin, einem weithin bekannten unabhängigen
Auftragnehmer hier in Lome Togo, der mit seiner Frau und seiner einzigen
Tochter bei einem Autounfall starb. Ich habe Sie kontaktiert, um mich bei
der Rückführung von zwei Millionen fünfhunderttausend Dollar auf Ihr Konto
zu unterstützen. Bitte kontaktieren Sie mich für weitere Informationen zu
diesem Thema.


Bug#968841: marked as done (mozilla-devstripts FTBFS: tests/dh_xul-ext/test: No such file or directory)

2020-08-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Aug 2020 13:04:43 +
with message-id 
and subject line Bug#968841: fixed in mozilla-devscripts 0.54.2
has caused the Debian Bug report #968841,
regarding mozilla-devstripts FTBFS: tests/dh_xul-ext/test: No such file or 
directory
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.)


-- 
968841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mozilla-devscripts
X-Debbugs-Cc: d...@debian.org
Version: 0.54.1
Severity: serious
Justification: FTBFS

Dear maintainers, Matthias,

The latest upload of mozilla-devscripts FTBFS.

https://buildd.debian.org/status/fetch.php?pkg=mozilla-devscripts=all=0.54.1=1596924970=0

Command: dpkg-buildpackage -us -uc -mall / amd64 / i386 Build Daemon
(x86-conova-01)  -A
-rfakeroot
--changes-option=-O../mozilla-devscripts_0.54.1_all-buildd.changes
--buildinfo-option=-O../mozilla-devscripts_0.54.1_all-buildd.buildinfo
dpkg-buildpackage: info: source package mozilla-devscripts
dpkg-buildpackage: info: source version 0.54.1
dpkg-buildpackage: info: source distribution unstable
 dpkg-source --before-build .
dpkg-source: warning: relation > is deprecated: use >> or >=
dpkg-checkbuilddeps: warning: relation > is deprecated: use >> or >=
 fakeroot debian/rules clean
dh clean --with python2,python3
   dh_auto_clean
make -j4 clean
make[1]: Entering directory '/<>'
rm -rf build *.pyc
make[1]: Leaving directory '/<>'
   dh_clean
 debian/rules build-indep
dh build-indep --with python2,python3
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   dh_auto_build -i
make -j4 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
make[1]: Nothing to be done for 'build'.
make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j4 test
make[1]: Entering directory '/<>'
tests/dh_xul-ext/test
make[1]: tests/dh_xul-ext/test: No such file or directory
make[1]: *** [Makefile:4: test] Error 127
make[1]: Leaving directory '/<>'
dh_auto_test: error: make -j4 test returned exit code 2
make: *** [debian/rules:4: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned
exit status 2

Build finished at 2020-08-08T22:16:06Z


Paul

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

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

Versions of packages mozilla-devscripts depends on:
ii  perl   5.30.3-4
ii  python 2.7.17-2
pn  python-librdf  
ii  python22.7.17-2
ii  python33.8.2-3
ii  unzip  6.0-25
ii  zip3.0-11+b1

mozilla-devscripts recommends no packages.

mozilla-devscripts suggests no packages.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mozilla-devscripts
Source-Version: 0.54.2
Done: Ximin Luo 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Aug 2020 13:42:52 +0100
Source: mozilla-devscripts
Architecture: source
Version: 0.54.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers 

Changed-By: Ximin Luo 
Closes: 968841
Changes:
 mozilla-devscripts (0.54.2) unstable; urgency=medium
 .
   [ Simon McVittie ]
   * Change shebang on Python 2 scripts to #!/usr/bin/python2
 (Closes: #968841)
   * Use non-deprecated syntax for python-librdf dependency
   * Document the python-librdf change in the previous version
Checksums-Sha1:
 

Bug#969123: webext-ublock-origin: FF80 broke ublock again

2020-08-31 Thread Christoph Anton Mitterer
On Mon, 2020-08-31 at 10:12 +0200, Markus Koschany wrote:
> remove
> ~/.mozilla/firefox to create a new profile to get it working again.

Doesn't really sound like a "solution" to me (well except than taking
it as a trigger to finally move away from crappy FF).

It seems to have become fashion nowadays for *zilla to completely break
user setups every few versions... first breakage of thousands of
"legacy" add-ons... and now they even break their webext addon and the
only solution is re-creating a profile directory for which these is no
proper migration procedure and where most data is stored in some binary
format?!


Cheers,
Chris.



Processed: notfound 967230 in 1.4.0+dfsg-1

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 967230 1.4.0+dfsg-1
Bug #967230 {Done: Ximin Luo } [src:umatrix] umatrix: 
Unversioned Python removal in sid/bullseye
No longer marked as found in versions umatrix/1.4.0+dfsg-1.
> thanks
Stopping processing here.

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



Bug#936336: coz-profiler: Python2 removal in sid/bullseye

2020-08-31 Thread Lluís Vilanova
On Wed, Aug 12, 2020 at 3:27 PM Petter Reinholdtsen  wrote:
> I've managed to fix my key problems, and can do the upload.
>
> Is it ready to go in?

New releases of coz-profiler and libelfin are now available. Let me
prepare an upstream merge and I'll ping back here.

Cheers,
Lluis



Bug#966898: binutils-avr: FTBFS: elf.c:706:35: error: overflow in conversion from ‘unsigned int’ to ‘int’ changes value from ‘num_group = 4294967295’ to ‘-1’ [-Werror=overflow]

2020-08-31 Thread Gregor Riepl
> > elf.c: In function ‘setup_group’:
> > elf.c:706:35: error: overflow in conversion from ‘unsigned int’ to ‘int’ 
> > changes value from ‘num_group = 4294967295’ to ‘-1’ [-Werror=overflow]
> >   706 | elf_tdata (abfd)->num_group = num_group = -1;

Upstream bug is here:
https://sourceware.org/bugzilla/show_bug.cgi?id=25717

This was fixed upstream by:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=cda7e5603f6efd7c3716e45cc6ea11b70dd8daae

Looks like it's caused by GCC 10 being more picky about signedness.

> > In file included from elf.c:45:
> > elf.c: In function ‘elfcore_write_linux_prpsinfo32’:
> > elf-linux-psinfo.h:73:7: warning: ‘strncpy’ output may be truncated copying 
> > 16 bytes from a string of length 16 [-Wstringop-truncation]

This and the rest of the errors are false positives occurring from GCC 8
onwards. They have been silenced upstream:

https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=5a6312e8c015d4a98020038f3b6e144db230f3ca

https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=b9f26d2e29bb56a0404216c5612d6d7fee54a769

https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=d99b4b92c8ed0f7ef98f370bbf65a360ed66ad7b

https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=602f16570454a1597c2af28af66852133432d1f2

(there may be other patches as well)

Related bug reports:
https://sourceware.org/bugzilla/show_bug.cgi?id=23146
(can't find any that describe the original problem)

Also, please note that elf-linux-psinfo.h was renamed to
elf-linux-core.h upstream:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=de64ce13a78669f094d6909fce51d210e2f9d2c0

Perhaps it's time to replace the outdated Atmel versions of avr-gcc
avr-binutils and avr-libc in favour of the upstream versions?



Processed: tagging 957685

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

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

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



Bug#969313: marked as done (doxygen: fails to parse long configuration files from standard input)

2020-08-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Aug 2020 10:48:25 +
with message-id 
and subject line Bug#969313: fixed in doxygen 1.8.20-1~exp1
has caused the Debian Bug report #969313,
regarding doxygen: fails to parse long configuration files from standard input
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.)


-- 
969313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: doxygen
Version: 1.8.19-1
Severity: serious

when doxygen is invoked with the "-" parameter, it does not always do what is 
advertised in the doxygen manpage ("If - is used for configName doxygen will 
read from standard input")

due to a buffer size limit, only 4096 characters of the configuration file from 
standard input are read in and the rest is discarded

also see #969142

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

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

Versions of packages doxygen depends on:
ii  libc6  2.31-3
ii  libclang-cpp9  1:9.0.1-14
ii  libclang1-91:9.0.1-14
ii  libgcc-s1  10.2.0-5
ii  libllvm9   1:9.0.1-14
ii  libstdc++6 10.2.0-5
ii  libxapian301.4.17-1

doxygen recommends no packages.

Versions of packages doxygen suggests:
pn  doxygen-doc
pn  doxygen-gui
ii  doxygen-latex  1.8.19-1
ii  graphviz   2.42.2-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: doxygen
Source-Version: 1.8.20-1~exp1
Done: Paolo Greppi 

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

Debian distribution maintenance software
pp.
Paolo Greppi  (supplier of updated doxygen package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Aug 2020 10:27:21 +0200
Source: doxygen
Architecture: source
Version: 1.8.20-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Paolo Greppi 
Changed-By: Paolo Greppi 
Closes: 969313
Changes:
 doxygen (1.8.20-1~exp1) experimental; urgency=medium
 .
   * doxygen 1.8.20 release. Closes: #969313.
Checksums-Sha1:
 9bd6dcd3ef9ebacbaa85dcbcc70bc2e1a1ea8176 2781 doxygen_1.8.20-1~exp1.dsc
 c0105f7d1d45d24f134a9ba0d97baa6cbf547808 5065824 doxygen_1.8.20.orig.tar.gz
 d2e4a3e17ced263ccfce40340df7c44e5a396eed 27924 
doxygen_1.8.20-1~exp1.debian.tar.xz
 f4c85cc0516fb6b3c014b7ec6b0ae0aadb484efd 12865 
doxygen_1.8.20-1~exp1_source.buildinfo
Checksums-Sha256:
 b36b24c43861d57be1910060ae217c4dcf06554c2f867cab2b5896c4d2a8835e 2781 
doxygen_1.8.20-1~exp1.dsc
 3dbdf8814d6e68233d5149239cb1f0b40b4e7b32eef2fd53de8828fedd7aca15 5065824 
doxygen_1.8.20.orig.tar.gz
 4312f98580ac989549eee9db87d35ae5d93cc2492dea4535495e3ffefd985389 27924 
doxygen_1.8.20-1~exp1.debian.tar.xz
 dddfd61119193b49fe76dc055b01d2165de911a3c35fe814391f469b4e4dca21 12865 
doxygen_1.8.20-1~exp1_source.buildinfo
Files:
 d46739254ab10ef4bd5e559cb58e2b19 2781 devel optional doxygen_1.8.20-1~exp1.dsc
 9a740a5a58b54916619c6a9b97529f02 5065824 devel optional 
doxygen_1.8.20.orig.tar.gz
 170dcf1231fde4e92ff0318ea417ea9d 27924 devel optional 
doxygen_1.8.20-1~exp1.debian.tar.xz
 1d951911a595abfb29818fdcd555b024 12865 devel optional 
doxygen_1.8.20-1~exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEEyTpTRBhTUv5T0mHqIjkMJVxGBPQFAl9Mz/0XHHBhb2xvLmdy
ZXBwaUBsaWJwZi5jb20ACgkQIjkMJVxGBPRjYxAAxxapn76KS+aTWsHYowFxeQn6
a3SIr5BpGfiHTyktGbnGVAn2O8f6aqrY62m5YE+a+9eCli8YtdWO1jHzXoF3JfTn
YoVTG4xit3fbGaSMvVeqpNU8DVvSXVkr/VxaUcQKFgDAC1YhW+nRL1I1IAzbUs+T
RZLk6hqT9Z2ZrUP377kMJCqFnHX/MWQWP79qnGTKrxtE4cNFxyzPN/bJZKm9v4zo
s3XemVDQYCviJuHQtXzocSoNSYBQyqPQf1lr030n8jijiGZlBx455FywEP86OKam
ZzNxdDoSU8MU11S3Hn0ZK9YepavDuyYJeBF1ymabMheEqTCdoTxOd/tEg+M6rfB5
bsZ4Ls+CDJsBzUKvRt4navTyMtxSW5m0VKOlqMVbUCanqP4bJ9eIKpiYUbaQ8DeI

Bug#969317: paryfor: baseline violation on x86 and FTBFS everywhere else

2020-08-31 Thread Adrian Bunk
Source: paryfor
Version: 0.1-2
Severity: serious
Tags: ftbfs

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

Building with -mcx16 is a baseline violation on x86 and
a FTBFS everywhere else.

And unlikely to be necessary, according to the gcc documentation
the instruction is not even used for atomics.



Bug#969316: qtpim-opensource-src FTBFS: test failure

2020-08-31 Thread Adrian Bunk
Source: qtpim-opensource-src
Version: 5.0~git20190618.8fec622c+dfsg1-1
Severity: serious
Tags: ftbfs

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

...
FAIL!  : tst_QContactManager::compareVariant(datetimes dt0 > dt1) Compared 
values are not the same
   Actual   (comparison): -1
   Expected (expected)  : 1
   Loc: [tst_qcontactmanager.cpp(3150)]
...
Totals: 237 passed, 1 failed, 3 skipped, 0 blacklisted, 1043ms
* Finished testing of tst_QContactManager *
make[6]: *** [Makefile:388: check] Error 1



Bug#969315: pytsk FTBFS with sleuthkit 4.9.0

2020-08-31 Thread Adrian Bunk
Source: pytsk
Version: 20190507-1.1
Severity: serious
Tags: patch ftbfs

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

...
   dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:217: cd /<>/.pybuild/cpython3_3.8/build; python3.8 
-m unittest discover -v 
tests.test_lib (unittest.loader._FailedTest) ... ERROR

==
ERROR: tests.test_lib (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: tests.test_lib
Traceback (most recent call last):
  File "/usr/lib/python3.8/unittest/loader.py", line 436, in _find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3.8/unittest/loader.py", line 377, in 
_get_module_from_name
__import__(name)
  File "/<>/.pybuild/cpython3_3.8/build/tests/test_lib.py", line 
5, in 
import pytsk3
ImportError: 
/<>/.pybuild/cpython3_3.8/build/pytsk3.cpython-38-x86_64-linux-gnu.so:
 undefined symbol: libvmdk_handle_read_buffer_at_offset


--
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.8/build; python3.8 -m unittest discover -v 
dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit 
code 13
make: *** [debian/rules:8: build-arch] Error 25


Fix:

--- 
pytsk-20200117/debian/patches/0001-Link-system-tsk-statically-talloc-dynamically-instea.patch
   2020-08-28 00:27:28.0 +0300
+++ 
pytsk-20200117/debian/patches/0001-Link-system-tsk-statically-talloc-dynamically-instea.patch
   2020-08-31 12:36:28.0 +0300
@@ -80,7 +80,7 @@
 +"libraries": [ "talloc" ],
 +"extra_link_args": [
 +  "-Wl,-Bstatic", "-ltsk", "-Wl,-Bdynamic",
-+  "-lafflib", "-lewf", "-lstdc++", "-lz",
++  "-lafflib", "-lewf", "-lstdc++", "-lz", "-lvmdk", "-lvhdi",
 +]}
  
  # The sources to build.



Processed: bug 968875 is forwarded to https://github.com/rss2email/rss2email/issues/134

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 968875 https://github.com/rss2email/rss2email/issues/134
Bug #968875 [rss2email] rss2email forges envelope sender
Set Bug forwarded-to-address to 
'https://github.com/rss2email/rss2email/issues/134'.
> thanks
Stopping processing here.

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



Bug#967091: marked as done (pmemkv: FTBFS: tests failed)

2020-08-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Aug 2020 09:33:58 +
with message-id 
and subject line Bug#967091: fixed in pmemkv 1.2-2
has caused the Debian Bug report #967091,
regarding pmemkv: FTBFS: tests 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.)


-- 
967091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pmemkv
Version: 1.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200803 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 '/<>'
> cd obj-x86_64-linux-gnu && PMEM_IS_PMEM_FORCE=1 ctest --output-on-failure -j1
> Test project /<>/obj-x86_64-linux-gnu
> Start   7: config_c_0_memcheck
>   1/134 Test   #7: config_c_0_memcheck 
> ...
>Passed0.95 sec
> Start   9: config_cpp_0_memcheck
>   2/134 Test   #9: config_cpp_0_memcheck 
> .
>Passed0.97 sec
> Start  11: blackhole_test_0_memcheck
>   3/134 Test  #11: blackhole_test_0_memcheck 
> .
>Passed0.87 sec
> Start  13: json_to_config_0_memcheck
>   4/134 Test  #13: json_to_config_0_memcheck 
> .
>Passed0.96 sec
> Start  15: cmap__c_api_null_db_config__default_0_memcheck
>   5/134 Test  #15: cmap__c_api_null_db_config__default_0_memcheck 
>   
>  Passed0.98 sec
> Start  17: cmap__put_get_remove__default_0_memcheck
>   6/134 Test  #17: cmap__put_get_remove__default_0_memcheck 
> ..
>Passed1.32 sec
> Start  20: 
> cmap__put_get_remove_charset_params__default_16_8_0_memcheck
>   7/134 Test  #20: 
> cmap__put_get_remove_charset_params__default_16_8_0_memcheck 
> ..   Passed
> 1.82 sec
> Start  23: cmap__put_get_remove_long_key__default_0_memcheck
>   8/134 Test  #23: cmap__put_get_remove_long_key__default_0_memcheck 
> .   
> Passed1.27 sec
> Start  26: cmap__put_get_remove_params__default_4000_0_memcheck
>   9/134 Test  #26: cmap__put_get_remove_params__default_4000_0_memcheck 
> ..   
> Passed4.85 sec
> Start  29: cmap__put_get_std_map__default_1000_100_200_0_memcheck
>  10/134 Test  #29: cmap__put_get_std_map__default_1000_100_200_0_memcheck 
>    Passed 
>1.72 sec
> Start  32: cmap__iterate__default_0_memcheck
>  11/134 Test  #32: cmap__iterate__default_0_memcheck 
> .
>Passed1.28 sec
> Start  35: 
> cmap__concurrent_put_get_remove_params__default_8_50_0_memcheck
>  12/134 Test  #35: 
> cmap__concurrent_put_get_remove_params__default_8_50_0_memcheck 
> ...   Passed2.17 
> sec
> Start  37: 
> cmap__concurrent_put_get_remove_gen_params__default_8_50_100_0_memcheck
>  13/134 Test  #37: 
> cmap__concurrent_put_get_remove_gen_params__default_8_50_100_0_memcheck 
> ...   Passed2.17 sec
> Start  39: 
> cmap__concurrent_put_get_remove_single_op_params__default_400_0_memcheck
>  14/134 Test  #39: 
> cmap__concurrent_put_get_remove_single_op_params__default_400_0_memcheck 
> ..   Passed   30.03 sec
> Start  41: 
> cmap__persistent_put_get_std_map_multiple_reopen__default_1000_100_200_0_memcheck
>  15/134 Test  #41: 
> cmap__persistent_put_get_std_map_multiple_reopen__default_1000_100_200_0_memcheck
>  .   Passed6.00 sec
> Start  44: cmap__persistent_not_found_verify__insert_check_0_memcheck
>  16/134 Test  #44: 

Processed: forwarded upstream + pending

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 969313 
> https://github.com/doxygen/doxygen/issues/7951#issuecomment-671370005
Bug #969313 [doxygen] doxygen: fails to parse long configuration files from 
standard input
Set Bug forwarded-to-address to 
'https://github.com/doxygen/doxygen/issues/7951#issuecomment-671370005'.
> tag 969313 pending
Bug #969313 [doxygen] doxygen: fails to parse long configuration files from 
standard input
Added tag(s) pending.
>
End of message, stopping processing here.

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



Bug#967128: marked as done (dispmua: Unversioned Python removal in sid/bullseye)

2020-08-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Aug 2020 10:45:23 +0200
with message-id <3611658d-fa71-67a7-c683-e6a5b6015...@debian.org>
and subject line Re: dispmua: Unversioned Python removal in sid/bullseye
has caused the Debian Bug report #967128,
regarding dispmua: 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.)


-- 
967128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dispmua
Version: 1.8.4.6-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 ---
dispmua does neither directly depend on python nor does it ship any
python code. It was affected by #967175 in mozilla-devscripts but since
this one has been resolved, I think we can close this bug report here now.




signature.asc
Description: OpenPGP digital signature
--- End Message ---


Bug#969313: doxygen: fails to parse long configuration files from standard input

2020-08-31 Thread Paolo Greppi
Package: doxygen
Version: 1.8.19-1
Severity: serious

when doxygen is invoked with the "-" parameter, it does not always do what is 
advertised in the doxygen manpage ("If - is used for configName doxygen will 
read from standard input")

due to a buffer size limit, only 4096 characters of the configuration file from 
standard input are read in and the rest is discarded

also see #969142

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

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

Versions of packages doxygen depends on:
ii  libc6  2.31-3
ii  libclang-cpp9  1:9.0.1-14
ii  libclang1-91:9.0.1-14
ii  libgcc-s1  10.2.0-5
ii  libllvm9   1:9.0.1-14
ii  libstdc++6 10.2.0-5
ii  libxapian301.4.17-1

doxygen recommends no packages.

Versions of packages doxygen suggests:
pn  doxygen-doc
pn  doxygen-gui
ii  doxygen-latex  1.8.19-1
ii  graphviz   2.42.2-4

-- no debconf information



Bug#950675: upstream does support doxygen-latex, but ...

2020-08-31 Thread Paolo Greppi
Hi Simon, thanks for revving the conversation on this bug. I'll summarize below 
my points.

Il 20/08/20 11:08, Simon McVittie ha scritto:
> On Wed, 05 Feb 2020 at 11:56:16 +0100, Paolo Greppi wrote:
> ...
> smcv
> 

- in general printable documentation is less relevant now than it used to be

- but some people may still need it, so doxygen-latex is useful in general, it 
mostly works fine, and we should try to keep it in Debian

- occasionally packages that build printable documentation (PDF or PS) with 
doxygen-latex have tripped (and will trip in the future) on obscure bugs in 
latex or doxygen or doxygen-latex or some-fancy-latex-plugin

- when this happens, I'll try to address it with the help of upstream, the 
latex maintainer and the latex community, but it may take a long time to fix or 
may be practically impossible to fix (because it's a messy tangle of old 
software, or because some-fancy-latex-plugin is no more supported, or some 
other obscure reason)

- when that takes really too long, on a case-by-case basis, and as a last 
resort, I would suggest the maintainers of those specific packages to 
(temporarily) drop PDF/PS documentation and only produce HTML docs, or to work 
with their upstream to switch to other PDF/PS generation toolchains as was 
suggested by Dimitri

In conclusion, I'll downgrade this bug to non-RC and if Aurelien is OK, I 
propose to close it.

Paolo



Processed: downgrade

2020-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 950675 normal
Bug #950675 [doxygen] doxygen-latex is now useless, should be removed from the 
archive?
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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



Bug#969284: marked as done (xorg-server: FTBFS: configure: error: Xwayland build explicitly requested, but required modules not found)

2020-08-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Aug 2020 08:21:36 +
with message-id 
and subject line Bug#969284: fixed in wayland 1.18.0-2~exp1.1
has caused the Debian Bug report #969284,
regarding xorg-server: FTBFS: configure: error: Xwayland build explicitly 
requested, but required modules not 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.)


-- 
969284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xorg-server
Version: 2:1.20.8-2
Severity: serious
Justification: FTBFS
X-Debbugs-Cc: car...@debian.org

Hi

When trying to build xorg-server 2:1.20.8-2 in unstable, the build
fails (on configure already) with:

configure: error: Xwayland build explicitly requested, but required modules not 
found

full build log though attached (and I have not further checked if
another dependency is actually at fault).

Regards,
Salvatore


xorg-server_1.20.8-2_amd64.build.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Source: wayland
Source-Version: 1.18.0-2~exp1.1
Done: Julien Cristau 

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated wayland package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Aug 2020 10:10:12 +0200
Source: wayland
Architecture: source
Version: 1.18.0-2~exp1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Closes: 969284
Changes:
 wayland (1.18.0-2~exp1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add missing dependency on libffi-dev (closes: #969284).
Checksums-Sha1:
 28fc959473dac029aaa6f254f7d5fa82c5502999 2629 wayland_1.18.0-2~exp1.1.dsc
 5a97658c29b4970af47194634d5547ba536a630d 16884 wayland_1.18.0-2~exp1.1.diff.gz
Checksums-Sha256:
 72ade67239aee78630cf2c400b3fc2d4572462d5c5ea3688b2bed743cf8f672c 2629 
wayland_1.18.0-2~exp1.1.dsc
 ad94e458a70fdd5bb39f71648708640b69e12f24b93cb8480086df37fb0b5462 16884 
wayland_1.18.0-2~exp1.1.diff.gz
Files:
 22e928674b32604fdf4c3c1f8d1cc97f 2629 x11 optional wayland_1.18.0-2~exp1.1.dsc
 c2fc8af6df0c446d35be5ac45d682992 16884 x11 optional 
wayland_1.18.0-2~exp1.1.diff.gz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAl9MsOMUHGpjcmlzdGF1
QGRlYmlhbi5vcmcACgkQnbAjVVb4z618Ww//XK3/ez3ZT3Iao73thEcpZGKSpC0E
W75vraB239bupkc/NONxch7KQiXQGo25Z5OHOdgIZbc+H6r1oB/OWOXeh+GqNHjw
cO9dEvSysGw66DB/IWBLcg3hk05ViD2VViOqitKwjuBPCiQtmCcOTBPrK48EB2Go
q+/Y2sVuW7JuS8DLYSUyKrqmjqAbJ8P+7g8RsH8w3/s/nYvYE0f9mBQFBFvO39CV
IVoXxwicWelbiAZ0j30Re4j4UKZYM2evzrgHC2SFiclJeMqNTpAfvBpBl8pMcLm7
nqVphuM9F/E3OBCecnuhxweRZGsxQpYfg4BHi8u3rG6rhoYWEb5M1gKfMglvcDdO
DTsf7zPHdxWAAxXWTgo09GwZCXsd4GR5ucRGs3nzPe22fW0xzWnjcEZLjRm0qq8t
En5eI3jaq2ANNmSayvyix7cJYvT4kA2De+EP63InDPJnkavFfGITLG+88KU5u0CI
9OroGTD9q9zA4sTaeMQpIFtFV7+p4zwzGZDzVLSX9sAIj3w/e/R3QMXBwD+x1kT4
cIgHP6zRTB4cUjjMGGmgJbCHmL8bg0PBACmZVBUk/WFnnVWAtoFcE3uhuLxcoehH
Ld85LkRJEV0yJvgUk3F9yrUWg2Lb0cIhgKfceMUlTyySE+TgqtkXuCTXu6kuvvGH
IGJPsAJAiP82vEw=
=0da0
-END PGP SIGNATURE End Message ---


Bug#967950: marked as done (doxygen: Autopkgtest regression with json-c 0.15)

2020-08-31 Thread Debian Bug Tracking System
Your message dated Mon, 31 Aug 2020 08:20:59 +
with message-id 
and subject line Bug#967950: fixed in doxygen 1.8.19-1
has caused the Debian Bug report #967950,
regarding doxygen: Autopkgtest regression with json-c 0.15
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.)


-- 
967950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doxygen
Version: 1.8.18-1
Severity: serious
Justification: failing autopkgtest on amd64

Dear Maintainer,

doxygen autopkgtest started failing after json-c 0.15-1 was uploaded to
unstable. This blocks migration of some other packages:

https://ci.debian.net/user/britney/jobs?package=doxygen

See any of the “test log” links for the log, for example this one:

https://ci.debian.net/data/autopkgtest/testing/amd64/d/doxygen/6526799/log.gz

The relevant line is:

  error: Doxyfile not found and no input file specified!

Attached is a patch that adapts the test to work with new json-c.

However, I think it would be better if that test did not rely on any external
data, and the needed data was shipped with doxygen itself. Maybe the test can
build doxygen's own documentation?

--
Dmitry Shachnev
diff --git a/debian/tests/control b/debian/tests/control
index f46086a..d707d73 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,2 +1,7 @@
 Tests: run
-Depends: apt:native, dpkg-dev, doxygen, graphviz:native
+Depends: apt:native,
+ build-essential,
+ cmake:native,
+ doxygen,
+ dpkg-dev,
+ graphviz:native
diff --git a/debian/tests/run b/debian/tests/run
index 31e4da5..f84a376 100755
--- a/debian/tests/run
+++ b/debian/tests/run
@@ -7,6 +7,10 @@ trap "rm -rf $WORKDIR" 0 INT QUIT ABRT PIPE TERM
 cd $WORKDIR
 apt-get source json-c 2>&1
 cd json-c-*
+mkdir build
+cd build
+cmake ..
+cd doc
 doxygen 2>&1
 cd /
 rm -Rf "$WORKDIR"


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: doxygen
Source-Version: 1.8.19-1
Done: Paolo Greppi 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Aug 2020 09:36:22 +0200
Source: doxygen
Architecture: source
Version: 1.8.19-1
Distribution: unstable
Urgency: medium
Maintainer: Paolo Greppi 
Changed-By: Paolo Greppi 
Closes: 967950 968340
Changes:
 doxygen (1.8.19-1) unstable; urgency=medium
 .
   * Upload to unstable. Closes: #967950, #968340.
Checksums-Sha1:
 481bdfa61ead6181fa89419148fd8203b2145592 2761 doxygen_1.8.19-1.dsc
 55e21b1a90f2e0d75fcd34c2fd52105d99ab94fe 27904 doxygen_1.8.19-1.debian.tar.xz
 0ad5364f3fb594f3d5f5e90fa67f0c6261ec438d 12845 
doxygen_1.8.19-1_source.buildinfo
Checksums-Sha256:
 984f814685324c8bf22e69fdba69b6476c38bd1ecb212c2c4a4e7c2fad8a93a5 2761 
doxygen_1.8.19-1.dsc
 6875b58318f1277c679929e9c3daa3a260f3133a7052933842f05b98c345df93 27904 
doxygen_1.8.19-1.debian.tar.xz
 19df6a718ca243568f44056c4948c81ac4ac4dc51dca7daf7632ae9d45e09302 12845 
doxygen_1.8.19-1_source.buildinfo
Files:
 d811fe9e2a630f7c9b3ac27fdacad807 2761 devel optional doxygen_1.8.19-1.dsc
 888240bf2352c1209320ed30e7fd4c5f 27904 devel optional 
doxygen_1.8.19-1.debian.tar.xz
 7d5df72b18d6840755c3a6711278514f 12845 devel optional 
doxygen_1.8.19-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEEyTpTRBhTUv5T0mHqIjkMJVxGBPQFAl9MqOMXHHBhb2xvLmdy
ZXBwaUBsaWJwZi5jb20ACgkQIjkMJVxGBPRuJA//SBNPZgH7KT3/0ESLxa7LtD7A
3gjoLhNDUrVc96soNlZ2laxPIdaLgPgZ779wmI/T3hVa8niCQJ2B/uLVhBrdA45x
mb8d2YAKDF43YpIpLRD7ayGavAJpayoH701AGG20doPAnAFGmqPKJsL1mB6JtI2B
UovGv4LEAU2kiFkbd+NG4QCDBBEhRrYBcVQplCuJXWtGOJ1tu7dgM7Ij0xd4/ask
m2Ay7JeNQVj8rBNipvohvknYeEZH+cgYKJ9+rdRm8KdUIFOs+0LtXTN+YVFY9dWv
a4giLGHCkVXy+S0/gidEWG8cN6YZeUv/Nwc3sSlP4f7DnqAXdzLcXFLLl9s86EjF
QEnpLiltdiVq7+AE8q9vsk1wvlq4RJTurY7OtZ1G/zHUb0yYwplNI6/BwW4zcnAb
E9WosYB/Uaed7R0eCBVc22b1BVVDcWbrGltkoYJV0xRU8MNYirQBuHteWClINvrJ

Bug#969123: webext-ublock-origin: FF80 broke ublock again

2020-08-31 Thread Markus Koschany
On Sat, 29 Aug 2020 01:37:27 +0200 Christoph Anton Mitterer
 wrote:
[...]
> Interestingly it seems other (all) add-ons are broken too, at least for
> me... but not when I create fresh profiles.

I stand corrected. Apparently this is a similar problem like


https://bugs.debian.org/931640

Disabling and re-enabling the addons should work or you can remove
~/.mozilla/firefox to create a new profile to get it working again. I
don't know how we can fix that in Debian because the bug affects the
home directory of the user. I intend to add this information to
README.Debian but if someone knows a better solution, please let us know.

Markus



signature.asc
Description: OpenPGP digital signature


Bug#969284: xorg-server: FTBFS: configure: error: Xwayland build explicitly requested, but required modules not found

2020-08-31 Thread Julien Cristau
Control: reassign -1 libwayland-dev 1.18.0-2~exp1
Control: affects -1 + src:xorg-server

On Sun, Aug 30, 2020 at 09:21:55PM +0200, Salvatore Bonaccorso wrote:
> Source: xorg-server
> Version: 2:1.20.8-2
> Severity: serious
> Justification: FTBFS
> X-Debbugs-Cc: car...@debian.org
> 
> Hi
> 
> When trying to build xorg-server 2:1.20.8-2 in unstable, the build
> fails (on configure already) with:
> 
> configure: error: Xwayland build explicitly requested, but required modules 
> not found
> 
> full build log though attached (and I have not further checked if
> another dependency is actually at fault).
> 
Log says:

Package 'libffi', required by 'wayland-client', not found

Cheers,
Julien



Processed: Re: Bug#969284: xorg-server: FTBFS: configure: error: Xwayland build explicitly requested, but required modules not found

2020-08-31 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 libwayland-dev 1.18.0-2~exp1
Bug #969284 [src:xorg-server] xorg-server: FTBFS: configure: error: Xwayland 
build explicitly requested, but required modules not found
Bug reassigned from package 'src:xorg-server' to 'libwayland-dev'.
No longer marked as found in versions xorg-server/2:1.20.8-2.
Ignoring request to alter fixed versions of bug #969284 to the same values 
previously set
Bug #969284 [libwayland-dev] xorg-server: FTBFS: configure: error: Xwayland 
build explicitly requested, but required modules not found
Marked as found in versions wayland/1.18.0-2~exp1.
> affects -1 + src:xorg-server
Bug #969284 [libwayland-dev] xorg-server: FTBFS: configure: error: Xwayland 
build explicitly requested, but required modules not found
Added indication that 969284 affects src:xorg-server

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



Processed: Bug#969227 marked as pending in docker.io

2020-08-31 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #969227 [docker.io] FTBFS with new runc 1.0.0~rc92 and libcap2 2.43
Added tag(s) pending.

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



Bug#969227: marked as pending in docker.io

2020-08-31 Thread Arnaud Rebillout
Control: tag -1 pending

Hello,

Bug #969227 in docker.io 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/docker-team/docker/-/commit/ad52cffa31359262a8e9d44daddf896c3e063dd2


Fix build against runc 1.0.0~rc92 (zhsj) (Closes: #969227)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/969227



Bug#957859: t4kcommon: ftbfs with GCC-10

2020-08-31 Thread Antoni Villalonga
Please consider adding attached patch.

Salsa Merge Request:
  https://salsa.debian.org/tux4kids-pkg-team/t4kcommon/-/merge_requests/1

Regards,

-- 
Antoni Villalonga
https://friki.cat/
Description: fix ftbfs with GCC-10
 Fix wrapped_lines variable declaration (extern)
Author: ant...@friki.cat
Forwarded: https://github.com/tux4kids/t4kcommon/pull/8
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/t4k_common.h
+++ b/src/t4k_common.h
@@ -239,7 +239,7 @@ MFStrategy;
 #define MAX_LINES 128 //!< Maximum lines to wrap.
 #define MAX_LINEWIDTH 256 //!< Maximum characters of each line.
 
-char wrapped_lines[MAX_LINES][MAX_LINEWIDTH]; //!< Global buffer for wrapped lines.
+extern char wrapped_lines[MAX_LINES][MAX_LINEWIDTH]; //!< Global buffer for wrapped lines.
 
 //TODO separate headers for different areas a la SDL?