Bug#992234: marked as done (uninstallable; incompatible with tmux 3.2)

2021-08-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Aug 2021 06:53:08 +
with message-id 
and subject line Bug#992233: fixed in tmuxinator 3.0.1-1
has caused the Debian Bug report #992233,
regarding uninstallable; incompatible with tmux 3.2
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.)


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

tmux 3.2a is now in sid, which makes tmuxinator uninstallable because it
is apparently incompatible and has the following Depends field:

Depends: ruby | ruby-interpreter, ruby-erubis, ruby-thor, ruby-xdg, tmux (<< 
3.2)

Please update the package to a compatible version ASAP as this will
prevent tmux from migrating to bookworm properly.

Thanks.
--- End Message ---
--- Begin Message ---
Source: tmuxinator
Source-Version: 3.0.1-1
Done: Youhei SASAKI 

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

Debian distribution maintenance software
pp.
Youhei SASAKI  (supplier of updated tmuxinator package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 Aug 2021 14:50:20 +0900
Source: tmuxinator
Architecture: source
Version: 3.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Youhei SASAKI 
Closes: 980736 992233
Changes:
 tmuxinator (3.0.1-1) unstable; urgency=medium
 .
   * New upstream version 3.0.1
   * Bump debhelper from old 12 to 13.
   * Update standards version to 4.5.1, no changes needed.
   * Relaxed version dependency (Closes: #992233)
   * Install bash-completion via Debian way (Closes: #980736)
Checksums-Sha1:
 647710f132cdc226e968c9d3ba9483d6fdb59abf 2194 tmuxinator_3.0.1-1.dsc
 e78ced25a27c480ee7eab4b2c589b63662defa19 50436 tmuxinator_3.0.1.orig.tar.gz
 1daee6af92022a6058c93b1ac49d3652c2e95303 4988 tmuxinator_3.0.1-1.debian.tar.xz
 61b26f311478bb3facc3dd9f97440ac565113eaa 10405 
tmuxinator_3.0.1-1_amd64.buildinfo
Checksums-Sha256:
 35b2edb5a2d6f4cdd6c1a5c1a69d7e1fb13ac53b59f4e1e0db33181ac91d6d19 2194 
tmuxinator_3.0.1-1.dsc
 1d79dd13beaaf2ed24c8a76410c1a41bedc7785498e199534fa3928bbf8aab01 50436 
tmuxinator_3.0.1.orig.tar.gz
 c472722a1d1650c0e9d80f91774cefd9959920c7e301a64cd4cf7c3d912b70a6 4988 
tmuxinator_3.0.1-1.debian.tar.xz
 41fea984627c30d6114548c1dbde540b71c5ffe632ed6cdc79e85ef65e074c24 10405 
tmuxinator_3.0.1-1_amd64.buildinfo
Files:
 cd325a2180a044a17a0b2433409984ff 2194 utils optional tmuxinator_3.0.1-1.dsc
 26e146fc55ddb90265aa6e37d2e4cb7c 50436 utils optional 
tmuxinator_3.0.1.orig.tar.gz
 7593b1284b0977d005e076e8fadbaf2a 4988 utils optional 
tmuxinator_3.0.1-1.debian.tar.xz
 03541157d5b0ee690326141993ef424c 10405 utils optional 
tmuxinator_3.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZqTqcE/iQFWNasLmk5TzVIkdfgcFAmEbVEUACgkQk5TzVIkd
fgcjsA/7BmUEtOxomcPE6SX9T+Daar/e55OFvXDdI99jt4O6W1wUC5mOTuWcxvD1
EM8UZiwgH7mK/LNikb7j04B7nsh8eoxWBH92tV0q6PjRyzlOa3fdvsL/K3A1jise
N5PcmL1T+TWmqvpfkzfWurr2MHf911ubpD+UjUuaqDyj/ZIclIYf73glqF8EaEUT
fMK7hbmxoGaOk1bQ3L0UlmwafOV/nicOKXKw8ILDefKxKKWvCT3bKxABIxwKqIbB
LohQpZyPbtQFBxasNvNpQu8HnlDwOdoARAx4lb8dLNdHNxaP6JRIa2ArTsY9Fqjn
mHKUKJ7KUqR/bZHjY28/aMXFCyPy+WvEKFFxoiWfADwcCciP6YayMEh9wuHPyq/Y
IG5F9FZ1uSnZvHRzlFMSK4wIj0jgmvku07YI05jEeSZ5d9UXMpDwYhw0pA+mEcVo
kXuUZjqgcfriSaXfC0iWJqst6MndnmvQ2TBbQbkE5IoFwfo7e6d8sHc0Mnt1jqB/
XCXQ+CmpEuce1hmFR9SOSGvigUfQsfwwZHEZMbB+xjCaHOdkVMGbWxT1N/j1vhyp
PJvV+LfR+HLU3kB7lR9e3FzI/I2WhJzpO1UswacLvv13zWQtaV5XsOu8xyqctTaa
09uXH8BqFj/yfTcgGWbCg9wOO3ctZNQzDrLd7rNL4rT+zBy36lY=
=lNXB
-END PGP SIGNATURE End Message ---


Bug#992233: marked as done (tmuxinator: Uninstallable due to new tmux version)

2021-08-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Aug 2021 06:53:08 +
with message-id 
and subject line Bug#992233: fixed in tmuxinator 3.0.1-1
has caused the Debian Bug report #992233,
regarding tmuxinator: Uninstallable due to new tmux version
to be marked as done.

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

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


-- 
992233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tmuxinator
Version: 2.0.2-1
Severity: serious
Tags: sid bookmworm

With the recent upload of tmux 3.2a-3 to unstable, tmuxinator became
uninstallable in Debian Unstable:

# aptitude install tmuxinator
The following NEW packages will be installed:
  tmuxinator{b}
0 packages upgraded, 1 newly installed and 0 to remove.
Need to get 23.6 kB of archives. After unpacking 104 kB will be used.
The following packages have unmet dependencies:
 tmuxinator : Depends: ruby-xdg but it is not going to be installed
  Depends: tmux (< 3.2) but 3.2a-3 is installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) tmuxinator [Not Installed]

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: tmuxinator
Source-Version: 3.0.1-1
Done: Youhei SASAKI 

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

Debian distribution maintenance software
pp.
Youhei SASAKI  (supplier of updated tmuxinator package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 Aug 2021 14:50:20 +0900
Source: tmuxinator
Architecture: source
Version: 3.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Youhei SASAKI 
Closes: 980736 992233
Changes:
 tmuxinator (3.0.1-1) unstable; urgency=medium
 .
   * New upstream version 3.0.1
   * Bump debhelper from old 12 to 13.
   * Update standards version to 4.5.1, no changes needed.
   * Relaxed version dependency (Closes: #992233)
   * Install bash-completion via Debian way (Closes: #980736)
Checksums-Sha1:
 647710f132cdc226e968c9d3ba9483d6fdb59abf 2194 tmuxinator_3.0.1-1.dsc
 e78ced25a27c480ee7eab4b2c589b63662defa19 50436 tmuxinator_3.0.1.orig.tar.gz
 1daee6af92022a6058c93b1ac49d3652c2e95303 4988 tmuxinator_3.0.1-1.debian.tar.xz
 61b26f311478bb3facc3dd9f97440ac565113eaa 10405 
tmuxinator_3.0.1-1_amd64.buildinfo
Checksums-Sha256:
 35b2edb5a2d6f4cdd6c1a5c1a69d7e1fb13ac53b59f4e1e0db33181ac91d6d19 2194 
tmuxinator_3.0.1-1.dsc
 1d79dd13beaaf2ed24c8a76410c1a41bedc7785498e199534fa3928bbf8aab01 50436 
tmuxinator_3.0.1.orig.tar.gz
 c472722a1d1650c0e9d80f91774cefd9959920c7e301a64cd4cf7c3d912b70a6 4988 
tmuxinator_3.0.1-1.debian.tar.xz
 41fea984627c30d6114548c1dbde540b71c5ffe632ed6cdc79e85ef65e074c24 10405 
tmuxinator_3.0.1-1_amd64.buildinfo
Files:
 cd325a2180a044a17a0b2433409984ff 2194 utils optional tmuxinator_3.0.1-1.dsc
 26e146fc55ddb90265aa6e37d2e4cb7c 50436 utils optional 
tmuxinator_3.0.1.orig.tar.gz
 7593b1284b0977d005e076e8fadbaf2a 4988 utils optional 
tmuxinator_3.0.1-1.debian.tar.xz
 03541157d5b0ee690326141993ef424c 10405 utils optional 
tmuxinator_3.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZqTqcE/iQFWNasLmk5TzVIkdfgcFAmEbVEUACgkQk5TzVIkd
fgcjsA/7BmUEtOxomcPE6SX9T+Daar/e55OFvXDdI99jt4O6W1wUC5mOTuWcxvD1
EM8UZiwgH7mK/LNikb7j04B7nsh8eoxWBH92tV0q6PjRyzlOa3fdvsL/K3A1jise
N5PcmL1T+TWmqvpfkzfWurr2MHf911ubpD+UjUuaqDyj/ZIclIYf73glqF8EaEUT
fMK7hbmxoGaOk1bQ3L0UlmwafOV/nicOKXKw8ILDefKxKKWvCT3bKxABIxwKqIbB
LohQpZyPbtQFBxasNvNpQu8HnlDwOdoARAx4lb8dLNdHNxaP6JRIa2ArTsY9Fqjn
mHKUKJ7KUqR/b

Bug#992233: marked as pending in tmuxinator

2021-08-16 Thread Youhei SASAKI
Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/tmuxinator/-/commit/edf1555fe0711e2ba50e25568572def69076e613


Relaxed version dependency (Closes: #992233)

Signed-off-by: Youhei SASAKI 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/992233



Processed: Bug#992233 marked as pending in tmuxinator

2021-08-16 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #992233 [tmuxinator] tmuxinator: Uninstallable due to new tmux version
Bug #992234 [tmuxinator] uninstallable; incompatible with tmux 3.2
Added tag(s) pending.
Added tag(s) pending.

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



Bug#992319: RM: nekobee -- RoQA, unmaintained, RC-buggy, dead-upstream, python2

2021-08-16 Thread Tobias Frost
Package: nekobee
Severity: serious

nekobee is currently RC buggy with 2 RC bugs, (one being a gcc 10 and one being
a python-removal-bug;  upstream seems dead as well with only a minor commit last
year.
The Debian package has seen the last upload 5 years ago, and missed bullseye,
so it looks unmaintained from here.

I guess this software is EOL and should probably be removed from the archives.

Dear maintainer,

If you disagree, just close this bug.
If you agree, please reassign this bug to ftp.d.o to make the RM happening.
I will do the latter in exactly 3 months from now if there is no answer on this 
bug.

--  
tobi



Processed: Re: nekobee: ftbfs with GCC-10

2021-08-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 -fixed-upstream
Bug #957588 [src:nekobee] nekobee: ftbfs with GCC-10
Removed tag(s) fixed-upstream.
> notforwarded -1
Bug #957588 [src:nekobee] nekobee: ftbfs with GCC-10
Unset Bug forwarded-to-address

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



Bug#957588: nekobee: ftbfs with GCC-10

2021-08-16 Thread Tobias Frost
Control: tags -1 -fixed-upstream
Control: notforwarded -1

The bug has been marked as forwarded to 
>  https://github.com/Caltech-IPAC/Montage/issues/49

however, this is a different project; upstream is at
> https://github.com/gordonjcp/nekobee

So I guess the original forwarding is not correct;
removing the tag and forwarded notation.

-- 
tobi



Processed: latencytop: diff for NMU version 0.5-0.1

2021-08-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 +patch +pending
Bug #947051 [src:latencytop] latencytop: Non-sensical source format and version
Added tag(s) patch.
Bug #947051 [src:latencytop] latencytop: Non-sensical source format and version
Added tag(s) pending.

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



Bug#947051: latencytop: diff for NMU version 0.5-0.1

2021-08-16 Thread Boyuan Yang
Control: tags -1 +patch +pending

Dear maintainer,

I've prepared an NMU for latencytop (versioned as 0.5-0.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru latencytop-0.5/debian/changelog latencytop-0.5/debian/changelog
--- latencytop-0.5/debian/changelog 2021-08-17 00:27:59.0 -0400
+++ latencytop-0.5/debian/changelog 2021-08-17 00:21:33.0 -0400
@@ -1,3 +1,23 @@
+latencytop (0.5-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to "3.0 (quilt)" source format for a sanity.
+(Closes: #947051)
+  * debian/rules: Convert to dh sequencer.
+  * debian/patches/0001-Convert-to-autoconf.patch: Convert buildsystem
+to autotools for better compatibility.
++ Fixes cross compilation. (Closes: #900303)
+  * debian/patches/0002-Fix-FTBFS-in-fsync.c.patch: Fix FTBFS with
+clang. (Closes: #760285)
+  * debian/patches/0003-typo-fix.patch: Fix typo in man page.
+(Closes: #619490)
+  * debian/control:
++ Add packaging VCS field (Debian Salsa GitLab).
++ Bump debhelper compat to v13. Closes: #965618
++ Bump Standards-Version to 4.5.1.
+
+ -- Boyuan Yang   Tue, 17 Aug 2021 00:21:33 -0400
+
 latencytop (0.5) unstable; urgency=low
 
   * New upstream version (
diff -Nru latencytop-0.5/debian/compat latencytop-0.5/debian/compat
--- latencytop-0.5/debian/compat2021-08-17 00:27:59.0 -0400
+++ latencytop-0.5/debian/compat1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-5
diff -Nru latencytop-0.5/debian/control latencytop-0.5/debian/control
--- latencytop-0.5/debian/control   2021-08-17 00:27:59.0 -0400
+++ latencytop-0.5/debian/control   2021-08-17 00:18:49.0 -0400
@@ -1,11 +1,13 @@
 Source: latencytop
 Section: utils
-Priority: extra
+Priority: optional
 Maintainer: Giacomo Catenazzi 
-Build-Depends: cdbs, debhelper (>= 5), pkg-config, libncursesw5-dev,
+Build-Depends: debhelper-compat (= 13), pkg-config, libncurses-dev,
   libglib2.0-dev, libgtk2.0-dev
-Standards-Version: 3.8.2
+Standards-Version: 4.5.1
 Homepage: http://www.latencytop.org/
+Vcs-Git: https://salsa.debian.org/debian/latencytop.git
+Vcs-Browser: https://salsa.debian.org/debian/latencytop
 
 Package: latencytop
 Architecture: any
diff -Nru latencytop-0.5/debian/latencytop.dirs latencytop-
0.5/debian/latencytop.dirs
--- latencytop-0.5/debian/latencytop.dirs   2021-08-17 00:27:59.0
-0400
+++ latencytop-0.5/debian/latencytop.dirs   1969-12-31 19:00:00.0
-0500
@@ -1,2 +0,0 @@
-usr/sbin
-usr/share/latencytop
diff -Nru latencytop-0.5/debian/patches/0001-Convert-to-autoconf.patch
latencytop-0.5/debian/patches/0001-Convert-to-autoconf.patch
--- latencytop-0.5/debian/patches/0001-Convert-to-autoconf.patch1969-
12-31 19:00:00.0 -0500
+++ latencytop-0.5/debian/patches/0001-Convert-to-autoconf.patch2021-
08-17 00:18:49.0 -0400
@@ -0,0 +1,72 @@
+From: Boyuan Yang 
+Date: Mon, 16 Aug 2021 12:10:37 -0400
+Subject: Convert to autoconf
+
+---
+ Makefile.am | 11 +++
+ configure.ac| 33 +
+ m4/.placeholder |  0
+ 3 files changed, 44 insertions(+)
+ create mode 100644 Makefile.am
+ create mode 100644 configure.ac
+ create mode 100644 m4/.placeholder
+
+diff --git a/Makefile.am b/Makefile.am
+new file mode 100644
+index 000..5fb764d
+--- /dev/null
 b/Makefile.am
+@@ -0,0 +1,11 @@
++ACLOCAL_AMFLAGS = -I m4
++
++sbin_PROGRAMS = latencytop
++
++latencytop_CFLAGS = -DHAS_GTK_GUI
++latencytop_CFLAGS += $(GLIB_CFLAGS) $(GTK2_CFLAGS)
++latencytop_SOURCES = latencytop.c text_display.c translate.c fsync.c
gtk_display.c
++latencytop_LDADD = $(GLIB_LIBS) $(GTK2_LIBS)
++
++latencytopdatadir = $(datadir)/latencytop
++latencytopdata_DATA = latencytop.trans global.png kernel_thread.png
user_process.png
+diff --git a/configure.ac b/configure.ac
+new file mode 100644
+index 000..96063a1
+--- /dev/null
 b/configure.ac
+@@ -0,0 +1,33 @@
++#   -*- Autoconf -*-
++# Process this file with autoconf to produce a configure script.
++
++AC_PREREQ([2.69])
++AC_INIT([latencytop], [0.5], [http://www.latencytop.org/])
++AC_CONFIG_SRCDIR([gtk_display.c])
++AC_CONFIG_HEADERS([config.h])
++AC_CONFIG_AUX_DIR([build-aux])
++
++AM_INIT_AUTOMAKE([foreign])
++
++# Checks for programs.
++AC_PROG_CC
++AC_PROG_INSTALL
++
++# Checks for libraries.
++AC_CHECK_LIB([ncursesw], [initscr])
++
++PKG_CHECK_MODULES([GLIB], [glib-2.0])
++PKG_CHECK_MODULES([GTK2], [gtk+-2.0])
++
++# Checks for header files.
++AC_CHECK_HEADERS([stdlib.h string.h sys/time.h unistd.h wchar.h])
++
++# Checks for typedefs, structures, and compiler characteristics.
++AC_TYPE_SIZE_T
++
++# Checks for library functions.
++AC_FUNC_MALLOC
++AC_CHECK_FUNCS([atexit gettimeofday memset select strchr strdup strstr
strtoull])
++
++AC_CONFIG_FILES([Makefile])
++AC_OUTPUT
+diff --git a/m4/.placeholder b/m4/.placeholder
+new 

Bug#992281: marked as done (libunistring FTBFS: configure.ac:25: error: AC_INIT should be called with package and version arguments)

2021-08-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 Aug 2021 23:51:47 +
with message-id 
and subject line Bug#992281: fixed in libunistring 0.9.10-6
has caused the Debian Bug report #992281,
regarding libunistring FTBFS: configure.ac:25: error: AC_INIT should be called 
with package and version arguments
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.)


-- 
992281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libunistring
Version: 0.9.10-4
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

libunistring fails to build from source in unstable. A build ends as
follows:

| dh binary-arch
|dh_update_autotools_config -a
|dh_autoreconf -a
| configure.ac:25: error: AC_INIT should be called with package and version 
arguments
| : gl_AM_INIT_AUTOMAKE is expanded from...
| /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
| configure.ac:25: the top level
| autom4te: /usr/bin/m4 failed with exit status: 1
| aclocal: error: /usr/bin/autom4te failed with exit status: 1
| autoreconf: aclocal failed with exit status: 1
| dh_autoreconf: error: autoreconf -f -i returned exit code 1
| make: *** [debian/rules:21: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

This is also seen by crossqa:
http://crossqa.debian.net/build/libunistring_0.9.10-4_s390x_20210816160355.log

http://savannah.gnu.org/bugs/?37851 seems related.

Helmut
--- End Message ---
--- Begin Message ---
Source: libunistring
Source-Version: 0.9.10-6
Done: Jörg Frings-Fürst 

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

Debian distribution maintenance software
pp.
Jörg Frings-Fürst  (supplier of updated libunistring 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, 16 Aug 2021 23:32:24 +0200
Source: libunistring
Architecture: source
Version: 0.9.10-6
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst 
Changed-By: Jörg Frings-Fürst 
Closes: 992281
Changes:
 libunistring (0.9.10-6) unstable; urgency=medium
 .
   * New debian/patches/0010-AC_INIT.patch to fix AC_INIT handling
 (Closes: #992281).
Checksums-Sha1:
 89c367aef98c98aba40193c9fae25a8cb5b36a81 2212 libunistring_0.9.10-6.dsc
 148d6e67e39b8d61014e457a0726b6f7fc2789b6 41588 
libunistring_0.9.10-6.debian.tar.xz
 bcb25f9f3f5a46c0fc612f712bf8c5023095033c 5451 
libunistring_0.9.10-6_source.buildinfo
Checksums-Sha256:
 68c06ffeb5dad6aa1af21e59543389028a34d2fadeb1a0bbefcc96b4b8501060 2212 
libunistring_0.9.10-6.dsc
 fb58a310ffeff4aa93b154a852612bcdc0fdff4c24ea9acc9521fbdae54998f1 41588 
libunistring_0.9.10-6.debian.tar.xz
 6db3fe140610282d6ed117c70285b63fc33ce77448daeb7cf839b6b0a019f306 5451 
libunistring_0.9.10-6_source.buildinfo
Files:
 e8321a6e07a9607695c814ebaeae85c9 2212 libs optional libunistring_0.9.10-6.dsc
 f800bc2323036cb6e9ac439ae58a650f 41588 libs optional 
libunistring_0.9.10-6.debian.tar.xz
 232ee03e2b2550402013ddcaabb6ca5d 5451 libs optional 
libunistring_0.9.10-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmEa8MQACgkQweDZLphv
fH6R+hAAh+Cxb7plRTIrF0JvuY5S0ahJpm5zd8wYGJThsJ5ZVSI8blJSoIjqCX3y
WLHXsYNoD1eURuGbgoY2IxAUcbai9m2bLXdgIXKX+E2UNUGMRScY12lT9tVqlvFh
eOhRWU0ZINziy91sm47sfAZNsVbqk7GQqDwq8k0x8QcL6R4tf6TCpGG7NIzrDhMe
pGiIhycVr+eiJIxIHiHOEGXfm5wkGeRn0r5CyZDIIVL52ZIhk2uVy4Gdzpr44z3T
fzCEn8I7lD2TZfT8elVm3kzhKXTntW5W8aDMMUDmV6QR5HELU9s9VBKman+1tps6
W4GPr4Bksac0A4Mlp61t+3xXExb4jjap9qjofmGcQP7xmZCm0bx9mYB2WkOwgn5y
X4g0+f+xal5n1PJTBXqz+4BC/lcR5ahR2/dLYcUT8GvTGkLwWDBmBIa+1g2hE75B
/RxrQEYhZU5YrhD6Pgma+C1nh8ILbqStUWnm3XLkaOqU5QSuIAWio1qcGq4PReyd
HZRFjV0M7TLCpWzaAEV0s3H2VYLcaUW7AFpNR7guqkxxlSig0tXdHYHum+gMYBB/
UqxLQrhazpSuSHXkjM/qNaNldR1QM3RqmPay+cg2FOM4cqZPLj1PEQBOhlu50wWd
Ed//hXTqJwSGXdIk+ewRXt/Aac80snBk2gDFhDj91KwSdPzQkfU=
=+dRs
-END PGP SIGNATURE End Message ---


Bug#992307: kdenlive-data: package fails to unpack

2021-08-16 Thread Christoph Anton Mitterer
Package: kdenlive-data
Version: 21.04.3-1
Severity: grave
Justification: renders package unusable


Hey.

There is some conflict:

Preparing to unpack .../kdenlive-data_21.04.3-1_all.deb ...
Unpacking kdenlive-data (21.04.3-1) over (20.12.3-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/kdenlive-data_21.04.3-1_all.deb (--unpack):
 trying to overwrite 
'/usr/share/icons/breeze-dark/actions/16/add-subtitle.svg', which is also in 
package breeze-icon-theme 4:5.83.0-2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/kdenlive-data_21.04.3-1_all.deb


Thanks,
Chris.



Processed:

2021-08-16 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 src:firefox-esr
Bug #992150 [firefox] Please allow symlink in system extension
Bug reassigned from package 'firefox' to 'src:firefox-esr'.
No longer marked as found in versions 57.0.0.
Ignoring request to alter fixed versions of bug #992150 to the same values 
previously set

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



Bug#992150:

2021-08-16 Thread Bastien ROUCARIES
control: reassign -1 src:firefox-esr



Bug#983910: marked as done (rpcsvc-proto: uninstallable due to Conflicts: libc6)

2021-08-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 Aug 2021 22:31:33 +
with message-id 
and subject line Bug#983910: fixed in rpcsvc-proto 1.4.2-2
has caused the Debian Bug report #983910,
regarding rpcsvc-proto: uninstallable due to Conflicts: libc6
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.)


-- 
983910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rpcsvc-proto
Version: 1.4.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Package: rpcsvc-proto
Version: 1.4.2-1
Architecture: amd64
Depends: libc6 (>= 2.14)
Conflicts: libc6

That does not work.

Andreas
--- End Message ---
--- Begin Message ---
Source: rpcsvc-proto
Source-Version: 1.4.2-2
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated rpcsvc-proto 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, 16 Aug 2021 22:50:21 +0200
Source: rpcsvc-proto
Architecture: source
Version: 1.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 983910
Changes:
 rpcsvc-proto (1.4.2-2) unstable; urgency=medium
 .
   * Replace the conflicts with libc6-dev by breaks + replaces on libc6-dev
 (<< 2.31-13).  Closes: #983910.
Checksums-Sha1:
 6093d28f8f4c249ee548d736569c41203df6d745 1977 rpcsvc-proto_1.4.2-2.dsc
 7eeac8f66b0e3e55c393cff9b70704fdfb1b6392 3888 
rpcsvc-proto_1.4.2-2.debian.tar.xz
 1192b4fb22377759d689a39008d5d662bcda1db4 5373 
rpcsvc-proto_1.4.2-2_source.buildinfo
Checksums-Sha256:
 31a1dcbe2e6a1fb3ebda1cd0ee45ef6f6ac801e038fb2da3dea006fa697a8f0d 1977 
rpcsvc-proto_1.4.2-2.dsc
 5538e0a7764486f2a37079eb3f0928fbfbe8f31c5b3dfc1d727443d77843c68c 3888 
rpcsvc-proto_1.4.2-2.debian.tar.xz
 b7b73f0a208ce3fc9abfa36831cb6c134ed19dfc7dfd0e844fe5de231027976c 5373 
rpcsvc-proto_1.4.2-2_source.buildinfo
Files:
 233ab1520910661f332a90e9cb288961 1977 devel optional rpcsvc-proto_1.4.2-2.dsc
 e3febf91693b97bb57d203735dd80f7c 3888 devel optional 
rpcsvc-proto_1.4.2-2.debian.tar.xz
 d3545fb1d0d65984630da65bad1fe93c 5373 devel optional 
rpcsvc-proto_1.4.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmEa1I4ACgkQE4jA+Jno
M2tBfhAAoLuwCeSORhzE1ZDVS1GtbS4PkoVZC5ab7ajPQiN+ztsgNTiyTruCQoQN
kEWuZSUA1ABqxalxVIrgZ5Ui6yDXouH41yBfARAmM/AG0VXM6oVMgsATavaj8hgZ
SkNhcTYuxAOGn8BgGDxR3UyX4sHe8IrdfUARXl2Zau1WXV7yCQKxQ7ru+216gV4x
1r19iBFdZ5jY+iiAf8N6xDxDkDi7sVb/ouJmEh0RFXkfAvfXOMxrIOV+ECVpLqIX
+Q85KNbx81tuhtkjv/mivBoVPvXAXG8nnrkBq/buhY64rlYIv9T+DqP1SbPKpJK9
QogUceKHIq9legQUyp9lj9OkL0h9uhEn4wGkSSf5q05xClkIUCX+W8rWQRy2hgbN
NfaWULViEH9BkWqb5BhtCGJDy55d+7z7P1wHyH62idUYSDQZGbuhyzKIoBvDlqK8
VkDJoPQKY6zCdt0VptZO7lHusbHNOm6suv08nsWIRRU9gASylrDilgisluAjhh8m
2t99la7jZc1j0n5HEka3EF4OpCZaqboq+DCc+cQhNzwaN5r6vpM9OLWM7RrbEVNH
AFg+wOc0RDRUkLufylFcAXs19xva756zHJpZfbZT3RY1wgC6LcOII6RkpAx7yibC
sxj+CgYmFBLm4t64VqxNdDhwFbAlART8dnfi6C5fyhkaHNCAJM8=
=qelp
-END PGP SIGNATURE End Message ---


Processed: Debian Bugs #992281

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

> tags 992281 + pending
Bug #992281 [src:libunistring] libunistring FTBFS: configure.ac:25: error: 
AC_INIT should be called with package and version arguments
Added tag(s) pending.
> --
Stopping processing here.

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



Bug#981934: marked as done (portfolio-filemanager: Package is unfit for release - should not be in unstable)

2021-08-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 Aug 2021 21:53:41 +
with message-id 
and subject line Bug#981934: fixed in portfolio-filemanager 0.9.12-1
has caused the Debian Bug report #981934,
regarding portfolio-filemanager: Package is unfit for release - should not be 
in unstable
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.)


-- 
981934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: portfolio-filemanager
Version: 0.9.8-1
Severity: serious
Tags: upstream
Justification: Policy 2.2.1

portfolio-filemanager is still a very new software that is not fit for
release. Upstream agrees with this and is expecting the software to
mature before it could be made part of a stable Debian release.

It has been accidentaly uploaded to unstable instead of
experimental.

This RC bug is created to prevent its transition to testing.


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

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

Versions of packages portfolio-filemanager depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  gir1.2-handy-1   1.0.3-1
ii  python3  3.9.1-1
ii  python3-gi   3.38.0-1+b2

portfolio-filemanager recommends no packages.

portfolio-filemanager suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: portfolio-filemanager
Source-Version: 0.9.12-1
Done: Henry-Nicolas Tourneur 

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

Debian distribution maintenance software
pp.
Henry-Nicolas Tourneur  (supplier of updated 
portfolio-filemanager 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, 16 Aug 2021 20:46:10 +
Source: portfolio-filemanager
Architecture: source
Version: 0.9.12-1
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Henry-Nicolas Tourneur 
Closes: 981934
Changes:
 portfolio-filemanager (0.9.12-1) unstable; urgency=medium
 .
   * New upstream version 0.9.12
   * Upload to unstable (Closes: #981934)
Checksums-Sha1:
 0adb615d4226c9bc175784d82532c1374bbeabb1 2361 
portfolio-filemanager_0.9.12-1.dsc
 aa06c340792a91e3ee75c33957914291c3cb9cc9 435111 
portfolio-filemanager_0.9.12.orig.tar.gz
 9c46fb87ad6b8b3516cb04e4d21fb91e6952bd16 8568 
portfolio-filemanager_0.9.12-1.debian.tar.xz
 105a4ffabda34ee12eebbdf12ab6d6fffe0d150b 16239 
portfolio-filemanager_0.9.12-1_amd64.buildinfo
Checksums-Sha256:
 c69370fce566546b06f4076f0bc4dafbde7af400c3e057b1606e7aafb03f78ce 2361 
portfolio-filemanager_0.9.12-1.dsc
 40ace67fafa3d611166cdf5aa001d98e54552b6dba87843566f67c0a48b30235 435111 
portfolio-filemanager_0.9.12.orig.tar.gz
 8faaa7e1cf642bb7943fd82cf7195b8428d9ca3210d6013dd229d11d00521b15 8568 
portfolio-filemanager_0.9.12-1.debian.tar.xz
 a5671da501466c420eb31f0d8217e9e4fab8dd5183d897eb7e596aeafcfe34d8 16239 
portfolio-filemanager_0.9.12-1_amd64.buildinfo
Files:
 a08fbe5265dda4d5340f72a8b7da5874 2361 gnome optional 
portfolio-filemanager_0.9.12-1.dsc
 4918a82a47b231d477fb0d403a6b5603 435111 gnome optional 
portfolio-filemanager_0.9.12.orig.tar.gz
 40d2c3a08ec9c785a9df409436989c41 8568 gnome optional 
portfolio-filemanager_0.9.12-1.debian.tar.xz
 b61f35ca62e9a66555e908159720efca 16239 gnome optional 
portfolio-filemanager_0.9.12-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEENS+/LT+kHSXcqokQ3QyVlN+SbJAFAmEa1gYQHGRlYmlhbkBu
aWx1eC5iZQAKCRDdDJWU35JskOP7EACvl5puRrUsBtkuqKy+KqWCE5mMgyqV7ZdS
C8GIuKFsTTJqjnfdD4AG0YgWY+MBsKcdpzTi8+c+tSGeqijWNkf2fffz+EumG7AQ
PR151jGuxEGwu0ELoAZi6+bAyXfimiAna7F0uSvOUdYl5T2SJW3pK4XznEDr1fy6
CL5YcnS4AOk5viernR8nfQP1JgtuL8pfkalLKwiY/vjelX2d

Bug#983910: marked as pending in glibc

2021-08-16 Thread Aurelien Jarno
Control: tag -1 pending

Hello,

Bug #983910 in glibc 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/glibc-team/rpcsvc-proto/-/commit/54544b7ba0c3fa2167a6725c4b321bda9c616407


Replace the conflicts with libc6-dev by breaks + replaces on libc6-dev (<< 
2.31-13).  Closes: #983910.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/983910



Processed: Bug#983910 marked as pending in glibc

2021-08-16 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #983910 [rpcsvc-proto] rpcsvc-proto: uninstallable due to Conflicts: libc6
Added tag(s) pending.

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



Processed: Re: Bug#992247: patchage FTBFS with glib 2.68.3

2021-08-16 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 patchage FTBFS: error: conversion from 
> ‘iterator_base’ to non-scalar type ‘iterator_base Ganv::Port,const _GanvPort>’ requested
Bug #992247 [src:patchage] patchage FTBFS with glib 2.68.3
Changed Bug title to 'patchage FTBFS: error: conversion from 
‘iterator_base’ to non-scalar type ‘iterator_base’ requested' from 'patchage FTBFS with glib 2.68.3'.

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



Bug#992247: patchage FTBFS with glib 2.68.3

2021-08-16 Thread Adrian Bunk
Control: retitle -1 patchage FTBFS: error: conversion from 
‘iterator_base’ to non-scalar type ‘iterator_base’ requested

On Mon, Aug 16, 2021 at 01:41:44PM +0300, Adrian Bunk wrote:
> Source: patchage
> Version: 1.0.0~dfsg0-0.2
> Severity: serious
> Tags: ftbfs bookworm sid
> 
> https://buildd.debian.org/status/package.php?p=patchage&suite=sid
> 
> ...
> 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/glibmm-2.4/glibmm/unicode.h:23,
>  from /usr/include/glibmm-2.4/glibmm/ustring.h:21,
>  from /usr/include/gtkmm-2.4/gtkmm/aboutdialog.h:9,
>  from ../src/Patchage.hpp:25,
>  from ../src/PatchageModule.cpp:17:
> /usr/include/glib-2.0/glib/gtypes.h:545:26: note: declared here
>   545 | typedef struct _GTimeVal GTimeVal 
> GLIB_DEPRECATED_TYPE_IN_2_62_FOR(GDateTime);
>   |  ^~~~
> ../src/PatchageModule.cpp: In member function ‘void 
> PatchageModule::update_menu()’:
> ../src/PatchageModule.cpp:56:32: error: conversion from 
> ‘iterator_base’ to non-scalar type ‘iterator_base Ganv::Port,const _GanvPort>’ requested
>56 |   for (const_iterator p = begin(); p != end(); ++p) {
>   |   ~^~
> ../src/PatchageModule.cpp:56:38: error: no match for ‘operator!=’ (operand 
> types are ‘Ganv::Module::const_iterator’ {aka 
> ‘Ganv::Module::iterator_base’} and 
> ‘Ganv::Module::iterator’ {aka ‘Ganv::Module::iterator_base _GanvPort>’})
>56 |   for (const_iterator p = begin(); p != end(); ++p) {
>   |~ ^~ ~
>   ||   |
>   ||   
> iterator_base
>   |iterator_base Ganv::Port,const _GanvPort>
> ...

This bug is actually older than the 2.68.3, whatever broke it seems to 
have happened in late January or early February:
https://tests.reproducible-builds.org/debian/history/patchage.html

cu
Adrian



Processed: Re: Bug#992271: ukui-window-switch FTBFS with glib 2.68.3

2021-08-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #992271 [src:ukui-window-switch] ukui-window-switch  FTBFS with glib 2.68.3
Added tag(s) patch.

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



Bug#992271: ukui-window-switch FTBFS with glib 2.68.3

2021-08-16 Thread Simon McVittie
Control: tags -1 + patch

On Mon, 16 Aug 2021 at 18:42:26 +0300, Adrian Bunk wrote:
> In file included from /usr/include/glib-2.0/glib/gatomic.h:31,
>  from /usr/include/glib-2.0/glib/gthread.h:32,
>  from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
>  from /usr/include/glib-2.0/glib.h:32,
>  from /usr/include/glib-2.0/gobject/gbinding.h:28,
>  from /usr/include/glib-2.0/glib-object.h:22,
>  from /usr/include/libwnck-3.0/libwnck/window.h:33,
>  from /usr/include/libwnck-3.0/libwnck/libwnck.h:26,
>  from src/ukws_window_box.h:25,
>  from src/ukws_indicator.h:24,
>  from src/ukws_indicator.cpp:20:
> /usr/include/c++/10/type_traits:56:3: error: template with C linkage
>56 |   template
>   |   ^~~~
> In file included from src/ukws_indicator.h:24,
>  from src/ukws_indicator.cpp:20:
> src/ukws_window_box.h:23:1: note: ‘extern "C"’ linkage started here
>23 | extern "C" {
>   | ^~

Bugs with this compiler error are caused by a header behaviour change
in GLib 2.68.

In older versions, the GLib headers contained only C code, even when
compiled with a C++ compiler. In GLib 2.68+, if C++ compilation is
detected, the headers make use of C++ features to make macros like
g_object_ref() more type-safe.

There are two ways to resolve the build failure:

1. Move inclusions of system headers outside extern "C" blocks, at least
   for well-behaved libraries like GLib and GTK that already include their
   own extern "C" guard, either directly or via macros like GLib's own
   G_BEGIN_DECLS/G_END_DECLS.

   Attached patch Don-t-wrap-C-header-inclusions-in-extern-C.patch
   implements this.

2. Target a specific GLib version older than 2.68 by defining the macros
   GLIB_VERSION_MIN_REQUIRED and GLIB_VERSION_MAX_ALLOWED (see GLib's
   documentation for details). This asks GLib to disable behaviour changes
   and deprecation warnings that happened since the target version.

   https://github.com/brummer10/gxtuner/pull/21 is an example of this
   in a different project, but I don't know how to specify CPPFLAGS
   in a qmake project, so I haven't attached a patch implementing this.

Maintainers can choose either or both of those methods. I would personally
recommend doing both.

Thanks,
smcv
From: Simon McVittie 
Date: Mon, 16 Aug 2021 18:29:14 +0100
Subject: Don't wrap C header inclusions in extern "C"

The GLib, Gdk-Pixbuf, Wnck and XCB headers all use extern "C"
internally, so it is unnecessary to wrap their inclusion in an
extern "C" block.

A redundant extern "C" block can be harmful, for example if these headers
test for defined(__cplusplus) and, if defined, use C++ features in their
macros. GLib 2.68 started to do this, to make macros like g_object_ref()
type-safe, resulting in compilation failure for C++ projects that
assumed GLib headers would always be pure C.

Bug-Debian: https://bugs.debian.org/992271
---
 src/ukws_helper.h| 2 --
 src/ukws_window_box.h| 2 --
 src/ukws_window_info.h   | 2 --
 src/ukws_wnck_operator.h | 2 --
 src/ukws_workspace_box.h | 2 --
 5 files changed, 10 deletions(-)

diff --git a/src/ukws_helper.h b/src/ukws_helper.h
index 610e91c..59806de 100644
--- a/src/ukws_helper.h
+++ b/src/ukws_helper.h
@@ -20,10 +20,8 @@
 #ifndef UKWS_HELPER_H
 #define UKWS_HELPER_H
 
-extern "C" {
 #include 
 #include 
-}
 
 #include 
 #include 
diff --git a/src/ukws_window_box.h b/src/ukws_window_box.h
index feb6a4b..d16da93 100644
--- a/src/ukws_window_box.h
+++ b/src/ukws_window_box.h
@@ -20,10 +20,8 @@
 #ifndef UKWS_WINDOWBOX_H
 #define UKWS_WINDOWBOX_H
 
-extern "C" {
 #define WNCK_I_KNOW_THIS_IS_UNSTABLE
 #include 
-}
 
 #include "ukws_window_extra_label.h"
 
diff --git a/src/ukws_window_info.h b/src/ukws_window_info.h
index 2c6d4e6..ef590e8 100644
--- a/src/ukws_window_info.h
+++ b/src/ukws_window_info.h
@@ -20,10 +20,8 @@
 #ifndef UKWS_WINDOW_INFO_H
 #define UKWS_WINDOW_INFO_H
 
-extern "C" {
 #define WNCK_I_KNOW_THIS_IS_UNSTABLE
 #include 
-}
 
 #include 
 #include 
diff --git a/src/ukws_wnck_operator.h b/src/ukws_wnck_operator.h
index 6391ad1..d75409e 100644
--- a/src/ukws_wnck_operator.h
+++ b/src/ukws_wnck_operator.h
@@ -20,10 +20,8 @@
 #ifndef UKWS_WNCK_OPERATOR_H
 #define UKWS_WNCK_OPERATOR_H
 
-extern "C" {
 #define WNCK_I_KNOW_THIS_IS_UNSTABLE
 #include 
-}
 
 #include 
 
diff --git a/src/ukws_workspace_box.h b/src/ukws_workspace_box.h
index 1023ca7..a039e06 100644
--- a/src/ukws_workspace_box.h
+++ b/src/ukws_workspace_box.h
@@ -20,11 +20,9 @@
 #ifndef UKWSWORKSPACEBOX_H
 #define UKWSWORKSPACEBOX_H
 
-extern "C" {
 #define WNCK_I_KNOW_THIS_IS_UNSTABLE
 #include 
 #include 
-}
 
 #include "ukws_window_extra_label.h"
 #include "ukws_wnck_operator.h"


Bug#992246: gxtuner FTBFS with glib 2.68.3

2021-08-16 Thread Simon McVittie
On Mon, 16 Aug 2021 at 19:14:58 +0100, Simon McVittie wrote:
> 1. Move inclusions of system headers outside extern "C" blocks ...
>Attached patch 0001-Move-system-header-inclusions-outside-extern-C.patch
>implements this.
> 
> 2. Target a specific GLib version by defining the macros
>GLIB_VERSION_MIN_REQUIRED and GLIB_VERSION_MAX_ALLOWED ...
>Attached patch 0001-build-Target-a-specific-GLib-API-version.patch
>implements this.

Now with patches actually attached.

smcv
>From 26f06c0416b1266b7d70ade61a8d29050960a208 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Mon, 16 Aug 2021 18:41:25 +0100
Subject: [PATCH] build: Target a specific GLib API version

Setting GLIB_VERSION_MIN_REQUIRED selects the minimum required version
of GLib for this project. Code that was deprecated after that version
will not cause deprecation warnings, and where header files have changed
their compile-time behaviour over time, the behaviour that was seen in
the selected version will be used where possible.

Setting GLIB_VERSION_MAX_ALLOWED causes GLib to emit warnings if a
function introduced after the selected version is used.

In particular, this disables new C++ behaviour introduced in GLib 2.68,
which caused this project to fail to build.

GLib 2.54 is an arbitrary choice: it happens to be the version that was
the current stable release when gxtuner 3.0.0 was released. It could
be reduced if gxtuner needs to compile on older distributions, or
increased if a newer dependency is acceptable.

Bug: https://github.com/brummer10/gxtuner/issues/19
Bug-Debian: https://bugs.debian.org/992246
Forwarded: https://github.com/brummer10/gxtuner/pull/21
---
 Makefile | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Makefile b/Makefile
index 88221f6..2680f86 100644
--- a/Makefile
+++ b/Makefile
@@ -14,6 +14,8 @@
 	NAME = gxtuner
 	LIBS = `pkg-config --libs jack gtk+-3.0 gthread-2.0 fftw3f x11` -lzita-resampler
 	CFLAGS += -Wall -ffast-math `pkg-config --cflags jack gtk+-3.0 gthread-2.0 fftw3f`
+	CFLAGS += -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_54
+	CFLAGS += -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_54
 	OBJS = resources.o jacktuner.o gxtuner.o cmdparser.o gx_pitch_tracker.o gtkknob.o \
paintbox.o tuner.o deskpager.o main.o
 	DEBNAME = $(NAME)_$(VER)
-- 
2.32.0

>From 2f3771ed5a6ca17688280953eff2859ba93ba8d9 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Mon, 16 Aug 2021 18:07:17 +0100
Subject: [PATCH] Move system header inclusions outside extern "C"

GLib and GTK both include extern "C" guards in their header files, so it
is unnecessary to wrap them in an extern "C" block.

A redundant extern "C" block can be harmful, because header files might
test #ifdef __cplusplus and include C++ syntax if it is defined, even in
an otherwise C header. In particular, GLib has done this since version
2.68, in order to make macros like g_object_ref() type-safe when called
from C++ code. the result was that this project failed to compile.

Bug: https://github.com/brummer10/gxtuner/issues/19
Bug-Debian: https://bugs.debian.org/992246
Forwarded: https://github.com/brummer10/gxtuner/pull/20
---
 gtkknob.h  | 4 ++--
 gxtuner.h  | 8 +++-
 paintbox.h | 4 ++--
 3 files changed, 7 insertions(+), 9 deletions(-)

diff --git a/gtkknob.h b/gtkknob.h
index d7d1cae..f5d8f0a 100644
--- a/gtkknob.h
+++ b/gtkknob.h
@@ -24,14 +24,14 @@
 #ifndef __GTK_KNOB_H__
 #define __GTK_KNOB_H__
 
+#include 
+
 #ifdef __cplusplus
 extern "C" {
 #endif
 
 #pragma once
 
-#include 
-
 G_BEGIN_DECLS
 
 #define GTK_TYPE_KNOB  (gtk_knob_get_type())
diff --git a/gxtuner.h b/gxtuner.h
index 4b729ec..8ca2399 100644
--- a/gxtuner.h
+++ b/gxtuner.h
@@ -26,15 +26,13 @@
 #ifndef _GX_TUNER_H_
 #define _GX_TUNER_H_
 
-#ifdef __cplusplus
-extern "C" {
-#endif
-
 #include 
 #include 
 #include  
 
-
+#ifdef __cplusplus
+extern "C" {
+#endif
 
 G_BEGIN_DECLS
 
diff --git a/paintbox.h b/paintbox.h
index 5e2781b..9821ef3 100644
--- a/paintbox.h
+++ b/paintbox.h
@@ -21,12 +21,12 @@
 #ifndef __PAINT_BOX_H__
 #define __PAINT_BOX_H__
 
+#include 
+
 #ifdef __cplusplus
 extern "C" {
 #endif
 
-#include 
-
 G_BEGIN_DECLS
 
 #define GX_TYPE_PAINT_BOX(gx_paint_box_get_type ())
-- 
2.32.0



Processed: Re: Bug#992246: gxtuner FTBFS with glib 2.68.3

2021-08-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #992246 [src:gxtuner] gxtuner FTBFS with glib 2.68.3
Added tag(s) patch.
> forwarded -1 https://github.com/brummer10/gxtuner/issues/19
Bug #992246 [src:gxtuner] gxtuner FTBFS with glib 2.68.3
Set Bug forwarded-to-address to 
'https://github.com/brummer10/gxtuner/issues/19'.

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



Bug#992246: gxtuner FTBFS with glib 2.68.3

2021-08-16 Thread Simon McVittie
Control: tags -1 + patch
Control: forwarded -1 https://github.com/brummer10/gxtuner/issues/19

(Adrian: I don't intend to cc you on responses to all bugs of this class,
but I thought I'd cc you on the first one so that you can see what I'm
recommending as a solution.)

On Mon, 16 Aug 2021 at 13:33:01 +0300, Adrian Bunk wrote:
> In file included from /usr/include/glib-2.0/glib/gatomic.h:31,
>  from /usr/include/glib-2.0/glib/gthread.h:32,
>  from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
>  from /usr/include/glib-2.0/glib.h:32,
>  from /usr/include/glib-2.0/gobject/gbinding.h:28,
>  from /usr/include/glib-2.0/glib-object.h:22,
>  from ./gxtuner.h:33,
>  from gxtuner.cpp:24:
> /usr/include/c++/10/type_traits:56:3: error: template with C linkage
>56 |   template
>   |   ^~~~
> In file included from gxtuner.cpp:24:
> ./gxtuner.h:30:1: note: ‘extern "C"’ linkage started here
>30 | extern "C" {
>   | ^~

Bugs with this compiler error are caused by a header behaviour change
in GLib 2.68.

In older versions, the GLib headers contained only C code, even when
compiled with a C++ compiler. In GLib 2.68+, if C++ compilation is
detected, the headers make use of C++ features to make macros like
g_object_ref() more type-safe.

There are two ways to resolve the build failure:

1. Move inclusions of system headers outside extern "C" blocks, at least
   for well-behaved libraries like GLib and GTK that already include their
   own extern "C" guard, either directly or via macros like GLib's own
   G_BEGIN_DECLS/G_END_DECLS.

   Attached patch 0001-Move-system-header-inclusions-outside-extern-C.patch
   implements this. I've proposed it upstream.

2. Target a specific GLib version by defining the macros
   GLIB_VERSION_MIN_REQUIRED and GLIB_VERSION_MAX_ALLOWED (see GLib's
   documentation for details). This asks GLib to disable behaviour changes
   and deprecation warnings that happened since the target version.

   Attached patch 0001-build-Target-a-specific-GLib-API-version.patch
   implements this. I've proposed it upstream. The choice of GLib 2.54
   is completely arbitrary (it's the version that was current at the time
   gxtuner was most recently released) so an upstream or downstream
   maintainer could probably make a better choice.

Maintainers can choose either or both of those methods. I would personally
recommend doing both.

I've successfully compiled gxtuner against GLib 2.68.3 with each of those
patches, individually. I have not otherwise tested the resulting executables.

Thanks,
smcv



Bug#992281: libunistring FTBFS: configure.ac:25: error: AC_INIT should be called with package and version arguments

2021-08-16 Thread Helmut Grohne
Source: libunistring
Version: 0.9.10-4
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

libunistring fails to build from source in unstable. A build ends as
follows:

| dh binary-arch
|dh_update_autotools_config -a
|dh_autoreconf -a
| configure.ac:25: error: AC_INIT should be called with package and version 
arguments
| : gl_AM_INIT_AUTOMAKE is expanded from...
| /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
| configure.ac:25: the top level
| autom4te: /usr/bin/m4 failed with exit status: 1
| aclocal: error: /usr/bin/autom4te failed with exit status: 1
| autoreconf: aclocal failed with exit status: 1
| dh_autoreconf: error: autoreconf -f -i returned exit code 1
| make: *** [debian/rules:21: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

This is also seen by crossqa:
http://crossqa.debian.net/build/libunistring_0.9.10-4_s390x_20210816160355.log

http://savannah.gnu.org/bugs/?37851 seems related.

Helmut



Bug#992277: protontricks: With any command, fails with "KeyError: 'LibraryFolders'"

2021-08-16 Thread Brian Vaughan
Package: protontricks
Version: 1.5.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: bgvaug...@gmail.com

Dear Maintainer,

Simply executing 'protontricks' shows the usage instructions. Executing it with
commands results in a Python error message.

$ protontricks -s "No Man's Sky"
Traceback (most recent call last):
  File "/usr/bin/protontricks", line 33, in 
sys.exit(load_entry_point('protontricks==1.5.0', 'console_scripts',
'protontricks')())
  File "/usr/lib/python3/dist-packages/protontricks/cli.py", line 167, in main
steam_lib_paths = get_steam_lib_paths(steam_path)
  File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 613, in
get_steam_lib_paths
library_folders = parse_library_folders(folders_vdf_path.read_text())
  File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 597, in
parse_library_folders
Path(value) for key, value in vdf_data["LibraryFolders"].items()
KeyError: 'LibraryFolders'

$ protontricks --gui
Traceback (most recent call last):
  File "/usr/bin/protontricks", line 33, in 
sys.exit(load_entry_point('protontricks==1.5.0', 'console_scripts',
'protontricks')())
  File "/usr/lib/python3/dist-packages/protontricks/cli.py", line 167, in main
steam_lib_paths = get_steam_lib_paths(steam_path)
  File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 613, in
get_steam_lib_paths
library_folders = parse_library_folders(folders_vdf_path.read_text())
  File "/usr/lib/python3/dist-packages/protontricks/steam.py", line 597, in
parse_library_folders
Path(value) for key, value in vdf_data["LibraryFolders"].items()
KeyError: 'LibraryFolders'

I had previously installed protontricks as a normal user, using pipx, following
the instructions at https://github.com/Matoking/protontricks and used it
successfully. I uninstalled it, using pipx, prior to installing the Debian
package.


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

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

Versions of packages protontricks depends on:
ii  python3  3.9.2-3
ii  python3-vdf  3.4-2
ii  steam1.0.0.68-1
ii  winetricks   0.0+20210206-2
ii  zenity   3.32.0-7

protontricks recommends no packages.

protontricks suggests no packages.



Bug#992271: ukui-window-switch FTBFS with glib 2.68.3

2021-08-16 Thread Adrian Bunk
Source: ukui-window-switch
Version: 3.0.0-1
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=ukui-window-switch&suite=sid

...
In file included from /usr/include/glib-2.0/glib/gatomic.h:31,
 from /usr/include/glib-2.0/glib/gthread.h:32,
 from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
 from /usr/include/glib-2.0/glib.h:32,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:22,
 from /usr/include/libwnck-3.0/libwnck/window.h:33,
 from /usr/include/libwnck-3.0/libwnck/libwnck.h:26,
 from src/ukws_window_box.h:25,
 from src/ukws_indicator.h:24,
 from src/ukws_indicator.cpp:20:
/usr/include/c++/10/type_traits:56:3: error: template with C linkage
   56 |   template
  |   ^~~~
In file included from src/ukws_indicator.h:24,
 from src/ukws_indicator.cpp:20:
src/ukws_window_box.h:23:1: note: ‘extern "C"’ linkage started here
   23 | extern "C" {
  | ^~
...


Bug#989112: marked as done (wims-lti: fails to install: ModuleNotFoundError: No module named 'wimsLTI.config')

2021-08-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 Aug 2021 15:13:40 +
with message-id 
and subject line Bug#989112: fixed in wims-lti 0.4.4.1-4
has caused the Debian Bug report #989112,
regarding wims-lti: fails to install: ModuleNotFoundError: No module named 
'wimsLTI.config'
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.)


-- 
989112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wims-lti
Version: 0.4.4.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Setting up wims-lti (0.4.4.1-3) ...
  Warning: The home dir /var/lib/wims-lti you specified already exists.
  Adding system user `lti' (UID 150) ...
  Adding new user `lti' (UID 150) with group `nogroup' ...
  The home directory `/var/lib/wims-lti' already exists.  Not copying from 
`/etc/skel'.
  adduser: Warning: The home directory `/var/lib/wims-lti' does not belong to 
the user you are currently creating.
  Adding group `lti' (GID 150) ...
  Done.
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 204, in fetch_command
  app_name = commands[subcommand]
  KeyError: 'collectstatic'
  
  During handling of the above exception, another exception occurred:
  
  Traceback (most recent call last):
File "/var/lib/wims-lti/./manage.py", line 15, in 
  execute_from_command_line(sys.argv)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 381, in execute_from_command_line
  utility.execute()
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 375, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 211, in fetch_command
  settings.INSTALLED_APPS
File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 79, in 
__getattr__
  self._setup(name)
File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 66, in 
_setup
  self._wrapped = Settings(settings_module)
File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 157, in 
__init__
  mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File "/var/lib/wims-lti/wimsLTI/settings.py", line 237, in 
  from wimsLTI.config import *  # noqa: E402 F401 F403
  ModuleNotFoundError: No module named 'wimsLTI.config'
  dpkg: error processing package wims-lti (--configure):
   installed wims-lti package post-installation script subprocess returned 
error exit status 1
  Processing triggers for libc-bin (2.31-12) ...
  Processing triggers for ca-certificates (20210119) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Errors were encountered while processing:
   wims-lti
  E: Sub-process /usr/bin/dpkg returned an error code (1)


cheers,


Andreas


wims-lti_0.4.4.1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: wims-lti
Source-Version: 0.4.4.1-4
Done: Georges Khaznadar 

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated wims-lti package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 16 Aug 2021 14:59:40 +

Bug#992270: rna-star FTBFS on !amd64: unrecognized command-line option ‘-mavx2’

2021-08-16 Thread Adrian Bunk
Source: rna-star
Version: 2.7.9a+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=rna-star&suite=sid

...
g++ -c -I./ -std=c++11 -Wdate-time -D_FORTIFY_SOURCE=2  -O3 -std=c++11 -fopenmp 
-D'COMPILATION_TIME_PLACE="2021-08-15T17:48:21+00:00 "' -flto -flto -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++0x -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3  -mavx2 opal.cpp
g++: error: unrecognized command-line option ‘-mavx2’
make[2]: *** [Makefile:94: opal/opal.o] Error 1


This does likely also cause a baseline violation on amd64,
defeating the purpose of building for different SIMD levels.


Processed (with 1 error): Re: Please allow symlink in system extension

2021-08-16 Thread Debian Bug Tracking System
Processing control commands:

> clone -1 -2
Bug #992150 [firefox] Please allow symlink in system extension
Bug 992150 cloned as bug 992263
> assign -1 src:firefox-esr
Unknown command or malformed arguments to command.


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



Bug#992150: Please allow symlink in system extension

2021-08-16 Thread Bastien ROUCARIES
Followup-For: Bug #992150
Control: clone -1 -2
Control: assign -1 src:firefox-esr



Bug#990069: openssh-server: Not accepting new connections during Debian 10 -> 11 upgrade

2021-08-16 Thread Aurelien Jarno
Hi,

On 2021-08-12 21:51, Andres Salomon wrote:
> Hi,
> 
> So this only affects users who do or do not have the ssh metapackage
> installed? This bug report is a bit confusing.
> 

It used to affects all users who do or do not have the ssh metapackage
installed, however following the fix that went into 2.31-13, all users
are now affected.

Regards,
Aurelien

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



Bug#992150: Please allow symlink in system extension

2021-08-16 Thread Bastien Roucariès
Followup-For: Bug #992150
Control: clone -1 src:firefox-esr



Bug#992158: Race in ifup maybe related to brctl failure in pre-up of network interface

2021-08-16 Thread Santiago Garcia Mantinan
Hi!

First I'd like to thank Dennis for his good support, as always ;-)

> > $ ifup virtbr0
> > Cannot find device "virtbr0"
> > ifup: failed to bring up virtbr0
> 
> It is because the "bridge_ports" directive is missing.  From the
> manpage bridge-utils-interfaces(5):
> 
>bridge_ports interface specification
>   this option must exist for the scripts to setup the bridge.
> 
> Either specify "bridge_ports none" or "bridge_ports enp2s0 enp2s1" (or
> whatever your physical interfaces are named).

That's it, you always have to specify the bridge_ports directive so that we
treat the interface as a bridge.

> > I also reactivated "systemd-udevd":
...
> > # systemctl reload /lib/systemd/network/80-bridgeutils.link
> > Failed to reload lib-systemd-network-80\x2dbridgeutils.link.mount: Unit 
> > lib-systemd-network-80\x2dbridgeutils.link.mount not found.

I really believe that this contribution from Dennis should not be needed, so
I'd appreciate if you could test without this extra stuff, which hasn't
really been thoroughtly tested and test with the standard setup, if we
identify a problem with the standard bridge_hw setup we'll go over it.

If you test it like that, please provide feedback to know if it worked and
if we can close the bug or not.

Regards.
-- 
Manty/BestiaTester -> http://manty.net



Processed: merging 992233 992234

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

> merge 992233 992234
Bug #992233 [tmuxinator] tmuxinator: Uninstallable due to new tmux version
Bug #992234 [tmuxinator] uninstallable; incompatible with tmux 3.2
Merged 992233 992234
> thanks
Stopping processing here.

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



Bug#992250: fonts-smc-manjari FTBFS: fntsample: not found

2021-08-16 Thread Adrian Bunk
Source: fonts-smc-manjari
Version: 2.000-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=fonts-smc-manjari&arch=all&ver=2.000-1&stamp=1629012666&raw=0

...
   dh_auto_test -i
make -j4 test
make[1]: Entering directory '/<>'
  BUILDManjari-Regular.ttf
  BUILDManjari-Bold.ttf
  BUILDManjari-Thin.ttf
   TESTManjari-Thin-kerning.pdf
   TESTManjari-Thin-ligatures.pdf
   TESTManjari-Thin-latin.pdf
   TESTManjari-Thin-content.pdf
   TESTManjari-Thin-numbers.pdf
   TESTManjari-Thin-table.pdf
/bin/sh: 1: fntsample: not found
make[1]: *** [Makefile:69: build/Manjari-Thin-table.pdf] Error 127



Bug#992249: s390-tools: missing build dependency on libglib2.0-dev

2021-08-16 Thread Adrian Bunk
Source: s390-tools
Version: 2.16.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=s390-tools&arch=s390x&ver=2.16.0-1&stamp=1629044714&raw=0

...

* Missing build requirement for: genprotimg*
* Install package..: glib2-devel / libglib2.0-dev  *
* You can skip build with..: make HAVE_GLIB2=0 *

make[4]: *** [Makefile:96: .check-dep-genprotimg] Error 1



Bug#992247: patchage FTBFS with glib 2.68.3

2021-08-16 Thread Adrian Bunk
Source: patchage
Version: 1.0.0~dfsg0-0.2
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=patchage&suite=sid

...
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/glibmm-2.4/glibmm/unicode.h:23,
 from /usr/include/glibmm-2.4/glibmm/ustring.h:21,
 from /usr/include/gtkmm-2.4/gtkmm/aboutdialog.h:9,
 from ../src/Patchage.hpp:25,
 from ../src/PatchageModule.cpp:17:
/usr/include/glib-2.0/glib/gtypes.h:545:26: note: declared here
  545 | typedef struct _GTimeVal GTimeVal 
GLIB_DEPRECATED_TYPE_IN_2_62_FOR(GDateTime);
  |  ^~~~
../src/PatchageModule.cpp: In member function ‘void 
PatchageModule::update_menu()’:
../src/PatchageModule.cpp:56:32: error: conversion from 
‘iterator_base’ to non-scalar type ‘iterator_base’ requested
   56 |   for (const_iterator p = begin(); p != end(); ++p) {
  |   ~^~
../src/PatchageModule.cpp:56:38: error: no match for ‘operator!=’ (operand 
types are ‘Ganv::Module::const_iterator’ {aka 
‘Ganv::Module::iterator_base’} and 
‘Ganv::Module::iterator’ {aka ‘Ganv::Module::iterator_base’})
   56 |   for (const_iterator p = begin(); p != end(); ++p) {
  |~ ^~ ~
  ||   |
  ||   
iterator_base
  |iterator_base
...


Bug#992246: gxtuner FTBFS with glib 2.68.3

2021-08-16 Thread Adrian Bunk
Source: gxtuner
Version: 3.0-2
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=gxtuner&suite=sid

...
In file included from /usr/include/glib-2.0/glib/gatomic.h:31,
 from /usr/include/glib-2.0/glib/gthread.h:32,
 from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
 from /usr/include/glib-2.0/glib.h:32,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:22,
 from ./gxtuner.h:33,
 from gxtuner.cpp:24:
/usr/include/c++/10/type_traits:56:3: error: template with C linkage
   56 |   template
  |   ^~~~
In file included from gxtuner.cpp:24:
./gxtuner.h:30:1: note: ‘extern "C"’ linkage started here
   30 | extern "C" {
  | ^~
...


Bug#992244: mongo-cxx-driver: keep out of testing

2021-08-16 Thread Roberto C. Sanchez
Package: mongo-cxx-driver
Severity: serious
Justification: keep package out of testing

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

This package should not enter testing.

- -- System Information:
Debian Release: 10.10
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEz9ERzDttUsU/BH8iLNd4Xt2nsg8FAmEaNxQACgkQLNd4Xt2n
sg8RBRAAqRen3qkwXMnk07Iwh1kvrVecUCZaLAMpWvogIHTEkiZ55PAVJG5phvm+
7WIRxhByuLytod/e+If3pyMJrqJbuN0EjqixsYnp/GiL1l+1eqkTApVUSbJQp44H
LoqCmUoSbYXZFEPtQUr8dEXcF6djT+u10pCyY1szKdEAhKxEa9zAEsGITk6my8mH
P4jRt3En3P7awyaxcbPPt1UEZU53qrjo7sqy9rSknJ8gDQgB72pZI6h+1nOHcv83
2lZCidF+nGy0n7JTykW7V2o1Chh2Sig7WjL2tnN1bh+ykA+yQoONr5gZejGwPDpE
bJUP5gE6fcT4/VVagJJUrOuu+Ikck6SuUflFa+Nfap5/r24RKrXJLg/eCpu6rm3F
mlkGY0FBKr1tSK/6sB4z9ruXaZeaPeF+ayOBGSMfY6viIvfdB0OORo9OeWrrnbly
nVmHXLIm8v7Utu7TWoG9UdHKDAyuFWs/0rCsV7+U5beWFrFGyMk60eqAGkLuLv5k
Da/yngtMd6HBPG3fIUVnUllxhEf67z+2KXhkq7/7BNVkHAx8yW14dc8bMtncwbOe
5Y6govGvP7i+UaUF7F5EJh8fj2aqhFUPwbpvHUsUL4u+bGVhLJrhoS7dqqhOJIUF
QntDHR8EgyB1ykZ9xPNInTNhS81unElcyiyquqZmzKYx/Q0rV6c=
=1zkY
-END PGP SIGNATURE-



Processed: tagging 885195

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

> tags 885195 + ftbfs
Bug #885195 [src:geda-gaf] geda-gaf: please upload latest version which uses 
guile-2.2
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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



Processed: Re: Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init

2021-08-16 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #992238 [debian-installer] debian-installer: Installation fails on HP 
ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init
Severity set to 'important' from 'critical'
> reassign -1 src:linux
Bug #992238 [debian-installer] debian-installer: Installation fails on HP 
ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init
Bug reassigned from package 'debian-installer' to 'src:linux'.
No longer marked as found in versions debian-installer/20210731.
Ignoring request to alter fixed versions of bug #992238 to the same values 
previously set

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



Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init

2021-08-16 Thread Steve McIntyre
Control: severity -1 important
Control: reassign -1 src:linux

Hi Justus!

Reassigning to the right package. While you're seeing this during d-i,
the problem is clearly coming from the Linux kernel.

On Mon, Aug 16, 2021 at 10:09:49AM +0200, Justus Winter wrote:
>Package: debian-installer
>Version: 20210731
>Severity: critical
>Tags: d-i
>Justification: breaks the whole system
>
>Dear Maintainer,
>
>I'm trying to install Debian Bullseye on a ProLiant m400 Server
>Cartridge.  The cartridge is in EFI mode, we boot the EFI shim, GRUB,
>the kernel, and the netboot initrd via PXE and tftp.  We added the
>necessary kernel command line flags to redirect the kernel log to the
>serial console early on, and various debugging flags.
>
>Reading the log we believe that there are two problems.  First, while
>bringing up additional CPU cores, we see them crash immediately.
>Adding nosmp to the kernel command line avoids this, but doesn't make
>the second problem go away.  Second, the kernel calls acpi_init, which
>does not seem to return.

Hmmm. The m400 sleds are getting quite old, and AIUI they're basically
EOL in terms of firmware support etc. I've got some Mustang (X-Gene 1)
machines here, which are the same core APM hardware but packaged on
standard motherboard (mini-itx I think?). I'm just trying a bullseye
update on one now.

Out of curiosity: how does an equivalent boot work with buster d-i on
your system?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I can't ever sleep on planes ... call it irrational if you like, but I'm
 afraid I'll miss my stop" -- Vivek Das Mohapatra



Processed: retitle 982123 to librsvg: FTBFS on ppc64el in buster

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

> retitle 982123 librsvg: FTBFS on ppc64el in buster
Bug #982123 [src:librsvg] librsvg: FTBFS on ppc64el
Changed Bug title to 'librsvg: FTBFS on ppc64el in buster' from 'librsvg: FTBFS 
on ppc64el'.
> thanks
Stopping processing here.

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



Bug#992239: Security fixes from the July 2021 CPU

2021-08-16 Thread Lars Tangvald

Source: mysql-8.0
Version: 8.0.23
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for July 2021 lists CVEs affecting 
MySQL 8.0

that are fixed in 8.0.26

CVE list:

  - CVE-2019-17543 CVE-2021-2339 CVE-2021-2340 CVE-2021-2342
  - CVE-2021-2352 CVE-2021-2354 CVE-2021-2356 CVE-2021-2357
  - CVE-2021-2367 CVE-2021-2370 CVE-2021-2372 CVE-2021-2374
  - CVE-2021-2383 CVE-2021-2384 CVE-2021-2385 CVE-2021-2387
  - CVE-2021-2389 CVE-2021-2390 CVE-2021-2399 CVE-2021-2402
  - CVE-2021-2410 CVE-2021-2412 CVE-2021-2417 CVE-2021-2418
  - CVE-2021-2422 CVE-2021-2424 CVE-2021-2425 CVE-2021-2426
  - CVE-2021-2427 CVE-2021-2429 CVE-2021-2437 CVE-2021-2440
  - CVE-2021-2441 CVE-2021-2444 CVE-2021-22901


Ref: https://www.oracle.com/security-alerts/cpujul2021.html#AppendixMSQL

Regards,

Lars Tangvald



Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init

2021-08-16 Thread Justus Winter
Package: debian-installer
Version: 20210731
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

I'm trying to install Debian Bullseye on a ProLiant m400 Server
Cartridge.  The cartridge is in EFI mode, we boot the EFI shim, GRUB,
the kernel, and the netboot initrd via PXE and tftp.  We added the
necessary kernel command line flags to redirect the kernel log to the
serial console early on, and various debugging flags.

Reading the log we believe that there are two problems.  First, while
bringing up additional CPU cores, we see them crash immediately.
Adding nosmp to the kernel command line avoids this, but doesn't make
the second problem go away.  Second, the kernel calls acpi_init, which
does not seem to return.

~~~ boot log ~~~
U-Boot 2013.04 (Oct 02 2015 - 14:44:51)

ProLiant m400 Server Cartridge - U02 (10/02/2015)
Copyright 2013 - 2015 Hewlett-Packard Development Company, L.P.
Copyright 2000 - 2012 Wolfgang Denk, DENX Software Engineering, w...@denx.de


CPU0: APM ARM 64-bit Potenza Rev B0 2400MHz PCP 2400MHz
 32 KB ICACHE, 32 KB DCACHE
 SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz
Boot from SPI-NOR
Slimpro FW: Ver: 2.3 (build 2015/03/16)
PMD: 960 mV
SOC: 950 mV
I2C:   ready
DRAM:  ECC 64 GiB @ 1333MHz
Using default environment

API sig @ 0x004ffdf13170
In:serial
Out:   serial
Err:   serial
CPUs:  
CPLD: 0B
SF: Detected MX25L12805D with page size 64 KiB, total 16 MiB
SF: 16384 KiB MX25L12805D at 0:0 is now current device

SF: flash read success (17417 bytes @ 0xe)
.
SF: flash read success (65568 bytes @ 0xc)

SF: flash read success (1477 bytes @ 0x10)
Node Boot Start Time: 2021-08-16T09:56:54
Node Serial Number: CN7447V0BK
Cartridge Chassis Slot ID: 26
Cartridge Serial Number: CN7447V0BK
Chassis Serial Number: CZ3450K3J5
Chassis Asset Tag:
Node UUID: 4445FA0A-122C-52F2-8764-A549A7928A4B
Product ID: 721717-B21
Timezone Name: Europe/London
Loading UEFI ...
SF: flash read success (3604480 bytes @ 0x20)
## Starting application at 0x400200 ...

ProLiant System BIOS U02 v1.01 (10/02/2015)
(C) Copyright 1982 - 2015 Hewlett-Packard Development Company, L.P.
Early system initialization, please wait...
Processor Root Ports Initialization
BIOS Configuration Initialization
Early PCI Initialization - Start
Early PCI Initialization - Complete
Switching console output to Primary Video. Please wait...
(C) Copyright 1982 - 2015 Hewlett-Packard Development Company, L.P.
HP ProLiant m400 Server
BIOS Version: U02 v1.01 (10/02/2015)
Serial Number: CN7447V0BK

System Memory: 64 GB
1 Processor(s) detected, 8 total cores enabled, Proc 1: X-Gene

HP Power Profile Mode: Balanced Power and Performance

Boot Mode: UEFI


For access via BIOS Serial Console:
Press 'ESC+9' for System Utilities
Press 'ESC+@' for Network Boot



>> Booting Embedded LOM 1 Port 1 : Port 1 - Mellanox Network Adapter (PXE IPv4)

>> Booting PXE over IPv4.
  Station IP address is 192.168.103.26

  Server IP address is 192.168.103.253
  NBP filename is debian-stable/debian-installer/arm64/bootnetaa64.efi
  NBP filesize is 856064 Bytes
 Downloading NBP file...

  NBP file downloaded successfully.
Fetching Netboot Image
Welcome to GRUB!

   GNU GRUB  version 2.04-20

 /\
 |*Install|
 | Graphical install  |
 | Advanced options ...   |
 | Dark theme option...   |
 | Install with speech synthesis  |
 ||
 ||
 ||
 ||
 ||
 ||
 ||
 ||
 \/

  Use the ^ and v keys to select which entry is highlighted.
  Press enter to boot the selected OS, `e' to edit the commands
  before booting or `c' for a command-line.



   GNU GRUB  version 2.04-20

 /\
 |setparams 'Install' |
 |

Processed: tagging 957588

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

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

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



Processed: tagging 992234

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

> tags 992234 + sid bookworm
Bug #992234 [tmuxinator] uninstallable; incompatible with tmux 3.2
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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



Processed: tagging 992233

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

> tags 992233 + bookworm
Bug #992233 [tmuxinator] tmuxinator: Uninstallable due to new tmux version
Added tag(s) bookworm.
> thanks
Stopping processing here.

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



Bug#992234: uninstallable; incompatible with tmux 3.2

2021-08-16 Thread Romain Francoise
Package: tmuxinator
Version: 2.0.2-1
Severity: serious

tmux 3.2a is now in sid, which makes tmuxinator uninstallable because it
is apparently incompatible and has the following Depends field:

Depends: ruby | ruby-interpreter, ruby-erubis, ruby-thor, ruby-xdg, tmux (<< 
3.2)

Please update the package to a compatible version ASAP as this will
prevent tmux from migrating to bookworm properly.

Thanks.



Bug#992233: tmuxinator: Uninstallable due to new tmux version

2021-08-16 Thread Axel Beckert
Package: tmuxinator
Version: 2.0.2-1
Severity: serious
Tags: sid bookmworm

With the recent upload of tmux 3.2a-3 to unstable, tmuxinator became
uninstallable in Debian Unstable:

# aptitude install tmuxinator
The following NEW packages will be installed:
  tmuxinator{b}
0 packages upgraded, 1 newly installed and 0 to remove.
Need to get 23.6 kB of archives. After unpacking 104 kB will be used.
The following packages have unmet dependencies:
 tmuxinator : Depends: ruby-xdg but it is not going to be installed
  Depends: tmux (< 3.2) but 3.2a-3 is installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) tmuxinator [Not Installed]

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

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



Processed: severity of 992216 is wishlist

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

> severity 992216 wishlist
Bug #992216 {Done: Carsten Schoenert } [thunderbird] 
thunderbird: Version 91 available upstream and fixes security problems
Severity set to 'wishlist' from 'grave'
> thanks
Stopping processing here.

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



Bug#992229: haskell-gi-gdkpixbuf FTBFS: Could not find module ‘GI.GModule.Structs.Module’

2021-08-16 Thread Adrian Bunk
Source: haskell-gi-gdkpixbuf
Version: 2.0.24-1
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/package.php?p=haskell-gi-gdkpixbuf&suite=sid

...
[20 of 25] Compiling GI.GdkPixbuf.Structs.PixbufModule ( 
GI/GdkPixbuf/Structs/PixbufModule.hs, 
dist-ghc/build/GI/GdkPixbuf/Structs/PixbufModule.o )

GI/GdkPixbuf/Structs/PixbufModule.hs:194:1: error:
Could not find module ‘GI.GModule.Structs.Module’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
|
194 | import qualified GI.GModule.Structs.Module as GModule.Module
| 
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1