date:20220615

Tags: + patch
thanks

Here's the small code change to fix the problem.  I built and
installed the patched version locally, and did 2 successful
add-apt-repository's to add ppa's.  Without the patch, every  attempt
failed (though admittedly each of those attempts was with a single ppa
and sometimes the problem seemed to be the keyserver was down).

I found only a single invocation of apt-key in ppa.py, and so I don't
think there are any other spots that need changing.

BTW, I don't know if my pseudo-headers will do the trick; I'm trying
to add a patch tag to the bug.

On Fri, Jun 10, 2022 at 10:27 PM Debian Bug Tracking System
 wrote:
>
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1012649: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012649.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   ross.boy...@ucsf.edu
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
>  Julian Andres Klode 
>
> If you wish to submit further information on this problem, please
> send it to 1012...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1012649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012649
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
diff --git a/debian/changelog b/debian/changelog
index 22af59f..c3a2736 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+software-properties (0.96.20.2-2.1rb1) unstable; urgency=medium
+
+  * Use exported key when adding to approved keys (Closes: #1012649).
+
+ -- Ross Boylan   Tue, 14 Jun 2022 21:22:07 -0700
+
 software-properties (0.96.20.2-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --git a/softwareproperties/ppa.py b/softwareproperties/ppa.py
index 23f848d..30b70a7 100644
--- a/softwareproperties/ppa.py
+++ b/softwareproperties/ppa.py
@@ -268,7 +268,7 @@ class AddPPASigningKey(object):
 apt_keyring = os.path.join(trustedgpgd, "%s.gpg" % (
 encode(ppa_info["reference"][1:])))
 res = subprocess.call(["apt-key", "--keyring", apt_keyring, "add",
-tmp_keyring])
+tmp_export_keyring])
 # cleanup
 cleanup(tmp_keyring_dir)
 return (res == 0)

Bug#1010785: gdome2: reproducible-builds: embedded build paths libgdome.so.*

2022-06-15 Thread Vagrant Cascadian

Control: found 1010785 0.8.1+debian-8

On 2022-05-09, Vagrant Cascadian wrote:
> The build path is embedded in /usr/lib/libgdome.so.0.8.1:
>
>   
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/gdome2.html
>
>   /build/1st/gdome2-0.8.1+debian/libgdome/gdome.c:65
>   vs.
>   /build/2/gdome2-0.8.1+debian/2nd/libgdome/gdome.c:65
>
>
> The attached patch to debian/rules fixes this by passing
> -ffile-prefix-map in CFLAGS and ensuring CFLAGS is passed to configure.
>
> Alternately, updating the packaging to use dh/debhelper at a recent
> compat level would also likely fix this.

Turns out simply switching to dh/debhelper was not sufficient...

Probably adjusting debian/rules with something like:

override_dh_auto_configure:
CFLAGS="$(CFLAGS) -ffile-prefix-map=$(CURDIR)" dh_auto_configure

I'll try and provide an updated patch and confirm the fix at some
point... though if someone else does it first I won't complain! :)


live well,
  vagrant

> From 65c23dfcbf5fd3a59d4a3141430247225e4d4413 Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian 
> Date: Mon, 9 May 2022 23:06:56 +
> Subject: [PATCH] debian/rules: add -ffile-prefix-map to CFLAGS and ensure
>  CFLAGS are passed in the configure phase.
>
> ---
>  debian/rules | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/debian/rules b/debian/rules
> index 5e25754..ae361d7 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -11,13 +11,15 @@ ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
>  INSTALL_PROGRAM += -s
>  endif
>  
> +CFLAGS += -ffile-prefix-map=$(CURDIR)=.
> +
>  configure: configure-stamp
>  configure-stamp:
>   dh_testdir
>   cp /usr/share/misc/config.sub /usr/share/misc/config.guess .
>   libtoolize -c -f
>   autoreconf -f -i
> - ./configure --prefix=/usr \
> + CFLAGS="$(CFLAGS)" ./configure --prefix=/usr \
>   --mandir=\$${prefix}/share/man \
>   --infodir=\$${prefix}/share/info \
>   --with-html-dir=\$${prefix}/share/doc/libgdome2-dev 
> -- 
> 2.36.0


signature.asc
Description: PGP signature

Bug#1012873: qnetstatview: crashes every time on startup

Package: qnetstatview
Version: 1.5.6-2
Severity: important
X-Debbugs-Cc: rossboy...@stanfordalumni.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

If it behaves this way for everyone, severity should be higher because the
package is completely unusable. I am unable to launch the program successfully.

1. When I select it from the menu, nothing visible happens.
2. When run from a terminal it produces a segfault, whether run as a regular
user or as root:


ross@barley:~$ qnetstatview
Segmentation fault
ross@barley:~$ sudo -i
[sudo] password for ross:
root@barley:~# qnetstatview
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Segmentation fault
root@barley:~#


I am running under KDE.



- -- System Information:
Debian Release: 11.3
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-15-amd64 (SMP w/8 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 qnetstatview depends on:
ii  libc6   2.31-13+deb11u3
ii  libgcc-s1   10.2.1-6
ii  libqt5core5a5.15.2+dfsg-9
ii  libqt5gui5  5.15.2+dfsg-9
ii  libqt5network5  5.15.2+dfsg-9
ii  libqt5widgets5  5.15.2+dfsg-9
ii  libstdc++6  10.2.1-6

qnetstatview recommends no packages.

qnetstatview suggests no packages.


-BEGIN PGP SIGNATURE-

iQFSBAEBCgA8FiEEreS674/HIyV9gBfdnAYPmOsbK2AFAmKqlvceHHJvc3Nib3ls
YW5Ac3RhbmZvcmRhbHVtbmkub3JnAAoJEJwGD5jrGytg3oAIAI/q3/piWKFaVF6M
zj7BzjottbROrYPQzcUcC+XiZ0IW6L5Ntzi1U1v7llZSSlhxnWlbLPrg6mkunUeT
ipbMEUGQC5iLH1gmFzeugXv8oLOwcbiOeFrtStjTkOIciOk6suziBpW+RiAL9qA9
OG0n7ixaQPN8tMOpmZesVn7Vs1l1FgAxIqmM5yZ7kwrM35AUDTYEkEjW8hn83Esy
Y0Hzfi+nWYg7EZQaXHTRQQYo4H6XruD+qL7G7dUv1QpW2dw7i1nQLa20B+pgHRvG
ZXYTGQWtz5RWQ7FW328I7quUspOBM1URjNFZbjN69wTf3qv4YmZw1/wzAEfkwzPb
ksr9GSQ=
=ZmQA
-END PGP SIGNATURE-

Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?

2022-06-15 Thread David

On Thu, 16 Jun 2022 at 06:33, Thomas Schmitt  wrote:

> i wrote:
> > > https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos

> Nevertheless, it should be tested independently of me whether it can be
> tricked into destroying existing data on disk or leaving temporary files
> on disk.

Hi Thomas,

Thank you for your many valued contributions to Debian community!

As a casual observer, can I politely suggest a couple of things
regarding this script:

1) Consider checking the script using the https://www.shellcheck.net/
tool and looking at the warnings it gives. In particular iterating
over the output of 'ls' is not advisable.

2) Consider whether you do want your script to depend on bash, or
perhaps remove any bash-dependent features and make it
posix-compatible so that it can run in for example Debian's default
shell, dash. This can be checked by changing the first line of the
script to '#!/bin/sh' and checking again with the shellcheck tool.
I tried that and it looks like there are no obstacles to doing that,
just small changes.

Bug#1011684: t4kcommon: FTBFS: t4k_menu.c:1264:6: error: conflicting types for ‘set_font_size’; have ‘void(_Bool)’

2022-06-15 Thread Stefan Kropp

Control: owner -1 !
Control: tags -1 + patch

The problem is the declaration of function set_font_size. I added
the bool parameter to the declaration.

-voidset_font_size();
+voidset_font_size(bool);

See attached patch file for more information.
Index: b/src/t4k_menu.c
===
--- a/src/t4k_menu.c
+++ b/src/t4k_menu.c
@@ -151,7 +151,7 @@ SDL_Surface**   render_buttons(MenuNode*
 char*   find_title_length(MenuNode* menu, int* length);
 char*   find_longest_text(MenuNode* menu, int* length);
 int find_longest_menu_page(MenuNode* menu);
-voidset_font_size();
+voidset_font_size(bool);
 voidprerender_menu(MenuNode* menu);
 int		min(int a, int b);
 int		max(int a, int b);

Bug#1012564: openssl: ckermit can't connect to telnetd-ssl with openssl 3.0.3-7

2022-06-15 Thread Arthur Marsh

Package: openssl
Version: 3.0.3-8
Followup-For: Bug #1012564

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I also found that telnet-ssl and ckermit could not connect to telnetd-ssl
if openssl 3.0.3-8 was installed.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

If I kept openssl at version 3.0.3-6, both ckermit and telnet-ssl could
connect to telnetd-ssl.

   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 5.19.0-rc2+ (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages openssl depends on:
ii  libc62.33-7
ii  libssl3  3.0.3-8

openssl recommends no packages.

Versions of packages openssl suggests:
ii  ca-certificates  20211016

-- no debconf information

Bug#896916: patch

2022-06-15 Thread Matt Barry

tags -1 + patch
thanks

Salsa PR 27 - implements the strategy Marc describes above.

Bug#1012800: ncurses-term: Terminfo entry jfbterm should not be linked to kon

2022-06-15 Thread Steven Shiau




On 6/16/2022 4:09 AM, Thomas Dickey wrote:

(I don't seem to have a source tarball for that at hand)

Maybe you can check this?
https://src.fedoraproject.org/repo/pkgs/kon2/kon2-0.3.9b.tar.gz/
The source tarball is:
https://src.fedoraproject.org/repo/pkgs/kon2/kon2-0.3.9b.tar.gz/f9f4da5d95f0010972a85d73a3b3addb/kon2-0.3.9b.tar.gz

Steven

--
Steven Shiau 
Public Key Server PGP Key ID: 4096R/163E3FB0
Fingerprint: EB1D D5BF 6F88 820B BCF5  356C 8E94 C9CD 163E 3FB0

Bug#1012872: software-properties-common: add-apt-repository man page appears garbled, confusing and incomplete

Package: software-properties-common
Version: 0.96.20.2-2.1rb1
Severity: normal
X-Debbugs-Cc: rossboy...@stanfordalumni.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

**Garbled**
The REPOSITORY STRING section of the man page refers to 3 forms.  Usually I
would expect a "form" to be a particular form of the command line in the
SYNOPSIS, but there is only a single form given there.

The REPOSITORY STRING section, in the first sentence, says that REPOSITORY can
either be a line in the form ppa:... or a distribution component.  That's 2
alternatives.  Which also doesn't match 3 forms.

The first sentence says ppa: is added directly to sources.list, with a link to
that man page.  But the sources.list man page has no references to ppa's (which
is probably why a couple of sentences later says that ppa: specifications are
rewritten before insertion to sources.list).

If we try to interpret the subsequent discussion of forms as relating to this,
we have the problem that there are 2 alternatives but 3 forms.  And the second
form is a ppa, even though that was the first alternative in the opening
sentence.  And the paragraph about the "second form" says the ppa will be
expanded, but the opening description says it is "a line that can be added
directly".

**Confusing**

It is not clear to me what is meant by a "distribution component", and I don't
know what it means that it will be "enabled for all sources".

There is a --massive-debug option, described as "print a lot of debug
information." It doesn't, at least when adding a repository.

And the addition of a ppa doesn't actually work, but that's a separate issue:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012649

- --remove turns this command from "add" to "subtract".  Using add-xxx to remove
is a bit confusing and surprising, though not unprecedented.  Perhaps a rm-apt-
repository command could be added as a symlink, with the usual tricks so that
behavior of the program depends on how it's invoked.

**Incomplete**

When adding a ppa to sources.list a release gets inserted as well.  It was
"kinetic" for all the ones I tried, including one repository that didn't have
anything for the kinetic release.  The insertion of a release seems worth
mentioning along with how the release is chosen and how, if at all, one can
alter the choice.  Perhaps this the "distribution component" referred to
earlier?

**Speculation**

The exact opening of the garbled section is
  REPOSITORY  can  be  either a line that can be added directly to
sources.list(5),
  in the form ppa:/ for adding Personal Package Archives, or a
  distribution component to enable.
The material between commas, starting with "in the form ppa:" appears to be an
appositive, a way of rephrasing that which came before it (actually it
restricts the meaning).  Given the previously noted fact that the thing before
(line that can be added directly) means something different from a ppa, I think
the intended meaning is
  REPOSITORY can take 3 forms
1. a line that can be added directly to sources.list
2. ppa:/ for adding Personal Package Archives
3. a distribution component to enable.
Then the 3 forms discussed in the rest of this section refer to those 3
alternatives, in that order.

This interpretation/rewrite resolves most of the issues in the **Garbled**
section, although it might be better if the SYNOPSIS actually did show 3 forms
directly.



- -- System Information:
Debian Release: 11.3
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-15-amd64 (SMP w/8 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 software-properties-common depends on:
ii  ca-certificates  20210119
ii  gir1.2-glib-2.0  1.66.1-1+b1
ii  gir1.2-packagekitglib-1.01.2.2-2
ii  python-apt-common2.2.1
ii  python3  3.9.2-3
ii  python3-dbus 1.2.16-5
ii  python3-gi   3.38.0-2
ii  python3-software-properties  0.96.20.2-2.1rb1

Versions of packages software-properties-common recommends:
ii  packagekit  1.2.2-2

software-properties-common suggests no packages.


-BEGIN PGP SIGNATURE-

iQFSBAEBCgA8FiEEreS674/HIyV9gBfdnAYPmOsbK2AFAmKqeHYeHHJvc3Nib3ls
YW5Ac3RhbmZvcmRhbHVtbmkub3JnAAoJEJwGD5jrGytg++UH/0eJe1VMqT3iuvkS
Vu3GcCldZofsuE9t+/uqfvnpXOhO50U/oJR8JUYA3uPHKxC5l7fQ2t/DcjTFWQ73
kliPkOGlYkGYNif+xgoOd68joShDl7MA9DZggRvghGjzj1nMeQ3gPbnbn0Y1guRh
br0l65Ypp1xicfT7M8050EPYapEBqFZexlmoVnzcT7Ub18IoiLi9iKAlYcnroYjz
dyrEQFJvAaZWWsCNrW1g27fa2wLjzWmBBmgESVkdEODp2ZzZxOnvlVrOKM9VEWRj
EEGtu6/DCWqjE5oTQnG571uzTqfAnhgcp4DmT4E8AkwhXQmUjOmFooz6LEdQHsol
WGR2hzk=
=u0JB
-END PGP SIGNATURE-

Bug#1012632: libffi: d/copyright is incomplete


Control: tags -1 patch

Please find a copyright file attached which is in machine-readable format.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment: This package was debianized by Matthias Klose 
Source: https://github.com/libffi/libffi/releases
Upstream-Contact:
Anthony Green 
GCC developers
See the README and below in the list of copyright holders for a more
complete list.

Files: *
Copyright:
Copyright (c) 1996-2011 Red Hat, Inc.
Copyright (C) 1996-2011 Anthony Green
Copyright (C) 1996-2010 Free Software Foundation, Inc
Copyright (c) 2003, 2004, 2006, 2007, 2008 Kaz Kojima
Copyright (c) 2010, 2011, Plausible Labs Cooperative , Inc.
Copyright (c) 2010 CodeSourcery
Copyright (c) 2012 Alan Hourihane
Copyright (c) 1998 Andreas Schwab
Copyright (c) 2012, 2016 Thorsten Glaser
Copyright (c) 2000 Hewlett Packard Company
Copyright (c) 2009 Bradley Smith
Copyright (c) 2008 David Daney
Copyright (c) 2004 Simon Posnjak
Copyright (c) 2005 Axis Communications AB
Copyright (c) 1998 Cygnus Solutions
Copyright (c) 2004 Renesas Technology
Copyright (c) 2002, 2007  Bo Thorsen 
Copyright (c) 2002 Ranjit Mathew
Copyright (c) 2002 Roger Sayle
Copyright (c) 2000, 2007 Software AG
Copyright (c) 2003 Jakub Jelinek
Copyright (c) 2000, 2001 John Hornkvist
Copyright (c) 1998 Geoffrey Keating
Copyright (c) 2008 Björn König
Copyright (c) 2021 Microsoft, Inc.
Copyright (c) 2019 Microsoft Corporation.
Copyright (c) 2012 Alexandre K. I. de Mendonca 

Copyright (c) 2012 Paulo Pizarro 
Copyright (c) 2015 Michael Knyszek 
Copyright (c) 2011 Timothy Wall
Copyright (c) 2020 Kalray
Copyright (c) 2013 Tensilica, Inc.
Copyright (c) 2011-2012 Tilera Corp.
Copyright (c) 2009-2012 ARM Ltd.
Copyright (c) 2013 IBM
Copyright (C) 2011 Kyle Moffett
Copyright (c) 1998 Geoffrey Keating
Copyright (c) 2013 The Written Word, Inc.
Copyright (c) 2013 Imagination Technologies
Copyright (c) 2013 Synopsys, Inc. (www.synopsys.com)
Copyright (c) 2014 Sebastian Macke 
Copyright (c) 2012, 2013 Xilinx, Inc
Copyright (c) 2013 Miodrag Vallat.  
Copyright (c) 2013 Mentor Graphics.
Copyright (c) 2020 Madhavan T. Venkataraman
License: Expat
Comment: See source files for details.
 The libffi source distribution contains certain code that is not part
 of libffi, and is only used as tooling to assist with the building and
 testing of libffi.  This includes the msvcc.sh script used to wrap the
 Microsoft compiler with GNU compatible command-line options,
 make_sunver.pl, and the libffi test code distributed in the
 testsuite/libffi.bhaible directory.  This code is distributed with
 libffi for the purpose of convenience only, and libffi is in no way
 derived from this code.

Files: doc/libffi.*
Copyright: (C) 2008-2019, 2021 Anthony Green and Red Hat, Inc.
License: Expat

Files: install-sh
Copyright: (C) 1994 X Consortium
License: X11
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to
 deal in the Software without restriction, including without limitation the
 rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
 sell copies of the Software, and to permit persons to whom the Software is
 furnished to do so, subject to the following conditions:
 .
 The above copyright notice and this permission notice shall be included in
 all copies or substantial portions of the Software.
 .
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
 X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
 AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC-
 TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 .
 Except as contained in this notice, the name of the X Consortium shall not
 be used in advertising or otherwise to promote the sale, use or other deal-
 ings in this Software without prior written authorization from the X Consor-
 tium.
Comment: FSF changes to this file are in the public domain.

Files: libtool-ldflags
Copyright: (C) 2005 Free Software Foundation, Inc.
License: GPL-2+
Comment: Contributed by CodeSourcery, LLC.

Files: make_sunver.pl
Copyright: (C) 2010, 2011, 2012, 2013 Free Software Foundation, Inc.
License: GPL-3+
Comment: Upstream does not have the license details.
 ffmpeg includes this software as GPL-3+.

Files: msvcc.sh
Copyright:
 The Initial Developer of the Original Code is
 Timothy Wall .
 Portions created by the Initial Developer are Copyright (C) 2009
 the Initial Developer. All Rights Reserved.
Comment: Contributor(s): Daniel Witte 
License: MPL-1.1 or GPL-2+ or LGPL-2.1+
 The

Bug#1012829: linux-image-5.17.0-3-amd64: intel_iommu=igfx_off workaround required for graphics card

2022-06-15 Thread Troy Telford

You are correct.

5.17.3-1 worked fine and 5.17.6-1 (and 5.17.11-1) are broken.

"Issues with Audio out via HDMI” is a *far* better description for the bug 
report. (Facepalm).

Setting intel_iommu=igfx_off is a workaround which addresses the issue for me.

I’ll see if I can find the issue in the list, but I’m not familiar with the 
kernel internals, so it’ll be mostly an adventure with git. I’ll be quite happy 
if I can find the file (or commit) where the change occurred.

> On Jun 15, 2022, at 2:26 AM, Diederik de Haas  wrote:
> 
> Control: tag -1 moreinfo
> 
> On Wednesday, 15 June 2022 03:27:23 CEST Troy Telford wrote:
>>After scouring my logs I've found this started after my
>> first boot of kernel 5.17.6-1 (2022-05-14). I started having issues with
>> audio out via HDMI - especially if the device had its input changed or was
>> turned off.
>> 
>>Kernel 5.17.0-1-amd64 (Debian 5.17.3-1 (2022-04-18) does not
>> have this issue, which should help reduce the Δ somewhat.
> 
> IIUC, kernel 5.17.3-1 was fine and 5.17.6-1 was broken?
> If that's the case, then the issue should be in the following list:
> https://tracker.debian.org/news/1324075/accepted-linux-5176-1-source-into-unstable-unstable/
> 
> And is the issue of this bug report "issues with audio out via HDMI"?
> The title of this bug report looks to describe a (potential) workaround.



signature.asc
Description: Message signed with OpenPGP

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

2022-06-15 Thread Ben Hutchings

On Mon, 2022-06-13 at 18:23 +0200, Ben Hutchings wrote:
[...]
> I can confirm that this module does not load, and this means it has an
> invalid signature.  The detached signature present in the source
> package seems to be truncated (408 bytes long, where for all other
> modules the detached signature is 411 bytes long).
> 
> The amd64 kernel package is also affected, but for a different module
> (xt_l2tp).
> 
> Since the truncated signatures are in the source packages, this is a
> problem introduced by the code signing service and will need to be
> fixed there.

I wrote a script to check for short signatures (and other unexpected
things) in detached signature files:
https://salsa.debian.org/kernel-team/kernel-team/-/blob/master/scripts/benh/check-sig-params

I've now run that over all linux-signed-* packages available on
snapshot.debian.org.  It found short signatures (in all cases, a raw
signature length of 254 bytes rather than 256 bytes) for the following
binary packages, versions, and files:

linux-image-4.19.0-0.bpo.4-686-pae 4.19.28-2~bpo9+1 
lib/modules/4.19.0-0.bpo.4-686-pae/kernel/drivers/usb/storage/ums-realtek.ko
linux-image-4.19.0-0.bpo.4-amd64 4.19.28-2~bpo9+1 
lib/modules/4.19.0-0.bpo.4-amd64/kernel/drivers/iio/gyro/bmg160_i2c.ko
linux-image-4.19.0-0.bpo.4-rt-amd64 4.19.28-2~bpo9+1 
lib/modules/4.19.0-0.bpo.4-rt-amd64/kernel/drivers/mtd/chips/map_ram.ko
linux-image-4.19.0-0.bpo.5-amd64 4.19.37-4~bpo9+1 
lib/modules/4.19.0-0.bpo.5-amd64/kernel/drivers/video/fbdev/via/viafb.ko
linux-image-4.19.0-0.bpo.6-686 4.19.67-2+deb10u1~bpo9+1 
lib/modules/4.19.0-0.bpo.6-686/kernel/drivers/media/usb/hackrf/hackrf.ko
linux-image-4.19.0-4-rt-686-pae 4.19.28-1 
lib/modules/4.19.0-4-rt-686-pae/kernel/drivers/media/tuners/fc2580.ko
linux-image-4.19.0-4-rt-amd64 4.19.28-1 
lib/modules/4.19.0-4-rt-amd64/kernel/drivers/vhost/vringh.ko
linux-image-4.19.0-4-rt-amd64 4.19.28-2 
lib/modules/4.19.0-4-rt-amd64/kernel/drivers/vhost/vringh.ko
linux-image-4.19.0-5-686-pae 4.19.37-2 
lib/modules/4.19.0-5-686-pae/kernel/drivers/bluetooth/ath3k.ko
linux-image-4.19.0-5-686-pae 4.19.37-3 
lib/modules/4.19.0-5-686-pae/kernel/drivers/bluetooth/ath3k.ko
linux-image-4.19.0-5-amd64 4.19.37-1 
lib/modules/4.19.0-5-amd64/kernel/drivers/net/wireless/ralink/rt2x00/rt2500usb.ko
linux-image-4.19.0-5-rt-amd64 4.19.37-5+deb10u2 
lib/modules/4.19.0-5-rt-amd64/kernel/net/ipv4/tcp_hybla.ko
linux-image-4.19.0-17-686 4.19.194-1 
lib/modules/4.19.0-17-686/kernel/drivers/thermal/intel_soc_dts_iosf.ko
linux-image-4.19.0-17-686 4.19.194-2 
lib/modules/4.19.0-17-686/kernel/drivers/thermal/intel_soc_dts_iosf.ko
linux-image-4.19.0-17-686 4.19.194-3 
lib/modules/4.19.0-17-686/kernel/drivers/thermal/intel_soc_dts_iosf.ko
linux-image-4.19.0-17-amd64 4.19.194-1 
lib/modules/4.19.0-17-amd64/kernel/drivers/dma/dw/dw_dmac_core.ko
linux-image-4.19.0-17-amd64 4.19.194-2 
lib/modules/4.19.0-17-amd64/kernel/drivers/dma/dw/dw_dmac_core.ko
linux-image-4.19.0-17-amd64 4.19.194-3 
lib/modules/4.19.0-17-amd64/kernel/drivers/dma/dw/dw_dmac_core.ko
linux-image-4.19.0-18-rt-686-pae 4.19.208-1 
lib/modules/4.19.0-18-rt-686-pae/kernel/drivers/staging/comedi/drivers/jr3_pci.ko
linux-image-4.19.0-19-rt-686-pae 4.19.232-1 
lib/modules/4.19.0-19-rt-686-pae/kernel/fs/sysv/sysv.ko
linux-image-4.19.0-20-amd64 4.19.235-1 
lib/modules/4.19.0-20-amd64/kernel/sound/pci/echoaudio/snd-indigoio.ko
linux-image-4.19.0-20-rt-arm64 4.19.235-1 
lib/modules/4.19.0-20-rt-arm64/kernel/drivers/video/fbdev/arkfb.ko
linux-image-5.2.0-0.bpo.2-amd64 5.2.9-2~bpo10+1 
lib/modules/5.2.0-0.bpo.2-amd64/kernel/drivers/input/keyboard/max7359_keypad.ko
linux-image-5.2.0-2-arm64 5.2.9-1 
lib/modules/5.2.0-2-arm64/kernel/crypto/cast6_generic.ko
linux-image-5.2.0-2-arm64 5.2.9-2 
lib/modules/5.2.0-2-arm64/kernel/crypto/cast6_generic.ko
linux-image-5.2.0-2-rt-686-pae 5.2.9-1 
lib/modules/5.2.0-2-rt-686-pae/kernel/drivers/net/ethernet/intel/ixgb/ixgb.ko
linux-image-5.2.0-2-rt-686-pae 5.2.9-2 
lib/modules/5.2.0-2-rt-686-pae/kernel/drivers/net/ethernet/intel/ixgb/ixgb.ko
linux-image-5.2.0-3-cloud-amd64 5.2.17-1 
lib/modules/5.2.0-3-cloud-amd64/kernel/net/sched/act_skbmod.ko
linux-image-5.3.0-1-amd64 5.3.7-1 
lib/modules/5.3.0-1-amd64/kernel/sound/pci/hda/snd-hda-codec-hdmi.ko
linux-image-5.3.0-2-arm64 5.3.9-3 
lib/modules/5.3.0-2-arm64/kernel/drivers/usb/gadget/function/u_ether.ko
linux-image-5.3.0-2-cloud-amd64 5.3.9-1 
lib/modules/5.3.0-2-cloud-amd64/kernel/fs/nls/nls_koi8-u.ko
linux-image-5.4.0-0.bpo.2-686-pae 5.4.8-1~bpo10+1 
lib/modules/5.4.0-0.bpo.2-686-pae/kernel/drivers/net/phy/aquantia.ko
linux-image-5.4.0-0.bpo.4-rt-arm64 5.4.19-1~bpo10+1 
lib/modules/5.4.0-0.bpo.4-rt-arm64/kernel/drivers/hwmon/lm73.ko
linux-image-5.4.0-3-cloud-amd64 5.4.13-1 
lib/modules/5.4.0-3-cloud-amd64/kernel/net/netfilter/xt_NETMAP.ko
linux-image-5.10.0-0.bpo.9-arm64 5.10.70-1~bpo10+1 
lib/modules/5.10.0-0.bpo.9-arm64/kernel/sound/usb/line6/snd-usb-line6.ko
linux-image-5.10.0-0.bpo.11-rt-686-pae 5.10.92-1~bpo10+1

Bug#1012853: binutils-multiarch: Provides /usr/bin/gp-archive (binutils), /usr/lib/x86_64-linux-gnu/gprofng/libgp-collector.so (libgprofng0:amd64)

Control: found -1 2.38.50.20220615-2
X-Debbugs-CC: d...@debian.org

On Wed, 15 Jun 2022 12:00:34 -0400 Boyuan Yang  wrote:
> Package: binutils-multiarch
> Severity: serious
> X-Debbugs-CC: binut...@elmo.tasta.io d...@debian.org
> Version: 2.38.50.20220615-1
> 
> Hi doko,
> 
> Doing OS upgrade on my Debian Sid amd64 fails with the following error:
> 
> Preparing to unpack .../binutils-multiarch_2.38.50.20220615-1_amd64.deb
...
> Unpacking binutils-multiarch (2.38.50.20220615-1) over (2.38-4) ...
> dpkg: error processing archive /var/cache/apt/archives/binutils-
> multiarch_2.38.50.20220615-1_amd64.deb (--unpack):
>  trying to overwrite '/usr/bin/gp-archive', which is also in package
> binutils 2.38.50.20220615-1
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/binutils-multiarch_2.38.50.20220615-1_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Besides, binutils-multiarch_2.38.50.20220615-1 also tries to overwrite
> /usr/lib/x86_64-linux-gnu/gprofng/libgp-collector.so , which is provided
by
> libgprofng0:amd64 2.38.50.20220615-1.
> 
> The former issue cannot be fixed by "apt install -f". The latter one can
be
> fixed using "apt install -f".

This bug still exist with latest version:

(Reading database ... 801954 files and directories currently installed.)
Preparing to unpack .../binutils_2.38.50.20220615-2_amd64.deb ...
Unpacking binutils (2.38.50.20220615-2) over (2.38-4) ...
dpkg: error processing archive
/var/cache/apt/archives/binutils_2.38.50.20220615-2_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/gprofng', which is also in package binutils-
multiarch 2.38.50.20220615-2
Preparing to unpack .../libgprofng0_2.38.50.20220615-2_amd64.deb ...
Unpacking libgprofng0:amd64 (2.38.50.20220615-2) ...
dpkg: error processing archive
/var/cache/apt/archives/libgprofng0_2.38.50.20220615-2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/gprofng/libgp-collector.so',
which is also in package binutils-multiarch 2.38.50.20220615-2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/binutils_2.38.50.20220615-2_amd64.deb
 /var/cache/apt/archives/libgprofng0_2.38.50.20220615-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Thanks,
Boyuan Yang

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

Bug#1012871: libcamera: Breaks Qt camera support when installed

2022-06-15 Thread Lisandro Damián Nicanor Pérez Meyer

Source: libcamera
Version: 0~git20200629+e7aa92a-8
Severity: important
X-Debbugs-Cc: lisan...@debian.org, pkg-kde-t...@alioth-lists.debian.net

Hi! I've found out that the sole fact of having libcamera0 installed
breaks Qt (tested with Qt 6).

As you can see by comparing the attached files with_libcamera.txt and
without_libcamera.txt calls to gst-device-monitor-1.0 Video differ.

The attached Qt example exemplifies this. Install qt6-base-dev and
qt6-multimedia-dev. Uncompress the tarball and:

cd test
qmake6
make
./test

If your system has a cemra available and libcamera is not installed the
application will list it. If libcamera is installed it will not be
listed.

Somehow libcamera manages to change something on the gstreamer pipeline
that breaks other unrelated software.

I really think this bug ought to be serious as it breaks unrelated
software, but I'll keep that at your discretion.

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

Kernel: Linux 5.18.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.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


camera_test.tar.gz
Description: application/gzip
Probing devices...


Device found:

name  : Integrated Camera: Integrated C
class : Video/Source
caps  : video/x-raw, format=YUY2, width=1280, height=720, 
pixel-aspect-ratio=1/1, framerate=10/1
video/x-raw, format=YUY2, width=960, height=540, 
pixel-aspect-ratio=1/1, framerate=10/1
video/x-raw, format=YUY2, width=848, height=480, 
pixel-aspect-ratio=1/1, framerate=10/1
video/x-raw, format=YUY2, width=640, height=480, 
pixel-aspect-ratio=1/1, framerate=30/1
video/x-raw, format=YUY2, width=640, height=360, 
pixel-aspect-ratio=1/1, framerate=30/1
video/x-raw, format=YUY2, width=424, height=240, 
pixel-aspect-ratio=1/1, framerate=30/1
video/x-raw, format=YUY2, width=352, height=288, 
pixel-aspect-ratio=1/1, framerate=30/1
video/x-raw, format=YUY2, width=320, height=240, 
pixel-aspect-ratio=1/1, framerate=30/1
video/x-raw, format=YUY2, width=320, height=180, 
pixel-aspect-ratio=1/1, framerate=30/1
image/jpeg, width=1280, height=720, pixel-aspect-ratio=1/1, 
framerate=30/1
image/jpeg, width=960, height=540, pixel-aspect-ratio=1/1, 
framerate=30/1
image/jpeg, width=848, height=480, pixel-aspect-ratio=1/1, 
framerate=30/1
image/jpeg, width=640, height=480, pixel-aspect-ratio=1/1, 
framerate=30/1
image/jpeg, width=640, height=360, pixel-aspect-ratio=1/1, 
framerate=30/1
image/jpeg, width=424, height=240, pixel-aspect-ratio=1/1, 
framerate=30/1
image/jpeg, width=352, height=288, pixel-aspect-ratio=1/1, 
framerate=30/1
image/jpeg, width=320, height=240, pixel-aspect-ratio=1/1, 
framerate=30/1
image/jpeg, width=320, height=180, pixel-aspect-ratio=1/1, 
framerate=30/1
properties:
udev-probed = true
device.bus_path = pci-:00:14.0-usb-0:8:1.0
sysfs.path = 
/sys/devices/pci:00/:00:14.0/usb3/3-8/3-8:1.0/video4linux/video0
device.bus = usb
device.subsystem = video4linux
device.vendor.id = 04f2
device.vendor.name = "Chicony\\x20Electronics\\x20Co.\\x2cLtd."
device.product.id = b725
device.product.name = "Integrated\ Camera:\ Integrated\ C"
device.serial = 
Chicony_Electronics_Co._Ltd._Integrated_Camera_0001
device.capabilities = :capture:
device.api = v4l2
device.path = /dev/video0
v4l2.device.driver = uvcvideo
v4l2.device.card = "Integrated\ Camera:\ Integrated\ C"
v4l2.device.bus_info = usb-:00:14.0-8
v4l2.device.version = 332290 (0x00051202)
v4l2.device.capabilities = 2225078273 (0x84a1)
v4l2.device.device_caps = 69206017 (0x0421)
gst-launch-1.0 v4l2src ! ...

Probing devices...

[0:28:36.376627515] [150393]  INFO Camera camera_manager.cpp:293 libcamera 
v0.0.0

Device found:

name  : \_SB_.PC00.XHCI.RHUB.HS08-8:1.0-04f2:b725
class : Source/Video
caps  : image/jpeg, width=320, height=180
image/jpeg, width=320, height=240
image/jpeg, width=352, height=288
image/jpeg, width=424, height=240
image/jpeg, width=640, height=360
image/jpeg, width=640, height=480

Bug#1012666: ITS: wget2

Hi,

在 2022-06-14星期二的 13:35 +0200，Noël Köthe写道：
> Hello Boyuan,
> 
> Am Samstag, dem 11.06.2022 um 09:10 -0400 schrieb Boyuan Yang:
> 
> > After looking into the package you maintain (wget2, 
> > https://tracker.debian.org/pkg/wget2), I found that this package
> > received no maintainer updates in the past 4 years and missed several
> > upstream
> > releases. The request of making new uploads
> > at https://bugs.debian.org/951354
> > was not solved as well. As a result, I am filing an ITS (Intent to
> > Salvage)
> > request against your package according to section 5.12 in Debian's
> > Developers'
> > Reference [1].
> > 
> > My current plan is to package the latest upstream release (2.0.1) and
> > clean up existing bugs.
> > 
> > Please let me know whether you are still willing to maintain this
> > package. According to the criteria listed at [2], I will upload a
> > Non-maintainer Upload (NMU) of this package onto DELAYED/7 after 21
> > days (July 02, 2022) to continue with the package salvaging. If you
> > find it necessary to pause the ITS process, please let me know
> > immediately by replying this bug report.
> 
> Thank you for your email.
> I will be able to work on the package in July (Debconf22) but you are
> welcome to do a NMU before.:) A DELAYED/2 will be fine for me.

It looks like the new version comes with a SONAME bump (libwget0 ->
libwget1) so we will need another round of copyright check. I have finished
an initial packaging refresh but not the copyright review. Please find the
initial version of debian/ directory in the attachment. We can make further
improvement based on this version.

Thanks,
Boyuan Yang



wget2_2.0.1-0.1.debian.tar.xz
Description: application/xz-compressed-tar


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

Bug#1000174: 1000174: bacula-director-pgsql: setup fails with "Unrecognized role option"

Exactly what is the "long standing and nasty problem"?

If my theory about ' being a problem is right (and I did get past this
problem when I omitted it), a stop gap would be to tell people not to
use that character in their password.  It does seem odd that the \'
isn't working to quote it.

Ross

P.S. For some reason I don't seem to have gotten the email with Paul's response.

Bug#1000176: bacula-director-pgsql: setup suggests no password and then rejects it

Thanks for your response. It's not clear to me  what more information
you want; you seem to be following what I did pretty well.

On rereading, I notice an additional ambiguity.  I believe I read
"postgres account with which this package should perform
administrative actions." as meaning the sql account *named* postgres
(or, more generally, the overall sql admin account, which defaults to
be postgres), which has overall admin rights for all postgres
databases.  Partly this is because the setup clearly needs to start
from there in order to create the bacula user!  I now suspect the
intended meaning is the account this package will use, i.e., bacula.
There is also some ambiguity in whether account refers to a database
account (so postgres is an adjective describing the account type) or a
linux account, though in context it seemed to me all references were
to database accounts.

So I think I was attempting to navigate the responses when I had set a
password for bacula but not postgres, and interpreting various
questions as referring to one or the other.  I interpreted the first
question as being about the bacula sql account (password) and the
second as being about the postgres sql account (no password).

My hope is that the setup questions not lead to a dead end, or the
revelation in question #2 of information necessary to answer question
#1 properly.  And I also hope the installer can cope with this split
situation of a password for one account (bacula) but not the other
(postgres).  I know I did eventually get it all working.

Some bacula-specific context may be relevant: there needs to be remote
access to the bacula database since clients may be on different
machines.  Since ident is insecure on a network, that means the bacula
database should have a password, as well as the necessary
configuration to permit remote access using passwords.  So this hybrid
situation (ident only for posgres db user and no password; password
for bacula) seems likely to arise in practice.

I assume your references to "indent" were meant as "ident".

I'm pretty sure postgres allows multiple authentication mechanisms so
one could access accounts on the local machine using ident and access
the same accounts remotely using a password.  The configuration
includes restrictions on which hosts and can use which mechanisms.

My concern about multiple names was mostly that either the installer
or postgres itself would get confused about whether access was local
or remote if postgres is installed with a system name of, e.g.,
pg.me.org and bacula is installed with a name of bac.me.org, but those
are aliases for the same machine.

Ross

Bug#1007717: Updated draft resolution

2022-06-15 Thread Sean Whitton

Hello,

On Wed 15 Jun 2022 at 04:06PM +02, Lucas Nussbaum wrote:

>
> According to https://udd.debian.org/~lucas/format10.cgi (which is based
> on what lintian knows about the archive), there are 114 packages using
> 1.0 with quilt. However, 67 of those are maintained by the Debian X
> team. If you plan to discontinue 1.0+patch-system in the context of
> this bug, it would probably be a good idea to have a discussion with
> them to better understand their use case.

Thanks for this info.

> I personally think that it would be enough for this bug to issue a clear
> statement that we want to move away from 1.0 unless there's a good
> reason, on a per-package basis, not to. That would create a mandate to
> work on surveying the remaining packages and identifying the remaining
> use cases. That would also allow motivated volunteers to work on
> migrating the remaining packages when there's no reason to stay with
> 1.0, using the NMU procedure if needed.

I agree that this would be a good outcome, as expressed by your option 4c.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1012870: defaults should include dbus-daemon

2022-06-15 Thread chrysn

Package: earlyoom
Version: 1.7-1
Severity: wishlist

The default settings, even when applying the suggestions, can easily
cause everything in a desktop session to be killed indirectly: I've
repeatedly seen dbus-daemon falling victim to earlyoom, which does
succeed in freeing a lot of memory, but has the side effect of taking
firefox, xfce4-terminal and a bunch of other processes down with it.

I suggest that dbus-daemon be included in the --avoid list offered in
/etc/default/earlyoom, and possibly even be enabled by default.

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

Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages earlyoom depends on:
ii  init-system-helpers  1.62
ii  libc62.33-7
ii  lsb-base 11.1.0

earlyoom recommends no packages.

earlyoom suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1012869: O: python-pex -- library for generating Python executable zip files

Package: wnpp
Severity: normal

The original maintainer for python-pex, Barry Warsaw , has
retired. As a result, I orphan this package.

This package need some care. New pex 2.x series needs to be packaged. The
packaging system has migrated away from setuptools and thus needs more
investigation.

Maintaining a package requires time and skills.  Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see 
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.  If you are still
uncertain about how to adopt the package, please feel free to let me
know or seek help from other Debian Developers.

Some information about this package:

 Package: pex
 Source: python-pex
 Version: 1.5.3-1
 Architecture: all
 Maintainer: Debian QA Group 
 Installed-Size: 29
 Depends: python3, python3-pex, python3-pkg-resources, python3-requests,
python3-setuptools, python3-wheel, python3:any
 Suggests: python-pex-doc
 Breaks: python-pex-cli (<< 1.0.3-2~)
 Replaces: python-pex-cli (<< 1.0.3-2~)
 Section: python
 Priority: optional
 Homepage: https://github.com/pantsbuild/pex
 Description: library for generating Python executable zip files
  pex is a library for generating .pex (Python EXecutable) files which
  are executable Python environments in the spirit of virtualenvs.  pex
  is an expansion upon the ideas outlined in PEP 441 and makes the
  deployment of Python applications as simple as cp.  pex files may even
  include multiple platform-specific Python distributions, meaning that
  a single pex file can be portable across Linux and OS X.
  .
  pex files can be built using the pex tool.  Build systems such as
  Pants and Buck also support building .pex files directly.


-- 
Thanks,
Boyuan Yang


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

Bug#1012867: bad line in usb.ids

2022-06-15 Thread Daniel Carlson

Package: usb.ids
Version: 2022.02.15-0+deb11u1

Line 23299 in usb.ids, containing "8087 07da  Centrino Advanced-N
6235", causes an error to be printed in the terminal when I run the
command "sudo usbip list -l". The error text is "usbip: error:
Protocol spec without prior Class and Subclass spec at line 23299".

When I checked the upstream version 2022.05.20 I found that this
line has been removed. I've removed the line on my machine and
the error is gone. The issue is mentioned here
https://usb-ids.gowdy.us/read/UD/8087/07da.

The error first occurred for me on my computer running an armbian
image. I've also reproduced it on my desktop running bullseye with
kernel 5.10.0-14-amd64 and usbip version 2.0+5.10.120-1.

Thanks,
Dan

Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?

2022-06-15 Thread Thomas Schmitt

Hi,

i wrote:
> > https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos

Steve McIntyre wrote:
> That might be a useful thing to include in a package. What do you think?

Best would be if debian-cd would take it, so that it can be adapted when
the repository format in the ISOs gets changed. It could be renamed to
e.g. "debian-cd-merge-isos" and become a separate "binary" package from
the debian-cd source package.
I would of course be willing to help with maintaining it.

But first it needs more testing, especially whether the resulting ISO
lacks anything that an ISO-1 from debian-cd with the same packages has.
Zhang Boyang posted a comparison in
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011343#115

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1011343;filename=diff.details.txt;msg=115
about which i ponder:

- Shall the script create a new /.disk/mkisofs ?
  The used xorriso run has few similarity with a xorriso run from
  debian-cd. The pool content and package lists have no influence
  on the xorriso run of debian-cd.
  So it might be better to stay with the original.

- There are some /firmware files missing in the merged ISO. Like
/firmware/arm-trusted-firmware-tools_2.4+dfsg-2_amd64.deb
...
/firmware/gnome-firmware_3.36.0-1_amd64.deb
  They are in the pool of DLBD-1. But how did they get into /firmware of
  Zhang Boyang's CUSTOM(all-in-one) ? (Or: Why aren't they in /firmware
  of DLBD-1 ?)

I hope that the script is sufficiently stable against bad arguments and
bad combinations of ISOs. At least i inserted a lot of error messages
and took care to trigger each of them.
Nevertheless, it should be tested independently of me whether it can be
tricked into destroying existing data on disk or leaving temporary files
on disk.

Have a nice day :)

Thomas

Bug#1012019: It's actually a sphinx issue

2022-06-15 Thread Dmitry Shachnev

Control: reassign -1 src:coq-doc 8.15.1-1
Control: forwarded -1 https://github.com/coq/coq/pull/16193

Hi Julien!

On Sat, Jun 11, 2022 at 09:16:50AM +0200, julien.pu...@gmail.com wrote:
> reassign #1012019 sphinx 4.5.0
> affects #1012019 coq-doc
> forwarded #1012019 https://github.com/sphinx-doc/sphinx/issues/10332
> thanks
>
> Hi,
>
> the problem with coq-doc actually stems from a sphinx 4.5.0 issue with
> latex: https://github.com/sphinx-doc/sphinx/issues/10332

Actually the issue is in coq-doc because it's monkey-patching one of Sphinx
methods, and the code is based on old version of Sphinx.

I submitted a pull request upstream to rebase the monkey-patched version on
top of the new version of that method (see Forwarded link). With that patch
coq-doc builds successfully.

So reassigning back to coq-doc.

--
Dmitry Shachnev

signature.asc
Description: PGP signature

Bug#984102: NMU: libfm-qt: ftbfs with GCC-11

2022-06-15 Thread Dmitry Shachnev

Hi Mateusz!

On Wed, Jun 15, 2022 at 09:36:06PM +0200, Mateusz Łukasik wrote:
> I see that. Fixed again on mentors.

Uploaded. Thank you for the fix!

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1012800: ncurses-term: Terminfo entry jfbterm should not be linked to kon

2022-06-15 Thread Thomas Dickey

On Tue, Jun 14, 2022 at 08:19:13PM +0800, Steven Shiau wrote:
> Package: ncurses-term
> Version: 6.3+20220423-2
> Severity: normal
> 
> Dear Maintainer,
> 
> Terminfo entry jfbterm should not be linked to kon. It causes CJK

That part's debatable (there probably are no active packages for either).
The entry you're commenting about dates from 2006.

REV:1.300   terminfo.src2006/09/09 22:38:37   tom
tags:v5_5_20060916, v5_5_20060909

   reviewed kon (kon2) and the later version jfbterm.  I can run the former,
   and read code for both.  Reviewing, I also noticed that linux was using
   invis, but that's incorrect.
...
# This is based on the Linux console (relies on the console to perform some
# of the functionality), but does not recognize as many control sequences.
# The program comes bundled with an old (circa 1998) copy of the Linux
# console terminfo.  It recognizes some non-ANSI/VT100 sequences such as
#   \E* move cursor to home, as as \E[H
#   \E,Xsame as \E(X
#   \EE move cursor to beginning of row
#   \E[y,xf same as \E[y,xH
#
# Note: The status-line support is buggy (dsl does not work).
kon|kon2|jfbterm|Kanji ON Linux console,
ccc@, hs,
civis@, cnorm@, cvvis@, dsl=\E[?H, flash@, fsl=\E[?F, initc@,
initp@, kcbt@, oc@, op=\E[37;40m, rs1=\Ec, tsl=\E[?T,
use=linux,

Seeing the report, the obvious problem is that in updating "linux" to
use "linux2.6", I altered these (which inherit from "linux"):

# 2011-07-16
#   * add/use xterm+tmux chunk from xterm #271 -TD
#   * resync xterm-new entry from xterm #271 -TD
#   * add E3 extended capability to linux-basic (Miroslav Lichvar)
#   * add linux2.2, linux2.6, linux3.0 entries to give context for E3 -TD
#   * add SI/SO change to linux2.6 entry (Debian #515609) -TD

the smacs/rmacs are SI/SO.

There's a related enacs...

> (Chinese, Japanes, Korean) environment showing weird characters.
> The original terminfo entry jfbterm from it's orignal tarball 0.4.7,

...uploaded in 2011-11-18, using sources dated 2005-02-24.

The accompanying Debian patch takes out the dsl which I commented on.

> could be found here:
> https://launchpad.net/ubuntu/+source/jfbterm/0.4.7-9

However, comparing the 0.4.7 version, I see these differences:

acsc: 
'++\,\,--..00``aaffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~', 
'++\,\,--..00II``aaffgghhjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~'.
enacs: '\E)0', -.
rmacs: '^O', '\E[10m'.
smacs: '^N', '\E[11m'.

So the fix is to undo that detail.

Whether kon and jfbterm should/should not be linked depends on what kon
really does (I don't seem to have a source tarball for that at hand).

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net

signature.asc
Description: PGP signature

Bug#1012655: upstream bug and fix

2022-06-15 Thread Salvatore Bonaccorso

Hi,

On Wed, Jun 15, 2022 at 07:59:27PM +0200, Diederik de Haas wrote:
> On Wednesday, 15 June 2022 17:40:45 CEST Stephan Verbücheln wrote:
> > Kernel 5.18.4 got the patch.
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/driver
> > s/input/mouse/bcm5974.c?id=v5.18.4=v5.18.3
> 
> Excellent, thanks for mentioning that :-)
> 
> > I will just use 5.17 or external mouse until the fix lands in Sid.
> 
> My guess is that the next upload to Sid should have it then.

This assumption is correct :)

Regards,
Salvatore

Bug#984102: NMU: libfm-qt: ftbfs with GCC-11


On 15.06.2022 21:03 +0200, Sebastian Ramacher wrote:


Control: reopen -1

On 2022-06-15 19:54:51 +0200, Bastian Germann wrote:

I am sponsoring a NMU that was provided to fix this.
debdiff is attached.

Thanks, but the fix was incomplete:
https://buildd.debian.org/status/fetch.php?pkg=libfm-qt=i386=0.16.0-3.1=1655316964=0

Cheers



diff -Nru libfm-qt-0.16.0/debian/changelog libfm-qt-0.16.0/debian/changelog
--- libfm-qt-0.16.0/debian/changelog2021-01-08 20:15:46.0 +0100
+++ libfm-qt-0.16.0/debian/changelog2022-06-15 09:59:06.0 +0200
@@ -1,3 +1,10 @@
+libfm-qt (0.16.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with Qt >=5.15.3 and gcc-11. (Closes: #984102)
+
+ -- Mateusz Łukasik   Wed, 15 Jun 2022 09:59:06 +0200
+
  libfm-qt (0.16.0-3) unstable; urgency=high
  
* Update symbols for armel, armhf, i386, mipsel and s390x to fit FTBFS.

diff -Nru libfm-qt-0.16.0/debian/libfm-qt8.symbols 
libfm-qt-0.16.0/debian/libfm-qt8.symbols
--- libfm-qt-0.16.0/debian/libfm-qt8.symbols2021-01-08 12:56:41.0 
+0100
+++ libfm-qt-0.16.0/debian/libfm-qt8.symbols2022-06-15 09:56:41.0 
+0200
@@ -1293,7 +1293,6 @@
   _ZNK2Fm9DeleteJob10metaObjectEv@Base 0.16.0
   _ZNK2Fm9Templates10metaObjectEv@Base 0.16.0
   
_ZNKSt10_HashtableIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_St10shared_ptrIKN2Fm8FileInfoEEESaISD_ENSt8__detail10_Select1stESt8equal_toIS6_ESt4hashIS5_ENSF_18_Mod_range_hashingENSF_20_Default_ranged_hashENSF_20_Prime_rehash_policyENSF_17_Hashtable_traitsILb1ELb0ELb119_M_find_before_nodeEmRS6_m@Base
 0.16.0
- 
_ZNSt10_HashtableIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_St10shared_ptrIKN2Fm8FileInfoEEESaISD_ENSt8__detail10_Select1stESt8equal_toIS6_ESt4hashIS5_ENSF_18_Mod_range_hashingENSF_20_Default_ranged_hashENSF_20_Prime_rehash_policyENSF_17_Hashtable_traitsILb1ELb0ELb14findERS6_@Base
 0.16.0
   
_ZNSt10_HashtableIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_St10shared_ptrIKN2Fm8FileInfoEEESaISD_ENSt8__detail10_Select1stESt8equal_toIS6_ESt4hashIS5_ENSF_18_Mod_range_hashingENSF_20_Default_ranged_hashENSF_20_Prime_rehash_policyENSF_17_Hashtable_traitsILb1ELb0ELb15clearEv@Base
 0.16.0
   
_ZNSt10_HashtableINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N2Fm12FileInfoListEESaISA_ENSt8__detail10_Select1stESt8equal_toIS5_ESt4hashIS5_ENSC_18_Mod_range_hashingENSC_20_Default_ranged_hashENSC_20_Prime_rehash_policyENSC_17_Hashtable_traitsILb1ELb0ELb15clearEv@Base
 0.16.0
   
_ZNSt14_Fwd_list_baseISt10shared_ptrIKN2Fm8IconInfoEESaIS4_EE14_M_erase_afterEPSt19_Fwd_list_node_baseS8_@Base
 0.16.0
@@ -1308,7 +1307,6 @@
   
_ZNSt6vectorIN2Fm8FilePathESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.16.0
   
_ZNSt6vectorIN2Fm8FilePathESaIS1_EE17_M_realloc_insertIJRS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.16.0
   
_ZNSt6vectorIN2Fm8FilePathESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.16.0
- 
_ZNSt6vectorIN2Fm8FilePathESaIS1_EE6insertEN9__gnu_cxx17__normal_iteratorIPKS1_S3_EERS6_@Base
 0.16.0
   
_ZNSt6vectorIN2Fm8FilePathESaIS1_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS1_S3_EES7_@Base
 0.16.0
   
_ZNSt6vectorIPN2Fm12ThumbnailJobESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.16.0
   
_ZNSt6vectorIPN2Fm16DirTreeModelItemESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.16.0
@@ -1319,12 +1317,12 @@
   
_ZNSt6vectorISt10shared_ptrIKN2Fm8FileInfoEESaIS4_EE12emplace_backIJRKS4_EEEvDpOT_@Base
 0.16.0
   
_ZNSt6vectorISt10shared_ptrIKN2Fm8FileInfoEESaIS4_EE17_M_realloc_insertIJRKS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base
 0.16.0
   
_ZNSt6vectorISt10shared_ptrIKN2Fm8FileInfoEESaIS4_EE17_M_realloc_insertIJS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base
 0.16.0
- 
_ZNSt6vectorISt10shared_ptrIKN2Fm8MimeTypeEESaIS4_EE12emplace_backIJRKS4_EEEvDpOT_@Base
 0.16.0
   
_ZNSt6vectorISt10shared_ptrIKN2Fm8MimeTypeEESaIS4_EE17_M_realloc_insertIJRKS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base
 0.16.0
   
_ZNSt6vectorISt10shared_ptrIN2Fm11ThumbnailerEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
 0.16.0
   
_ZNSt6vectorISt10shared_ptrIN2Fm12TemplateItemEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
 0.16.0
   
_ZNSt6vectorISt10shared_ptrIN2Fm12TemplateItemEESaIS3_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS3_S5_EES9_@Base
 0.16.0
   
_ZNSt6vectorISt10shared_ptrIN2Fm6FolderEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
 0.16.0
+ 
_ZNSt6vectorISt10unique_ptrIN2Fm8ArchiverESt14default_deleteIS2_EESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 0.16.0

Bug#1012768: Bug#1012785: libgsasl7 depends on outdated gsasl-common version 1.10.0-5

2022-06-15 Thread Sebastian Ramacher

Hi Simon

On 2022-06-14 18:54:30 +0200, Simon Josefsson wrote:
> > > I guess the idea is that all packages that are built against
> > > libgsasl7
> > > is going to be NMU'd through the transition, so that they are built
> > > against libgsasl18 instead.  Then this shouldn't be a problem.
> > 
> > While this won't be a problem in testing and unstable once the
> > transition is done, it could be a problem for bullseye -> bookworm
> > upgrades.
> 
> Okay, this statement, and your entire email, makes me believe that the
> situation is fine for this transition, but we should continue discuss
> if there is something to be improved to handle bullseye->bookworm
> upgrades.  Right?

Right, in general the goal is that the shared library packages are
co-installable to ease the upgrades. That's one of the motivations
behind Policy 8.1.

> > Whether this is a problem for libgsasl, we'll see once upgrade tests
> > for bullseye -> bookworm are started.
> 
> Right.  I can't help but feel unsatisfied by relying on testing rather
> than a complete understanding of what is supposed to happen.
> 
> I would have thought piuparts testing (which I did) would catch
> problems like this.  Maybe I misunderstood what I tested, or it has to
> be tested in a different way.

The automated tests only cover what they can. They essentially just give
some assurance that apt is able to find an upgrade path where the
removal of libgasl7 is a valid solution and that this (dist-)upgrade can
be performed without errors. They do however not cover cases where, say,
an admin needs to upgrade database cluster from one database server
release to the next one and thus needs the packages from bullseye and
bookworm installed at the same time. Now, if libgasl7 would be involved
and force the removal of the bullseye packages, that would be rendered
impossible (or would require a lot more work for users).

(As said earlier, I don't know if libgasl7 has reverse dependencies
where this could be an easier. But I'd prefer if we wouldn't have to
find out during the freeze.)

> I think the upgrade problem will go away once the transition is
> finished.
> 
> > > B) Somehow drop the gsasl-common dependency?  It only contains
> > > translations, which works for both libgsasl7 and libgsasl18.
> > 
> > If gsasl-common only contains translations, would a Recommends:
> > gsasl-common (>= ${source:Version}) (or Depends) be enough? The
> > solution
> > with Depends would not improve the situation for this transition, but
> > only for the next one.
> 
> Yes perhaps -- libgsasl7 and libgsasl18 works without gsasl-common but
> translations will be broken.  Translations shouldn't be broken, hence a
> 'Required:' field.  I guess these things are subjective though.

We have both packages depending and recommending their translations.
This can be argued both ways …

> > > C) Change the versioning dependency, so that new gsasl-common
> > > satisfy
> > > the old libgsasl7 dependency -- but I'm not sure that's possible,
> > > libgsasl7 depends on the same version of gsasl-common.
> > 
> > That won't be possible … unless SRMs accept such a change in stable.
> 
> Indeed, and it wouldn't help if someone didn't upgrade to a "fixed"
> stable gsasl package either, but went directly from current 'gsasl' in
> stable to unstable.
> 
> > > Maybe B) is the right solution?!  We could move the translations
> > > into
> > > libgsasl18 and drop gsasl-common.  Then old libgsasl7 could depend
> > > on
> > > gsasl-common and things will work, and you could have libgsasl18
> > > installed too -- however, they would conflict in files since both
> > > ship
> > > the same translation files... unless we modify the filenames so
> > > they
> > > live in separate directories or basenames.  I'm not sure that is
> > > worth
> > > it.
> > 
> > Note that this requires the translation files contained in libgsasl18
> > to be versioned exactly in the same way as the shared library. See
> > Policy 8.2.
> 
> Reading
> 
> https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#shared-library-support-files
> 
> makes me believe the situation is correct here: translations do not
> change between library SO versions and should thus not be in the
> libgsasl7 or libgsasl18 package, and putting them in a gsasl-common
> seems to be the recommended approach.  However, translations is such a
> widespread class of files that maybe they are discussed elsewhere in
> the policy manual, but I can't find any reference now.
> 
> Maybe what is the problem is the hard versioned dependency from
> libgsasl7 and libgsasl18 on gsasl-common?  Maybe it shouldn't be
> versioned at all, or a >= condition?

… if possible, an unversioned dependency would help a lot.

Cheers
-- 
Sebastian Ramacher

Bug#1012866: RFS: libfm-qt/0.16.0-3.2 [NMU] [RC] -- Language package for libfm-qt


Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "libfm-qt":

 * Package name: libfm-qt
   Version : 0.16.0-3.2
   Upstream Author : [fill in name and email of upstream]
 * URL :https://github.com/lxqt/libfm-qt
 * License : BSD-3-Clause, LGPL-2.1+
 * Vcs :https://salsa.debian.org/lxqt-team/libfm-qt
   Section : x11

The source builds the following binary packages:

  libfm-qt8 - file management support for pcmanfm-qt
  libfm-qt-dev - file management support library for pcmanfm-qt (development 
files)
  libfm-qt-l10n - Language package for libfm-qt

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/libfm-qt/

Alternatively, you can download the package with 'dget' using this command:

  dget 
-xhttps://mentors.debian.net/debian/pool/main/libf/libfm-qt/libfm-qt_0.16.0-3.2.dsc

Changes since the last upload:

 libfm-qt (0.16.0-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update symbols files from build logs. (Closes: #984102)

Regards,
--
  Mateusz Łukasik

Bug#1012865: grub2: Re-enable discovery of other OSes by default (GRUB_DISABLE_OS_PROBER=false)

2022-06-15 Thread Samuel Henrique

Source: grub2
X-Debbugs-Cc: samuel...@debian.org
Version: 2.06-1
Severity: normal

Hello,

Grub's upstream has changed its default behavior regarding discovery
of other OSes by disabling the feature (os-prober).

This has come to my attention when updating grub2 on testing today:
https://salsa.debian.org/grub-team/grub/-/blob/f844128767f947e18f86ba8a32d745f9d7a60b57/debian/NEWS#L1-L5

When briefly discussing this over IRC at debian-devel, I was pointed
at another brief discussion, which has a nice summary of the
reasonings behind it:
https://lists.ubuntu.com/archives/ubuntu-devel/2021-December/041769.html

This is my request for us to not follow upstream's default, and stick
to discovering other OSes in the system, as it was the previous
behavior.

I'm worried that not doing so will lead to a lot of frustration for
our users, as this basically means shipping Debian without dual boot
support out of the box.
The users would need to 1st: know about this issue and 2nd: perform a
configuration change and grub update.

I understand we have the NEWS file in place to warn users upgrading
their systems, and also that grub will print a warning about it, but I
don't think this is good enough as it will catch a lot of users by
surprise.

I also don't think there's a worthy trade-off being made here
(security vs user experience), the Ubuntu mailing list does discuss
better alternatives which would require some more work, but with only
2 options in the table (OS discovery enabled or disabled), I prefer
enabled.

Regards,

-- 
Samuel Henrique

Bug#984102: NMU: libfm-qt: ftbfs with GCC-11

2022-06-15 Thread Sebastian Ramacher

Control: reopen -1

On 2022-06-15 19:54:51 +0200, Bastian Germann wrote:
> I am sponsoring a NMU that was provided to fix this.
> debdiff is attached.

Thanks, but the fix was incomplete:
https://buildd.debian.org/status/fetch.php?pkg=libfm-qt=i386=0.16.0-3.1=1655316964=0

Cheers


> diff -Nru libfm-qt-0.16.0/debian/changelog libfm-qt-0.16.0/debian/changelog
> --- libfm-qt-0.16.0/debian/changelog  2021-01-08 20:15:46.0 +0100
> +++ libfm-qt-0.16.0/debian/changelog  2022-06-15 09:59:06.0 +0200
> @@ -1,3 +1,10 @@
> +libfm-qt (0.16.0-3.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Fix FTBFS with Qt >=5.15.3 and gcc-11. (Closes: #984102)
> +
> + -- Mateusz Łukasik   Wed, 15 Jun 2022 09:59:06 +0200
> +
>  libfm-qt (0.16.0-3) unstable; urgency=high
>  
>* Update symbols for armel, armhf, i386, mipsel and s390x to fit FTBFS.
> diff -Nru libfm-qt-0.16.0/debian/libfm-qt8.symbols 
> libfm-qt-0.16.0/debian/libfm-qt8.symbols
> --- libfm-qt-0.16.0/debian/libfm-qt8.symbols  2021-01-08 12:56:41.0 
> +0100
> +++ libfm-qt-0.16.0/debian/libfm-qt8.symbols  2022-06-15 09:56:41.0 
> +0200
> @@ -1293,7 +1293,6 @@
>   _ZNK2Fm9DeleteJob10metaObjectEv@Base 0.16.0
>   _ZNK2Fm9Templates10metaObjectEv@Base 0.16.0
>   
> _ZNKSt10_HashtableIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_St10shared_ptrIKN2Fm8FileInfoEEESaISD_ENSt8__detail10_Select1stESt8equal_toIS6_ESt4hashIS5_ENSF_18_Mod_range_hashingENSF_20_Default_ranged_hashENSF_20_Prime_rehash_policyENSF_17_Hashtable_traitsILb1ELb0ELb119_M_find_before_nodeEmRS6_m@Base
>  0.16.0
> - 
> _ZNSt10_HashtableIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_St10shared_ptrIKN2Fm8FileInfoEEESaISD_ENSt8__detail10_Select1stESt8equal_toIS6_ESt4hashIS5_ENSF_18_Mod_range_hashingENSF_20_Default_ranged_hashENSF_20_Prime_rehash_policyENSF_17_Hashtable_traitsILb1ELb0ELb14findERS6_@Base
>  0.16.0
>   
> _ZNSt10_HashtableIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_St10shared_ptrIKN2Fm8FileInfoEEESaISD_ENSt8__detail10_Select1stESt8equal_toIS6_ESt4hashIS5_ENSF_18_Mod_range_hashingENSF_20_Default_ranged_hashENSF_20_Prime_rehash_policyENSF_17_Hashtable_traitsILb1ELb0ELb15clearEv@Base
>  0.16.0
>   
> _ZNSt10_HashtableINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N2Fm12FileInfoListEESaISA_ENSt8__detail10_Select1stESt8equal_toIS5_ESt4hashIS5_ENSC_18_Mod_range_hashingENSC_20_Default_ranged_hashENSC_20_Prime_rehash_policyENSC_17_Hashtable_traitsILb1ELb0ELb15clearEv@Base
>  0.16.0
>   
> _ZNSt14_Fwd_list_baseISt10shared_ptrIKN2Fm8IconInfoEESaIS4_EE14_M_erase_afterEPSt19_Fwd_list_node_baseS8_@Base
>  0.16.0
> @@ -1308,7 +1307,6 @@
>   
> _ZNSt6vectorIN2Fm8FilePathESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
>  0.16.0
>   
> _ZNSt6vectorIN2Fm8FilePathESaIS1_EE17_M_realloc_insertIJRS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
>  0.16.0
>   
> _ZNSt6vectorIN2Fm8FilePathESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
>  0.16.0
> - 
> _ZNSt6vectorIN2Fm8FilePathESaIS1_EE6insertEN9__gnu_cxx17__normal_iteratorIPKS1_S3_EERS6_@Base
>  0.16.0
>   
> _ZNSt6vectorIN2Fm8FilePathESaIS1_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS1_S3_EES7_@Base
>  0.16.0
>   
> _ZNSt6vectorIPN2Fm12ThumbnailJobESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
>  0.16.0
>   
> _ZNSt6vectorIPN2Fm16DirTreeModelItemESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
>  0.16.0
> @@ -1319,12 +1317,12 @@
>   
> _ZNSt6vectorISt10shared_ptrIKN2Fm8FileInfoEESaIS4_EE12emplace_backIJRKS4_EEEvDpOT_@Base
>  0.16.0
>   
> _ZNSt6vectorISt10shared_ptrIKN2Fm8FileInfoEESaIS4_EE17_M_realloc_insertIJRKS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base
>  0.16.0
>   
> _ZNSt6vectorISt10shared_ptrIKN2Fm8FileInfoEESaIS4_EE17_M_realloc_insertIJS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base
>  0.16.0
> - 
> _ZNSt6vectorISt10shared_ptrIKN2Fm8MimeTypeEESaIS4_EE12emplace_backIJRKS4_EEEvDpOT_@Base
>  0.16.0
>   
> _ZNSt6vectorISt10shared_ptrIKN2Fm8MimeTypeEESaIS4_EE17_M_realloc_insertIJRKS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base
>  0.16.0
>   
> _ZNSt6vectorISt10shared_ptrIN2Fm11ThumbnailerEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
>  0.16.0
>   
> _ZNSt6vectorISt10shared_ptrIN2Fm12TemplateItemEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
>  0.16.0
>   
> _ZNSt6vectorISt10shared_ptrIN2Fm12TemplateItemEESaIS3_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS3_S5_EES9_@Base
>  0.16.0
>   
> _ZNSt6vectorISt10shared_ptrIN2Fm6FolderEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
>  0.16.0
> + 
>

Bug#1012864: graphviz: new upstream version 2.44.0 is available

2022-06-15 Thread Martin-Éric Racine

Package: graphviz
Version: 2.42.2-5
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

A new upstream version 2.44.0 is available, you should consider packaging it.

- -- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages graphviz depends on:
ii  libann01.1.2+doc-7
ii  libc6  2.31-13+deb11u3
ii  libcdt52.42.2-5
ii  libcgraph6 2.42.2-5
ii  libexpat1  2.2.10-2+deb11u3
ii  libgcc-s1  10.2.1-6
ii  libgd3 2.3.0-2
ii  libglib2.0-0   2.66.8-1
ii  libgts-0.7-5   0.7.6+darcs121130-4+b1
ii  libgvc62.42.2-5
ii  libgvpr2   2.42.2-5
ii  liblab-gamut1  2.42.2-5
ii  libstdc++6 10.2.1-6
ii  libx11-6   2:1.7.2-1
ii  libxaw72:1.0.13-1.1
ii  libxmu62:1.1.2-2+b3
ii  libxt6 1:1.2.0-1

Versions of packages graphviz recommends:
pn  fonts-liberation  

Versions of packages graphviz suggests:
pn  graphviz-doc  
ii  gsfonts   1:8.11+urwcyr1.0.7~pre44-4.5

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmKqLKIACgkQrh+Cd8S0
17Z0fA//XMpYiZBvlcSm9KpO2W9TSpQ/DEcGdWX/A8ktrkejKX6YlP8Oy7OgMu+z
2ohHjnrEOoyqosfVgPeFF7Eb9x0+qtRx4FrPd4ET8d8jOVPdbgQbX+Vp8V+Wwon3
5FLiTimJy0uOqffP9L8r5PJyuiKogwaDNMasq9jXInavi0El/s8Q2teAuTNyDxMF
aVA5oe8Uf7levIkgKOkO2A2+oEAr//plKcqKYwVJCCtj/ihdxxF6QswzlZTZfwDG
9IQcYbeIyckzI6u9R9AD32ADZdppdJPPzk3ReQb90At5l5qEZOhVOPkMAu8vD+aZ
1m1QdhMcxMMK8TT6bv1Fw1xRwBsKZlwxOfUJZp6gwcZu6saH4Dd/6YwwaL5X4Jjl
zxpfHUVooID2ps0By7WfTs/ycgwjc+oeOs+caKkO6qIGQNmx3l+vut65sHFVJ1Kn
V+PBJdIn0QKsNep8HAMmGG68BSkY6F7oySrN33S4+16Ww1kZRBQ+B0dGT+l+N7Op
9gLDIpAzFkIq3RVBqd9de0MG8ZAdVDfnoEDW/RgJVFFR4KQvxH5Ma8VC+ZUJOVEQ
bSVuYPktFY3JRtz71gOIiy5K++bDHwXI5cIsuSRsLaGdOjjsZdtdscKqy/hFq3op
8z6pF7sy9RztzgpOh+4xoQdk3HoFNyCL20LIVRtNE5PtbCk7Ugg=
=yzkX
-END PGP SIGNATURE-

Bug#1012863: libsdl2: Add --disable-video-rpi to configure

2022-06-15 Thread Christer Solskogen

Package: libsdl2-dev
Version: 2.0.22+dfsg-3
Severity: normal
File: libsdl2
Tags: newcomer

Dear Maintainer,
Please add --disable-video-rpi to ./configure in order to disable the usage of 
the old and unmaintained Raspberry Pi driver. KMS is now the prefered driver 
for the Pi, and while this option might seem correct, it uses the old kernel 
driver which conflicts with KMS/DRM.
I've compiled libsdl2 using the sources from bookwork, and compiles cleanly and 
the resulting library works as far as my testing goes.
The lastest Raspberry Pi OS use bullseye, and the old Raspberry Pi SDL driver 
is incompatible with it. 

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.15.32-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 libsdl2-dev depends on:
ii  libasound2-dev1.2.4-1.1+rpt2
ii  libdbus-1-dev 1.12.20-2
ii  libegl1-mesa-dev  20.3.5-1+rpt4+rpi1
ii  libgl-dev 1.3.2-1
ii  libgles-dev   1.3.2-1
ii  libglu1-mesa-dev  9.0.1-1
ii  libibus-1.0-dev   1.5.23-2
ii  libpulse-dev  14.2-2+rpi1
ii  libsdl2-2.0-0 2.0.22+dfsg-3
ii  libsndio-dev  1.5.0-3
ii  libudev-dev   247.3-7
ii  libwayland-dev1.18.0-2~exp1.1
ii  libx11-dev2:1.7.2-1
ii  libxcursor-dev1:1.2.0-2
ii  libxext-dev   2:1.3.3-1.1
ii  libxi-dev 2:1.7.10-1
ii  libxinerama-dev   2:1.1.4-2
ii  libxkbcommon-dev  1.0.3-2
ii  libxrandr-dev 2:1.5.1-1
ii  libxss-dev1:1.2.3-1
ii  libxt-dev 1:1.2.0-1
ii  libxv-dev 2:1.0.11-1
ii  libxxf86vm-dev1:1.1.4-1+b2

libsdl2-dev recommends no packages.

libsdl2-dev suggests no packages.

-- no debconf information

Bug#1012862: lmms: FTBFS: Cannot find (any matches for) "usr/lib//lmms/RemoteVstPlugin

2022-06-15 Thread Sebastian Ramacher

Source: lmms
Version: 1.2.2+dfsg1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=lmms=i386=1.2.2%2Bdfsg1-3=1655316479=0

Installing bash completion...

Bash completion for lmms has been installed to 
/<>/debian/tmp/usr/share/bash-completion/completions/lmms
make[1]: Leaving directory '/<>/obj-i686-linux-gnu'
   dh_install -a
dh_install: warning: Cannot find (any matches for) 
"usr/lib/*/lmms/RemoteVstPlugin*" (tried in ., debian/tmp)

dh_install: warning: lmms-vst-server missing files: 
usr/lib/*/lmms/RemoteVstPlugin*
dh_install: error: missing files, aborting
make: *** [debian/rules:42: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


Cheers
-- 
Sebastian Ramacher

Bug#1012861: FileNotFoundError: [Errno 2] No such file or directory: 'screen'

2022-06-15 Thread Diederik de Haas

Package: ranger
Version: 1.9.3-3
Severity: normal
Tags: upstream fixed-upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I installed ranger and after that tried to run it, from within a tmux
session (and 'screen' is not installed), resulting in this fatal error:

# ranger
ranger version: ranger 1.9.3
Python version: 3.10.5 (main, Jun  8 2022, 09:26:22) [GCC 11.3.0]
Locale: en_US.UTF-8

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/ranger/core/main.py", line 171, in main
fm.initialize()
  File "/usr/lib/python3/dist-packages/ranger/core/fm.py", line 132, in 
initialize
self.ui.initialize()
  File "/usr/lib/python3/dist-packages/ranger/gui/ui.py", line 127, in 
initialize
self.handle_multiplexer()
  File "/usr/lib/python3/dist-packages/ranger/gui/ui.py", line 499, in 
handle_multiplexer
self._screen_title = check_output(
  File "/usr/lib/python3/dist-packages/ranger/ext/spawn.py", line 35, in 
check_output
process = Popen(popenargs, stderr=fd_devnull, **kwargs)
  File "/usr/lib/python3.10/subprocess.py", line 969, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.10/subprocess.py", line 1845, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'screen'

ranger crashed. Please report this traceback at:
https://github.com/ranger/ranger/issues

At https://github.com/ranger/ranger/issues/2580 it was already reported
upstream and that also pointed to a commit fixing it:
https://github.com/ranger/ranger/commit/1cdcce0a44d031be13009a70e25cc4cf75789eac

But that commit is not (yet) part of any released version.

On my normal PC, which does have 'screen' installed, I couldn't
reproduce this issue, ranger started fine within a tmux session.

I'll leave a decision to cherry-pick/backport that commit up to the
maintainer, but the last upstream release was from 2019-12-31 ...

- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.18.0-1-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 ranger depends on:
ii  python3 3.10.4-1+b1
ii  sensible-utils  0.0.17

Versions of packages ranger recommends:
ii  file 1:5.41-4
ii  less 590-1
ii  python3-chardet  4.0.0-2
ii  w3m-img  0.5.3+git20220429-1+b1

Versions of packages ranger suggests:
pn  atool 
pn  caca-utils
pn  highlight | python3-pygments  
pn  mediainfo | exiftool  
pn  poppler-utils | mupdf-tools   
pn  sudo  
pn  unoconv   
ii  w3m   0.5.3+git20220429-1+b1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCYqokuAAKCRDXblvOeH7b
blngAP9bGUhgJlhh1y2USXu8nctiygXETqDliUyzUIv3lxzTZQD/Rm/TThkmX13U
ayAp+4CZnqaR/2tzvauzycveLcKH3Q0=
=OxTy
-END PGP SIGNATURE-

Bug#1012860: eom: Should recommend libgdk-pixbuf2.0-bin

2022-06-15 Thread Luís Picciochi Oliveira

Package: eom
Version: 1.24.1-1
Severity: normal
Tags: patch
X-Debbugs-Cc: pitxy...@gmail.com

Hi,

When using eom, the thumbnails at the bottom (activated through 'View' ->
'Image Collection (Ctrl+F9)') were not being generated.

For these to work I had to dig around and ultimately found that installing the
libgdk-pixbuf2.0-bin package fixes this.
I could not find any reference to this package in the dependencies of eom, so I
suggest it to be added at least as a recommendation.

I tried to provide this patch through a merge request or some more expedite way
in Salsa but I couldn't find out how. Did I miss something?

Feel free to integrate it:
https://salsa.debian.org/Pitxyoki/eom/-/commit/dd4125d76e8dff4e9696abdee4689ca97543b03d

Thanks,
Luís Picciochi Oliveira

-- System Information:
Debian Release: 11.3
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-15-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 eom depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-2
ii  eom-common   1.24.1-1
ii  gir1.2-eom-1.0   1.24.1-1
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-13+deb11u3
ii  libcairo21.16.0-5
ii  libexempi8   2.5.2-1
ii  libexif120.6.22-3
ii  libgdk-pixbuf2.0-0   2.40.2-2
ii  libgirepository-1.0-11.66.1-1+b1
ii  libgl1   1.3.2-1
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-4+deb11u2
ii  libjpeg62-turbo  1:2.0.6-4
ii  liblcms2-2   2.12~rc1-2
ii  libmate-desktop-2-17 1.24.1-2
ii  libpeas-1.0-01.28.0-2+b1
ii  librsvg2-2   2.50.3+dfsg-1
ii  librsvg2-common  2.50.3+dfsg-1
ii  libx11-6 2:1.7.2-1
ii  libxml2  2.9.10+dfsg-6.7+deb11u2
ii  mate-desktop-common  1.24.1-2
ii  shared-mime-info 2.0-1
ii  zlib1g   1:1.2.11.dfsg-2+deb11u1

eom recommends no packages.

eom suggests no packages.

Bug#1012655: upstream bug and fix

2022-06-15 Thread Diederik de Haas

On Wednesday, 15 June 2022 17:40:45 CEST Stephan Verbücheln wrote:
> Kernel 5.18.4 got the patch.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/driver
> s/input/mouse/bcm5974.c?id=v5.18.4=v5.18.3

Excellent, thanks for mentioning that :-)

> I will just use 5.17 or external mouse until the fix lands in Sid.

My guess is that the next upload to Sid should have it then.

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

Bug#998848: thunderbird: please build against librnp-dev (and Depend: on librnp0) directly

2022-06-15 Thread Daniel Kahn Gillmor

On Wed 2022-06-15 18:04:09 +0200, Carsten Schoenert wrote:
> 2) What is needed to modify in the upstream configure script voodoo so
> its possible to use the configure options
>
>   --with-system-botan
>   --with-system-bz2
>   --with-system-jsonc

Is it possible that these three flags aren't relevant any longer
*because* we're using the system rnp?

in comm/third_party/openpgp.configure i see the tests for those options
bracketed within a block that begins:

-
with only_when(in_tree_librnp):
-

And i don't see those options anywhere else in the codebase.

It would make sense if those options shouldn't be supplied at all any
longer when we're using the system rnp, and i'd expect that the updated
thunderbird wouldn't acquire any new dependencies from omitting those
changes.

I'd guess that you can probably also remove the build-deps on:

libbotan-2-dev
libbz2-dev
libjson-c-dev

And the build should complete without an error, but i haven't tested it
myself.

Thank you very much for working on this, Carsten!

--dkg

signature.asc
Description: PGP signature

Bug#1012227: webkitgtk: CPU usage

2022-06-15 Thread tmcconnell168

Sorry I thought I had replied to this and I didn't. All I'm doing when
this happens is checking my local email (log file reports etc) in
Evolution. It doesn't do it when I check gmail though. and strangely
enough, it only does it if the PC sits over night, with Evolution open.
So like if I check email first thing in the morning, the rest of the
day it's fine. 
Tim  

On Fri, 2022-06-10 at 21:51 +, Alberto Garcia wrote:
> On Fri, Jun 10, 2022 at 02:25:28PM -0500,
> tmcconnell...@gmail.com wrote:
> > I had a better idea, and piped it to the attached file and let it
> > run
> > until the CPU usage went down. Currently my CPU is between 9 - 15 %
> > Sorry for the big file, it took a while. 
> > Tim
> 
> Ok, it looks like it's just drawing text all the time, do you have
> any
> particular website or page open, or when does this happen?
> 
> Berto

Bug#984102: NMU: libfm-qt: ftbfs with GCC-11


I am sponsoring a NMU that was provided to fix this.
debdiff is attached.diff -Nru libfm-qt-0.16.0/debian/changelog libfm-qt-0.16.0/debian/changelog
--- libfm-qt-0.16.0/debian/changelog2021-01-08 20:15:46.0 +0100
+++ libfm-qt-0.16.0/debian/changelog2022-06-15 09:59:06.0 +0200
@@ -1,3 +1,10 @@
+libfm-qt (0.16.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with Qt >=5.15.3 and gcc-11. (Closes: #984102)
+
+ -- Mateusz Łukasik   Wed, 15 Jun 2022 09:59:06 +0200
+
 libfm-qt (0.16.0-3) unstable; urgency=high
 
   * Update symbols for armel, armhf, i386, mipsel and s390x to fit FTBFS.
diff -Nru libfm-qt-0.16.0/debian/libfm-qt8.symbols 
libfm-qt-0.16.0/debian/libfm-qt8.symbols
--- libfm-qt-0.16.0/debian/libfm-qt8.symbols2021-01-08 12:56:41.0 
+0100
+++ libfm-qt-0.16.0/debian/libfm-qt8.symbols2022-06-15 09:56:41.0 
+0200
@@ -1293,7 +1293,6 @@
  _ZNK2Fm9DeleteJob10metaObjectEv@Base 0.16.0
  _ZNK2Fm9Templates10metaObjectEv@Base 0.16.0
  
_ZNKSt10_HashtableIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_St10shared_ptrIKN2Fm8FileInfoEEESaISD_ENSt8__detail10_Select1stESt8equal_toIS6_ESt4hashIS5_ENSF_18_Mod_range_hashingENSF_20_Default_ranged_hashENSF_20_Prime_rehash_policyENSF_17_Hashtable_traitsILb1ELb0ELb119_M_find_before_nodeEmRS6_m@Base
 0.16.0
- 
_ZNSt10_HashtableIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_St10shared_ptrIKN2Fm8FileInfoEEESaISD_ENSt8__detail10_Select1stESt8equal_toIS6_ESt4hashIS5_ENSF_18_Mod_range_hashingENSF_20_Default_ranged_hashENSF_20_Prime_rehash_policyENSF_17_Hashtable_traitsILb1ELb0ELb14findERS6_@Base
 0.16.0
  
_ZNSt10_HashtableIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_St10shared_ptrIKN2Fm8FileInfoEEESaISD_ENSt8__detail10_Select1stESt8equal_toIS6_ESt4hashIS5_ENSF_18_Mod_range_hashingENSF_20_Default_ranged_hashENSF_20_Prime_rehash_policyENSF_17_Hashtable_traitsILb1ELb0ELb15clearEv@Base
 0.16.0
  
_ZNSt10_HashtableINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N2Fm12FileInfoListEESaISA_ENSt8__detail10_Select1stESt8equal_toIS5_ESt4hashIS5_ENSC_18_Mod_range_hashingENSC_20_Default_ranged_hashENSC_20_Prime_rehash_policyENSC_17_Hashtable_traitsILb1ELb0ELb15clearEv@Base
 0.16.0
  
_ZNSt14_Fwd_list_baseISt10shared_ptrIKN2Fm8IconInfoEESaIS4_EE14_M_erase_afterEPSt19_Fwd_list_node_baseS8_@Base
 0.16.0
@@ -1308,7 +1307,6 @@
  
_ZNSt6vectorIN2Fm8FilePathESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.16.0
  
_ZNSt6vectorIN2Fm8FilePathESaIS1_EE17_M_realloc_insertIJRS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.16.0
  
_ZNSt6vectorIN2Fm8FilePathESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.16.0
- 
_ZNSt6vectorIN2Fm8FilePathESaIS1_EE6insertEN9__gnu_cxx17__normal_iteratorIPKS1_S3_EERS6_@Base
 0.16.0
  
_ZNSt6vectorIN2Fm8FilePathESaIS1_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS1_S3_EES7_@Base
 0.16.0
  
_ZNSt6vectorIPN2Fm12ThumbnailJobESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.16.0
  
_ZNSt6vectorIPN2Fm16DirTreeModelItemESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 0.16.0
@@ -1319,12 +1317,12 @@
  
_ZNSt6vectorISt10shared_ptrIKN2Fm8FileInfoEESaIS4_EE12emplace_backIJRKS4_EEEvDpOT_@Base
 0.16.0
  
_ZNSt6vectorISt10shared_ptrIKN2Fm8FileInfoEESaIS4_EE17_M_realloc_insertIJRKS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base
 0.16.0
  
_ZNSt6vectorISt10shared_ptrIKN2Fm8FileInfoEESaIS4_EE17_M_realloc_insertIJS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base
 0.16.0
- 
_ZNSt6vectorISt10shared_ptrIKN2Fm8MimeTypeEESaIS4_EE12emplace_backIJRKS4_EEEvDpOT_@Base
 0.16.0
  
_ZNSt6vectorISt10shared_ptrIKN2Fm8MimeTypeEESaIS4_EE17_M_realloc_insertIJRKS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base
 0.16.0
  
_ZNSt6vectorISt10shared_ptrIN2Fm11ThumbnailerEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
 0.16.0
  
_ZNSt6vectorISt10shared_ptrIN2Fm12TemplateItemEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
 0.16.0
  
_ZNSt6vectorISt10shared_ptrIN2Fm12TemplateItemEESaIS3_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS3_S5_EES9_@Base
 0.16.0
  
_ZNSt6vectorISt10shared_ptrIN2Fm6FolderEESaIS3_EE17_M_realloc_insertIJS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
 0.16.0
+ 
_ZNSt6vectorISt10unique_ptrIN2Fm8ArchiverESt14default_deleteIS2_EESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 0.16.0
  
_ZNSt6vectorISt4pairISt10shared_ptrIKN2Fm8FileInfoEES5_ESaIS6_EE12emplace_backIJS6_EEEvDpOT_@Base
 0.16.0
  
_ZNSt6vectorISt4pairISt10shared_ptrIKN2Fm8FileInfoEES5_ESaIS6_EE17_M_realloc_insertIJS6_EEEvN9__gnu_cxx17__normal_iteratorIPS6_S8_EEDpOT_@Base
 0.16.0

Bug#1012859: installation-reports: Ethernet firmware module failure - no LAN / internet access during or after install

2022-06-15 Thread Leslie Rhorer

Package: installation-reports
Severity: grave
Tags: d-i a11y
Justification: renders package unusable
X-Debbugs-Cc: lesrho...@siliconventures.net

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: 
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-dvd/firmware-11.3.0-amd64-DVD-1.iso
Date: 5/28/2022

Machine: Asus AMD system with an 8 core FX-8350 CPU and Asus PEB-10G/57811-1S 
10GbE SFP+ Network Adapter
Partitions: N/A


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[0]
Configure network:  [E]
Detect media:   [0]
Load installer modules: [E]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

   Two of my servers are having bizarre problems after upgrading to Debian 
Bullseye.  After attempting numerous fixes, I decided to wipe the systems and 
do a fresh install.  I did a fresh install of the first from a netinst thumb 
drive, but the .iso does not contain the bnx2c drivers needed for the ASUS 
PEB-10G/57811-1S 10GbE SFP+ Network Adapters used by both systems.  I tried 
adding what I thought to be the correct non-free drivers, but I still got 
errors about the bnx2x drivers and the interface shows no carrier.  Since no 
carrier is detected on the interface, no LAN or internet access is possible.  
The system was effectively dead, although it boots up and of course I have 
local console access.

   After several different approaches, I changed from the netinst image to 
a full non-free image.  It still would not properly load the bnx2x drivers.  I 
tried downloading all six bnx2x e1, e1h, and e2 release 7.13.15.0 and 7.13.21.0 
firmware files and adding them to the initram image.  It no longer complains 
about missing files, but it doesn't activate the NIC, either.  I tried 
compiling the driver from source, but I get a cc1 error saying the code model 
kernel does not support PIC mode.  I have tried numerous modifications to the 
make file, but I have not been able to eliminate the error.

   The only thing I spot from dmesg that seems possibly related is:

[1.420748] r8169 :0b:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[1.433467] r8169 :0b:00.0 eth0: RTL8168f/8111f, 50:46:5d:65:15:9c, XID 
480, IRQ 39
[1.433469] r8169 :0b:00.0 eth0: jumbo features [frames: 9194 bytes, tx 
checksumming: ko]
...
[1.458361] r8169 :0b:00.0 enp11s0: renamed from eth0
[1.465675] bnx2x: disagrees about version of symbol module_layout
...
[   12.976323] r8169 :0b:00.0: firmware: failed to load 
rtl_nic/rtl8168f-1.fw (-2)
[   12.976478] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   12.976632] r8169 :0b:00.0: Direct firmware load for 
rtl_nic/rtl8168f-1.fw failed with error -2
[   12.976636] r8169 :0b:00.0: Unable to load firmware 
rtl_nic/rtl8168f-1.fw (-2)
[   12.977326] RTL8211E Gigabit Ethernet r8169-0-b00:00: attached PHY driver 
[RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=r8169-0-b00:00, irq=IGNORE)
[   13.046445] r8169 :0b:00.0 enp11s0: Link is Down




Please make sure that any installation logs that you think would
be useful are attached to this report. Please compress large
files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20210731+deb11u3"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux Backup 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] 
RD9x0/RX980 Host Bridge [1002:5a14] (rev 02)
lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD9x0/RX980 
Host Bridge [1002:5a14]
lspci -knn: 00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] 
RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GFX port 0) [1002:5a16]
lspci -knn: DeviceName:  Onboard IGD
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] 
RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 0) [1002:5a18]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] 
RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 1) [1002:5a19]
lspci

Bug#1012858: grub-common: changed from Radeon to amdgpu

2022-06-15 Thread Tim McConnell

Package: grub-common
Version: 2.06-3
Severity: normal
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

What led up to the situation? (sorry for the lengthy explanation) Added this
line GRUB_CMDLINE_LINUX_DEFAULT="quiet radeon.cik_support=0
amdgpu.cik_support=1" to /etc/default/grub as per this link provided by Steam/
Proton (apparently I have a "Sea Islands" card)
https://github.com/ValveSoftware/Proton/wiki/For-AMD-users-having-issues-with-
non-OpenGL-games that states: [Quote] Vulkan requires the amdgpu driver, it
doesn't detect the graphics adapter when using radeon.

If you're experiencing crashes or the game doesn't load at all, it's probably
because your distribution defaults to the radeon driver and Vulkan may be using
Intel's graphics adapter instead (if available).

If that's the case, amdgpu has to be enabled explicitly in the kernel
commandline.

Instructions for Debian/Ubuntu

Open your terminal and run sudo nano /etc/default/grub.

Append to GRUB_CMDLINE_LINUX_DEFAULT:

radeon.si_support=0 amdgpu.si_support=1 if you have a Southern Islands
card.
radeon.cik_support=0 amdgpu.cik_support=1 if you have a Sea Islands card.

For example: GRUB_CMDLINE_LINUX_DEFAULT="quiet radeon.cik_support=0
amdgpu.cik_support=1"

Note: You can safely append both variants if you are unsure which family your
card belongs to.

Save with CTRL+X followed by Y and then Enter.

Run sudo update-grub and then reboot your system.

You can check which driver is loaded by running lspci -k:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Hawaii PRO [Radeon R9 290/390]
Subsystem: PC Partner Limited / Sapphire Technology Hawaii PRO [Radeon
R9 290/390]
Kernel driver in use: amdgpu
Kernel modules: radeon, amdgpu

If your desktop environment doesn't load, check the kernel log by running sudo
dmesg. If you see that amdgpu is crashing, append amdgpu.dc=0 to the kernel
commandline.[ENDQUOTE]

and I double checked their information with this link
https://wiki.debian.org/AtiHowTo#Drivers. And my sound quit working.

What exactly did you do (or not do) that was effective (or ineffective)? made
the changes as per the instructions listed above and rebooted.

What was the outcome of this action? My sound quit working altogether.

What outcome did you expect instead?
Not to lose sound (music, system sounds etc) from what was supposed to be just
a change to use a different GPU driver. Is there something else I should have
added to Grub to ensure the sound didn't quit working or something I can add to
force it to make it recognize my sound device like it did before? If this
should go to someone else please send this to them, this is more of a question
than an actual bug report.




-- Package-specific info:

*** BEGIN /proc/mounts
/dev/sda4 / ext4 rw,relatime,errors=remount-ro 0 0
/dev/sda3 /tmp ext4 rw,relatime 0 0
/dev/sda7 /boot/efi vfat 
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
/dev/sda5 /var ext4 rw,relatime 0 0
/dev/loop1 /snap/bare/5 squashfs ro,nodev,relatime,errors=continue 0 0
/dev/loop4 /snap/core18/2409 squashfs ro,nodev,relatime,errors=continue 0 0
/dev/loop0 /snap/gtk-common-themes/1519 squashfs 
ro,nodev,relatime,errors=continue 0 0
/dev/loop3 /snap/gimp/383 squashfs ro,nodev,relatime,errors=continue 0 0
/dev/loop5 /snap/gtk-common-themes/1534 squashfs 
ro,nodev,relatime,errors=continue 0 0
/dev/loop2 /snap/gnome-3-28-1804/161 squashfs ro,nodev,relatime,errors=continue 
0 0
/dev/loop6 /snap/snapd/15904 squashfs ro,nodev,relatime,errors=continue 0 0
/dev/loop7 /snap/snapd/16010 squashfs ro,nodev,relatime,errors=continue 0 0
/dev/loop8 /snap/warzone2100/5456 squashfs ro,nodev,relatime,errors=continue 0 0
/dev/sda6 /home ext4 rw,relatime 0 0
/dev/loop9 /snap/warzone2100-videos/2 squashfs 
ro,nodev,relatime,errors=continue 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod

Bug#869169: packaged and uploaded

2022-06-15 Thread Hans-Christoph Steiner


https://salsa.debian.org/debian/minisign

Bug#1012826: broadcom-sta-dkms: Installation fails after upgrade to kernel 5.18-01-amd64

2022-06-15 Thread Manel Vallès

Ok! thanks for your job! copied from arch user blog, sorry.

On Wed, 15 Jun 2022 18:02:15 +0200 Eduard Bloch  wrote:
> Version: 6.30.223.271-20
> 
> Hallo,
> * manel [Wed, Jun 15 2022, 12:50:44AM]:
> > Package: broadcom-sta-dkms
> > Version: 6.30.223.271-19
> > Followup-For: Bug #1012826
> > X-Debbugs-Cc: manel@mbp13.xarxa
> >
> > Dear Maintainer,
> >
> > *** Reporter, please consider answering these questions, where
> > appropriate ***
> >
> >    * What led up to the situation?
> >    * What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> >    * What was the outcome of this action?
> >    * What outcome did you expect instead?
> >
> > *** End of the template - remove these template lines ***
> >
> > Patch solve issue:
> 
> As far as I can see, this is the same patch we already have in Debian
> Unstable. Closing this report, feel free to reopen if you disagree.
> 
>
https://salsa.debian.org/broadcom-sta-team/broadcom-sta/-/commit/cdee7bf4db17b7f6d62e0779b1fddd87e176a5df
> https://salsa.debian.org/broadcom-sta-team/broadcom-sta/-/branches
> 
> Best regards,
> Eduard.
> 
>

Bug#1012857: libpopplerkit0: Please update for Poppler 22.06

Package: libpopplerkit0
Severity: normal
Tags: patch
X-Debbugs-Cc: nathan.teodo...@canonical.com

Dear Maintainer,

Since Poppler 22.06 made its way into experimental, Libpopplerkit0 will need
the compatibility changes present in the attached debdiff.


-- System Information:
Debian Release: bookworm/sid
  APT prefers kinetic
  APT policy: (500, 'kinetic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-33-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.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 libpopplerkit0 depends on:
pn  gnustep-back0.29  
ii  gnustep-base-runtime  1.28.0-4build2
ii  gnustep-gui-runtime   0.29.0-2build2
ii  gsfonts   1:8.11+urwcyr1.0.7~pre44-4.5
ii  libc6 2.35-0ubuntu3
ii  libfontconfig12.13.1-4.4ubuntu1
ii  libgcc-s1 12.1.0-2ubuntu1
ii  libgnustep-base1.28   1.28.0-4build2
ii  libgnustep-gui0.290.29.0-2build2
ii  libobjc4  12.1.0-2ubuntu1
pn  libpoppler118 
ii  libstdc++612.1.0-2ubuntu1

libpopplerkit0 recommends no packages.

libpopplerkit0 suggests no packages.
diff -Nru popplerkit.framework-0.0.20051227svn/debian/changelog 
popplerkit.framework-0.0.20051227svn/debian/changelog
--- popplerkit.framework-0.0.20051227svn/debian/changelog   2022-02-08 
11:46:16.0 -0300
+++ popplerkit.framework-0.0.20051227svn/debian/changelog   2022-06-15 
12:33:01.0 -0300
@@ -1,3 +1,12 @@
+popplerkit.framework (0.0.20051227svn-8.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Nathan Pratta Teodosio ]
+  * Fix bild with poppler 22.06.
+
+ -- Nathan Pratta Teodosio   Wed, 15 Jun 2022 
12:33:01 -0300
+
 popplerkit.framework (0.0.20051227svn-8.2) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru popplerkit.framework-0.0.20051227svn/debian/patches/poppler2206.patch 
popplerkit.framework-0.0.20051227svn/debian/patches/poppler2206.patch
--- popplerkit.framework-0.0.20051227svn/debian/patches/poppler2206.patch   
1969-12-31 21:00:00.0 -0300
+++ popplerkit.framework-0.0.20051227svn/debian/patches/poppler2206.patch   
2022-06-15 12:32:04.0 -0300
@@ -0,0 +1,15 @@
+Description: Fix build for Poppler 22.06
+Author: Nathan Pratta Teodosio 
+
+--- a/bindings/poppler_document.cc 2022-06-15 12:25:10.501074922 -0300
 b/bindings/poppler_document.cc 2022-06-15 12:25:15.113136267 -0300
+@@ -31,8 +31,7 @@
+   return NULL;
+}
+
+-   GooString* path_g = new GooString(path);
+-   PDFDoc* doc = new PDFDoc(path_g, NULL, NULL);
++   PDFDoc* doc = new PDFDoc(std::make_unique(path));
+return doc;
+ }
+ 
diff -Nru popplerkit.framework-0.0.20051227svn/debian/patches/series 
popplerkit.framework-0.0.20051227svn/debian/patches/series
--- popplerkit.framework-0.0.20051227svn/debian/patches/series  2022-02-08 
11:46:16.0 -0300
+++ popplerkit.framework-0.0.20051227svn/debian/patches/series  2022-06-15 
12:31:16.0 -0300
@@ -5,3 +5,4 @@
 build_poppler71.patch
 build_poppler85.patch
 build_poppler107.patch
+poppler2206.patch

Bug#1012856: sbuild: fails on .dsc symlinks pointing to files not ending in .dsc

2022-06-15 Thread Benjamin Drung

Package: sbuild
Version: 0.83.1
Severity: normal
Tags: patch
X-Debbugs-Cc: bdr...@ubuntu.com

Dear Maintainer,

Commit d15d5ea67b81cde811207ff6853b381c3ebe4b41 breaks the Ubuntu
lp-buildd builds. This problem can be reproduced by running:

```
pull-debian-source -d distro-info 1.1
mv distro-info_1.1.dsc distro-info_1.1_with_diffent_ending.txt
ln -s distro-info_1.1_with_diffent_ending.txt distro-info_1.1.dsc
sbuild -d unstable distro-info_1.1.dsc
```

abs_path() expands jobname from 'distro-info_1.1.dsc' to
'/full/path/to/distro-info_1.1_with_diffent_ending.txt'. Then it tries
to fetch that source file (instead of using it as dsc file).

-- 
Benjamin Drung
Debian & Ubuntu Developer

Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?

Hey Thomas!

On Wed, Jun 15, 2022 at 01:17:31PM +0200, Thomas Schmitt wrote:
>Hi,
>
>although it was not the final solution of this bug report, i beefed up
>my merger script for Debian ISOs so that it can combine an arbitrary
>number of ISOs (within the limits of /dev/loop* and mount(8)).
>Maybe it can serve as answer for the next time this wish comes up.
>
>The script is uploaded as
>
>  
> https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos
>
>with GPG detached signature
>  
> https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos.sig
>for checking by gpg --verify.

Cool. :-)

That might be a useful thing to include in a package. What do you think?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Armed with "Valor": "Centurion" represents quality of Discipline,
  Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
  concord the digital world while feeling safe and proud.

Bug#1012855: RFS: smplayer/22.2.0~ds0-1 -- Complete front-end for MPlayer and mpv


Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "smplayer":

 * Package name: smplayer
   Version : 22.2.0~ds0-1
   Upstream Author : Ricardo Villalba
 * URL :http://smplayer.sourceforge.net/
 * License : LGPL-2.1+, BSD-2-clause, CC0-1.0, LGPL-2+, Expat, GPL-2+, 
BSD-3-clause
 * Vcs :https://salsa.debian.org/multimedia-team/smplayer
   Section : video

The source builds the following binary packages:

  smplayer - Complete front-end for MPlayer and mpv
  smplayer-l10n - Complete front-end for MPlayer and mpv - translation files

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/smplayer/

Alternatively, you can download the package with 'dget' using this command:

  dget 
-xhttps://mentors.debian.net/debian/pool/main/s/smplayer/smplayer_22.2.0~ds0-1.dsc

Changes since the last upload:

 smplayer (22.2.0~ds0-1) unstable; urgency=medium
 .
   * New upstream release.

Regards,
--
  Mateusz Łukasik

Bug#1012854: RFS: libfm-qt/0.16.0-3.1 [NMU] [RC] -- Language package for libfm-qt


Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "libfm-qt":

 * Package name: libfm-qt
   Version : 0.16.0-3.1
   Upstream Author : [fill in name and email of upstream]
 * URL :https://github.com/lxqt/libfm-qt
 * License : BSD-3-Clause, LGPL-2.1+
 * Vcs :https://salsa.debian.org/lxqt-team/libfm-qt
   Section : x11

The source builds the following binary packages:

  libfm-qt8 - file management support for pcmanfm-qt
  libfm-qt-dev - file management support library for pcmanfm-qt (development 
files)
  libfm-qt-l10n - Language package for libfm-qt

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/libfm-qt/

Alternatively, you can download the package with 'dget' using this command:

  dget 
-xhttps://mentors.debian.net/debian/pool/main/libf/libfm-qt/libfm-qt_0.16.0-3.1.dsc

Changes since the last upload:

 libfm-qt (0.16.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with Qt >=5.15.3 and gcc-11. (Closes: #984102)

Regards,
--
  Mateusz Łukasik

Bug#1012849: efitools: ftbfs on riscv64

On Wed, Jun 15, 2022 at 11:57:15PM +0800, xiao sheng wen wrote:
>Hi,
>
>在 2022/6/15 23:21, Steve McIntyre 写道:
>> Control: severity -1 wishlist
>> 
>> On Wed, Jun 15, 2022 at 11:02:50PM +0800, xiao sheng wen wrote:
>> > Control: Severity -1  important
>> Please don't raise severity on packages asking for support for a
>> non-release architecture.
>
>FTBFS bug is a RC bug in release architecture,
>as riscv is a non-release architecture, so downgrade these FTBFS bugs to 
>Severity: important,

There's a difference between "FTBFS on this ports architecture" (but
previously built OK) and "has never built on this ports architecture".

I'm not saying I'm going to look at the bug report and patch here, but
please don't inflate severity.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"You can't barbecue lettuce!" -- Ellie Crane

Bug#998848: thunderbird: please build against librnp-dev (and Depend: on librnp0) directly

2022-06-15 Thread Carsten Schoenert

Hi Daniel,

Am 15.06.22 um 17:12 schrieb Daniel Kahn Gillmor:

after again months of waiting for some typical build tools and a lot of
try and errors attempts I'm now able to build the current beta version
of Thunderbird (102.0~b4) together with the system package of
librnp-dev.

that's great news! thanks for doing this.

uploaded to experimental just right now.

The downside is that this requires currently the usage of the internal
version of botan, bz2 and jsonc.

I've no kowledge if upstream has plans to reenable the usage of system
packages for these tools, maybe it's also just a misconfiguration of the
buildsystem.

Ugh, that doesn't sound so reasonable. I'd expect those libraries to be
internal to librnp, and not directly exposed to the rest of thunderbird.
so they shouldn't be related to the build process at all, afaict.

Preparing the current version did make a lot of headaches. :-)
So far I've experienced we need to use the option --enable-av1 now to
get a recent Thunderbird, otherwise the build failed with an error
messages that make not really sense to me.

0:12.47 js/src> updating cache ./config.cache
0:12.47 js/src> creating ./config.data
0:12.48 Creating config.status
0:12.67 Reticulating splines...
0:12.97 0:00.33 File already read. Skipping:
/build/thunderbird-98.0~b2/intl/components/moz.build
0:13.18 0:00.53 File already read. Skipping:
/build/thunderbird-98.0~b2/gfx/angle/targets/angle_common/moz.build
0:15.20 Traceback (most recent call last):
0:15.20 File "/build/thunderbird-98.0~b2/configure.py", line 349, in
0:15.20 sys.exit(main(sys.argv))
0:15.20 File "/build/thunderbird-98.0~b2/configure.py", line 161, in main
0:15.20 return config_status(config)
0:15.20 File "/build/thunderbird-98.0~b2/configure.py", line 300, in
config_status
0:15.20 return config_status(args=[], **sanitized_config)
0:15.20 File
"/build/thunderbird-98.0~b2/python/mozbuild/mozbuild/config_status.py", line
162, in config_status
0:15.20 definitions = list(definitions)
0:15.20 File
"/build/thunderbird-98.0~b2/python/mozbuild/mozbuild/frontend/emitter.py", line
179, in emit
0:15.20 objs = list(self._emit_libs_derived(contexts))
0:15.20 File
"/build/thunderbird-98.0~b2/python/mozbuild/mozbuild/frontend/emitter.py", line
261, in _emit_libs_derived
0:15.20 self._link_libraries(context, obj, variable, idl_sources)
0:15.20 File
"/build/thunderbird-98.0~b2/python/mozbuild/mozbuild/frontend/emitter.py", line
378, in _link_libraries
0:15.20 self._link_library(context, obj, variable, path)
0:15.20 File
"/build/thunderbird-98.0~b2/python/mozbuild/mozbuild/frontend/emitter.py", line
469, in _link_library
0:15.20 raise SandboxValidationError(
0:15.20 mozbuild.frontend.reader.SandboxValidationError:
0:15.20 ==
0:15.20 FATAL ERROR PROCESSING MOZBUILD FILE
0:15.20 ==
0:15.20
0:15.20 The error occurred while processing the following file or one of the files it includes:
0:15.20
0:15.20 /build/thunderbird-98.0~b2/media/ffvpx/libavcodec/moz.build
0:15.20
0:15.20 The error occurred when validating the result of the execution. The reported error is:
0:15.20
0:15.20 USE_LIBS contains "dav1d", which does not match any LIBRARY_NAME in the tree.
0:15.20
0:15.20

Building TB with AV1 support isn't something what I think is needed to
have. :-) But well, the build configuration isn't something that is
getting less complex over time.

Have you reported this upstream at all? do you have examples of the
build failures that happen when you use the system librnp that we could
work through and post where upstream can see them?
No, I haven't reported any issue upstream yet, I wanted first to have a
basic working Thunderbird package for the current Beta versions.
Unfortunately I often needed to wait in the past on the most bleeding
edge Rust and Cargo stuff due the version dependencies. And now we are
getting closer to the next ESR version of Thunderbird, a broader user
base that can try out these version(s) is more helpful for Debian and to
me as we can mostly work around some upstream issues.

I see currently two main things we need to bring to upstream issue tracker.

1) Why we can't set --disable-av1 as before and the configure script is
ending with an exit code of 1.

2) What is needed to modify in the upstream configure script voodoo so
its possible to use the configure options

--with-system-botan
--with-system-bz2
--with-system-jsonc

again.

So if someone wants to play with these option there will be easily the
build problem visible I've encountered in the past weeks and months on
my side.

--
Regards
Carsten

Bug#1012853: binutils-multiarch: Provides /usr/bin/gp-archive (binutils), /usr/lib/x86_64-linux-gnu/gprofng/libgp-collector.so (libgprofng0:amd64)

Package: binutils-multiarch
Severity: serious
X-Debbugs-CC: binut...@elmo.tasta.io d...@debian.org
Version: 2.38.50.20220615-1

Hi doko,

Doing OS upgrade on my Debian Sid amd64 fails with the following error:

Preparing to unpack .../binutils-multiarch_2.38.50.20220615-1_amd64.deb ...
Unpacking binutils-multiarch (2.38.50.20220615-1) over (2.38-4) ...
dpkg: error processing archive /var/cache/apt/archives/binutils-
multiarch_2.38.50.20220615-1_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/gp-archive', which is also in package
binutils 2.38.50.20220615-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/binutils-multiarch_2.38.50.20220615-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Besides, binutils-multiarch_2.38.50.20220615-1 also tries to overwrite
/usr/lib/x86_64-linux-gnu/gprofng/libgp-collector.so , which is provided by
libgprofng0:amd64 2.38.50.20220615-1.

The former issue cannot be fixed by "apt install -f". The latter one can be
fixed using "apt install -f".

Thanks,
Boyuan Yang


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

Bug#1012849: efitools: ftbfs on riscv64

2022-06-15 Thread 肖盛文


Hi,

在 2022/6/15 23:21, Steve McIntyre 写道:

Control: severity -1 wishlist

On Wed, Jun 15, 2022 at 11:02:50PM +0800, xiao sheng wen wrote:

Control: Severity -1  important

Please don't raise severity on packages asking for support for a
non-release architecture.


FTBFS bug is a RC bug in release architecture,
as riscv is a non-release architecture, so downgrade these FTBFS bugs to 
Severity: important,

Is this suitable?

There is one email in debian-riscv maillist had talk about it:
https://lists.debian.org/debian-riscv/2022/06/msg8.html


--
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012852: bcron-sched fails to start

2022-06-15 Thread Lorenzo Beretta

Package: bcron
Version: 0.11-12
Severity: important

Sorry for using gmail webmail - gmail decided I can't let "less secure
apps" send mail on my behalf, I'm trying to figure out what can be
done.

Anyway, here's what I wanted reportbug to send...

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Lorenzo Beretta 
To: Debian Bug Tracking System 
Subject: bcron-sched fails to start after latest update
Message-ID: 
<165530519508.4489.146445291116667405.report...@dudu.homenet.telecomitalia.it>
X-Mailer: reportbug 11.5.0devuan1
Date: Wed, 15 Jun 2022 16:59:55 +0200

Package: bcron
Version: 0.11-12
Severity: important

Dear Maintainer,

right after the latest upgrade bcron stopped working:
crontab says "bcrontab: Fatal: Could not read crontab",
bcron-sched fails to start, svlogd says
2022-06-15_14:45:25.22147 bcron-sched: Starting
2022-06-15_14:45:25.22152 bcron-sched: Fatal: Could not open crontabs
directory: Permission denied
2022-06-15_14:45:25.22168 bcron-exec: Waiting for remaining slots to complete

According to strace bcron calls setuid(997) (ie "cron")
and then it chdirs /var/spool/cron (OK)
and THEN it tries to openat(AT_FDCWD, "crontabs", ...) => EACCES

$ ls -ld /var/spool/cron/crontabs/
drwx-wx--T 2 root crontab 4096 Jun 15 16:51 /var/spool/cron/crontabs/

but the crontabs in there are owned by cron:cron.

I'm using devuan, but the exact same bug happens in a sid virtual machine.

That's all the info I have atm, good day.


-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
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: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages bcron depends on:
ii  cron-daemon-common   3.0pl1-144
ii  daemon   0.8-1
ii  init-system-helpers  1.63devuan1
ii  libbg2   2.04+dfsg-2.1
ii  libc62.33-7
ii  runit-helper 2.13.1
ii  sysuser-helper   1.3.7+really1.4.1
ii  ucspi-unix   1.0-1

Versions of packages bcron recommends:
ii  dma [mail-transport-agent]  0.13-1+b1
ii  runit   2.1.2-45

Versions of packages bcron suggests:
ii  anacron 2.3-32
ii  runit-init  2.1.2-45

-- no debconf information

Bug#1012655: upstream bug and fix

2022-06-15 Thread Stephan Verbücheln

Kernel 5.18.4 got the patch.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/input/mouse/bcm5974.c?id=v5.18.4=v5.18.3

Regards

Bug#1012851: librust-zstd-sys-dev: impossible to install: depends on missing librust-bindgen-0.59+default-dev

Package: librust-zstd-sys-dev
Version: 1.4.15-1.1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As subject says, the package librust-zstd-sys-dev is totally unusable.

Please, while at it, consider upgrading to v2 - v1.4.15 was abandoned
upstream more than a year ago!


 - Jonas


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

Kernel: Linux 5.17.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages librust-zstd-sys-dev depends on:
pn  librust-bindgen-0.59+default-dev
pn  librust-libc-0.2+default-dev
pn  librust-pkg-config-0.3+default-dev  
pn  libzstd-dev 

librust-zstd-sys-dev recommends no packages.

librust-zstd-sys-dev suggests no packages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKp/R0ACgkQLHwxRsGg
ASE7/hAAlj1GUBaig9+yA679SXSuLenFVoq0exOL0XMCdJVJFMcomftMbbbufl0Y
/kjKjNdeEgfWTmdnEY8rzID+l6m6dK1tmTjJPNld45fm271kwC1Yz9SeINJmq1M2
Bcp2hG19yRqCIgUXY7PnMX28lAcTA+rbt25WgFkSJcG3G7j5+PFhoqCJjCf2y/BO
mq7sF1u8yMGRod0E2I7Or4Fr6N1spBMprFMMCrx7RHllMYIjBRQ8NGy8gu0ZkcBm
EHsbiWDu64mdbwyyBCTFahAMuPzZRGQ3AsM9mcsXhh5sEKRWXTeE6+Ur3rL++Qn6
qRMRgsZ08lO2Dm1ONmCx1bUT4CAof35vGUy4yvpMdAy0U0c+cgQ0sdBFE641I1TY
12IyC/5zaweLh7QR9X3TwiA3ovglNx8BSa6v5LTDqY9yC8c1StgVtS0NOGH0l2EN
biPwxGnXSk0iLDM1DFKJ0/Pt17e5QX6Jnr6ErDbb2by2mYPHk03Zv5/5bvdXLSAC
a393J7pNYE6EfS8W733rrlUAHC6A/CkDL3KOE8S15yOUY43zaokaZdXMX8pGfbNY
TcUKKJCSjZHvUlLGHQ91u9LV6t4dlhLVEBscucddLEPMduFc6YnXdC+jUdCFTfyE
scN9RyzMxBcqx7ryhwJEfYrM78U0MHYswL/iMsW0b1PMk1axefw=
=MlYy
-END PGP SIGNATURE-

Bug#1012451: [Android-tools-devel] Bug#1012451: apksigner: Using PKCS11 keystore fails with NoSuchMethodException

2022-06-15 Thread dev

With upstream I assume you mean the apksigner binary shipped with the Android 
build-tools? I tried with build-tools 30.0.2:

$ /opt/android/cmdline-tools/tools/bin/sdkmanager --install 
"build-tools;30.0.2"

Followed by:

$ /opt/android/build-tools/30.0.2/apksigner sign \
  --ks NONE --ks-type PKCS11 \
  --ks-pass 0001password --ks-key-alias "APK Signing Cert" \
  --provider-class sun.security.pkcs11.SunPKCS11 \
  --provider-arg /etc/pkcs11/sunpkcs11_yubihsm2.cfg \
  --min-sdk-version 21 --max-sdk-version 31 \
  --out apk-release-signed.apk app-release-unsigned.apk
Exception in thread "main" java.lang.NoSuchMethodException: 
sun.security.pkcs11.SunPKCS11.(java.lang.String)
at java.base/java.lang.Class.getConstructor0(Class.java:3585)
at java.base/java.lang.Class.getConstructor(Class.java:2271)
at 
com.android.apksigner.ApkSignerTool$ProviderInstallSpec.installProvider(ApkSignerTool.java:1055)
at 
com.android.apksigner.ApkSignerTool$ProviderInstallSpec.access$200(ApkSignerTool.java:1030)
at com.android.apksigner.ApkSignerTool.sign(ApkSignerTool.java:281)
at com.android.apksigner.ApkSignerTool.main(ApkSignerTool.java:84)

The line numbers in ApkSignerTool are different, but the error remains. I tried 
both with Java 17 and 11.

Danilo

Bug#1012697: libffi: Source URL change not documented


Control: tags -1 patch

A watch file that works for the current release and possible later GitHub 
releases is attached.version=4
opts=uversionmangle=s/-(rc[0-9]+)$/~$1/ \
  https://github.com/libffi/libffi/releases .*/libffi-(\d\S+)\.tar.*

Bug#1012840: xscreensaver-systemd doesn't exit at end of Xfce session

2022-06-15 Thread Jamie Zawinski

I don't see how this is possible. When the user logs out, the X server exits. 
The display connection that both xscreensaver and xscreensaver-systemd have 
open will close with SIGPIPE.

Send logs.

-- 
Jamie Zawinski • jwz.org • dnalounge.com

Bug#1012849: efitools: ftbfs on riscv64

Control: severity -1 wishlist

On Wed, Jun 15, 2022 at 11:02:50PM +0800, xiao sheng wen wrote:
>Control: Severity -1  important
>
>
>在 2022/6/15 22:18, Bo YU 写道:
>> [...]
>> The lintian gives hints also:
>> 
>> ```
>> E: efitools: binary-from-other-architecture usr/bin/cert-to-efi-hash-list
>
>This is a bug of lintian, it's pending, see:
>
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012090

Please don't raise severity on packages asking for support for a
non-release architecture.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"When C++ is your hammer, everything looks like a thumb." -- Steven M. Haflich

Bug#1012847: Stable update

2022-06-15 Thread David Prévot


Hi William,

Thank you for your quick feedback.

Le 15/06/2022 à 16:30, William Desportes a écrit :


Would it be possible to backport that fix in a stable point release


[…]

I am really not sure what is accepted into stable point releases and how 
it works to send such changes. Maybe you could help me better understand 
this ?


The documentation should answer most of your questions, if not, feel 
free to ping me back (and feel free to keep me in the loop before or 
after you submit a bug to release.debian.org).


https://www.debian.org/doc/manuals/developers-reference/pkgs#upload-stable

Regards

David

Bug#998848: thunderbird: please build against librnp-dev (and Depend: on librnp0) directly

2022-06-15 Thread Daniel Kahn Gillmor

Hi Carsten--

On Sun 2022-06-12 17:15:08 +0200, Carsten Schoenert wrote:
> Am Sat, Mar 26, 2022 at 04:06:46PM -0400 schrieb Daniel Kahn Gillmor:
>> I've just uploaded rnp 0.16.0 into debian unstable.  According to
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1732809 the main
>> development line of thunderbird now has a --with-system-rnp flag (but
>> the 91esr series doesn't have it.
>> 
>> So when new versions of thunderbird get built in debian (in experimental
>> first, maybe?) please try to use --with-system-rnp.  If you run into any
>> reason why building against the system rnp isn't working, please don't
>> hesitate to file bug reports against rnp and we'll sort them out.
>
> after again months of waiting for some typical build tools and a lot of
> try and errors attempts I'm now able to build the current beta version
> of Thunderbird (102.0~b4) together with the system package of
> librnp-dev.

that's great news!  thanks for doing this.

> The downside is that this requires currently the usage of the internal
> version of botan, bz2 and jsonc.
>
> I've no kowledge if upstream has plans to reenable the usage of system
> packages for these tools, maybe it's also just a misconfiguration of the
> buildsystem.

Ugh, that doesn't sound so reasonable.  I'd expect those libraries to be
internal to librnp, and not directly exposed to the rest of thunderbird.
so they shouldn't be related to the build process at all, afaict.

Have you reported this upstream at all?  do you have examples of the
build failures that happen when you use the system librnp that we could
work through and post where upstream can see them?

 --dkg


signature.asc
Description: PGP signature

Bug#1012850: scribus: Please update for Poppler 22.06

Package: scribus
Severity: normal
Tags: patch
X-Debbugs-Cc: nathan.teodo...@canonical.com

Dear Maintainer,

Since Poppler 22.06 made its way into experimental, Scribus will need
compatibility changes that are already in upstream to build.

I cherry-picked the relevant changes in the attached patches. However, although
they apply fine with `patch` on the .orig, the patches won't apply with
`debuild`, and I couldn't figure out why. I'm hoping you will spot it faster
than I.


-- System Information:
Debian Release: bookworm/sid
  APT prefers kinetic
  APT policy: (500, 'kinetic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-33-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.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 scribus depends on:
ii  ghostscript  9.55.0~dfsg1-0ubuntu5
ii  libc62.35-0ubuntu3
ii  libcairo21.16.0-5ubuntu2
ii  libcdr-0.1-1 0.1.6-2build3
ii  libcups2 2.4.2-1ubuntu1
ii  libfontconfig1   2.13.1-4.4ubuntu1
ii  libfreehand-0.1-10.1.2-3build2
ii  libfreetype6 2.12.1+dfsg-2
ii  libgcc-s112.1.0-2ubuntu1
ii  libgraphicsmagick-q16-3  1.4+really1.3.38-1
ii  libharfbuzz-icu0 2.7.4-1ubuntu4
ii  libharfbuzz0b2.7.4-1ubuntu4
ii  libhunspell-1.7-01.7.0-4build1
ii  libicu71 71.1-3
ii  libjpeg8 8c-2ubuntu10
ii  liblcms2-2   2.12~rc1-2build2
ii  libmspub-0.1-1   0.1.4-3build4
pn  libopenscenegraph161 
ii  libopenthreads21 3.6.5+dfsg1-7build3
ii  libpagemaker-0.0-0   0.0.4-1build3
ii  libpng16-16  1.6.37-5
ii  libpodofo0.9.8   0.9.8+dfsg-2
pn  libpoppler118
ii  libpython3.103.10.5-1
ii  libqt5core5a 5.15.4+dfsg-2
ii  libqt5gui5   5.15.4+dfsg-2
ii  libqt5network5   5.15.4+dfsg-2
ii  libqt5opengl55.15.4+dfsg-2
ii  libqt5printsupport5  5.15.4+dfsg-2
ii  libqt5widgets5   5.15.4+dfsg-2
ii  libqt5xml5   5.15.4+dfsg-2
ii  libqxp-0.0-0 0.0.2-1build5
ii  librevenge-0.0-0 0.0.4-6ubuntu7
ii  libstdc++6   12.1.0-2ubuntu1
ii  libtiff5 4.4.0~rc1-1
ii  libvisio-0.1-1   0.1.7-1build6
ii  libxml2  2.9.14+dfsg-1
ii  libzmf-0.0-0 0.0.2-1build8
pn  scribus-data 
ii  zlib1g   1:1.2.11.dfsg-2ubuntu9

Versions of packages scribus recommends:
ii  cups-bsd2.4.2-1ubuntu1
ii  fonts-dejavu2.37-2build1
ii  fonts-liberation1:1.07.4-11
ii  hyphen-en-us [hyphen-hyphenation-patterns]  2.8.8-7build2
pn  icc-profiles-free   
ii  xfonts-scalable 1:1.0.3-1.2ubuntu1

Versions of packages scribus suggests:
pn  icc-profiles   
pn  scribus-doc
pn  scribus-template   
ii  texlive-latex-recommended  2021.20220204-1
Index: scribus-1.5.8+dfsg/scribus/plugins/import/pdf/importpdf.cpp
===
--- scribus-1.5.8+dfsg.orig/scribus/plugins/import/pdf/importpdf.cpp
+++ scribus-1.5.8+dfsg/scribus/plugins/import/pdf/importpdf.cpp
@@ -90,7 +90,11 @@ QImage PdfPlug::readThumbnail(const QStr
 #endif
globalParams->setErrQuiet(gTrue);
 
+#if POPPLER_ENCODED_VERSION >= POPPLER_VERSION_ENCODE(22, 3, 0)
+   PDFDoc pdfDoc{ std::make_unique(fname) };
+#else
PDFDoc pdfDoc{fname, nullptr, nullptr, nullptr};
+#endif
if (!pdfDoc.isOk() || pdfDoc.getErrorCode() == errEncrypted)
return QImage();
 
@@ -343,7 +347,11 @@ bool PdfPlug::convert(const QString& fn)
globalParams->setErrQuiet(gTrue);
 // globalParams->setPrintCommands(gTrue);
QList ocgGroups;
+#if POPPLER_ENCODED_VERSION >= POPPLER_VERSION_ENCODE(22, 3, 0)
+   auto pdfDoc = 
std::make_unique(std::make_unique(fname));
+#else
auto pdfDoc = std::unique_ptr(new PDFDoc(fname, nullptr, 
nullptr, nullptr));
+#endif
if (pdfDoc)
{
if (pdfDoc->getErrorCode() == errEncrypted)
@@ -362,8 +370,13 @@ bool PdfPlug::convert(const QString& fn)
 #else
auto fname = new 
GooString(QFile::encodeName(fn).data());
 #endif
+#if POPPLER_ENCODED_VERSION >= POPPLER_VERSION_ENCODE(22, 3, 0)
+   std::optional userPW(std::in_place, 
text.toLocal8Bit().data());
+   pdfDoc.reset(new 
PDFDoc(std::make_unique(fname), userPW, userPW, nullptr));
+#else
auto userPW = new 
GooString(text.toLocal8Bit().data());

Bug#939713: ifupdown: add support for iproute2 bridge to replace deprecated bridge-utils

2022-06-15 Thread Martin-Éric Racine

Package: ifupdown
Version: 0.8.37
Followup-For: Bug #939713

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As stated in many different places, bridge-utils has long been deprecated and 
ought to be replaced with built-in support for the "bridge" command in iproute2 
instead. 

The syntax I would propose for interfaces:

iface br0 inet METHOD
address (IP address, if METHOD other than dhcp)
hwaddress (default: random, or specify MAC address)
bridge ("all" or space-separated list, may include /en* wildcards)

This would also bring the syntax for bridges in line with what ifupdown already 
uses (bridge-utils deviates from this for a number of options).

ifupdown already Depends on iproute2, so this should be fairly straightforward.

- -- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 'testing')
Architecture: i386 (i586)

Kernel: Linux 5.18.0-1-686 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ifupdown depends on:
ii  adduser   3.121
ii  iproute2  5.18.0-1
ii  libc6 2.33-7
ii  lsb-base  11.2

Versions of packages ifupdown recommends:
ii  dhcpcd5 [dhcp-client]  9.4.1-0.1

Versions of packages ifupdown suggests:
ii  ppp 2.4.9-1+1.1+b1
pn  rdnssd  

- -- debconf information:
  ifupdown/convert-interfaces: true
  ifupdown/convert-interfaces-hotplug: true

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmKp8zMACgkQrh+Cd8S0
17a+ABAAhKlvHzsvCDJAbqSTi6Lt/6JAk7C0p2vSCqEASnT0RlQGx+eEnHeue73T
ulH0L9D4m5V9Va4gxiJJDNxXHKi6a5Fl08uRR3+tVLFXswq2IIucnZPhwurJ6Rqx
gCKkHLWz1pNiWlMMhj5YFSrpxGrAaHzhbR0oEg5Ja//QIwNTWgGhyVCB8ibJV63i
vPReuJfwc7xtwghcO9QCJKyQG98d/oqoiqhySaT8kUaMWi2pIC0OpLit5af07jpd
J381SVGs6SCG6h0CJGRwYaL/hZls0t716Tq+AF2P1t8/7b4ruQp2n2hL/bNz+uZg
7zlRo/wFvneuAMhwlPnE+5a5eISL1JVBKK4Dr39jXdy8SfhbTP2H+zL/xl6WPMAr
9zv1nWZpykFkwrbNq8lQnso7R+r6PKcluBdguu19AnpA8LivoXnk0JbF01p1z9Ys
+0FJJqjey5GeThW7w9V4x/ldQw8KtRvwCs1/58qUcYdKvAJrSugv59WFq4IkgdN6
+zYxe5vZhd08aPh0Amt8QxYze3yC8y0z6juF/DI2ev6xavYjW+RG6/U9WKCLKBQu
pmz3+8t3YaHu523VNxBSdx9LFdTAfBsajJPcg8VjuG2V8Csn9sGl+EXMRcevyYvs
NOO4zDTShmdcXzE+u2wPu4JEt9cyM/XRuvytOt4Qswp1GkX+4wg=
=rssa
-END PGP SIGNATURE-

Bug#1012849: efitools: ftbfs on riscv64

2022-06-15 Thread 肖盛文


Control: Severity -1  important


在 2022/6/15 22:18, Bo YU 写道:

[...]
The lintian gives hints also:

```
E: efitools: binary-from-other-architecture usr/bin/cert-to-efi-hash-list


This is a bug of lintian, it's pending, see:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012090


--
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012849: efitools: ftbfs on riscv64

2022-06-15 Thread Bo YU

Package: efitools
Version: 1.9.2-2
Severity: minor
Tags: ftbfs, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org

Dear Maintainer,

The package has a ftbfs issue on riscv64 due to unsupported arch.
The full buildd log is here:

https://buildd.debian.org/status/fetch.php?pkg=efitools=riscv64=1.9.2-2=1655250102=0

Although it is ok to build on my locally machines with patch attached,
but I'm not sure now if he works properly on riscv64 hardware.
The lintian gives hints also: 

```
E: efitools: binary-from-other-architecture usr/bin/cert-to-efi-hash-list
E: efitools: binary-from-other-architecture usr/bin/cert-to-efi-sig-list
E: efitools: binary-from-other-architecture usr/bin/efi-readvar
E: efitools: binary-from-other-architecture usr/bin/efi-updatevar
E: efitools: binary-from-other-architecture usr/bin/flash-var
E: efitools: binary-from-other-architecture usr/bin/hash-to-efi-sig-list
E: efitools: binary-from-other-architecture usr/bin/sig-list-to-certs
E: efitools: binary-from-other-architecture usr/bin/sign-efi-sig-list
E: efitools-dbgsym: binary-from-other-architecture 
usr/lib/debug/.dwz/riscv64-linux-gnu/efitools.debug

```
Please consider to apply it if you think this patch makes sense:)

Thank you,

Bo
--- a/Make.rules
+++ b/Make.rules
@@ -8,6 +8,8 @@
 ARCH3264 =
 else ifeq ($(ARCH),aarch64)
 ARCH3264 =
+else ifeq ($(ARCH),riscv64)
+ARCH3264 =
 else ifeq ($(ARCH),arm)
 ARCH3264 =
 else
@@ -55,6 +57,11 @@
   LDFLAGS += --defsym=EFI_SUBSYSTEM=0x0a
   FORMAT = -O binary
 endif
+
+ifeq ($(ARCH),riscv64)
+  LDFLAGS += --defsym=EFI_SUBSYSTEM=0x0a
+  FORMAT = -O binary
+endif
 
 %.efi: %.so
 	$(OBJCOPY) -j .text -j .sdata -j .data -j .dynamic -j .dynsym \


signature.asc
Description: PGP signature

Bug#1012848: synaptic: strange error when rinning from CLI: gl_surface_presentation_helper

2022-06-15 Thread Tim McConnell

Package: synaptic
Version: 0.90.2+b1
Severity: normal
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? ran synaptic from terminal
   * What exactly did you do (or not do) that was effective (or
 ineffective)? chose programs and installed
   * What was the outcome of this action? weird output, not sure if it's a
"bug" or not:
sudo synaptic
[sudo] password for tmick:
[38563:38597:0615/085706.649998:ERROR:bus.cc(398)] Failed to connect to the
bus: Could not parse server address: Unknown address type (examples of valid
types are "tcp" and on UNIX "unix")
[38563:38597:0615/085706.650102:ERROR:bus.cc(398)] Failed to connect to the
bus: Could not parse server address: Unknown address type (examples of valid
types are "tcp" and on UNIX "unix")
[38563:38597:0615/085707.836196:ERROR:bus.cc(398)] Failed to connect to the
bus: Could not parse server address: Unknown address type (examples of valid
types are "tcp" and on UNIX "unix")
[38563:38597:0615/085707.836248:ERROR:bus.cc(398)] Failed to connect to the
bus: Could not parse server address: Unknown address type (examples of valid
types are "tcp" and on UNIX "unix")
libva error: vaGetDriverNameByIndex() failed with unknown libva error,
driver_name = (null)
[38563:38597:0615/085709.583415:ERROR:bus.cc(398)] Failed to connect to the
bus: Could not parse server address: Unknown address type (examples of valid
types are "tcp" and on UNIX "unix")
[38563:38597:0615/085709.583454:ERROR:bus.cc(398)] Failed to connect to the
bus: Could not parse server address: Unknown address type (examples of valid
types are "tcp" and on UNIX "unix")
[38563:38600:0615/085712.298860:ERROR:nss_util.cc(335)] After loading Root
Certs, loaded==false: NSS error code: -8018
[38605:38605:0615/085718.088767:ERROR:gl_surface_presentation_helper.cc(260)]
GetVSyncParametersIfAvailable() failed for 1 times!
[38605:38605:0615/085728.244112:ERROR:gl_surface_presentation_helper.cc(260)]
GetVSyncParametersIfAvailable() failed for 2 times!
[38605:38605:0615/085733.42:ERROR:gl_surface_presentation_helper.cc(260)]
GetVSyncParametersIfAvailable() failed for 3 times!

* What outcome did you expect instead? no errors?

*** End of the template - remove these template lines ***


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

Kernel: Linux 5.18.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT)
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 synaptic depends on:
ii  hicolor-icon-theme   0.17-2
ii  libapt-pkg6.02.5.0
ii  libc62.33-7
ii  libept1.6.0  1.2.1
ii  libgcc-s112.1.0-2
ii  libgdk-pixbuf-2.0-0  2.42.8+dfsg-1
ii  libglib2.0-0 2.72.2-2
ii  libgtk-3-0   3.24.34-1
ii  libpango-1.0-0   1.50.7+ds-1
ii  libstdc++6   12.1.0-2
ii  libvte-2.91-00.68.0-1+b1
ii  libxapian30  1.4.18-4
ii  policykit-1  0.105-33

Versions of packages synaptic recommends:
ii  libgtk3-perl  0.038-1
ii  xdg-utils 1.1.3-4.1

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.53
ii  deborphan1.7.35
ii  dwww 1.15
ii  menu 2.1.49
ii  software-properties-gtk  0.96.20.2-2.1
ii  tasksel  3.69+rebuild

-- no debconf information

Bug#967075: haskell-ghc-lib-parser: FTBFS on mips* and s390x: /usr/lib/ghc/include/stg/SMP.h:390:2: error: #error memory barriers unimplemented on this architecture

2022-06-15 Thread John David Anglin


Same error occurs on hppa.

The "sync" instruction is simplest barrier on hppa, so the powerpc asm would 
work:

#elif defined(powerpc_HOST_ARCH) || defined(powerpc64_HOST_ARCH) \
    || defined(powerpc64le_HOST_ARCH)
    __asm__ __volatile__ ("sync" : : : "memory");

--
John David Anglin  dave.ang...@bell.net

Bug#1007717: Updated draft resolution

2022-06-15 Thread Lucas Nussbaum

Hi,

On 15/06/22 at 07:32 +0200, Helmut Grohne wrote:
> The other model restricts itself to only adding files below
> debian/ and then using debian/rules to actually apply patches during
> build. This latter model is fairly annoying, because there are so many
> different ways of doing it (i.e. we lack consistency there).

If you look at Debian 'testing' only, I think that the only remaining
way to do that is 1.0 + quilt (packages that were using dpatch have all
been converted or removed from testing).

> So what I'd like to ensure is that any resolution we do here is clear
> about discontinuing the use of 1.0-with-diff together with a patch
> system to be applied during package build. We've explored that model in
> depth and settled on 3.0 (quilt) as the superior solution. There is no
> need to explore it any further (and as demonstrated by curl, gcc and
> glibc, you can even turn 3.0 (quilt) ad absurdum). So in my view, the
> only reasonable use of 1.0-with-diff is where you manage your diff
> externally rather than during package build.

According to https://udd.debian.org/~lucas/format10.cgi (which is based
on what lintian knows about the archive), there are 114 packages using
1.0 with quilt. However, 67 of those are maintained by the Debian X
team. If you plan to discontinue 1.0+patch-system in the context of
this bug, it would probably be a good idea to have a discussion with
them to better understand their use case.

I personally think that it would be enough for this bug to issue a clear
statement that we want to move away from 1.0 unless there's a good
reason, on a per-package basis, not to. That would create a mandate to
work on surveying the remaining packages and identifying the remaining
use cases. That would also allow motivated volunteers to work on
migrating the remaining packages when there's no reason to stay with
1.0, using the NMU procedure if needed.

Lucas

Bug#987613: closed by Debian FTP Masters (reply to Steve McIntyre <93...@debian.org>) (Bug#987613: fixed in mokutil 0.6.0-1)

On Wed, Jun 15, 2022 at 04:17:05PM +0300, Adrian Bunk wrote:
>Control: reopen -1
>
>On Sun, Jun 12, 2022 at 09:09:08PM +, Debian Bug Tracking System wrote:
>>...
>>  mokutil (0.6.0-1) unstable; urgency=medium
>>...
>>* Switch to Arch: any to allow for more architectures.
>>  Closes: #987613, #991933.
>>...
>
>This change seems to be missing in the package:
>https://buildd.debian.org/status/package.php?p=mokutil
>https://tracker.debian.org/media/packages/m/mokutil/control-0.6.0-1

Argh, apologies - looks like I lost that change in building and
testing locally. Just uploaded again now.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Since phone messaging became popular, the young generation has lost the
 ability to read or write anything that is longer than one hundred and sixty
 characters."  -- Ignatios Souvatzis

Bug#1012600: Upvote

2022-06-15 Thread Jonas Lippuner

I am also affected by this. I did simple apt update and apt upgrade and now
I can't use my zfs volume anymore.

Bug#987613: closed by Debian FTP Masters (reply to Steve McIntyre <93...@debian.org>) (Bug#987613: fixed in mokutil 0.6.0-1)

2022-06-15 Thread Adrian Bunk

Control: reopen -1

On Sun, Jun 12, 2022 at 09:09:08PM +, Debian Bug Tracking System wrote:
>...
>  mokutil (0.6.0-1) unstable; urgency=medium
>...
>* Switch to Arch: any to allow for more architectures.
>  Closes: #987613, #991933.
>...

This change seems to be missing in the package:
https://buildd.debian.org/status/package.php?p=mokutil
https://tracker.debian.org/media/packages/m/mokutil/control-0.6.0-1

cu
Adrian

Bug#1008016: ITP: safe-network -- network routing and service daemon for the Safe Network

0.62.4 draft 1 needs embedding 159 crates (111 missing, 1 broken, 25 outdated, 
22 ahead); builds in ~65 minutes; runs but functionality not yet properly tested

Main task now is to keep package up-to-date with upstream releases, and
package more of the crates currently embedded.

Here's how you can help:

As user running Debian, you can test this draft package: Either build it
yourself from source or tell (by posting to this bugreport) if you
prefer testing the binary packages I built - then I will share those.

As developer (but no need to be official member of Debian!), you can
join the Debian Rust team and help package these missing crates:
https://salsa.debian.org/debian/safe-network/-/blob/debian/latest/debian/TODO


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1012846: karbon: Please update for Poppler 22.06

Package: karbon
Severity: normal
X-Debbugs-Cc: nathan.teodo...@canonical.com

Dear Maintainer,

Since Poppler 22.06 is made its way into experimental, Karbon will need
compatibility changes that are already in upstream to build. Please consider
updating the package.


-- System Information:
Debian Release: bookworm/sid
  APT prefers kinetic
  APT policy: (500, 'kinetic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-33-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.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 karbon depends on:
pn  calligra-libs 
ii  libc6 2.35-0ubuntu3
ii  libgcc-s1 12.1.0-2ubuntu1
ii  libkf5archive55.95.0-0ubuntu1
ii  libkf5completion5 5.95.0-0ubuntu1
ii  libkf5configcore5 5.95.0-0ubuntu1
ii  libkf5coreaddons5 5.95.0a-0ubuntu1
ii  libkf5guiaddons-bin   5.95.0-0ubuntu1
ii  libkf5guiaddons5  5.95.0-0ubuntu1
ii  libkf5i18n5   5.95.0-0ubuntu1
ii  libkf5iconthemes5 5.95.0-0ubuntu1
ii  libkf5widgetsaddons5  5.95.0-0ubuntu1
ii  libkf5xmlgui5 5.95.0-0ubuntu1
ii  libodfgen-0.1-1   0.1.8-2build2
pn  libpoppler118 
ii  libqt5core5a  5.15.4+dfsg-2
ii  libqt5gui55.15.4+dfsg-2
ii  libqt5widgets55.15.4+dfsg-2
ii  libqt5xml55.15.4+dfsg-2
ii  librevenge-0.0-0  0.0.4-6ubuntu7
ii  libstdc++612.1.0-2ubuntu1
ii  libwpg-0.3-3  0.3.3-1build3
ii  libwps-0.4-4  0.4.12-2build1

Versions of packages karbon recommends:
ii  pstoedit  3.78-1

karbon suggests no packages.

Bug#1012847: Fails (500 Internal Server Error) with some queries

2022-06-15 Thread David Prévot

Package: phpmyadmin
Version: 4:5.0.4+dfsg2-2
Severity: important
Tags: upstream patch
X-Debbugs-Cc: emor...@evolix.fr
Control: submitter -1 emor...@evolix.fr

Hi William,

In Bullseye (and Buster backports), some queries ends with an Internal
Server Error (500), e.g.:

SELECT *, count(reference)
FROM declaloc_declarant
GROUP BY reference, platform_uuid
HAVING count(reference) > 1;

I notice you fixed it in recent versions, and the same fix has been
deployed in production with success.

https://github.com/phpmyadmin/phpmyadmin/commit/16f81e47eab289b13bf39ed2ca6c3c0b0c923845

Would it be possible to backport that fix in a stable point release, and
in buster-backports?

Thanks in advance.

Regards

David


signature.asc
Description: PGP signature

Bug#1012844: wpasupplicant: please provide a default wpa_supplicant.conf file to have /run/wpa_supplicant in the netdev group

2022-06-15 Thread Andrej Shadura

Hi,

On Wed, 15 Jun 2022, at 13:55, Vincent Lefevre wrote:
> Package: wpasupplicant
> Version: 2:2.10-9+b1
> Severity: wishlist
>
> Users should not have to modify the default configuration to make
> things work as expected. Currently, it is not possible to run wpa_cli
> and wpa_gui as a normal user from the netdev group, contrary to other
> wifi-related tools like iwconfig, nmcli, iw, and in the past, wicd.

Thanks for the bug report!

Would something like this work for you?
https://salsa.debian.org/debian/wpa/-/commit/14709d27604a4dc34cf07e9ef5ccb579cf9d7192

Unfortunately, I’m not sure there is a better way to provide a default without 
patching wpa_supplicant’s config parser.

-- 
Cheers,
  Andrej

Bug#1009998: [Pkg-samba-maint] Processed: Re: Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade

2022-06-15 Thread L. van Belle

Micheal, 

For the above link/bug reports, which points to : 

https://gitlab.com/samba-team/samba/-/commit/34771e1931587807d0395c7ac7f4be1
8654997f4 

This fix is already included in 4.16.2.  I've just verified the source of
4.16.2


Greetz, 

Louis



> -Oorspronkelijk bericht-
> Van: Pkg-samba-maint  lists.debian.net> Namens Debian Bug Tracking System
> Verzonden: woensdag 15 juni 2022 12:27
> Aan: Michael Tokarev 
> CC: pkg-samba-ma...@lists.alioth.debian.org
> Onderwerp: [Pkg-samba-maint] Processed: Re: Bug#1009998: gvfs-backends:
> Unable to access smb://host/sharing on any file manager after upgrade
> 
> Processing control commands:
> 
> > tag -1 + moreinfo
> Bug #1009998 [src:samba] gvfs-backends: Unable to access
> smb://host/sharing on any file manager after upgrade Added tag(s)
> moreinfo.
> 
> --
> 1009998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009998
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> 
> ___
> Pkg-samba-maint mailing list
> pkg-samba-ma...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-samba-maint

Bug#1012845: pdftoipe: Patch for compatibility with Poppler >22.03

Package: pdftoipe
Severity: normal
Tags: patch
X-Debbugs-Cc: nathan.teodo...@canonical.com

Dear Maintainer,

Since Poppler 22.06 is made its way into experimental, Pdftoipe will need
compatibility changes to build. I got the merge request from
https://github.com/otfried/ipe-
tools/pull/48/commits/14335180432152ad094300d0afd00d8e390469b2 and adapted it
so that it doesn't break builds with previous Poppler versions.

The result is in the attached patch. With Sbuilder I made sure it builds
against both current and new Poppler.


-- System Information:
Debian Release: bookworm/sid
  APT prefers kinetic
  APT policy: (500, 'kinetic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-33-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.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 pdftoipe depends on:
ii  libc6  2.35-0ubuntu3
ii  libgcc-s1  12.1.0-2ubuntu1
pn  libpoppler118  
ii  libstdc++6 12.1.0-2ubuntu1

Versions of packages pdftoipe recommends:
pn  ipe  

pdftoipe suggests no packages.

*** /home/nteodosio/canonical/debian-updates/poppler/ipetools.diff
diff -Nru ipe-tools-7.2.24.1/debian/changelog 
ipe-tools-7.2.24.1/debian/changelog
--- ipe-tools-7.2.24.1/debian/changelog 2022-02-19 15:56:57.0 -0300
+++ ipe-tools-7.2.24.1/debian/changelog 2022-06-15 09:06:32.0 -0300
@@ -1,3 +1,11 @@
+ipe-tools (1:7.2.24.1-2) UNRELEASED; urgency=medium
+
+  [ Nathan Pratta Teodosio ]
+  * build-with-poppler-22.03.patch: Fix build for poppler 22.03.
+  * d/control: Build depends on libpoppler-cpp-dev.
+
+ -- Nathan Pratta Teodosio   Wed, 15 Jun 2022 
09:06:32 -0300
+
 ipe-tools (1:7.2.24.1-1) unstable; urgency=medium
 
   [ Steve Robbins ]
diff -Nru ipe-tools-7.2.24.1/debian/control ipe-tools-7.2.24.1/debian/control
--- ipe-tools-7.2.24.1/debian/control   2022-02-19 15:56:57.0 -0300
+++ ipe-tools-7.2.24.1/debian/control   2022-06-15 09:05:56.0 -0300
@@ -8,7 +8,8 @@
dh-python,
python3:any | python3-all:any | python3-dev:any | 
python3-all-dev:any | dh-sequence-python3,
pkg-config,
-   libpoppler-private-dev
+   libpoppler-private-dev,
+   libpoppler-cpp-dev
 Standards-Version: 4.1.3
 Vcs-Browser: https://salsa.debian.org/science-team/ipe-tools
 Vcs-Git: https://salsa.debian.org/science-team/ipe-tools.git
diff -Nru ipe-tools-7.2.24.1/debian/patches/build-with-poppler-22.03.patch 
ipe-tools-7.2.24.1/debian/patches/build-with-poppler-22.03.patch
--- ipe-tools-7.2.24.1/debian/patches/build-with-poppler-22.03.patch
1969-12-31 21:00:00.0 -0300
+++ ipe-tools-7.2.24.1/debian/patches/build-with-poppler-22.03.patch
2022-06-15 09:06:32.0 -0300
@@ -0,0 +1,42 @@
+Author: Nathan Pratta Teodosio , oreo639
+Description: Fix build for poppler >22.03
+
+--- a/pdftoipe/pdftoipe.cpp2022-06-15 08:45:57.248773786 -0300
 b/pdftoipe/pdftoipe.cpp2022-06-15 08:45:23.915883939 -0300
+@@ -7,6 +7,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #include "goo/GooString.h"
+ #include "goo/gmem.h"
+@@ -84,6 +85,20 @@
+   if (quiet)
+ globalParams->setErrQuiet(quiet);
+ 
++#if POPPLER_VERSION_MAJOR > 22 || (POPPLER_VERSION_MAJOR == 22 && 
POPPLER_VERSION_MINOR >= 3)
++  std::optional ownerPW, userPW;
++  if (ownerPassword[0]) {
++ownerPW = GooString(ownerPassword);
++  } else {
++ownerPW = std::nullopt;
++  }
++  if (userPassword[0]) {
++userPW = GooString(userPassword);
++  } else {
++userPW = std::nullopt;
++  }
++  PDFDoc *doc = new PDFDoc(std::make_unique(fileName), ownerPW, 
userPW);
++#else
+   GooString *ownerPW, *userPW;
+   if (ownerPassword[0]) {
+ ownerPW = new GooString(ownerPassword);
+@@ -100,6 +115,7 @@
+   PDFDoc *doc = new PDFDoc(fileName, ownerPW, userPW);
+   delete userPW;
+   delete ownerPW;
++#endif
+ 
+   if (!doc->isOk())
+ return 1;
diff -Nru ipe-tools-7.2.24.1/debian/patches/series 
ipe-tools-7.2.24.1/debian/patches/series
--- ipe-tools-7.2.24.1/debian/patches/series2022-02-19 15:56:57.0 
-0300
+++ ipe-tools-7.2.24.1/debian/patches/series2022-06-15 09:06:32.0 
-0300
@@ -1 +1,2 @@
+build-with-poppler-22.03.patch
 cross.patch
diff -Nru ipe-tools-7.2.24.1/debian/changelog 
ipe-tools-7.2.24.1/debian/changelog
--- ipe-tools-7.2.24.1/debian/changelog 2022-02-19 15:56:57.0 -0300
+++ ipe-tools-7.2.24.1/debian/changelog 2022-06-15 09:06:32.0 -0300
@@ -1,3 +1,11 @@
+ipe-tools (1:7.2.24.1-2) UNRELEASED; urgency=medium
+
+  [ Nathan Pratta Teodosio ]
+  * build-with-poppler-22.03.patch: Fix build for poppler 22.03.
+  * d/control: Build depends on libpoppler-cpp-dev.
+
+ -- Nathan Pratta Teodosio   Wed, 15 Jun 2022 
09:06:32 -0300
+
 ipe-tools (1:7.2.24.1-1) unstable;

Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade

2022-06-15 Thread Jeremy Bicha

Control: tags -1 -patch

On Wed, Jun 15, 2022 at 8:10 AM Michael Tokarev  wrote:
> Well, sure I've seen this particular message, but this "fix" is included in 
> 4.16.0 already, FWIW.
>
> So the "patch" tag must be due to something else, I guess.
> This is why I asked for more info here.

I only added the patch tag because of the earlier link to a patch.
I'll remove it now based on your comments that the patch was already
applied.

Thanks,
Jeremy Bicha

Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade

2022-06-15 Thread Michael Tokarev


15.06.2022 14:59, L. van Belle wrote:

Since im not seeing it apparing in debian mail folder here.


Thank you for this Louis!


-Oorspronkelijk bericht-
Van: L. van Belle 
Verzonden: woensdag 15 juni 2022 13:47
Aan: '1009...@bugs.debian.org' <1009...@bugs.debian.org>
Onderwerp: RE: [Pkg-samba-maint] Processed: Re: Bug#1009998: gvfs-
backends: Unable to access smb://host/sharing on any file manager after
upgrade

Micheal,

For the above link/bug reports, which points to :

https://gitlab.com/samba-team/samba/-
/commit/34771e1931587807d0395c7ac7f4be18654997f4

This fix is already included in 4.16.2.  I've just verified the source of 4.16.2


Well, sure I've seen this particular message, but this "fix" is included in 
4.16.0 already, FWIW.

So the "patch" tag must be due to something else, I guess.
This is why I asked for more info here.

Thanks,

/mjt

Bug#1012844: wpasupplicant: please provide a default wpa_supplicant.conf file to have /run/wpa_supplicant in the netdev group

2022-06-15 Thread Vincent Lefevre

Package: wpasupplicant
Version: 2:2.10-9+b1
Severity: wishlist

Users should not have to modify the default configuration to make
things work as expected. Currently, it is not possible to run wpa_cli
and wpa_gui as a normal user from the netdev group, contrary to other
wifi-related tools like iwconfig, nmcli, iw, and in the past, wicd.

The way suggested by the README.Debian file:


The wpa_supplicant process can be interacted with by members of the "netdev"
group if the example roaming configuration was used as is (or by whatever
group or gid specified by the GROUP= crtl_interface parameter).

# the default ctrl_interface option used in the example file
# /usr/share/doc/wpasupplicant/examples/wpa-roam.conf
ctrl_interface=DIR=/run/wpa_supplicant GROUP=netdev

To interact with the supplicant, the wpa_cli (command line) and wpa_gui (QT)
have been provided. With these you may connect, disconnect, add/delete new
network blocks, provide required interactive security information and so on.


This should be configured like that by default.

(Perhaps until wpa_cli and wpa_gui are able to communicate with
wpa_supplicant via DBus? Not sure about that...)

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

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

Versions of packages wpasupplicant depends on:
ii  adduser3.121
ii  libc6  2.33-7
ii  libdbus-1-31.14.0-1
ii  libnl-3-2003.5.0-0.1
ii  libnl-genl-3-200   3.5.0-0.1
ii  libnl-route-3-200  3.5.0-0.1
ii  libpcsclite1   1.9.8-1
ii  libreadline8   8.1.2-1.2
ii  libssl33.0.3-7
ii  lsb-base   11.2

wpasupplicant recommends no packages.

Versions of packages wpasupplicant suggests:
pn  libengine-pkcs11-openssl  
pn  wpagui

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1012776: gambas3: backport package


Am 15.06.22 um 13:02 schrieb Belmootek:

But the backport is not in the apt list.

Please, could you tell me how its works?


It is still waiting in the NEW queue: 
https://ftp-master.debian.org/new/gambas3_3.17.2-1~bpo11+1.html

Bug#1012843: i2pd: Default install SEGV

2022-06-15 Thread Erik de Castro Lopo

Package: i2pd
Version: 2.41.0-1+b1
Severity: important

Dear Maintainer,

* Installed i2pd.
* `systemctl status i2pd` reports:
× i2pd.service - I2P Router written in C++
 Loaded: loaded (/lib/systemd/system/i2pd.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: signal) since Wed 2022-06-15 21:25:17 AEST; 
1min 51s ago
   Docs: man:i2pd(1)
 https://i2pd.readthedocs.io/en/latest/
Process: 23181 ExecStart=/usr/sbin/i2pd $DAEMON_OPTS (code=killed, 
signal=SEGV)
CPU: 72ms

Jun 15 21:25:14 ada systemd[1]: Starting I2P Router written in C++...
Jun 15 21:25:14 ada systemd[1]: i2pd.service: Control process exited, 
code=killed, status=11/SEGV
Jun 15 21:25:17 ada systemd[1]: i2pd.service: Failed with result 'signal'.
Jun 15 21:25:17 ada systemd[1]: Failed to start I2P Router written in C++.

* `systemctl restart i2pd` has the same issue.

* I expect it to run out of the box (especially not SEGV).


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages i2pd depends on:
ii  adduser 3.121
ii  init-system-helpers 1.63
ii  libboost-filesystem1.74.0   1.74.0-16
ii  libboost-program-options1.74.0  1.74.0-16
ii  libc6   2.33-7
ii  libgcc-s1   12.1.0-2
ii  libminiupnpc17  2.2.3-1+b1
ii  libssl3 3.0.3-7
ii  libstdc++6  12.1.0-2
ii  lsb-base11.2
ii  zlib1g  1:1.2.11.dfsg-4

i2pd recommends no packages.

i2pd suggests no packages.

-- no debconf information

Bug#934072: OpenRD images are gone

2022-06-15 Thread Rick Thomas

Hi all,

This has suddenly had it's priority raised a bit for me.  I was fiddling around 
with my Ultimate OpenRD, and I managed to render the boot disk un-bootable.  
I'd like to re-install with either Bullseye or Bookworm (Prior to my fumble 
fingers, it was happily running Bullseye via upgrade from Buster and probably 
Stretch back before that).  Ideally, I'd like to try Bookworm, but if that's 
not possible, I'll be happy with Bullseye.

Do you think it's possible to make the install stuff for the OpenRD's sometime 
soon?

Thanks very much!
Rick

On Wed, Jun 8, 2022, at 10:25 PM, Martin Michlmayr wrote:
> Vagrant, see below:
>
> * Martin Michlmayr  [2019-08-06 20:10]:
>> I noticed that there are no pre-built images for OpenRD in buster
>> anymore.
>> 
>> I found:
>> 
>> commit e799d626f45e9c706d05003e3112d481db2870a9
>> Author: Vagrant Cascadian 
>> Date:   Wed Dec 5 17:45:22 2018 +0100
>> 
>> [armel] Disable OpenRD targets, no longer present in u-boot.
>> 
>> While it's true that there are no u-boot images for OpenRD anymore,
>> I think the installer and kernel should still work fine (people can
>> install u-boot from stretch or even use the Marvell u-boot that ships
>> with the device).
>> 
>> I think the part of the commit above that removed openrd from
>> build/config/armel/kirkwood/netboot.cfg should be reverted.
>> (the change to build/boot/arm/armel-kirkwood-u-boot-image-config
>> is obviously fine)
>> 
>> I don't have an OpenRD anymore but I can probably find someone if
>> testing is required.
>
> I became aware recently that this was never fixed.  Rick Thomas has
> two OpenRD (Ultimate and Client) and could test the images.
>
> Since bullseye is the last release to support these devices (I think?
> I never know what the status of armel is), I wonder if it would make
> sense to add the images back to d-i in a point release.
>
> Basically to revert the change to build/config/armel/kirkwood/netboot.cfg
> from commit e799d626f45e9c706d05003e3112d481db2870a9
>
> Vagrant, do you think you could do a bullseye d-i checkout, make that
> change and make the OpenRD images available for Rick to test?
> (I don't have any ARM machines)
>
> -- 
> Martin Michlmayr
> https://www.cyrius.com/

Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?

2022-06-15 Thread Thomas Schmitt

Hi,

although it was not the final solution of this bug report, i beefed up
my merger script for Debian ISOs so that it can combine an arbitrary
number of ISOs (within the limits of /dev/loop* and mount(8)).
Maybe it can serve as answer for the next time this wish comes up.

The script is uploaded as

https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos

with GPG detached signature

https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos.sig
for checking by gpg --verify.

After download, the user probably has to give x-permissions to the script.

When run without arguments it gives this help text:
---

usage: merge_debian_isos result_iso mount_template iso1 iso2 [... isoN]

Mounts by sudo the ISO 9660 images iso1 to isoN at directories
mount_template1 to mount_templateN, if not already mounted that way.
Then the Debian pools and package lists get merged and a new
ISO 9660 image result_iso is produced, which must not yet exist.
If iso1 is bootable then the new image will be bootable by the
same means.
At least the parent directory of mount_template must already exist.
All arguments must be single words without using quotation marks.
None of the isoN must be equal to another isoM.

This script creates and finally removes the following temporary tree
and files which must not yet exist in the current working directory:
./merged_dists , ./merged_md5sum.txt , ./merged_REAMDE.txt
./temp_file
Further it creates and finally removes directories mount_template*
if they are needed and do not exist when the script starts.
It depends on the following programs:
awk, basename, bash, cat, chmod, cp, dirname, expr, fgrep, grep,
gunzip, gzip, head, ls, mkdir, mount, mv, rm, rmdir, sha256sum,
sed, sort, stat, sudo, umount, xorriso
Recommended are: md5sum, sha1sum, sha512sum

Exported non-empty variable MERGE_DATE enforces a particular
date string in the text which gets prepended to /README.txt .
Exported non-empty variable MERGE_FOR_DIST enforces the use of a
particular directory in /dists of iso1. Normally only one
such directory is found and thus no need to set MERGE_FOR_DIST.
Exported non-empty variable XORRISO overrides command xorriso.
This may be needed if installed xorriso is older than 1.4.2.

Example using GNU xorriso-1.5.4 instead of /usr/bin/xorriso:
export XORRISO=$HOME/xorriso-1.5.4/xorriso/xorriso
mkdir merge_mount
merge_debian_isos merged.iso merge_mount/iso \
debian-11.2.0-amd64-DVD-[12345].iso
rmdir merge_mount

---

The old script merge_2_debian_isos still exists but will refuse to run,
unless the user removes an exit command near the start of the script.
In its downloaded form it tells the user:
---
THIS SCRIPT IS DEPRECATED ! USE ITS SUCCESSOR: merge_debian_isos

The script merge_2_debian_isos still exists only because it was mentioned
in Debian bug 1011343. The successor can merge more than two ISOs.
So do not edit this script to remove this warning and the 'exit 7' line.
---

I tested the new script by merging the first three ISOs of
debian-11.2.0-amd64-DVD-*.iso
and installing Debian from the result into a qemu-system-x86_64 VM with
4 GB RAM and 128 GB system disk.

After the installation was completed, i successfuly installed packages
which are in DVDs 1, 2, and 3 and were not installed yet:
apt-get install apt-file
apt-get install lame
apt-get install xorriso

To verify that this success does not come from an unwanted network
connection i tried to install packages from DVD 4
apt-get install bash-doc
apt-get install devede
Both attempts failed with the message that the packages are not available.

Have a nice day :)

Thomas

Bug#1012776: gambas3: backport package

2022-06-15 Thread Belmootek


Hi,

Thanks for do the backport.

I follow the tutorial in: https://wiki.debian.org/Backports

But the backport is not in the apt list.

Please, could you tell me how its works?

Thanks

Martin

El 14/6/22 a las 0:21, Bastian Germann escribió:

Source: gambas3
Severity: wishlist
X-Debbugs-Cc: Belmootek 

Request by Martín Belmootek:

As you know it is now feasible to make web pages quite well done with 
WebForms in version 3.17.2 of Gambas3 IDE but when we want to deploy 
these packages on the stable Debian server (11 Bullseye) we always 
run into that these recent improvements are not available because the 
package in this case is version 3.15.
I have seen that there are packages of more updated versions that are 
compiled with the libraries of the stable version i.e. Backports, 
would it be possible to have a gambas 3.17.2 in debian version 11?

Bug#996464: ITP: atomic-data-rust -- graph database server to share Atomic Data on the web

0.32.0+test draft 1 needs embedding 99 crates (83 missing, 1 broken, 14 
outdated, 1 ahead); builds in ~25 minutes; runs but needs to point to external 
web assets until those are packaged

Wohoo: Less than 100 crates are now missing!

Main task now is to package companion npm project Atomic Data Browser,
and to continue packaging of remaining missing Rust crates.

Here's how you can help:

As user running Debian, you can test this draft package: Either build it
yourself from source or tell (by posting to this bugreport) if you
prefer testing the binary that I've built - then I will share that.

As developer (but no need to be official member of Debian!), you can
join the Debian Rust team and help package these missing crates: 
https://salsa.debian.org/debian/atomic-data-rust/-/blob/debian/latest/debian/TODO


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1009104: GTK4 support

2022-06-15 Thread دانیال بهزادی

Any news on this? Without NetworkManager-fortisslvpn 1.4.0 upstream, 
network-manager-fortisslvpn-gnome is completely unusable in Debian.

Danial Behzadi

Bug#1008973: linux-image-amd64: Very slow wireless with MEDIATEK 7961

2022-06-15 Thread Julien Negros


Hello !

I tried this one also 
https://packages.debian.org/sid/linux-image-5.17.0-3-amd64-unsigned, 
same issue.
I saw that 5.18 was available, so I tried 
https://packages.debian.org/sid/linux-image-5.18.0-1-amd64, it's better 
but we're still far from 5.15...


Le 20/04/2022 à 14:28, Julien Negros a écrit :

Hi Vincent,

Not sure I installed the right one 
(https://packages.debian.org/sid/linux-image-5.17.0-1-amd64-unsigned) 
but I couldn't find another.


Same issue for me, I even fell like it's worse :/

Le 19/04/2022 à 15:53, Vincent Blut a écrit :

Control: tags -1 moreinfo

Hi,

Le 2022-04-05 14:39, Xavier Chantry a écrit :

Package: linux-image-amd64
Version: 5.10.84-1
Severity: important
X-Debbugs-Cc: chantry.xav...@gmail.com

Dear Maintainer,

We have a problem with MEDIATEK 7961 wireless on Levono P14s with AMD
Ryzen.

With 5.10 kernel on debian stable the wireless just does not work, so we
installed kernel 5.16 from testing.

With kernel 5.16 the wireless is so slow that it's unusable, each
internet query takes several seconds. A simple ping to google.com varies
from 100ms to 3000ms.

With kernel 5.17 it's slighly better but the ping still goes up to
600ms.

With kernel 5.15 however, it works quite good, Internet is very usable,
ping varies from 3ms to 30ms.
(on the same network, the P14s with Intel wireless does better and is
always under 10ms).

It looks like big changes were made to the mt7921e driver in 5.16
according to Phoronix :
The Mediatek MT7921 WiFi driver has added support for 6GHz WiFi, active
state power management (ASPM), and other improvements.

And it looks like this caused a big regression with MEDIATEK 7961.

Besides the network performance problem on 5.16, suspend/resume is also
broken, while it works perfectly on 5.15.


Le 2022-04-06 10:19, Christoph Martin a écrit :

I have the same Problem with an P14s and Mediathek 7921e.
There is even about 30% package loss.

Christoph

Am 05.04.22 um 14:39 schrieb Xavier Chantry:


With kernel 5.16 the wireless is so slow that it's unusable, each
internet query takes several seconds. A simple ping to google.com 
varies

from 100ms to 3000ms.

With kernel 5.17 it's slighly better but the ping still goes up to
600ms.


Le 2022-04-15 14:19, Julien Negros a écrit :

Hi,

Same issue here, switching to linux-image-5.15.0-0.bpo.3-amd64 did the
trick. Hope the next kernel version fixes this problem !

Cheers
--
Julien Négros
Linux 5.17.3 (uploaded to unstable earlier today) includes a lot of 
fixes for
Mediatek WLAN devices. Could you please check if that kernel fixes the 
slowness

you are seeing?

Cheers,
Vincent




--
Julien Négros

Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade

2022-06-15 Thread Michael Tokarev


Control: tag -1 + moreinfo

On Tue, 7 Jun 2022 16:25:47 -0400 Jeremy Bicha  
wrote:

Control: reassign -1 src:samba 2:4.16.0+dfsg-6
Control: affects -1 src:gvfs
Control: tags -1 +patch
Control: severity -1 important


Jeremy, you're adding the "patch" tag here, please tell me which change/patch is
supposed to fix the issue.

Thanks,

/mjt


The Debian samba maintainers did not have a chance to see your bug
report since this bug is recorded as affecting gvfs not samba. Let me
try to fix that up for you now.

Bug#1012501: rust-sct: please upgrade to v0.7