Bug#1037496: mdadm: Please restore support for use without systemd as PID 1

[Daniel Baumann]

Hi Mark,

On 6/17/23 19:13, Mark Hindley wrote:
> I am asking gently for the reinstatement of the recently removed non-systemd 
> initscripts.

I hear you, but I prefer not doing this for the stated reasons.

How about getting the mdadm initscript into orphan-sysvinit-scripts? I
read the section about bugs/limitations on orphan-sysvinit-scripts but
can't see anything that would be of concern for mdadm.

Assuming there are no problems of having mdadm initscripts in
orphan-sysvinit-scripts, I think this is the best way forward.

Also, I've added a check to show a note via debconf (only briefly tested):

https://git.progress-linux.org/users/daniel.baumann/debian/packages/mdadm/log/

Regards,
Daniel

Bug#1037304: Addendum

[Brett Gilio]

Hey there comrades,

I would like to add that I can also replicate this same bug on a fresh
install of Debian 12. However, when I upgrade to attempt to use Xorg rather
than Wayland compositing the issue is bypassed. Likewise if I upgrade to
unstable packages. Might this lead to the issue not being gnome-keyring?

Brett

Bug#1038426: renpy: Uncaught exception occurred when attempting to start

[Zach]

Package: renpy
Version: 8.0.3+dfsg-1
Severity: important
X-Debbugs-Cc: zachm...@hotmail.com

The package "renpy" fails to start on an amd64 Debian 12 KDE system. When 
trying to run the package I get a text file
pop-up that says "I'm sorry, but an uncaught exception occurred." and then 
provides some extra information which I
have included below:

After initialization, but before game start.
  File "renpy/common/00preferences.rpy", line 612, in prepare_screen
screen _self_voicing():
  File "renpy/common/00preferences.rpy", line 612, in prepare
screen _self_voicing():
  File "renpy/common/00preferences.rpy", line 622, in prepare
text message:
  File "renpy/common/00preferences.rpy", line 622, in prepare
text message:
ValueError: AST node line range (628, 1) is not valid

-- Full Traceback 

Full traceback:
  File "/usr/share/games/renpy/renpy/bootstrap.py", line 277, in bootstrap
renpy.main.main()
  File "/usr/share/games/renpy/renpy/main.py", line 664, in main
run(restart)
  File "/usr/share/games/renpy/renpy/main.py", line 95, in run
renpy.display.screen.prepare_screens()
  File "/usr/share/games/renpy/renpy/display/screen.py", line 976, in 
prepare_screens
s.ast.prepare_screen()
  File "renpy/common/00preferences.rpy", line 612, in prepare_screen
screen _self_voicing():
  File "renpy/common/00preferences.rpy", line 612, in prepare
screen _self_voicing():
  File "renpy/common/00preferences.rpy", line 622, in prepare
text message:
  File "renpy/common/00preferences.rpy", line 622, in prepare
text message:
  File "/usr/share/games/renpy/renpy/sl2/slast.py", line 84, in compile_expr
return compile(expr, filename, "eval", flags, 1)
ValueError: AST node line range (628, 1) is not valid

Linux-6.1.0-9-amd64-x86_64-with-glibc2.36 x86_64
Ren'Py 8.0.3.22090809u
Ren'Py Launcher 8.0.3.22090809u
Sun Jun 18 03:36:23 2023

However, I have noticed that this output is inconsistent and sometimes outputs 
something different. Here is an
example:

I'm sorry, but an uncaught exception occurred.

After initialization, but before game start.
  File "launcher/game/translations.rpy", line 78, in prepare_screen
screen translate:
  File "launcher/game/translations.rpy", line 78, in prepare
screen translate:
  File "launcher/game/translations.rpy", line 83, in prepare
frame:
  File "launcher/game/translations.rpy", line 83, in prepare
frame:
  File "launcher/game/translations.rpy", line 87, in prepare
window:
  File "launcher/game/translations.rpy", line 87, in prepare
window:
  File "launcher/game/translations.rpy", line 89, in prepare
has vbox
  File "launcher/game/translations.rpy", line 89, in prepare
has vbox
  File "launcher/game/translations.rpy", line 136, in prepare
hbox:
  File "launcher/game/translations.rpy", line 136, in prepare
hbox:
  File "launcher/game/translations.rpy", line 138, in prepare
frame:
  File "launcher/game/translations.rpy", line 138, in prepare
frame:
  File "launcher/game/translations.rpy", line 143, in prepare
has vbox
  File "launcher/game/translations.rpy", line 143, in prepare
has vbox
  File "launcher/game/translations.rpy", line 148, in prepare
frame:
  File "launcher/game/translations.rpy", line 148, in prepare
frame:
  File "launcher/game/translations.rpy", line 150, in prepare
has vbox
  File "launcher/game/translations.rpy", line 150, in prepare
has vbox
  File "launcher/game/translations.rpy", line 152, in prepare
textbutton _("Generate Translations"):
  File "launcher/game/translations.rpy", line 152, in prepare
textbutton _("Generate Translations"):
ValueError: AST node line range (154, 1) is not valid

-- Full Traceback 

Full traceback:
  File "/usr/share/games/renpy/renpy/bootstrap.py", line 277, in bootstrap
renpy.main.main()
  File "/usr/share/games/renpy/renpy/main.py", line 664, in main
run(restart)
  File "/usr/share/games/renpy/renpy/main.py", line 95, in run
renpy.display.screen.prepare_screens()
  File "/usr/share/games/renpy/renpy/display/screen.py", line 976, in 
prepare_screens
s.ast.prepare_screen()
  File "launcher/game/translations.rpy", line 78, in prepare_screen
screen translate:
  File "launcher/game/translations.rpy", line 78, in prepare
screen translate:
  File "launcher/game/translations.rpy", line 83, in prepare
frame:
  File "launcher/game/translations.rpy", line 83, in prepare
frame:
  File "launcher/game/translations.rpy", line 87, in prepare
window:
  File "launcher/game/translations.rpy", line 87, in prepare
window:
  File "launcher/game/translations.rpy", line 89, in prepare
has vbox
  File "launcher/game/translations.rpy", line 89, in prepare
has vbox
  File "launcher/game/translations.rpy", line 136, in prepare
hbox:
  File 

Bug#1038425: runit-services: missing dependency on net-tools for ifconfig

[Olaf Meeuwissen]

Package: runit-services
Version: 0.5.4
Severity: normal

The sv/dhclient/check file uses ifconfig.  This is part of the net-tools
package.  The package is Priority: important, so would normally be
installed.  However, iproute2 mentions in its package description that
`ifconfig` is a legacy tool.  That led me to remove net-tools.  I have
been doing mostly fine without net-tools but this hit me when I pulled
in runit-services, unintentionally, during an upgrade.

I've since uninstalled runit-services but thought I'd let you know.
--
Olaf Meeuwissen

Bug#1038424: hostapd systemd template only works when matching interface name

[kolafl...@kolahilft.de]

Package: hostapd
Version: 2:2.10-12

The file
  /usr/share/doc/hostapd/README.Debian
tells, that you can run hostapd by creating a config
  /etc/hostapd/wifi.conf
and using the template hostapd@wifi.service systemd unit.
So you run
  systemctl enable --now hostapd@wifi.service
to enable and start it.
Side note:
  systemctl command not mentioned in the README.debian.
  But that's how systemd unit templates are handled as far as
  I know. Maybe this should be added to the README.debian.

PROBLEM:
That only works if your wlan interface is namend "wifi".
If your interface is named differently, the templated name has to be 
changed accordingly. E.g. for "wlan0": hostapd@wlan0.service



If the name doesn't matched the systemd unit is somehow immediately 
stopped again:


Jun 18 04:53:00 myhost systemd[1]: Starting hostapd@wifi.service - 
Access point and authentication server for Wi-Fi and Ethernet (wifi)...
Jun 18 04:53:01 myhost hostapd[45039]: wlan0: interface state 
UNINITIALIZED->COUNTRY_UPDATE
Jun 18 04:53:01 myhost hostapd[45039]: wlan0: interface state 
COUNTRY_UPDATE->ENABLED

Jun 18 04:53:01 myhost hostapd[45039]: wlan0: AP-ENABLED
Jun 18 04:53:01 myhost systemd[1]: Started hostapd@wifi.service - Access 
point and authentication server for Wi-Fi and Ethernet (wifi).
Jun 18 04:53:01 myhost systemd[1]: Stopping hostapd@wifi.service - 
Access point and authentication server for Wi-Fi and Ethernet (wifi)...
Jun 18 04:53:02 myhost systemd[1]: hostapd@wifi.service: Deactivated 
successfully.
Jun 18 04:53:02 myhost systemd[1]: Stopped hostapd@wifi.service - Access 
point and authentication server for Wi-Fi and Ethernet (wifi).


IF this behavior is not intended, it's a bug.

IF this behavior is intended, the README.Debian should mention it!
-> "documentation bug"
(just spend 30 minutes figuring it out)



Kind regards,
kolAflash


OpenPGP_0xEA831012D83C3408.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038423: ITP: maven-native -- plugin to compile c and c++ source via maven

[Joseph Nahmias]

Package: wnpp
Severity: wishlist
Owner: Joseph Nahmias 
X-Debbugs-Cc: debian-de...@lists.debian.org, mojohaus-...@googlegroups.com, 
pkg-java-maintain...@lists.alioth.debian.org, j...@nahmias.net

* Package name: maven-native
  Version : 1.0-alpha-11
  Upstream Contact: mojohaus-...@googlegroups.com,
* URL : https://www.mojohaus.org/maven-native/native-maven-plugin/
* License : Expat
  Programming Lang: Java
  Description : plugin to compile c and c++ source via maven

 This maven plugin creates a custom build lifecycle suited to compiling
 native C and C++ code using standard compilers such as gcc.
 .
 Use cases / usage examples include:
 .
  * Building a DLL with JNI.
  * Building a standard Unix shared library.
  * Building a static library, including ranlib.

Bug#1037190: re-introduction of epoch? #1037190 dhcpcd: version is lower than in wheezy

[Martin-Éric Racine]

On Sat, Jun 17, 2023 at 11:44 PM Andreas Beckmann  wrote:
>
> On 17/06/2023 20.30, Martin-Éric Racine wrote:
> > This is what I would do if the archive policy demands it. Won't affect
> > transitional dhcpcd5 or dhcpcd-base.
>
> Ack.
>
> I'm not sure whether the transitional dhcpcd5 package should have a
> versioned dependency on the "right" dhcpcd, either
> (= 1:${binary:Version}) or (>= 1:9). IIRC you need to add the epoch
> manually in the former case.

Merely re-introducing the epoch for bin:dhcpcd ought to be enough.
dhcpcd5 depends on a versionless dhcpcd. Thus:

override_dh_gencontrol:
dh_gencontrol --package=dhcpcd -- -v1:$(DEB_VERSION_UPSTREAM_REVISION)
dh_gencontrol --remaining-packages

Would probably be enough to make this policy-compliant again.

Martin-Éric

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

[R.L. Nicholas]

Package: ntpsec
Version: 1.2.2+dfsg1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: forest.ow...@riseup.net

Dear Maintainer,

I updated the Debian release from bullseye to bookworm.  With that update
the ntp package (ntpd 4.2.8p15) was replaced by ntpsec.  The ntpsec version
of ntpd starts as expected, but randomly crashes in a few hours.  It reports
the following information to the kern.log file:
2023-06-17T01:12:52.873519+00:00 karita kernel: [258683.650167] ntpd[23269]: 
segfault at 10 ip 7f6d3ece0ab3 sp 7ffc9c364830 error 4 in 
libcrypto.so.3[7f6d3ecc5000+278000] likely on CPU 1 (core 0, socket 1)
2023-06-17T01:12:52.873554+00:00 karita kernel: [258683.650185] Code: 1f 84 00 
00 00 00 00 48 83 ec 08 48 c7 c0 ff ff ff ff 48 85 ff 0f 84 63 04 00 00 48 85 
d2 0f 84 5a 04 00 00 41 ba 00 08 00 10 <0f> 10 07 0f 57 e4 44 23 15 e4 fa 39 00 
48 8d 42 10 81 fe 00 01 00

Obviously, once the software crashes it stops functioning.

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/2 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)
LSM: AppArmor: enabled

Versions of packages ntpsec depends on:
ii  adduser3.134
ii  init-system-helpers1.65.2
ii  libbsd00.11.7-2
ii  libc6  2.36-9
ii  libcap21:2.66-4
ii  libssl33.0.9-1
ii  lsb-base   11.6
ii  netbase6.4
ii  python33.11.2-1+b1
ii  python3-ntp1.2.2+dfsg1-1
ii  sysvinit-utils [lsb-base]  3.06-4
ii  tzdata 2023c-5

Versions of packages ntpsec recommends:
ii  cron [cron-daemon]  3.0pl1-162
ii  systemd 252.6-1

Versions of packages ntpsec suggests:
ii  apparmor   3.0.8-3
pn  certbot
pn  ntpsec-doc 
pn  ntpsec-ntpviz  

-- no debconf information

Bug#1038421: Fix for CVE-2022-45188

[Daniel Markstedt]

Package: netatalk
Version: 3.1.15~ds-1
X-Debbugs-Cc: pkg-netatalk-de...@lists.alioth.debian.org

This bug is to record that the fix for CVE-2022-45188 has already been
included with netatalk 3.1.15~ds-1.

It is still flagged as unresolved for bookworm, which is not correct.

See https://github.com/Netatalk/netatalk/releases/tag/netatalk-3-1-15
for the changelog.

Bug#1037457:

[Zach Berger]

This is still reproducible on the kernel just released into Sid, Linux 
6.3.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.3.7-1 (2023-06-12) x86_64 
GNU/Linux

Bug#1035736: neovim: Turning off the banner causes the cursor to flicker permanently and CPU usage goes up

[James McCoy]

On Mon, May 08, 2023 at 03:13:41PM +0200, Bastian Venthur wrote:
> Turning off the netrw's banner (netrw-I), via g:netrw_banner and or by 
> pressing
> "I" in the Explorer causes the cursor to flicker permanently and the CPU usage
> goes up to 50% or so.

I can't reproduce this.  “nvim --clean” followed by “:e .” and pressing
I doesn't result in flickering or high CPU usage.

If this “nvim --clean” works fine, then I'd suggest looking through your
config and “:scriptnames” to see what may be affecting it.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#1038420: rust-rustls - autopkgtest failure with new base64.

[Peter Michael Green]

Package: rust-rustls
Version: 0.20.8-4
Severity: serious
Tags: trixie, sid

The autopkgtest for rust-rustls autopkgtest depends on rust-base64 0.13 but
unstable now has 0.21 and we are trying to get it into trixie.

Since your package does not use skip-not-installable this is a hard failure
and is blocking the testing migration of rust-rustls-pemfile and hence
rust-base64.

When upstream bumped the dependency they made some code
changes, but it looks like said code changes were only needed
to fix deprecation warnings. Simply bumping the dependency in
Cargo.toml and debian/tests/control is enough to make the autopkgtest
pass.

Debdiff attatched, if this is still outstanding in a week or so and other
blockers for testing migration are cleared, I will probablly NMU it.
diff -Nru rust-rustls-0.20.8/debian/changelog 
rust-rustls-0.20.8/debian/changelog
--- rust-rustls-0.20.8/debian/changelog 2023-02-03 13:57:58.0 +
+++ rust-rustls-0.20.8/debian/changelog 2023-06-18 01:01:18.0 +
@@ -1,3 +1,10 @@
+rust-rustls (0.20.8-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump base64 dev-dependency to 0.21.
+
+ -- Peter Michael Green   Sun, 18 Jun 2023 01:01:18 +
+
 rust-rustls (0.20.8-4) unstable; urgency=medium
 
   * add patch 1001 to add feature constraints to tests
diff -Nru rust-rustls-0.20.8/debian/patches/2004_bump_base64.patch 
rust-rustls-0.20.8/debian/patches/2004_bump_base64.patch
--- rust-rustls-0.20.8/debian/patches/2004_bump_base64.patch1970-01-01 
00:00:00.0 +
+++ rust-rustls-0.20.8/debian/patches/2004_bump_base64.patch2023-06-18 
01:01:00.0 +
@@ -0,0 +1,11 @@
+--- rust-rustls-0.20.8.orig/rustls/Cargo.toml
 rust-rustls-0.20.8/rustls/Cargo.toml
+@@ -37,7 +37,7 @@ log = "0.4.4"
+ rustls-native-certs = "0.6"
+ criterion = "0.3.0"
+ rustls-pemfile = "1.0.0"
+-base64 = "0.13.0"
++base64 = "0.21.0"
+ 
+ [[example]]
+ name = "bogo_shim"
diff -Nru rust-rustls-0.20.8/debian/patches/series 
rust-rustls-0.20.8/debian/patches/series
--- rust-rustls-0.20.8/debian/patches/series2023-02-03 13:56:11.0 
+
+++ rust-rustls-0.20.8/debian/patches/series2023-06-18 01:00:10.0 
+
@@ -1,3 +1,4 @@
 1001_feature_constraints.patch
 2001_native_certs.patch
 2003_network_access.patch
+2004_bump_base64.patch
diff -Nru rust-rustls-0.20.8/debian/tests/control 
rust-rustls-0.20.8/debian/tests/control
--- rust-rustls-0.20.8/debian/tests/control 2023-02-02 19:14:08.0 
+
+++ rust-rustls-0.20.8/debian/tests/control 2023-06-18 00:58:44.0 
+
@@ -4,7 +4,7 @@
 Features: test-name=rust-rustls-0.20:@
 Depends:
  dh-cargo (>= 18),
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
  librust-criterion-0.3+default-dev,
  librust-docopt-1+default-dev,
  librust-env-logger-0.9+default-dev,
@@ -27,7 +27,7 @@
 Features: test-name=rust-rustls-0.20:dangerous_configuration
 Depends:
  dh-cargo (>= 18),
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
  librust-criterion-0.3+default-dev,
  librust-docopt-1+default-dev,
  librust-env-logger-0.9+default-dev,
@@ -48,7 +48,7 @@
 Features: test-name=rust-rustls-0.20:quic
 Depends:
  dh-cargo (>= 18),
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
  librust-criterion-0.3+default-dev,
  librust-docopt-1+default-dev,
  librust-env-logger-0.9+default-dev,
@@ -69,7 +69,7 @@
 Features: test-name=rust-rustls-0.20:secret_extraction
 Depends:
  dh-cargo (>= 18),
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
  librust-criterion-0.3+default-dev,
  librust-docopt-1+default-dev,
  librust-env-logger-0.9+default-dev,
@@ -90,7 +90,7 @@
 Features: test-name=rust-rustls-0.20:tls12
 Depends:
  dh-cargo (>= 18),
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
  librust-criterion-0.3+default-dev,
  librust-docopt-1+default-dev,
  librust-env-logger-0.9+default-dev,
@@ -111,7 +111,7 @@
 Features: test-name=rust-rustls-0.20:read_buf
 Depends:
  dh-cargo (>= 18),
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
  librust-criterion-0.3+default-dev,
  librust-docopt-1+default-dev,
  librust-env-logger-0.9+default-dev,
@@ -133,7 +133,7 @@
 Features: test-name=rust-rustls-0.20:
 Depends:
  dh-cargo (>= 18),
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
  librust-criterion-0.3+default-dev,
  librust-docopt-1+default-dev,
  librust-env-logger-0.9+default-dev,
@@ -154,7 +154,7 @@
 Features: test-name=rust-rustls-0.20:default
 Depends:
  dh-cargo (>= 18),
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
  librust-criterion-0.3+default-dev,
  librust-docopt-1+default-dev,
  librust-env-logger-0.9+default-dev,
@@ -175,7 +175,7 @@
 Features: test-name=rust-rustls-0.20:logging
 Depends:
  dh-cargo (>= 18),
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
  librust-criterion-0.3+default-dev,
  

Bug#1038419: installation-reports: [arm64] Installation hangs on "Configuring grub-efi-arm64 (arm64)"

[Joel May]

Package: installation-reports
Severity: important

Boot method: USB
Image version: 
https://cdimage.debian.org/debian-cd/current/arm64/bt-cd/debian-12.0.0-arm64-netinst.iso.torrent
Date: 2023-06-17

Machine: Lenovo HR350A server
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
rootfs rootfs   263117412  216724 262900688   1% /
tmpfs  tmpfs 26311744 144  26311600   1% /run
devtmpfs   devtmpfs 131020564   0 131020564   0% /dev
/dev/sdc1  iso9660 612352  612352 0 100% /cdrom
/dev/sdb2  ext4 237753112 1161200 224441896   1% /target
/dev/sdb1  vfat5240006224517776   2% /target/boot/efi


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

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

Comments/Problems:

Installation hangs on "Configuring grub-efi-arm64 (arm64)".

When the installer is stuck in this state, other commands from the shell also 
hang, such as
`efibootmgr`
`cat /sys/firmware/efi/efivars/Boot-...`
`modprobe` (called by `reportbug installation-report`).

Using the expert install to disable updating NVRAM variables works around the 
problem.
For reference, Debian Bullseye, Ubuntu 22.04.2, and RHEL 9.2 successfully 
install the UEFI bootloader on this system.

-- Package-specific info:
- dmesg
[  396.440480] Adding 1000444k swap on /dev/sda3.  Priority:-2 extents:1 
across:1000444k SSFS
[  398.952999] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota 
mode: none.
[  398.963417] FAT-fs (sda1): Volume was not properly unmounted. Some data may 
be corrupt. Please run fsck.
[  850.581829] fuse: init (API version 7.37)
[  887.150168] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  887.150177] rcu: 1-...0: (1 GPs behind) idle=dae4/1/0x4000 
softirq=11625/11625 fqs=2163
[  887.150185]  (detected by 7, t=5252 jiffies, g=68329, q=166 ncpus=32)
[  887.150188] Task dump for CPU 1:
[  887.150190] task:kworker/u64:0   state:R  running task stack:0 pid:9 
ppid:2  flags:0x000a
[  887.150197] Workqueue: efi_rts_wq efi_call_rts
[  887.150206] Call trace:
[  887.150208]  __switch_to+0xf0/0x170
[  887.150214]  0x0
[  950.170167] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[  950.170173] rcu: 1-...0: (1 GPs behind) idle=dae4/1/0x4000 
softirq=11625/11625 fqs=7867
[  950.170180]  (detected by 16, t=21007 jiffies, g=68329, q=296 ncpus=32)
[  950.170183] Task dump for CPU 1:
[  950.170184] task:kworker/u64:0   state:R  running task stack:0 pid:9 
ppid:2  flags:0x000a
[  950.170190] Workqueue: efi_rts_wq efi_call_rts
[  950.170196] Call trace:
[  950.170198]  __switch_to+0xf0/0x170
[  950.170203]  0x0
[ 1013.190168] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 1013.190173] rcu: 1-...0: (1 GPs behind) idle=dae4/1/0x4000 
softirq=11625/11625 fqs=13685
[ 1013.190180]  (detected by 0, t=36762 jiffies, g=68329, q=343 ncpus=32)
[ 1013.190183] Task dump for CPU 1:
[ 1013.190184] task:kworker/u64:0   state:R  running task stack:0 pid:9 
ppid:2  flags:0x000a
[ 1013.190191] Workqueue: efi_rts_wq efi_call_rts
[ 1013.190197] Call trace:
[ 1013.190198]  __switch_to+0xf0/0x170
[ 1013.190204]  0x0
[ 1076.210168] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 1076.210173] rcu: 1-...0: (1 GPs behind) idle=dae4/1/0x4000 
softirq=11625/11625 fqs=19448
[ 1076.210179]  (detected by 11, t=52517 jiffies, g=68329, q=373 ncpus=32)
[ 1076.210182] Task dump for CPU 1:
[ 1076.210183] task:kworker/u64:0   state:R  running task stack:0 pid:9 
ppid:2  flags:0x000a
[ 1076.210189] Workqueue: efi_rts_wq efi_call_rts
[ 1076.210195] Call trace:
[ 1076.210196]  __switch_to+0xf0/0x170
[ 1076.210201]  0x0
[ 1088.482198] INFO: task khugepaged:188 blocked for more than 120 seconds.
[ 1088.482205]   Not tainted 6.1.0-9-arm64 #1 Debian 6.1.27-1
[ 1088.482207] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 1088.482209] task:khugepaged  state:D stack:0 pid:188   ppid:2  
flags:0x0008
[ 1088.482214] Call trace:
[ 1088.482215]  __switch_to+0xf0/0x170
[ 1088.482221]  __schedule+0x340/0x940
[ 1088.482225]  schedule+0x58/0xf0
[ 1088.482228]  schedule_timeout+0x14c/0x180
[ 1088.482231]  __wait_for_common+0xd4/0x254
[ 1088.482234]  wait_for_completion+0x28/0x3c
[ 1088.482238]  __flush_work.isra.0+0x180/0x2dc
[ 1088.482244]  flush_work+0x18/0x2c
[ 1088.482246]  __lru_add_drain_all+0x1a0/0x260
[ 1088.482250]  lru_add_drain_all+0x1c/0x30
[ 1088.482253]  

Bug#1038418: upgrade-reports: pipewire-pulse replaces pulseaudio when upgrading from bullseye to bookworm

[Elija Goitke]

Package: upgrade-reports
Severity: normal

The described issue can be reproduced on a fresh bullseye install made
through the latest
official bullseye installer. The issue only concerns the KDE Plasma desktop
environment version of Debian.

My previous release is: bullseye
I am upgrading to: bookworm
Upgrade date: 17.6.2023
Method: Minimal upgrade steps according to
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-
upgrading.en.html

Contents of /etc/apt/sources.list:
 untouched, except changing "bullseye" to "bookworm" in order to
upgrade.

- Were there any non-Debian packages installed before the upgrade? If
   so, what were they?
 No

- Was the system pre-update a 'pure' system only containing packages
   from the previous release? If not, which packages were not from that
   release?
 Yes, fresh install directly from official installer.

- Did any packages fail to upgrade?
 No

- Were there any problems with the system after upgrading?
 Yes, see below


Further Comments/Problems:

A fresh Debian 12 Bookworm installation (directly from the official
installer)
with the KDE Plasma desktop environment uses the pulseaudio server as a
default audio
middleware, but when upgrading from a fresh "off-the-shelf" Debian
11 Bullseye to 12 Bookworm (with the steps as advised by
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-
upgrading.en.html) pipewire-pulse and wireplumber get installed
automatically (apparently per
suggestion by package plasma-pa) and replace
pulseaudio from there on. Pulseaudio remains installed,
only being suppressed by pipewire-pulse.

I noticed this first on my own private Debian installation, where I recently
upgraded. I was also able to reproduce this on a fresh Debian 11 Bullseye
install where I then upgraded to Bookworm. (according to upgrade guidelines)

This behavior does not break system sound or usability as far as I can
assess, but since it
does deviate from the default KDE Plasma setup that you get from installing
Debian Bookworm directly from installer rather than upgrading to it, as
well as changing the
sound server from pulseaudio to pipewire without informing or asking the
user,
I assume this is still unwanted behavior and hence a bug.

Best regards.

Bug#1036804: RFP: shadowsocks-rust -- a rust port of shadowsocks

[4tn223y6zity]

Debian now has shadowsocks-libev, but it is now considered legacy and probably 
won't be updated.

shadowsocks-rust is now basically main reference implementation with all 
improvements and fixes. Please add it.

Bug#1000072: New upstream version

[Marcelo Jorge Vieira]

Hi,

I've prepared an NMU and I will upload it to sid.

https://salsa.debian.org/sk-guest/libapache2-mod-qos/-/merge_requests/5


Cheers,

-- 
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
https://metaldot.alucinados.com



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

Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore

[Mike Hommey]

On Sun, Jun 18, 2023 at 08:15:43AM +0900, Mike Hommey wrote:
> On Sun, Jun 18, 2023 at 06:09:57AM +0900, Mike Hommey wrote:
> > On Sat, Jun 17, 2023 at 01:20:30AM +0200, Diederik de Haas wrote:
> > > Control: tag -1 -moreinfo
> > > Control: found -1 6.1.20-1
> > > 
> > > On Saturday, 17 June 2023 01:00:58 CEST Mike Hommey wrote:
> > > > > 6.1.12-1 and 6.1.15-1 are good. 6.1.20-1 is the first broken one.
> > > 
> > > Excellent, thanks. This is already very useful.
> > > 
> > > > > > A `git bisect` would be best, but grabbing these intermediate 
> > > > > > versions
> > > > > > (from snapshot.debian.org) is the quickest way to narrow the range.
> > > > > 
> > > > > Last time I tried to build Debian linux kernels, it was spending a 
> > > > > large
> > > > > amount of time building packages I don't need, and finding the right
> > > > > incantation to reduce that load was not straightforward, and I can't
> > > > > find my notes, unfortunately. If you have instructions I can use to go
> > > > > through a bisect in a quick manner, I'm all ears.
> > > > 
> > > > Although, if you have instructions to just build the one module and 
> > > > avoid
> > > > rebooting, that would be even better.
> > > 
> > > I _think_ building just one module or without rebooting is not possible.
> > > 
> > > The 'official' instructions: 
> > > https://wiki.debian.org/DebianKernel/GitBisect
> > > 
> > > I know some things to reduce what gets build, like f.e. what's described 
> > > here:
> > > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.7
> > > And there's also a facility to work with _build profiles_.
> > > But I don't know if or how that could be applied to the 'official' 
> > > instructions
> > > as that deals with the upstream kernel source directly.
> > > 
> > > Hopefully one of the (more) experienced people chimes in with 
> > > actual useful things ...
> > 
> > I was able to build the relevant module only. The regression comes from
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=337c3624bcb008f92bab38c8fc4cdf97ae5313a2
> 
> I sent a patch upstream, but it's not showing up on the archives yet.
> I'll update with a link when I have one.

Here we go:
https://patchwork.kernel.org/project/linux-input/patch/20230617230957.6mx73th4blv7o...@glandium.org/

Mike

Bug#1011401: mount: umount bash completion explodes awk on some paths

[наб]

Control: found -1 2.38.1-5+b1
Control: tags -1 + fixed-upstream - help

On Sun, Sep 04, 2022 at 12:07:35PM +0200, Andreas Henriksson wrote:
> Thanks for narrowing this down. Could you please submit your findings
> to the upstream mailing list? (util-linux at vger.kernel.org)
You removed me from CC so I didn't get your mail
(submitters don't get bug mail forwarded by default);
re-discovered this report after I got
  nabijaczleweli@tarta:~/uwu/SunOS 2.0 (Tape) [Sun-2]/tape1$ sudo umount 0awk: 
cmd. line:8: (FILENAME=- FNR=1) fatal: invalid regexp: Invalid range end: 
/^/home/nabijaczleweli/uwu/SunOS 2.0 (Tape) [Sun-2]/tape1/
  awk: cmd. line:8: (FILENAME=- FNR=1) fatal: invalid regexp: Invalid range 
end: /^/home/nabijaczleweli/uwu/SunOS 2.0 (Tape) [Sun-2]/tape1/
  awk: cmd. line:8: (FILENAME=- FNR=1) fatal: invalid regexp: Invalid range 
end: /^/home/nabijaczleweli/uwu/SunOS 2.0 (Tape) [Sun-2]/tape1/
(yes, same path; same archive) today on bookworm.

I tested the util-linux 2.39 tarball to prepare a patch:
the completion has changed, and now escapes the path before using it as
a regex; I've validated that
  $ (cd ~/uwu/SunOS\ 2.0\ \(Tape\)\ \[Sun-2]/tape1; _umount_points_list)
  awk: cmd. line:8: (FILENAME=- FNR=1) fatal: invalid regexp: Invalid range 
end: /^/home/nabijaczleweli/uwu/SunOS 2.0 (Tape) [Sun-2]/tape1/
  $ . /usr/share/bash-completion/completions/umount
  $ (cd ~/uwu/SunOS\ 2.0\ \(Tape\)\ \[Sun-2]/tape1; _umount_points_list)
  awk: cmd. line:8: (FILENAME=- FNR=1) fatal: invalid regexp: Invalid range 
end: /^/home/nabijaczleweli/uwu/SunOS 2.0 (Tape) [Sun-2]/tape1/
  $ . ./bash-completion/umount
  $ (cd ~/uwu/SunOS\ 2.0\ \(Tape\)\ \[Sun-2]/tape1; _umount_points_list)
  /home/nabijaczleweli
  /proc
  # ...
  /home/nabijaczleweli
  ~/uwu/SunOS\ 2.0\ \(Tape\)\ \[Sun-2\]/tape1/04.d
  ./04.d
  04.d
  /home/nabijaczleweli/uwu/SunOS\ 2.0\ \(Tape\)\ \[Sun-2\]/tape1/04.d

Re-tagging appropriately.

Best,
наб


signature.asc
Description: PGP signature

Bug#1038417: jdupes: Broken hard linking

[Joao Eriberto Mota Filho]

Package: jdupes
Version: 1.24.0-1
Severity: important
Tags: upstream patch
X-Debbugs-Cc: Jody Bruchon 

The upstream, Jody Bruchon, notified me about hard linking is not working in
1.24.0 version. The solution for this issue is to use the following commits
from the official repository[1]:

https://github.com/jbruchon/jdupes/commit/9f66732
https://github.com/jbruchon/jdupes/commit/70dc66d
https://github.com/jbruchon/jdupes/commit/62f365d

[1] https://github.com/jbruchon/jdupes

Thanks Jody!

Eriberto

Bug#1038383: lsb_release: please add the ability to guess_release_from_apt()

[Harshula]

Hi Santiago,

On 18/6/23 03:04, Gioele Barabucci wrote:

One can use the mechanism discussed in section 5.14.3 of the Developer's 
Reference [1]:


1) Block the automatic migration via britney/excuses.
2) When a new version is released, dput two different versions: one into 
unstable and one into testing-proposed-updates.


To reduce the amount of work needed for each update of `base-files`, 
`/etc/os-release` can be moved to package like `debian-version-info`, so 
the manual double upload must be done only once per release cycle.


[1] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#direct-updates-to-testing


What are your thoughts on this proposal?

Thanks,
Harshula

Bug#1036804: RFP: shadowsocks-rust -- a rust port of shadowsocks

[4tn223y6zity]

Also, this might be of help: https://gitlab.com/xdeb/shadowsocks-rust

Bug#1038416: proftpd-basic: proftpd service fails to start on next server reboot

[Predrag Damnjanovic]

Package: proftpd-basic
Version: 1.3.8+dfsg-4
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Even on clean Debian12, with just proftpd installed, proftpd service will 
not start om next server reboot.

   * What exactly did you do (or not do) that was effective (or ineffective)?
Service is installed this way:
# apt install proftpd
Note, selecting 'proftpd-core' instead of 'proftpd'
The following additional packages will be installed:
  libhashkit2 libhiredis0.14 libmemcached11 libmemcachedutil2 
libpcre2-posix3
The following NEW packages will be installed:
  libhashkit2 libhiredis0.14 libmemcached11 libmemcachedutil2 
libpcre2-posix3 proftpd-core

I also did:
# systemctl enable proftpd
Output is:
Synchronizing state of proftpd.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable proftpd

...but on next reboot proftpd service will not be automatically started.

So, after reboot, if I do:
# systemctl status proftpd
Output is:
○ proftpd.service - ProFTPD FTP Server
 Loaded: loaded (/lib/systemd/system/proftpd.service; enabled; preset: 
enabled)
 Active: inactive (dead)

It's clearly not started.

If I do:
# grep 'proftpd' /var/log/syslog
Output is only this line:
2023-06-17T21:34:40.157071+00:00 vesna systemd[1]: Listening on 
proftpd.socket - ProFTPD FTP Server Activation Socket.

Also:
# ps -Af | grep 'proftp'
gives nothing.

But if I run:
# cat /var/log/proftpd/proftpd.log
I get:
2023-06-17 21:34:19,440 vesna proftpd[35867] xxx.xxx.xxx.xxx: ProFTPD 
killed (signal 15)
2023-06-17 21:34:19,440 vesna proftpd[35867] xxx.xxx.xxx.xxx: ProFTPD 1.3.8 
standalone mode SHUTDOWN
2023-06-17 21:40:21,401 vesna proftpd[2593] xxx.xxx.xxx.xxx: Failed binding 
to ::, port 21: Address already in use
2023-06-17 21:40:21,402 vesna proftpd[2593] xxx.xxx.xxx.xxx: Check the 
ServerType directive to ensure you are configured correctly
2023-06-17 21:40:21,402 vesna proftpd[2593] xxx.xxx.xxx.xxx: Check to see 
if inetd/xinetd, or another proftpd instance, is already using ::, port 21
2023-06-17 21:40:21,402 vesna proftpd[2593] xxx.xxx.xxx.xxx: Unable to 
start proftpd; check logs for more details

Looks like it is killed by something (inetd?), but when incoming connection 
comes, it says port 21 is in use.

Then, when I check netstat:
# netstat -tuapen | grep ':21'
I get:
tcp6   0  0 :::21   :::*LISTEN  
0  15323  1/init

Now if I start proftpd manually:
# systemctl start proftpd

# netstat -tuapen | grep ':21'
gives:
tcp6   0  0 :::21   :::*LISTEN  
10931548  6990/proftpd: (acce 

# ps -Af | grep 'proftp'
gives:
proftpd 6990   1  0 22:25 ?00:00:00 proftpd: (accepting 
connections)

... and proftpd service perfectly works...

On next reboot the situation is the same as on the beginning of this report.

My /etc/proftpd/proftpd.conf is default one, I didn't changed anything 
after proftpd is installed.


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

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

Versions of packages proftpd-basic depends on:
ii  proftpd-core1.3.8+dfsg-4
ii  proftpd-mod-crypto  1.3.8+dfsg-4
ii  proftpd-mod-wrap1.3.8+dfsg-4

proftpd-basic recommends no packages.

proftpd-basic suggests no packages.

-- no debconf information

Bug#786885: Broken gettext check in the build system of bison

[Bruno Haible]

The issue was fixed through
https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=b67399b40bc5bf3165b09e6a095ec941d4b30a97
and is thus contained in gettext-0.19.8 and newer.

The *gettext functions in musl libc work seamlessly with .mo files
produced by msgfmt 0.22 or newer, except for the 'I' flag in format
strings, that musl libc does not support.

Bruno

Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore

[Mike Hommey]

On Sun, Jun 18, 2023 at 06:09:57AM +0900, Mike Hommey wrote:
> On Sat, Jun 17, 2023 at 01:20:30AM +0200, Diederik de Haas wrote:
> > Control: tag -1 -moreinfo
> > Control: found -1 6.1.20-1
> > 
> > On Saturday, 17 June 2023 01:00:58 CEST Mike Hommey wrote:
> > > > 6.1.12-1 and 6.1.15-1 are good. 6.1.20-1 is the first broken one.
> > 
> > Excellent, thanks. This is already very useful.
> > 
> > > > > A `git bisect` would be best, but grabbing these intermediate versions
> > > > > (from snapshot.debian.org) is the quickest way to narrow the range.
> > > > 
> > > > Last time I tried to build Debian linux kernels, it was spending a large
> > > > amount of time building packages I don't need, and finding the right
> > > > incantation to reduce that load was not straightforward, and I can't
> > > > find my notes, unfortunately. If you have instructions I can use to go
> > > > through a bisect in a quick manner, I'm all ears.
> > > 
> > > Although, if you have instructions to just build the one module and avoid
> > > rebooting, that would be even better.
> > 
> > I _think_ building just one module or without rebooting is not possible.
> > 
> > The 'official' instructions: https://wiki.debian.org/DebianKernel/GitBisect
> > 
> > I know some things to reduce what gets build, like f.e. what's described 
> > here:
> > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.7
> > And there's also a facility to work with _build profiles_.
> > But I don't know if or how that could be applied to the 'official' 
> > instructions
> > as that deals with the upstream kernel source directly.
> > 
> > Hopefully one of the (more) experienced people chimes in with 
> > actual useful things ...
> 
> I was able to build the relevant module only. The regression comes from
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=337c3624bcb008f92bab38c8fc4cdf97ae5313a2

I sent a patch upstream, but it's not showing up on the archives yet.
I'll update with a link when I have one.

Mike

Bug#1038415: Source present upstream, but not in .tar.gz

[Don Armstrong]

Package: perltidy
Version: 20230309-1
Severity: important

The source for a number of documentation files is present upstream here:
https://github.com/perltidy/perltidy but not distributed in the .tar.gz
or in Debian.

Running lintian...
E: perltidy source: source-is-missing [docs/BugLog.html]
E: perltidy source: source-is-missing [docs/Tidy.html]
E: perltidy source: source-is-missing [docs/perltidy.html]
E: perltidy source: source-is-missing [docs/tutorial.html]

This should get fixed upstream.


-- 
Don Armstrong  https://www.donarmstrong.com

"She decided what she wished to happen and then assumed that reality
would bend to her wishes." [...] "Reality doesn't indulge wishes."
 -- Terry Goodkind _Phantom_ p133

Bug#1038414: make podman error message about storage driver friendlier

[Junichi Uekawa]

Package: podman
Version: 4.3.1+ds1-8+b1

After upgrade from bullseye to bookworm, there's error from local storage 
format.

ERRO[] User-selected graph driver "vfs" overwritten by graph driver 
"overlay" from database - delete libpod local files to resolve.  May prevent 
use of images created by other tools 

upstream seems to have better error message 
https://github.com/containers/podman/pull/16311 worth backporting? (might be 
challenging).

Warning disappeared after deleting ~/.local/share/containers/ and recreating.

Bug#1038339: qbittorrent: no icons after upgrade to 4.5.3

[Christian Marillat]

On 17 juin 2023 19:18, Emanuele Rocca  wrote:

> Hi,
>
> On 2023-06-17 04:57, Christian Marillat wrote:
>> 'Use icons from system theme' is set in preferences ?
>
> Yes. "Use custom UI Theme" is not set, "Use icons from system theme" is.

I mixed up these two options in my previous e-mail.

Do you see icons when the second option is not set ?

Christian

Bug#1038413: DDP Documentation policy: should no longer recommend docbook xml

[Holger Wansing]

Package: www.debian.org
Severity: minor


https://www.debian.org/doc/ddp.en.html says under "Documentation Policy":

"We use Docbook XML for our documents."

Since some documents (Debian Policy, Developers Reference) have been migrated
to Sphinx/restructuredText alredy, can this be considered as the new recommend?

If so, the text should be updated to something like

"We use restructuredText or Docbook XML (deprecated) for our documents."



Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1038339: qbittorrent: no icons after upgrade to 4.5.3

[Christian Marillat]

On 17 juin 2023 19:18, Emanuele Rocca  wrote:

> Hi,
>
> On 2023-06-17 04:57, Christian Marillat wrote:
>> 'Use icons from system theme' is set in preferences ?
>
> Yes. "Use custom UI Theme" is not set, "Use icons from system theme" is.

When option "Use custom UI Theme" is set do you see these icons ?

> Please find a screenshot of qt5ct attached, it looks a little weird?

Yes because you have the default theme. Try to set another theme in
appearance tab.

Christian

Bug#1038271: linux-image-6.1.0-9-amd64: Logitech trackpad T651 doesn't work anymore

[Mike Hommey]

On Sat, Jun 17, 2023 at 01:20:30AM +0200, Diederik de Haas wrote:
> Control: tag -1 -moreinfo
> Control: found -1 6.1.20-1
> 
> On Saturday, 17 June 2023 01:00:58 CEST Mike Hommey wrote:
> > > 6.1.12-1 and 6.1.15-1 are good. 6.1.20-1 is the first broken one.
> 
> Excellent, thanks. This is already very useful.
> 
> > > > A `git bisect` would be best, but grabbing these intermediate versions
> > > > (from snapshot.debian.org) is the quickest way to narrow the range.
> > > 
> > > Last time I tried to build Debian linux kernels, it was spending a large
> > > amount of time building packages I don't need, and finding the right
> > > incantation to reduce that load was not straightforward, and I can't
> > > find my notes, unfortunately. If you have instructions I can use to go
> > > through a bisect in a quick manner, I'm all ears.
> > 
> > Although, if you have instructions to just build the one module and avoid
> > rebooting, that would be even better.
> 
> I _think_ building just one module or without rebooting is not possible.
> 
> The 'official' instructions: https://wiki.debian.org/DebianKernel/GitBisect
> 
> I know some things to reduce what gets build, like f.e. what's described here:
> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.7
> And there's also a facility to work with _build profiles_.
> But I don't know if or how that could be applied to the 'official' 
> instructions
> as that deals with the upstream kernel source directly.
> 
> Hopefully one of the (more) experienced people chimes in with 
> actual useful things ...

I was able to build the relevant module only. The regression comes from
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=337c3624bcb008f92bab38c8fc4cdf97ae5313a2

Mike

Bug#1038412: gnome-shell-extension-weather: Update to 121 to support GNOME 44

[Amr Ibrahim]

Package: gnome-shell-extension-weather
Version: 119-1
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

Dear Maintainer,

Please update to 121 to support GNOME 44.

Best,
Amr


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 gnome-shell-extension-weather depends on:
ii  ca-certificates  20230311
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-clutter-1.0   1.26.4+dfsg-4
ii  gir1.2-glib-2.0  1.74.0-3
ii  gir1.2-gtk-3.0   3.24.37-2
ii  gir1.2-soup-3.0  3.2.2-2
ii  gnome-shell  43.6-1

Versions of packages gnome-shell-extension-weather recommends:
ii  gnome-tweaks  42~beta-4

gnome-shell-extension-weather suggests no packages.

-- no debconf information

Bug#1038317: nautilus: new tab with ctrl+t keyboard set completely gray window

[Simon McVittie]

Control: tags -1 + moreinfo unreproducible

On Fri, 16 Jun 2023 at 23:51:04 -0400, zezamoral wrote:
>* What led up to the situation?
> launch new tab with ctrl+t keyboard combination

I wasn't able to reproduce this issue on a fresh installation from
debian-live-12.0.0-amd64-gnome.iso using debian-installer, or on my usual
development system.

Is there anything special about the current directory when you see this
bug occur? I tried navigating to a directory with many files (/usr/bin)
but still didn't see it.

Are any warnings logged in the system log (systemd Journal) when this
happens? You can watch for new journal messages by running
"journalctl -f" in a Terminal window.

> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE

Is this the NVIDIA graphics drivers? If yes, I wonder whether that might
be relevant...

Thanks,
smcv

Bug#1038411: calamares: Attempt to grow a EFI partition leads to an installation failure

[Dmitry K]

Package: calamares
Severity: important
Tags: d-i
X-Debbugs-Cc: kuteyni...@gmail.com

Dear Maintainer,

I installed Debian Bookworm from a Gnome live USB stick. The installer
complained on an insufficient size of the ESP (200Mb instead of 500). To fix
this I scheduled a resize of the ESP via manual partitioning in the
installation wizard. No warnings were shown notifying me in advance that this
operation cannot be performed. As a result, when I started the installation,
the process was interrupted in the middle of file system rearrangements.

Workaround: I had to backup, manually remove, recreate the EFI partition with a
desired size and restore its content.

Expected behavior: Either add support for growing FAT32 EFI partitions, or
prevent the user to select unsupported operations before the installation
started.

Here is the output of the installer:

Grow partition ‘/dev/sdb1’ from 260.00 MiB to 515.00 MiB
Job: Check file system on partition ‘/dev/sdb1’
Command: fsck.fat -a -w -v /dev/sdb1
Job: Set geometry of partition ‘/dev/sdb1’: Start sector: 2,048, length:
1,054,720
Command: sfdisk --force /dev/sdb -N 1
Job: Resize file system on partition ‘/dev/sdb1’ to 1,054,720 sectors
Resizing file system from 532,480 to 1,054,720 sectors.
The file system on partition ‘/dev/sdb1’ cannot be resized because there is no
support for it.
Resize/move failed: Could not resize the file system on partition ‘/dev/sdb1’
Job: Set geometry of partition ‘/dev/sdb1’: Start sector: 2,048, length:
532,480
Command: sfdisk --force /dev/sdb -N 1
Resizing/moving partition ‘/dev/sdb1’ failed.


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

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

Versions of packages calamares depends on:
pn  kpackagetool5
pn  libboost-python1.74.0
pn  libboost-python1.74.0-py311  
ii  libc62.36-9
ii  libcrypt11:4.4.33-2
ii  libgcc-s112.2.0-14
pn  libkf5configcore5
pn  libkf5coreaddons5
pn  libkf5package5   
pn  libkf5parts5 
pn  libkpmcore12 
ii  libparted2   3.5-3
ii  libpwquality11.4.5-1+b1
ii  libpython3.113.11.2-6
ii  libqt5core5a 5.15.8+dfsg-11
ii  libqt5dbus5  5.15.8+dfsg-11
ii  libqt5gui5   5.15.8+dfsg-11
ii  libqt5network5   5.15.8+dfsg-11
ii  libqt5qml5   5.15.8+dfsg-3
ii  libqt5quick5 5.15.8+dfsg-3
ii  libqt5quickwidgets5  5.15.8+dfsg-3
ii  libqt5svg5   5.15.8-3
ii  libqt5webkit55.212.0~alpha4-30
ii  libqt5widgets5   5.15.8+dfsg-11
ii  libqt5xml5   5.15.8+dfsg-11
ii  libstdc++6   12.2.0-14
pn  libyaml-cpp0.7   
ii  os-prober1.81

Versions of packages calamares recommends:
ii  btrfs-progs 6.2-1
ii  squashfs-tools  1:4.5.1-1

calamares suggests no packages.

Bug#1037919: denial of service in vte2.91 with OSC 104

[Simon McVittie]

(redirecting replies to the vte2.91 bug, this doesn't seem like something
that we need to bother the release team with)

On Sat, 17 Jun 2023 at 21:06:07 +0200, Salvatore Bonaccorso wrote:
> On Sat, Jun 17, 2023 at 03:22:21PM +0100, Simon McVittie wrote:
> > I asked the security team whether they wanted to do a DSA for
> > this and haven't heard back, so I'm assuming the answer is no.
> 
> Aplogies, we have missed to reply to your question in #1037919. Te
> point release approach looks indeed fine.
> 
> FWIW, do you know if upstream has requested a CVE for it?

I am not aware of any attempt to request a CVE. It's not clear to me
whether upstream consider it to be a denial-of-service security issue,
or an ordinary non-security bug (and I'm not really sure myself, tbh):
the discussion on the upstream bug says

In this issue here there is no buffer overflow or vulnerability,
just an indefinite hang (maybe classified as potential DoS). While
this is a bit bad, it's a 5 year old bug and this the first report
of it, so I don't think it's too grave.

Please see https://gitlab.gnome.org/GNOME/vte/-/issues/2631 for any other
details or coordination that might be needed.

smcv

Bug#1037190: re-introduction of epoch? #1037190 dhcpcd: version is lower than in wheezy

[Andreas Beckmann]

On 17/06/2023 20.30, Martin-Éric Racine wrote:

This is what I would do if the archive policy demands it. Won't affect
transitional dhcpcd5 or dhcpcd-base.


Ack.

I'm not sure whether the transitional dhcpcd5 package should have a 
versioned dependency on the "right" dhcpcd, either
(= 1:${binary:Version}) or (>= 1:9). IIRC you need to add the epoch 
manually in the former case.



Andreas

Bug#1038117: util-linux: resume building of static libs

[Leo Antunes]

Hi,

On Thu, 15 Jun 2023 17:38:27 +0200 Chris Hofstaedtler 
wrote:
> For Debian we just do the Debian thing: do not ship static libraries
> except for very narrow within-Debian-use-cases.

Don't wanna come off too abrasive here, but:
$ apt-file search -lx '^/usr/lib/.*\.a$' | sort | uniq | wc -l
6849

That doesn't look very narrow 
Also, policy explicitly mentions it as "usually provided"[0], which -
granted - doesn't mean you *have* to do it, but does kinda endorse it.

Just because we (via policy) forbid linking statically within debian,
it shouldn't mean we have to unnecessarily alienate out users (in this
case myself ) when they want to do it on their systems.

> I think if you do custom stuff for minimal containers etc, its best
> if you bring your own libraries and do not rely on development
> packages intended -for- Debian packages.

Not sure I understand the reasoning: a library is a tool, in the
broadest sense. Our users rely on debian providing a usable gcc to
build stuff, just as they rely on us providing libs for them to link
against, dynamically or otherwise. AFAICT there's nothing particularly
debian-specific about this?

But don't get me wrong: if there's a technical reason I'm overlooking,
then the points above are irrelevant, of course.

--
Leo

[0]
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#static-libraries

Bug#1037304: gnome-control-center: sharing non-accessible after fresh GNOME 3 installation

[Simon McVittie]

Control: clone -1 -2
Control: retitle -1 Keyring access in gnome-control-center -> Sharing gets 
stuck during first login to fresh installation
Control: tags -1 + confirmed
Control: reassign -1 gnome-keyring 42.1-1
Control: affects -1 + gnome-control-center
Control: retitle -2 gnome-control-center: Sharing panel should access 
gnome-keyring asynchronously
Control: severity -2 wishlist

On Sat, 10 Jun 2023 at 20:32:11 +0200, Markus Koschany wrote:
> I just installed GNOME 3 on a Lenovo X280 and X230i Thinkpad.
> 
> Open the gnome-control-center, click on the sharing menu item. Now the 
> application starts to freeze and a dialogue opens whether I would like to 
> wait or force quit the application. I waited for several minutes and retried 
> the process but that didn't help.

I can reproduce this with a fresh installation from
debian-live-12.0.0-amd64-gnome.iso using debian-installer.

I think this is a problem with gnome-keyring, rather than
gnome-control-center specifically. Attaching gdb to gnome-control-center
indicates that the main thread is blocking in a call to
secret_password_store_sync(), which is storing a generated password to be
used by gnome-remote-desktop if enabled:

Thread 1 (Thread 0x70a31640 (LWP 3605) "gnome-control-c"):
#0  0x7603cfff in __GI___poll (fds=0x558f6010, nfds=1, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x77c8e9ae in g_main_context_poll (priority=, 
n_fds=1, fds=0x558f6010, timeout=, context=0x5828ba10) 
at ../../../glib/gmain.c:4553
#2  g_main_context_iterate (context=0x5828ba10, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4243
#3  0x77c8ecef in g_main_loop_run (loop=0x558f3470) at 
../../../glib/gmain.c:4448
#4  0x76864f08 in secret_password_storev_sync 
(schema=schema@entry=0x55848ae0 , 
attributes=attributes@entry=0x582a2d20, 
collection=collection@entry=0x556d8de2 "default", 
label=label@entry=0x556e50f8 "GNOME Remote Desktop RDP credentials", 
password=password@entry=0x582a7430 "{'username': <'user'>, 'password': 
<'__REDACTED__'>}", cancellable=cancellable@entry=0x0, error=0x0) at 
../libsecret/secret-password.c:466
#5  0x7686510b in secret_password_store_sync (schema=0x55848ae0 
, collection=collection@entry=0x556d8de2 
"default", label=label@entry=0x556e50f8 "GNOME Remote Desktop RDP 
credentials", password=password@entry=0x582a7430 "{'username': <'user'>, 
'password': <'__REDACTED__'>}", cancellable=cancellable@entry=0x0, 
error=error@entry=0x0) at ../libsecret/secret-password.c:404
#6  0x55638597 in cc_grd_store_rdp_credentials 
(username=username@entry=0x582f22b0 "user", 
password=password@entry=0x7fffed46f008 "__REDACTED__", cancellable=) at ../panels/sharing/cc-gnome-remote-desktop.c:52
#7  0x5563620e in store_remote_desktop_credentials_timeout 
(user_data=) at ../panels/sharing/cc-sharing-panel.c:1004
#8  0x77c8f19a in g_timeout_dispatch (source=0x582f21b0, 
callback=, user_data=) at 
../../../glib/gmain.c:5017
#9  0x77c8e67f in g_main_dispatch (context=0x558a4f00) at 
../../../glib/gmain.c:3454
#10 g_main_context_dispatch (context=context@entry=0x558a4f00) at 
../../../glib/gmain.c:4172
#11 0x77c8ea38 in g_main_context_iterate 
(context=context@entry=0x558a4f00, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4248
#12 0x77c8eacc in g_main_context_iteration 
(context=context@entry=0x558a4f00, may_block=may_block@entry=1) at 
../../../glib/gmain.c:4313
#13 0x77eae65d in g_application_run (application=0x558a0110, 
argc=argc@entry=1, argv=argv@entry=0x7fffe0e8) at 
../../../gio/gapplication.c:2573
#14 0x555b2e41 in main (argc=1, argv=0x7fffe0e8) at 
../shell/main.c:60

However, gnome-keyring didn't start correctly:

Jun 17 20:46:35 momentum systemd[1875]: Listening on 
gnome-keyring-daemon.socket - GNOME Keyring daemon.
...
Jun 17 20:46:35 momentum systemd[1875]: Started gnome-keyring-daemon.service - 
GNOME Keyring daemon.
...
Jun 17 20:46:35 momentum gnome-keyring-daemon[1900]: 
GNOME_KEYRING_CONTROL=/run/user/1000/keyring
...
Jun 17 20:46:36 momentum gnome-keyring-daemon[1900]: The PKCS#11 component was 
already initialized
Jun 17 20:46:36 momentum gnome-keyring-d[1900]: The PKCS#11 component was 
already initialized
Jun 17 20:46:36 momentum gnome-keyring-daemon[2043]: discover_other_daemon: 1
Jun 17 20:46:36 momentum gnome-keyring-pkcs11.desktop[2043]: 
discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Jun 17 20:46:36 momentum gnome-keyring-daemon[1900]: The Secret Service was 
already initialized
Jun 17 20:46:36 momentum gnome-keyring-daemon[2044]: discover_other_daemon: 1
Jun 17 20:46:36 momentum gnome-keyring-ssh.desktop[2044]: 
discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Jun 17 20:46:36 momentum gnome-keyring-ssh.desktop[2044]: 

Bug#1038409: linux-image-6.3.0-1-amd64: CONFIG_RTW88_8822BU is disabled, preventing me from using my wifi adapter

[Elizaveta L.]

Package: src:linux
Version: 6.3.7-1
Severity: normal


-- Package-specific info:
** Version:
Linux version 6.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.3.7-1 (2023-06-12)

** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-9-amd64 
root=UUID=86f5cc6e-383a-49be-bfed-4c37762c059d ro initrd=/install/gtk/initrd.gz 
quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Gigabyte Technology Co., Ltd.
product_name: To be filled by O.E.M.
product_version: To be filled by O.E.M.
chassis_vendor: Gigabyte Technology Co., Ltd.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: F8d
board_vendor: Gigabyte Technology Co., Ltd.
board_name: F2A88XM-DS2
board_version: x.x

** Loaded modules:
rtw88_8822b
rtw88_core
mac80211
libarc4
cfg80211
vboxnetadp(OE)
vboxnetflt(OE)
xt_REDIRECT
xt_tcpudp
vboxdrv(OE)
nft_chain_nat
xt_MASQUERADE
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nft_compat
nf_tables
nfnetlink
nvme_fabrics
snd_seq_dummy
snd_hrtimer
snd_seq
snd_seq_device
qrtr
rfkill
cpufreq_ondemand
cpufreq_conservative
cpufreq_powersave
cpufreq_userspace
tun
dm_raid
binfmt_misc
nvidia_drm(POE)
drm_kms_helper
nvidia_modeset(POE)
nls_ascii
nls_cp437
vfat
fat
nvidia(POE)
edac_mce_amd
snd_hda_codec_realtek
snd_hda_codec_generic
ledtrig_audio
kvm_amd
snd_hda_codec_hdmi
ccp
rng_core
snd_hda_intel
snd_intel_dspcfg
snd_intel_sdw_acpi
kvm
snd_hda_codec
snd_hda_core
snd_hwdep
sp5100_tco
irqbypass
snd_pcm
k10temp
watchdog
snd_timer
snd
soundcore
joydev
acpi_cpufreq
evdev
sg
parport_pc
ppdev
lp
parport
drm
fuse
loop
efi_pstore
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
dm_crypt
dm_mod
efivarfs
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
crc32c_generic
raid1
raid0
multipath
linear
md_mod
hid_generic
usbhid
hid
uas
usb_storage
sd_mod
nvme
crc32_pclmul
crc32c_intel
nvme_core
ahci
r8169
ghash_clmulni_intel
libahci
sha512_ssse3
t10_pi
xhci_pci
sha512_generic
aesni_intel
libata
crc64_rocksoft_generic
ohci_pci
ehci_pci
ohci_hcd
crc64_rocksoft
crc_t10dif
ehci_hcd
xhci_hcd
realtek
mdio_devres
scsi_mod
crypto_simd
cryptd
crct10dif_generic
i2c_piix4
libphy
usbcore
scsi_common
crct10dif_pclmul
crc64
usb_common
crct10dif_common
video
wmi
button

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 10h-1fh) Processor Root Complex [1022:1410]
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
10h-1fh) Processor Root Complex [1022:1410]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 10h-1fh) Processor Root Port [1022:1414] (prog-if 00 [Normal decode])
Subsystem: Advanced Micro Devices, Inc. [AMD] Trinity A-series APU 
[1022:1234]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 10h-1fh) Processor Root Port [1022:1415] (prog-if 00 [Normal decode])
Subsystem: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
10h-1fh) Processor Root Port [1022:1234]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller [1022:7814] (rev 09) (prog-if 30 [XHCI])
Subsystem: Gigabyte Technology Co., Ltd FCH USB XHCI Controller 
[1458:5004]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:10.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller [1022:7814] (rev 09) (prog-if 30 [XHCI])

Bug#991428: Consider migrating to original 7-Zip for Linux

[Bastian Germann]

Now that the 7zip package is feature-compatible with p7zip please move this 
forward
and convert the p7zip packages to transitional packages.

Bug#1038408: ruby3.1: CVE-2023-28755 CVE-2023-28756

[Salvatore Bonaccorso]

Source: ruby3.1
Version: 3.1.2-7
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for ruby3.1.

CVE-2023-28755[0]:
| A ReDoS issue was discovered in the URI component through 0.12.0 in
| Ruby through 3.2.1. The URI parser mishandles invalid URLs that have
| specific characters. It causes an increase in execution time for
| parsing strings to URI objects. The fixed versions are 0.12.1,
| 0.11.1, 0.10.2 and 0.10.0.1.


CVE-2023-28756[1]:
| A ReDoS issue was discovered in the Time component through 0.2.1 in
| Ruby through 3.2.1. The Time parser mishandles invalid URLs that
| have specific characters. It causes an increase in execution time
| for parsing strings to Time objects. The fixed versions are 0.1.1
| and 0.2.2.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-28755
https://www.cve.org/CVERecord?id=CVE-2023-28755
[1] https://security-tracker.debian.org/tracker/CVE-2023-28756
https://www.cve.org/CVERecord?id=CVE-2023-28756

Regards,
Salvatore

Bug#1038404: Single option to not depend on host configuration

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Josh Triplett (2023-06-17 20:37:47)
> mmdebstrap has a couple of places in which it copies host configuration into
> the bootstrapped system. For instance, it puts the host's hostname into
> /etc/hostname, and copies in the host's /etc/resolv.conf. Please consider
> providing a single option that suppresses all current and future uses of the
> host configuration, to make it easier to build reproducible installations.
> 
> The manpage mentions using a customize-hook to handle those two files,
> but given the common need for reproducible installations, it'd be nice
> to have this become simpler and standardized.

you are right, mmdebstrap only creates bit-by-bit reproducible output if run
from the same host because of these two files it copies in. You are right in
that it should be easier to prevent those two files from messing up
reproducibility.

The next question becomes: what should be done about /etc/hostname and
/etc/resolv.conf? What should their reproducible content be?

Or should they just be deleted?

You are not the only one who wants such an option:

https://gitlab.mister-muffin.de/josch/mmdebstrap/issues/26
https://gitlab.mister-muffin.de/josch/mmdebstrap/issues/33

As I've explained in the first of above issue, I'd rather add a hook than a
command line flag because all instances that I can come up with where you want
to run mmdebstrap to create bit-by-bit reproducible output, you run it from a
script and not manually type the command from the terminal. Can you confirm
this?

Thanks!

cheers josch

signature.asc
Description: signature

Bug#1037279: Angelfish built-in ad blocker not built due to missing Rust Build-Depends (Corrosion etc.)

[Nilesh Patra]

On Sat, 10 Jun 2023 05:09:08 +0200 Kevin Kofler  wrote:> Angelfish has a built-in ad blocker based on the Rust adblock crate from 
the Brave developers. This feature is missing from the Debian package 
because Corrosion and other build-time dependencies are not Build-Depended.


Right, and the reason is...


(They may need to be added to Debian first.)


Precisely this. At the time of packaging angelfish, I suppose neither of us (me 
and Praveen) have had the
bandwidth to package all the rust toolchain yet.


In addition to Corrosion, you will need cargo(though Corrosion should
already be requiring it), rust-adblock, rust-cxx-build, and rust-cxx.


corossion, rust-adblock need packaging. Rest are in the archive already at the 
moment. I doubt if we need
corossion too, since this is mainly for comat with cmake based projects, and we 
are usually not relying on
submodule struct, and package things separately.


You may also need to hack things up so that it can build offline.


I'm quite sure it'd need some changes.

See also https://bugzilla.redhat.com/show_bug.cgi?id=2213926 for the exact 
same issue in the Fedora package.


Cool. Thanks for reporting. Can get back to this once we have the bandwidth.

Best
Nilesh

Bug#1037543: closed by Andreas Metzler (Re: Bug#1037543: bugreport in terms of GNUPG)

[John Danielsson]

Thank you for the quick reply!
It worked. :)

Debian Bug Tracking System  ezt írta (időpont: 2023.
jún. 14., Sze, 18:54):

> This is an automatic notification regarding your Bug report
> which was filed against the gnupg package:
>
> #1037543: bugreport in terms of GNUPG
>
> It has been closed by Andreas Metzler .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Andreas Metzler <
> ametz...@bebt.de> by
> replying to this email.
>
>
> --
> 1037543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037543
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Andreas Metzler 
> To: 1037543-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Wed, 14 Jun 2023 18:50:27 +0200
> Subject: Re: Bug#1037543: bugreport in terms of GNUPG
> On 2023-06-14 John Danielsson  wrote:
> > Package: GNUPG
> > Version: 2.2
>
> > Dear Team,
>
> > I would like to report a bug regarding GNUPG export key feature.
> > Everytime I export a key using --export GPGID command manually from
> > terminal,
> > I am not able to import the key, while using the GNUPG gui from Gnome
> > successfully
> > exports the secretkey.
>
> You got the syntax wrong ("gpg --import key Key.gpg"), try
>
> gpg --import < Key.gpg"
>
> instead.
>
> cu Andreas
> --
> `What a good friend you are to him, Dr. Maturin. His other friends are
> so grateful to you.'
> `I sew his ears on from time to time, sure'
>
>
> -- Forwarded message --
> From: John Danielsson 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Wed, 14 Jun 2023 00:07:39 +0200
> Subject: bugreport in terms of GNUPG
> Package: GNUPG
> Version: 2.2
>
> Dear Team,
>
> I would like to report a bug regarding GNUPG export key feature.
> Everytime I export a key using --export GPGID command manually from
> terminal,
> I am not able to import the key, while using the GNUPG gui from Gnome
> successfully
> exports the secretkey.
>
> Best regards,
>
> John
>

Bug#1038343: fim: Depends on SDL 1.2

[Rafael Laboissière]

Control: forwarded -1 https://savannah.nongnu.org/bugs/index.php?64313

Hello Simon,

Thanks for this bug report. I forwarded it upstream and I am also sending 
this message with Cc to the upstream author.


Best,

Rafael

* Simon McVittie  [2023-06-17 10:28]:


Source: fim
Tags: trixie sid
User: pkg-sdl-maintain...@lists.alioth.debian.org
Usertags: libsdl1.2

This package has a Depends or Build-Depends on SDL version 1.2, which 
is unmaintained upstream.


If possible, please port this package to SDL 2 and close this bug. There 
is a migration guide at , 
and examples of successful ports from SDL 1.2 to SDL 2 can be found in 
the commit history of packages like darkplaces and ioquake3.


If it is not possible to port to SDL 2, please test the package with 
libsdl1.2-compat-shim (preferably version 1.2.64 or later), and leave 
this bug open to track the package as still using SDL 1.2 APIs.


libsdl1.2-compat-shim is a compatibility layer that provides the SDL 1.2 
API/ABI by using SDL 2: it has already replaced the "classic" SDL 1.2 
library in some other distributions like Fedora and Arch, and my intention 
is to do the same in Debian during the trixie release cycle.


Please don't change dependencies from libsdl1.2debian to 
libsdl1.2-compat-shim, or from libsdl1.2-dev to libsdl1.2-compat-dev. 
The -compat packages have Provides for the old package names, and my 
intention is to make a future version of sdl12-compat take over the old 
package names, to minimize the changes that are required in dependent 
packages.


The interesting scenarios to test with libsdl1.2-compat-shim are:

1. Install libsdl1.2-compat-shim and run the program in an X11 environment, 
  such as "GNOME on Xorg" or XFCE. 
  ($XDG_RUNTIME_DIR/wayland-* should not exist) 
2. Install libsdl1.2-compat-shim and run the program in a Wayland 
  environment such as GNOME's default mode, using Xwayland. 
  ($XDG_RUNTIME_DIR/wayland-* should exist) 
3. Install libsdl1.2-compat-shim and run the program in a Wayland 
  environment, but this time with environment variable 
  SDL_VIDEODRIVER=wayland so that it uses the native Wayland interface 
  (this is not currently the default for SDL 2). 
4. Install libsdl1.2-compat-dev and recompile the package.


Note that using libsdl1.2-compat and LD_LIBRARY_PATH is not sufficient if 
the package contains programs that are setgid games. See 
 
for more information.


If any of those fail, please report it as a bug in the 
libsdl1.2-compat-shim or libsdl1.2-compat-dev package as appropriate, 
with "affects" pointing to the program that is affected.


Thanks, 
   smcv


--
This bug report is part of a mass-bug-filing:

Bug#1038390: bookworm-pu: package vte2.91/0.70.6-1~deb12u1

[Salvatore Bonaccorso]

Hi Simon,

On Sat, Jun 17, 2023 at 03:22:21PM +0100, Simon McVittie wrote:
> Package: release.debian.org
> Severity: normal
> Tags: bookworm
> User: release.debian@packages.debian.org
> Usertags: pu
> X-Debbugs-Cc: vte2...@packages.debian.org, debian-b...@lists.debian.org, 
> t...@security.debian.org
> Control: affects -1 + src:vte2.91
> 
> [ Reason ]
> Fix an infinite-loop bug processing a particular control sequence.
> (#1037919, LP: #2022019)
> 
> [ Impact ]
> If unfixed, the infinite loop could be triggered by a malicious program
> accessed via ssh, telnet or similar protocols and used as a denial of
> service. I asked the security team whether they wanted to do a DSA for
> this and haven't heard back, so I'm assuming the answer is no.

Aplogies, we have missed to reply to your question in #1037919. Te
point release approach looks indeed fine.

FWIW, do you know if upstream has requested a CVE for it?

Regards,
Salvatore

Bug#1021060: apt-clone: diff for NMU version 0.4.3+nmu2

[Boyuan Yang]

Control: tags 1021060 + pending
X-Debbugs-CC: ales...@debian.org michael.v...@ubuntu.com

Dear maintainer,

I've prepared an NMU for apt-clone (versioned as 0.4.3+nmu2) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru apt-clone-0.4.3+nmu1/apt-clone apt-clone-0.4.3+nmu2/apt-clone
--- apt-clone-0.4.3+nmu1/apt-clone  2021-09-20 16:21:48.0 -0400
+++ apt-clone-0.4.3+nmu2/apt-clone  2023-06-17 14:27:03.0 -0400
@@ -21,6 +21,7 @@
 
 import argparse
 import os
+import subprocess
 import sys
 
 from apt_clone import AptClone
@@ -132,8 +133,12 @@
 # packages because they are probably new defaults pkgs. If however
 # we are not yet on the new release its fine to remove installed
 # pkgs as part of the upgrade
-import lsb_release
-codename = lsb_release.get_os_release()["CODENAME"]
+try:
+import lsb_release
+codename = lsb_release.get_os_release()["CODENAME"]
+except ImportError:
+codename = subprocess.getoutput("lsb_release --codename --
short")
+
 if (args.new_distro_codename and args.new_distro_codename ==
codename):
 protect_installed = True
 else:
diff -Nru apt-clone-0.4.3+nmu1/apt_clone.py apt-clone-
0.4.3+nmu2/apt_clone.py
--- apt-clone-0.4.3+nmu1/apt_clone.py   2021-09-20 16:21:48.0 -0400
+++ apt-clone-0.4.3+nmu2/apt_clone.py   2023-06-17 14:27:03.0 -0400
@@ -26,7 +26,10 @@
 import glob
 import hashlib
 import logging
-import lsb_release
+try:
+import lsb_release
+except ImportError:
+lsb_release = None
 import os
 import re
 import shutil
@@ -71,8 +74,10 @@
 return (ret == 0)
 
 def debootstrap(self, targetdir, distro=None):
-if distro is None:
+if distro is None and lsb_release:
 distro = lsb_release.get_distro_information()['CODENAME']
+if distro is None:
+distro = subprocess.getoutput("lsb_release --codename --short")
 ret = subprocess.call(["debootstrap", distro, targetdir])
 return (ret == 0)
 
@@ -187,7 +192,10 @@
 cache = self._cache_cls(rootdir=sourcedir)
 s = ""
 foreign = ""
-distro_id = lsb_release.get_distro_information()['ID']
+if lsb_release:
+distro_id = lsb_release.get_distro_information()['ID']
+else:
+distro_id = subprocess.getoutput("lsb_release --id --short")
 for pkg in cache:
 if pkg.is_installed:
 # a version identifies the pacakge
diff -Nru apt-clone-0.4.3+nmu1/debian/changelog apt-clone-
0.4.3+nmu2/debian/changelog
--- apt-clone-0.4.3+nmu1/debian/changelog   2021-09-20
16:21:48.0 -0400
+++ apt-clone-0.4.3+nmu2/debian/changelog   2023-06-17
14:27:03.0 -0400
@@ -1,3 +1,20 @@
+apt-clone (0.4.3+nmu2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Dave Jones ]
+  * Apply PR #17 to have apt-clone call lsb_release as a command, instead
of
+importing the Python module which no longer exists (LP: #2007566)
+
+
+  [ Boyuan Yang ]
+  * Import Ubuntu patch to fix crashes caused by missing lsb_release
+Python module. (Closes: #1021060)
+  * debian/control: Replace deprecated Priority: extra with Priority:
+optional.
+
+ -- Boyuan Yang   Sat, 17 Jun 2023 14:27:03 -0400
+
 apt-clone (0.4.3+nmu1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru apt-clone-0.4.3+nmu1/debian/control apt-clone-
0.4.3+nmu2/debian/control
--- apt-clone-0.4.3+nmu1/debian/control 2021-09-20 16:21:48.0 -0400
+++ apt-clone-0.4.3+nmu2/debian/control 2023-06-17 14:27:03.0 -0400
@@ -1,6 +1,6 @@
 Source: apt-clone
 Section: admin
-Priority: extra
+Priority: optional
 Maintainer: Michael Vogt 
 Uploaders: Alessio Treglia 
 Build-Depends: debhelper (>= 7.0.50~),


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

Bug#1038407: src:rust-criterion: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: rust-criterion
Version: 0.3.6-4
Severity: serious
Control: close -1 0.4.0-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1031306

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:rust-criterion has been trying to migrate 
for 133 days [2] (yes, partially because of the freeze). Hence, I am 
filing this bug. The autopkgtest of this package regressed (filed in bug 
1031306).


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=rust-criterion



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038406: src:rust-ahash: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: rust-ahash
Version: 0.7.6-7
Severity: serious
Control: close -1 0.8.3-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1031751

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:rust-ahash has been trying to migrate for 
134 days [2] (yes, partially because of the freeze). Hence, I am filing 
this bug. The autopkgtest of your package regressed (filed in bug #1031751).


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=rust-ahash



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038405: src:r-cran-rstan: fails to migrate to testing for too long: FTBFS on armel, armhf and i386

[Paul Gevers]

Source: r-cran-rstan
Version: 2.21.7-1
Severity: serious
Control: close -1 2.21.8-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-rstan has been trying to migrate 
for 147 days [2] (yes, partially because of the freeze). Hence, I am 
filing this bug. Your package failed to build from source on armel, 
armhf and i386 where it built successfully in the past.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=r-cran-rstan



OpenPGP_signature
Description: OpenPGP digital signature

Bug#966073: info2www outputs HTML4/iso-8859-1 but text is UTF-8

[Kaleb Hornsby]

I came across this bug as well, but my fix is slightly different:


166c166
< print "Content-type: text/html; charset=utf-8\n\n"; # Mime header
for NCSA httpd
---
> print "Content-type: text/html\n\n"; # Mime header for NCSA httpd

Bug#1037942: linphone-desktop: Call notification windows in the middle of the screen

[Dennis Filder]

X-Debbugs-CC: Samuel Wolf 
Control: reassign -1 src:qtwayland-opensource-src

On Fri, Jun 16, 2023 at 11:18:00AM +0200, Samuel Wolf wrote:

> I tried the same setup with X11 (disable wayland) and it works as expected.
> So this is another "wayland" issue and maybe not a linphone problem?

Looks like it.

> Do you see any chance for a workaround in wayland?

Running linphone under XWayland could be worth a try.  If that doesn't
work either I guess we'll probably just have to wait till the
Wayland-related bug in Qt has been ironed out.  Anyway, I'll reassign
this to src:qtwayland-opensource-src in the hope that this will increase
its chance of getting resolved eventually.

Regards.

Bug#1038404: Single option to not depend on host configuration

[Josh Triplett]

Package: mmdebstrap
Version: 1.3.6-3
Severity: wishlist
X-Debbugs-Cc: j...@joshtriplett.org

mmdebstrap has a couple of places in which it copies host configuration
into the bootstrapped system. For instance, it puts the host's hostname
into /etc/hostname, and copies in the host's /etc/resolv.conf. Please
consider providing a single option that suppresses all current and
future uses of the host configuration, to make it easier to build
reproducible installations.

The manpage mentions using a customize-hook to handle those two files,
but given the common need for reproducible installations, it'd be nice
to have this become simpler and standardized.

Bug#1036094: nss: libnss3 libnss3-dev fails to debuild -us -uc

[Paul Gevers]

Hi,

On Mon, 15 May 2023 13:06:26 +0200 Renato Gallo  
wrote:

The following packages have unmet dependencies:
 libnss3-dev : Depends: libnss3 (= 2:3.87.1-1) but 2:3.89-2 is to be installed


It think this problem solved itself, but the reproducible-builds 
infrastructure [1] claims nss still FTBFS. I'm not understanding what 
the tail of the log means thought.


Sat Jun 17 13:08:40 UTC 2023  I: 1st build successful. Starting 2nd 
build on remote node ionos11-amd64.debian.net.
Sat Jun 17 13:08:40 UTC 2023  I: Preparing to do remote build '2' on 
ionos11-amd64.debian.net.
Sat Jun 17 13:09:04 UTC 2023  I: Deleting $TMPDIR on 
ionos11-amd64.debian.net.
Sat Jun 17 13:09:05 UTC 2023  I: 
https://tests.reproducible-builds.org/debian/unstable/amd64/nss : FTBR ➤ 
FTBFS


Paul

[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nss.html


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038403: mintUpdate manager for Debian

[Solrak Rainbowarrior]

Package: mintUpdate

Version: mintUpdate from Ubuntu based version

Linux Mint update manager (mintupdate) Ubuntu-based version, it's a great
application. It includes update manager, kernel and repository manager. 3
in 1.
As well as other very practical utilities, such as installing missing
repository keys.
It can do many things, It's wonderful. By now I think Debian should have a
kernel manager.

If a program is already made and works well, why not have it?

I think Debian should have programs to manage kernels, an update manager
and repositories.
I mean an update manager that doesn't depend on Discover or Gnome Software.
And with more options than synaptic.
I have already reached the necessary knowledge to live without it, but
there are many things that I still don't know how to do. And other users
who do not know how to do it.
If Debian includes these packages in its repositories, it would win over a
large number of users.

I know LMDE exist, but, If someone wants to use SID or Testing?
And the nice thing would be to have these programs on all branches of
Debian.

Thanks and regards.

Bug#1037305: bookworm-pu: package postfix/3.7.5-2

[Scott Kitterman]

On June 17, 2023 5:25:46 PM UTC, "Adam D. Barratt"  
wrote:
>Control: tags -1 + confirmed
>
>On Sat, 2023-06-10 at 16:50 -0400, Scott Kitterman wrote:
>> First in the normal series of postfix bug fix updates for bookworm.
>> 
>
>Please go ahead.

Thanks.  Uploaded.

Scott K

Bug#997948: [Pkg-pascal-devel] Bug#997948: FPC should provide a way to trigger automatic rebuild of

[Abou Al Montacir]

Hi Paul,

On Mon, 2023-02-20 at 20:57 +0100, Paul Gevers wrote:
> The Release Team scripts don't care about the section, they look at 
> installability. But if we compare the units to C libraries, we normally 
> asks library maintainers to *not* version the dev packages, because then 
> all reverse build dependencies need an update when the SONAME gets 
> bumped, making the transition process very labor-some.
> 
> What we want to achieve here is a way to ensure packages are rebuild 
> (semi) automatically when the units require it. But we *also* want to 
> come up with a way that doesn't require changes in the reverse 
> dependencies at the same time. Consider also that adding new binary 
> packages require a trip through NEW. Would it make sense that every unit 
> provides a virtual abi package, which get embedded in the dependencies 
> during build time, such that when a unit bumps the virtual abi, the 
> release team tools notice and rebuilds can be triggered? Or is that what 
> we already more or less do?
We already have fpc-abi-x.y.z that handle this.
However the problem of fpc-abi-* is that it does not carry a patch indicator.
So one way to fix this is that if we change any interface, we should bump its
version.
Today we define it as fpc-abi-3.2.2. We can add a number like fpc-abi-3.2.2+p1,
+p2, ...
This way each time we change an interface of any unit we bump the patch number.

However, this will solve only the problem for FPC, but not for LCL or any other
units supplied by other projects (like CGE).

So maybe the solution would be to make the units dependency strict. I meant id
fp-units-foo build depends on fp-unit-bar then it should depend on it strictly.
And any rebuild of fp-units-bar shall trigger rebuild of fp-units-foo.
-- 
Cheers,
Abou Al Montacir


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

Bug#1036977: bullseye-pu: package jqueryui/1.12.1+dfsg-8+deb11u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2023-05-31 at 15:13 +0400, Yadd wrote:
> jqueryui is potentially vulnerable to cross-site scripting
> (CVE-2022-31160)
> 

Please go ahead.

Regards,

Adam

Bug#1036975: bullseye-pu: package node-url-parse/1.5.3-1+deb11u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2023-05-31 at 14:47 +0400, Yadd wrote:
> node-url-parse is vulnerable to authorization bypass through
> user-controlled key prior version 1.5.6
> 

Please go ahead.

Regards,

Adam

Bug#1038153: bullseye-pu: package spip/3.2.11-3+deb11u8

[Adam D. Barratt]

Control: tags 1 + confirmed

On Fri, 2023-06-16 at 08:31 +0200, David Prévot wrote:
> SPIP has been updated upstream to fix some security issues (link to
> the
> French-only announcement follows), and we agreed with the security
> team
> that they don’t warrant a DSA this time.
> 
> https://blog.spip.net/Mise-a-jour-de-maintenance-et-securite-sortie-de-SPIP-4-2-3-SPIP-4-1-10.html
> 
> The main backported fix is the one that limits recursion depth in
> protege_champ() function.
> 

Please go ahead.

Regards,

Adam

Bug#1037187: bullseye-pu: package libprelude/5.2.0-3+deb11u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2023-06-07 at 13:06 +0200, Andreas Beckmann wrote:
> 'import prelude' fails in python3 due to some missing symbol,
> rendering
> python3-prelude useless.
> 

Please go ahead.

Regards,

Adam

Bug#1038154: bookworm-pu: package spip/4.1.9+dfsg-1+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Fri, 2023-06-16 at 08:40 +0200, David Prévot wrote:
> SPIP has been updated upstream to fix some security issues (link to
> the
> French-only announcement follows), and we agreed with the security
> team
> that they don’t warrant a DSA this time.
> 
> https://blog.spip.net/Mise-a-jour-de-maintenance-et-securite-sortie-de-SPIP-4-2-3-SPIP-4-1-10.html
> 
> The main backported fix is the one that limits recursion depth in
> protege_champ() function.
> 

Please go ahead.

Regards,

Adam

Bug#1037542: bookworm-pu: package xerial-sqlite-jdbc/3.40.1.0+dfsg-1+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2023-06-14 at 00:01 +0200, Pierre Gruet wrote:
> Grave bug #1036706 has been filled a few days before the release of
> Bookworm.
> This is a security bug associated to CVE-2023-32697.

Please go ahead.

Regards,

Adam

Bug#1038401: vim: focus problems under alacritty and ncurses-term from experimental

[Sven Joachim]

Package: vim
Version: 2:9.0.1378-2
Severity: normal
Forwarded: https://github.com/vim/vim/issues/12499
Tags: fixed-upstream

A recent change to the alacritty terminfo entry (addition of xterm+focus
in the ncurses 20230408 patchlevel) has triggered annoying focus
behavior in vim. Steps to reproduce which work for me in both alacritty
and xterm:

- Install ncurses-term (and ncurses-base) from experimental.

- Start vim without customization:

$ TERM=alacritty LANG=C vim -u /dev/null /etc/fstab

- In Vim, enable mouse support by typing ":set mouse=a".

- Switch focus away from the terminal emulator.  This causes Vim to ring
  the terminal bell (or flash, depending on your terminal emulator's
  visual bell setting).

- Switch focus back.  Vim prints three lines at the bottom of the
  screen: the file name, its first line and the prompt
  "Press ENTER or type command to continue".

This problem has already been reported upstream (see the "Forwarded:"
URL above) and recently been fixed in patch 9.0.1619, see
https://github.com/vim/vim/commit/85ef2df075a189da8b767d7554caaed8077de868.
I have not tested the patch yet, though.


-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.basic
/usr/bin/vim is /usr/bin/vim.basic


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

Versions of packages vim depends on:
ii  libacl1  2.3.1-3
ii  libc62.36-9
ii  libgpm2  1.20.7-10+b1
ii  libselinux1  3.4-1+b6
ii  libsodium23  1.0.18-1
ii  libtinfo66.4+20230603-1
ii  vim-common   2:9.0.1378-2
ii  vim-runtime  2:9.0.1378-2

vim recommends no packages.

Versions of packages vim suggests:
pn  ctags
pn  vim-doc  
pn  vim-scripts  

-- no debconf information

Bug#1037305: bookworm-pu: package postfix/3.7.5-2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2023-06-10 at 16:50 -0400, Scott Kitterman wrote:
> First in the normal series of postfix bug fix updates for bookworm.
> 

Please go ahead.

Regards,

Adam

Bug#1038212: SOLVED

[Joe Fiallo]

Thank

After you confirm, I removed information about the previous package:

rm  /var/lib/dpkg/info/libsasl2-2*


The update process has been completed without errors

.


GRAZIE MILLE


Joe

Bug#1038339: qbittorrent: no icons after upgrade to 4.5.3

[Emanuele Rocca]

Hi,

On 2023-06-17 04:57, Christian Marillat wrote:
> 'Use icons from system theme' is set in preferences ?

Yes. "Use custom UI Theme" is not set, "Use icons from system theme" is.

Please find a screenshot of qt5ct attached, it looks a little weird?

Bug#1037496: mdadm: Please restore support for use without systemd as PID 1

[Mark Hindley]

Michael,

On Sat, Jun 17, 2023 at 07:17:40PM +0300, Michael Tokarev wrote:
> You're still not getting the point.  Which is the lack of real infrastructure
> within other init systems, which needs real work. Which, apparently,
> neither you nor other complainers are willing to do.

I am not complaining. I am asking gently for the reinstatement of the recently
removed non-systemd initscripts. Together with an offer to provide continued and
on-going support for them.

However imperfect those scripts may have been, they worked, were used and were
useful and would continue to be so.

With best wishes

Mark

Bug#1038383: lsb_release: please add the ability to guess_release_from_apt()

[Gioele Barabucci]

On 17/06/23 16:53, Harshula wrote:

On 17/6/23 23:26, Gioele Barabucci wrote:
I understand your request and I fully support having better OS 
information in unstable and testing (see my request to base-files in 
bug #1021663 [1]).


Since package updates transition from unstable to testing, can you 
please elaborate on how this would be fixed in the base-files package?


The automatic migration is not a straitjacket. :)

One can use the mechanism discussed in section 5.14.3 of the Developer's 
Reference [1]:


1) Block the automatic migration via britney/excuses.
2) When a new version is released, dput two different versions: one into 
unstable and one into testing-proposed-updates.


To reduce the amount of work needed for each update of `base-files`, 
`/etc/os-release` can be moved to package like `debian-version-info`, so 
the manual double upload must be done only once per release cycle.


[1] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#direct-updates-to-testing


Regards,

--
Gioele Barabucci

Bug#1038400: /usr/share/perl/.../Pod/Man.pm: String C+: use '\s+2' not '\s0'

[Bjarni Ingi Gislason]

Package: perl-modules-5.36
Version: 5.36.0-7
Severity: normal

Dear Maintainer,

  wrong type size is created with, for example in gcc(1),

.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'

combined with

\s-1ISO \*(C+\s0

#

Do not use "\s0" in a string definition but an absolute number,
as the size of the string could be changed.
Then a situation of "\s-X...\s-Y...\s0...\s0" could emerge.
Type size changes have an effect in "groff", but not in "nroff".

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

Kernel: Linux 6.1.27-1 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages perl-modules-5.36 depends on:
ii  dpkg   1.21.22
ii  perl-base  5.36.0-7

Versions of packages perl-modules-5.36 recommends:
ii  perl  5.36.0-7

perl-modules-5.36 suggests no packages.

-- no debconf information

Bug#1037214: bullseye-pu: package appstream-glib/0.7.18-1+deb11u1

[Matthias Klumpp]

Am Do., 8. Juni 2023 um 21:18 Uhr schrieb Simon McVittie :
>
> On Wed, 07 Jun 2023 at 21:33:29 +0100, Simon McVittie wrote:
> >   [x] attach debdiff against the package in (old)stable
>
> That was, in fact, a lie. See attached (or the nmudiff on #1037206 if
> you'd prefer the unfiltered version).

Thank you for working on this! It will be nice to have this issue
fixed in bullseye soon, as it seems to affect quite a bunch of users!

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#1001045: libconfig-model-dpkg-perl: scan-copyright reports empty license

[Dominique Dumont]

On Mon, 13 Dec 2021 14:24:24 +0530 Vignesh Raman  
wrote:
> Have reported the bug in licensecheck - http://bugs.debian.org/1001615

Looks like this bug won't be fixed in licensecheck.

Then I would suggest to override the license information reported by 
licensecheck.

For details, please see
 
https://github.com/dod38fr/config-model/wiki/Updating-debian-copyright-file-with-cme#filling-missing-information

HTH

Bug#1037496: mdadm: Please restore support for use without systemd as PID 1

[Michael Tokarev]

17.06.2023 19:05, Mark Hindley wrote:

Michael,

On Sat, Jun 17, 2023 at 08:07:52AM +0300, Michael Tokarev wrote:

I wonder do we want no mdadm in debian at all or working mdadm with systemd?
 From the two alternatives I definitely prefer the working one..


That isn't the choice on offer. 


It is.

The suggestion was to raise this bug report severity level to prevent
mdadm from migrating to testing and later on to be removed from Debian.
Without offering real implementation for whatever init systems you use,
which, as the maintainer explained, is not an easy task to support and
he lacks resources to do so.  Raising bug severity like that without
actually doing some real stuff gains nothing besides making mdadm to be
removed.  And with my former mdadm maintainer hat on, I agree completely
the way it worked with sysvinit was a complete mess, systemd bought up
the missing-for-years infrastructure needed for it to work well, finally.

You're still not getting the point.  Which is the lack of real infrastructure
within other init systems, which needs real work. Which, apparently,
neither you nor other complainers are willing to do.

So please don't remove mdadm from debian.

Thanks,

/mjt

Bug#1037496: mdadm: Please restore support for use without systemd as PID 1

[Mark Hindley]

Michael,

On Sat, Jun 17, 2023 at 08:07:52AM +0300, Michael Tokarev wrote:
> I wonder do we want no mdadm in debian at all or working mdadm with systemd?
> From the two alternatives I definitely prefer the working one..

That isn't the choice on offer. The choice is mdadm in Debian which is only
usable with systemd or mdadm in Debian which is usable with systemd, openrc,
runit and sysvinit.

Best wishes

Mark

Bug#1038121: tracker.debian.org: debian/patches check vs. single-debian-patch in debian/source/local-options

[Guillem Jover]

Hi!

On Fri, 2023-06-16 at 20:59:52 +, Thorsten Glaser wrote:
> reassign 1038121 dpkg-dev
> thanks

> Raphael Hertzog dixit:
> >So maybe it's dpkg-source that needs to be tweaked so that such patches
> >have a field "Forwarded: not-needed" and an explanation that the patch
> >is an auto-generated mess that can't be forwarded as is.
> 
> I guess so. I was thinking along these lines, and if the patch tracker
> has no other way to distinguish these (it’s in local-options, so it
> probably does not) then yes, that’s most likely the right solution.

While using «Forwarded: not-needed» for now seems ok, I think we need
a better marking, because IMO the contents should be ideally be
forwarded, just not in that form. Perhaps we should add a new field
called «Autogenerated: yes», or a new value to «Origin: autogenerated»,
perhaps with something parseable appended «, » or
similar. In any case I think I'll add this to my list of things to
revisit in the patch tagging guidelines for when I start that
discussion. For now I've queued the attached patch.

Thanks,
Guillem
From a4f63404cd0e6deb8e771bd5ebf9bc52b398e8d5 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Sat, 17 Jun 2023 16:39:56 +0200
Subject: [PATCH] Dpkg::Source::Package::V2: Mark single-debian-patch as not
 needing forwarding

These patches are autogenerated and in general should not be submitted
upstream as is, as they are going to be a conglomerate of unrelated
changes that need to be submitted upstream in atomic pieces. So applying
the patch tagging guidelines in this situation is not very helpful.

Closes: #1038121
---
 scripts/Dpkg/Source/Package/V2.pm | 10 ++
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/scripts/Dpkg/Source/Package/V2.pm b/scripts/Dpkg/Source/Package/V2.pm
index 4aad9ba8c..1f0946128 100644
--- a/scripts/Dpkg/Source/Package/V2.pm
+++ b/scripts/Dpkg/Source/Package/V2.pm
@@ -621,11 +621,13 @@ sub _get_patch_header {
 
 if ($self->{options}->{single_debian_patch}) {
 return <<'AUTOGEN_HEADER';
-This is an autogenerated patch header for a single-debian-patch file. The
-delta against upstream is either kept as a single patch, or maintained
-in some VCS, and exported as a single patch instead of more manageable
-atomic patches.
+Description: Autogenerated patch header for a single-debian-patch file.
+ The delta against upstream is either kept as a single patch, or maintained
+ in some VCS, and exported as a single patch instead of more manageable
+ atomic patches.
+Forwarded: not-needed
 
+---
 AUTOGEN_HEADER
 }
 
-- 
2.40.1

Bug#1038339: qbittorrent: no icons after upgrade to 4.5.3

[Christian Marillat]

On 17 juin 2023 15:19, Emanuele Rocca  wrote:

> On 2023-06-17 02:49, Christian Marillat wrote:
>> You must configure qt* for that.
>> 
>> Install qt5ct
>> 
>> sudo apt-get install qt5ct
>> 
>> Add "export QT_QPA_PLATFORMTHEME=qt5ct" in the ~/.bashrc or ~/.zshrc
>> 
>> In qt5ct go to 'Icon theme' tab and select an icon theme.
>
> Done that, still no icons unfortunately.

I'm not sure if you have received this e-mail. e-mail rejected by gmail.


'Use icons from system theme' is set in preferences ?

Christian

Bug#1038399: RFP: log2ram -- Log2Ram is a collection of scripts designed to offload log files from storage to RAM, primarily aimed at Raspberry Pi systems. By storing log files in RAM, Log2Ram helps r

[Doug Baggett]

Package: wnpp
Severity: wishlist

* Package name: log2ram
  Version : 1.6.1 
  Upstream Author : Name 
* URL : https://github.com/azlux/log2ram
* License : (MIT/X)
  Programming Lang: (Bash)
  Description : Log2Ram is a collection of scripts designed to offload log 
files from storage to RAM, primarily aimed at Raspberry Pi systems. By storing 
log files in RAM, Log2Ram helps reduce the wear on storage devices, such as SD 
cards, and potentially extends their lifespan. Although initially developed for 
Raspberry Pi devices, Log2Ram is compatible with all Debian-based systems.

Useful for RaspberryPi for not writing on the SD card all the time. You need it 
because your SD card doesn't want to suffer anymore!

Explanations: The script creates a /var/log mount point in RAM. So any writing 
of the log to the /var/log folder will not actually be written to disk (in this 
case to the SD card on a Raspberry Pi) but directly to RAM. By default, every 
day the CRON will synchronize the contents in RAM with the folder located on 
the physical disk. The script will also make this copy of RAM to disk in case 
of machine shutdowns (but, of course, it still won't do it in case of power 
failures). This way you can avoid excessive writing on the SD card and extend 
its life.

Log2Ram's script works on every Linux system.

Bug#1037196: bullseye-pu: package dbus/1.12.28-0+deb11u1

[Simon McVittie]

On Wed, 07 Jun 2023 at 14:24:36 +0100, Simon McVittie wrote:
> [ Reason ]
> Fix a local denial of service for which the security team does not intend
> to do a DSA (dbus#457, #1037151; CVE assignment pending).

CVE-2023-34969 was assigned. I didn't think it was worth editing the
changelog and repinning the package just to add that, so the diff I
previously attached is still current.

I went ahead with uploading to bullseye-proposed-updates in the hope that
this will save the release team some time.

>   [ ] the issue is verified as fixed in unstable
>   - intentionally not done yet due to the full freeze, because dbus
> has udebs

Now fixed in unstable by 1.14.8-1.

smcv

Bug#1029347: Removal notice: obsolete

[Ilias Tsitsimpis]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: haskell-taskell -- ROM; obsolete
Control: severity -2 normal

On Sat, Jan 21, 2023 at 05:04PM, Ilias Tsitsimpis wrote:
> I intend to remove this package:
> 
>   * It has no rev dependencies
>   * The current version FTBFS (BD-Uninstallable)
>   * Upstream development has stopped
>   * It's not part of the latest Stackage LTS
>   * Newer versions depend on libraries not available in Debian
>   * It has never been a part of a stable Debian release

Dear FTP masters, please remove haskell-taskell from unstable.

-- 
Ilias

Bug#1038397: RFA: arbtt -- Automatic Rule-Based Time Tracker

[Ilias Tsitsimpis]

Package: wnpp
Severity: normal
X-Debbugs-Cc: ar...@packages.debian.org
Control: affects -1 + src:arbtt

I request an adopter for the arbtt package.

No one in the Debian Haskell Group is willing to maintain this package
(see https://bugs.debian.org/1026136). If no one shows interest in this
package, I will request its removal.

The package description is:
 The program arbtt, the automatic rule-based time tracker, allows you to
 investigate how you spend your time, without having to manually specify what
 you are doing. arbtt records what windows are open and active, and provides
 you with a powerful rule-based language to afterwards categorize your work.

-- 
Ilias

Bug#1038396: RM: gtkboard -- ROM; ancient, unmaintained upstream, uses sdl 1.2 and gtk 2

[Barak A. Pearlmutter]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: gtkbo...@packages.debian.org
Control: affects -1 + src:gtkboard

Nothing depends on this package. It is ancient, unmaintained upstream,
and uses the obsolete SDL 1.2 and GTK 2.

Bug#1038212: Aggiornamento a Debian 12 interrotto

[Bastian Germann]

Am 17.06.23 um 15:43 schrieb Joe Fiallo:

  il file dei trigger "ci" contiene una direttiva "cctsvite-noawai0" sconosciuta


I do not know where this error comes from. Where is that ci trigger? It is 
certainly not part of the package.

Bug#1038395: bist: Should we keep this package in Debian?

[Boyuan Yang]

Package: bist
Severity: important
Version: 0.5.2-1.2
Tags: sid
X-Debbugs-CC: da...@debian.org

Dear Debian bist package maintainer,

I noticed package bist ( https://tracker.debian.org/pkg/bist ) maintained by
you recently in Debian. It seems that this package saw no maintainer upload
for 11 years, and currently FTBFS due to incompatibility with GCC 11+. Package
bist already missed last Debian Stable release due to FTBFS.

Looking at its upstream condition, its upstream vcs hosting (gna.org) has shut
down. A web page that looks like project home page
https://www.autistici.org/interzona/bist.html says that the software has
ceased its development.

Given all the conditions above, I am wondering whether we should continue to
keep package bist in Debian archive. Please let me know whether you would like
to continue with the package maintenance of bist. If there is no possible
improvement, I plan to request package removal to Debian FTP Masters in the
Debian 13 development cycle, possibly after 2023-07.

Thanks and looking forward to your reply,
Boyuan Yang


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

Bug#1038339: qbittorrent: no icons after upgrade to 4.5.3

[Christian Marillat]

On 17 juin 2023 15:19, Emanuele Rocca  wrote:

> On 2023-06-17 02:49, Christian Marillat wrote:
>> You must configure qt* for that.
>> 
>> Install qt5ct
>> 
>> sudo apt-get install qt5ct
>> 
>> Add "export QT_QPA_PLATFORMTHEME=qt5ct" in the ~/.bashrc or ~/.zshrc
>> 
>> In qt5ct go to 'Icon theme' tab and select an icon theme.
>
> Done that, still no icons unfortunately.

'Use icons from system theme' is set in preferences ?

Christian

Bug#1038383: lsb_release: please add the ability to guess_release_from_apt()

[Harshula]

Hi Gioele,

On 17/6/23 23:26, Gioele Barabucci wrote:

I understand your request and I fully support having better OS 
information in unstable and testing (see my request to base-files in bug 
#1021663 [1]).


Since package updates transition from unstable to testing, can you 
please elaborate on how this would be fixed in the base-files package?


Thanks,
Harshula

Bug#1038210: please provide a way to use UCRT instead of MSVCRT

[Stephen Kitt]

On Fri, 16 Jun 2023 17:00:19 +0200, Sébastien Villemot 
wrote:
> Le vendredi 16 juin 2023 à 16:42 +0200, Sébastien Villemot a écrit :
> > 2. at runtime, by passing a modified specs file to the cross-compiler
> > (more specifically, replacing -lmsvcrt by -lucrt in the libgcc section)  
> 
> Actually I realize that this solution probably does not work very
> reliably, in particular for C++ programs (because libstdc++ would still
> be built against MSVCRT).

Right, that wouldn’t work — or rather, it would work in some cases but not in
others...

> So the only reliable solution may be to provide different binary
> packages with cross-compilers for UCRT.

I’m leaning towards taking the same approach as Fedora, using a new triplet,
...-w64-mingw32ucrt (see https://fedoraproject.org/wiki/Changes/F37MingwUCRT
for details and
https://sourceforge.net/p/mingw-w64/mailman/mingw-w64-public/thread/CAMxuvax0nSO5%2BMRNQG%3DkBiN%3DPPAFbXrzAR-OVgS0kiKoVPeWSw%40mail.gmail.com/
for a very brief discussion with upstream).

Regards,

Stephen


pgp6iwNzeM5RL.pgp
Description: OpenPGP digital signature

Bug#1038394: libpipewire-0.3-0: client configurations and modules not included or required

[Thomas Weißschuh]

Package: libpipewire-0.3-0
Version: 0.3.19-4
Severity: minor

Dear Maintainer,

libpipewire as packaged currently does not ship or depend on the client
configurations and modules.
These are only included in the full "pipewire" package.

When libpipewire is used in its default configuration this will lead to 
user-visible warnings.

```
[W][00355.592783] pw.conf | [ conf.c: 939 try_load_conf()] can't load config 
client.conf: No such file or directory
[E][00355.593459] pw.conf | [ conf.c: 963 pw_conf_load_conf_for_context()] 
can't load default config client.conf: No such file or directory
```

Upstream advise is that such a setup of libpipewire is not useful for general 
use.
The Fedora package as maintained by the PipeWire lead developer also included 
the configs and modules as part of the libpipewire package. (called 
"pipewire-libs" there)

Additional info:
* https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3296
* https://src.fedoraproject.org/rpms/pipewire/blob/rawhide/f/pipewire.spec
* 
https://fedora.pkgs.org/38/fedora-x86_64/pipewire-libs-0.3.67-1.fc38.x86_64.rpm.html
* https://github.com/mpv-player/mpv/issues/11790


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

Kernel: Linux 5.10.0-23-amd64 (SMP w/2 CPU threads)
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 libpipewire-0.3-0 depends on:
ii  libc6   2.31-13+deb11u6
ii  libspa-0.2-modules  0.3.19-4

Versions of packages libpipewire-0.3-0 recommends:
pn  pipewire  

libpipewire-0.3-0 suggests no packages.

-- no debconf information

Bug#1038132: qtwebengine-opensource-src: FTBFS: ../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: Error: operand type mismatch for `shr'

[Adrian Bunk]

On Thu, Jun 15, 2023 at 09:23:20PM +0200, Sebastian Ramacher wrote:
> Source: qtwebengine-opensource-src
> Version: 5.15.13+dfsg-1~deb12u1
> Severity: serious
> Tags: ftbfs sid trixie
> Justification: fails to build from source (but built successfully in the past)
> 
> https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src=amd64=5.15.13%2Bdfsg-1%7Edeb12u1%2Bb1=1686790387=0
> 
> FAILED: 
> obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavcodec_flacdec.o 
> /usr/bin/gcc -MMD -MF 
> obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavcodec_flacdec.o.d 
> -DHAVE_AV_CONFIG_H -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
> -DFFMPEG_CONFIGURATION=NULL -DCHROMIUM_NO_LOGGING -D_ISOC99_SOURCE 
> -D_LARGEFILE_SOURCE -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 
> -DOFFICIAL_BUILD -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
> -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -DNDEBUG -DNVALGRIND 
> -DDYNAMIC_ANNOTATIONS_ENABLED=0 
> -I../../3rdparty/chromium/third_party/ffmpeg/chromium/config/Chrome/linux/x64 
> -I../../3rdparty/chromium/third_party/ffmpeg 
> -I../../3rdparty/chromium/third_party/ffmpeg/compat/atomics/gcc -Igen 
> -I../../3rdparty/chromium -Igen -fPIC -Wno-deprecated-declarations 
> -fomit-frame-pointer -w -std=c99 -pthread -fno-math-errno -fno-signed-zeros 
> -fno-tree-vectorize -fno-strict-aliasing --param=ssp-buffer-size=4 
> -fstack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC 
> -pipe -pthread -m64 -g0 -fvisibility=hidden -Wno-unused-local-typedefs 
> -Wno-maybe-uninitialized -Wno-deprecated-declarations 
> -fno-delete-null-pointer-checks -Wno-comments -Wno-packed-not-aligned 
> -Wno-dangling-else -Wno-missing-field-initializers -Wno-unused-parameter -O2 
> -fno-ident -fdata-sections -ffunction-sections -I/usr/include/opus -std=gnu11 
> -c 
> ../../3rdparty/chromium/third_party/ffmpeg/libavcodec/autorename_libavcodec_flacdec.c
>  -o obj/third_party/ffmpeg/ffmpeg_internal/autorename_libavcodec_flacdec.o
> ../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h: 
> Assembler messages:
> ../../3rdparty/chromium/third_party/ffmpeg/libavcodec/x86/mathops.h:125: 
> Error: operand type mismatch for `shr'
>...

Upstream ffmpeg fails in unstable+experimental with the same error:
https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/ffmpeg.html

I suspect the new binutils is the trigger, I haven't investigated 
whether this is a bug in gas or something that has to be fixed in ffmpeg.

> Cheers

cu
Adrian

Bug#1023237: openjdk-11: Keep out of testing and stable

[theofficialgman]

Is there a better reason this should be kept out of testing and stable?
Many users find this openjdk-11 helpful and necessary for
stability/continuity reasons over the current LTS. Security updates will
last for 3+ more years so I don't see any reason why this should be held
back from stable and testing.

Bug#1038393: supertux: improve d/watch file

[Patrice Duroux]

Source: supertux
Version: 0.6.3-2
Severity: wishlist

Dear Maintainer,

Here is a patch that can do it.

Regards,
Patrice


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

Kernel: Linux 6.3.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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
diff --git a/debian/watch b/debian/watch
index 83aa7f1..a6f6860 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,3 +1,3 @@
 version=4
-opts="uversionmangle=s/-rc/~rc/;s/-alpha/~alpha/;s/-beta/~beta/;s/-Source//" \
-https://github.com/SuperTux/supertux/releases 
.*/SuperTux-v?@ANY_VERSION@-Source@ARCHIVE_EXT@
+opts="uversionmangle=s/-rc/~rc/;s/-alpha/~alpha/;s/-beta/~beta/, 
filenamemangle=s%(?:.*?)?v?@ANY_VERSION@(@ARCHIVE_EXT@)%@PACKAGE@-$1$2%" \
+https://github.com/SuperTux/@PACKAGE@/tags 
(?:.*?/)?v?@ANY_VERSION@@ARCHIVE_EXT@

Bug#1038392: RM: qnodeeditor -- ROM; Dead Upstream; Useless

[Boyuan Yang]

Package: ftp.debian.org
Control: affects -1 + src:qnodeeditor
X-Debbugs-Cc: qnodeedi...@packages.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: by...@debian.org
Severity: normal

Dear FTP Masters,

Please remove qnodeeditor https://tracker.debian.org/pkg/qnodeeditor from
Debian archive. It was initially intended to be used as a library dependency,
but eventually left unused. Its upstream also ceased its development. All
binary packages from src:qnodeeditor have no reverse dependencies and reverse
build-dependencies.

Thanks,
Boyuan Yang


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

Bug#1038391: groff: tbl uU (half-line-up) doesn't work for cells enclosed in T{ T}

[наб]

Package: groff
Version: 1.22.4-10
Severity: normal

Dear Maintainer,

I wanted to have half-lines between my table rows; tbl(1) says:
  u,UMove the corresponding column up one half-line.
Great! However:
  $ cat tblest
  .TS
  l  l  l
  lu lu lu .
  a b   c
  A T{
  B
  T}C
  .TE
  $ groff -t -Tps tblest > tblest.ps
shows that (see image) cells A and C are raised, but cell B isn't.

Best,
наб

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages groff depends on:
ii  groff-base  1.22.4-10
ii  libc6   2.36-9
ii  libgcc-s1   12.2.0-14
ii  libstdc++6  12.2.0-14
ii  libx11-62:1.8.4-2
ii  libxaw7 2:1.0.14-1
ii  libxmu6 2:1.1.3-3
ii  libxt6  1:1.2.1-1.1

Versions of packages groff recommends:
ii  ghostscript  10.0.0~dfsg-11
ii  imagemagick  8:6.9.11.60+dfsg-1.6
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.6
ii  libpaper11.1.29
ii  netpbm   2:11.01.00-2
ii  perl 5.36.0-7
ii  psutils  1.17.dfsg-4

groff suggests no packages.

-- no debconf information
.TS
l l l 
lu lu lu .
a   b   c
A   T{
B
T}  C
.TE


signature.asc
Description: PGP signature

Bug#995218: xinv3d new upstream release

[Patrice Duroux]

Hi,

Last version here https://github.com/JoesCat/xinv3d is 1.5.0 (Feb 23, 2022) but
it seems then that its author re-started here
https://github.com/JoesCat/xinvaders3d, version 1.5.0 (Feb 24, 2023).

Regards,
Patrice

Bug#907384: plasma-discover: needrestart breaks Plasma-discover upgrade mechanism

[Hanisch]

Package: plasma-discover
Version: 5.27.5-2
Followup-For: Bug #907384
X-Debbugs-Cc: ch-hani...@t-online.de

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: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages plasma-discover depends on:
ii  appstream0.16.1-2
ii  apt-config-icons 0.16.1-2
ii  kio  5.103.0-1
ii  libappstreamqt2  0.16.1-2
ii  libc62.36-9
ii  libkf5attica55.103.0-1
ii  libkf5configcore55.103.0-2
ii  libkf5configgui5 5.103.0-2
ii  libkf5coreaddons55.103.0-1
ii  libkf5crash5 5.103.0-1
ii  libkf5dbusaddons55.103.0-1
ii  libkf5i18n5  5.103.0-1
ii  libkf5idletime5  5.103.0-2
ii  libkf5jobwidgets55.103.0-1
ii  libkf5kiocore5   5.103.0-1
ii  libkf5kiogui55.103.0-1
ii  libkf5newstuffcore5  5.103.0-1
ii  libkf5notifications5 5.103.0-1
ii  libkf5service-bin5.103.0-1
ii  libkf5service5   5.103.0-1
ii  libkf5widgetsaddons5 5.103.0-1
ii  libkf5windowsystem5  5.103.0-1
ii  libmarkdown2 2.2.7-2
ii  libpackagekitqt5-1   1.1.1-1
ii  libqt5core5a 5.15.8+dfsg-12
ii  libqt5dbus5  5.15.8+dfsg-12
ii  libqt5gui5   5.15.8+dfsg-12
ii  libqt5network5   5.15.8+dfsg-12
ii  libqt5qml5   5.15.8+dfsg-3
ii  libqt5quick5 5.15.8+dfsg-3
ii  libqt5webview5   5.15.8-2+b1
ii  libqt5widgets5   5.15.8+dfsg-12
ii  libstdc++6   13.1.0-5
ii  packagekit   1.2.6-5
ii  plasma-discover-common   5.27.5-2
ii  qml-module-org-kde-kcoreaddons   5.103.0-1
ii  qml-module-org-kde-kirigami2 5.103.0-1
ii  qml-module-org-kde-kquickcontrols5.103.0-1
ii  qml-module-org-kde-kquickcontrolsaddons  5.103.0-1
ii  qml-module-org-kde-qqc2desktopstyle  5.103.0-1
ii  qml-module-qtquick-dialogs   5.15.8-2

Versions of packages plasma-discover recommends:
pn  apt-config-icons-hidpi 
pn  apt-config-icons-large 
pn  apt-config-icons-large-hidpi   
pn  kde-config-updates 
ii  plasma-discover-backend-fwupd  5.27.5-2
pn  software-properties-qt 

Versions of packages plasma-discover suggests:
pn  plasma-discover-backend-flatpak  

-- no debconf information

Bug#1037194: bookworm-pu: package dbus/1.14.8-1~deb12u1

[Simon McVittie]

On Wed, 07 Jun 2023 at 14:11:05 +0100, Simon McVittie wrote:
> Fix a local denial of service for which the security team does not intend
> to do a DSA (dbus#457, #1037151; CVE assignment pending).

CVE-2023-34969 was now assigned.

> I'll be uploading to unstable to get
> wider user testing as soon as the trixie cycle opens

1.14.8 has been in unstable for a few days. fwupd:armhf and
slic3r-prusa:arm64 show up as regressions, but both look more like a
flaky test than a dbus bug.

A release-candidate of the bookworm package is available from:

deb [trusted=yes] https://people.debian.org/~smcv/12.1 bookworm-proposed 
main

This is intentionally versioned slightly lower (as
1.14.8-1~deb12u1~1+1+g3b42362c0) but the changelog is the only difference.

>   [ ] the issue is verified as fixed in unstable
>   - intentionally not done yet due to the full freeze

Now fixed in unstable by a functionally equivalent package.

Updated debdiff attached: the only difference between this and what I
previously sent (which is what's now in unstable) is the extra changelog
entry.

I've uploaded to stable-NEW in the hope that the stable release team will
be happy to continue following upstream stable branches like we did for
bullseye and buster, but please let me know if any of the changes are
considered inappropriate.

Thanks,
smcv
debdiff *.dsc | filterdiff -p1 -xaminclude_static.am -xMakefile.in -x'*/Makefile.in' -xconfigure

diffstat for dbus-1.14.6 dbus-1.14.8

 AUTHORS |9 ++
 Makefile.in |2 
 NEWS|   29 
 aminclude_static.am |2 
 bus/Makefile.in |2 
 bus/connection.c|   15 
 cmake/DBus1ConfigVersion.cmake  |2 
 configure   |   26 +++
 configure.ac|4 -
 dbus/Makefile.in|2 
 dbus/dbus-connection-internal.h |2 
 dbus/dbus-connection.c  |   11 ++-
 dbus/dbus-internals.h   |2 
 dbus/dbus-message.c |   12 ++-
 dbus/dbus-spawn-win.c   |8 +-
 dbus/dbus-sysdeps-win.c |4 -
 debian/changelog|   22 ++
 debian/control  |2 
 debian/gbp.conf |2 
 debian/watch|2 
 doc/dbus-api-design.duck|4 -
 test/Makefile.in|2 
 test/data/valid-config-files/forbidding.conf.in |3 
 test/monitor.c  |   84 +---
 24 files changed, 207 insertions(+), 46 deletions(-)

diff -Nru dbus-1.14.6/AUTHORS dbus-1.14.8/AUTHORS
--- dbus-1.14.6/AUTHORS	2022-10-05 11:03:53.0 +0100
+++ dbus-1.14.8/AUTHORS	2023-06-06 14:00:36.0 +0100
@@ -15,6 +15,7 @@
 Artem Bityutskiy 
 Arun Raghavan 
 Aurelien Jarno 
+Barnabás Pőcze 
 Benedikt Heine 
 Benjamin Reed 
 Bertrand SIMONNET 
@@ -46,6 +47,7 @@
 Daniel Reed 
 Daniel Wendt 
 Dan Williams 
+Dave Jones 
 Dave Reisner 
 David King 
 David Redondo 
@@ -58,6 +60,7 @@
 Dmitri Iouchtchenko 
 DreamNik 
 Eamon Walsh 
+Evgeny Vereshchagin 
 eXeC001er 
 Federico Mena Quintero 
 Felipe Franciosi 
@@ -75,6 +78,7 @@
 Havoc Pennington 
 Havoc Pennington 
 Hendrik Buschmeier 
+hongjinghao 
 hyeric 
 ilovezfs 
 Ioan-Adrian Ratiu 
@@ -90,6 +94,7 @@
 Jean-Louis Fuchs 
 Jens Granseuer 
 Jérémie Dimino 
+Jeremi Piotrowski 
 Jesper Dam 
 Jiří Klimeš 
 Joe Marcus Clarke 
@@ -104,7 +109,9 @@
 Jon Trowbridge 
 Julien Schueller 
 Justin Lee 
+Kai A. Hiller 
 Kay Sievers 
+Khem Raj 
 Kimmo Hämäläinen 
 Kir Kolyshkin 
 Kjartan Maraas 
@@ -126,6 +133,7 @@
 Marc Brockschmidt 
 Marc Mutz 
 Marc Mutz 
+Marco Trevisan (Treviño) 
 Marcus Brinkmann 
 Mark Brand 
 Mark McLoughlin 
@@ -236,6 +244,7 @@
 Wulf C. Krueger 
 Xan Lopez 
 Yaakov Selkowitz 
+Yen-Chin, Lee 
 Yiyang Fei 
 Zack Rusin 
 Zeeshan Ali 
diff -Nru dbus-1.14.6/bus/connection.c dbus-1.14.8/bus/connection.c
--- dbus-1.14.6/bus/connection.c	2022-10-02 15:06:53.0 +0100
+++ dbus-1.14.8/bus/connection.c	2023-06-06 14:00:36.0 +0100
@@ -2374,6 +2374,21 @@
   if (!dbus_message_set_sender (message, DBUS_SERVICE_DBUS))
 return FALSE;
 
+  /* Make sure the message has a non-zero serial number, otherwise
+   * bus_transaction_capture_error_reply() will not be able to mock up
+   * a corresponding reply for it. Normally this would be delayed until
+   * the first time we actually send the message out from a
+   * connection, when the transaction is committed, but that's too late
+   * in this case.
+   */
+  if (dbus_message_get_serial (message) == 0)
+{
+  dbus_uint32_t 

Bug#1038212: Aggiornamento a Debian 12 interrotto

[Joe Fiallo]

Buongiorno

Scaricando il pacchetto libsasl2-2 singolarmente da un repository 
diverso  il messaggio cambia leggermente ma l'errore rimane



wget 
http://ftp.us.debian.org/debian/pool/main/c/cyrus-sasl2/libsasl2-2_2.1.28+dfsg-10_arm64.deb


sudo dpkg -i libsasl2-2_2.1.28+dfsg-10_arm64.deb

(Lettura del database... 76693 file e directory attualmente installati.)
Preparativi per estrarre libsasl2-2_2.1.28+dfsg-10_arm64.deb...
dpkg: errore nell'elaborare l'archivio 
libsasl2-2_2.1.28+dfsg-10_arm64.deb (--install):
 il file dei trigger "ci" contiene una direttiva "cctsvite-noawai0" 
sconosciuta

Si sono verificati degli errori nell'elaborazione:
 libsasl2-2_2.1.28+dfsg-10_arm64.deb

Grazie

    Joe

Bug#1038383: lsb_release: please add the ability to guess_release_from_apt()

[Gioele Barabucci]

Control: severity -1 wishlist
Control: tags -1 wontfix
Control: merge 1020893 -1

On 17/06/23 13:54, Harshula wrote:
The old lsb_release.py script contains the function 
guess_release_from_apt(). Can you please add similar functionality to 
lsb-release to fix the regression?


Dear Harshula,

I understand your request and I fully support having better OS 
information in unstable and testing (see my request to base-files in bug 
#1021663 [1]).


However, fixing the deficiencies of Debian's `/etc/os-release` is not 
the job of this minimalist implementation of `lsb_release`.


By the way, LSB is no longer an active project and all distributions, 
including Debian, stopped supporting LSB in 2015 [2]. Scripts and 
infrastructure relying on `lsb_release` should be ported to modern (and 
simpler) cross-distro facilities like `/etc/os-release`.


Regards,

[1] https://bugs.debian.org/1021663
[2] https://lwn.net/Articles/658809/

--
Gioele Barabucci

Bug#1038389: devscripts: dch --bpo should reference bpo12 and bookworm-backports, not bullseye

[John Goerzen]

Package: devscripts
Version: 2.23.4
Severity: normal

dch --bpo in bookworm references bullseye-backports.


-- Package-specific info:

--- /etc/devscripts.conf ---
Empty.

--- ~/.devscripts ---
DEBCOMMIT_STRIP_MESSAGE=yes
DEBSIGN_KEYID=0x276D7B77B69B756C7CB68669DD29F88442839ED3

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/16 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 devscripts depends on:
ii  dpkg-dev  1.21.22
ii  fakeroot  1.31-1.2
ii  file  1:5.44-3
ii  gnupg 2.2.40-1.1
ii  gnupg22.2.40-1.1
ii  gpgv  2.2.40-1.1
ii  libc6 2.36-9
ii  libfile-dirlist-perl  0.05-3
ii  libfile-homedir-perl  1.006-2
ii  libfile-touch-perl0.12-2
ii  libfile-which-perl1.27-2
ii  libipc-run-perl   20220807.0-1
ii  libmoo-perl   2.005005-1
ii  libwww-perl   6.68-1
ii  patchutils0.4.2-1
ii  perl  5.36.0-7
ii  python3   3.11.2-1+b1
ii  sensible-utils0.0.17+nmu1
ii  wdiff 1.2.2-5

Versions of packages devscripts recommends:
ii  apt 2.6.1
ii  curl7.88.1-10
ii  dctrl-tools 2.24-3+b1
ii  debian-keyring  2022.12.24
ii  dput1.1.3
ii  dupload 2.9.12
ii  equivs  2.3.1
pn  libdistro-info-perl 
ii  libdpkg-perl1.21.22
ii  libencode-locale-perl   1.05-3
pn  libgit-wrapper-perl 
pn  libgitlab-api-v4-perl   
ii  liblist-compare-perl0.55-2
ii  liblwp-protocol-https-perl  6.10-1
ii  libsoap-lite-perl   1.27-3
ii  libstring-shellquote-perl   1.04-3
ii  libtry-tiny-perl0.31-2
ii  liburi-perl 5.17-1
ii  licensecheck3.3.5-1
ii  lintian 2.116.3
ii  man-db  2.11.2-2
ii  patch   2.7.6-7
ii  pristine-tar1.50
ii  python3-apt 2.6.0
ii  python3-debian  0.1.49
ii  python3-magic   2:0.4.26-3
ii  python3-requests2.28.1+dfsg-1
ii  python3-unidiff 0.7.3-1
ii  python3-xdg 0.28-2
ii  strace  6.1-0.1
ii  unzip   6.0-28
ii  wget1.21.3-1+b2
ii  xz-utils5.4.1-0.2

Versions of packages devscripts suggests:
pn  adequate  
ii  at3.2.5-1+b1
ii  autopkgtest   5.28
pn  bls-standalone
ii  bsd-mailx [mailx] 8.1.2-0.20220412cvs-1
ii  build-essential   12.9
pn  check-all-the-things  
pn  cvs-buildpackage  
ii  debhelper 13.11.4
pn  diffoscope
pn  disorderfs
ii  dose-extra7.0.0-1+b2
pn  duck  
pn  elpa-devscripts   
pn  faketime  
ii  gnuplot   5.4.4+dfsg1-2
ii  gnuplot-nox [gnuplot] 5.4.4+dfsg1-2+b2
pn  how-can-i-help
ii  libauthen-sasl-perl   2.1600-3
pn  libdbd-pg-perl
ii  libfile-desktopentry-perl 0.22-3
ii  libterm-size-perl 0.211-1+b2
ii  libtimedate-perl  2.3300-2
ii  libyaml-syck-perl 1.34-2+b1
ii  mailutils [mailx] 1:3.15-4
pn  mmdebstrap
pn  mozilla-devscripts
ii  mutt  2.2.9-1+b1
ii  openssh-client [ssh-client]   1:9.2p1-2
pn  piuparts  
ii  postgresql-client 15+248
ii  postgresql-client-13 [postgresql-client]  13.11-0+deb11u1
ii  postgresql-client-15 [postgresql-client]  15.3-0+deb12u1
pn  pristine-lfs  
ii  quilt 0.67+really0.66-1
pn  ratt  
pn  reprotest 
pn  svn-buildpackage  
ii  w3m   0.5.3+git20230121-2

-- no debconf information

Bug#1038339: qbittorrent: no icons after upgrade to 4.5.3

[Emanuele Rocca]

On 2023-06-17 02:49, Christian Marillat wrote:
> You must configure qt* for that.
> 
> Install qt5ct
> 
> sudo apt-get install qt5ct
> 
> Add "export QT_QPA_PLATFORMTHEME=qt5ct" in the ~/.bashrc or ~/.zshrc
> 
> In qt5ct go to 'Icon theme' tab and select an icon theme.

Done that, still no icons unfortunately.

Bug#1037465: redmine autopkgtest fails with ruby-rouge 4.1 in experimental

[Pirate Praveen]

On Tue, 13 Jun 2023 13:03:19 +0530 Pirate Praveen 
 wrote:

> Package: redmine
> Version: 5.0.4-5
> Severity: important
>
> Redmine is not compatible with ruby-rouge 4.1 in experimental.
> autopkgtest fails with
>
> Could not find gem 'rouge (~> 3.28)' in cached gems or installed
> locally.
>
> Full log attached. Please adapt redmine to rouge 4.1 so I can 
reupload

> it unstable soon.
>

I'm hoping to upload ruby-rouge 4.1 to unstable on July 1st. redmine is 
the last blocking package. If redmine is fixed before that, I can 
upload ruby-rouge earlier too.

Bug#1038388: shotcut: Shotcut 23 timeline widget is blank

[Doug Larrick]

Package: shotcut
Version: 23.06.14+git20230616+ds-1
Severity: important

Dear Maintainer,

On my system at least, Shotcut 23 displays a blank area where the timeline
should be. The portable tar image provided by the Shotcut project at
https://shotcut.org/download/ does not show this issue.

Doing a bit of mix and match with this upstream tar image, I can reproduce the
issue there by not setting QML2_IMPORT_PATH in their wrapper script. To my
untrained eye, it appears the upstream is shipping with qml files from Qt6,
whereas the packages available from Debian (qml-module-qtquick2 etc.) are from
Qt5.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages shotcut depends on:
ii  frei0r-plugins 1:2.3.0-dmo1
ii  libc6  2.36-9
ii  libfftw3-double3   3.3.10-1
ii  libgcc-s1  12.2.0-14
ii  libjs-three111+dfsg1-3
ii  libmlt++7  7.14.0-1
ii  libmlt77.14.0-1
ii  libqt6core66.4.2+dfsg-10
ii  libqt6gui6 6.4.2+dfsg-10
ii  libqt6multimedia6  6.4.2-5
ii  libqt6network6 6.4.2+dfsg-10
ii  libqt6opengl6  6.4.2+dfsg-10
ii  libqt6qml6 6.4.2+dfsg-1
ii  libqt6quick6   6.4.2+dfsg-1
ii  libqt6quickcontrols2-6 6.4.2+dfsg-1
ii  libqt6quickwidgets66.4.2+dfsg-1
ii  libqt6sql6 6.4.2+dfsg-10
ii  libqt6widgets6 6.4.2+dfsg-10
ii  libqt6xml6 6.4.2+dfsg-10
ii  libstdc++6 12.2.0-14
ii  melt   7.14.0-1
ii  qml-module-qtgraphicaleffects  5.15.8-2
ii  qml-module-qtqml-models2   5.15.8+dfsg-3
ii  qml-module-qtquick-controls5.15.8-2
ii  qml-module-qtquick-controls2   5.15.8+dfsg-2
ii  qml-module-qtquick-dialogs 5.15.8-2
ii  qml-module-qtquick-extras  5.15.8-2
ii  qml-module-qtquick-layouts 5.15.8+dfsg-3
ii  qml-module-qtquick-window2 5.15.8+dfsg-3
ii  qml-module-qtquick25.15.8+dfsg-3
ii  shotcut-data   23.06.14+git20230616+ds-1

shotcut recommends no packages.

shotcut suggests no packages.

-- no debconf information