Bug#1023086: RFS: libquazip1-qt5/1.3-1 [ITP] -- Qt/C++ wrapper over minizip - Version 1 (Qt5)

[Ben Westover]

Package: sponsorship-requests
Severity: wishlist
Control: block 1023083 by -1

Dear mentors,

I am looking for a sponsor for my package "libquazip1-qt5":

  * Package name : libquazip1-qt5
Version  : 1.3-1
Upstream contact : Sergey A. Tachenov 
  * URL  : https://github.com/stachenov/quazip
  * License  : zlib, LGPL-2.1+ with static linking exception
  * Vcs  : https://salsa.debian.org/BenTheTechGuy/libquazip1-qt5
Section  : libs

The source builds the following binary packages:

   libquazip1-qt5-1 - Qt/C++ wrapper over minizip - Version 1 (Qt5)
   libquazip1-qt5-dev - Qt/C++ wrapper over minizip - Version 1 (Qt5) -
development files
   libquazip1-qt5-doc - Qt/C++ wrapper over minizip - Version 1 (Qt5) -
documentation

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

   https://mentors.debian.net/package/libquazip1-qt5/

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

   dget -x
https://mentors.debian.net/debian/pool/main/libq/libquazip1-qt5/libquazip1-qt5_1.3-1.dsc

Changes for the initial release:

  libquazip1-qt5 (1.3-1) unstable; urgency=medium
  .
* Initial Package (Closes: #1023083)

Regards,
--
Ben Westover


OpenPGP_signature
Description: PGP signature

Bug#1019270: cups-browsed: Query to /proc/sys/net/ipv6/conf/all/disable_ipv6 blocked by AppArmor, spamming syslog

[Boyuan Yang]

Control: tags -1 +patch
X-Debbugs-CC: alteh...@debian.org till.kamppe...@gmail.com

Dear Debian cups-filters maintainers,

On Tue, 06 Sep 2022 13:08:34 -0400 Boyuan Yang  wrote:
> Package: cups-browsed
> Version: 1.28.16-1
> Severity: normal
> 
> Dear Debian cups-filters packagers,
> 
> On my current Debian/Sid system (as of Sep 2022), the syslog keeps
printing
> the following messages:
> 
> kernel: audit: type=1400 audit(1662483939.030:193): apparmor="DENIED"
> operation="open" profile="/usr/sbin/cups-browsed"
> name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=3336 comm="cups-
browsed"
> requested_mask="r" denied_mask="r" fsuid=0 ouid=0
> 
> kernel: audit: type=1400 audit(1662483939.030:194): apparmor="DENIED"
> operation="open" profile="/usr/sbin/cups-browsed"
> name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=3336 comm="cups-
browsed"
> requested_mask="r" denied_mask="r" fsuid=0 ouid=0
> 
> audit[3336]: AVC apparmor="DENIED" operation="open"
profile="/usr/sbin/cups-
> browsed" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=3336
> comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
> 
> audit[3336]: AVC apparmor="DENIED" operation="open"
profile="/usr/sbin/cups-
> browsed" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=3336
> comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
> 
> 
> 
> These logs keeps spam my syslog. Please consider looking into it and
adjust
> AppArmor profile or cups-browsed program accordingly.

Since cups-browsed only needs to read
/proc/sys/net/ipv6/conf/all/disable_ipv6 to determine whether ipv6 is
disabled, I believe this request should be allowed by AppArmor.

As a result, I am attaching the following one-liner patch (see attachment).
Please consider applying it to avoid spamming syslog journal.



--- a/debian/apparmor/usr.sbin.cups-browsed
+++ b/debian/apparmor/usr.sbin.cups-browsed
@@ -17,6 +17,9 @@
   /var/log/cups/* rw,
   /tmp/** rw,
 
+  # Allow reading system ipv6 status
+  /proc/sys/net/ipv6/conf/all/disable_ipv6 r,
+
   # Courtesy to the Debian Edu team...
   /etc/cups/cups-browsed-debian-edu.conf r,



It would be really benificial if this fix could enter upcoming Debian 12.
Please let me know if you have any questions. Thanks!

Best Regards,
Boyuan Yang
From c257243882c2f6ab3ceaea7ec99a462f53fb0e1c Mon Sep 17 00:00:00 2001
From: Boyuan Yang 
Date: Sun, 30 Oct 2022 00:50:55 -0400
Subject: [PATCH] debian/apparmor/: Allow reading disable_ipv6 file under /proc

Otherwise syslog is spammed by repeated AppArmor denial:

apparmor="DENIED" operation="open" profile="/usr/sbin/cups-browsed"
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=61278
comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

This patch would Closes: #1019270.
---
 debian/apparmor/usr.sbin.cups-browsed | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/apparmor/usr.sbin.cups-browsed b/debian/apparmor/usr.sbin.cups-browsed
index 9c2dbff..cab1cd0 100644
--- a/debian/apparmor/usr.sbin.cups-browsed
+++ b/debian/apparmor/usr.sbin.cups-browsed
@@ -17,6 +17,9 @@
   /var/log/cups/* rw,
   /tmp/** rw,
 
+  # Allow reading system ipv6 status
+  /proc/sys/net/ipv6/conf/all/disable_ipv6 r,
+
   # Courtesy to the Debian Edu team...
   /etc/cups/cups-browsed-debian-edu.conf r,
 
-- 
2.37.2



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

Bug#1023083: ITP: libquazip1-qt5 -- Qt/C++ wrapper over minizip - Version 1 (Qt5)

[Nilesh Patra]

On 10/30/22 09:38, Ben Westover wrote:

Hello Nilesh,
You're replying to an old message by Filippo; I'm not *trying* to do
anything. I have already explained to Filippo that this is not the
correct way to do that.


Had you simply linked the bug report/alioth-list mails in your original ITP, 
it'd have prevented
this admittedly un-necessary correspondence. It was not clear at all in the 
original
ITP bug as to what the entire situation is, but I understand now.

Thanks for working on it!

--
Best,
Nilesh

Bug#1023085: fails to load on Wireless-AC 9260

[Ash Joubert]

Package: firmware-iwlwifi
Version: 20220913-1
Severity: important
X-Debbugs-Cc: a...@transient.nz

Dear Maintainer,

firmware-iwlwifi 20220913-1 fails to load on Intel Corporation Wireless-AC 9260
(rev 29), breaking network connectivity. Downgrading to firmware-iwlwifi
20210818-1, running "update-initramfs -u", and rebooting restores network
connectivity. Relevant log entries attached.

Kind regards,
Ash.


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

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

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.142

-- no debconf information
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: enabling device ( -> 
0002)
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: firmware: direct-loading 
firmware iwlwifi-9260-th-b0-jf-b0-46.ucode
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 0
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 1
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 2
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 3
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 4
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 6
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 8
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 9
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
10
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
11
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
15
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
16
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
18
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
19
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
20
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
21
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
28
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
Oct 30 16:15:00 ripley kernel: firmware_class: See 
https://wiki.debian.org/Firmware for information about missing firmware
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: loaded firmware version 
46.9d0122c0.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: Detected Intel(R) 
Wireless-AC 9260 160MHz, REV=0x321
Oct 30 16:15:01 ripley kernel: [ cut here ]
Oct 30 16:15:01 ripley kernel: Timeout waiting for hardware access 
(CSR_GP_CNTRL 0x)
Oct 30 16:15:01 ripley kernel: WARNING: CPU: 7 PID: 781 at 
drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2128 
__iwl_trans_pcie_grab_nic_access+0x1ef/0x220 [iwlwifi]
Oct 30 16:15:01 ripley kernel: Modules linked in: iwlmvm(+) ipt_REJECT 
nf_reject_ipv4 mac80211 xt_tcpudp libarc4 xt_conntrack nf_conntrack qrtr 
nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter>
Oct 30 16:15:01 ripley kernel:  jbd2 btrfs blake2b_generic zstd_compress 
dm_crypt dm_mod efivarfs raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq lib>
Oct 30 16:15:01 ripley kernel: CPU: 7 PID: 781 Comm: modprobe Not tainted 
6.0.0-2-amd64 #1  Debian 6.0.5-1
Oct 30 16:15:01 ripley kernel: Hardware name: System manufacturer System 
Product Name/H110I-PLUS, BIOS 4212 07/24/2019
Oct 30 16:15:01 ripley kernel: RIP: 
0010:__iwl_trans_pcie_grab_nic_access+0x1ef/0x220 [iwlwifi]
Oct 30 16:15:01 ripley kernel: Code: 48 89 df e8 a3 db fe ff 4c 89 f7 e8 8b 95 
0c df e9 e3 fe ff ff 89 c6 48 c7 c7 b0 26 34 c1 c6 05 e5 57 03 00 01 e8 3b 20 
07 df <0f> 0b e9 01 ff ff ff 48>
Oct 30 16:15:01 ripley kernel: RSP: 0018:ab5240f6bb60 EFLAGS: 00010282
Oct 30 16:15:01 ripley kernel: RAX:  RBX: 8a2d8b928028 RCX: 

Oct 30 16:15:01 ripley kernel: RDX: 0202 RSI: a0b7ed12 RDI: 

Oct 30 16:15:01 ripley kernel: RBP:  R08:  R09: 
ab5240f6b9e8
Oct 30 16:15:01 ripley kernel: R10: 0003 R11: a12d2128 R12: 
0001
Oct 30 16:15:01 ripley kernel: R13:  R14: 8a2d8b92a974 R15: 
0011
Oct 30 16:15:01 ripley kernel: FS:  7fbf50890480() 

Bug#1023083: ITP: libquazip1-qt5 -- Qt/C++ wrapper over minizip - Version 1 (Qt5)

[Ben Westover]

Hello Nilesh,

On 10/29/22 11:39 PM, Nilesh Patra wrote:
> On Sun, Oct 30, 2022 at 03:12:18AM +, Ben Westover wrote:
>> On 10/29/22 1:20 PM, Filippo Rusconi wrote:
>>> On Tue, Sep 13, 2022 at 03:40:13PM +, Ben Westover wrote:
 On 9/13/22 8:28 AM, Filippo Rusconi wrote:
>> I'd support any attempt to move the current libquazip[1] away
>> from Debian Med team where it is just by chance since it was a
>> dependency of some of our packages.  It does not make any sense to
>> maintain it inside the Debian Med team and I would love to hand it
>> over.  All maintainers except me do not respond to pings any more
>> and thus can be droped from the list of Uploaders.
>
> I understand that, let's take it away from Debian Med and put it in 
> Debian at
> large. Ben, if you would do the update, then I'd go over it and upload 
> it. That
> would be very good.
>
> If you want to take it out of debian-med team, the right way is to * ask * the
> med-team to transfer it somewhere else. What you are trying to do here is 
> considered
> as a hostile takeover.

You're replying to an old message by Filippo; I'm not *trying* to do
anything. I have already explained to Filippo that this is not the
correct way to do that.

 As stated above, the existing QuaZip *0.9* package (libquazip) and my
 new QuaZip *1.3* package (libquazip1-qt6) are unrelated. While they are
 both QuaZip packages, they are separate since QuaZip 0.x and 1.x are
 supposed to coexist, much like Qt5 and Qt6. The orphaning of libquazip
 is unrelated to my new libquazip1-qt6 being uploaded. My new package is
 outside of any team.
 The correct procedure here is to orphan libquazip, and anyone who is
 interested can adopt it.
>
> Why should the package be orphaned?

The actual maintainers have said that they wish it to be. Read through
the threads [1] and [2] and see the message [3].

 Again, my new package libquazip1-qt6 is not
 related to the existing libquazip package or the Med Team.
>
> There are already some changes committed to git for version 1.1 in the med 
> team
> package. If we happened to miss seeing this ITP, we might have ended up 
> stepping
> on your toes.

Again, the Med Team has asked me to create a new package instead of
attempting to use their WIP 1.1 code. 0.x is supposed to be pacakged
separately from 1.x.

Please read the all messages of the last bug at [3] for full context.
Also FYI, libquazip1-qt6 already exists; we've already gone through that
whole thing. This is just an otherwise identical package for Qt5.

Thanks,
--
Ben Westover

[1]
https://alioth-lists.debian.net/pipermail/debian-med-packaging/2022-August/102963.html
[2]
https://alioth-lists.debian.net/pipermail/debian-med-packaging/2022-September/103264.html
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019507#42
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019507


OpenPGP_signature
Description: PGP signature

Bug#1013211: problem is gone

[Douglas Silva]

I can no longer reproduce this. Currently running Ubuntu 22.10 with kernel 
5.19.0-23-generic. C-states enabled in the BIOS.

Bug#1023084: apt-listchanges: Unable to retrieve changelog for package linux-headers-amd64; 'apt-get changelog' failed with: E: Version '6.0.5+1' for 'linux-headers-amd64' was not found

[Paul Wise]

Package: apt-listchanges
Version: 3.24
Severity: normal
Usertags: version

I noticed that when I upgrade the linux-headers-amd64 metapackage,
which is built from the linux-signed-amd64 source package, then
apt-listchanges is not able to retrieve the changelog:

   apt-listchanges: Unable to retrieve changelog for package 
linux-headers-amd64; 'apt-get changelog' failed with: E: Version '6.0.5+1' for 
'linux-headers-amd64' was not found

It looks like it is passing the source version with the binary name
instead of the binary version with the binary name.

   $ apt-cache showsrc linux-headers-amd64 | grep ^Version
   Version: 6.0.3+1
   Version: 6.0.5+1
   
   $ apt-cache show linux-headers-amd64 | grep ^Version
   Version: 6.0.5-1
   Version: 6.0.3-1
   
   $ apt-get changelog linux-headers-amd64=6.0.5+1 | sponge | head -n2 
   E: Version '6.0.5+1' for 'linux-headers-amd64' was not found
   E: No packages found
   
   $ apt-get changelog linux-headers-amd64=6.0.5-1 | sponge | head -n2 
   Get:1 store: linux-signed-amd64 6.0.5+1 Changelog
   linux (6.0.5-1) unstable; urgency=medium

-- Package-specific info:
==> /etc/apt/listchanges.conf <==
[apt]
frontend=pager
email_address=root
confirm=1
save_seen=/var/lib/apt/listchanges.db
which=both
no_network=false
email_format=text
headers=false
reverse=false

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt-listchanges depends on:
ii  apt2.5.3+b1
ii  debconf [debconf-2.0]  1.5.79
ii  python33.10.6-1
ii  python3-apt2.3.0+nmu1
ii  python3-debconf1.5.79
ii  sensible-utils 0.0.17
ii  ucf3.0043

apt-listchanges recommends no packages.

Versions of packages apt-listchanges suggests:
ii  chromium [www-browser] 107.0.5304.87-1
ii  dillo [www-browser]3.0.5-7+b1
ii  elinks [www-browser]   0.13.2-1+b4
ii  exim4-daemon-light [mail-transport-agent]  4.96-7
ii  firefox [www-browser]  106.0-1
ii  firefox-esr [www-browser]  102.4.0esr-1
ii  gnome-console [x-terminal-emulator]43.0-2
ii  gnome-terminal [x-terminal-emulator]   3.46.2-1
ii  links [www-browser]2.27-1+b1
ii  lynx [www-browser] 2.9.0dev.10-1+b1
ii  netsurf-gtk [www-browser]  3.10-1+b3
ii  python3-gi 3.42.2-2
ii  w3m [www-browser]  0.5.3+git20220429-1+b1
ii  xterm [x-terminal-emulator]374-1

-- debconf information:
* apt-listchanges/email-address: root
* apt-listchanges/email-format: text
* apt-listchanges/save-seen: true
* apt-listchanges/frontend: pager
* apt-listchanges/which: both
* apt-listchanges/reverse: false
* apt-listchanges/headers: false
* apt-listchanges/no-network: false
* apt-listchanges/confirm: true

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1023083: ITP: libquazip1-qt5 -- Qt/C++ wrapper over minizip - Version 1 (Qt5)

[Nilesh Patra]

On Sun, Oct 30, 2022 at 03:12:18AM +, Ben Westover wrote:
> On 10/29/22 1:20 PM, Filippo Rusconi wrote:
> > On Tue, Sep 13, 2022 at 03:40:13PM +, Ben Westover wrote:
> >> On 9/13/22 8:28 AM, Filippo Rusconi wrote:
>  I'd support any attempt to move the current libquazip[1] away
>  from Debian Med team where it is just by chance since it was a
>  dependency of some of our packages.  It does not make any sense to
>  maintain it inside the Debian Med team and I would love to hand it
>  over.  All maintainers except me do not respond to pings any more
>  and thus can be droped from the list of Uploaders.
> >>>
> >>> I understand that, let's take it away from Debian Med and put it in 
> >>> Debian at
> >>> large. Ben, if you would do the update, then I'd go over it and upload 
> >>> it. That
> >>> would be very good.

If you want to take it out of debian-med team, the right way is to * ask * the
med-team to transfer it somewhere else. What you are trying to do here is 
considered
as a hostile takeover.

> >> As stated above, the existing QuaZip *0.9* package (libquazip) and my
> >> new QuaZip *1.3* package (libquazip1-qt6) are unrelated. While they are
> >> both QuaZip packages, they are separate since QuaZip 0.x and 1.x are
> >> supposed to coexist, much like Qt5 and Qt6. The orphaning of libquazip
> >> is unrelated to my new libquazip1-qt6 being uploaded. My new package is
> >> outside of any team.
> >> The correct procedure here is to orphan libquazip, and anyone who is
> >> interested can adopt it.

Why should the package be orphaned?

> >> Again, my new package libquazip1-qt6 is not
> >> related to the existing libquazip package or the Med Team.

There are already some changes committed to git for version 1.1 in the med team
package. If we happened to miss seeing this ITP, we might have ended up stepping
on your toes.

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1023004: [Pkg-utopia-maintainers] Bug#1023004: network-manager: does not attempt reconnect after a temporary wifi failure

[Vincent Lefevre]

On 2022-10-29 10:17:09 +0200, Michael Biebl wrote:
> Am 29.10.22 um 01:26 schrieb Vincent Lefevre:
> > Package: network-manager
> > Version: 1.40.2-1
> > Severity: normal
> > 
> > In case of temporary wifi failure, network-manager doesn't try to
> > reconnect. Here are the logs:
> > 
> > Oct 29 00:58:06 zira wpa_supplicant[851]: wlp61s0: CTRL-EVENT-BEACON-LOSS

Note that I get CTRL-EVENT-BEACON-LOSS quite often. In general,
NetworkManager can reconnect, but not always. I could reproduce
the issue:

Oct 30 04:08:02 zira wpa_supplicant[1765023]: wlp61s0: CTRL-EVENT-BEACON-LOSS
Oct 30 04:08:02 zira wpa_supplicant[1765023]: wlp61s0: CTRL-EVENT-BEACON-LOSS
Oct 30 04:08:02 zira wpa_supplicant[1765023]: wlp61s0: CTRL-EVENT-BEACON-LOSS
Oct 30 04:08:02 zira wpa_supplicant[1765023]: wlp61s0: CTRL-EVENT-BEACON-LOSS
Oct 30 04:08:03 zira dhclient[1765928]: DHCPREQUEST for 192.168.43.172 on 
wlp61s0 to 255.255.255.255 port 67
Oct 30 04:08:03 zira wpa_supplicant[1765023]: wlp61s0: CTRL-EVENT-DISCONNECTED 
bssid=02:03:aa:bd:c4:e0 reason=4 locally_generated=1
Oct 30 04:08:03 zira wpa_supplicant[1765023]: wlp61s0: WPA: 4-Way Handshake 
failed - pre-shared key may be incorrect
Oct 30 04:08:03 zira wpa_supplicant[1765023]: wlp61s0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Cosmo WiFi_3428" auth_failures=1 
duration=10 reason=WRONG_KEY
Oct 30 04:08:03 zira wpa_supplicant[1765023]: wlp61s0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
Oct 30 04:08:03 zira NetworkManager[956]:   [1667099283.2631] device 
(wlp61s0): supplicant interface state: 4way_handshake -> disconnected
Oct 30 04:08:03 zira NetworkManager[956]:   [1667099283.2632] device 
(p2p-dev-wlp61s0): supplicant management interface state: 4way_handshake -> 
disconnected
Oct 30 04:08:03 zira NetworkManager[956]:   [1667099283.3630] device 
(wlp61s0): supplicant interface state: disconnected -> scanning
Oct 30 04:08:03 zira NetworkManager[956]:   [1667099283.3631] device 
(p2p-dev-wlp61s0): supplicant management interface state: disconnected -> 
scanning
Oct 30 04:08:11 zira dhclient[1765928]: DHCPDISCOVER on wlp61s0 to 
255.255.255.255 port 67 interval 3
Oct 30 04:08:13 zira NetworkManager[956]:   [1667099293.9252] device 
(wlp61s0): link timed out.
Oct 30 04:08:13 zira NetworkManager[956]:   [1667099293.9259] device 
(wlp61s0): state change: activated -> failed (reason 'supplicant-timeout', 
sys-iface-state: 'managed')
Oct 30 04:08:13 zira NetworkManager[956]:   [1667099293.9265] manager: 
NetworkManager state is now DISCONNECTED
Oct 30 04:08:13 zira NetworkManager[956]:   [1667099293.9274] device 
(wlp61s0): Activation: failed for connection 'cosmo'

> Can you try with iwd as well?

I've tried, following https://wiki.debian.org/NetworkManager/iwd
but I get

Error: Connection activation failed: (7) Secrets were required, but not 
provided.

when I want to connect with nmcli.

In any case, NM with iwd would have a similar issue as said on the wiki:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/628

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

Bug#1023083: ITP: libquazip1-qt5 -- Qt/C++ wrapper over minizip - Version 1 (Qt5)

[Ben Westover]

Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org
Owner: Ben Westover 
Severity: wishlist

* Package name: libquazip1-qt5
  Version : 1.3
  Upstream Author : Sergey A. Tachenov 
* URL : https://github.com/stachenov/quazip
* License : zlib, LGPL-2.1 with static linking exception
  Programming Lang: C, C++
  Description : Qt/C++ wrapper over minizip - Version 1 (Qt5)

QuaZip is the C++ wrapper for Gilles Vollant's ZIP/UNZIP package (AKA
Minizip) using Trolltech's Qt library.

While quazip is already packaged in Debian, it's version 0.9.1. The
author of quazip has stated that versions 1.x are meant to be used
alongside 0.x and not as an upgrade/replacement, like how Qt5 is still
packaged alongside Qt6.
This package is for versions 1.x of quazip built for Qt5. I'm packaging
it at the request of Filippo Rusconi (context below). I do not plan to
package this inside a team, unless one expresses interest. I will need a
sponsor at first as I'm only a DM.

Thanks,
--
Ben Westover

On 10/29/22 1:20 PM, Filippo Rusconi wrote:
> Greetings, Ben,
>
> On Tue, Sep 13, 2022 at 03:40:13PM +, Ben Westover wrote:
>> Hello,
>>
>> On 9/13/22 8:28 AM, Filippo Rusconi wrote:
 I'd support any attempt to move the current libquazip[1] away
 from Debian Med team where it is just by chance since it was a
 dependency of some of our packages.  It does not make any sense to
 maintain it inside the Debian Med team and I would love to hand it
 over.  All maintainers except me do not respond to pings any more
 and thus can be droped from the list of Uploaders.
>>>
>>> I understand that, let's take it away from Debian Med and put it in Debian 
>>> at
>>> large. Ben, if you would do the update, then I'd go over it and upload it. 
>>> That
>>> would be very good.
>>
>> As stated above, the existing QuaZip *0.9* package (libquazip) and my
>> new QuaZip *1.3* package (libquazip1-qt6) are unrelated. While they are
>> both QuaZip packages, they are separate since QuaZip 0.x and 1.x are
>> supposed to coexist, much like Qt5 and Qt6. The orphaning of libquazip
>> is unrelated to my new libquazip1-qt6 being uploaded. My new package is
>> outside of any team.
>>
>> The correct procedure here is to orphan libquazip, and anyone who is
>> interested can adopt it. Again, my new package libquazip1-qt6 is not
>> related to the existing libquazip package or the Med Team.
>
> Yes, certainly. However, we have to support libquazip1.3 as a Qt5- and 
> Qt6-built
> library. I would suggest that we make this package (Ben's) or the other 
> (Debian
> med's) support both Qt libraries' versions.
>
> This would be pretty similar to what I have proposed for QCustomPlot ([0] any
> comment about it, not a single comment about my previous emails, by the way).
>
> Ben, would you do this or would you accept pull requests ?
>
> Sincerely,
> Filippo
>
> 0. https://salsa.debian.org/science-team/qcustomplot/-/tree/qt5-and-qt6


OpenPGP_signature
Description: PGP signature

Bug#1023082: /usr/bin/kicad: Core applications are not usable

[Mithat Konar]

Package: kicad
Version: 6.0.9+dfsg-1
Severity: important
File: /usr/bin/kicad
X-Debbugs-Cc: mkonar.do...@gmail.com

Dear Maintainer,

The following KiCad applications fail to launch when attempting to do so from
the main GUI wrapper:

- Schematic Editor
- Symbol Editor
- PCB Editor
- Footprint Editor
- Gerber Viewer
- Drawing Sheet Editor

eeschema and pcbnew also fail when invoked at the command line. I have not
tried the others.

All the launch failures are accompanied by a dialog indicating the following
error: "Failed to load shared library '/usr/bin/': /lib/x86_64-linux-
gnu/libwx_gtk3u_gl-3.2.so.0: undefined symbol: eglCreatePlatformWindowSurface"

My installation using the upstream flatpak does not have this issue.


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

Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
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 kicad depends on:
ii  libc62.35-4
ii  libcairo21.16.0-6
ii  libcurl4 7.86.0-1
ii  libegl1  1.5.0-1
ii  libgcc-s112.2.0-7
ii  libgl1   1.5.0-1
ii  libglib2.0-0 2.74.0-3
ii  libglu1-mesa [libglu1]   9.0.2-1.1
ii  libgtk-3-0   3.24.34-3
ii  libngspice0  37+ds-1
ii  libocct-data-exchange-7.67.6.3+dfsg1-5
ii  libocct-foundation-7.6   7.6.3+dfsg1-5
ii  libocct-modeling-algorithms-7.6  7.6.3+dfsg1-5
ii  libocct-modeling-data-7.67.6.3+dfsg1-5
ii  libocct-ocaf-7.6 7.6.3+dfsg1-5
ii  libpixman-1-00.40.0-1
ii  libpython3.103.10.8-1
ii  libstdc++6   12.2.0-7
ii  libwxbase3.2-0   3.2.1+dfsg-1
ii  libwxgtk3.2-03.2.1+dfsg-1
ii  python3  3.10.6-1
ii  python3-wxgtk4.0 4.2.0+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4.1

Versions of packages kicad recommends:
ii  kicad-demos  6.0.9+dfsg-1
ii  kicad-libraries  6.0.9+dfsg-1
ii  xsltproc 1.1.35-1

Versions of packages kicad suggests:
ii  extra-xdg-menus  1.0-6
pn  kicad-doc-ca | kicad-doc-de | kicad-doc-en | kicad-doc-es | kicad-d  
pn  kicad-packages3d 

-- no debconf information

Bug#1021985: sddm login screen changed to white and does not display the breeze theme any more

[Chris Nospam]

This bug was silently fixed in sddm-theme-breeze 4:5.26.0-2 .

Bug#1004955: Wish: switch to new version of soundmodem

[tony mancill]

On Fri, Feb 04, 2022 at 11:22:28AM +0100, Roland Schwarz wrote:
> Package: soundmodem
> Version: 0.20-6
> 
> Please consider switching to my forked version of soundmodem available at:
> 
> https://gitlab.com/packetradio/soundmodem
> 
> I addressed the following issues:
> 
> * dependency on legacy gtk2, -> moved to gtk3
> * missing systemd integration added
> * improved 96 FSK mode

Hello Roland,

Please excuse the long delay in responding.  I'm not a current
soundmodem user, but the updates in the fork sound useful.

Any concerns from you or anyone on the list making this fork the basis
for soundmodem.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#648185: reportbug: ftp.debian.org RM bugs should get X-Debbugs-CC: maintainer

[Paul Wise]

Hi Debian FTP team,

In Debian bug #648185 it was proposed to set affects src:$PACKAGE
and XCC $PACKAGE@packages.d.o for ftp.d.o removal bugs.

I would like to apply this to ftp.d.o override request bugs too and
also any future package related ftp.d.o bugs too.

This would help maintainers and people reading the bugs web pages find
out about the removal, override and other requests.

The reportbug maintainers usually require changes to pseudo-package
bugs to be approved by the teams owning those pseudo-packages.

Would the above changes be acceptable to you?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1017977: Fails to load intel/ibt-20-1-3.sfi

[Olaf Meeuwissen]

> Package: linux-image-5.18.0-4-amd64
> Severity: important
>
> The intel/ibt-20-1-3.sfi file loads fine on linux-image-5.18.0-3-amd64.
> Used that to report this bug as the failure to load leaves me without a
> working keyboard.  It's a bluetooth-only keyboard and it not working at
> all is why I've marked this important.

I just want to add that this is still an issue with 6.0.0-2.  Exact same
symptoms.  Keyboard is useless when booting after a poweroff.  Booting
into 5.18.0-3 restores keyboard usability.  A subsequent *reboot* to the
latest linux-image version, as opposed to a poweroff+boot, leaves the
keyboard in a usable state.

Hope this helps,
--
Olaf Meeuwissen

Bug#1023081: ITP: rocsolver -- ROCm library for numerical linear algebra

[Cordell Bloor]

Package: wnpp
Severity: wishlist
Owner: Cordell Bloor 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: rocsolver
  Version : 5.3.0
  Upstream Author : Advanced Micro Devices, Inc.
* URL : https://github.com/ROCmSoftwarePlatform/rocSOLVER
* License : BSD 2-Clause
  Programming Lang: C, C++, HIP
  Description : ROCm library for numerical linear algebra

 rocSOLVER is an implementation of LAPACK routines built on the AMD ROCm
 platform and optimized for discrete AMD GPUs.
 .
 rocSOLVER provides a C99 API that extends the rocBLAS interface. It
 includes LAPACK and LAPACK-like routines for triangular factorizations,
 orthogonal factorizations, linear-systems solvers, least-squares solvers,
 symmetric eigensolvers and singular value decomposition.

rocSOLVER is a dependency of a number of libraries for scientific
computing including Tensorflow, Tasmanian, and QMCPACK, as well as other
components of the ROCm platform such as hipBLAS and hipSOLVER.

This package is part of AMD's ROCm stack and will be maintained
under the Debian AI team umbrella.

Bug#1023080: lists.debian.org: Add a 'pkg-sourcehut' mailing list

[Ben Finney]

Package: lists.debian.org
Severity: wishlist
X-Debbugs-Cc: de...@laxalde.org

Howdy list masters,

This request is for the addition of a mailing list for the Debian SourceHut 
Packaging Team.

Name: pkg-sourcehut

  (The naming convention might dictate a different name, such as
  ‘debian-pkg-sourcehut’.)

Synopsis:
Debian packaging team for the SourceHut development forge

Description:
Discussion of Debian packages for installing the SourceHut
development forge on Debian.

This is the primary discussion forum for the Debian SourceHut
Packaging Team.

SourceHut is a development forge with many services to help
software projects; see https://sourcehut.org/. Ths Debian
SourceHut Packaging Team works to make packages to install
SourceHut to run on a Debian host.

Category: Development

Subscription policy: open

Post policy: open

Web Archive: yes

Bug#1023076: linux-headers-6.0.0-2-amd64: bluetooth crashes after returning from suspend

[Diederik de Haas]

Control: reassign -1 src:linux 6.0.3-1
Control: severity -1 important

On Sunday, 30 October 2022 00:50:25 CEST Gabriel Francisco wrote:
> Package: linux-headers-6.0.0-2-amd64
> Version: 6.0.3-1
> Severity: normal
> 
> With this kernel seems to crash bluetooth when returning from
> suspend. Few days ago my cursor froze, the computer rebooted and I
> couldn't find logs in /var/log/syslog.
> 
> I think it might be related to #1021905.

Indeed many similarities, but not exactly the same ...

> [24595.999699] general protection fault,
> ...
> [24595.999793]  ? bt_sock_wait_ready+0x128/0x1a0 [bluetooth]

These things are different. I increased severity because of GPF.

Before we look further, can you test 6.0.5-1 available in Unstable?


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

Bug#1020299: equinox-p2: wrong information in the manifest files

[Sudip Mukherjee]

Control: tags -1 patch
--

On Mon, Sep 19, 2022 at 03:58:29PM +0100, Sudip Mukherjee wrote:
> Source: equinox-p2
> Version: 4.21-1
> Severity: important
> X-Debbugs-Cc: sudipm.mukher...@gmail.com
> 
> Dear Maintainer,
> 
> The manifest file of equinox-p2 mentions that it needs bouncycastle 
> version="1.65.0" but in Debian we have bouncycastle 1.71 and as a result any 
> eclipse based application is not able to use equinox-p2 and it gives the 
> errors like:
> 
> org.eclipse.equinox.p2.engine [130]
>   Unresolved requirement: Import-Package: org.bouncycastle.openpgp; 
> version="1.65.0"
> 
> org.eclipse.equinox.p2.core [131]
>   Unresolved requirement: Import-Package: org.bouncycastle.bcpg; 
> version="1.65.0"

The attached patch is the minimum required to unblock eclipse-tracecompass.
But Emmanuel Bourg did not agree so I am not doing an upload but keeping
the patch here for record.
Ref: https://lists.debian.org/debian-java/2022/09/msg2.html

-- 
Regards
Sudip
diff -Nru equinox-p2-4.21/debian/changelog equinox-p2-4.21/debian/changelog
--- equinox-p2-4.21/debian/changelog	2021-10-18 15:14:21.0 +0100
+++ equinox-p2-4.21/debian/changelog	2022-09-07 21:02:34.0 +0100
@@ -1,3 +1,10 @@
+equinox-p2 (4.21-1.1) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Fix Manifest. (Closes: #1020299)
+
+ -- Sudip Mukherjee   Wed, 07 Sep 2022 21:02:34 +0100
+
 equinox-p2 (4.21-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru equinox-p2-4.21/debian/patches/manifest.patch equinox-p2-4.21/debian/patches/manifest.patch
--- equinox-p2-4.21/debian/patches/manifest.patch	1970-01-01 01:00:00.0 +0100
+++ equinox-p2-4.21/debian/patches/manifest.patch	2022-09-07 21:02:34.0 +0100
@@ -0,0 +1,73 @@
+Description: Fix Manifest
+
+Author: Sudip Mukherjee 
+
+---
+
+Bug-Debian: https://bugs.debian.org/1020299
+Forwarded: no
+
+--- equinox-p2-4.21.orig/bundles/org.eclipse.equinox.p2.artifact.repository/META-INF/MANIFEST.MF
 equinox-p2-4.21/bundles/org.eclipse.equinox.p2.artifact.repository/META-INF/MANIFEST.MF
+@@ -38,14 +38,14 @@ Require-Bundle: org.eclipse.equinox.comm
+  org.eclipse.equinox.p2.metadata,
+  org.tukaani.xz;bundle-version="1.3.0"
+ Import-Package: javax.xml.parsers,
+- org.bouncycastle.bcpg;version="1.65.0",
+- org.bouncycastle.jce.provider;version="1.65.1",
+- org.bouncycastle.openpgp;version="1.65.0",
+- org.bouncycastle.openpgp.bc;version="1.65.0",
+- org.bouncycastle.openpgp.jcajce;version="1.65.0",
+- org.bouncycastle.openpgp.operator;version="1.65.0",
+- org.bouncycastle.openpgp.operator.bc;version="1.65.0",
+- org.bouncycastle.openpgp.operator.jcajce;version="1.65.0",
++ org.bouncycastle.bcpg;version="1.71.0",
++ org.bouncycastle.jce.provider;version="1.71.0",
++ org.bouncycastle.openpgp;version="1.71.0",
++ org.bouncycastle.openpgp.bc;version="1.71.0",
++ org.bouncycastle.openpgp.jcajce;version="1.71.0",
++ org.bouncycastle.openpgp.operator;version="1.71.0",
++ org.bouncycastle.openpgp.operator.bc;version="1.71.0",
++ org.bouncycastle.openpgp.operator.jcajce;version="1.71.0",
+  org.eclipse.core.runtime.jobs,
+  org.eclipse.equinox.internal.p2.core.helpers,
+  org.eclipse.equinox.internal.p2.jarprocessor,
+--- equinox-p2-4.21.orig/bundles/org.eclipse.equinox.p2.core/META-INF/MANIFEST.MF
 equinox-p2-4.21/bundles/org.eclipse.equinox.p2.core/META-INF/MANIFEST.MF
+@@ -70,8 +70,8 @@ Require-Bundle: org.eclipse.equinox.comm
+ Bundle-RequiredExecutionEnvironment: JavaSE-11
+ Bundle-ActivationPolicy: lazy
+ Service-Component: OSGI-INF/eventBus.xml, OSGI-INF/agentProvider.xml
+-Import-Package: org.bouncycastle.bcpg;version="1.65.0",
+- org.bouncycastle.openpgp;version="1.65.0",
++Import-Package: org.bouncycastle.bcpg;version="1.71.0",
++ org.bouncycastle.openpgp;version="1.71.0",
+  org.eclipse.osgi.framework.eventmgr;version="1.2.0",
+  org.eclipse.osgi.framework.log;version="1.0.0",
+  org.eclipse.osgi.service.debug;version="1.0.0",
+--- equinox-p2-4.21.orig/bundles/org.eclipse.equinox.p2.engine/META-INF/MANIFEST.MF
 equinox-p2-4.21/bundles/org.eclipse.equinox.p2.engine/META-INF/MANIFEST.MF
+@@ -26,7 +26,7 @@ Bundle-RequiredExecutionEnvironment: Jav
+ Bundle-ActivationPolicy: lazy
+ Service-Component: OSGI-INF/profileRegistry.xml, OSGI-INF/engine.xml
+ Import-Package: javax.xml.parsers,
+- org.bouncycastle.openpgp;version="1.65.0",
++ org.bouncycastle.openpgp;version="1.71.0",
+  org.eclipse.core.internal.preferences,
+  org.eclipse.core.runtime.preferences,
+  org.eclipse.equinox.internal.p2.artifact.processors.pgp,
+--- equinox-p2-4.21.orig/bundles/org.eclipse.equinox.p2.ui/META-INF/MANIFEST.MF
 equinox-p2-4.21/bundles/org.eclipse.equinox.p2.ui/META-INF/MANIFEST.MF
+@@ -36,9 +36,9 @@ Require-Bundle: org.eclipse.ui;bundle-ve
+  org.eclipse.equinox.security.ui;bundle-version="[1.0.0,2.0.0)",
+  org.eclipse.e4.ui.dialogs;bundle-version="1.1.600"
+ Import-Package: javax.xml.parsers,
+- org.bouncycastle.bcpg;version="1.65.0",
+- 

Bug#995792: printing text files

[Thorsten Alteholz]

Hi everybody,

from my point of view it totally makes sense, when you install a printer 
driver to print files on braille printers, that this software does what 
it is supposed to do.


The problem seems to be that it was installed on a system without need 
for it. Wouldn't there be a better package than printer-driver-all-enforce 
to add a Recommends: for it?  Maybe Odyx can shed some light on it?


  Thorsten

Bug#1019488: bouncycastle: incomplete information in the manifest files

[Sudip Mukherjee]

Control: tags -1 patch
--

On Sat, Sep 10, 2022 at 01:09:06PM +0100, Sudip Mukherjee wrote:
> Source: bouncycastle
> Version: 1.71-1
> Severity: important
> X-Debbugs-Cc: sudipm.mukher...@gmail.com
> 
> Dear Maintainer,
> 
> The META-INF/MANIFEST.MF file of libbcpg-java contains only the following:
> 



> 
> Which is incomplete and does not contain all the other required information
> like Bundle-Version, Bundle-Name, Export-Package etc. And this lack of 
> information
> makes the package unusable when using a SimpleConfigurator based bundles.info 
> file.

The attached patch is the minimum required to unblock eclipse-tracecompass.
But Emmanuel Bourg did not agree so I am not doing an upload but keeping
the patch here for record.
Ref: https://lists.debian.org/debian-java/2022/09/msg2.html

-- 
Regards
Sudip
diff -Nru bouncycastle-1.71/debian/changelog bouncycastle-1.71/debian/changelog
--- bouncycastle-1.71/debian/changelog	2022-05-03 18:51:47.0 +0100
+++ bouncycastle-1.71/debian/changelog	2022-09-19 12:20:40.0 +0100
@@ -1,3 +1,10 @@
+bouncycastle (1.71-2) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Fix Manifest. (Closes: #1019488)
+
+ -- Sudip Mukherjee   Mon, 19 Sep 2022 12:20:40 +0100
+
 bouncycastle (1.71-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru bouncycastle-1.71/debian/patches/manifest.patch bouncycastle-1.71/debian/patches/manifest.patch
--- bouncycastle-1.71/debian/patches/manifest.patch	1970-01-01 01:00:00.0 +0100
+++ bouncycastle-1.71/debian/patches/manifest.patch	2022-09-19 12:20:40.0 +0100
@@ -0,0 +1,31 @@
+Description: Fix manifest
+
+Author: Sudip Mukherjee 
+
+---
+Bug-Debian: https://bugs.debian.org/1019488
+Forwarded: no
+
+--- bouncycastle-1.71.orig/ant/bc+-build.xml
 bouncycastle-1.71/ant/bc+-build.xml
+@@ -414,6 +414,10 @@
+ 
+ 
+ 
++
++
++
++
+ 
+ 
+ 
+@@ -882,6 +886,9 @@
+ 
+ 
+ 
++
++
++
+ 
+ 
+ 
diff -Nru bouncycastle-1.71/debian/patches/series bouncycastle-1.71/debian/patches/series
--- bouncycastle-1.71/debian/patches/series	2022-05-03 10:10:16.0 +0100
+++ bouncycastle-1.71/debian/patches/series	2022-09-19 12:20:40.0 +0100
@@ -1,3 +1,4 @@
 02_index.patch
 fix-encoding.patch
 backward-compatibility.patch
+manifest.patch

Bug#1020298: eclipse-platform-runtime: wrong information in the manifest files

[Sudip Mukherjee]

Control: tags -1 patch
--

On Mon, Sep 19, 2022 at 03:55:54PM +0100, Sudip Mukherjee wrote:
> Source: eclipse-platform-runtime
> Version: 4.19-1
> Severity: important
> X-Debbugs-Cc: sudipm.mukher...@gmail.com
> 
> Dear Maintainer,
> 
> eclipse-platform-runtime needs javax.annotation.PostConstruct and 
> javax.annotation.PreDestroy and the MANIFEST.MF file mentions:
> 
>  Import-Package: javax.annotation;version="1.3.5" and also mentions
>  javax.annotation;bundle-version="[1.3.5,2.0.0)" in Require-Bundle.

The attached patch is the minimum required to unblock eclipse-tracecompass.
But Emmanuel Bourg did not agree so I am not doing an upload but keeping
the patch here for record.
Ref: https://lists.debian.org/debian-java/2022/09/msg2.html

-- 
Regards
Sudip
diff -Nru eclipse-platform-runtime-4.19/debian/changelog eclipse-platform-runtime-4.19/debian/changelog
--- eclipse-platform-runtime-4.19/debian/changelog	2021-10-09 15:47:19.0 +0100
+++ eclipse-platform-runtime-4.19/debian/changelog	2022-05-27 23:58:33.0 +0100
@@ -1,3 +1,10 @@
+eclipse-platform-runtime (4.19-1.1) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Fix manifest information. (Closes: #1020298)
+
+ -- Sudip Mukherjee   Fri, 27 May 2022 23:58:33 +0100
+
 eclipse-platform-runtime (4.19-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru eclipse-platform-runtime-4.19/debian/patches/manifest.patch eclipse-platform-runtime-4.19/debian/patches/manifest.patch
--- eclipse-platform-runtime-4.19/debian/patches/manifest.patch	1970-01-01 01:00:00.0 +0100
+++ eclipse-platform-runtime-4.19/debian/patches/manifest.patch	2022-05-27 23:58:33.0 +0100
@@ -0,0 +1,47 @@
+Description: Fix Manifest
+
+Author: Sudip Mukherjee 
+
+---
+
+Bug-Debian: https://bugs.debian.org/1020298
+Forwarded: no
+
+--- eclipse-platform-runtime-4.19.orig/bundles/org.eclipse.e4.core.di.extensions.supplier/META-INF/MANIFEST.MF
 eclipse-platform-runtime-4.19/bundles/org.eclipse.e4.core.di.extensions.supplier/META-INF/MANIFEST.MF
+@@ -17,7 +17,7 @@ Import-Package: org.eclipse.core.runtime
+  org.osgi.service.component.annotations;version="1.3.0";resolution:=optional,
+  org.osgi.service.event;version="1.3.0",
+  org.osgi.service.log;version="1.3.0",
+- javax.annotation;version="1.3.5"
++ javax.annotation;version="[1.3,1.3.5]"
+ Service-Component: OSGI-INF/org.eclipse.e4.core.di.internal.extensions.OSGiObjectSupplier.xml,
+  OSGI-INF/org.eclipse.e4.core.di.internal.extensions.EventObjectSupplier.xml,
+  OSGI-INF/org.eclipse.e4.core.di.internal.extensions.PreferencesObjectSupplier.xml,
+--- eclipse-platform-runtime-4.19.orig/bundles/org.eclipse.e4.core.di/META-INF/MANIFEST.MF
 eclipse-platform-runtime-4.19/bundles/org.eclipse.e4.core.di/META-INF/MANIFEST.MF
+@@ -12,10 +12,10 @@ Export-Package: org.eclipse.e4.core.di;v
+  org.eclipse.e4.core.internal.di;x-friends:="org.eclipse.e4.core.contexts",
+  org.eclipse.e4.core.internal.di.osgi;x-internal:=true,
+  org.eclipse.e4.core.internal.di.shared;x-friends:="org.eclipse.e4.core.contexts,org.eclipse.e4.core.di.extensions.supplier"
+-Require-Bundle: org.eclipse.e4.core.di.annotations;bundle-version="[1.4.0,2.0.0)";visibility:=reexport,
+- javax.annotation;bundle-version="[1.3.5,2.0.0)"
++Require-Bundle: org.eclipse.e4.core.di.annotations;bundle-version="[1.4.0,2.0.0)";visibility:=reexport
+ Import-Package: javax.inject;version="1.0.0",
+  org.eclipse.osgi.framework.log;version="1.1.0",
+  org.osgi.framework;version="1.8.0",
+- org.osgi.util.tracker;version="1.5.1"
++ org.osgi.util.tracker;version="1.5.1",
++ javax.annotation;version="[1.3,1.3.5]"
+ Automatic-Module-Name: org.eclipse.e4.core.di
+--- eclipse-platform-runtime-4.19.orig/bundles/org.eclipse.e4.core.services/META-INF/MANIFEST.MF
 eclipse-platform-runtime-4.19/bundles/org.eclipse.e4.core.services/META-INF/MANIFEST.MF
+@@ -7,7 +7,7 @@ Bundle-Localization: plugin
+ Bundle-Version: 2.2.600.qualifier
+ Bundle-ActivationPolicy: lazy
+ Bundle-RequiredExecutionEnvironment: JavaSE-1.8
+-Import-Package: javax.annotation;version="1.3.5",
++Import-Package: javax.annotation;version="[1.3,1.3.5]",
+  javax.inject;version="1.0.0",
+  org.eclipse.osgi.service.debug;version="1.1.0",
+  org.eclipse.osgi.service.localization;version="1.1.0",
diff -Nru eclipse-platform-runtime-4.19/debian/patches/series eclipse-platform-runtime-4.19/debian/patches/series
--- eclipse-platform-runtime-4.19/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ eclipse-platform-runtime-4.19/debian/patches/series	2022-05-27 23:58:33.0 +0100
@@ -0,0 +1 @@
+manifest.patch

Bug#1023078: ITP: rocsparse -- ROCm library for sparse linear algebra

[Cordell Bloor]

Package: wnpp
Severity: wishlist
Owner: Cordell Bloor 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: rocsparse
  Version : 5.3.0
  Upstream Author : Advanced Micro Devices, Inc.
* URL : https://github.com/ROCmSoftwarePlatform/rocSPARSE
* License : Expat (MIT/X)
  Programming Lang: C, C++, HIP
  Description : ROCm library for sparse linear algebra

 rocSPARSE is a library that implements BLAS operations for sparse data
 structures. It is built on the AMD ROCm platform and optimized for
 discrete AMD GPUs.
 .
 rocSPARSE provides a C99 API containing sparse level 1, sparse level 2 and
 sparse level 3 BLAS functions, as well as general matrix multiplication
 between dense and sparse matricies (GEMMI), sparse preconditioner functions,
 sparse matrix format conversion functions, and sparse matrix reordering
 functions.
 .
 It supports a variety of sparse matrix formats, including coordinate list
 in either array of structure form (COO) or structure of array form (COO SOA),
 compressed sparse row (CSR) or column (CSC), block compressed sparse row
 (BSR), general block compressed sparse row (GEBSR), and the ELLPACK-ITPACK
 format (ELL).

rocSPARSE is a dependency of a number of libraries for scientific computing
that can use AMD GPU hardware including PyTorch, Tensorflow, PETSc, Hypre,
Tasmanian, and MFEM, as well as other ROCm libraries such as hipSPARSE
and rocALUTION.

This package is part of AMD's ROCm stack and will be maintained
under the Debian AI team umbrella.

Bug#1023079: toot: manpage out of date

[gregor herrmann]

Package: toot
Version: 0.28.0-2
Severity: minor

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Ths subcommands ("options") mentioned in the manpage don't reflect
the reality of the toot command, as seen by `toot' help output.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmNdsKtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYOphAAmwHFR/Tut+NzlF3Cv7GCDlQCTxOCPWN+uGzTH2kk5Uc6lGLqbuV7rvxy
oBsCC0WRjjF1l6xOpYk8sqQbqjMdHzdNlfPWQXJYwCCnDRq+YOJft8IklWMH+4Em
xmIOyD2qm86IpLZETWKSFLGnbB6HIWsEYNbxVek427ECtMGx7KUiIPQUsfgIJc+O
AeXXZuA4V/4CjFFXNEBGFhiYiwVFHpHHhkg3wiAMXDVv+ZPjC9zSuNtpnFZj63Rf
NJGFjs3tuzDvJs66lvo85km6/0LwF80tApQe+Egtz6A2GqK8cC7GiaTEqSmG2Yq0
OVMGWQiT08rJ50w4KoeJKtEPOVOiEJzBmP/JUtwuuUDMgebbAGTXYPXgFaZgbpcW
TDUbd2H7zzDM5eqHD9yEl7l3LZcXXEmU1I56j0FZBBcB5uDQOPoSthqV4xdj2atI
UgFYzSuZztErXTUM+FsKoX+dZ3AOY+9VDz7QDxaFYQ7ZuapsNhCF2QC4UzgcdhQL
xy+ihQGXseE9r81c45RydN/XYwQvUKX26Ol23i+Iw6adxFVuCK+gUnO9sIvHrgoB
LL2kLlcdNEV9g/3JhotDi2OHu5c0KcEsLqfW71DTt1942KZw4rxFad0ek0+wBtYz
GxQO3xqWkSPoaGpc4uA7BAdAm6yVh0eMoRFHRzDcn0X94dtj/AA=
=N7dV
-END PGP SIGNATURE-

Bug#1023036: [Debian-on-mobile-maintainers] Bug#1023036: osk-sdl: Pinephone with FDE can't boot with v0.67-2

[undef]

Dear Maintainer,



Hi,

Thanks for the bug report.


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

done.

Begin: Mounting root file system ... Begin: Running /scripts/local-top
... stty: standard

Input: cannot perform all requested operations: Resource temporarily
unavailable

[13.466434] random: osk-sdl: uninitialized urandom read (16 bytes read)

[13.969621] random: osk-sdl: uninitialized urandom read (16 bytes read)

[24.870996] random: crng init done

[41.955178] ps: disabling

[41.958144] dc1sw: disablingup: uninitialized urandom read (4 bytes
read)

[41.961320] avdd-csi: disabling

[41.964854] vcc-1v2-hsic: disabling

[41.968634] usb0-vbus: disabling

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

...and booting does not progress past that.  I have reverted to v0.67-1.

I did a dist-upgrade October 28 and then tried v0.67-2 again and got
the same result.



This sounds very similar to 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017842#5. Could you 
try deleting the final `cat > /dev/null` line in v0.67-2? If so, this 
bug will be fixed in 0.67.1-1 that I am currently preparing.

Bug#1023077: qt6-webchannel FTCBFS: does not pass QT_HOST_PATH to cmake

[Helmut Grohne]

Source: qt6-webchannel
Version: 6.3.1-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

qt6-webchannel fails to cross build from source, because it does not
pass QT_HOST_PATH to cmake. Please consider applying the attached patch
to fix that.

Helmut
diff --minimal -Nru qt6-webchannel-6.3.1/debian/changelog 
qt6-webchannel-6.3.1/debian/changelog
--- qt6-webchannel-6.3.1/debian/changelog   2022-08-15 19:24:11.0 
+0200
+++ qt6-webchannel-6.3.1/debian/changelog   2022-10-30 00:51:53.0 
+0200
@@ -1,3 +1,10 @@
+qt6-webchannel (6.3.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Pass QT_HOST_PATH. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 30 Oct 2022 00:51:53 +0200
+
 qt6-webchannel (6.3.1-2) unstable; urgency=medium
 
   [ Patrick Franz ]
diff --minimal -Nru qt6-webchannel-6.3.1/debian/rules 
qt6-webchannel-6.3.1/debian/rules
--- qt6-webchannel-6.3.1/debian/rules   2021-11-25 00:17:42.0 +0100
+++ qt6-webchannel-6.3.1/debian/rules   2022-10-30 00:51:52.0 +0200
@@ -3,12 +3,19 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+extra_cmake_args :=
+
+ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+extra_cmake_args += -DQT_HOST_PATH=/usr
+endif
+
 %:
dh $@ --with pkgkde_symbolshelper --buildsystem=cmake+ninja
 
 override_dh_auto_configure:
dh_auto_configure -- \
-   -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH)
+   -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH) \
+   $(extra_cmake_args)
 
 execute_after_dh_auto_install:
# Reproducible builds: remove build paths from .prl files

Bug#1023076: linux-headers-6.0.0-2-amd64: bluetooth crashes after returning from suspend

[Gabriel Francisco]

Package: linux-headers-6.0.0-2-amd64
Version: 6.0.3-1
Severity: normal
X-Debbugs-Cc: frc.gabr...@gmail.com

Dear Maintainer,

With this kernel seems to crash bluetooth when returning from
suspend. Few days ago my cursor froze, the computer rebooted and I
couldn't find logs in /var/log/syslog.

I think it might be related to #1021905.

This time I can see this message from dmesg:

[24504.576562] Bluetooth: hci0: RTL: fw version 0xd9a8a0cd
[24504.659770] r8169 :05:00.0 enp5s0: Link is Down
[24504.706018] Bluetooth: MGMT ver 1.22
[24506.722037] Bluetooth: hci0: Ignoring error of Inquiry Cancel command
[24509.160942] wlp3s0: authenticate with e4:bf:fa:cc:15:70
[24509.180111] wlp3s0: Invalid HE elem, Disable HE
[24509.299099] wlp3s0: send auth to e4:bf:fa:cc:15:70 (try 1/3)
[24509.305463] wlp3s0: authenticated
[24509.335739] wlp3s0: associate with e4:bf:fa:cc:15:70 (try 1/3)
[24509.337000] wlp3s0: RX AssocResp from e4:bf:fa:cc:15:70 (capab=0x1011 
status=0 aid=3)
[24509.448135] wlp3s0: associated
[24509.448274] wlp3s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 
e4:bf:fa:cc:15:70
[24509.512359] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[24510.633689] input: Shure AONIC TW2 (AVRCP) as /devices/virtual/input/input32
[24519.113962] audit: type=1400 audit(1667082607.529:55): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2327 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[24519.173906] audit: type=1400 audit(1667082607.585:56): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2327 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[24519.232356] audit: type=1400 audit(1667082607.645:57): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2327 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[24519.241718] audit: type=1400 audit(1667082607.657:58): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2327 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[24554.003191] Bluetooth: hci0: Opcode 0x 402 failed: -16
[24595.999699] general protection fault, probably for non-canonical address 
0x867f:  [#1] PREEMPT SMP NOPTI
[24595.999706] CPU: 4 PID: 979 Comm: bluetoothd Not tainted 6.0.0-2-amd64 #1  
Debian 6.0.3-1
[24595.999708] Hardware name: LENOVO 21A4GE/21A4GE, BIOS R1MET49W (1.19 
) 06/27/2022
[24595.999710] RIP: 0010:hci_send_acl+0x21/0x2f0 [bluetooth]
[24595.999739] Code: cc cc 0f 1f 80 00 00 00 00 0f 1f 44 00 00 41 57 49 89 ff 
41 56 41 55 41 54 55 48 89 f5 53 48 83 ec 28 4c 8b 67 18 89 54 24 0c <4d> 8b 8c 
24 80 06 00 00 4c 89 4c 24 18 66 90 0f b7 da 8b 4d 70 2b
[24595.999740] RSP: 0018:a8c8817ffcc0 EFLAGS: 00010286
[24595.999742] RAX: 88da73ec RBX: 0003 RCX: 0003
[24595.999743] RDX:  RSI: 88db1cb2af00 RDI: 88d99e47de00
[24595.999745] RBP: 88db1cb2af00 R08: 88d99dc1f0c0 R09: 000c
[24595.999746] R10: 002a R11:  R12: 7fff
[24595.999746] R13: a8c8817ffe10 R14: 88db1cb2af00 R15: 88d99e47de00
[24595.999747] FS:  7f2851c0e7c0() GS:88df11f0() 
knlGS:
[24595.999749] CS:  0010 DS:  ES:  CR0: 80050033
[24595.999749] CR2: 55e4b0ec2300 CR3: 000107586000 CR4: 00750ee0
[24595.999750] PKRU: 5554
[24595.999751] Call Trace:
[24595.999754]  
[24595.999755]  ? mutex_lock+0xe/0x30
[24595.999761]  l2cap_chan_send+0x12f/0xc60 [bluetooth]
[24595.999787]  ? remove_wait_queue+0x20/0x60
[24595.999791]  ? _raw_spin_unlock_irqrestore+0x23/0x40
[24595.999793]  ? bt_sock_wait_ready+0x128/0x1a0 [bluetooth]
[24595.999812]  l2cap_sock_sendmsg+0x9a/0x100 [bluetooth]
[24595.999833]  sock_sendmsg+0x5f/0x70
[24595.999836]  __sys_sendto+0x11c/0x170
[24595.999840]  __x64_sys_sendto+0x20/0x30
[24595.999841]  do_syscall_64+0x3a/0xc0
[24595.999844]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
[24595.999846] RIP: 0033:0x7f2851b0c2fc
[24595.999848] Code: 02 eb bd 66 2e 0f 1f 84 00 00 00 00 00 90 41 89 ca 64 8b 
04 25 18 00 00 00 85 c0 75 19 45 31 c9 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 64 c3 0f 1f 00 41 54 48 83 ec 20 48 89 54 24
[24595.999849] RSP: 002b:7ffd5ae68d68 EFLAGS: 0246 ORIG_RAX: 
002c
[24595.999851] RAX: ffda RBX: 55ceb8074290 RCX: 7f2851b0c2fc
[24595.999852] RDX: 0003 RSI: 55ceb80326b0 RDI: 002a
[24595.999852] RBP: 0003 R08:  R09: 
[24595.999853] R10:  R11: 0246 R12: 55ceb80326b0
[24595.999854] R13: 002a R14: 55ceb8074290 R15: 55ceb8032e60

Bug#1023075: qt6-positioning FTCBFS: does not pass QT_HOST_PATH

[Helmut Grohne]

Source: qt6-positioning
Version: 6.3.1-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

qt6-positioning fails to cross build from source, because it does not
pass QT_HOST_PATH. Please consider applying the attached patch to fix
that.

Helmut
diff --minimal -Nru qt6-positioning-6.3.1/debian/changelog 
qt6-positioning-6.3.1/debian/changelog
--- qt6-positioning-6.3.1/debian/changelog  2022-08-15 19:22:59.0 
+0200
+++ qt6-positioning-6.3.1/debian/changelog  2022-10-30 00:46:52.0 
+0200
@@ -1,3 +1,10 @@
+qt6-positioning (6.3.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Pass QT_HOST_PATH. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 30 Oct 2022 00:46:52 +0200
+
 qt6-positioning (6.3.1-2) unstable; urgency=medium
 
   [ Patrick Franz ]
diff --minimal -Nru qt6-positioning-6.3.1/debian/rules 
qt6-positioning-6.3.1/debian/rules
--- qt6-positioning-6.3.1/debian/rules  2021-12-04 16:03:23.0 +0100
+++ qt6-positioning-6.3.1/debian/rules  2022-10-30 00:46:51.0 +0200
@@ -3,12 +3,19 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+extra_cmake_args :=
+
+ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+extra_cmake_args += -DQT_HOST_PATH=/usr
+endif
+
 %:
dh $@ --with pkgkde_symbolshelper --buildsystem=cmake+ninja
 
 override_dh_auto_configure:
dh_auto_configure -- \
-   -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH)
+   -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH) \
+   $(extra_cmake_args)
 
 execute_after_dh_auto_install:
# Reproducible builds: remove build paths from .prl files

Bug#1023074: qt6-svg FTCBFS: does not pass QT_HOST_PATH

[Helmut Grohne]

Source: qt6-svg
Version: 6.3.1-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

qt6-svg fails to cross build from source, because it does not pass
QT_HOST_PATH. Please consider applying the attached patch to fix that.

Helmut
diff --minimal -Nru qt6-svg-6.3.1/debian/changelog 
qt6-svg-6.3.1/debian/changelog
--- qt6-svg-6.3.1/debian/changelog  2022-08-15 19:23:56.0 +0200
+++ qt6-svg-6.3.1/debian/changelog  2022-10-30 00:40:25.0 +0200
@@ -1,3 +1,10 @@
+qt6-svg (6.3.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Pass QT_HOST_PATH. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 30 Oct 2022 00:40:25 +0200
+
 qt6-svg (6.3.1-2) unstable; urgency=medium
 
   [ Patrick Franz ]
diff --minimal -Nru qt6-svg-6.3.1/debian/rules qt6-svg-6.3.1/debian/rules
--- qt6-svg-6.3.1/debian/rules  2021-12-02 09:24:06.0 +0100
+++ qt6-svg-6.3.1/debian/rules  2022-10-30 00:40:25.0 +0200
@@ -4,12 +4,19 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+extra_cmake_args :=
+
+ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+extra_cmake_args += -DQT_HOST_PATH=/usr
+endif
+
 %:
dh $@ --with pkgkde_symbolshelper --buildsystem=cmake+ninja
 
 override_dh_auto_configure:
dh_auto_configure -- \
-   -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH)
+   -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH) \
+   $(extra_cmake_args)

 execute_after_dh_auto_install:
# Reproducible builds: remove build paths from .prl files

Bug#1023073: qt6-declarative FTCBFS: QT_HOST_PATH not specified and more

[Helmut Grohne]

Source: qt6-declarative
Version: 6.3.1+dfsg-5
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

qt6-declarative fails to cross build from source. The immediate failure
is QT_HOST_PATH not being specified. A few more things come up and I've
created a patch for your convenience. The details are in the changelog.
Please consider applying it.

Helmut
diff --minimal -Nru qt6-declarative-6.3.1+dfsg/debian/changelog 
qt6-declarative-6.3.1+dfsg/debian/changelog
--- qt6-declarative-6.3.1+dfsg/debian/changelog 2022-09-04 07:34:45.0 
+0200
+++ qt6-declarative-6.3.1+dfsg/debian/changelog 2022-10-29 16:02:51.0 
+0200
@@ -1,3 +1,13 @@
+qt6-declarative (6.3.1+dfsg-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Pass QT_HOST_* variables to cmake.
++ Build tools when cross compiling.
++ Build depend on ourselves during cross compiling.
+
+ -- Helmut Grohne   Sat, 29 Oct 2022 16:02:51 +0200
+
 qt6-declarative (6.3.1+dfsg-5) unstable; urgency=medium
 
   * Team upload.
diff --minimal -Nru qt6-declarative-6.3.1+dfsg/debian/control 
qt6-declarative-6.3.1+dfsg/debian/control
--- qt6-declarative-6.3.1+dfsg/debian/control   2022-09-03 20:11:00.0 
+0200
+++ qt6-declarative-6.3.1+dfsg/debian/control   2022-10-29 16:02:51.0 
+0200
@@ -16,6 +16,7 @@
pkg-kde-tools,
qt6-base-dev (>= 6.3.1+dfsg~),
qt6-base-private-dev (>= 6.3.1+dfsg~),
+   qt6-declarative-dev:native ,
qt6-languageserver-private-dev (>= 6.3.1~),
 Standards-Version: 4.6.1
 Homepage: https://www.qt.io/developers/
diff --minimal -Nru qt6-declarative-6.3.1+dfsg/debian/rules 
qt6-declarative-6.3.1+dfsg/debian/rules
--- qt6-declarative-6.3.1+dfsg/debian/rules 2021-11-20 19:53:33.0 
+0100
+++ qt6-declarative-6.3.1+dfsg/debian/rules 2022-10-29 16:02:51.0 
+0200
@@ -6,12 +6,22 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+extra_cmake_args :=
+
+ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+extra_cmake_args += \
+   -DQT_HOST_PATH=/usr \
+   -DQT_HOST_PATH_CMAKE_DIR=/usr/lib/${DEB_BUILD_MULTIARCH}/cmake \
+   -DQT_BUILD_TOOLS_WHEN_CROSSCOMPILING=ON
+endif
+
 %:
dh $@ --with pkgkde_symbolshelper --buildsystem=cmake+ninja
 
 override_dh_auto_configure:
dh_auto_configure -- \
-   -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH)
+   -DCMAKE_LIBRARY_PATH=$(DEB_HOST_MULTIARCH) \
+   $(extra_cmake_args)
 
 execute_after_dh_auto_install:
# Reproducible builds: remove build paths from .prl files

Bug#994696: Bind9's systemd .service says named available before it actually is, which makes services which depend on it fail

[Bernhard Schmidt]

Am 29.10.22 um 10:44 schrieb Bernhard Schmidt:

Hi Ondrej,


I think it would be best if someone has finished the upstream systemd
support. I am currently busy with other more important stuff, but if 
there

was a working MR I would be happy to do the review and also do the
backport to 9.18. The change is isolated, so it won't create any fuzz.


The code has been merged in 9.19.6. Do you think we could backport it, 
either upstream in the next release or in 9.18.8 for Debian?


I'll look at enabling this in the experimental branch.


Appears to work fine, I've pushed a commit enabling sd_notify to the 
debian/9.19 branch and it looks good, readyness is properly signaled and 
autopkgtest works even without the sleep 1


https://salsa.debian.org/dns-team/bind9/-/commit/5a6ee84642d91cdb721a04be11beb28621dd8e1f

Bernhard

Bug#1018915: v4l-utils: FTBFS with libbpf 1.0.0

[Sudip Mukherjee]

Control: tags -1 patch
--

Hi Sean, Gregor,

On Wed, Sep 14, 2022 at 05:29:57PM +0100, Sean Young wrote:
> Hi Gregor,
> 
> On Wed, Sep 07, 2022 at 02:53:49PM +0200, Gregor Jasny wrote:
> > Hello Sudip,
> > 
> > thanks for the report.
> > 
> > On 02.09.22 01:19, Sudip Mukherjee wrote:
> > > Package: v4l-utils
> > > Version: 1.22.1-4
> > > Severity: important
> > > Tags: ftbfs
> > > X-Debbugs-Cc: sudipm.mukher...@gmail.com
> > > Usertags: libbpf1
> > > 
> > > Dear Maintainer,
> > > 
> > > v4l-utils FTBFS with libbpf 1.0.0 (available in experimental).
> > > This is the first error from the build log:
> > > 



> > 
> > Sean, would you be able to port the existing code to libbpf 1.0? I noticed
> > that the current code already triggers deprecation warnings with libbpf
> > 0.8.0.
> 
> This needs porting, I'll add it to my todo list.

Can you please test the attached patch and confirm that it does not break
any of the functionality. This is the only one now which is blocking me
from requesting libbbpf transition.

-- 
Regards
Sudip
diff -Nru v4l-utils-1.22.1/debian/changelog v4l-utils-1.22.1/debian/changelog
--- v4l-utils-1.22.1/debian/changelog	2022-05-22 14:08:50.0 +0100
+++ v4l-utils-1.22.1/debian/changelog	2022-10-29 11:33:37.0 +0100
@@ -1,3 +1,10 @@
+v4l-utils (1.22.1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Port changes for libbpf/1.0.1
+
+ -- Sudip Mukherjee   Sat, 29 Oct 2022 11:33:37 +0100
+
 v4l-utils (1.22.1-4) unstable; urgency=high
 
   * Bump standards to version 4.6.1.0 (no changes needed)
diff -Nru v4l-utils-1.22.1/debian/patches/libbpf.patch v4l-utils-1.22.1/debian/patches/libbpf.patch
--- v4l-utils-1.22.1/debian/patches/libbpf.patch	1970-01-01 01:00:00.0 +0100
+++ v4l-utils-1.22.1/debian/patches/libbpf.patch	2022-10-29 11:33:37.0 +0100
@@ -0,0 +1,113 @@
+Description: Changes for libbpf/1.0.1
+
+Author: Sudip Mukherjee 
+
+---
+
+Bug-Debian: https://bugs.debian.org/1018915
+Forwarded: no
+
+--- v4l-utils-1.22.1.orig/utils/keytable/bpf_load.c
 v4l-utils-1.22.1/utils/keytable/bpf_load.c
+@@ -63,19 +63,16 @@ struct bpf_file {
+ 
+ static int load_and_attach(int lirc_fd, struct bpf_file *bpf_file, struct bpf_insn *prog, int size)
+ {
+-	struct bpf_load_program_attr load_attr;
+-	int fd, err;
++	LIBBPF_OPTS(bpf_prog_load_opts, opts);
++	int fd, err, insn_cnt;
+ 
+-	memset(_attr, 0, sizeof(struct bpf_load_program_attr));
++	insn_cnt = size / sizeof(struct bpf_insn);
+ 
+-	load_attr.prog_type = BPF_PROG_TYPE_LIRC_MODE2;
+-	load_attr.expected_attach_type = BPF_LIRC_MODE2;
+-	load_attr.name = bpf_file->name;
+-	load_attr.insns = prog;
+-	load_attr.insns_cnt = size / sizeof(struct bpf_insn);
+-	load_attr.license = bpf_file->license;
++	opts.expected_attach_type = BPF_LIRC_MODE2;
++	opts.log_buf = bpf_log_buf;
++	opts.log_size = LOG_BUF_SIZE;
+ 
+-	fd = bpf_load_program_xattr(_attr, bpf_log_buf, LOG_BUF_SIZE);
++	fd = bpf_prog_load(BPF_PROG_TYPE_LIRC_MODE2, bpf_file->name, bpf_file->license, prog, insn_cnt, );
+ 	if (fd < 0) {
+ 		printf("bpf_load_program() err=%m\n%s", bpf_log_buf);
+ 		return -1;
+@@ -95,6 +92,9 @@ static int build_raw_map(struct bpf_map_
+ 	int no_patterns, value_size, fd, key, i;
+ 	struct raw_entry *e;
+ 	struct raw_pattern *p;
++	LIBBPF_OPTS(bpf_map_create_opts, opts,
++		.map_flags = map->def.map_flags,
++	);
+ 
+ 	no_patterns = 0;
+ 
+@@ -110,14 +110,13 @@ static int build_raw_map(struct bpf_map_
+ 
+ 	value_size = sizeof(struct raw_pattern) + max_length * sizeof(short);
+ 
+-	fd = bpf_create_map_node(map->def.type,
+- map->name,
+- map->def.key_size,
+- value_size,
+- no_patterns,
+- map->def.map_flags,
+- numa_node);
+-
++	opts.numa_node = numa_node;
++	fd = bpf_map_create(map->def.type,
++			map->name,
++			map->def.key_size,
++			value_size,
++			no_patterns,
++			);
+ 	if (fd < 0) {
+ 		printf(_("failed to create a map: %d %s\n"),
+ 		   errno, strerror(errno));
+@@ -174,27 +173,34 @@ static int load_maps(struct bpf_file *bp
+ 
+ 		if (maps[i].def.type == BPF_MAP_TYPE_ARRAY_OF_MAPS ||
+ 		maps[i].def.type == BPF_MAP_TYPE_HASH_OF_MAPS) {
+-			int inner_map_fd = bpf_file->map_fd[maps[i].def.inner_map_idx];
++			LIBBPF_OPTS(bpf_map_create_opts, opts,
++.inner_map_fd = bpf_file->map_fd[maps[i].def.inner_map_idx],
++.map_flags = maps[i].def.map_flags,
++.numa_node = numa_node,
++			);
+ 
+-			bpf_file->map_fd[i] = bpf_create_map_in_map_node(
++			bpf_file->map_fd[i] = bpf_map_create(
+ 			maps[i].def.type,
+ 			maps[i].name,
+ 			maps[i].def.key_size,
+-			inner_map_fd,
++			4,
+ 			maps[i].def.max_entries,
+-			maps[i].def.map_flags,
+-			numa_node);
++			);
+ 		} else if (!strcmp(maps[i].name, "raw_map")) {
+ 			bpf_file->map_fd[i] = build_raw_map([i], raw, numa_node);
+ 		} else {
+-			bpf_file->map_fd[i] = bpf_create_map_node(
++			LIBBPF_OPTS(bpf_map_create_opts, opts,
++.map_flags = maps[i].def.map_flags,
++

Bug#1021179: pipewire-pulse: KDE Plasma+ALC4080 onboard card: unable to select working profile

[Maurizio Avogadro]

tags 1021179 + patch
thanks

Hi Dylan

Jaroslav Kysela prepared a MR [1] that solves the issue. The patch is attached 
here unchanged: it applies cleanly to the source tree of pipewire v0.3.59-1, I 
could simply add it to the series and rebuild the binaries.


Thanks

[1] https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1429From a2278a5f70fcc03ee72173c44896928d4c6b88d5 Mon Sep 17 00:00:00 2001
From: Jaroslav Kysela 
Date: Sat, 29 Oct 2022 20:22:06 +0200
Subject: [PATCH] spa: support the speakers (output) only case in
 report_jack_state()

The Realtek ALC4080 USB audio device (integrated in the
motherboards) can detect the presence on all I/O jacks.

If user connects only speakers, it's a valid case.

BugLink: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2744
---
 spa/plugins/alsa/acp/acp.c | 29 +++--
 1 file changed, 27 insertions(+), 2 deletions(-)

diff --git a/spa/plugins/alsa/acp/acp.c b/spa/plugins/alsa/acp/acp.c
index f23232ed3..c49c9e088 100644
--- a/spa/plugins/alsa/acp/acp.c
+++ b/spa/plugins/alsa/acp/acp.c
@@ -624,7 +624,7 @@ static int report_jack_state(snd_mixer_elem_t *melem, unsigned int mask)
 	pa_card *impl = snd_mixer_elem_get_callback_private(melem);
 	snd_hctl_elem_t *elem = snd_mixer_elem_get_private(melem);
 	snd_ctl_elem_value_t *elem_value;
-	bool plugged_in;
+	bool plugged_in, any_input_port_available;
 	void *state;
 	pa_alsa_jack *jack;
 	struct temp_port_avail *tp, *tports;
@@ -735,6 +735,31 @@ static int report_jack_state(snd_mixer_elem_t *melem, unsigned int mask)
 	if (impl->card.active_profile_index != ACP_INVALID_INDEX)
 		active_available = impl->card.profiles[impl->card.active_profile_index]->available;
 
+	/* First round - detect, if we have any input port available.
+	   If the hardware can report the state for all I/O jacks, only speakers
+	   may be plugged in. */
+	any_input_port_available = false;
+	PA_HASHMAP_FOREACH(profile, impl->profiles, state) {
+		pa_device_port *port;
+		void *state2;
+
+		if (profile->profile.flags & ACP_PROFILE_OFF)
+			continue;
+
+		PA_HASHMAP_FOREACH(port, impl->ports, state2) {
+			if (!pa_hashmap_get(port->profiles, profile->profile.name))
+continue;
+
+			if (port->port.direction == ACP_DIRECTION_CAPTURE &&
+			port->port.available != ACP_AVAILABLE_NO) {
+any_input_port_available = true;
+goto input_port_found;
+			}
+		}
+	}
+input_port_found:
+
+	/* Second round */
 	PA_HASHMAP_FOREACH(profile, impl->profiles, state) {
 		pa_device_port *port;
 		void *state2;
@@ -768,7 +793,7 @@ static int report_jack_state(snd_mixer_elem_t *melem, unsigned int mask)
 
 		if (has_input_port && !has_output_port && found_available_input_port)
 			available = ACP_AVAILABLE_YES;
-		if (has_output_port && !has_input_port && found_available_output_port)
+		if (has_output_port && (!has_input_port || !any_input_port_available) && found_available_output_port)
 			available = ACP_AVAILABLE_YES;
 		if (has_output_port && has_input_port && found_available_output_port && found_available_input_port)
 			available = ACP_AVAILABLE_YES;
-- 
GitLab

Bug#1023072: RFS: sanlock/3.8.5-1 -- Shared storage lock manager

[Håvard F . Aasen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : sanlock
   Version  : 3.8.5-1
   Upstream contact :
 * URL  : https://www.pagure.io/sanlock/
 * License  : LGPL-2.1+, GPL-2+
 * Vcs  : https://salsa.debian.org/haava/sanlock
   Section  : libs

The source builds the following binary packages:

  sanlock - Shared storage lock manager
  sanlk-reset - Host reset daemon and client using sanlock
  libsanlock-client1 - Shared storage lock manager (client library)
  libsanlock1 - Shared storage lock manager (shared library)
  libsanlock-dev - Shared storage lock manager (development files)
  python3-sanlock - Python3 bindings to shared storage lock manager

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/sanlock/sanlock_3.8.5-1.dsc

Changes since the last upload:

 sanlock (3.8.5-1) unstable; urgency=medium
 .
   * New upstream release.
   * Drop python-build.patch, not needed when using pybuild.
   * Update wildcard for increased flexibility when installing files in
 Python package.
   * Update maintainer name and email.
   * d/libsanlock1.symbols
 - Update symbols.
 - Add Build-Depends field for library 'libwdmd'.
   * d/control:
 - Add python3-setuptools as BD.
 - Update BD to handle cross build.
 - Update Standards-Version to 4.6.1
   * d/rules:
 - Explicitly build Python package with pybuild.
 - Include hardening build flags
   * d/copyright: Add myself under Debian paragraph.
   * Update d/sanlock.postinst to reflect changes in adduser package.

Regards,
-- 
  Håvard F. Aasen

Bug#1023071: please bump gap-kernel-7 to gap-kernel-8

[Bill Allombert]

Package: gap-io
Version: 4.7.0+ds-2
Severity: important

Dear Debian Science team,

gap-io depends on gap-kernel-7. This need to be bumped to gap-kernel-8 
and rebuild, to work with gap 4.12.
Idem for gap-float

Thanks in advance,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#1011210: reverse dependencies

[Jochen Sprickerhof]

Control: tags -1 - moreinfo

Hi Thorsten,

* Thorsten Alteholz  [2022-09-18 17:35]:

there are reverse dependencies that need to be taken care of:

Checking reverse dependencies...
# Broken Depends:
android-platform-art: dexdump [amd64 arm64 armhf i386]
 dexlist [amd64 arm64 armhf i386]
android-platform-frameworks-base: android-libandroidfw-dev [amd64 
arm64 armel armhf i386 mips64el mipsel]


# Broken Build-Depends:
android-platform-art: android-libbacktrace-dev (>= 1:29)
 android-libcutils-dev (>= 1:29)
 android-libziparchive-dev (>= 1:29)
android-platform-frameworks-base: android-libutils-dev (>= 1:29)
 android-libziparchive-dev (>= 1:29)
android-platform-system-extras: android-libbase-dev (>= 1:10.0.0+r36-1~)
   android-libcutils-dev (>= 1:10.0.0+r36-1~)
   android-libsparse-dev (>= 1:10.0.0+r36-1~)
   android-platform-system-core-headers (>= 
1:10.0.0+r36-1~)
android-platform-system-tools-aidl: android-libbase-dev (>= 10.0.0+r36~)
   android-libcutils-dev (>= 10.0.0+r36~)
android-platform-system-tools-hidl: android-libbase-dev (>= 1:10.0.0+r36~)
   android-libcrypto-utils-dev (>= 
1:10.0.0+r36-3~)
   android-liblog-dev (>= 1:10.0.0+r36~)
   android-libutils-dev (>= 1:10.0.0+r36~)


In case they matter, this needs to be addressed first. Please remove 
the moreinfo tag once that is done.


The latest dak output is:

Checking reverse dependencies...
# Broken Depends:
android-platform-art: dexdump [amd64 arm64 armhf i386]
  dexlist [amd64 arm64 armhf i386]
android-platform-frameworks-base: android-libandroidfw-dev [amd64 arm64 armel 
armhf i386 mips64el mipsel]

# Broken Build-Depends:
android-platform-art: android-libbacktrace-dev (>= 1:29)
  android-libcutils-dev (>= 1:29)
  android-libziparchive-dev (>= 1:29)
android-platform-frameworks-base: android-libutils-dev (>= 1:29)
  android-libziparchive-dev (>= 1:29)
android-platform-system-extras: android-libbase-dev (>= 1:10.0.0+r36-1~)
android-libcutils-dev (>= 1:10.0.0+r36-1~)
android-libsparse-dev (>= 1:10.0.0+r36-1~)
android-platform-system-core-headers (>= 
1:10.0.0+r36-1~)
android-platform-system-tools-aidl: android-libbase-dev (>= 10.0.0+r36~)
android-libcutils-dev (>= 10.0.0+r36~)
android-platform-system-tools-hidl: android-libbase-dev (>= 1:10.0.0+r36~)
android-liblog-dev (>= 1:10.0.0+r36~)
android-libutils-dev (>= 1:10.0.0+r36~)

As far as I can see all those packages are actually provided by 
src:android-platform-tools but the old versions are still in the archive 
(probably due to being arch all and new arch any). So please remove:


android-libbacktrace-dev_10.0.0+r36-10_all
android-libcutils-dev_10.0.0+r36-10_all
android-libziparchive-dev_10.0.0+r36-10_all
android-libutils-dev_10.0.0+r36-10_all
android-libbase-dev_10.0.0+r36-10_all
android-libsparse-dev_10.0.0+r36-10_all
android-platform-system-core-headers_10.0.0+r36-10_all
android-liblog-dev_10.0.0+r36-10_all

(all build by android-platform-system-core)

Afterwards src:android-platform-system-core should be removable as well 
(I hope).


Cheers Jochen


signature.asc
Description: PGP signature

Bug#1023070: libzfslinux-dev: needs to depend on libblkid-dev

[наб]

Package: libzfslinux-dev
Version: 2.1.6-2
Severity: important

Dear Maintainer,

I just got this:
-- >8 --
$ pkg-config --cflags libzfs
Package blkid was not found in the pkg-config search path.
Perhaps you should add the directory containing `blkid.pc'
to the PKG_CONFIG_PATH environment variable
Package 'blkid', required by 'libzfs_core', not found
-- >8 --

Of course, this was alleviated by installing libblkid-dev,
but having the packages not depend on each other means that
libzfslinux-dev is unusable when building dependent packages with
mininal dependencies.

Best,
наб


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

Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
LSM: AppArmor: enabled

Versions of packages libzfslinux-dev depends on:
ii  libnvpair3linux  2.1.6-2
ii  libssl-dev   3.0.5-4
ii  libuutil3linux   2.1.6-2
ii  libzfs4linux 2.1.6-2
ii  libzfsbootenv1linux  2.1.6-2
ii  libzpool5linux   2.1.6-2

libzfslinux-dev recommends no packages.

libzfslinux-dev suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1023069: RFS: uriparser/0.9.7+dfsg-1 -- documentation files for uriparser

[Jörg Frings-Fürst]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

   Package name : uriparser
   Version  : 0.9.7+dfsg-1
   Upstream contact : 
   URL  : http://uriparser.sourceforge.net
   License  : LGPL-2.1+, BSD-3-clause
   Vcs  : https://jff.email/cgit/uriparser.git
   Section  : libs

The source builds the following binary packages:

  liburiparser1 - URI parsing library compliant with RFC 3986
  liburiparser-dev - development files for uriparser
  liburiparser-doc - documentation files for uriparser

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

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

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

 dget -x 
https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.9.7+dfsg-1.dsc

or from 

 git https://jff.email/cgit/uriparser.git/?h=release%2Fdebian%2F0.9.7%2Bdfsg-1



Changes since the last upload:

 uriparser (0.9.7+dfsg-1) unstable; urgency=medium
 .
   * New upstream release.
   * Fix debian/watch.
   * Declare compliance with Debian Policy 4.6.1.0 (No changes needed).


CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#1023055: libzia so filename contains upstream version (only)

[Florian Wolters]

>I know nothing about the technical details here, but it seems quite
>unlikely to me that anything external would ever depend on libzia, so
>shipping both in one package would make sense.

I second that. libzia is only used by tucnak. So making it one package would be 
absolutely fine. 

  73s Florian DF2ET 

Bug#1021157: missing firmwares for Qualcomm NFA725A

[Vincent Bernat]

On 2022-10-29 20:05, Diederik de Haas wrote:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/?qt=grep=WCN6855
does show various results which come very close ...SILICONZ_LITE-3.6510.7 vs
the referenced ...SILICONZ_LITE-3.6510.16.
And one commit is for symlinks to hw2.1

qca/rampatch_usb_00130201.bin is also present in the upstream repo, but
searching for nvm_usb_00130201_gf.bin did not yield any results.

So this looks like upstream does have most of the needed files, albeit a
slightly older version?
I don't know if anything should be done based on this, but figured I'd share
my findings.


I suppose the search engine only works for stuff mentioned directly in 
commit messages. The file present in the repository: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qca/nvm_usb_00130201_gf.bin.

Bug#1023068: /usr/share/perl5/Config/Model/Dpkg/Dependency.pm: warning with perl 5.36

[gregor herrmann]

Package: libconfig-model-dpkg-perl
Version: 2.164
Severity: minor
File: /usr/share/perl5/Config/Model/Dpkg/Dependency.pm

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Since the upgrade to perl 5.36 I see:

Use of @_ in numeric gt (>) with signatured subroutine is experimental at 
/usr/share/perl5/Config/Model/Dpkg/Dependency.pm line 344.


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmNdl9lfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbXBg/+JBgaG6CqnTKeBjvEP5GGvYmYp5ogEqUf2aAMADnTQnTtD84nWT2bk5F6
akxx+W2zgXVOpW+Tze7KOb2FkxX/szAaKaZQdAUM+XEv0K60A/tZp8O7a6K8wP9C
SJWP1ew1swKRP6UqcSI2Usuki2nw2tJLZGJx6EpjEwvVfZQO0EP961/DQ16Rgn0C
xZViTXTmSHTfOT5iS6/Mpz4S7nRmtHi/0C3hjlvstssxejuwTzbpIWTJzzKRzuWt
aVJbNddK58QeR7k50a+YJj8tdRWMO6e65mQc6KSf1dtx2KgWR7wq+R07wwnmuWFy
9PcjMLii03ixAVbNQmhQ6QZd4QNVy7VTiMm4D3AEFn02EhvLTPpBxb8ZxqcEd1kO
wQhv185iNsqQ/nBEAXLeNs5VUzV8zknQerG0hauhSKkI9pkinOWKSTwEltdOX6zl
fiPAQg6N7Jjsvs9uNRMWu90oHUYJdv+bRLJ1IMnxKOlXKVLlTZNFCcmL10TILqv1
KVzKS9pKoyDo+cxsIPXbGU98/GtGWh352nbTKUBs5Gbl2BL8Bz01dlQ/mTlfPU34
4urgSAU/e3erZ35uQKr10rim6l9tmoXFS8VTPtaNKokKssM6EeFFM2pxG3E0ys4e
0YSRswQsH4/tt04HqhURYAFxeoge3Hx1oCvzW4Zt/RCsWozFZys=
=Pyv+
-END PGP SIGNATURE-

Bug#1022837: /lib/runit/run_sysv_scripts uses wrong test to skip initscripts

[Andras Korn]

On Fri, Oct 28, 2022 at 03:07:07PM +0200, Lorenzo wrote:

Hi,

> > Package: runit
> > Version: 2.1.2-50
> > Severity: normal
> > 
> > Hi,
> > 
> > /lib/runit/run_sysv_scripts has this:
> > 
> > for script in "$initdir/$rX"* ; do
> > [ ! -x "$script" ] && continue
> > path=$(realpath "$script")
> > name=${path##*/}
> > # Special case for wicd. Runscript is called "wicd-daemon",
> > # to match binary package name.
> > [ -d "/etc/sv/$name" ] && continue
> > [ -d "/etc/sv/$name-daemon" ] && continue
> > "$script" "$rcommand"
> > done
> > 
> > Checking for /etc/sv/$name and skipping initscripts if those
> > directories exist is wrong for two reasons:
> > 
> >  1. /etc/sv/$name may not be symlinked into /etc/service (false
> > positive);
> 
> The runit service exists and is not enabled, so why one would want to
> start a sysv instance instead? 
> To me 1. looks correct, can you make an example when it causes
> unexpected/buggy results?

Our expectations are apparently different. I would expect 
/lib/runit/run_sysv_scripts to do what it says on the tin: run sysv scripts. 
The only reason to skip a script (as far as I'm concerned) is that running it 
would conflict with a runit service.

It's not just about starting services either: if /etc/sv/$name exists but the 
service is not managed by runit (that is, /etc/service/$name doesn't exist), 
and I start the service manually via the initscript, run_sysv_scripts will also 
fail to stop it.

I understand that you're thinking of /etc/sv/ as "configuration", but in this 
instance I would prefer configuration to be more explicit; if I want to disable 
a service I'll make sure it can't be started (e.g. by modifying its 
/etc/default file), not just refrain from creating a /etc/service/ symlink for 
it.

If I just want to disable automatic startups, I'll create 
/etc/service/servicename/down.

> >  2. /etc/service may contain a symlink to a service directory for this 
> > service that is elsewhere in the filesystem, not in /etc/sv (false 
> > negative).

Example:

lrwxrwxrwx 1 root root 34 Feb  9  2009 /etc/service/atd -> 
/var/lib/svn-checkout/services/atd

This isn't in /etc/sv, but it still means atd(8) is managed by runit.

> > As a minimum, I suggest the following: instead of /etc/sv/$name, check for 
> > /etc/service/$name (and $name-daemon if necessary), and not with "-d" but 
> > "-L" (because when running rcS.d, the target of the symlink may only appear 
> > later, for example when a new filesystem is mounted).
> > 
> > This is still imperfect during boot because /etc/service may point to some 
> > directory that is not the one we'll switch to with runsvdir in stage 2. I 
> > don't know what the best way of handling this (likely rare) case is, but 
> > the following solutions come to mind:
> 
> 2. is an issue, especially because I'm thinking of moving the runtime
> directory form /etc/sv/ --> /run/runit/sv/ : this move requires a
> long transition period where both the old and the new path are
> supported as runtime directories..

Uh, what runtime directory? /etc/sv is currently a repository for 
package-supplied and admin-provided service directories. Why would you move 
that to /run, which is volatile?

> On the other hand I don't know if with systemd or Sysvinit is even possible 
> to boot the system with a custom path for services; I don't want to make it 
> unnecessary hard to do it with runit, but I think it's reasonable to expect 
> some effort on admin side for such setup.

I'm sorry, you lost me completely (or maybe I lost you; see my example symlink 
above).

> >  1. have a /etc/runit/override-init.d/ directory. If $name exists in it, 
> > don't invoke the initscript in /lib/runit/run_sysv_scripts. This places the 
> > entire administration/configuration burden on the admin but is very simple 
> > to do, and easy enough for the admin to automate (e.g. your own service 
> > scripts can just create these files when they're first run).
> 
> I'm ok with adding this, but it's unclear to me if the above is theoretical 
> reasoning or you have an actual problem with your setup: in case of the 
> latter please add more detail to avoid the unhappy case where the fix that i 
> push doesn't solve your issue

Yes.

For example, I have an atd service whose service directory is 
/var/lib/svn-checkout/services/atd. This is symlinked into /etc/service. 
run_sysv_scritps doesn't detect it as a runit-supervised service, because the 
directory is different from /etc/sv/atd, and starts another instance via the 
initscript.

I have many such services. I keep my runit service directories in Subversion 
and have a checkout of the repository on all systems. I just symlink the 
appropriate directory from the checkout into /etc/service if I want to run a 
service.

I use /etc/sv to instantiate services that I have templates for; for example, I 
have an openvpn runit service template, so I'll create /etc/sv/openvpn-foobar 
and create a 

Bug#1006500: marked as done (Missing bnx2x firmware 7.13.21.0 renders NIC unusable with Linux 5.16)

[Christoph Anton Mitterer]

On Sat, 2022-10-29 at 09:44 +0200, Salvatore Bonaccorso wrote:
> We do similar with intel-microcode updates, so maybe this is
> something
> we should consider to. But I think it's to early to think about a
> potential 20220913-1~deb11u1 via a bullseye point release.

It's just that for any bullseye users, this NICs are in principle
broken (at least out of the box) right now.

Anyway... I guess it's not super urgent :-)


Cheers,
Chris.

Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

[Christoph Anton Mitterer]

On Sat, 2022-10-29 at 09:23 +0200, Salvatore Bonaccorso wrote:
> 
> No unfortunately we cannot do that. The reason is similar to what
> lead
> to
> https://salsa.debian.org/kernel-team/linux/-/commit/248736d493fcfd0e05cd23f97befe40f5c125c71
> or caused bugs like #916927.

Forgive me my ignorance, but from the package's file list I'd assume
that the signatures are included in the kernel image respectively the
module files themselves?

Is that a must, or could they be standalone signatures?

Cause if the latter, wouldn't something like the following be possible:
- have only one package that actually contains the kernel and modules
  (and that would be available earlier)
- have that depend on a separate package that ships the standalone
  signatures

That would have the benefit that there are no "duplicate" packages, and
people could create a dummy for the signature package with e.g. equivs.

> The signed packages need always longer as this needs action of
> signing
> them trough a seprate manual process of ftp-masters.

Sure, clear.


Best wishes,
Chris.

Bug#1021997: cargo: New upstream version

[Jonathan Rubenstein]

Hey maintainers,

I am also facing the same problem, some crates refuse to build on my 
machine because they require a newer version of cargo (0.60 at minimum)

The current version is 0.57, could this be updated? Thanks.

Best Regards,

Jonathan Rubenstein

Bug#1023067: Bookworm netinstall CD: X-Server crashing on virtio-gpu

[kolafl...@kolahilft.de]

Package: debian-installer
Version: 20220917

Hi,

the X-Server on the netinstall CD crashes when using a virtio GPU.


qemu-system-x86_64 \
  -m 1G -machine pc,accel=kvm \
  -device virtio-vga \
  -cdrom \

debian-12-netinstall-amd64_testing-20221029-1721/debian-testing-amd64-netinst.iso


CD image downloaded here:
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso

I attached some logfiles.
The bug should be really easy to reproduce. Just boot up the graphical 
installer.


This is a regression. Using a Debian-11 CD works fine.
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.5.0-amd64-netinst.iso



Sincerely,
kolAflash



--
PGP: https://misc.kolahilft.de/pgp/MoritzDuge_0xC49633CB.asc


bookworm_netinstall_virtio-gpu.tar.xz
Description: application/xz


OpenPGP_0xEA831012D83C3408.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1022900: grub-install, efibootmgr etc. not working with new kernel

[Stephan Verbücheln]

For completeness: The problem persists with the new kernel in Sid.

> 6.0.0-2-amd64 / Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux

Bug#1023066: ITP: libmastodon-client-perl -- Mastodon API perl bindings

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libmastodon-client-perl
  Version : 0.017
  Upstream Author : Jos?? Joaqu??n Atria 
* URL : https://metacpan.org/release/Mastodon-Client
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Mastodon API perl bindings

Mastodon::Client lets you talk to a Mastodon server to obtain authentication
credentials, read posts from timelines in both static or streaming mode, and
perform all the other operations exposed by the Mastodon API.

Most of these are available through convenience methods, which validate input
parameters and are likely to provide meaningful feedback in case of
errors.

Alternatively, this distribution can be used via the low-level request
methods (post, get, etc), which allow direct access to the API endpoints. All
other methods call one of these at some point.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Bug#1023065: xuxen-eu-spell: stop building hunspell-eu

[Andreas Beckmann]

Source: xuxen-eu-spell
Version: 3.0.20070215-1
Severity: serious

hunspell-eu is now built by src:hunspell-eu. Please stop building it
from xuxen-eu-spell.


Andreas

Bug#1023064: bullseye-pu: package libdatetime-timezone-perl/1:2.47-1+2022f

[gregor herrmann]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: debian-p...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I've uploaded libdatetime-timezone-perl/1:2.47-1+2022f to bullseye,
with the changes from tzdata 2022f applied to the perl data
structures as a quilt patch.

Changes, taken from tzdata upstream:

   Mexico will no longer observe DST after 2022, except for areas
near the US border that continue to observe US DST rules.
On 2022-10-30 at 02:00 the Mexican state of Chihuahua moves
from -07 (-06 with DST) to year-round -06, thus not changing
its clocks that day.  The new law states that Chihuahua
near the US border no longer observes US DST.
(Thanks to gera for the heads-up about Chihuahua.)

Fiji will not observe DST in 2022/3.  (Thanks to Shalvin Narayan.)
For now, assume DST is suspended indefinitely.


I'm attaching a stripped down debdiff.


Thanks in advance,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmNdjaRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaWSg/+OUnckBHcKKHqHLaYmfF32B5XK2y3l0w1Hd2Rotg2g/GGvL/2Tdg4tVya
mMaKgjyLl2jGLefyQrgKHNsMxbiGatcwcZzDyQZJQoCaEPBLKL8t1AviRVzHdUod
FRhCoKF1MjZYkT/ccDwVWn2uJcp1KYbjtK7IBCfB/4MUXx7i034VEWmNB23kBREf
R9QMbBVZ8dCChUrzRXNHXYkbg13UrSHDWMKIiQpUXWhsRAPz4tgm6iZ5nIoe9XTI
biLmB2slQ1aKQ0m2vvQXu2YLch0tf8FPizA707KQGKqV96NX8cycVULaL8zbcEMk
33Xt7aqEUbvlyHmwAYGiKl8YtBqKtz6eF6kMrAKekVNjereQK+Jjt+r2zZmiceim
xUgfom2TIeDQJKD2ip2vzH55xIGxyBuXjQKc9G64dNo5Ee3nuR331s1dMEEESCdV
356+Rm/ny/OptaVpLN6+SjwDxhAW6JRVeVUC7oD0TDzaneDw256Htl6n8xH22nrX
EVbYtXcSACEePd8CmTZHDjPgBY6NHo25UeYrE3B9zxdpjiOUdEuLoV5yOpl655zH
uBMpUYXSGwi80xokTbLbNYEruN7ZNkBn4v/0tXMdwNVyqGBhlPtG76OSt53n7Mj1
d/82QeUuKC9gZ+QOEnZLM94b1zdD2mFneYhcyg0VS2Lcjp0gnPc=
=XjJx
-END PGP SIGNATURE-
diff -Nru libdatetime-timezone-perl-2.47/debian/changelog 
libdatetime-timezone-perl-2.47/debian/changelog
--- libdatetime-timezone-perl-2.47/debian/changelog 2022-10-14 
15:26:55.0 +0200
+++ libdatetime-timezone-perl-2.47/debian/changelog 2022-10-29 
22:24:15.0 +0200
@@ -1,3 +1,10 @@
+libdatetime-timezone-perl (1:2.47-1+2022f) bullseye; urgency=medium
+
+  * Update to Olson database version 2022f.
+This update includes contemporary changes for Fiji and Mexico.
+
+ -- gregor herrmann   Sat, 29 Oct 2022 22:24:15 +0200
+
 libdatetime-timezone-perl (1:2.47-1+2022e) bullseye; urgency=medium
 
   * Update to Olson database version 2022e.
diff -Nru libdatetime-timezone-perl-2.47/debian/patches/olson-2022f 
libdatetime-timezone-perl-2.47/debian/patches/olson-2022f
--- libdatetime-timezone-perl-2.47/debian/patches/olson-2022f   1970-01-01 
01:00:00.0 +0100
+++ libdatetime-timezone-perl-2.47/debian/patches/olson-2022f   2022-10-29 
22:24:15.0 +0200
@@ -0,0 +1,12698 @@
+Description: Update to Olson DB 2022f
+Origin: vendor
+Author: gregor herrmann 
+Last-Update: 2022-10-29
+
+--- a/lib/DateTime/TimeZone/Africa/Abidjan.pm
 b/lib/DateTime/TimeZone/Africa/Abidjan.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from debian/tzdata/africa.  Olson data version 2022e
++# Generated from debian/tzdata/africa.  Olson data version 2022f
+ #
+ # Do not edit this file directly.
+ #
+@@ -43,7 +43,7 @@
+ ],
+ ];
+ 
+-sub olson_version {'2022e'}
++sub olson_version {'2022f'}
+ 
+ sub has_dst_changes {0}
+ 
+--- a/lib/DateTime/TimeZone/America/Merida.pm
 b/lib/DateTime/TimeZone/America/Merida.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from debian/tzdata/northamerica.  Olson data version 2022e
++# Generated from debian/tzdata/northamerica.  Olson data version 2022f
+ #
+ # Do not edit this file directly.
+ #
+@@ -538,207 +538,18 @@
+ ],
+ [
+ 63802796400, #utc_start 2022-10-30 07:00:00 (Sun)
+-63816105600, #  utc_end 2023-04-02 08:00:00 (Sun)
++DateTime::TimeZone::INFINITY, #  utc_end
+ 63802774800, #  local_start 2022-10-30 01:00:00 (Sun)
+-63816084000, #local_end 2023-04-02 02:00:00 (Sun)
++DateTime::TimeZone::INFINITY, #local_end
+ -21600,
+ 0,
+ 'CST',
+ ],
+-[
+-63816105600, #utc_start 2023-04-02 08:00:00 (Sun)
+-63834246000, #  utc_end 2023-10-29 07:00:00 (Sun)
+-63816087600, #  local_start 2023-04-02 03:00:00 (Sun)
+-63834228000, #local_end 2023-10-29 02:00:00 (Sun)
+--18000,
+-1,
+-'CDT',
+-],
+-[
+-63834246000, #utc_start 2023-10-29 07:00:00 (Sun)
+-6384816, #  utc_end 2024-04-07 08:00:00 (Sun)
+-63834224400, #  local_start 2023-10-29 01:00:00 (Sun)
+-63848138400, #local_end 2024-04-07 02:00:00 (Sun)
+--21600,
+-0,
+-'CST',
+-],
+-[
+-6384816, #utc_start 2024-04-07 08:00:00 (Sun)
+-63865695600, #  utc_end 

Bug#1021919: virtionet device not found in debian testing netinst ISO 20221017

[kolafl...@kolahilft.de]

Hi,

I got the same problem using Qemu.
(Debian-11 host, using Debian's Qemu-5.2.0)


qemu-system-x86_64 \
  -m 1G -machine pc,accel=kvm \
  -device virtio-net-pci,netdev=user.1 -netdev user,id=user.1 \
  -cdrom 
debian-12-netinstall-amd64_testing-20221029-1721/debian-testing-amd64-netinst.iso



When the installer begins detecting the network hardware.
(after selecting the keyboard layout)

dmesg:
[   52.822967] BPF: [97154] STRUCT
[   52.822970] BPF: size=896 vlen=72
[   52.822970] BPF:
[   52.822971] BPF: invalid name
[   52.822971] BPF:
[   52.822972] failed to validate module [failover] BTF: -22


Maybe related?
  arm64+virtio: "No device for installation media was detected" error
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998087


Sincerely,
kolAflash


OpenPGP_0xEA831012D83C3408.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023063: ITP: golang-sourcehut-emersion-go-scfg -- Go library for a simple configuration file format

[Taavi Väänänen]

Package: wnpp
Severity: wishlist
Owner: Taavi Väänänen 

* Package name: golang-sourcehut-emersion-go-scfg
  Version : 0.0~git20211215.c2c7a15-1
  Upstream Author : Simon Ser 
* URL : https://git.sr.ht/~emersion/go-scfg
* License : Expat
  Programming Lang: Go
  Description : Go library for a simple configuration file format

go-scfg is a Go library to work with the scfg configuration file
format.

I am packaging this since it is a dependency of the sr.ht CLI tool hut
(https://git.sr.ht/~emersion/hut).


OpenPGP_0xEF242F709F912FBE.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023062: RM: sockjs-client -- RoQA; superseded by node-sockjs-client

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal

Please remove the obsolete src:sockjs-client and the libjs-sockjs binary
package is had built. This functionality is now provided by
(src:)node-sockjs-client. There are no rdepends left ;-)

Andreas

Bug#985769: xwayland: 100% of CPU, The system gets stuck.

[John Norris]

Hello, I am seeing this behavior with a new and up-to-date installation of
Debian.  I am running Debian as a guest OS in VMWare Player.  The host OS
is Windows 11 running on a Dell XPS laptop.

John

Bug#1023061: RFS: ipmitool/1.8.19-1 -- utility for IPMI control with kernel driver or LAN interface (daemon)

[Jörg Frings-Fürst]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

   Package name : ipmitool
   Version  : 1.8.19-1
   Upstream contact : 
   URL  : https://github.com/ipmitool/ipmitool
   License  : BSD-3-clause
   Vcs  : https://jff.email/cgit/ipmitool.git
   Section  : utils

The source builds the following binary packages:

  ipmitool - utility for IPMI control with kernel driver or LAN
interface (daemon)

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

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

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

 dget -x 
https://mentors.debian.net/debian/pool/main/i/ipmitool/ipmitool_1.8.19-1.dsc

or from 

 git https://jff.email/cgit/ipmitool.git?h=release%2Fdebian%2F1.8.19-1


Changes since the last upload:

 ipmitool (1.8.19-1) unstable; urgency=medium
 .
   * New upstrem release.
 - New debian/patches/0700-build.patch.
 - New debian/patches/0620-manpage_typo.patch.
   * Remove longer not needed patches.
   * Declare compliance with Debian Policy 4.6.1.0 (No changes needed).
   * debian/copyright:
 - Add year 2022 to myself.
   * New debian/patches/0105-sensor_reading.patch (Closes: #983082):
 - Fix sensor reading for non-analog sensors.
   * New debian/README.Debian with the explanation how to change the
   start parameters (Closes: #1002013).


CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#1023060: RM: nthash [armel armhf i386 mipsel s390x] -- ROM; B-D btllib un-supported on 32-bit

[Nilesh Patra]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: debian-...@lists.debian.org

Hi,

nthash has recently started to build-depend on btllib, which is
not supported on 32-bit and probably on big-endian systems as well.

The upstream has also confirmed the same:

https://github.com/bcgsc/btllib/issues/62#issuecomment-1295671711

Hence please remove nthash from these archs.

Thanks!
Nilesh

Bug#1023055: libzia so filename contains upstream version (only)

[Christoph Berg]

Re: tony mancill
> Is there a reason why libzia shouldn't install a libzia.so or
> libzia.0.so symlink to the currently installed version of the library so
> we can potentially upgrade the library without necessarily breaking
> tucnak installs (and vice-versa)?  Or if there is a good reason why this
> will never work, should we combine tucnak and libzia into a single
> package?

I know nothing about the technical details here, but it seems quite
unlikely to me that anything external would ever depend on libzia, so
shipping both in one package would make sense.

Christoph

Bug#1023059: RM: libnthash-dev [arch:all] -- ROM; architecture change from all to any

[Nilesh Patra]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: debian-...@lists.debian.org

Hi,

libnthash-dev binary package from src:nthash has changed its arch
from all to any, because it now also ships a static lib along with
it, hence please remove the arch:all binary for this binary package.

Thanks!
Nilesh

Bug#1023058: git-buildpackage: gbp dch refuses to work with $[DEB]EMAIL unset, doesn't use either at all?

[наб]

Package: git-buildpackage
Version: 0.9.29
Severity: normal

Dear Maintainer,

Every time I do:
-- >8 --
$ gbp dch --verbose -R
gbp:error: Either 'EMAIL' or 'DEBEMAIL' must be set in the environment
for 'dch' to work
-- >8 --
and every time I re-run with EMAIL=: gbp ...

AFAICT, nothing actually uses the variables, so idk why they're
complained about. My config is:
-- >8 --
$ grep -v '^#' ~/.gbp.conf
[DEFAULT]
builder = debuild -i -I -sa
cleaner = fakeroot debian/rules clean
debian-branch = debian
git-debian-branch = debian
git-author = True

[buildpackage]
export-dir = ../build-output/

[import-orig]
dch = False
filter-pristine-tar = True
-- >8 --

The changelog "-- author  date" line correctly lists my public
mailing address (not the machine-local one).

Best,
наб

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

Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
LSM: AppArmor: enabled

Versions of packages git-buildpackage depends on:
ii  devscripts 2.22.2
ii  git1:2.37.2-1
ii  man-db 2.11.0-1+b1
ii  python33.10.6-1
ii  python3-dateutil   2.8.2-1
ii  python3-pkg-resources  65.5.0-1
ii  python3-yaml   5.4.1-1+b2
ii  sensible-utils 0.0.17

Versions of packages git-buildpackage recommends:
pn  cowbuilder | pbuilder | sbuild  
ii  pristine-tar1.49
ii  python3-requests2.27.1+dfsg-1

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
ii  sudo 1.9.11p3-2
ii  unzip6.0-27

-- no debconf information


signature.asc
Description: PGP signature

Bug#1014537: unnamed packaging files in a multibinary package should be an error

[Niels Thykier]

Control: clone -1 -2 -3
Control: reassign -2 lintian
Control: reassign -3 lintian-brush
Control: block -3 by -2
Control: block -3 by -1
Control: block -2 by -1

Hi,

CC'ing relevant maintainers for clone + reassign for lintian + 
lintian-brush.


I am looking at making `debian/foo` an error by default in debhelper 
compat 15 (triggering a warning from compat 14).  The choice of having 
an intermediate compat level is to align the change with another 
"single-binary vs. multi-binary" change.


My current code proposal is at 
https://salsa.debian.org/debian/debhelper/-/merge_requests/97 for people 
who are curious or want to help by testing.


@Michael: This has some interesting affects on the 
dh_installsystemd{,user} test cases.  Could you have a look at 
dh_installsystemd{,user} and see if you agree with where this is headed 
for that helper?  If it is becoming unslightly, maybe we should combine 
it with a fix for #932152.


On Sat, 9 Jul 2022 00:11:47 +0200 gregor herrmann  wrote:

On Thu, 07 Jul 2022 08:48:36 -0700, Steve Langasek wrote:

> This kind of packaging, with some packaging files under debian/ having an
> associated binary package name and some not, is an antipattern.

+1

(I also don't like packaging files without binary package name for
single-binary source package, but that's just a matter of taste.)
 


I will standardize forbidding `debian/foo` in the general case with the 
following exceptions:


 * debian/copyright
 * debian/changelog
 * debian/NEWS

These have historically applied to all packages and it does not seem 
useful to force everyone to maintain N copies of {changelog,copyright,...}.


 * debian/README.Debian
 * debian/TODO

These have historically been installed into the main package and a note 
in debhelper (dh_installdocs) suggests these (or at least README.Debian) 
is a name standardized by Policy.  I am open to not installing them by 
default if one of you are willing to drive the discussion on 
debian-devel to assert there is consensus for that.


Otherwise, I will keep the special-case for these two files for now.


> I would like to suggest that in the next debhelper compat level, debhelper
> should consider it an error when debian/control lists more than one binary
> package, but contains unnamed packaging files under debian/.  


Or maybe start with a warning (maybe immediately) and then proceed to
an error?

I also wonder if a lintian warning might be helpful to get this
going.
(And I admit that I haven't checked if such a lintian tag exists but
I can't remember seeing one.)


Cheers,
gregor

[...]
I have CC'ed lintian + lintian-brush on CC and cloned bugs for them. 
Having a lintian tag for them will enable the Janitor to help with the 
migration, so I agree we should have a lintian tag for this.


Thanks,
~Niels

Bug#1023055: libzia so filename contains upstream version (only)

[tony mancill]

Source: libzia
Version: 4.36-1
Severity: normal

Hello,

I am working to update tucnak and libzia to 4.37 and am finally fully
grokking something Christoph mentioned a while back about the tight
coupling between these packages.

The libzia-4.37 package is ready to upload.  However, doing so will
immediately break the current version of tucnak in the archive until it
is rebuilt, since it expects to find /usr/lib//libzia-4.36.so.
Only to see if it would work, I tested the version of tucnak 4.36
in the archive against a locally install libzia-4.37 by creating a
symlink.  This works fine, but the current situation seems generally
"broken."

Is there a reason why libzia shouldn't install a libzia.so or
libzia.0.so symlink to the currently installed version of the library so
we can potentially upgrade the library without necessarily breaking
tucnak installs (and vice-versa)?  Or if there is a good reason why this
will never work, should we combine tucnak and libzia into a single
package?

Thanks,
tony


signature.asc
Description: PGP signature

Bug#1022982: mark libfile-slurp-perl Multi-Arch: foreign

[Helmut Grohne]

Control: block -1 by 749826

Hi,

On Sat, Oct 29, 2022 at 01:10:53PM +1000, Alexander Zangerl wrote:
> not until somebody points me to some authoritative documentation
> of this multi-arch field. (and no, wikis in ubuntu-land don't count.)

We've tried, but getting there has proved difficult. For the foreign
annotation, the major difficulty is striking a good balance between a
readable text and including enough detail to cover corner cases.

You can find my own attempt at
https://wiki.debian.org/DependencyHell#Multi-Arch:_foreign

This has been used as a basis for the relevant policy bug #749826, but
progress has stalled there
https://salsa.debian.org/dbnpolicy/policy/-/compare/master...bug749826-spwhitton

Does this count as authoritative documentation to you?

Feedback on these texts (in particular on how easy they are to
understand) would be very welcome.

Helmut

Bug#1023054: qt6-base FTCBFS: multiple reasons

[Helmut Grohne]

Source: qt6-base
Version: 6.3.1+dfsg-10
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

qt6-base fails to cross build from source for many different reasons.
I've created a patch that makes it cross buildable and documented the
individual aspects in the changelog. Does all of that make sense to you?
The most contentious parts are probably in cross.patch. Do you think
they're upstreamable in some way?

Helmut
diff --minimal -Nru qt6-base-6.3.1+dfsg/debian/changelog 
qt6-base-6.3.1+dfsg/debian/changelog
--- qt6-base-6.3.1+dfsg/debian/changelog2022-10-01 18:58:47.0 
+0200
+++ qt6-base-6.3.1+dfsg/debian/changelog2022-10-28 19:58:00.0 
+0200
@@ -1,3 +1,16 @@
+qt6-base (6.3.1+dfsg-10.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Pass QT_HOST_PATH. (Closes: #-1)
++ cross.patch: Honour PKG_CONFIG_EXECUTABLE
++ cross.patch: Allow building android tools
++ Pass QT_HOST_* variables to build.
++ Depend on a native qt toolchain for the former.
++ Do build tools even when cross building.
++ Add excess files t debian/not-installed.
+
+ -- Helmut Grohne   Fri, 28 Oct 2022 19:58:00 +0200
+
 qt6-base (6.3.1+dfsg-10) unstable; urgency=medium
 
   [ Lisandro Damián Nicanor Pérez Meyer ]
diff --minimal -Nru qt6-base-6.3.1+dfsg/debian/control 
qt6-base-6.3.1+dfsg/debian/control
--- qt6-base-6.3.1+dfsg/debian/control  2022-09-17 19:21:11.0 +0200
+++ qt6-base-6.3.1+dfsg/debian/control  2022-10-28 19:58:00.0 +0200
@@ -71,6 +71,7 @@
ninja-build,
pkg-config,
pkg-kde-tools (>= 0.15.17~),
+   qt6-base-dev:native ,
unixodbc-dev,
zlib1g-dev,
 Standards-Version: 4.6.1
diff --minimal -Nru qt6-base-6.3.1+dfsg/debian/not-installed 
qt6-base-6.3.1+dfsg/debian/not-installed
--- qt6-base-6.3.1+dfsg/debian/not-installed2022-09-11 13:58:51.0 
+0200
+++ qt6-base-6.3.1+dfsg/debian/not-installed2022-10-28 19:58:00.0 
+0200
@@ -4,3 +4,8 @@
 usr/lib/${DEB_HOST_MULTIARCH}/cmake/Qt6/3rdparty/kwin/qt_attribution.json
 usr/lib/qt6/bin/qmake
 usr/lib/qt6/bin/qtpaths
+# cross build specific:
+usr/lib/qt6/bin/host-qmake
+usr/lib/qt6/bin/host-qtpaths
+usr/lib/qt6/bin/target_qt.conf
+usr/lib/${DEB_HOST_MULTIARCH}/qt6/mkspecs/qdevice.pri
diff --minimal -Nru qt6-base-6.3.1+dfsg/debian/patches/cross.patch 
qt6-base-6.3.1+dfsg/debian/patches/cross.patch
--- qt6-base-6.3.1+dfsg/debian/patches/cross.patch  1970-01-01 
01:00:00.0 +0100
+++ qt6-base-6.3.1+dfsg/debian/patches/cross.patch  2022-10-28 
19:58:00.0 +0200
@@ -0,0 +1,22 @@
+--- 
qt6-base-6.3.1+dfsg.orig/cmake/QtBuildInternals/QtBuildInternalsConfig.cmake
 qt6-base-6.3.1+dfsg/cmake/QtBuildInternals/QtBuildInternalsConfig.cmake
+@@ -146,8 +146,6 @@
+ set(FEATURE_pkg_config "${pkg_config_enabled}" CACHE STRING "Using 
pkg-config")
+ if(NOT pkg_config_enabled)
+ qt_build_internals_disable_pkg_config()
+-else()
+-unset(PKG_CONFIG_EXECUTABLE CACHE)
+ endif()
+ endfunction()
+ 
+--- qt6-base-6.3.1+dfsg.orig/src/tools/configure.cmake
 qt6-base-6.3.1+dfsg/src/tools/configure.cmake
+@@ -2,7 +2,7 @@
+ SECTION "Deployment"
+ LABEL "Android deployment tool"
+ PURPOSE "The Android deployment tool automates the process of creating 
Android packages."
+-CONDITION NOT CMAKE_CROSSCOMPILING AND QT_FEATURE_regularexpression)
++CONDITION QT_FEATURE_regularexpression)
+ 
+ qt_feature("macdeployqt" PRIVATE
+ SECTION "Deployment"
diff --minimal -Nru qt6-base-6.3.1+dfsg/debian/patches/series 
qt6-base-6.3.1+dfsg/debian/patches/series
--- qt6-base-6.3.1+dfsg/debian/patches/series   2022-09-17 13:50:40.0 
+0200
+++ qt6-base-6.3.1+dfsg/debian/patches/series   2022-10-28 19:58:00.0 
+0200
@@ -11,3 +11,4 @@
 
 # Don't use yield on CPUs that might not support it
 armel-noyield.patch
+cross.patch
diff --minimal -Nru qt6-base-6.3.1+dfsg/debian/rules 
qt6-base-6.3.1+dfsg/debian/rules
--- qt6-base-6.3.1+dfsg/debian/rules2022-09-17 19:21:11.0 +0200
+++ qt6-base-6.3.1+dfsg/debian/rules2022-10-28 19:58:00.0 +0200
@@ -19,6 +19,13 @@
 extra_cmake_args += -DFEATURE_sctp=OFF
 endif
 
+ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+   extra_cmake_args += \
+   -DQT_HOST_PATH=/usr \
+   -DQT_HOST_PATH_CMAKE_DIR=/usr/lib/${DEB_BUILD_MULTIARCH}/cmake \
+   -DQT_BUILD_TOOLS_WHEN_CROSSCOMPILING=ON
+endif
+
 %:
dh $@ --with pkgkde_symbolshelper --buildsystem=cmake+ninja
 

Bug#1023053: bash FTBFS on musl: duplicate definition of strtoimax

[Helmut Grohne]

Source: bash
Version: 5.2-2
Tags: ftbfs patch upstream
User: helm...@debian.org
Usertags: rebootstrap

bash fails to build from source on musl-linux-any. The root cause of
this is a logic inversion bug in the detection of strtoimax where it
provides a replacement function iff strtoimax is available. This affects
any architecture, but due to linking order only produces a build failure
for the musl libc. I'm attaching a patch that corrects the logic
inversion for your convenience.

Helmut
--- a/m4/strtoimax.m4
+++ b/m4/strtoimax.m4
@@ -29,7 +29,7 @@
   fi
 ])
 AC_MSG_RESULT($bash_cv_func_strtoimax)
-if test $bash_cv_func_strtoimax = yes; then
+if test $bash_cv_func_strtoimax = no; then
 AC_LIBOBJ(strtoimax)
 fi
 ])

Bug#1023052: ITP: tesseract-plumbing -- safe wrapper of tesseract-sys

[Jonas Smedegaard]

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: tesseract-plumbing
  Version : 0.7.1
  Upstream Author : Chris Couzens 
* URL : https://github.com/ccouzens/tesseract-plumbing
* License : Expat
  Programming Lang: Rust
  Description : safe wrapper of tesseract-sys

 Leptonica-plumbing exposes a safe version of the tesseract-sys api,
 to access the C API of tesseract in a safe manner.

This package will be maintained in the collaborative Debian section of
Salsa, at .

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNdcPwACgkQLHwxRsGg
ASHqcxAAm8lIn6H7WZnld9GFSJhrbNKDK5oq23Lxxf9uSFgbSYo9wRu+7ByNjtQ0
t3ltf78mDb4a7/Iv6wWMp3x2gHkqUsmxKbo5q7hk4xJEY3mR7Xdr9EhjiQNp7fI+
Xv6QWRYk3QU3erwh/oTisKTPltsL7F+jZM6ablK77GUzWEHUzPNp0VG84b0oKvAF
mDyfOXk68yBOvwJA8S5UeuKDphdRK0pYM46JXgSSMtt/dWR/UmR9jKjkMxByFg9M
QGWk1tUHe3mTFM6RfnvR8O3Sh9iaItRSCVOTTjH1Vqzud/UDcxmtipJXhcP7cy6N
MiMju2DCZpaZOOmIf1qXvw5bI7l35gCIv54emRc+aFdT6DKcB1+hxNdcini2NOAC
y43k0XytyZF/CiFYukPAb2GLSxMZrA47xGVp6igX635MW8VrDZVnOyusUHqTe/iR
weylHtLuyQEncGu1zcLZoxMOVApdW5gXHnGJdq/+claCZ3Qcrz68WC9YRKkPZtSG
2LC23Z8cV5cj1wxqNnsEFSxB2bm+3NuUtktm2tThiGNNXvPZtUK1T9Yhn6Q7Xb/X
J7BSrQfv7WxZefjLTDeT61o5mq5Y2NYtVpAxuv9BEIeQFQ7orSW+Tto8ApnpZKdu
qf37gY2JC+W36QxprEhLvB3iVSO79t3eUeifLAKOiKC8uS3I094=
=mXOk
-END PGP SIGNATURE-

signature.asc
Description: signature

Bug#1023051: ITP: leptonica-plumbing -- safe wrapper of leptonica-sys

[Jonas Smedegaard]

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: leptonica-plumbing
  Version : 0.6.0
  Upstream Author : Chris Couzens 
* URL : https://github.com/ccouzens/leptonica-plumbing
* License : Expat
  Programming Lang: Rust
  Description : safe wrapper of leptonica-sys

 Leptonica-plumbing exposes a safe version of the leptonica-sys api,
 to access the C API of leptonica in a safe manner.

This package will be maintained in the collaborative Debian section of
Salsa, at .

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNdcPwACgkQLHwxRsGg
ASHqcxAAm8lIn6H7WZnld9GFSJhrbNKDK5oq23Lxxf9uSFgbSYo9wRu+7ByNjtQ0
t3ltf78mDb4a7/Iv6wWMp3x2gHkqUsmxKbo5q7hk4xJEY3mR7Xdr9EhjiQNp7fI+
Xv6QWRYk3QU3erwh/oTisKTPltsL7F+jZM6ablK77GUzWEHUzPNp0VG84b0oKvAF
mDyfOXk68yBOvwJA8S5UeuKDphdRK0pYM46JXgSSMtt/dWR/UmR9jKjkMxByFg9M
QGWk1tUHe3mTFM6RfnvR8O3Sh9iaItRSCVOTTjH1Vqzud/UDcxmtipJXhcP7cy6N
MiMju2DCZpaZOOmIf1qXvw5bI7l35gCIv54emRc+aFdT6DKcB1+hxNdcini2NOAC
y43k0XytyZF/CiFYukPAb2GLSxMZrA47xGVp6igX635MW8VrDZVnOyusUHqTe/iR
weylHtLuyQEncGu1zcLZoxMOVApdW5gXHnGJdq/+claCZ3Qcrz68WC9YRKkPZtSG
2LC23Z8cV5cj1wxqNnsEFSxB2bm+3NuUtktm2tThiGNNXvPZtUK1T9Yhn6Q7Xb/X
J7BSrQfv7WxZefjLTDeT61o5mq5Y2NYtVpAxuv9BEIeQFQ7orSW+Tto8ApnpZKdu
qf37gY2JC+W36QxprEhLvB3iVSO79t3eUeifLAKOiKC8uS3I094=
=mXOk
-END PGP SIGNATURE-

Bug#1023050: RM: ibus-tests [armel] -- RoQA; NBS; restricted to architectures with working mozjs102

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal

 ibus (1.5.27-2) unstable; urgency=medium
 .
   * Team upload
 .
   [ Simon McVittie ]
   * Only build and run ibus-tests on architectures with working mozjs102
 (closes: #1018871)

Please remove the cruft package on armel:

ibus-tests | 1.5.27-1 | unstable| armel


Andreas

Bug#1023025: linux-image-6.0.0-2-686: kernel BUG at mm/memory.c:2660!

[Diederik de Haas]

Control: tag -1 -a11y

On zaterdag 29 oktober 2022 12:33:59 CEST femenia wrote:
> Package: src:linux
> Version: 6.0.3-1
> Severity: grave
> Tags: a11y

I don't see how a11y is relevant here, so removing the tag

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

Bug#1021157: missing firmwares for Qualcomm NFA725A

[Diederik de Haas]

On zaterdag 29 oktober 2022 07:15:19 CEST Vincent Bernat wrote:
> On 2022-10-29 00:50, Diederik de Haas wrote:
> >> The card works just fine with a 5.19 kernel after installing these files
> >> in /usr/lib/firmware/ath11k/WCN6855/hw2.0/:
> >> https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/1.1/WLA
> >> N.H SP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.16/amss.bin
> >> https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/1.1/WLA
> >> N.
> >> HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.16/m3.bin
> >> https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/board-2
> >> .b
> >> in
> >> https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/regdb.b
> >> in
> >> 
> >> And then creating a symlink from /usr/lib/firmware/ath11k/WCN6855/hw2.1/
> >> to hw2.0/ .
> >> 
> >> (I do not understand the structure of the directories in
> >> WCN6855/hw2.0/1.1/, so I choose the newest files.)
> >> 
> >> Some other firmwares from
> >> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.g
> >> it/tree/qca are needed for Bluetooth support and are missing as well:
> >> 
> >> qca/rampatch_usb_00130201.bin
> >> qca/nvm_usb_00130201_gf.bin
> > 
> > I found all the mentioned file names in the buildd log for 20220913-1, so
> > I guess the issue is fixed.
> > Can you verify that and update/close the bug accordingly?
> 
> They are not present.
> 
>   07:14 ❱ dpkg -L firmware-atheros | grep -E '(WCN6855|nvm_usb_00130201)'

Thanks for checking. It turned out my checks were 'incomplete'.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/?qt=grep=WCN6855
does show various results which come very close ...SILICONZ_LITE-3.6510.7 vs
the referenced ...SILICONZ_LITE-3.6510.16.
And one commit is for symlinks to hw2.1

qca/rampatch_usb_00130201.bin is also present in the upstream repo, but 
searching for nvm_usb_00130201_gf.bin did not yield any results.

So this looks like upstream does have most of the needed files, albeit a
slightly older version?
I don't know if anything should be done based on this, but figured I'd share
my findings.

HTH,
  Diederik

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

Bug#1005400: closed by Diederik de Haas (Re: Bug#1005400: firmware-nonfree: Please package AMD SEV firmware.)

[Salvatore Bonaccorso]

Hi,

On Sat, Oct 29, 2022 at 02:06:55PM -0300, Henrique de Moraes Holschuh wrote:
> Like I said the last time this was asked about:
> 
> I am fine either way, but whatever package takes up these firmware
> files must be prepared to make releases *to stable and backports*
> relatively often, and deal with regressions.

> 
> And it is easier to deal with regression issues on firmware when
> they're split to their own packages, really.
> 
> Since SEV firmware is "loaded late" (unlike cpu microcode), it will
> work just fine wherever it is packaged.  So, it really is just an
> issue of how annoying it will be to deal with updates and reverting
> it should it cause regressions.  I personally feel it makes sense to
> group it with the processor firmware, though.
> 
> Meanwhile, if there is an important SEV update pending, please file
> a bug requesting an update on amd64-microcode.

Okay from my view at least, let's keep them provided by
src:amd64-microcode accordingly!

Regards,
Salvatore

Bug#1005400: closed by Diederik de Haas (Re: Bug#1005400: firmware-nonfree: Please package AMD SEV firmware.)

[Henrique de Moraes Holschuh]

Like I said the last time this was asked about:

I am fine either way, but whatever package takes up these firmware files must 
be prepared to make releases *to stable and backports* relatively often, and 
deal with regressions.

And it is easier to deal with regression issues on firmware when they're split 
to their own packages, really.

Since SEV firmware is "loaded late" (unlike cpu microcode), it will work just 
fine wherever it is packaged.  So, it really is just an issue of how annoying 
it will be to deal with updates and reverting it should it cause regressions.  
I personally feel it makes sense to group it with the processor firmware, 
though.

Meanwhile, if there is an important SEV update pending, please file a bug 
requesting an update on amd64-microcode.

-- 
  Henrique de Moraes Holschuh 

Bug#1023049: wsjtx: Fails to exit cleanly

[Hilary Snaden]

Package: wsjtx
Version: 2.6.0~rc4+repack-1
Severity: normal
X-Debbugs-Cc: hilary.sna...@zoho.com

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 ***


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

Kernel: Linux 5.19.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
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)
LSM: AppArmor: enabled

Versions of packages wsjtx depends on:
ii  libboost-filesystem1.74.0  1.74.0-17
ii  libboost-log1.74.0 1.74.0-17
ii  libboost-thread1.74.0  1.74.0-17
ii  libc6  2.35-3
ii  libfftw3-single3   3.3.8-2
ii  libgcc-s1  12.2.0-3
ii  libgfortran5   12.2.0-3
ii  libgomp1   12.2.0-3
ii  libhamlib-utils4.3.1-1+b4
ii  libhamlib4 4.3.1-1+b4
ii  libqcustomplot2.0  2.0.1+dfsg1-6
ii  libqt5core5a   5.15.4+dfsg-5
ii  libqt5gui5 5.15.4+dfsg-5
ii  libqt5multimedia5  5.15.4-2
ii  libqt5multimedia5-plugins  5.15.4-2
ii  libqt5network5 5.15.4+dfsg-5
ii  libqt5serialport5  5.15.4-2
ii  libqt5sql5 5.15.4+dfsg-5
ii  libqt5sql5-sqlite  5.15.4+dfsg-5
ii  libqt5widgets5 5.15.4+dfsg-5
ii  libstdc++6 12.2.0-3
ii  wsjtx-data 2.6.0~rc4+repack-1

Versions of packages wsjtx recommends:
ii  wsjtx-doc  2.6.0~rc4+repack-1

wsjtx suggests no packages.

-- no debconf information

On exiting the program by GUI, not all threads are terminated. "killall wsjtx" 
is necessary to clean up.

Bug#1023048: wsjtx: Crash on configuration change

[Hilary Snaden]

Package: wsjtx
Version: 2.6.0~rc4+repack-1
Severity: normal
X-Debbugs-Cc: hilary.sna...@zoho.com

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 ***


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

Kernel: Linux 5.19.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
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)
LSM: AppArmor: enabled

Versions of packages wsjtx depends on:
ii  libboost-filesystem1.74.0  1.74.0-17
ii  libboost-log1.74.0 1.74.0-17
ii  libboost-thread1.74.0  1.74.0-17
ii  libc6  2.35-3
ii  libfftw3-single3   3.3.8-2
ii  libgcc-s1  12.2.0-3
ii  libgfortran5   12.2.0-3
ii  libgomp1   12.2.0-3
ii  libhamlib-utils4.3.1-1+b4
ii  libhamlib4 4.3.1-1+b4
ii  libqcustomplot2.0  2.0.1+dfsg1-6
ii  libqt5core5a   5.15.4+dfsg-5
ii  libqt5gui5 5.15.4+dfsg-5
ii  libqt5multimedia5  5.15.4-2
ii  libqt5multimedia5-plugins  5.15.4-2
ii  libqt5network5 5.15.4+dfsg-5
ii  libqt5serialport5  5.15.4-2
ii  libqt5sql5 5.15.4+dfsg-5
ii  libqt5sql5-sqlite  5.15.4+dfsg-5
ii  libqt5widgets5 5.15.4+dfsg-5
ii  libstdc++6 12.2.0-3
ii  wsjtx-data 2.6.0~rc4+repack-1

Versions of packages wsjtx recommends:
ii  wsjtx-doc  2.6.0~rc4+repack-1

wsjtx suggests no packages.

-- no debconf information

Changing between different configurations usually results in the program 
crashing. (This may be connected with the program usually failing to exit 
cleanly.)

Bug#1023047: wsjtx: No transmit audio

[Hilary Snaden]

Package: wsjtx
Version: 2.6.0~rc4+repack-1
Severity: important
X-Debbugs-Cc: hilary.sna...@zoho.com

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 ***


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

Kernel: Linux 5.19.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
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)
LSM: AppArmor: enabled

Versions of packages wsjtx depends on:
ii  libboost-filesystem1.74.0  1.74.0-17
ii  libboost-log1.74.0 1.74.0-17
ii  libboost-thread1.74.0  1.74.0-17
ii  libc6  2.35-3
ii  libfftw3-single3   3.3.8-2
ii  libgcc-s1  12.2.0-3
ii  libgfortran5   12.2.0-3
ii  libgomp1   12.2.0-3
ii  libhamlib-utils4.3.1-1+b4
ii  libhamlib4 4.3.1-1+b4
ii  libqcustomplot2.0  2.0.1+dfsg1-6
ii  libqt5core5a   5.15.4+dfsg-5
ii  libqt5gui5 5.15.4+dfsg-5
ii  libqt5multimedia5  5.15.4-2
ii  libqt5multimedia5-plugins  5.15.4-2
ii  libqt5network5 5.15.4+dfsg-5
ii  libqt5serialport5  5.15.4-2
ii  libqt5sql5 5.15.4+dfsg-5
ii  libqt5sql5-sqlite  5.15.4+dfsg-5
ii  libqt5widgets5 5.15.4+dfsg-5
ii  libstdc++6 12.2.0-3
ii  wsjtx-data 2.6.0~rc4+repack-1

Versions of packages wsjtx recommends:
ii  wsjtx-doc  2.6.0~rc4+repack-1

wsjtx suggests no packages.

-- no debconf information

There is no audio output in any mode or with TUNE. Audio from Fldigi on the 
same machine is satisfactory.

Bug#1022252: fuse3: update-initramfs fails on fuse hook

[Joe Pfeiffer]

Update -- it appears mount.fuse has already been added to the initramfs
before this hook is called, so the call to copy_exec fails.  Replacing
the failing line with

copy_exec /sbin/mount.fuse3 /sbin || true

enables the initramfs to be created, though I doubt it's the optimal
solution.

On Sat, 22 Oct 2022 12:16:16 -0600 Joe Pfeiffer  
wrote:
> Package: fuse3
> Version: 3.11.0-1
> Severity: important
> 
> Dear Maintainer,
> 
> Attempting to upgrade my system, I get the following in the output for
> every kernel:
> 
> E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
> 
> Trying to get a little more information, I ran
> 
> update-initramfs -u -v -k all
> 
> and after many lines of output, got:
> 
> Adding binary /usr/lib/x86_64-linux-gnu/libe2p.so.2.3
> Calling hook fuse
> Adding binary /sbin/mount.fuse3
> E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
> 
> *** 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 ***
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (700, 'testing'), (650, 'stable'), (600, 'unstable'), (550, 
> 'experimental'), (500, 'oldstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.18.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: 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 fuse3 depends on:
> ii  adduser3.129
> ii  libc6  2.35-3
> ii  libfuse3-3 3.11.0-1
> ii  lsb-base   11.4
> ii  mount  2.38.1-1.1+b1
> ii  sed4.8-1
> ii  sysvinit-utils [lsb-base]  3.05-6
> 
> fuse3 recommends no packages.
> 
> fuse3 suggests no packages.
> 

Bug#1023046: zabbix: FTBFS: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)

[Mathias Gibbens]

Source: zabbix
Version: 1:6.0.9+dfsg-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

  While rebuilding the reverse build dependencies of another golang
package I'm updating, I noticed that zabbix fails to build in a clean
sid chroot. I suspect this was likely caused by the recent update of
the golang-golang-x-sys package, but I haven't investigated further.

> on.compileArch=`go env GOARCH` -X main.applicationName=zabbix_web_service" -o 
> bin zabbix.com/cmd/zabbix_web_service
> 
> [snip]
> 
> golang.org/x/text/unicode/norm
> # golang.org/x/sys/unix
> vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires go1.17 
> or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice requires 
> go1.17 or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice requires 
> go1.17 or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice requires 
> go1.17 or later (-lang was set to go1.16; check go.mod)
> zabbix.com/pkg/procfs
> # golang.org/x/sys/unix
> vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires go1.17 
> or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice requires 
> go1.17 or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice requires 
> go1.17 or later (-lang was set to go1.16; check go.mod)
> vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice requires 
> go1.17 or later (-lang was set to go1.16; check go.mod)


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

Bug#1023045: apt-listbugs: [INTL:de] Updated German Translation

[Chris Leick]

Package: apt-listbugs
Version: 0.1.37
Severity: wishlist
Tags: l10n patch



Hi,

please find attached the newest German translation.

Kind regards,
Chris

apt_listbugs.tar.gz
Description: application/gzip

Bug#838324: xfdesktop4: drag and drop copies

[Akbarkhon Variskhanov]

Control: tags -1 moreinfo upstream

Related upstream bugs (depending on whether you have Thunar or other
file managers):
https://bugzilla.xfce.org/show_bug.cgi?id=2644
https://bugzilla.xfce.org/show_bug.cgi?id=13929

Bug#1023044: ITP: apksigtool -- parse/verify/clean android apk signing blocks & apks

[FC Stegerman]

Package: wnpp
Severity: wishlist
Owner: FC Stegerman 
X-Debbugs-Cc: debian-de...@lists.debian.org, f...@obfusk.net

* Package name: apksigtool
  Version : 0.5.0
  Upstream Author : FC Stegerman 
* URL : https://github.com/obfusk/apksigtool
* License : AGPLv3+
  Programming Lang: Python
  Description : parse/verify/clean android apk signing blocks & apks

  apksigtool is a tool for parsing android APK Signing Blocks (either
  embedded in an APK or extracted as a separate file, e.g. using
  apksigcopier) and verifying APK signatures.  It can also clean them
  (i.e. remove everything that's not an APK Signature Scheme v2/v3
  Block or verity padding block), which can be useful for reproducible
  builds.

  WARNING: verification is considered EXPERIMENTAL and SHOULD NOT BE
  RELIED ON, please use apksigner instead.

apksigtool is a proposed new optional dependency for diffoscope [1],
allowing it to properly compare APK Signing Blocks.

I am the upstream author and want to package and maintain it for
Debian as well (like I already do with apksigcopier).

I am looking for a sponsor, since I am (still) a Sponsored Maintainer.

NB: v0.5.0 hasn't actually been released yet, but it will be soon.

- FC

[1] https://salsa.debian.org/reproducible-builds/diffoscope/-/issues/320

Bug#1023043: nvda2speechd: FTBFS: error[E0308]: mismatched types, expected `u64`, found `usize`

[Andreas Beckmann]

Source: nvda2speechd
Version: 0.1-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

nvda2speechd recently started to FTBFS.
It probably downloads different crates during build than last week ...

error[E0308]: mismatched types
   --> 
/build/nvda2speechd-0.1/tmp/registry/src/github.com-1ecc6299db9ec823/speech-dispatcher-0.15.1/src/lib.rs:273:36
|
273 | (*c).callback_begin = Some(cb);
|^^ expected `u64`, found `usize`
|
= note: expected fn pointer `unsafe extern "C" fn(u64, u64, _)`
  found fn item `unsafe extern "C" fn(usize, usize, _) {cb}`

error[E0308]: mismatched types
   --> 
/build/nvda2speechd-0.1/tmp/registry/src/github.com-1ecc6299db9ec823/speech-dispatcher-0.15.1/src/lib.rs:274:34
|
274 | (*c).callback_end = Some(cb);
|  ^^ expected `u64`, found `usize`
|
= note: expected fn pointer `unsafe extern "C" fn(u64, u64, _)`
  found fn item `unsafe extern "C" fn(usize, usize, _) {cb}`

error[E0308]: mismatched types
   --> 
/build/nvda2speechd-0.1/tmp/registry/src/github.com-1ecc6299db9ec823/speech-dispatcher-0.15.1/src/lib.rs:275:37
|
275 | (*c).callback_cancel = Some(cb);
| ^^ expected `u64`, found `usize`
|
= note: expected fn pointer `unsafe extern "C" fn(u64, u64, _)`
  found fn item `unsafe extern "C" fn(usize, usize, _) {cb}`

error[E0308]: mismatched types
   --> 
/build/nvda2speechd-0.1/tmp/registry/src/github.com-1ecc6299db9ec823/speech-dispatcher-0.15.1/src/lib.rs:276:36
|
276 | (*c).callback_pause = Some(cb);
|^^ expected `u64`, found `usize`
|
= note: expected fn pointer `unsafe extern "C" fn(u64, u64, _)`
  found fn item `unsafe extern "C" fn(usize, usize, _) {cb}`

error[E0308]: mismatched types
   --> 
/build/nvda2speechd-0.1/tmp/registry/src/github.com-1ecc6299db9ec823/speech-dispatcher-0.15.1/src/lib.rs:277:37
|
277 | (*c).callback_resume = Some(cb);
| ^^ expected `u64`, found `usize`
|
= note: expected fn pointer `unsafe extern "C" fn(u64, u64, _)`
  found fn item `unsafe extern "C" fn(usize, usize, _) {cb}`

error[E0308]: mismatched types
   --> 
/build/nvda2speechd-0.1/tmp/registry/src/github.com-1ecc6299db9ec823/speech-dispatcher-0.15.1/src/lib.rs:278:33
|
278 | (*c).callback_im = Some(cb_im);
| ^ expected `u64`, found `usize`
|
= note: expected fn pointer `unsafe extern "C" fn(u64, u64, _, _)`
  found fn item `unsafe extern "C" fn(usize, usize, _, _) 
{cb_im}`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `speech-dispatcher` due to 6 previous errors

Caused by:
  process didn't exit successfully: `rustc --crate-name speech_dispatcher 
--edition=2021 
/build/nvda2speechd-0.1/tmp/registry/src/github.com-1ecc6299db9ec823/speech-dispatcher-0.15.1/src/lib.rs
 --error-format=json --json=diagnostic-rendered-ansi --crate-type lib 
--emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 
'feature="0_10"' --cfg 'feature="0_11"' --cfg 'feature="default"' -C 
metadata=9e545f3f8c39f4ea -C extra-filename=-9e545f3f8c39f4ea --out-dir 
/build/nvda2speechd-0.1/src/server/target/x86_64-unknown-linux-gnu/release/deps 
--target x86_64-unknown-linux-gnu -L 
dependency=/build/nvda2speechd-0.1/src/server/target/x86_64-unknown-linux-gnu/release/deps
 -L dependency=/build/nvda2speechd-0.1/src/server/target/release/deps --extern 
lazy_static=/build/nvda2speechd-0.1/src/server/target/x86_64-unknown-linux-gnu/release/deps/liblazy_static-ac37d2380b0cc4a6.rmeta
 --extern 
libc=/build/nvda2speechd-0.1/src/server/target/x86_64-unknown-linux-gnu/release/deps/liblibc-49c171b24e724ec2.rmeta
 --extern 
speech_dispatcher_sys=/build/nvda2speechd-0.1/src/server/target/x86_64-unknown-linux-gnu/release/deps/libspeech_dispatcher_sys-a23202149dfc8f5f.rmeta
 --cap-lints allow` (exit status: 1)
warning: build failed, waiting for other jobs to finish...
error: build failed



Andreas


nvda2speechd_0.1-5.log.gz
Description: application/gzip

Bug#995660: clickhouse: FTBFS with OpenSSL 3.0

[Tobias Frost]

Control: tags -1 +patch

MR on salsa: https://salsa.debian.org/debian/ClickHouse/-/merge_requests/3

Bug#1023041: FTBFS: uninstalled files; dh_missing errors out

[Håvard F . Aasen]

On Sat, 29 Oct 2022 16:34:27 +0200 Rene Engelhard  wrote:
> Package: openscap
> Version: 1.3.6+dfsg-2
> Severity: serious
> 
> Hi,
> 
> while trying to build openscap with xmlsec 1.2.35 I noticed the
> following:
> 
> make[1]: Leaving directory '/home/rene/t/openscap-1.3.6+dfsg'
>dh_install
>dh_installdocs
>debian/rules override_dh_installchangelogs
> make[1]: Entering directory '/home/rene/t/openscap-1.3.6+dfsg'
> dh_installchangelogs NEWS
> make[1]: Leaving directory '/home/rene/t/openscap-1.3.6+dfsg'
>dh_installexamples
>dh_installman
>debian/rules override_dh_python3
> make[1]: Entering directory '/home/rene/t/openscap-1.3.6+dfsg'
> dh_python3 -popenscap-utils -ppython3-openscap --shebang=/usr/bin/python3
> I: dh_python3 fs:482: renaming _openscap_py.so to 
> _openscap_py.cpython-310-x86_64-linux-gnu.so
> I: dh_python3 tools:114: replacing shebang in 
> debian/openscap-utils/usr/bin/oscap-docker
> I: dh_python3 tools:114: replacing shebang in 
> debian/openscap-utils/usr/bin/autotailor
> I: dh_python3 tools:114: replacing shebang in 
> debian/openscap-utils/usr/bin/scap-as-rpm
> make[1]: Leaving directory '/home/rene/t/openscap-1.3.6+dfsg'
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
> dh_missing: warning: lib/systemd/system/oscap-remediate.service exists in 
> debian/tmp but is not installed to anywhere
> dh_missing: warning: usr/bin/oscap-remediate-offline exists in debian/tmp but 
> is not installed to anywhere
> dh_missing: warning: usr/libexec/oscap-remediate exists in debian/tmp but is 
> not installed to anywhere
> dh_missing: warning: usr/share/man/man8/oscap-remediate-offline.8 exists in 
> debian/tmp but is not installed to anywhere
> dh_missing: error: missing files, aborting
>   The following debhelper tools have reported what they installed (with 
> files per package)
>* dh_install: libopenscap-dev (4), libopenscap-perl (2), libopenscap25 
> (4), openscap-common (3), openscap-doc (2), openscap-scanner (2), 
> openscap-utils (8), python3-openscap (1)
>* dh_installdocs: libopenscap-dev (3), libopenscap-perl (0), 
> libopenscap25 (0), openscap-common (0), openscap-doc (0), openscap-scanner 
> (1), openscap-utils (0), python3-openscap (0)
>* dh_installexamples: libopenscap-dev (0), libopenscap-perl (0), 
> libopenscap25 (0), openscap-common (0), openscap-doc (0), openscap-scanner 
> (1), openscap-utils (0), python3-openscap (0)
>* dh_installman: libopenscap-dev (0), libopenscap-perl (0), 
> libopenscap25 (0), openscap-common (0), openscap-doc (0), openscap-scanner 
> (1), openscap-utils (7), python3-openscap (0)
>   If the missing files are installed by another tool, please file a bug 
> against it.
>   When filing the report, if the tool is not part of debhelper itself, 
> please reference the
>   "Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
> for debhelper (10.6.3+).
> (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
>   Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
> when only a subset is built
>   If the omission is intentional or no other helper can take care of this 
> consider adding the
>   paths to debian/not-installed.
> make: *** [debian/rules:68: binary] Error 25
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2
> debuild: fatal error at line 1182:
> dpkg-buildpackage -us -uc -ui -b failed
> 
> Doesn't look related to xmlsec1 1.2.35 so I did a cross-check with sid
> and it also FTBFS there.
> 

Would you mind providing a complete build log? I actually can't reproduce
this on my end in unstable. This was also rebuilt in the main archive just
eight days ago, but sure, a lot can happen in that time.


Regards,
Håvard

Bug#1023042: Acknowledgement (conmon: should not depends of golang-go to build)

[Rogerio Bastos]

However it uses golang to run tests too.

On Sat, Oct 29, 2022 at 11:54 AM Debian Bug Tracking System
 wrote:
>
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1023042: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023042.
>
> 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.
>
> Your message has been sent to the package maintainer(s):
>  Podman Packaging Team 
>
> If you wish to submit further information on this problem, please
> send it to 1023...@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.
>
> --
> 1023042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023042
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems



-- 
Rogerio Bastos

Bug#1011660: opensubdiv ftbfs against onetbb/experimental: tbb api break

[Adrian Bunk]

On Thu, May 26, 2022 at 08:45:33AM +0300, Andrius Merkys wrote:
> On 2022-05-26 02:56, M. Zhou wrote:
> > tbb -> onetbb transition breaks this package.
> 
> Relevant part from the build log:
> 
> [  6%] Building CXX object
> opensubdiv/osd/CMakeFiles/osd_cpu_obj.dir/tbbEvaluator.cpp.o
> cd /<>/build/opensubdiv/osd && /usr/bin/c++
> -DGLFW_VERSION_3 -DOPENSUBDIV_HAS_GLSL_COMPUTE
> -DOPENSUBDIV_HAS_GLSL_TRANSFORM_FEEDBACK -DOPENSUBDIV_HAS_OPENGL
> -DOPENSUBDIV_HAS_OPENMP -DOPENSUBDIV_HAS_T
> BB -DOPENSUBDIV_VERSION_STRING=\"3.4.4\" -DOSD_USES_INTERNAL_GLAPILOADER
> -I/<>/opensubdiv -I/<>/glLoader
> -I/<>/build/opensubdiv/osd -g -O2
> -ffile-prefix-map=/<
> >=. -fstack-protector-strong -Wformat -Werror=format-security
> -Wdate-time -D_FORTIFY_SOURCE=2  -O3 -DNDEBUG   -Wall -Wextra
> -Wno-invalid-offsetof -Wno-strict-aliasing -fopenmp -fPIC -MD -MT
> opensubdiv/osd/CMakeF
> iles/osd_cpu_obj.dir/tbbEvaluator.cpp.o -MF
> CMakeFiles/osd_cpu_obj.dir/tbbEvaluator.cpp.o.d -o
> CMakeFiles/osd_cpu_obj.dir/tbbEvaluator.cpp.o -c
> /<>/opensubdiv/osd/tbbEvaluator.cpp
> /<>/opensubdiv/osd/tbbEvaluator.cpp:28:10: fatal error:
> tbb/task_scheduler_init.h: No such file or directory
>28 | #include 
>   |  ^~~
> compilation terminated.

Moving the libtbb-dev build dependency from Build-Depends to 
Build-Conflicts fixes the build.

This might be a reasonable workaround until upstream has fixed it?

> Andrius

cu
Adrian

Bug#1022394: python-trustme: FTBFS: make: *** [debian/rules:4: clean] Error 1

[Nilesh Patra]

Dear Maintainer,

I NMU'd this package since this is directly affecting key packages, and it
is FTBFS for sometime by now.

Please find the debdiff attached. I have also `dgit push`ed it.

Thanks!

-- 
Best,
Nilesh
diff -Nru python-trustme-0.9.0/debian/changelog 
python-trustme-0.9.0/debian/changelog
--- python-trustme-0.9.0/debian/changelog   2022-10-29 20:58:46.0 
+0530
+++ python-trustme-0.9.0/debian/changelog   2021-11-08 01:55:59.0 
+0530
@@ -1,10 +1,3 @@
-python-trustme (0.9.0-1.1) unstable; urgency=medium
-
-  * Non-maintainer Upload.
-  * Drop deprecates "X-Python3-Version: all", fixes FTBFS (Closes: #1022394)
-
- -- Nilesh Patra   Sat, 29 Oct 2022 20:58:46 +0530
-
 python-trustme (0.9.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru python-trustme-0.9.0/debian/control 
python-trustme-0.9.0/debian/control
--- python-trustme-0.9.0/debian/control 2022-10-29 20:58:46.0 +0530
+++ python-trustme-0.9.0/debian/control 2021-11-08 01:55:05.0 +0530
@@ -12,6 +12,7 @@
python3-pytest,
python3-service-identity,
python3-setuptools
+X-Python3-Version: all
 Homepage: https://github.com/python-trio/trustme
 
 Package: python3-trustme


signature.asc
Description: PGP signature

Bug#1023001: Log

[Andrés Segarra]

Ok, feel free to close this bug then. Thanks!

On Sat, 29 Oct 2022, 12:14 pm Patrick Franz,  wrote:

> Hi Andrés,
>
> yes, that is what I mean. Now, what I think happened is the following:
>
> You ran "apt upgrade" which upgraded a bunch of packages. However, a
> number of packages were held back because upgrading them required the
> removal of some other packages (e.g. kwin merged some binary packages,
> nothing strange about this). You then ended up with a hybrid of Plasma
> 5.25 and 5.26 which lead to some weird behaviour such as certain
> plasmoids not working correctly.
>
> The fix was to upgrade everything while allowing the removal of certain
> packages which could've been done with "apt full-upgrade" as well.
> Unfortunately, there is no way around this when packages need to be
> removed.
>
> I'm inclined to close this bug unless you object because there isn't too
> much we can do here. Migrating Plasma from unstable to testing has
> always been challenging.
>
>
> --
> Med vänliga hälsningar
>
> Patrick Franz
>
>
>

Bug#833858: xfce4-power-manager: outdated copyright file and newer versions available

[Akbarkhon Variskhanov]

Hi, Julian. Thanks for reporting.

While goodies.x.o has indeed been decommissioned, the package itself
might have been first downloaded from there. Note the initial
statement in the copyright file. So the first two paragraphs can be
interpreted as "this package was downloaded from goodies.x.o and
debianized by ... in 2008"

Perhaps, it is worth/time to rewrite the copyright file to make it
compliant with DEP 5.

Cheers,
Akbar.

Bug#1023042: conmon: should not depends of golang-go to build

[Rogerio Bastos]

Package: conmon
Version: 2.1.3+ds1-1
Severity: minor

Since the debian/rules script uses pre-compiled go-md2man [1]
installed as build dependency, it is possible to remove golang-go from
debian/control [2] Build-Depends list.

[1] https://salsa.debian.org/podman-team/conmon/-/blob/master/debian/rules#L18
[2] https://salsa.debian.org/podman-team/conmon/-/blob/master/debian/control#L11

Regards,
-- 
Rogerio Bastos

Bug#1023041: FTBFS: uninstalled files; dh_missing errors out

[Rene Engelhard]

Package: openscap
Version: 1.3.6+dfsg-2
Severity: serious

Hi,

while trying to build openscap with xmlsec 1.2.35 I noticed the
following:

make[1]: Leaving directory '/home/rene/t/openscap-1.3.6+dfsg'
   dh_install
   dh_installdocs
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/home/rene/t/openscap-1.3.6+dfsg'
dh_installchangelogs NEWS
make[1]: Leaving directory '/home/rene/t/openscap-1.3.6+dfsg'
   dh_installexamples
   dh_installman
   debian/rules override_dh_python3
make[1]: Entering directory '/home/rene/t/openscap-1.3.6+dfsg'
dh_python3 -popenscap-utils -ppython3-openscap --shebang=/usr/bin/python3
I: dh_python3 fs:482: renaming _openscap_py.so to 
_openscap_py.cpython-310-x86_64-linux-gnu.so
I: dh_python3 tools:114: replacing shebang in 
debian/openscap-utils/usr/bin/oscap-docker
I: dh_python3 tools:114: replacing shebang in 
debian/openscap-utils/usr/bin/autotailor
I: dh_python3 tools:114: replacing shebang in 
debian/openscap-utils/usr/bin/scap-as-rpm
make[1]: Leaving directory '/home/rene/t/openscap-1.3.6+dfsg'
   dh_perl
   dh_link
   dh_strip_nondeterminism
   dh_compress
   dh_fixperms
   dh_missing
dh_missing: warning: lib/systemd/system/oscap-remediate.service exists in 
debian/tmp but is not installed to anywhere
dh_missing: warning: usr/bin/oscap-remediate-offline exists in debian/tmp but 
is not installed to anywhere
dh_missing: warning: usr/libexec/oscap-remediate exists in debian/tmp but is 
not installed to anywhere
dh_missing: warning: usr/share/man/man8/oscap-remediate-offline.8 exists in 
debian/tmp but is not installed to anywhere
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: libopenscap-dev (4), libopenscap-perl (2), libopenscap25 
(4), openscap-common (3), openscap-doc (2), openscap-scanner (2), 
openscap-utils (8), python3-openscap (1)
 * dh_installdocs: libopenscap-dev (3), libopenscap-perl (0), 
libopenscap25 (0), openscap-common (0), openscap-doc (0), openscap-scanner (1), 
openscap-utils (0), python3-openscap (0)
 * dh_installexamples: libopenscap-dev (0), libopenscap-perl (0), 
libopenscap25 (0), openscap-common (0), openscap-doc (0), openscap-scanner (1), 
openscap-utils (0), python3-openscap (0)
 * dh_installman: libopenscap-dev (0), libopenscap-perl (0), 
libopenscap25 (0), openscap-common (0), openscap-doc (0), openscap-scanner (1), 
openscap-utils (7), python3-openscap (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make: *** [debian/rules:68: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -b failed

Doesn't look related to xmlsec1 1.2.35 so I did a cross-check with sid
and it also FTBFS there.

Regards,

Rene

Bug#1023040: nbconvert: downloads artifacts during build

[Paul Gevers]

Source: nbconvert
Version: 6.4.4-2
Severity: serious

Dear maintainer(s),

Why investigating a fix for bug #1021560 I happened to stumble apon
the following lines in the build log [1]:
'''
loading intersphinx inventory from https://docs.python.org/3.6/objects.inv...
loading intersphinx inventory from http://jinja.pocoo.org/docs/objects.inv...
loading intersphinx inventory from 
https://nbformat.readthedocs.io/en/latest/objects.inv...
intersphinx inventory has moved: http://jinja.pocoo.org/docs/objects.inv -> 
https://jinja.palletsprojects.com/en/3.1.x/objects.inv
'''

And indeed, when I disable network during the build I see this instead:
'''
loading intersphinx inventory from https://docs.python.org/3.6/objects.inv...
loading intersphinx inventory from http://jinja.pocoo.org/docs/objects.inv...
loading intersphinx inventory from 
https://nbformat.readthedocs.io/en/latest/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://docs.python.org/3.6/objects.inv' not fetchable 
due to : 
HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded 
with url: /3.6/objects.inv (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary 
failure in name resolution'))
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'http://jinja.pocoo.org/docs/objects.inv' not fetchable 
due to : 
HTTPConnectionPool(host='jinja.pocoo.org', port=80): Max retries exceeded with 
url: /docs/objects.inv (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno 101] Network is 
unreachable'))
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://nbformat.readthedocs.io/en/latest/objects.inv' 
not fetchable due to : 
HTTPSConnectionPool(host='nbformat.readthedocs.io', port=443): Max retries 
exceeded with url: /en/latest/objects.inv (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno 101] Network is 
unreachable'))
'''

That's a violation of the policy section 4.9:
'''
For packages in the main archive, required targets must not attempt network 
access, except, via the loopback interface, to services on the build host that 
have been started by the build.
'''

Paul

[1] 
https://buildd.debian.org/status/fetch.php?pkg=nbconvert=all=6.4.4-2=1657467822=0

Bug#1023039: python-xmlsec: FTBFS with xmlsec1 1.2.35

[Rene Engelhard]

Package: python-xmlsec
Version: 1.3.12-1
Severity: important

Hi,

Given I was already a bit wary about the changed in xmlsec1 I uploaded
it to experimental first.
Which turns out to be a good idea since that one causes oath-toolkit to
FTBFS/fail its tests:

   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:240: cd 
/home/rene/t/python-xmlsec-1.3.12/.pybuild/cpython3_3.10/build; python3.10 -m 
pytest tests
= test session starts ==
platform linux -- Python 3.10.8, pytest-7.1.2, pluggy-1.0.0+repack
rootdir: /home/rene/t/python-xmlsec-1.3.12
plugins: tornado-0.8.1, hypothesis-6.36.0, requests-mock-1.9.3, cov-4.0.0, 
asyncio-0.19.0
asyncio: mode=strict
collected 166 items / 1 skipped

tests/test_xmlsec.py .   [  0%]
tests/test_constants.py  [  3%]
tests/test_doc_examples.py s [  3%]
tests/test_ds.py .FE..   [ 27%]
tests/test_enc.py    [ 42%]
tests/test_keys.py . [ 66%]
tests/test_main.py . [ 74%]
tests/test_templates.py ..   [ 95%]
tests/test_tree.py   [100%]

 ERRORS 
_ ERROR at teardown of TestSignContext.test_sign_case5 _

self = 

def test_sign_case5(self):
"""Should sign a file using a dynamicaly created template, key from PEM 
file and an X509 certificate."""
root = self.load_xml("sign5-in.xml")
sign = xmlsec.template.create(root, consts.TransformExclC14N, 
consts.TransformRsaSha1)
self.assertIsNotNone(sign)
root.append(sign)
ref = xmlsec.template.add_reference(sign, consts.TransformSha1)
xmlsec.template.add_transform(ref, consts.TransformEnveloped)

ki = xmlsec.template.ensure_key_info(sign)
x509 = xmlsec.template.add_x509_data(ki)
xmlsec.template.x509_data_add_subject_name(x509)
xmlsec.template.x509_data_add_certificate(x509)
xmlsec.template.x509_data_add_ski(x509)
x509_issuer_serial = xmlsec.template.x509_data_add_issuer_serial(x509)
xmlsec.template.x509_issuer_serial_add_issuer_name(x509_issuer_serial, 
'Test Issuer')

xmlsec.template.x509_issuer_serial_add_serial_number(x509_issuer_serial, '1')

ctx = xmlsec.SignatureContext()
ctx.key = xmlsec.Key.from_file(self.path("rsakey.pem"), 
format=consts.KeyDataFormatPem)
self.assertIsNotNone(ctx.key)
ctx.key.load_cert_from_file(self.path('rsacert.pem'), 
consts.KeyDataFormatPem)
ctx.key.name = 'rsakey.pem'
self.assertEqual("rsakey.pem", ctx.key.name)

ctx.sign(sign)
>   self.assertEqual(self.load_xml("sign5-out.xml"), root)

tests/test_ds.py:186:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
tests/base.py:132: in assertXmlEqual
self.assertXmlEqual(c1, c2)
tests/base.py:132: in assertXmlEqual
self.assertXmlEqual(c1, c2)
tests/base.py:132: in assertXmlEqual
self.assertXmlEqual(c1, c2)
tests/base.py:132: in assertXmlEqual
self.assertXmlEqual(c1, c2)
tests/base.py:122: in assertXmlEqual
self.fail('text: %r != %r. %s' % (first.text, second.text, msg))
E   AssertionError: text: 'JIQs8tRZIGKLLlyGkKOqMLonGpw=' != None.
=== FAILURES ===
___ TestSignContext.test_sign_case5 

self = 

def test_sign_case5(self):
"""Should sign a file using a dynamicaly created template, key from PEM 
file and an X509 certificate."""
root = self.load_xml("sign5-in.xml")
sign = xmlsec.template.create(root, consts.TransformExclC14N, 
consts.TransformRsaSha1)
self.assertIsNotNone(sign)
root.append(sign)
ref = xmlsec.template.add_reference(sign, consts.TransformSha1)
xmlsec.template.add_transform(ref, consts.TransformEnveloped)

ki = xmlsec.template.ensure_key_info(sign)
x509 = xmlsec.template.add_x509_data(ki)
xmlsec.template.x509_data_add_subject_name(x509)
xmlsec.template.x509_data_add_certificate(x509)
xmlsec.template.x509_data_add_ski(x509)
x509_issuer_serial = xmlsec.template.x509_data_add_issuer_serial(x509)
xmlsec.template.x509_issuer_serial_add_issuer_name(x509_issuer_serial, 
'Test Issuer')

xmlsec.template.x509_issuer_serial_add_serial_number(x509_issuer_serial, '1')

ctx = xmlsec.SignatureContext()
ctx.key = xmlsec.Key.from_file(self.path("rsakey.pem"), 
format=consts.KeyDataFormatPem)

Bug#976052: ITP: zola -- static site generator

[Jonas Smedegaard]

0.16.1 draft 2 needs embedding 46 crates (28 missing, 3 outdated, 15 ahead); 
builds in ~55 minutes and works fine (except for disabled or 
stripped-needing-separate-packaging features as mentioned in packaging TODO 
file).

Main tasks now are to keep package up-to-date with upstream releases, package 
more of the crates currently embedded, and package the stripped JavaScript code.

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/zola/-/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#1023038: oath-toolkit: FTBFS with xmlsec1 1.2.35

[Rene Engelhard]

Source: oath-toolkit
Version: 2.6.7-3
Severity: important

Dear Maintainer,

Hi,

Given I was already a bit wary about the changed in xmlsec1 I uploaded
it to experimental first.
Which turns out to be a good idea since that one causes oath-toolkit to
FTBFS/fail its tests:

make  check-TESTS
make[6]: Entering directory 
'/home/rene/t/oath-toolkit-2.6.7/build/pskctool/tests'
make[7]: Entering directory 
'/home/rene/t/oath-toolkit-2.6.7/build/pskctool/tests'
PASS: tst_hyphen.sh
PASS: tst_roundtrip.sh
FAIL: tst_sign.sh
FAIL: tst_libexamples.sh
PASS: tst_pskctool.sh
==
   pskctool 2.6.7: tests/test-suite.log
==

# TOTAL: 5
# PASS:  3
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tst_libexamples.sh


--- ../../../pskctool/tests/../../libpskc/examples/pskc-hotp-signed.xml 
2020-11-11 18:39:10.0 +
+++ foo 2022-10-29 14:08:07.929083657 +
@@ -38,7 +38,8 @@
 rMxnil6ChoIBvSSPGHhJuj1bW1EPW92JtIa6byrAj1m4RwSviQy2i65YoIdtrhRt
 CWekj2zuL/0szv5rZMCCvxioOCA8znqELEPMfs0Aa/cACD2MZcC4gGXehNCvzYJr
 TmB6lFpxP6f0g6eO7PVcqYN9NCwECxb5Cvx2j2uNlereY35/9oPR6YJx+V7sL+DB
-n6F0mN8OUAFxDamepKdGRApU8uZ35624o/I4
+n6F0mN8OUAFxDamepKdGRApU8uZ35624o/I4
+
 
 
 
FAIL: pskctool --sign output change, commit updated file.
FAIL tst_libexamples.sh (exit status: 1)

FAIL: tst_sign.sh
=

--- ../../../pskctool/tests/pskc-all-signed.xml 2021-04-30 19:24:55.0 
+
+++ tmp-signed.xml  2022-10-29 14:08:07.909083495 +
@@ -38,7 +38,8 @@
 rMxnil6ChoIBvSSPGHhJuj1bW1EPW92JtIa6byrAj1m4RwSviQy2i65YoIdtrhRt
 CWekj2zuL/0szv5rZMCCvxioOCA8znqELEPMfs0Aa/cACD2MZcC4gGXehNCvzYJr
 TmB6lFpxP6f0g6eO7PVcqYN9NCwECxb5Cvx2j2uNlereY35/9oPR6YJx+V7sL+DB
-n6F0mN8OUAFxDamepKdGRApU8uZ35624o/I4
+n6F0mN8OUAFxDamepKdGRApU8uZ35624o/I4
+
 
 
 
FAIL tst_sign.sh (exit status: 1)


Testsuite summary for pskctool 2.6.7

 TOTAL: 5
# PASS:  3
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to oath-toolkit-h...@nongnu.org

make[7]: *** [Makefile:1640: test-suite.log] Error 1
make[7]: Leaving directory 
'/home/rene/t/oath-toolkit-2.6.7/build/pskctool/tests'
make[6]: *** [Makefile:1748: check-TESTS] Error 2
make[6]: Leaving directory 
'/home/rene/t/oath-toolkit-2.6.7/build/pskctool/tests'
make[5]: *** [Makefile:1849: check-am] Error 2
make[5]: Leaving directory 
'/home/rene/t/oath-toolkit-2.6.7/build/pskctool/tests'
make[4]: *** [Makefile:1757: check-recursive] Error 1
make[4]: Leaving directory '/home/rene/t/oath-toolkit-2.6.7/build/pskctool'
make[3]: *** [Makefile:2054: check] Error 2
make[3]: Leaving directory '/home/rene/t/oath-toolkit-2.6.7/build/pskctool'
make[2]: *** [Makefile:406: check-recursive] Error 1
make[2]: Leaving directory '/home/rene/t/oath-toolkit-2.6.7/build'
make[1]: *** [Makefile:706: check] Error 2
make[1]: Leaving directory '/home/rene/t/oath-toolkit-2.6.7/build'
dh_auto_test: error: cd build && make -j16 check "TESTSUITEFLAGS=-j16 
--verbose" VERBOSE=1 returned exit code 2
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

So basically the reference file needs to be updated but then it probably
breaks with 1.2.34...

Regards,

Rene

Bug#1014514: Armadillo library doesnt work correct anymore after update to Debian 11

[Kumar Appaiah]

Dear Andrew,


Apologies for the late response.

On Thu, Jul 07, 2022 at 11:51:47AM +, Schlager, Andreas wrote:
>After updating to Debian 11, the armadillo library for C++ doesn’t work
>properly anymore (e.g. matrix inversions deliver obviously wrong results),
>as can be seen in the example code and results attached.
> 
>Short note about the problem: Assume you have a square matrix B, then
>B*inv(B) should yield the unit matrix. In armadillo this worked without
>problems until the update to Debian 11. Now I get a completely random
>result for B*inv(B). The larger the dimension of B the more severe the
>problem is. There might be a numerical issue that didn’t exist in older
>Debian versions.
> 
> 
> 
>According to the Armadillo-team, this is not a problem of Armadillo itself
>but might be the problem of the versions of libopenblas, liblapack or
>libblas used by Debian 11.
> 
>One of these libraries might be corrupt or incompatible with Debian 11.

In my current installation, I do not have this problem, with libblas3
and liblapack3 version 3.10.1-2. Can you please let me know whether
you still have this issue with your current installation?

Thanks.

Kumar

Bug#1023024: Session crashes when switching back to first display from a second one connected with HDMI when Wayland is used with KDE

[Aurélien COUDERC]

control: tags -1 + wontfix

Dear mYnDstrEAm,



Le 29 octobre 2022 12:29:23 GMT+02:00, mYnDstrEAm  a 
écrit :
>Package: plasma-workspace
>Version: 5.20.5-6
>
>First of all I don't know which package is causing this but it has to do with 
>Wayland and KDE.

Wayland on Debian 11 is provided as a technology preview and is not supported.

You should either upgrade to Debian testing if you need to run Wayland, or stay 
on X11 if you need to run Debian stable.


Happy hacking,
--
Aurélien

Bug#1023037: ITS: goodvibes

[Arnaud Rebillout]

Package: goodvibes
Version: 0.7.2-0.1
Severity: important
X-Debbugs-Cc: sergi...@debian.org

Dear Maintainer,

I would like to maintain this package from now on. Disclaimer: I'm also
the upstream author of this program.

The reason for me taking over this package is that the current
maintainer Elías doesn't seem to be around anymore:

* Dec 2021: I did the last upload (version 0.7.2-0.1), it was sponsored
  by Sergio (CC in this email).
* Apr 2022: I opened a bug to notify of a new upstream release [2], but
  there was no answer so far.

Elias, if you see this email, please answer! You are very welcome to
keep maintaining this package if you wish to do so. Otherwise I'm happy
to take care of it from now on.

All the best,

Arnaud

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993929#12
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009355

Bug#1023036: osk-sdl: Pinephone with FDE can't boot with v0.67-2

[MichaelR]

Package: osk-sdl
Version: 0.67-2
Severity: important

Dear Maintainer,



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

Kernel: Linux 5.15-sunxi64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, 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)

Versions of packages osk-sdl depends on:
ii  cryptsetup2:2.5.0-5
ii  cryptsetup-initramfs  2:2.5.0-5
ii  fonts-dejavu-core 2.37-2
ii  libc6 2.35-3
ii  libcryptsetup12   2:2.5.0-5
ii  libegl1   1.5.0-1
ii  libgcc-s1 12.2.0-3
ii  libgl11.5.0-1
ii  libgles2  1.5.0-1
ii  libsdl2-2.0-0 2.24.1+dfsg-1
ii  libsdl2-ttf-2.0-0 2.20.1+dfsg-1
ii  libstdc++612.2.0-3

osk-sdl recommends no packages.

osk-sdl suggests no packages.

-- debconf information excluded


This was originally reported to Mobian as
https://gitlab.com/mobian1/issues/-/issues/472

Hardware is a Pinephone v1.2b Convergence model using "full disk
encryption".  The system worked properly until upgrading from osk-sdl
v0.67-1 to v0.67-2 in early September 2022. With v0.67-2, after
entering the LUKS passphrase, the screen shows...

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

done.

Begin: Mounting root file system ... Begin: Running /scripts/local-top
... stty: standard

Input: cannot perform all requested operations: Resource temporarily
unavailable

[13.466434] random: osk-sdl: uninitialized urandom read (16 bytes read)

[13.969621] random: osk-sdl: uninitialized urandom read (16 bytes read)

[24.870996] random: crng init done

[41.955178] ps: disabling

[41.958144] dc1sw: disablingup: uninitialized urandom read (4 bytes
read)

[41.961320] avdd-csi: disabling

[41.964854] vcc-1v2-hsic: disabling

[41.968634] usb0-vbus: disabling

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

...and booting does not progress past that.  I have reverted to v0.67-1.

I did a dist-upgrade October 28 and then tried v0.67-2 again and got
the same result.

Bug#996130: clickhouse FTBFS with gcc 11

[Tobias Frost]

Control: tags -1 patch

MR is on salsa, https://salsa.debian.org/debian/ClickHouse/-/merge_requests/1

Patch consists of 3 commits:
missing include -- reported in #996130 -- 20e3e51f
capn removed class in newer version, so version check was wrong -- 045baedf
missing include to in some unit test. -- c1a9cf1d

-- 
tobi

Bug#1023035: gauche: Includes non-free software

[Bastian Germann]

Source: gauche
Severity: serious
Version: 0.9.10-3

debian/ext/srfi/srfi-19.scm has a license that reads "However, this document itself 
may not be modified in any way"
and is documented in d/copyright for lib/srfi-11.scm, which does not have that license (anymore). This clause makes the 
license non-free. Please remove files that are non-free or move the package to the non-free archive section.

Bug#1023034: yelp: info: The file ‘(null)’ does not exist

[Jakub Wilk]

Package: yelp
Version: 42.2-1

I wanted to test yelp's info browsing capabilities, so I run:

$ yelp info:coreutils

But the only thing it displayed was:

The file ‘(null)’ does not exist.


-- System Information:
Architecture: i386

Versions of packages yelp depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  libatk1.0-0  2.46.0-3
ii  libbz2-1.0   1.0.8-5+b1
ii  libc62.35-4
ii  libcairo-gobject21.16.0-6
ii  libcairo21.16.0-6
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.74.1-1
ii  libgtk-3-0   3.24.34-3
ii  libhandy-1-0 1.8.0-1
ii  libharfbuzz0b5.2.0-2
ii  libjavascriptcoregtk-4.1-0   2.38.1-1
ii  liblzma5 5.2.7-0.1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libsoup-3.0-03.2.1-2
ii  libsqlite3-0 3.39.4-1
ii  libwebkit2gtk-4.1-0  2.38.1-1
ii  libxml2  2.9.14+dfsg-1+b1
ii  libxslt1.1   1.1.35-1
ii  libyelp0 42.2-1
ii  man-db   2.11.0-1+b1
ii  python3-distro   1.8.0-1
ii  yelp-xsl 42.1-2

--
Jakub Wilk