date:20230117

I recently came across this bug report while working on cleaning up Lintian 
errors on 
qtwebengine-opensource-src.

The summarized version of the problem is that the file was originally licensed 
under a non-
DFSG-free license, but was later changed by Unicode to be under a DFSG-free 
licence.

Google has some discussion of the issue here:

https://bugs.chromium.org/p/google-breakpad/issues/detail?id=270[1]

Based on what was documented, they changed the license of the file in their 
repository 
here:

https://chromium.googlesource.com/breakpad/breakpad/+/
14bbefbd9600e08d6a34d7250faa8bc9dba2113e%5E%21/[2]

LLVM has recently changed the license of the code in their repository for the 
version 16 
release:

https://llvm.org/doxygen/ConvertUTF_8cpp_source.html[3]

The text of the DFSG-free license can be found at:

https://www.unicode.org/license.txt[4]

The result is that some of the packages in Debian still have the problematic 
code listed in 
the header, but others do not.

Packages with the non-DFSG-free license (correct Lintian positive):
binaryen
desmume
funguloids
libdbd-odbc-perl
llvm-toolchain-9
llvm-toolchain-13
llvm-toolchain-14
llvm-toolchain-15
opencollada
parser
spring
tla
unshield
zeek

Packages with a DFSG-free license (false Lintian positive):
firefox
firefox-esr
llvm-toolchain-snapshot
qt6-webengine
qtwebengine-opensource-src
thunderbird

It is easy to tell which packages have the problematic license because they 
contain the 
words “products supporting”, which phrase is not contained in the acceptable 
license.

I propose that the Lintian check be modified to only flag files that contain 
“products 
supporting”.  Once that change is made, I would be happy to work with the 
various 
maintainers of the problematic packages to help them get the correct licensing 
into their 
upstream files.


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

Bug#965894: xfonts-scalable: diff for NMU version 1:1.0.3-1.3

2023-01-17 Thread Simon McVittie

Control: tags 965894 + pending

I've prepared an NMU for xfonts-scalable (versioned as 1:1.0.3-1.3) with
the attached diff, also available at
.

Since this only contains changes that were already merged into the
maintainers' VCS months ago, I'm going to upload a NMU without further
delay.

Thanks,
smcv
diffstat for xfonts-scalable_1.0.3-1.2 xfonts-scalable_1.0.3-1.3

 .gitignore |   78 +
 debian/compat  |1 
 xfonts-scalable-1.0.3/debian/changelog |   18 +++
 xfonts-scalable-1.0.3/debian/control   |6 +-
 xfonts-scalable-1.0.3/debian/rules |9 ++-
 xfonts-scalable-1.0.3/debian/watch |3 -
 6 files changed, 109 insertions(+), 6 deletions(-)

diff -u xfonts-scalable-1.0.3/debian/changelog xfonts-scalable-1.0.3/debian/changelog
--- xfonts-scalable-1.0.3/debian/changelog
+++ xfonts-scalable-1.0.3/debian/changelog
@@ -1,3 +1,21 @@
+xfonts-scalable (1:1.0.3-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload, incorporating changes from the maintainers'
+packaging repository
+
+  [ Julien Cristau ]
+  * Remove Cyril and David from Uploaders.
+  * Add Vcs-* control fields.
+  * Use https URL in debian/watch.
+
+  [ Simon McVittie ]
+  * d/control: Update Vcs-* for migration to salsa.debian.org
+  * Use recommended debhelper compat level 13 (Closes: #965894)
+  * d/rules: Add missing build-arch, build-indep targets (Policy §4.9)
+  * d/control: Declare that the build does not require (fake)root
+
+ -- Simon McVittie   Sun, 15 Jan 2023 14:18:32 +
+
 xfonts-scalable (1:1.0.3-1.2) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
reverted:
--- xfonts-scalable-1.0.3/debian/compat
+++ xfonts-scalable-1.0.3.orig/debian/compat
@@ -1 +0,0 @@
-5
diff -u xfonts-scalable-1.0.3/debian/control xfonts-scalable-1.0.3/debian/control
--- xfonts-scalable-1.0.3/debian/control
+++ xfonts-scalable-1.0.3/debian/control
@@ -2,15 +2,17 @@
 Section: fonts
 Priority: optional
 Maintainer: Debian X Strike Force 
-Uploaders: David Nusinow , Cyril Brulebois 
 Build-Depends:
- debhelper (>= 5.0.31),
+ debhelper-compat (= 13),
  xfonts-utils (>= 1:7.6~),
  automake,
  autoconf,
  xutils-dev (>= 1:7.5+1),
  pkg-config,
 Standards-Version: 3.8.3
+Vcs-Git: https://salsa.debian.org/xorg-team/font/xfonts-scalable.git
+Vcs-Browser: https://salsa.debian.org/xorg-team/font/xfonts-scalable
+Rules-Requires-Root: no
 
 Package: xfonts-scalable
 Architecture: all
diff -u xfonts-scalable-1.0.3/debian/rules xfonts-scalable-1.0.3/debian/rules
--- xfonts-scalable-1.0.3/debian/rules
+++ xfonts-scalable-1.0.3/debian/rules
@@ -34,6 +34,7 @@
 
 
 build: build-stamp
+build-indep: build-stamp
 build-stamp: $(STAMP_DIR)/prepare
 	dh_testdir
 	autoreconf -vfi
@@ -45,6 +46,9 @@
 	cd build && $(MAKE)
 	>$@
 
+build-arch:
+# Nothing to do
+
 clean: xsfclean
 	dh_testdir
 	dh_testroot
@@ -64,7 +68,7 @@
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 
 	cd build && $(MAKE) DESTDIR=$(CURDIR)/debian/tmp install
@@ -81,7 +85,8 @@
 	dh_testroot
 
 	dh_installdocs
-	dh_install --sourcedir=debian/tmp --fail-missing --exclude=fonts.dir --exclude=fonts.scale
+	dh_install --sourcedir=debian/tmp --exclude=fonts.dir --exclude=fonts.scale
+	dh_missing --fail-missing --exclude=fonts.dir --exclude=fonts.scale
 	dh_installxfonts
 	dh_installchangelogs
 	dh_compress
diff -u xfonts-scalable-1.0.3/debian/watch xfonts-scalable-1.0.3/debian/watch
--- xfonts-scalable-1.0.3/debian/watch
+++ xfonts-scalable-1.0.3/debian/watch
@@ -1,2 +1,3 @@
+#git=git://anongit.freedesktop.org/xorg/font/bitstream-type1
 version=3
-http://xorg.freedesktop.org/releases/individual/font/ font-bitstream-type1-(.*)\.tar\.gz
+https://xorg.freedesktop.org/releases/individual/font/ font-bitstream-type1-(.*)\.tar\.gz
only in patch2:
unchanged:
--- xfonts-scalable-1.0.3.orig/.gitignore
+++ xfonts-scalable-1.0.3/.gitignore
@@ -0,0 +1,78 @@
+#
+#		X.Org module default exclusion patterns
+#		The next section if for module specific patterns
+#
+#	Do not edit the following section
+# 	GNU Build System (Autotools)
+aclocal.m4
+autom4te.cache/
+autoscan.log
+ChangeLog
+compile
+config.guess
+config.h
+config.h.in
+config.log
+config-ml.in
+config.py
+config.status
+config.status.lineno
+config.sub
+configure
+configure.scan
+depcomp
+.deps/
+INSTALL
+install-sh
+.libs/
+libtool
+libtool.m4
+ltmain.sh
+lt~obsolete.m4
+ltoptions.m4
+ltsugar.m4
+ltversion.m4
+Makefile
+Makefile.in
+mdate-sh
+missing
+mkinstalldirs
+*.pc
+py-compile
+stamp-h?
+symlink-tree
+texinfo.tex
+ylwrap
+
+#	Do not edit the following section
+# 	Edit Compile Debug Document Distribute
+*~
+*.[0-9]
+*.[0-9]x
+*.bak
+*.bin
+core
+*.dll
+*.exe
+*-ISO*.bdf
+*-JIS*.bdf
+*-KOI8*.bdf
+*.kld
+*.ko
+*.ko.cmd
+*.lai
+*.l[oa]
+*.[oa]
+*.obj
+*.patch
+*.so
+*.pcf.gz
+*.pdb
+*.tar.bz2
+*.tar.gz
+#
+#

Bug#965901: xfonts-encodings: diff for NMU version 1:1.0.4-2.2

2023-01-17 Thread Simon McVittie

Control: tags 965901 + pending

I've prepared an NMU for xfonts-encodings (versioned as 1:1.0.4-2.2) with
the attached diff, also available at
.

Since this only contains changes that were already merged into the
maintainers' VCS months ago, I'm going to upload a NMU without further
delay.

Thanks,
smcv
diffstat for xfonts-encodings_1.0.4-2.1 xfonts-encodings_1.0.4-2.2

 .gitignore  |   80 
 debian/compat   |1 
 xfonts-encodings-1.0.4/debian/changelog |   17 ++
 xfonts-encodings-1.0.4/debian/control   |7 +-
 xfonts-encodings-1.0.4/debian/copyright |2 
 xfonts-encodings-1.0.4/debian/rules |9 ++-
 xfonts-encodings-1.0.4/debian/watch |2 
 7 files changed, 110 insertions(+), 8 deletions(-)

diff -u xfonts-encodings-1.0.4/debian/changelog xfonts-encodings-1.0.4/debian/changelog
--- xfonts-encodings-1.0.4/debian/changelog
+++ xfonts-encodings-1.0.4/debian/changelog
@@ -1,3 +1,20 @@
+xfonts-encodings (1:1.0.4-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload, incorporating changes from the maintainers'
+packaging repository
+
+  [ Julien Cristau ]
+  * Switch Vcs-* control fields to https.
+  * Switch xorg.freedesktop.org URLs in packaging to https.
+
+  [ Simon McVittie ]
+  * d/control: Update Vcs-* for migration to salsa.debian.org
+  * Use recommended debhelper compat level 13 (Closes: #965901)
+  * d/rules: Add missing targets build-arch, build-indep (Policy §4.9)
+  * d/control: Declare that the build does not require (fake)root
+
+ -- Simon McVittie   Sun, 15 Jan 2023 14:14:38 +
+
 xfonts-encodings (1:1.0.4-2.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
reverted:
--- xfonts-encodings-1.0.4/debian/compat
+++ xfonts-encodings-1.0.4.orig/debian/compat
@@ -1 +0,0 @@
-5
diff -u xfonts-encodings-1.0.4/debian/control xfonts-encodings-1.0.4/debian/control
--- xfonts-encodings-1.0.4/debian/control
+++ xfonts-encodings-1.0.4/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian X Strike Force 
 Build-Depends:
- debhelper (>= 5.0.0),
+ debhelper-compat (= 13),
 Build-Depends-Indep:
  pkg-config,
  xfonts-utils (>= 1:7.6~),
@@ -11,8 +11,9 @@
  automake,
  xutils-dev (>= 1:7.5+1),
 Standards-Version: 3.8.3
-Vcs-Git: git://git.debian.org/git/pkg-xorg/font/xfonts-encodings.git
-Vcs-Browser: http://git.debian.org/?p=pkg-xorg/font/xfonts-encodings.git
+Vcs-Git: https://salsa.debian.org/xorg-team/font/xfonts-encodings.git
+Vcs-Browser: https://salsa.debian.org/xorg-team/font/xfonts-encodings
+Rules-Requires-Root: no
 
 Package: xfonts-encodings
 Architecture: all
diff -u xfonts-encodings-1.0.4/debian/copyright xfonts-encodings-1.0.4/debian/copyright
--- xfonts-encodings-1.0.4/debian/copyright
+++ xfonts-encodings-1.0.4/debian/copyright
@@ -1,5 +1,5 @@
 This package contains the encodings tarball downloaded from
-http://xorg.freedesktop.org/releases/individual/font/
+https://xorg.freedesktop.org/releases/individual/font/
 
 The XFree86/Xorg encoding files are in the public domain.
 
diff -u xfonts-encodings-1.0.4/debian/rules xfonts-encodings-1.0.4/debian/rules
--- xfonts-encodings-1.0.4/debian/rules
+++ xfonts-encodings-1.0.4/debian/rules
@@ -34,6 +34,7 @@
 
 
 build: build-stamp
+build-indep: build-stamp
 build-stamp:
 	dh_testdir
 	autoreconf -vfi
@@ -45,6 +46,9 @@
 	cd build && $(MAKE)
 	>$@
 
+build-arch:
+# Nothing to do
+
 clean: xsfclean
 	dh_testdir
 	dh_testroot
@@ -63,7 +67,7 @@
 install: build
 	dh_testdir
 	dh_testroot
-	dh_clean -k
+	dh_prep
 	dh_installdirs
 	cd build && $(MAKE) DESTDIR=$(CURDIR)/debian/tmp install
 
@@ -77,7 +81,8 @@
 	dh_testroot
 
 	dh_installdocs
-	dh_install --sourcedir=debian/tmp --list-missing
+	dh_install --sourcedir=debian/tmp
+	dh_missing --list-missing
 	dh_installchangelogs
 	dh_link
 	dh_strip
diff -u xfonts-encodings-1.0.4/debian/watch xfonts-encodings-1.0.4/debian/watch
--- xfonts-encodings-1.0.4/debian/watch
+++ xfonts-encodings-1.0.4/debian/watch
@@ -1,3 +1,3 @@
 #git=git://anongit.freedesktop.org/xorg/font/encodings
 version=3
-http://xorg.freedesktop.org/releases/individual/font/ encodings-(.*)\.tar\.gz
+https://xorg.freedesktop.org/releases/individual/font/ encodings-(.*)\.tar\.gz
only in patch2:
unchanged:
--- xfonts-encodings-1.0.4.orig/.gitignore
+++ xfonts-encodings-1.0.4/.gitignore
@@ -0,0 +1,80 @@
+#
+#		X.Org module default exclusion patterns
+#		The next section if for module specific patterns
+#
+#	Do not edit the following section
+# 	GNU Build System (Autotools)
+aclocal.m4
+autom4te.cache/
+autoscan.log
+ChangeLog
+compile
+config.guess
+config.h
+config.h.in
+config.log
+config-ml.in
+config.py
+config.status
+config.status.lineno
+config.sub
+configure
+configure.scan
+depcomp
+.deps/
+INSTALL
+install-sh
+.libs/
+libtool
+libtool.m4
+ltmain.sh
+lt~obsolete.m4
+ltoptions.m4
+ltsugar.m4

Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors

2023-01-17 Thread Stefano Simonucci

Package: src:linux
Version: 6.0.12-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

in the last upgrade I got this errors:
Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.0.0-6-amd64 all 
KERNEL_SRC=/lib/modules/6.0.0-6-amd64/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.0.0-6-amd64 (x86_64)
Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at 
/var/lib/dpkg/info/linux-headers-6.0.0-6-amd64.postinst line 11.

Then the package remains unconfigured, but installed. The next reboot gives a 
kernel panic, so I must boot previous kernels. 
Thanks
Best regards
Stefano

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUS
product_name: All Series
product_version: System Version
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: 2202
board_vendor: ASUSTeK COMPUTER INC.
board_name: Z97-K
board_version: Rev X.0x

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp

auto dsl-provider
iface dsl-provider inet ppp
pre-up /bin/ip link set eth1 up # line maintained by pppoeconf
provider dsl-provider

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM 
Controller [8086:0c00] (rev 06)
Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor DRAM Controller 
[1043:8534]
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: hsw_uncore

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal 
decode])
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller [1043:8534]
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:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB 
xHCI Controller [8086:8cb1] (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family USB xHCI 
Controller [1043:8534]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset 
Family ME Interface #1 [8086:8cba]
Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family ME Interface 
[1043:8534]
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: mei_me
Kernel modules: mei_me

00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB 
EHCI Controller #2 [8086:8cad] (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family USB EHCI 
Controller [1043:8534]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio 
Controller [8086:8ca0]
Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family HD Audio 
Controller [1043:8616]
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: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI 
Express Root Port 1 [8086:8c90] (rev d0) (prog-if 00 [Normal decode])
Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family PCI Express 
Root Port 1 [1043:8534]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr-

Bug#1028451: 2nd DisplayPort doesn't get video

2023-01-17 Thread Bastian Venthur

Package: src:linux
Version: 6.1.4-1
Followup-For: Bug #1028451
X-Debbugs-Cc: vent...@debian.org

Dear Maintainer,

I can confirm this bug on my Lenovo T14s with integrated AMD graphics. I have
two monitors connected via docking station. One Display Port the other one via
HDMI, since 6.1 only one of them shows active already after starting the boot
process.

Via Gnome's system settings, I can see that both monitors are there, I can
however only ever activate one of them (if that makes sense). That is maybe the
new bit of information from the original bugreport as that not only the 2nd DP
is affected but the HDMI as well.

On <= 6.0 this was never an issue. Please note that I'm currently running 6.0
in order to use both monitors.


Cheers,

Bastian



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20UHS0G000
product_version: ThinkPad T14s Gen 1
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: R1CET73W(1.42 )
board_vendor: LENOVO
board_name: 20UHS0G000
board_version: SDK0J40697 WIN

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
Root Complex [1022:1630]
Subsystem: Lenovo Renoir/Cezanne Root Complex [17aa:5082]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode])
Subsystem: Lenovo Renoir/Cezanne PCIe GPP Bridge [17aa:5082]
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:02.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode])
Subsystem: Lenovo Renoir/Cezanne PCIe GPP Bridge [17aa:5082]
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:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode])
Subsystem: Lenovo Renoir/Cezanne PCIe GPP Bridge [17aa:5082]
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:02.7 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode])
Subsystem: Lenovo Renoir/Cezanne PCIe GPP Bridge [17aa:5082]
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:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 51)
Subsystem: Lenovo FCH SMBus Controller [17aa:5082]
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-

Bug#1023697: can wolfssl bug be closed?

2023-01-17 Thread gs-bugs . debian . org

Can this be closed?  Are there any action items remaining for this bug?

I am still getting messages that packages depending on wolfssl are
"marked for autoremoval from testing on 2023-01-27"

Thank you.  Glenn

Bug#1028541: lvm2: LVM filters render server unbootable

2023-01-17 Thread Bastian Blank

On Tue, Jan 17, 2023 at 08:13:33AM +0100, Christian Herzog wrote:
> update: we were told by upstream that there is a known instability between lvm
> and udev-generated symlinks and a devices file should be used instead. So
> that's what we're going to do.

I think I actually know what the problem is.  pvscan is run during the
udev event handling, esp in the initramfs where no systemd is available
to move that out.  Modifications to devices and symlinks are only
applies at the end of the event.  So symlinks will always be missing on
the first event.

If you have systemd running, it uses systemd-run, then it is just a race
condition between udev and systemd, which one is faster in finishing.

The only way to fix this is to provide the symlink information to pvscan
in addition to the device itself and let it figure that out.

Regards,
Bastian

-- 
No problem is insoluble.
-- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4

Bug#1029064: binaryen: Fix for ConvertUTF.cpp licensing problem

Source: binaryen
Version: 108-1
Severity: wishlist

Your source contains a copy of ConvertUTF.cpp at 
third_party/llvm-project/ConvertUTF.cpp.

As https://lintian.debian.org/tags/license-problem-convert-utf-code indicates, 
the license listed at the top of the file is not DFSG-free.

However, as https://bugs.chromium.org/p/google-breakpad/issues/detail?id=270 
and 
https://chromium.googlesource.com/breakpad/breakpad/+/14bbefbd9600e08d6a34d7250faa8bc9dba2113e%5E%21/
 explain, the license was replaced by Unicode with a different license that is 
DFSG-free.

Specifically, the file can now be licensed with the text at 
https://www.unicode.org/license.txt.

It looks like your upstream code uses a copy acquired from LLVM.  Beginning 
with version 16, LLVM has replaced the license the problematic licensing text 
with the current license as can be seen at 
https://llvm.org/doxygen/ConvertUTF_8cpp_source.html.

Once your upstream updates the license, you can remove your current Lintian 
override.

Bug#1029065: mirrors: ftp.bg.d.o wrong CNAME

2023-01-17 Thread velin

Package: mirrors
Severity: normal

Dear Maintainer,

Currently ftp.bg.debian.org CNAME is towards klecker-ftp.debian.org,
which is not in Bulgaria. I'd like to request to change the CNAME to
ftp.uni-sofia.bg.

Regards,
--velin

Bug#1029070: /usr/lib/python3/dist-packages/ipalib/x509.py: Broken by python3-cryptography API break in 38.0.1

2023-01-17 Thread Sam Morris

Package: python3-ipalib
Version: 4.9.8-1
Severity: important
File: /usr/lib/python3/dist-packages/ipalib/x509.py

$ ipa vault-find
Traceback (most recent call last):
  File "/usr/bin/ipa", line 27, in 
from ipaclient.__main__ import main
  File "/usr/lib/python3/dist-packages/ipaclient/__main__.py", line 7, in 

from ipalib import api, cli
  File "/usr/lib/python3/dist-packages/ipalib/__init__.py", line 921, in 

from ipalib.frontend import Command, LocalOrRemote, Updater
  File "/usr/lib/python3/dist-packages/ipalib/frontend.py", line 31, in 

from ipalib.parameters import create_param, Param, Str, Flag
  File "/usr/lib/python3/dist-packages/ipalib/parameters.py", line 125, in 

from ipalib.x509 import (
  File "/usr/lib/python3/dist-packages/ipalib/x509.py", line 91, in 
@crypto_utils.register_interface(crypto_x509.Certificate)
AttributeError: module 'cryptography.utils' has no attribute 
'register_interface'. Did you mean: 'verify_interface'?

According to  this is caused by
cryptography 38.0.1 which removed the register_interface decorator.

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

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

Versions of packages python3-ipalib depends on:
ii  freeipa-common  4.9.8-1
ii  gpg 2.2.40-1
ii  gpg-agent   2.2.40-1
ii  keyutils1.6.3-2
ii  librpm9 4.18.0+dfsg-1
ii  python3 3.10.6-3+b1
ii  python3-cffi1.15.1-5
ii  python3-cryptography38.0.4-2
ii  python3-dbus1.3.2-3
ii  python3-dnspython   2.2.1-2
ii  python3-gssapi  1.8.2-1
ii  python3-ldap3.4.3-2+b1
ii  python3-libipa-hbac 2.8.2-1~1.gbp44da1a
ii  python3-lxml4.9.2-1
ii  python3-netaddr 0.8.0-2
ii  python3-netifaces   0.11.0-2
ii  python3-pyasn1  0.4.8-3
ii  python3-pyasn1-modules  0.2.8-1
ii  python3-qrcode  7.3.1-1
ii  python3-requests2.28.1+dfsg-1
ii  python3-setuptools  65.5.0-1.1
ii  python3-six 1.16.0-4
ii  python3-usb 1.2.1-1
ii  python3-yubico  1.3.3-0.3
ii  systemd 252.4-1

python3-ipalib recommends no packages.

python3-ipalib suggests no packages.

-- no debconf information

Bug#1029071: enable pam_umask usergroups by default

2023-01-17 Thread Tomas Senabre

Package: libpam-modules
Version: 1.4.0-9+deb11u1
Followup-For: Bug #583958

This bug has not yet been resolved and is still causing problems in 2023. The
setting for UMASK is not respected for logins on tty as well as via SSH or
SSHFS.  I have spent the last 10 years manually adding this configuration to
the file with every new Debian install:

echo "session optional pam_umask.so usergroups" >> /etc/pam.d/common-session

This line of code is present in most GNU/Linux distributions by default and
solves the problem.


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

Kernel: Linux 5.10.0-20-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 libpam-modules depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  libaudit1  1:3.0-2
ii  libc6  2.31-13+deb11u5
ii  libcrypt1  1:4.4.18-4
ii  libdb5.3   5.3.28+dfsg1-0.8
ii  libnsl21.3.0-2
ii  libpam-modules-bin 1.4.0-9+deb11u1
ii  libpam0g   1.4.0-9+deb11u1
ii  libselinux13.1-3
ii  libtirpc3  1.3.1-1+deb11u1

libpam-modules recommends no packages.

Bug#1028201: riseup-vpn unable to find a usable polkit agent under phosh

2023-01-17 Thread Guido Günther

Hi,

On Sun, Jan 08, 2023 at 06:54:17PM +0530, Pirate Praveen wrote:
> Package: riseup-vpn,phosh
> severity: grave
> 
> On mobian under phosh (librem 5), riseup-vpn gives error.
> output of riseup-vpn attached.

I don't think the severity is justified for phosh as it's certianly not
unusable or mostly so. I tihnk the same is true for riseup-net.

Cheers,
 -- Guido

> 
> phosh provides polkit-1-auth-agent
> 
> phosh 0.23
> riseup-vpn 0.21.11+ds1-2+b1
> 

> No systray icon available.
> qml: flavor: riseup-vpn
> QSystemTrayIcon::setVisible: No Icon set
> QObject::connect: No such signal 
> QPlatformNativeInterface::systemTrayWindowChanged(QScreen*)
> 2023/01/08 18:44:03 Client expects anon auth
> 2023/01/08 18:44:03 Checking for updates...
> qml: delay...
> 2023/01/08 18:44:14 Get "https://downloads.leap.se/RiseupVPN/linux/lastver": 
> net/http: TLS handshake timeout
> 2023/01/08 18:44:14 Fetching MOTD for riseup.net
> 2023/01/08 18:44:16 There are 4 pending messages
> 2023/01/08 18:44:16 firewall stop
> 2023/01/08 18:44:17 Fetching gateways...
> 2023/01/08 18:44:17 Cannot find any usable polkit
> 2023/01/08 18:44:17 ERROR: no polkit
> qml: errors, setting root.error
> qrc:/components/InitErrors.qml:39: ReferenceError: splashSpinner is not 
> defined
> qrc:/components/InitErrors.qml:38:13: QML PropertyChanges: Cannot assign to 
> non-existent property "visible"
> qml: errors, setting root.error
> qml: errors, setting root.error
> 2023/01/08 18:44:38 Close: cleanup and vpn shutdown...
> 2023/01/08 18:44:38 firewall stop
> 2023/01/08 18:44:38 openvpn stop
> 
> Catched signal(2): quitting

Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors

2023-01-17 Thread Bastian Blank

Control: reassign -1 dkms - breaks kernel installation
Control: severity -1 grave

On Tue, Jan 17, 2023 at 09:36:26AM +0100, Stefano Simonucci wrote:
> Package: src:linux
> Version: 6.0.12-1
> Severity: critical
> Justification: breaks the whole system

No, it does not.  The kernel is the system and you always have an old
one.

> in the last upgrade I got this errors:
> Building module:
> Cleaning build area...
> make -j8 KERNELRELEASE=6.0.0-6-amd64 all 
> KERNEL_SRC=/lib/modules/6.0.0-6-amd64/build...(bad exit status: 2)
> Error! Bad return status for module build on kernel: 6.0.0-6-amd64 (x86_64)
> Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information.

dkms fails the installation if anything it tries to build does not work.
This must go, reassigning accordingly.

Bastian

-- 
You're dead, Jim.
-- McCoy, "The Tholian Web", stardate unknown

Bug#1029067: ssmtp sends parts of its own config file on invalid inputs

2023-01-17 Thread Alex

Package: ssmtp
Version: ssmtp sends on invalid inputs parts of its own config file
Severity: important

Dear Maintainer,
when running
$ ssmtp root
and then typing
Test[RETURN]
[Ctrl-D]

ssmtp sends a mail with parts of its own configuration and possibly even
other files. The result looks like this:

---
Test
TP aliases
# 
# Format:   local_account:outgoing_address:mailhub
#
# Example: root:your_login@your.domain:mailhub.your.domain[:port]
# where [:port] is an optional port number that defaults to 25.
 is required no 
# MX records are consulted. Commonly mailhosts are named mail.domain.com
mailhub=mail

# Where will the mail seem to come from?
rewriteDomain=vms.laxu.de

# The full hostname
hostname=seafile.vms.laxu.de

# Are users allowed to set their own From: address?
# YES - Allow the user to specify their own From: address
# NO - Use the system generated From: address
FromLineOverride=NO
/backups:/usr/sbin/nologin
list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
irc:x:39:39:ircd:/run/ircd:/usr/sbin/nologin
gnats:x:41:41:Gnats Bug-Reporting System 
(admin):/var/lib/gnats:/usr/sbin/nologin
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
...
---

it does not happen, when the input is terminated with a "." on a single
line before sending Ctrl-D.

it looks like it could even be a overflow bug. It didn't crash for me,
through.

-- System Information:
Debian Release: bullseye
Foreign Architectures: i386

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

ssmtp recommends no packages.

ssmtp suggests no packages.

Bug#1029024: isc-dhcp-server: apparmor blocks reading files outside /etc/dhcpd

2023-01-17 Thread Santiago Ruano Rincón

Hi,

El 16/01/23 a las 18:29, Simone Piccardi escribió:
> Package: isc-dhcp-server
> Version: 4.4.3-P1-1.1
> Severity: normal
> 
> Dear Maintainer,
> 
> 
> After upgrading from version 4.4.3-P1-1 to 4.4.3-P1-1.1 the added
> apparmor configurations block the include of files outside /etc/dhcp/,
> like DDNS TSIG keys definition that are usually installed under
> /etc/bind.

As commented in usr.sbin.dhcpd:

  # access to bind9 keys for dynamic update
  # It's expected that users will generate one key per zone and have it
  # stored in both /etc/bind9 (for bind to access) and /etc/dhcp/ddns-keys
  # (for dhcpd to access).
  /etc/dhcp/ddns-keys/** r,

See also https://wiki.debian.org/DDNS

> I can understand avoiding to read files everywhere, but the use of
> TSIG keys defined by bind with is quite a common usage, that stop
> working with misleading permission denied error for readable files.
> 
> This break previously working configurations, whitout a note in
> the changelog.
> 

Indeed, unfortunately the NMU is missing a changelog update.

Cheers,

 -- Santiago


signature.asc
Description: PGP signature

Bug#1029066: diffoscope: FTBFS if no internet is available (using internet connection during build)

2023-01-17 Thread Gianfranco Costamagna


Source: diffoscope
Version: 232
Severity: serious

Hello, your package FTBFS when internet is not available during control file 
regeneration phase

dpkg-buildpackage: info: source package diffoscope
dpkg-buildpackage: info: source version 232
dpkg-buildpackage: info: source distribution unstable
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using options from diffoscope-232/debian/source/options: 
--tar-ignore=.*.sw? --tar-ignore=*/*~ --tar-ignore=,,* --tar-ignore=.[#~]* 
--tar-ignore=.deps --tar-ignore=.git --tar-ignore=.gitattributes 
--tar-ignore=.gitignore --tar-ignore=.gitmodules
 debian/rules clean
dh clean --with python3 --with bash-completion --buildsystem=pybuild
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
debian/tests/control.sh
Generating the debian/tests/control file...
WARNING: The directory '/sbuild-nonexistent/.cache/pip' or its parent directory 
is not owned or is not writable by the current user. The cache has been 
disabled. Check the permissions and owner of that directory. If executing pip 
with sudo, you should use sudo's -H flag.
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service 
not known')': /simple/setuptools/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service 
not known')': /simple/setuptools/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service 
not known')': /simple/setuptools/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service 
not known')': /simple/setuptools/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service 
not known')': /simple/setuptools/
ERROR: Could not find a version that satisfies the requirement setuptools (from 
versions: none)
ERROR: No matching distribution found for setuptools
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pep517/meta.py", line 72, in load
path = Path(build_as_zip(builder))
^
  File "/usr/lib/python3/dist-packages/pep517/meta.py", line 59, in build_as_zip
builder(dest=out_dir)
  File "/usr/lib/python3/dist-packages/pep517/meta.py", line 53, in build
env.pip_install(system['requires'])
  File "/usr/lib/python3/dist-packages/pep517/envbuild.py", line 103, in 
pip_install
check_call(
  File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3', '-m', 'pip', 
'install', '--ignore-installed', '--prefix', '/tmp/pep517-build-env-i1vz1wye', 
'setuptools', 'wheel']' returned non-zero exit status 1.
Files debian/tests/control and debian/tests/control.tmp differ

The generated control file differs from the actual one.
A sourceful upload of this package is needed.

Differences:
--- debian/tests/control2023-01-13 07:05:01.0 +
+++ debian/tests/control.tmp2023-01-17 02:06:59.340564039 +
@@ -7,7 +7,7 @@
 #   $ mv debian/tests/control.tmp debian/tests/control
 
 Tests: pytest-with-recommends

-Depends: python3-all, diffoscope, black, python3-pytest, python3-h5py, file, 
linux-image-amd64 [amd64] | linux-image-generic [amd64], abootimg, acl, 
apksigcopier, apksigner, apktool [!ppc64el !s390x], binutils-multiarch, bzip2, 
caca-utils, colord, coreboot-utils, db-util, default-jdk-headless | default-jdk 
| java-sdk, device-tree-compiler, docx2txt, e2fsprogs, enjarify, ffmpeg, 
fontforge-extras, fonttools, fp-utils [!ppc64el !s390x], genisoimage, gettext, 
ghc, ghostscript, giflib-tools, gnumeric, gnupg, gnupg-utils, hdf5-tools, 
html2text, imagemagick, jsbeautifier, libarchive-tools, libxmlb-dev, llvm, lz4 
| liblz4-tool, lzip, mono-utils, ocaml-nox, odt2txt, oggvideotools [!s390x], 
openssh-client, openssl, pgpdump, poppler-utils, procyon-decompiler, 
python3-pdfminer, r-base-core, rpm2cpio, sng, sqlite3, squashfs-tools, tcpdump, 
u-boot-tools, unzip, wabt, xmlbeans, xxd, xz-utils, zip, zstd, androguard, 
python3-argcomplete, python3-binwalk, python3-defusedxml, python3-distro, 
python3-guestfs, python3-jsondiff, python3-progressbar, python3-pypdf, 
python3-debian, python3-pyxattr, python3-rpm, python3-tlsh
+Depends: python3-all, diffoscope, black, python3-pytest, python3-h5py, file,

Bug#1011049: freetype: breaks architecture bootstrap by depending on librsvg2-dev

2023-01-17 Thread Hugh McMaster

Hi Simon,

On Fri, 13 Jan 2023 at 06:20, Simon McVittie wrote:
>
> On Wed, 11 Jan 2023 at 16:55:05 +1100, Hugh McMaster wrote:
> > I've added support for your suggested build profile
> > (pkg.freetype.nodemos), since it's useful (and more efficient) to
> > build without the demos at times.
>
> If freetype2-demos does what its name suggests, then this might be
> in-scope for the non-package-specific build profile noinsttest ("Disable
> binary packages consisting entirely of automated tests, manual tests,
> example/demo programs and test tools"). The scope of noinsttest is a bit
> wider than its name suggests, because "as-installed" automated tests
> like gtk-4-tests and examples/demos/manual tests like gtk-4-examples
> seem like they have quite a lot in common.
>
> However, I see there are other packages that depend on freetype2-demos,
> which makes it unclear to me whether freetype2-demos *only* contains
> demos, or whether it also contains general-purpose utilities analogous to
> the ones in libglib2.0-bin (which would be out-of-scope for noinsttest).

freetype2-demos only contains programs used to test and showcase the
FreeType 2 font engine. They aren't general-purpose utilities.

Would this mean the binary package qualifies for the noinsttest build profile?

Bug#1025206: Rescission of ITP

2023-01-17 Thread Asa Mirzaieva

I rescind my intent to package as it is already packaged here (
https://build.opensuse.org/package/show/home:bespokesynth/bespokesynth-current)
and I'm not sure I'll have time to maintain this.

Bug#1029064: Lintian Bug

There is some additional information in the Lintian bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854209[1]

-- 
Soren Stoutner
so...@stoutner.com


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854209


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

Bug#1029068: vcswatch: fails to run due to full file system.

2023-01-17 Thread Hilmar Preusse

Package: qa.debian.org
Severity: important

Dear Maintainer,

the vcswatch service currently fails to run:

"Error: fatal: Unable to create
'/srv/scratch/qa.debian.org/vcswatch/c/cm-super/shallow.lock': No
space left on device"

this hits a few of my git repositories.  Please be so kind to solve
the issue and implement some kind of monitoring.  ;-)

Hilmar

-- 
sigmentation fault


signature.asc
Description: PGP signature

Bug#1029069: libc6: wcswidth doesn't report correct width for ：

2023-01-17 Thread Craig Small

Package: libc6
Version: 2.36-6
Severity: minor

I've been trying to work out why the Chinese translation for free
doesn't want to line up the columns like everyone else, report is
at [1]

For some reason, it thinks the strange colon used in the translation is
one character wide, but its actually two. This means the column is
mis-aligned.

A small test program:
--
#define _XOPEN_SOURCE 1
#include 
#include 
#include 

void printme(char *str)
{
int len, width;
wchar_t wstr[BUFSIZ];

len = mbstowcs(wstr, str, BUFSIZ);
width = wcswidth(wstr, 99);
printf("len=%d width=%d\n",
len, width, str);
printf("%s%.s%s\n", str, 6 - width, "blah");
}

int main()
{
printme(":");
printme("：");

}
--
$~/width
len=1 width=1
:blah
len=-1 width=1
：blah

We can see that the second colon is 2 wide, the "b" in blah lines up
with the "n" in len but wcswidth thinks it is 2.  I have no idea why
this is so and even where this information comes from.

It's not the end-of-the world sort of bug, but it is a very stange one.

 - Craig

1: https://gitlab.com/procps-ng/procps/-/issues/213


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

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

Versions of packages libc6 depends on:
ii  libgcc-s1  12.2.0-10

Versions of packages libc6 recommends:
ii  libidn2-0  2.3.3-1+b1

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.80
pn  glibc-doc  
ii  libc-l10n  2.36-6
pn  libnss-nis 
pn  libnss-nisplus 
ii  locales2.36-6

-- debconf information excluded

Bug#1029097: pam: FTBFS on hurd-i386

2023-01-17 Thread Sam Hartman

> "Svante" == Svante Signell  writes:
Svante> modules_pam_nologin_tst-pam_nologin-retval.c.diff disabling
Svante> two subtests failing on GNU/Hurd.  -

Why do these subtests fail?

Svante> 
Svante> debian_libpam-modules-bin.install.hurd-i386.patch creating
Svante> an install file for Hurd excluding two systemd-specific
Svante> files not needed.

Why is installing these files harmful?
I'm reluctant to take  this patch unless it actually breaks something
and there's no other way to do it.
If I take this patch, then I'll have to remember to update the hurd
install list every time something changes.


signature.asc
Description: PGP signature

Bug#1029066: diffoscope: FTBFS if no internet is available (using internet connection during build)

2023-01-17 Thread Vagrant Cascadian

Control: found 1029066 230

On 2023-01-17, Gianfranco Costamagna wrote:
> Hello, your package FTBFS when internet is not available during control file 
> regeneration phase
...
> debian/tests/control.sh
> Generating the debian/tests/control file...
...
> ERROR: Could not find a version that satisfies the requirement setuptools 
> (from versions: none)
> ERROR: No matching distribution found for setuptools
> Traceback (most recent call last):
>File "", line 1, in 
>File "/usr/lib/python3/dist-packages/pep517/meta.py", line 72, in load
>  path = Path(build_as_zip(builder))
>  ^
>File "/usr/lib/python3/dist-packages/pep517/meta.py", line 59, in 
> build_as_zip
>  builder(dest=out_dir)
>File "/usr/lib/python3/dist-packages/pep517/meta.py", line 53, in build
>  env.pip_install(system['requires'])
>File "/usr/lib/python3/dist-packages/pep517/envbuild.py", line 103, in 
> pip_install
>  check_call(
>File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
>  raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['/usr/bin/python3', '-m', 'pip', 
> 'install', '--ignore-installed', '--prefix', 
> '/tmp/pep517-build-env-i1vz1wye', 'setuptools', 'wheel']' returned non-zero 
> exit status 1.
> Files debian/tests/control and debian/tests/control.tmp differ
>
> The generated control file differs from the actual one.
> A sourceful upload of this package is needed.
>
> Differences:
> --- debian/tests/control  2023-01-13 07:05:01.0 +
> +++ debian/tests/control.tmp  2023-01-17 02:06:59.340564039 +
> @@ -7,7 +7,7 @@
>   #   $ mv debian/tests/control.tmp debian/tests/control
>   
>   Tests: pytest-with-recommends
> -Depends: python3-all, diffoscope, black, python3-pytest, python3-h5py, file, 
> linux-image-amd64 [amd64] | linux-image-generic [amd64], abootimg, acl, 
> apksigcopier, apksigner, apktool [!ppc64el !s390x], binutils-multiarch, 
> bzip2, caca-utils, colord, coreboot-utils, db-util, default-jdk-headless | 
> default-jdk | java-sdk, device-tree-compiler, docx2txt, e2fsprogs, enjarify, 
> ffmpeg, fontforge-extras, fonttools, fp-utils [!ppc64el !s390x], genisoimage, 
> gettext, ghc, ghostscript, giflib-tools, gnumeric, gnupg, gnupg-utils, 
> hdf5-tools, html2text, imagemagick, jsbeautifier, libarchive-tools, 
> libxmlb-dev, llvm, lz4 | liblz4-tool, lzip, mono-utils, ocaml-nox, odt2txt, 
> oggvideotools [!s390x], openssh-client, openssl, pgpdump, poppler-utils, 
> procyon-decompiler, python3-pdfminer, r-base-core, rpm2cpio, sng, sqlite3, 
> squashfs-tools, tcpdump, u-boot-tools, unzip, wabt, xmlbeans, xxd, xz-utils, 
> zip, zstd, androguard, python3-argcomplete, python3-binwalk, 
> python3-defusedxml, python3-distro, python3-guestfs, python3-jsondiff, 
> python3-progressbar, python3-pypdf, python3-debian, python3-pyxattr, 
> python3-rpm, python3-tlsh
> +Depends: python3-all, diffoscope, black, python3-pytest, python3-h5py, file, 
> linux-image-amd64 [amd64] | linux-image-generic [amd64], abootimg, acl, 
> apksigcopier, apksigner, apktool [!ppc64el !s390x], binutils-multiarch, 
> bzip2, caca-utils, colord, coreboot-utils, db-util, default-jdk-headless | 
> default-jdk | java-sdk, device-tree-compiler, docx2txt, e2fsprogs, enjarify, 
> ffmpeg, fontforge-extras, fonttools, fp-utils [!ppc64el !s390x], genisoimage, 
> gettext, ghc, ghostscript, giflib-tools, gnumeric, gnupg, gnupg-utils, 
> hdf5-tools, html2text, imagemagick, jsbeautifier, libarchive-tools, 
> libxmlb-dev, llvm, lz4 | liblz4-tool, lzip, mono-utils, ocaml-nox, odt2txt, 
> oggvideotools [!s390x], openssh-client, openssl, pgpdump, poppler-utils, 
> procyon-decompiler, python3-pdfminer, r-base-core, rpm2cpio, sng, sqlite3, 
> squashfs-tools, tcpdump, u-boot-tools, unzip, wabt, xmlbeans, xxd, xz-utils, 
> zip, zstd,

Confirmed that it also affects the version in bookworm:

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope.html

And according to test history, may go back to much earlier versions
(222+)... although there were some other possible FTBFS issues that may
have affected older versions, and I don't immediately see a way to look
at the logs from older versions.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1029116: hw-detect: check-missing-firmware fails will attempting to reload kernel module on MT7922 WiFi card

2023-01-17 Thread Stuart Hayhurst

Source: hw-detect
Version: 1.152
Severity: important
X-Debbugs-Cc: stuart.a.hayhu...@gmail.com

Running "Detect network interfaces" hangs the installer, and with a bit of 
troubleshooting, it's caused when check-missing-firmware removes and loads the 
kernel module for my WiFi chip (mt7921e driver)

check-missing-firmware: removing and loading kernel module mt7921e
Jan 17 21:16:49 check-missing-firmware: installing firmware package 
/media/firmware/firmware-misc-nonfree_20221214-3_all.deb
Jan 17 21:16:53 check-missing-firmware: removing and loading kernel module 
mt7921e
Jan 17 21:16:53 kernel: [ 1290.681036] [ cut here ]
Jan 17 21:16:53 kernel: [ 1290.681044] WARNING: CPU: 0 PID: 6956 at 
kernel/workqueue.c:3066 __flush_work.isra.0+0x270/0x280
Jan 17 21:16:53 kernel: [ 1290.681066] Modules linked in: nls_ascii nls_cp437 
vfat fat mt7921e(-) mt7921_common mt76_connac_lib mt76 mac80211 libarc4 
cfg80211 rfkill isofs cdrom dm_mod sd_mod uas usb_storage scsi_mod scsi_common 
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi 
snd_hda_intel snd_intel_dspcfg snd_acp6x_pdm_dma snd_soc_acp6x_mach 
snd_intel_sdw_acpi snd_soc_dmic snd_hda_codec snd_soc_core nvme snd_hda_core 
snd_compress snd_pci_acp6x snd_hwdep nvme_core snd_pcm xhci_pci sdhci_pci 
snd_timer t10_pi snd_pci_acp5x cqhci xhci_hcd hid_sensor_custom 
snd_rn_pci_acp3x crc64_rocksoft snd crc64 snd_acp_config sdhci hid_multitouch 
video snd_soc_acpi crc_t10dif hid_sensor_hub hid_generic usbcore mmc_core 
crc32_pclmul evdev i2c_hid_acpi snd_pci_acp3x usb_common soundcore i2c_hid 
crct10dif_common battery wmi hid
Jan 17 21:16:53 kernel: [ 1290.681174] CPU: 0 PID: 6956 Comm: modprobe Tainted: 
GE  6.1.0-1-amd64 #1  Debian 6.1.4-1
Jan 17 21:16:53 kernel: [ 1290.681180] Hardware name: LENOVO 82QF/LNVNB161216, 
BIOS K5CN35WW 09/23/2022
Jan 17 21:16:53 kernel: [ 1290.681183] RIP: 0010:__flush_work.isra.0+0x270/0x280
Jan 17 21:16:53 kernel: [ 1290.681191] Code: 8b 04 25 c0 fb 01 00 48 89 44 24 
40 48 8b 73 30 8b 4b 28 e9 e3 fe ff ff 40 30 f6 4c 8b 3e e9 21 fe ff ff 0f 0b 
e9 3a ff ff ff <0f> 0b e9 33 ff ff ff e8 b4 40 95 00 0f 1f 40 00 0f 1f 44 00 00 
55
Jan 17 21:16:53 kernel: [ 1290.681195] RSP: 0018:aab880e8fc20 EFLAGS: 
00010246
Jan 17 21:16:53 kernel: [ 1290.681199] RAX:  RBX: 
9a00d4257bd8 RCX: 
Jan 17 21:16:53 kernel: [ 1290.681202] RDX: 0001 RSI: 
 RDI: aab880e8fc68
Jan 17 21:16:53 kernel: [ 1290.681204] RBP: 9a00d4257bd8 R08: 
 R09: 
Jan 17 21:16:53 kernel: [ 1290.681206] R10:  R11: 
0001 R12: 
Jan 17 21:16:53 kernel: [ 1290.681207] R13: aab880e8fc20 R14: 
0001 R15: c082c108
Jan 17 21:16:53 kernel: [ 1290.681210] FS:  7fd893d77740() 
GS:9a03afc0() knlGS:
Jan 17 21:16:53 kernel: [ 1290.681213] CS:  0010 DS:  ES:  CR0: 
80050033
Jan 17 21:16:53 kernel: [ 1290.681215] CR2: 7fd893e569f0 CR3: 
00010171 CR4: 00750ef0
Jan 17 21:16:53 kernel: [ 1290.681218] PKRU: 5554
Jan 17 21:16:53 kernel: [ 1290.681220] Call Trace:
Jan 17 21:16:53 kernel: [ 1290.681224]  
Jan 17 21:16:53 kernel: [ 1290.681233]  __cancel_work_timer+0xff/0x190
Jan 17 21:16:53 kernel: [ 1290.681242]  rfkill_unregister+0x3c/0xe0 [rfkill]
Jan 17 21:16:53 kernel: [ 1290.681256]  wiphy_unregister+0x66/0x3b0 [cfg80211]
Jan 17 21:16:53 kernel: [ 1290.681315]  ? _raw_spin_lock_irqsave+0x23/0x50
Jan 17 21:16:53 kernel: [ 1290.681323]  ? _raw_spin_unlock_irqrestore+0x23/0x40
Jan 17 21:16:53 kernel: [ 1290.681327]  ? skb_dequeue+0x6e/0x80
Jan 17 21:16:53 kernel: [ 1290.681334]  ieee80211_unregister_hw+0xd4/0x100 
[mac80211]
Jan 17 21:16:53 kernel: [ 1290.681391]  mt7921_pci_remove+0x44/0x110 [mt7921e]
Jan 17 21:16:53 kernel: [ 1290.681401]  pci_device_remove+0x36/0xa0
Jan 17 21:16:53 kernel: [ 1290.681409]  
device_release_driver_internal+0x1b2/0x230
Jan 17 21:16:53 kernel: [ 1290.681417]  driver_detach+0x44/0x90
Jan 17 21:16:53 kernel: [ 1290.681420]  bus_remove_driver+0x55/0xe0
Jan 17 21:16:53 kernel: [ 1290.681428]  pci_unregister_driver+0x2a/0xb0
Jan 17 21:16:53 kernel: [ 1290.681434]  __do_sys_delete_module+0x1d5/0x320
Jan 17 21:16:53 kernel: [ 1290.681442]  do_syscall_64+0x5b/0xc0
Jan 17 21:16:53 kernel: [ 1290.681449]  ? do_syscall_64+0x67/0xc0
Jan 17 21:16:53 kernel: [ 1290.681453]  ? syscall_exit_to_user_mode+0x17/0x40
Jan 17 21:16:53 kernel: [ 1290.681457]  ? do_syscall_64+0x67/0xc0
Jan 17 21:16:53 kernel: [ 1290.681460]  ? do_syscall_64+0x67/0xc0
Jan 17 21:16:53 kernel: [ 1290.681464]  ? 
fpregs_assert_state_consistent+0x22/0x50
Jan 17 21:16:53 kernel: [ 1290.681471]  ? exit_to_user_mode_prepare+0x3c/0x1c0
Jan 17 21:16:53 kernel: [ 1290.681474]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
Jan 17 21:16:53 kernel: [ 1290.681479] RIP: 0033:0x7fd893e838f7
Jan 17 21:16:53 kernel: [

Bug#1029103: coreutils: csplit: -z misdocumented

2023-01-17 Thread Pádraig Brady


Fair point.
I'll clarify like:

commit 70dc90c579adc972644c9047543ff1dc611b89cc (HEAD -> master)
Author: Pádraig Brady 
Date:   Tue Jan 17 21:31:31 2023 +

doc: csplit: more accurate --elide-empty-files help

* src/csplit.c (usage): Use "suppress" rather than "remove"
when describing -z so it's more apparent that the effect
is a particular numbered file is not created, rather than
being removed later.  I.e., don't suggest -z may induce
gaps in file numbering.

diff --git a/src/csplit.c b/src/csplit.c
index da4b36a7c..9a31697b6 100644
--- a/src/csplit.c
+++ b/src/csplit.c
@@ -1471,7 +1471,7 @@ Read standard input if FILE is -\n\
   fputs (_("\
   -n, --digits=DIGITSuse specified number of digits instead of 2\n\
   -s, --quiet, --silent  do not print counts of output file sizes\n\
-  -z, --elide-empty-filesremove empty output files\n\
+  -z, --elide-empty-filessuppress empty output files\n\
 "), stdout);
   fputs (HELP_OPTION_DESCRIPTION, stdout);
   fputs (VERSION_OPTION_DESCRIPTION, stdout);

Bug#1029115: linux-apfs-rw: autopkgtest failure on armel, armhf and i386

2023-01-17 Thread Salvatore Bonaccorso

Hi,

On Tue, Jan 17, 2023 at 10:22:41PM +0100, Paul Gevers wrote:
> Source: linux-apfs-rw
> Version: 0+git20221028+ds-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fails-always
> 
> Dear maintainer(s),
> 
> You recently added an autopkgtest to your package linux-apfs-rw, great.
> However, it fails on armel, armhf and i386. Currently this failure is
> blocking the migration to testing [1]. Can you please investigate the
> situation and fix it?
> 
> I copied some of the output at the bottom of this report.
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [1] https://qa.debian.org/excuses.php?package=linux-apfs-rw
> 
> https://ci.debian.net/data/autopkgtest/testing/armel/l/linux-apfs-rw/30094133/log.gz
> 
> I: Removing binary package apfs-dkms, to get clean state.
> I: Installing binary package apfs-dkms
> Reading package lists...
> Building dependency tree...
> Reading state information...
> The following NEW packages will be installed:
>   apfs-dkms
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 96.0 kB of archives.
> After this operation, 605 kB of additional disk space will be used.
> Get:1 http://deb.debian.org/debian unstable/main armel apfs-dkms all
> 0+git20221028+ds-2 [96.0 kB]
> debconf: delaying package configuration, since apt-utils is not installed
> Fetched 96.0 kB in 0s (1502 kB/s)
> Selecting previously unselected package apfs-dkms.
> (Reading database ... (Reading database ... 5%
> (Reading database ... 10%
> (Reading database ... 15%
> (Reading database ... 20%
> (Reading database ... 25%
> (Reading database ... 30%
> (Reading database ... 35%
> (Reading database ... 40%
> (Reading database ... 45%
> (Reading database ... 50%
> (Reading database ... 55%
> (Reading database ... 60%
> (Reading database ... 65%
> (Reading database ... 70%
> (Reading database ... 75%
> (Reading database ... 80%
> (Reading database ... 85%
> (Reading database ... 90%
> (Reading database ... 95%
> (Reading database ... 100%
> (Reading database ... 29846 files and directories currently installed.)
> Preparing to unpack .../apfs-dkms_0+git20221028+ds-2_all.deb ...
> Unpacking apfs-dkms (0+git20221028+ds-2) ...
> Setting up apfs-dkms (0+git20221028+ds-2) ...
> autoinstall for dkms modules has been disabled.
> I: Checking for missing dkms dependency by trying to deinstall dkms
> dpkg: dependency problems prevent removal of dkms:
>  apfs-dkms depends on dkms (>= 2.1.0.0).
> 
> dpkg: error processing package dkms (--remove):
>  dependency problems - not removing
> Errors were encountered while processing:
>  dkms
> I: No Linux header packages are installed.
> I: Installing all available ones from src:linux 6.0.12-1:
> I:   install linux-headers-6.0.0-6-marvell
> I:   install linux-headers-6.0.0-6-rpi
> I:   install linux-headers-marvell
> I:   install linux-headers-rpi
> Reading package lists...
> Building dependency tree...
> Reading state information...
> The following additional packages will be installed:
>   linux-compiler-gcc-12-arm linux-headers-6.0.0-6-common linux-kbuild-6.0
> The following NEW packages will be installed:
>   linux-compiler-gcc-12-arm linux-headers-6.0.0-6-common
>   linux-headers-6.0.0-6-marvell linux-headers-6.0.0-6-rpi
>   linux-headers-marvell linux-headers-rpi linux-kbuild-6.0
> 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
> Need to get 12.8 MB of archives.
> After this operation, 64.8 MB of additional disk space will be used.
> Get:1 http://deb.debian.org/debian testing/main armel
> linux-compiler-gcc-12-arm armel 6.0.12-1 [556 kB]
> Get:2 http://deb.debian.org/debian testing/main armel
> linux-headers-6.0.0-6-common all 6.0.12-1 [9655 kB]
> Get:3 http://deb.debian.org/debian testing/main armel linux-kbuild-6.0 armel
> 6.0.12-1 [789 kB]
> Get:4 http://deb.debian.org/debian testing/main armel
> linux-headers-6.0.0-6-marvell armel 6.0.12-1 [881 kB]
> Get:5 http://deb.debian.org/debian testing/main armel
> linux-headers-6.0.0-6-rpi armel 6.0.12-1 [867 kB]
> Get:6 http://deb.debian.org/debian testing/main armel linux-headers-marvell
> armel 6.0.12-1 [1144 B]
> Get:7 http://deb.debian.org/debian testing/main armel linux-headers-rpi
> armel 6.0.12-1 [1140 B]
> debconf: delaying package configuration, since apt-utils is not installed
> Fetched 12.8 MB in 0s (31.3 MB/s)
> Selecting previously unselected package linux-compiler-gcc-12-arm.
> (Reading database ... (Reading database ... 5%
> (Reading database ... 10%
> (Reading database ... 15%
> (Reading database ... 20%
> (Reading database ... 25%
> (Reading database ... 30%
> (Reading database ... 35%
> (Reading database ... 40%
> (Reading database ... 45%
> (Reading database ... 50%
> (Reading database ... 55%
> (Reading database ... 60%
> (Reading database ... 65%
> (Reading database ... 70%
> (Reading database ... 75%
> (Reading database ... 80%
>

Bug#1028528: transition: libcotp

2023-01-17 Thread Sebastian Ramacher

Control: tags -1 moreinfo

On 2023-01-12 11:45:45 +, Francisco Vilmar Cardoso Ruviaro wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> I would like to update libcotp in unstable to the 2.0.0-1.
> 
> I would like to request a transition slot for libcotp, changing the
> library name from libcotp12 to libcotp2. The version 2.0.0

Why is the SONAME going backwards?

Cheers

> introducing the ABI change has been in experimental since 2023-01-10.
> 
> I have successfully rebuilt the reversed dependencies on amd64.
> 
> $ reverse-depends -b src:libcotp
> Reverse-Build-Depends
> * otpclient (for libcotp-dev)
> 
> There is already a tracker available here:
> 
> https://release.debian.org/transitions/html/auto-libcotp.html
> 
> Thanks!
> -- 
> Francisco Vilmar Cardoso Ruviaro 
> 4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00




-- 
Sebastian Ramacher

Bug#1018775: fix is in 1.13.0


Control: fixed -1 1.13.0-1

The upstream version that claims to fix this is already in Debian.

Bug#1029107: vfu: problem with long cyrillic file names

2023-01-17 Thread Anonymous 648

Package: vfu
Version: 4.21-1
Severity: normal
X-Debbugs-Cc: gmtmpa...@gmail.com

Dear Maintainer,

1) Create file with long latin name
touch 
lng_name.ext

2) Create file with long cyrillic(non latin) name
touch 
жж.ext
 

3) Run vfu 

Cyrillic name gets cut off. Please check screenshot attached.


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

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

Versions of packages vfu depends on:
ii  bzip2 1.0.8-4
ii  libc6 2.31-13+deb11u5
ii  libgcc-s1 10.2.1-6
ii  libncursesw6  6.2+20201114-2
ii  libpcre3  2:8.39-13
ii  libstdc++610.2.1-6
ii  libtinfo6 6.2+20201114-2
ii  unzip 6.0-26+deb11u1

vfu recommends no packages.

vfu suggests no packages.

-- no debconf information

Bug#1029109: cimg: build dependency gone after tiff transition

2023-01-17 Thread Paul Gevers


Source: cimg
Version: 3.1.6+dfsg-6
Severity: serious
User: debian...@lists.debian.org
Usertag: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting issues with your packages. Normally your build 
dependencies shouldn't be removed from testing without removal all 
reverse build dependencies too, nor should a package be allowed to 
migrate unless all build dependencies are candidate for migration too. 
However, somehow we ended up in the current state and your source 
package is missing some Build-Depends for some while now. Not being able 
to build from source in a suite is an RC bug in that suite.


Your package Build-Depends on a particular SONAME of the tiff library, 
but that was dropped in the last tiff transition. Are you sure you need 
to Build-Depends on the library, it's already pulled in via the tiff 
header package.


Can you please solve the situation by either helping the maintainer of 
your Build-Depends to enable migration to testing, or by working around 
the lack of this build dependency?


Paul

[1] https://qa.debian.org/dose/debcheck/src_testing_main/index.html


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1029110: firmware-ast: Please move to non-free-firmware/kernel section

2023-01-17 Thread Cyril Brulebois

Package: firmware-ast
Severity: important
Tags: patch

Hi,

The installer team is currently implementing a plan to make firmware
packages installed from non-free-firmware, which would mean no longer
having to enable non-free just to install firmware packages (and keep
them up-to-date).

The attached patch prepares firmware-ast for this plan.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
>From 701bd7112cfb508804e164c79405af687b2c8f1d Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Mon, 16 Jan 2023 23:53:51 +
Subject: [PATCH] Move to non-free-firmware/kernel section.

Move source and binary from non-free/kernel to non-free-firmware/kernel
following the 2022 General Resolution about non-free firmware.
---
 debian/changelog | 7 +++
 debian/control   | 4 ++--
 2 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index f04d8f8..8049ebe 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+firmware-ast (20140808-7) UNRELEASED; urgency=medium
+
+  * Move source and binary from non-free/kernel to non-free-firmware/kernel
+following the 2022 General Resolution about non-free firmware.
+
+ -- Cyril Brulebois   Mon, 16 Jan 2023 23:52:40 +
+
 firmware-ast (20140808-6) sid; urgency=medium
 
   * Uploading to sid.
diff --git a/debian/control b/debian/control
index 8508697..0342243 100644
--- a/debian/control
+++ b/debian/control
@@ -1,5 +1,5 @@
 Source: firmware-ast
-Section: non-free/kernel
+Section: non-free-firmware/kernel
 Priority: optional
 Maintainer: Daniel Baumann 
 Build-Depends:
@@ -13,7 +13,7 @@ Vcs-Git: 
https://git.progress-linux.org/users/daniel.baumann/debian/packages/fir
 XS-Autobuild: yes
 
 Package: firmware-ast
-Section: non-free/kernel
+Section: non-free-firmware/kernel
 Architecture: all
 Multi-Arch: foreign
 Depends:
-- 
2.30.2

Bug#1029115: linux-apfs-rw: autopkgtest failure on armel, armhf and i386

2023-01-17 Thread Paul Gevers


Source: linux-apfs-rw
Version: 0+git20221028+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package linux-apfs-rw, great. 
However, it fails on armel, armhf and i386. Currently this failure is 
blocking the migration to testing [1]. Can you please investigate the 
situation and fix it?


I copied some of the output at the bottom of this report.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=linux-apfs-rw

https://ci.debian.net/data/autopkgtest/testing/armel/l/linux-apfs-rw/30094133/log.gz

I: Removing binary package apfs-dkms, to get clean state.
I: Installing binary package apfs-dkms
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  apfs-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 96.0 kB of archives.
After this operation, 605 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main armel apfs-dkms all 
0+git20221028+ds-2 [96.0 kB]

debconf: delaying package configuration, since apt-utils is not installed
Fetched 96.0 kB in 0s (1502 kB/s)
Selecting previously unselected package apfs-dkms.
(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 29846 files and directories currently installed.)
Preparing to unpack .../apfs-dkms_0+git20221028+ds-2_all.deb ...
Unpacking apfs-dkms (0+git20221028+ds-2) ...
Setting up apfs-dkms (0+git20221028+ds-2) ...
autoinstall for dkms modules has been disabled.
I: Checking for missing dkms dependency by trying to deinstall dkms
dpkg: dependency problems prevent removal of dkms:
 apfs-dkms depends on dkms (>= 2.1.0.0).

dpkg: error processing package dkms (--remove):
 dependency problems - not removing
Errors were encountered while processing:
 dkms
I: No Linux header packages are installed.
I: Installing all available ones from src:linux 6.0.12-1:
I:   install linux-headers-6.0.0-6-marvell
I:   install linux-headers-6.0.0-6-rpi
I:   install linux-headers-marvell
I:   install linux-headers-rpi
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  linux-compiler-gcc-12-arm linux-headers-6.0.0-6-common linux-kbuild-6.0
The following NEW packages will be installed:
  linux-compiler-gcc-12-arm linux-headers-6.0.0-6-common
  linux-headers-6.0.0-6-marvell linux-headers-6.0.0-6-rpi
  linux-headers-marvell linux-headers-rpi linux-kbuild-6.0
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 12.8 MB of archives.
After this operation, 64.8 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian testing/main armel 
linux-compiler-gcc-12-arm armel 6.0.12-1 [556 kB]
Get:2 http://deb.debian.org/debian testing/main armel 
linux-headers-6.0.0-6-common all 6.0.12-1 [9655 kB]
Get:3 http://deb.debian.org/debian testing/main armel linux-kbuild-6.0 
armel 6.0.12-1 [789 kB]
Get:4 http://deb.debian.org/debian testing/main armel 
linux-headers-6.0.0-6-marvell armel 6.0.12-1 [881 kB]
Get:5 http://deb.debian.org/debian testing/main armel 
linux-headers-6.0.0-6-rpi armel 6.0.12-1 [867 kB]
Get:6 http://deb.debian.org/debian testing/main armel 
linux-headers-marvell armel 6.0.12-1 [1144 B]
Get:7 http://deb.debian.org/debian testing/main armel linux-headers-rpi 
armel 6.0.12-1 [1140 B]

debconf: delaying package configuration, since apt-utils is not installed
Fetched 12.8 MB in 0s (31.3 MB/s)
Selecting previously unselected package linux-compiler-gcc-12-arm.
(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 29875 files and directories currently installed.)
Preparing to unpack .../0-linux-compiler-gcc-12-arm_6.0.12-1_armel.deb ...
Unpacking linux-compiler-gcc-12-arm (6.0.12-1) ...

Bug#1014125: libheif: CVE-2020-23109


Control: fixed -1 1.8.0-1

This is claimed to be fixed with 
https://github.com/strukturag/libheif/commit/bca0162018df9a32d21c05aad1fa203881fa7813
which was included in v1.7.0

Bug#924862: Enable shaderc support in mpv

2023-01-17 Thread Shmerl

Now that shaderc was added to Debian unstable / testing, can you please
enable building mpv with it?

See: https://tracker.debian.org/pkg/shaderc

Thanks!

Shmerl.

Bug#1027760: gortr appears to be unmaintained

2023-01-17 Thread Marco d'Itri

Control: severity -1 important
Control: affects -1 cfrpki

On Jan 03, Marco d'Itri  wrote:

> gortr has not been updated upstream in over two years and probably most
> users at this point have switched to stayrtr for good.
But cfrpki build-depends on golang-github-cloudflare-gortr-dev, so let's 
ignore this for the time being.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1029117: libtasn1-6: Convert d/copyright to machine-readable format

Source: libtasn1-6
Version: 4.19.0-2
Tags: patch

Please consider converting the debian/copyright file to the machine-readable
format.
I have attached a converted file that also adds the missing X11 and FSFAP
license and some copyright lines.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment:
This package was debianized by Ivo Timmermans on
Sat, 15 Jun 2002 23:37:29 +0200 by Matthias Urlichs .
.
It is now maintained by Andreas Metzler , Eric Dorland
and James Westby
.
The library itself is licensed as LGPL-2.1+, the build system,
test-suite, and command-line tools (package libtasn1-bin) are GPL-3+.
Source:
It was downloaded from https://ftp.gnu.org/gnu/libtasn1/
Upstream-Contact:
Fabio Fiorina
Simon Josefsson
Nikos Mavrogiannopoulos

Files: *
Copyright: (C) 2000-2022 Free Software Foundation, Inc.
License: GPL-3+

Files: lib/*
fuzz/corpus2array.c
m4/ax_code_coverage.m4
src/gl/intprops-internal.h
src/gl/getopt_int.h
src/gl/idx.h
src/gl/getopt-ext.h
src/gl/intprops.h
src/gl/getopt.c
src/gl/explicit_bzero.c
src/gl/getopt1.c
src/gl/stdckdint.in.h
src/gl/getopt-core.h
src/gl/filename.h
Copyright: (C) 2000-2022 Free Software Foundation, Inc.
License: LGPL-2.1+
* This file is part of LIBTASN1.
*
* The LIBTASN1 library is free software; you can redistribute it
* and/or modify it under the terms of the GNU Lesser General Public
* License as published by the Free Software Foundation; either
* version 2.1 of the License, or (at your option) any later version.
*
* This library is distributed in the hope that it will be useful, but
* WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
* 02110-1301, USA
Comment:
On Debian GNU/Linux systems, the complete text of the GNU Lesser
General Public License can be found in
`/usr/share/common-licenses/LGPL'; the text of the earliest applying version
of the license (2.1) can be found in `/usr/share/common-licenses/LGPL-2.1'.

Files: doc/gdoc
Copyright:
Copyright (c) 2002-2021 Simon Josefsson
Copyright (c) 2001, 2002 Nikos Mavrogiannopoulos
Copyright (c) 1998 Michael Zucchi
Copyright (c) 2013 Adam Sampson
License: GPL-3+

Files: tests/object-id-encoding.c
Copyright: (C) 2019 Nikos Mavrogiannopoulos
License: GPL-3+

Files: tests/object-id-decoding.c
tests/ocsp-basic-response.c
tests/spc_pe_image_data.c
Copyright: (C) 2016 Red Hat, Inc.
License: GPL-3+

Files: gtk-doc.make
Copyright: (C) 2003 James Henstridge
2004-2007 Damon Chaplin
2007-2017 Stefan Sauer
License: GPL-3+

License: GPL-3+
* This file is part of LIBTASN1.
*
* This program is free software: you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation, either version 3 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program. If not, see .
Comment:
On Debian GNU/Linux systems, the complete text of the GNU General Public
License version 3 can be found in /usr/share/common-licenses/GPL-3.

Files: doc/*.texi
doc/*.1
doc/reference/*
Copyright: (c) 2001-2022 Free Software Foundation, Inc.
License: GFDL-NIV-1.3+
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.3 or any later version published by the Free Software
Foundation; with no Invariant Sections, no Front-Cover Texts, and no
Back-Cover Texts. A copy of the license is included in the section
entitled "GNU Free Documentation License".
Comment:
On Debian systems a copy of the complete text of the GNU FDL 1.3
can be found in /usr/share/common-licenses/GFDL-1.3.

Files: AUTHORS INSTALL NEWS THANKS
doc/TODO doc/man/*
Copyright: Copyright (C) 2002-2022 Free Software Foundation, Inc.
License: FSFAP
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved.

Files: build-aux/install-sh
Copyright: (C) 1994 X Consortium
License: X11
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation

Bug#1013756: (No Subject)

2023-01-17 Thread danielle.davout

Hi, I had the same bug, so I try to follow the instructions given in

https://github.com/alsa-project/alsa-python/commit/a64a6cc703d08db5c223a16bf812a569534ba464

I could "hear" some improvements (some sound), but now I am face to

'''Traceback (most recent call last):
File "/usr/share/solfege/solfege/exercises/idbyname.py", line 296, in 
new_question
self.do_at_question_start_show_play()
File "/usr/share/solfege/solfege/abstract.py", line 1077, in 
do_at_question_start_show_play
self.m_t.m_P.play_question()
File "/usr/share/solfege/solfege/lessonfile.py", line 1413, in play_question
question[varname].play(self, question)
File "/usr/share/solfege/solfege/lessonfile.py", line 573, in play
self.__play(lessonfile_ref, question,
File "/usr/share/solfege/solfege/lessonfile.py", line 601, in __play
soundcard.synth.play_track(t1, t2, t3)
File "/usr/share/solfege/solfege/soundcard/alsa_sequencer.py", line 51, in 
play_track
self.play_midieventstream(MidiEventStream(*tracks))
File "/usr/share/solfege/solfege/soundcard/alsa_sequencer.py", line 94, in 
play_midieventstream
event.time = tTypeError: integer or float expected...
Thanks

Bug#1029113: postfix: updated German po-file

2023-01-17 Thread Markus Hiereth

Package: postfix
Version: 3.7.3-4
Severity: normal

Dear Maintainer,

find the attached german messages for the debconf dialogue. The two 
fuzzy strings were checked and improved. The po-file has been proof-read by the 
German language team.

Best regards
Markus

-- System Information:
Debian Release: 11.5
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 5.10.0-9-686-pae (SMP w/1 CPU thread)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
# Translation of postfix debconf templates to German
# This file is distributed under the same license as the postfix package.
# Copyright (C) Helge Kreutzmann , 2006-2008, 2012, 2014, 
2016.
# Markus Hiereth , 2016, 2018, 2022, 2023
msgid ""
msgstr ""
"Project-Id-Version: postfix 3.7.3-4\n"
"Report-Msgid-Bugs-To: post...@packages.debian.org\n"
"POT-Creation-Date: 2021-12-28 14:12-0500\n"
"PO-Revision-Date: 2023-01-15 22:00+0100\n"
"Last-Translator: Markus Hiereth \n"
"Language-Team: debian-l10n-german \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Virtaal 0.7.1\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Update configuration to avoid compatibility warnings?"
msgstr ""
"Um Warnungen zu Inkompatibiltäten zu vermeiden, die Konfiguration "
"aktualisieren?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"This upgrade of Postfix changes some default values in the configuration. As "
"part of this upgrade, the following will be changed: (1) chrooted components "
"will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set "
"to a fully-qualified domain name if it is not already such. The install will "
"be aborted if you do not allow the change."
msgstr ""
"Diese Aktualisierung von Postfix ändert einige Standardwerte der "
"Konfiguration. Dazu gehört: (1) in master.cf wird bei chrooted-Komponenten "
"der Wert '-' durch 'y' ersetzt. (2) »myhostname« wird, falls die Variable "
"noch nicht die Anforderungen an einen voll-qualifizierten Domainnamen (FQDN) "
"erfüllt, in eine solche überführt. Sollten Sie diese Änderungen nicht "
"zulassen, wird die Installation abgebrochen."

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Update main.cf for daemon_directory change?"
msgstr "main.cf für eine Änderung von »daemon_directory« aktualisieren?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"This upgrade of Postfix changes where daemons are located, and your Postfix "
"configuration explicitly specifies the old location. The install will be "
"aborted if you do not allow the change."
msgstr ""
"Dieses Upgrade von Postfix ändert den Ort von Hintergrundprozessen, Ihre "
"Postfix-Konfiguration spezifiziert allerdings ausdrücklich den alten Ort. "
"Sollten Sie diese Änderungen nicht zulassen, wird die Installation "
"abgebrochen."

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Update dynamicmaps.cf for 3.0?"
msgstr "dynamicmaps.cf für 3.0 aktualisieren?"

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"Postfix version 3.0 changes how dynamic maps are delivered, and your "
"dynamicmaps.cf does not reflect that. Accept this option to convert "
"dynamicmaps.cf to the version required for 3.0."
msgstr ""
"Mit Postfix Version 3.0 ändert sich, wie dynamische Zuordnungen "
"bereitgestellt werden, Ihre dynamicmaps.cf widerspiegelt dies jedoch nicht. "
"Akzeptieren Sie diese Option, um dynamicmaps.cf in die für 3.0 benötigte "
"Version zu konvertieren."

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Ignore incorrect hostname entry?"
msgstr "Fehlerhaften Hostnamen-Eintrag ignorieren?"

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"The string '${enteredstring}' does not follow RFC 1035 and does not appear "
"to be a valid IP address."
msgstr ""
"Die Zeichenkette »${enteredstring}« entspricht nicht RFC 1035 und scheint "
"keine gültige IP-Adresse zu sein."

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"RFC 1035 states that 'each component must start with an alphanum, end with "
"an alphanum and contain only alphanums and hyphens. Components must be "
"separated by full stops.'"
msgstr ""
"RFC 1035 fordert, dass »jede Komponente mit einem alphanumerischen Zeichen "
"beginnen und enden muss und ansonsten auch nur aus alphanumerischen Zeichen "
"und Bindestrichen bestehen darf. Alle Komponenten müssen jeweils durch einen "
"Punkt getrennt werden«."

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Please check and confirm if you want to keep your entry."
msgstr ""
"Bitte kontrollieren und bestätigen Sie, falls Sie Ihren Eintrag beibehalten 
möchten."

#. Type: select
#. Choices
#. Translators beware!

Bug#1029114: git: CVE-2022-23521 CVE-2022-41903

2023-01-17 Thread Salvatore Bonaccorso

Source: git
Version: 1:2.30.2-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:2.39.0-1

Hi,

The following vulnerabilities were published for git.

CVE-2022-23521[0]:
| gitattributes parsing integer overflow

CVE-2022-41903[1]:
| heap overflow in `git archive` and `git log --format`

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-2022-23521
https://www.cve.org/CVERecord?id=CVE-2022-23521
[1] https://security-tracker.debian.org/tracker/CVE-2022-41903
https://www.cve.org/CVERecord?id=CVE-2022-41903

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1029046: Wayland session doesn't get back to life post-suspend

2023-01-17 Thread Didier 'OdyX' Raboud

Control: found -1 6.1.6-1
Control: found -1 6.1.4-1
Control: severity -1 serious

Hello there,

Le mardi, 17 janvier 2023, 15.32:37 h CET Diederik de Haas a écrit :
> On Monday, 16 January 2023 22:33:05 CET Didier 'OdyX' Raboud wrote:
> > This is on 6.1.4-1a~test, patched against the "2nd DisplayPort doesn't
> > light up", so feel free to close the bug; I'll test if I get the same
> > symptoms on an unpatched kernel anyway :-)
> 
> If this issue doesn't occur with the unpatched kernel, that would be VERY
> important extra information!
> https://gitlab.freedesktop.org/drm/amd/-/issues/2171#note_1724186 may be the
> same or similar finding?
> 
> If that issue doesn't occur with the unpatched kernel, could you add your
> finding to that upstream/forwarded issue?

Now that I got my kernel build in place; I can actually confirm that:

On my Thinkpad X13 Gen 2a, without any dongle, hub or docking station (on 
battery), with a KDE Plasma Wayland session:

* 6.0.0-6-amd64 (6.0.12-1)
  suspends and resumes correctly
* 6.1.0-1-amd64 (6.1.4-1, unpatched)
  doesn't finish suspending
* 6.1.0-2-amd64 (6.1.6-1, from the 'sid' branch on salsa, not patched)
  doesn't finish suspending
* 6.1.0-2-amd64 (6.1.6-1, from the 'sid' branch on salsa, patched),
  doesn't finish suspending

All three 6.1 kernels (whether patched or not) don't bring the laptop to the 
suspended state (power led 'breathing', fans off), but it's kept in an "on" 
state (power led on, fans on), from which I found that I *can* wake the laptop 
up by short-pressing the power button; the screens gets back to life and show 
my lockscreen. But from there, I can't move the mouse nor do anything else. 
Alt-SysRq-r + ctrl-alt-f2 give me a tty, but any comeback to tty1 only blank 
(not even a blank screen, just a freeze).

This seems to point to a quite severe regression in amdgpu or other amd-
related code; I can't suspend-and-resume the laptop anymore on any 6.1 kernel, 
on battery, without anything attached to it.

I'll forward the above findings to the bug you pointed to, hoping it could 
help upstream too!

Best,

OdyX

Bug#1028821: pysurfer was still affected by numpy 1.24

2023-01-17 Thread Étienne Mollier

Control: reassign -1 pysurfer 0.11.0-3
Control: retitle -1 pysurfer ftbfs with numpy 1.24
Control: found -1 0.11.0-3
Control: fixed -1 0.11.0-4

Hi,

I'm under the impression I was not well inspired to reassing the
present bug to mayavi2, because pysurfer still used to ftbfs
after the mayavi2 update.  Thankfully this has been fixed by Bas
patch and Nilesh's upload already.

Besides, it seems that I accidentally entangled a migration
between mayavi2 and pysurfer, which is forbidden at this stage
of the release I believe.  If need be, I'll check with the
Release Team.

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#996799: twitterwatch - upload needed

2023-01-17 Thread Emmanuel Arias

Hi,

On Tue, Jan 17, 2023 at 6:16 PM Malik  wrote:

> Hello Emmanuel,
>
> currently upstream-author has no plan to update or release any further
> releases for this project [1]
>
Ok

>
>

> [1] https://gitlab.com/chaica/twitterwatch/-/issues/1
>
> kind regards,
> Malik
>

If you leave the package as is it now, when a new release exists, d/watch
won't note it.
So, I'd change the d/watch to the Gitlab repository. Also Homepage link.

Cheers,
Emmanuel

Bug#1028451: 2nd DisplayPort doesn't get video

2023-01-17 Thread Paul Gevers


Hi,

On 17-01-2023 07:14, Salvatore Bonaccorso wrote:

I will bite the bullet (taking full responsibility for it if
necessary, don't blame the other kernel team members) and ask here now
the release team: Can we let linux 6.1.4-1 despite the RC bug
reported, migrate to testing, so we can move on to 6.1.y?


I have added the hints. linux should migrate in the 22:00 UTC britney run.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1029111: rtl8723bt-firmware: please move to non-free-firmware/kernel section

2023-01-17 Thread Cyril Brulebois

Package: rtl8723bt-firmware
Severity: important
Tags: patch

Hi,

The installer team is currently implementing a plan to make firmware
packages installed from non-free-firmware, which would mean no longer
having to enable non-free just to install firmware packages (and keep
them up-to-date).

The attached patch prepares rtl8723bt-firmware for this plan.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
diff -Nru rtl8723bt-firmware-20181104/debian/changelog 
rtl8723bt-firmware-20181104/debian/changelog
--- rtl8723bt-firmware-20181104/debian/changelog2022-05-26 
09:32:47.0 +0200
+++ rtl8723bt-firmware-20181104/debian/changelog2023-01-17 
21:05:17.0 +0100
@@ -1,3 +1,10 @@
+rtl8723bt-firmware (20181104-2) UNRELEASED; urgency=medium
+
+  * Move source and binary from non-free/kernel to non-free-firmware/kernel
+following the 2022 General Resolution about non-free firmware.
+
+ -- Cyril Brulebois   Tue, 17 Jan 2023 20:05:17 +
+
 rtl8723bt-firmware (20181104-1) unstable; urgency=medium
 
   * Initial release. (Closes: #1011744)
diff -Nru rtl8723bt-firmware-20181104/debian/control 
rtl8723bt-firmware-20181104/debian/control
--- rtl8723bt-firmware-20181104/debian/control  2022-05-26 09:32:47.0 
+0200
+++ rtl8723bt-firmware-20181104/debian/control  2023-01-17 21:05:17.0 
+0100
@@ -1,5 +1,5 @@
 Source: rtl8723bt-firmware
-Section: non-free/kernel
+Section: non-free-firmware/kernel
 Priority: optional
 Maintainer: Bastian Germann 
 Rules-Requires-Root: no

Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

2023-01-17 Thread Sebastian Reichel

Hi,

On Sat, 14 Jan 2023 21:53:59 + Martin  wrote:
> Control: severity -1 normal
> 
> The problem disappeared magically for all users who reported it before.
> I assume, that there is a hidden bug in libproxy, that only appears in
> certain circumstances. Downgrading for now.

I just got the new package through testing and now gajim segfaults
ony my system with stacktrace pointing to libproxy. So this is not
magically solved.

-- Sebastian

signature.asc
Description: PGP signature

Bug#1029093: solaar doesn't enable plugdev when plugdev requested

2023-01-17 Thread Stephen Kitt

Control: forcemerge 1028922 -1
Control: severity 1028922 important

Hi Mason,

On Tue, 17 Jan 2023 11:05:46 -0500, Mason Loring Bliss 
wrote:
> My previous bug, BZ#1028922, was closed inappropriately, given that the
> bug is not fixed in Bookworm, and will impact Bullseye users until Bullseye
> leaves support.

The Debian bug tracker (which isn’t Bugzilla ;-) takes version information
into account; if you look at the diagram on the right-hand side of
https://bugs.debian.org/1028922 you’ll see that the only fixed version is the
version currently in unstable, and that the versions currently in stable
(Bullseye) and testing (Bookworm) are marked as unfixed. Likewise, if you
compare https://bugs.debian.org/solaar;dist=stable and
https://bugs.debian.org/solaar;dist=unstable you’ll see that the former still
lists 1028922 as outstanding, i.e. unresolved.

I’m merging this bug with 1028922 and upgrading the importance of the latter,
so that it can be fixed in an upcoming Bullseye point release (if the stable
release managers approve).

Regards,

Stephen

pgpYWWwnXEZiU.pgp
Description: OpenPGP digital signature

Bug#1026204: tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64

2023-01-17 Thread Helge Deller


On Sat, 14 Jan 2023 20:38:38 +0100 Andreas Henriksson  wrote:

Here's a slightly different patch to implement basically the same thing


Yes, I like this patch better too.

Helge

Bug#207095: so hard to get dates

2023-01-17 Thread Dan Jacobson

On https://github.com/GPSBabel/gpsbabel/issues/981#issuecomment-1385579428
I was racking my brains again to show them the dates.

Bug#854209: Update Description

Once this bug has been fixed, it would probably make sense to update the 
Lintian description to indicate that the problematic file can be appropriately 
relicensed to a DFSG compatible license, with a link to this bug report for 
information about the details.

-- 
Soren Stoutner
so...@stoutner.com

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

Bug#1029108: tuxguitar: limit build architectures

2023-01-17 Thread tony mancill

Package: tuxguitar
Version: 1.5.6+dfsg1-1
Severity: important

tuxguitar is FTBFS on multiple architectures:

https://buildd.debian.org/status/logs.php?pkg=tuxguitar=1.5.6%2Bdfsg1-1

We should either address the FTBFS or limit the build architectures in
the next upload.

Bug#1029106: make: new upstream release (4.4)

2023-01-17 Thread Jakub Wilk


Source: make-dfsg
Severity: wishlist

--
Jakub Wilk

Bug#928912: README.Debian updated in 5.1.8.1-1

2023-01-17 Thread Jeremy Sowden

Control: fixed -1 shorewall/5.1.8.1-1

The explanation in README.Debian of how to enable shorewall on boot was
updated to include systemd in 5.1.8.1-1.

J.


signature.asc
Description: PGP signature

Bug#1029118: Possible typo in "#if !(defined(yylex) ..."

2023-01-17 Thread Bjarni Ingi Gislason

Package: byacc
Version: byacc - 2.0 20221229
Severity: normal

Dear Maintainer,

   * What led up to the situation?

  Compiling groff



output.c:   putl_code(fp, "#if !(defined(yylex) || defined(YYSTATE))\n");

  "yylex" is a name of a function but "#... defined(...)" applies to
macros not functions(?).



  When compiling, a warning is issued:

  CXX  src/preproc/eqn/eqn-eqn.o
src/preproc/eqn/eqn.cpp:73:23: warning: redundant redeclaration of 'int
yylex()' in same scope [-Wredundant-decls]
   73 | # define YYLEX_DECL() yylex(void)
  |   ^
src/preproc/eqn/eqn.cpp:78:5: note: in expansion of macro 'YYLEX_DECL'
   78 | int YYLEX_DECL();
  | ^~
../src/preproc/eqn/eqn.ypp:31:5: note: previous declaration of 'int
yylex()'
   31 | int yylex(void);
  | ^
  CXXLDeqn



  When I change "yylex" to "YYLEX" in the "putl_code(...)" line there
is no warning.

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

Kernel: Linux 6.0.12-1 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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 byacc depends on:
ii  libc6  2.36-8

byacc recommends no packages.

byacc suggests no packages.

Bug#1029101: Acknowledgement (fontconfig-config: 2.14.1 upload breaks testSimpleText of libreoffice)

2023-01-17 Thread Rene Engelhard


severity 1029101 important
retitle 1029101 please Enable RGB stripes layout for sub-pixel rendering 
on KDE only

thanks

[ sorry for "spamming" ]

Hi,

Am 17.01.23 um 19:04 schrieb Rene Engelhard:
it still fails. Probably it ignores it since it's already set in /etc 
and that already matches?


OK, got it. I need to "delete" it.

  

mode="delete">rgb

  


Then it passes and it shouldn't  break with 2.13 either since deleting 
somethng non-existing works ;-)


Will reassign a clone to libreoffice to fix that test failure.

Regards,


Rene

Bug#1027613: update

2023-01-17 Thread M. Zhou

Control: severity -1 important

I think this FTBFS mostly stems from the toolchain.

1. before the bug is filed, it builds successfully on amd64
2. On the day I recieved this bug report, I reproduced it
3. after some toolchain updates, I cannot reproduce it anymore

Bug#1028957: librocrand-dev: rocrand_INCLUDE_DIR does not exist

2023-01-17 Thread Cordell Bloor


Thanks for taking a look at this, Étienne.

On 1/15/23 11:16, Étienne Mollier wrote:

Not sure it will help, but I suppose I could first bump the
rocrand package up to 5.2.3 to be consistent with the build
chain.  It should still be easy to do while we're not in the
next stage of the freeze on February 12th.


I would not worry too much about exactly matching the HIP version, 
though. While rocrand 5.3 was in development, the hip 5.3 library didn't 
exist. The upstream developers would have been building and testing on 
hip 5.2 (or earlier) during most of the development cycle.


IMO, it's perfectly fine to update to any version of rocrand that passes 
its test suite. My suggestion is 5.3.3, since it matches the other 
mathlibs in Debian, but 5.4.2 would also be fine and 5.2.3 could 
probably be made to work with minor patches.



The upstream hipRAND repo does't have any tags (and therefore getting tarballs
with uscan might be tricky?). If tags would help, I can work with upstream to
get them added retroactively for rocm-5.1.0 and later. Just let me know.

For a regular package it would be possible to use git commit IDs
instead, but that leads to hard to read version numbers.  In the
case of MUT, strolling through the example from rocm-hipamd, I
see it may be necessary to restrict the version number of the
side tarball to be the same as the main source package.  So...
yes please?  :)

The tags have now been added to hipRAND. 
https://github.com/ROCmSoftwarePlatform/hipRAND/tags


Sincerely,
Cory Bloor

Bug#1029112: Surprise build issue with ibus-libzhuyin

2023-01-17 Thread Gunnar Hjalmarsson


Package: src:ibus-libzhuyin
Version: 1.10.2-1
Severity: serious
Tags: ftbfs

Hello!

ibus-libzhuyin 1.10.2-1 failed to build. This is the relevant part of 
the buildlog:


Making all in model
make[4]: Entering directory '/<>/data/model'
wget http://downloads.sourceforge.net/libzhuyin/models/model13.text.tar.gz
/bin/bash: line 1: wget: command not found

And yes, it's true that wget is not included in Build-Depends. But 
previously that has not been needed. This is from the buildlog for the 
latest successful build:


Making all in model
make[4]: Entering directory '/<>/data/model'
rm -f phrase_index.bin pinyin_index.bin addon_phrase_index.bin 
addon_pinyin_index.bin bigram.db tsi.bin

gen_binary_files --table-dir ../../data/model
import_interpolation --table-dir ../../data/model < 
../../data/model/interpolation2.text

gen_unigram --table-dir ../../data/model

or just:

Making check in model
make[3]: Entering directory '/<>/data/model'
make[3]: Nothing to be done for 'check'.

I have not found any code changes which would explain the new behavior. 
And when trying (in an Ubuntu PPA) to add wget to Build-Depends, it 
failed to resolve the download URL. (It builds fine on my harddisk, though.)


I figured out that this patch would help it build successfully:

--- a/data/Makefile.am
+++ b/data/Makefile.am
@@ -27,7 +27,6 @@

  SUBDIRS = \
  icons \
-model \
  $(NULL)

  appdatadir = @datadir@/appdata

But since I don't know how that would affect the functionality of the 
package, I have left it in its failed state for now.


In other words: I need help to solve this.

--
Rgds,
Gunnar

Bug#1029112: Surprise build issue with ibus-libzhuyin

2023-01-17 Thread Osamu Aoki

Hi,

Debian official packages are required to build without downloading external
files during their build.  (Builddd is in isolated network environment only with
access to the Debian package repository.


> Tags: ftbfs

So if it requires wget file access, it is ftbfs.  Don't make build script to do
this.   ... (continue to the bottom).

> Making all in model
> make[4]: Entering directory '/<>/data/model'
> wget http://downloads.sourceforge.net/libzhuyin/models/model13.text.tar.gz
> /bin/bash: line 1: wget: command not found
> 
> And yes, it's true that wget is not included in Build-Depends. But 
> previously that has not been needed. This is from the buildlog for the 
> latest successful build:
> 
> Making all in model
> make[4]: Entering directory '/<>/data/model'
> rm -f phrase_index.bin pinyin_index.bin addon_phrase_index.bin 
> addon_pinyin_index.bin bigram.db tsi.bin
> gen_binary_files --table-dir ../../data/model
> import_interpolation --table-dir ../../data/model < 
> ../../data/model/interpolation2.text
> gen_unigram --table-dir ../../data/model
> 
> or just:
> 
> Making check in model
> make[3]: Entering directory '/<>/data/model'
> make[3]: Nothing to be done for 'check'.
> 
> I have not found any code changes which would explain the new behavior. 
> And when trying (in an Ubuntu PPA) to add wget to Build-Depends, it 
> failed to resolve the download URL. (It builds fine on my harddisk, though.)
> 
> I figured out that this patch would help it build successfully:
> 
> --- a/data/Makefile.am
> +++ b/data/Makefile.am
> @@ -27,7 +27,6 @@
> 
>    SUBDIRS = \
>    icons \
> -    model \
>    $(NULL)
> 
>    appdatadir = @datadir@/appdata
> 
> But since I don't know how that would affect the functionality of the 
> package, I have left it in its failed state for now.
> 
> In other words: I need help to solve this.


If I were you, I will build package "without this mod in an environment with
wget included as Build-dep" and "with this mod only without wget in chroot". 
Then I will check resulting binary packages.

If these generated packages contain different model data, then you need to
modify code to use pre-existing data and download such model data in advance to
be included in debian/ directory.  Of course, you need to check license terms of
such model data and document it.

If these contain same model data, your proposed fix should be OK.

Regards,

Osamu

Bug#1029119: coreutils: csplit: makes an empty file when an expression goes backwards, must error per POSIX

2023-01-17 Thread наб

Package: coreutils
Version: 9.1-1
Severity: normal

Dear Maintainer,

Quoth Issue 7 (and Issue 8 Draft 2.1), XCU, csplit, OPERANDS:
  An error shall be reported if an operand does not reference
  a line between the current position and the end of the file.

Why, then:
-- >8 --
$ seq 999 | csplit - /10/ /^0$/
18
csplit: ‘/^0$/’: match not found
3870
-- >8 --
but
-- >8 --
$ seq 999 | csplit - /10/ 2
18
0
3870
-- >8 --
?

Cf. NetBSD, which gets both right:
-- >8 --
$ seq 999 | csplit - /10/ /^0/
18
csplit: ^0: no match
$ seq 999 | csplit - /10/ 2
18
csplit: 2: can't go backwards
-- >8 --

Best,
наб

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-2
ii  libattr1 1:2.5.1-3
ii  libc62.36-7
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b4

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1029105: /usr/bin/getmails: 32: Bad substitution

2023-01-17 Thread Robbie Harwood (frozencemetery)

Package: getmail6
Version: 6.18.11-1
Severity: normal
X-Debbugs-Cc: rharw...@club.cc.cmu.edu

Dear Maintainer,

When running getmails, I get this:

$ getmails
/usr/bin/getmails: 32: Bad substitution
$

and it bails out without downloading any mail.

Of course it's still possible to run getmail itself without the wrapper
script.

Be well,
--Robbie

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

Kernel: Linux 6.0.0-6-amd64 (SMP w/12 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 getmail6 depends on:
ii  python3  3.10.6-3+b1

getmail6 recommends no packages.

getmail6 suggests no packages.

-- no debconf information

Bug#1029079: akonadi-backend-mysql: Build against default-mysql-{client,server}-core 1.1.0

2023-01-17 Thread Patrick Franz

Hi Sedat,

On Tue, 17 Jan 2023 14:51:56 +0100 Sedat Dilek  
wrote:
> I removed akonadi-backend-mysql from my Debian/unstable AMD64 box as I 
> need a higher version of mariadb.

There is no need to remove akonadi-backend-mysql from Sid and I also 
don't see why we would need to rebuild it.
During the upgrade of MariaDB, the package default-mysql-server-core is 
unconfigured for a short moment, but that's it. The log should tell you 
that it's configured afterwards.

-- 
Med vänliga hälsningar

Patrick Franz

Bug#996799: twitterwatch - upload needed

2023-01-17 Thread Malik

Hello Emmanuel,

currently upstream-author has no plan to update or release any further
releases for this project [1]

[1] https://gitlab.com/chaica/twitterwatch/-/issues/1

kind regards,
Malik

Am So., 15. Jan. 2023 um 13:28 Uhr schrieb Emmanuel Arias <
eam...@yaerobi.com>:

> Hi,
>
> On Sun, Jan 15, 2023 at 12:24:43PM +0100, Malik wrote:
> > Hello Emannauel,
> >
> > Thank you for the suggestions.
> >
> > I was not sure how to handle the new homepage [1]  since there are no
> tags
> > or releases maintained by the upstream maintainer, should I delete the
> > watchfile? or can I watch the version in the setup.py ?
>
> Oh, I didn't note it. Perhaps it's a good reason to contact to upstream
> and ask for them. Don't remove d/watch file.
>
> >
> > And for the tests, should I mock the calls to the "internet" since those
> > would be skipped if conceited to the internet
>
> Yes, or skip them.
> >
> >
> > [1]: https://gitlab.com/chaica/twitterwatch/-/tags
> >
> > regards,
> > Malik
> >
>
> Cheers,
> Emmanuel
>


-- 
Malik Mlitat

Bug#1029116: hw-detect: check-missing-firmware fails will attempting to reload kernel module on MT7922 WiFi card

2023-01-17 Thread Cyril Brulebois

Hi Stuart,

and thanks for your report.

Stuart Hayhurst  (2023-01-17):
> Source: hw-detect
> Version: 1.152
> Severity: important
> X-Debbugs-Cc: stuart.a.hayhu...@gmail.com
> 
> Running "Detect network interfaces" hangs the installer, and with a
> bit of troubleshooting, it's caused when check-missing-firmware
> removes and loads the kernel module for my WiFi chip (mt7921e driver)

This wouldn't be the first issue about this modprobe dance, but I'm not
sure why the kernel would go haywire… I'm definitely looking into
firmware related issues these days, so maybe I'll be able to reproduce
it somewhere, and/or find a different solution to account for the newly
installed firmware (current plan would be to keep hw-detect ± as is
while introducing support for non-free-firwmare).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1029097: pam: FTBFS on hurd-i386

2023-01-17 Thread Svante Signell

On Tue, 2023-01-17 at 18:49 +, Sam Hartman wrote:
> > > > > > "Svante" == Svante Signell 
> > > > > > writes:
>     Svante> modules_pam_nologin_tst-pam_nologin-retval.c.diff
> disabling
>     Svante> two subtests failing on GNU/Hurd.  -
> 
> Why do these subtests fail?
> 
tst-pam_nologin-retval.c:185: Assertion failed: PAM_SYSTEM_ERR (0x4) ==
pam_authenticate(pamh, 0) (0x6)
tst-pam_nologin-retval.c:189: Assertion failed: PAM_SYSTEM_ERR (0x4) ==
pam_acct_mgmt(pamh, 0) (0x6)

>     Svante> 
>     Svante> debian_libpam-modules-bin.install.hurd-i386.patch
> creating
>     Svante> an install file for Hurd excluding two systemd-specific
>     Svante> files not needed.
> 
> Why is installing these files harmful?
> I'm reluctant to take  this patch unless it actually breaks something
> and there's no other way to do it.
> If I take this patch, then I'll have to remember to update the hurd
> install list every time something changes.

I did not say they are harmful. They just weren't built/available in
the build tree during the installation of libpam-modules-bin, so that
failed.

(I've tried to add stuff like (arch=!hurd-any) ... to the .install
file. It seems like that such attempts does not work, as they for e.g.
.symbol files.)

I found the two missing files here though: modules/pam_namespace/
pam_namespace_helper
pam_namespace.service

Dunno why they are not found under the debian/ directory.

Thanks!

Bug#1029120: coreutils: csplit: handles {*} repetitions inconsistently

2023-01-17 Thread наб

Package: coreutils
Version: 9.1-1
Severity: normal

Dear Maintainer,

Consider the standard repetition:
-- >8 --
$ seq 999 | csplit - /10/1 {99}
21
271
8
8
8
8
8
400
400
400
400
400
400
400
400
csplit: ‘/10/1’: match not found on repetition 15
356
$ seq 999 | csplit - 88 {99}
252
340
352
352
352
352
352
352
352
352
352
csplit: ‘88’: line number out of range on repetition 11
128
-- >8 --

Good! POSIX agrees:
  An error shall be reported if an operand does not reference
  a line between the current position and the end of the file.
(the operand being /10/1 or 88, resp., as re-applied via {99}).

So why, then:
-- >8 --
$ seq 999 | csplit - /10/1 {*}
21
271
8
8
8
8
8
400
400
400
400
400
400
400
400
356
$ seq 999 | csplit - 88 {*}
252
340
352
352
352
352
352
352
352
352
352
csplit: ‘88’: line number out of range on repetition 11
128
-- >8 --

The manual defines {*} as
  {*}repeat the previous pattern as many times as possible
but then inconsistently uses it as
  88{∞}
  /10/1 {until no more matches}

Best,
наб

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-2
ii  libattr1 1:2.5.1-3
ii  libc62.36-7
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b4

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1026669: request-tracker5: FTBFS: can't locate java: No such file or directory

2023-01-17 Thread Ángel

The error here is that ./debian/build-final-ckeditor.sh fails with
« can't locate java: No such file or directory »

This script is actually calling ckbuilder ( jexec /usr/bin/ckbuilder --
build ... )

However, the package correctly lists ckbuilder as a build-dep, and
ckbuilder itself depends on java ( default-jre | java{7..11}-runtime)

The full build log shows that java *was* installed, *and* that it
provided the usual suspects:

> update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> amd64/bin/java to provide /usr/bin/java (java) in auto mode
> update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> amd64/bin/jpackage to provide /usr/bin/jpackage (jpackage) in auto
> mode
> update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> amd64/bin/keytool to provide /usr/bin/keytool (keytool) in auto mode
> update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> amd64/bin/rmiregistry to provide /usr/bin/rmiregistry (rmiregistry)
> in auto mode
> update-alternatives: using /usr/lib/jvm/java-17-openjdk-
> amd64/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode

Bug#1029122: scm: ftbfs on mipsel

2023-01-17 Thread Bo YU

Source: scm
Version: 5f2-3
Severity: serious 

Dear Maintainer,

The upload[0] cause a regression with build failure on mipsel:

```
...
make checklit
make[3]: Entering directory '/<>'
./scmlit -fr4rstest.scm -e'(test-sc4)(test-delay)(gc)' \
-e '(or (null? errs) (quit 1))' < /dev/null
remove
#define SHORT_INT
in scmfig.h and recompile scm
make[3]: *** [Makefile:553: checklit] Error 1
```

The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=scm=mipsel=5f3-3=1673937776=0

I have fixed the issue on my local machine and upload it after testing it.
Thanks.

[0]: 
https://tracker.debian.org/news/1409807/accepted-scm-5f3-3-source-into-unstable/
-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1028691: dask.distributed: FTBFS: unsatisfiable build-dependencies: python3-dask (>= 2022.02.0), python-numpy-doc

2023-01-17 Thread Sebastiaan Couwenberg


Control: tags -1 pending

python-numpy-doc has been dropped from the build dependencies in git, 
but the package FTBFS due to test failures. Those might be fixed in a 
new upstream release, but that may introduce regressions in its rdeps.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1027900: parole 4.16.0-2 does not start

2023-01-17 Thread Yves-Alexis Perez

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2023-01-04 at 15:12 +0300, Сергей Фёдоров wrote:
> parole 4.16.0-2 when running in the terminal emulator outputs :
> free(): invalid pointer
> Emergency stop
> 
> parole 4.16.0-1 is up and running.

Yes indeed, so we have an issue with -1 which doesn't build, and -2 which
doesn't run...

We'll try to investigate when possible.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmPHo6QACgkQ3rYcyPpX
RFso8wf/a4WKNKwWJ0klpyxStGxtoGL2TVFU1JdB8I+iMsVdIjC+4DoZleLs55Tx
fMas2p0AdP7YrO7xcpHrdBLU4fcqHdmAGe3p5nda6oFhew2JfBVal5CCaZR74n80
kxUg3SIMiA8TGBiOk68x7dO6ukyYmWlzlcBVGnnoDLJbhNv71ZSsQDQ7UEYAllCx
9ZoIej0Yvev7eYomcRQQUiwehosBY+D/efaeQYNnZhnTaLkacWl6rzNZUYaSLoX3
H0xPBh/L2h9aGNYVR6aOdxj3juYeICVlFi876rcPLftVidtmoUgbcdgFx13fQzTW
AEYqe9m+qCFzE+ofdiViAa/ksRSKFQ==
=jQTc
-END PGP SIGNATURE-

Bug#1029118: Possible typo in "#if !(defined(yylex) ..."

2023-01-17 Thread Thomas Dickey

On Wed, Jan 18, 2023 at 12:45:50AM +, Bjarni Ingi Gislason wrote:
> Package: byacc
> Version: byacc - 2.0 20221229
> Severity: normal
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
>   Compiling groff

(in a quick check, I compiled the version from 2022/12/28
on my Debian/oldstable without seeing this problem - but I see
the issue is compiler options).

> 
> 
> output.c:   putl_code(fp, "#if !(defined(yylex) || defined(YYSTATE))\n");
> 
>   "yylex" is a name of a function but "#... defined(...)" applies to
> macros not functions(?).

That's intentional (not a bug).  It's done to allow changing the function
signature -- but not if there's already a macro to confuse things.

Here's more context:

/* Parameters sent to lex. */
#ifdef YYLEX_PARAM
# define YYLEX_DECL() yylex(void *YYLEX_PARAM)
# define YYLEX yylex(YYLEX_PARAM)
#else
# define YYLEX_DECL() yylex(void)
# define YYLEX yylex()
#endif

#if !(defined(yylex) || defined(YYSTATE))
int YYLEX_DECL();
#endif

Changing that YYSTATE to YYLEX will turn off the declaration.

YYSTATE is a lex symbol (#define'd), so it seemed a better choice than
the flex-specific FLEX_SCANNER symbol which Guy Harris used in the first
version of this ifdef.

The intent here is to not use the declaration if the lex/flex code is
inserted before that point (reducing redefinition problems).

> 
> 
>   When compiling, a warning is issued:
> 
>   CXX  src/preproc/eqn/eqn-eqn.o
> src/preproc/eqn/eqn.cpp:73:23: warning: redundant redeclaration of 'int
> yylex()' in same scope [-Wredundant-decls]
>73 | # define YYLEX_DECL() yylex(void)
>   |   ^

yes - that's a problem.  There's been no universally-guaranteed prototype
for yylex, so applications add one.  (There was some update on the Austin
review a couple of years ago, but the recommendation from that would run
into the same problem -- and it introduced other problems).

For this case, I could add a third symbol, which would "only" be set by
the caller (not a lex/flex symbol that one might trip over).

> src/preproc/eqn/eqn.cpp:78:5: note: in expansion of macro 'YYLEX_DECL'
>78 | int YYLEX_DECL();
>   | ^~
> ../src/preproc/eqn/eqn.ypp:31:5: note: previous declaration of 'int
> yylex()'
>31 | int yylex(void);
>   | ^
>   CXXLDeqn
> 
> 
> 
>   When I change "yylex" to "YYLEX" in the "putl_code(...)" line there
> is no warning.
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.0.12-1 (SMP w/2 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_WARN
> 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 byacc depends on:
> ii  libc6  2.36-8
> 
> byacc recommends no packages.
> 
> byacc suggests no packages.

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

signature.asc
Description: PGP signature

Bug#766863: Intent to NMU darkstat to fix longstanding l10n bug

2023-01-17 Thread Emil Mikulic

I'm not planning a new release. Go for it!

Bug#1027656: leaflet autoremoval

2023-01-17 Thread Yadd


On 1/16/23 09:34, Jonas Smedegaard wrote:

[replying via bugreport, to have the conversation public]

Quoting Sebastiaan Couwenberg (2023-01-16 05:54:07)

Do either of you have time to look into fixing #1026688 which will cause
autoremoval of leaflet and its rdeps?


I should be able to take time for that before its removal - but am happy
if others beat me to it.


Hi,

done, was just a missing rollup-3 patch (rollup.config updated to CJS)

Cheers,
Yadd

Bug#1027656: leaflet autoremoval

2023-01-17 Thread Jonas Smedegaard

Quoting Yadd (2023-01-18 06:40:14)
> On 1/16/23 09:34, Jonas Smedegaard wrote:
> > [replying via bugreport, to have the conversation public]
> > 
> > Quoting Sebastiaan Couwenberg (2023-01-16 05:54:07)
> >> Do either of you have time to look into fixing #1026688 which will cause
> >> autoremoval of leaflet and its rdeps?
> > 
> > I should be able to take time for that before its removal - but am happy
> > if others beat me to it.
> 
> Hi,
> 
> done, was just a missing rollup-3 patch (rollup.config updated to CJS)

Thanks!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

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

signature.asc
Description: signature

Bug#1029117: libtasn1-6: Convert d/copyright to machine-readable format

2023-01-17 Thread Andreas Metzler

Control: tags -1 -patch

On 2023-01-17 Bastian Germann  wrote:
> Source: libtasn1-6
> Version: 4.19.0-2
> Tags: patch

> Please consider converting the debian/copyright file to the machine-readable 
> format.
> I have attached a converted file that also adds the missing X11 and FSFAP 
> license and some copyright lines.

Good morning,

DEP-5 per file copyright is quite unmanageable (i.e. enormously
time-consuming if done properly) for non-tiny pieces of software if done
manually by editing debian/copyright.

I will happily apply patches that do the right thing with
"cme update dpkg-copyright", i.e. with debian/fill.copyright.blanks.yml
debian/copyright-scan-patterns.yml and debian/fix.scanned.copyright but
just doing a one-time conversion with huge maintenance costs afterwards
is not productive use of time.

cme seems to be only piece of softwar in Debian thatv tries to tackle
this, but the degree of handholding required via debian/*copyright* is
still huge.

cu Andreas

Bug#1029108: tuxguitar: limit build architectures

2023-01-17 Thread tony mancill

On Tue, Jan 17, 2023 at 11:59:07AM -0800, tony mancill wrote:
> Package: tuxguitar
> Version: 1.5.6+dfsg1-1
> Severity: important
> 
> tuxguitar is FTBFS on multiple architectures:
> 
> https://buildd.debian.org/status/logs.php?pkg=tuxguitar=1.5.6%2Bdfsg1-1
> 
> We should either address the FTBFS or limit the build architectures in
> the next upload.

The initial buildd build failed for arm64, but it's successful for me
locally in a clean chroot.  Once I figure out why it's failing on the
buildd, I intend to restrict the build archs to amd64 and arm64.

signature.asc
Description: PGP signature

Bug#1027686: transition: rakudo

2023-01-17 Thread M. Zhou

I have uploaded moarvm, nqp, and rakudo to unstable.
They turned green on release architectures.
The ppc64el buildd lags a little bit but I believe the result will be
green as well based on the previous no-change build in experimental.

On Sun, 2023-01-15 at 19:09 +0100, Sebastian Ramacher wrote:
> Control: tags -1 = confirmed
> 
> On 2023-01-15 18:49:24 +0100, Dominique Dumont wrote:
> > On Sunday, 15 January 2023 15:21:55 CET Sebastian Ramacher wrote:
> > > > I've found where compiler-id is computed. I'm going patch
> > > > rakudo in
> > > > experimental so that compiler-id depends only on source files
> > > > and nqp
> > > > version. This patch will land in experimental.
> > > 
> > > Okay, please let me know once it's available in experimental.
> > 
> > Done with rakudo 2022.12-1~exp3
> > 
> > I've patched the compiler id to be a sha1 of "Debian- > version>".
> > 
> > I've verified that compiler id is the same for the arch that are
> > built.
> > 
> > Is it still time to trigger a transition to fix all raku modules ?
> > (there's no 
> > impact outside of raku modules)
> 
> Thanks, please go ahead.
> 
> Cheers

Bug#1029121: bullseye-pu: package lxc/4.0.6-2+deb11u2

2023-01-17 Thread Mathias Gibbens

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: pkg-lxc-de...@lists.alioth.debian.org, gib...@debian.org
Control: affects -1 + src:lxc

[ Reason ]
The version of lxc in bullseye is affected by the low-severity
CVE-2022-47952 which was fixed in the recent release of lxc 5.0.2
(uploaded to unstable yesterday). As the fix was trivial to apply to
the version of lxc in bullseye, I think it would be beneficial to
include it in the next point release.

[ Impact ]
Affected versions of lxc suffer a minor information leak which allows a
local user to infer whether any file exists, even within a protected
directory tree.

[ Tests ]
A manual proof-of-concept test is provided in the upstream commit
fixing this issue.

[ Risks ]
There are no changes to any of the logic of lxc; the error messages
which are returned are modified to be identical in every error case,
preventing the information leak.

[ Checklist ]
  [*] *all* changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in (old)stable
  [*] the issue is verified as fixed in unstable

[ Changes ]
Backport upstream commit 1b0469530d7a38b8f8990e114b52530d1bf7f3b8,
which fixes CVE-2022-47952. (The line numbers in the diff shifted
slightly, otherwise no changes to the patch.)

[ Other info ]
The source debdiff is attached.
diff -Nru lxc-4.0.6/debian/changelog lxc-4.0.6/debian/changelog
--- lxc-4.0.6/debian/changelog	2022-01-13 19:57:39.0 +
+++ lxc-4.0.6/debian/changelog	2023-01-18 02:53:46.0 +
@@ -1,3 +1,9 @@
+lxc (1:4.0.6-2+deb11u2) bullseye; urgency=medium
+
+  * Backport fix for CVE-2022-47952
+
+ -- Mathias Gibbens   Wed, 18 Jan 2023 02:53:46 +
+
 lxc (1:4.0.6-2+deb11u1) bullseye; urgency=medium
 
   * lxc-download: Switch GPG server.
diff -Nru lxc-4.0.6/debian/patches/fix-CVE-2022-47952.patch lxc-4.0.6/debian/patches/fix-CVE-2022-47952.patch
--- lxc-4.0.6/debian/patches/fix-CVE-2022-47952.patch	1970-01-01 00:00:00.0 +
+++ lxc-4.0.6/debian/patches/fix-CVE-2022-47952.patch	2023-01-18 02:53:23.0 +
@@ -0,0 +1,69 @@
+From 1b0469530d7a38b8f8990e114b52530d1bf7f3b8 Mon Sep 17 00:00:00 2001
+From: Maher Azzouzi 
+Date: Sun, 25 Dec 2022 13:50:25 +0100
+Subject: [PATCH] Patching an incoming CVE (CVE-2022-47952)
+
+lxc-user-nic in lxc through 5.0.1 is installed setuid root, and may
+allow local users to infer whether any file exists, even within a
+protected directory tree, because "Failed to open" often indicates
+that a file does not exist, whereas "does not refer to a network
+namespace path" often indicates that a file exists. NOTE: this is
+different from CVE-2018-6556 because the CVE-2018-6556 fix design was
+based on the premise that "we will report back to the user that the
+open() failed but the user has no way of knowing why it failed";
+however, in many realistic cases, there are no plausible reasons for
+failing except that the file does not exist.
+
+PoC:
+> % ls /l
+> ls: cannot open directory '/l': Permission denied
+> % /usr/lib/x86_64-linux-gnu/lxc/lxc-user-nic delete lol lol /l/h/tt h h
+> cmd/lxc_user_nic.c: 1096: main: Failed to open "/l/h/tt" <- file does not exist.
+> % /usr/lib/x86_64-linux-gnu/lxc/lxc-user-nic delete lol lol /l/h/t h h
+> cmd/lxc_user_nic.c: 1101: main: Path "/l/h/t" does not refer to a network namespace path < file exist!
+
+Signed-off-by: MaherAzzouzi 
+Acked-by: Serge Hallyn 
+---
+ src/lxc/cmd/lxc_user_nic.c | 15 ++-
+ 1 file changed, 6 insertions(+), 9 deletions(-)
+
+diff --git a/src/lxc/cmd/lxc_user_nic.c b/src/lxc/cmd/lxc_user_nic.c
+index a91e2259d5..69bc6f17d1 100644
+--- a/src/lxc/cmd/lxc_user_nic.c
 b/src/lxc/cmd/lxc_user_nic.c
+@@ -1088,20 +1088,17 @@ int main(int argc, char *argv[])
+ 	} else if (request == LXC_USERNIC_DELETE) {
+ 		char opath[LXC_PROC_PID_FD_LEN];
+ 
+-		/* Open the path with O_PATH which will not trigger an actual
+-		 * open(). Don't report an errno to the caller to not leak
+-		 * information whether the path exists or not.
+-		 * When stracing setuid is stripped so this is not a concern
+-		 * either.
+-		 */
++		// Keep in mind CVE-2022-47952: It's crucial not to leak any
++		// information whether open() succeeded of failed.
++
+ 		netns_fd = open(args.pid, O_PATH | O_CLOEXEC);
+ 		if (netns_fd < 0) {
+-			usernic_error("Failed to open \"%s\"\n", args.pid);
++			usernic_error("Failed while opening netns file for \"%s\"\n", args.pid);
+ 			_exit(EXIT_FAILURE);
+ 		}
+ 
+ 		if (!fhas_fs_type(netns_fd, NSFS_MAGIC)) {
+-			usernic_error("Path \"%s\" does not refer to a network namespace path\n", args.pid);
++			usernic_error("Failed while opening netns file for \"%s\"\n", args.pid);
+ 			close(netns_fd);
+ 			_exit(EXIT_FAILURE);
+ 		}
+@@ -1115,7 +1112,7 @@ int main(int argc, char *argv[])
+ 		/* Now get an fd that we can use in setns() calls. */
+ 		ret = open(opath,

Bug#1025618: cloud-init and firewalld systemd unit files have ordering cycles

2023-01-17 Thread Ross Vandegrift

On Fri, Dec 16, 2022 at 03:48:00PM -0800, Ross Vandegrift wrote:
> At a high level the issue is: firewalld.service forces network-pre.target 
> after
> sysinit.target, but cloud-init.service forces the other way around.  In 
> detail,
> using < to represent Before, the imposed orderings look like:
> 
> - from firewalld:
>   sysinit.target < dbus.service < firewalld.service < network-pre.target
> - from cloud-init:
>   cloud-init-local.service < network-pre.target < 
> systemd-networkd-wait-online.service < cloud-init.service < sysinit.target
> 
> There's a few approaches to resolving this.  As far as I can tell, the only
> immediately viable one (at the bottom) requires users to manually fix this
> and accept some trade-offs.  Anyone have any better ideas?

We discussed this issue on the recent cloud-team meeting and had some
revised options.

> Modify firewalld to run before sysinit.target 
> -
[snip]

This one still seems impossible.

> Modify cloud-init to run after sysinit.target
> -
[snip]

The main downside of this one, is that cloud-init will be running too
late to configure block devices.  But this feature didn't always work
well.  So maybe we'd affect a non-working feature.

I've confirmed that cloud-init's block device setup is working well on
AWS at least.  So I think this will break working cloud-init features.
IMO, that means it is not viable.

> Locally override firewalld.service's order
> --
[snip]

This remains unattractive since unsuspecting users will be left with
broken images and no clear path to fix the problem.

Modify dbus to run later

We discussed a way improve things by shuffling dbus later, but I didn't
take good enough notes, and I can't reconstruct the details.  Sorry for
forgetting - Bastian do you recall the details?

Add Breaks or Conflicts to prevent coinstallation
-

None of the alternatives seem reasonable and installing cloud-init and
firewalld cannot produce a working Debian image.  So we should prevent
this state.

We thought Conflicts might be required because once both are unpacked,
the problematic cycle technically exists.  Though it may not cause harm
unless both services are (re-)started simultaneously.

Ross

Bug#1029124: adduser: french transalation update of manual

2023-01-17 Thread Guillonneau Jean-Paul

Package: adduser
Version: 3.118
Severity: wishlist

Dear Maintainer,

Please find attached the french update of the translation of the manpage of
adduser, proofread by the
debian-l10n-french mailing list contributors.

Regards.


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

Kernel: Linux 5.10.0-20-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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

Versions of packages adduser depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  passwd 1:4.8.1-1

adduser recommends no packages.

Versions of packages adduser suggests:
ii  liblocale-gettext-perl  1.07-4+b1
ii  perl5.32.1-4+deb11u2

-- debconf information:
  adduser/title:
# adduser's manual pages translation to French
# Copyright (C) 2004 Software in the Public Interest
# This file is distributed under the same license as the adduser package
#
# Nicolas François , 2008.
# David Prévot , 2010.
# Jean-Paul Guillonneau , 2016-2023.
msgid ""
msgstr ""
"Project-Id-Version: adduser 3.115\n"
"POT-Creation-Date: 2023-01-04 08:44+0100\n"
"PO-Revision-Date: 2023-01-18 08:09+0100\n"
"Last-Translator: Jean-Paul Guillonneau \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: vim\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

# type: TH
#. type: TH
#: ../adduser.8:16
#, no-wrap
msgid "ADDUSER"
msgstr "ADDUSER"

# type: TH
#. type: TH
#: ../adduser.8:16 ../adduser.conf.5:13 ../deluser.8:13 ../deluser.conf.5:12
#, no-wrap
msgid "Debian GNU/Linux"
msgstr "Debian GNU/Linux"

# type: SH
#. type: SH
#: ../adduser.8:17 ../adduser.conf.5:14 ../deluser.8:14 ../deluser.conf.5:13
#, no-wrap
msgid "NAME"
msgstr "NOM"

# type: Plain text
#. type: Plain text
#: ../adduser.8:19
msgid "adduser, addgroup - add or manipulate users or groups"
msgstr ""
"adduser, addgroup – Ajouter ou manipuler des utilisateurs ou des groupes"

# type: SH
#. type: SH
#: ../adduser.8:19 ../deluser.8:16
#, no-wrap
msgid "SYNOPSIS"
msgstr "SYNOPSIS"

# type: TH
#. type: SY
#: ../adduser.8:20 ../adduser.8:43 ../adduser.8:59 ../adduser.8:88
#: ../adduser.8:96 ../adduser.8:99
#, no-wrap
msgid "adduser"
msgstr "adduser"

# type: TP
#. type: OP
#: ../adduser.8:21
#, no-wrap
msgid "--add-extra-groups"
msgstr "--add-extra-groups"

#. type: OP
#: ../adduser.8:22
#, no-wrap
msgid "--allow-all-names"
msgstr "--allow-all-names"

# type: TP
#. type: OP
#: ../adduser.8:23
#, no-wrap
msgid "--allow-bad-names"
msgstr "--allow-bad-names"

#. type: OP
#: ../adduser.8:24 ../adduser.8:45
#, no-wrap
msgid "--comment"
msgstr "--comment"

#. type: OP
#: ../adduser.8:24 ../adduser.8:45
#, no-wrap
msgid "comment"
msgstr "commentaire"

# type: TP
#. type: OP
#: ../adduser.8:25 ../adduser.8:46 ../adduser.8:61 ../adduser.8:71
#: ../adduser.8:83 ../adduser.8:89 ../deluser.8:21 ../deluser.8:34
#: ../deluser.8:44 ../deluser.8:52 ../deluser.8:60
#, no-wrap
msgid "--conf"
msgstr "--conf"

#. type: OP
#: ../adduser.8:25 ../adduser.8:46 ../adduser.8:61 ../adduser.8:71
#: ../adduser.8:83 ../adduser.8:89 ../deluser.8:21 ../deluser.8:34
#: ../deluser.8:44 ../deluser.8:52 ../deluser.8:60
#, no-wrap
msgid "file"
msgstr "fichier"

# type: TP
#. type: OP
#: ../adduser.8:26 ../adduser.8:47 ../adduser.8:62 ../adduser.8:72
#: ../adduser.8:90 ../deluser.8:22 ../deluser.8:35 ../deluser.8:45
#: ../deluser.8:53 ../deluser.8:61
#, no-wrap
msgid "--debug"
msgstr "--debug"

# type: TP
#. type: OP
#: ../adduser.8:27
#, no-wrap
msgid "--disabled-login"
msgstr "--disabled-login"

# type: TP
#. type: OP
#: ../adduser.8:28
#, no-wrap
msgid "--disabled-password"
msgstr "--disabled-password"

# NOTE: ce serait mieux d'avoir exactement la même chaîne que dans deluser
# type: TP
#. type: OP
#: ../adduser.8:29 ../adduser.8:63 ../adduser.8:73
#, no-wrap
msgid "--firstgid"
msgstr "--firstgid"

#. type: OP
#: ../adduser.8:29 ../adduser.8:30 ../adduser.8:31 ../adduser.8:34
#: ../adduser.8:35 ../adduser.8:39 ../adduser.8:48 ../adduser.8:54
#: ../adduser.8:63 ../adduser.8:65 ../adduser.8:73 ../adduser.8:75
#: ../adduser.8:82
#, no-wrap
msgid "id"
msgstr "ID"

# NOTE: ce serait mieux d'avoir exactement la même chaîne que dans deluser
# type: TP
#. type: OP
#: ../adduser.8:30
#, no-wrap
msgid "--firstuid"
msgstr "--firstuid"

#. type: OP
#: ../adduser.8:31 ../adduser.8:48 ../adduser.8:64 ../adduser.8:74
#: ../adduser.8:82
#, no-wrap
msgid "--gid"
msgstr "--gid"

# type: TP
#. type: OP
#: ../adduser.8:32 ../adduser.8:50
#, no-wrap
msgid "--home"
msgstr "--home"

#. type: OP
#: ../adduser.8:32 ../adduser.8:50 ../deluser.8:20 ../deluser.8:33
#, no-wrap
msgid "dir"
msgstr "rép"

#

Bug#996839: [PATCH v3] perf script flamegraph: Avoid d3-flame-graph package dependency

2023-01-17 Thread Ian Rogers

Currently flame graph generation requires a d3-flame-graph template to
be installed. Unfortunately this is hard to come by for things like
Debian [1]. If the template isn't installed then ask if it should be
downloaded from jsdelivr CDN. The downloaded HTML file is validated
against an md5sum. If the download fails, generate a minimal flame
graph with the javascript coming from links to jsdelivr CDN.

v3. Adds a warning message and quits before download in live mode.
v2. Change the warning to a prompt about downloading and add the
--allow-download command line flag. Add an md5sum check for the
downloaded HTML.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996839

Signed-off-by: Ian Rogers 
---
 tools/perf/scripts/python/flamegraph.py | 107 +++-
 1 file changed, 85 insertions(+), 22 deletions(-)

diff --git a/tools/perf/scripts/python/flamegraph.py 
b/tools/perf/scripts/python/flamegraph.py
index b6af1dd5f816..cf7ce8229a6c 100755
--- a/tools/perf/scripts/python/flamegraph.py
+++ b/tools/perf/scripts/python/flamegraph.py
@@ -19,12 +19,34 @@
 # pylint: disable=missing-function-docstring
 
 from __future__ import print_function
-import sys
-import os
-import io
 import argparse
+import hashlib
+import io
 import json
+import os
 import subprocess
+import sys
+import urllib.request
+
+minimal_html = """
+  https://cdn.jsdelivr.net/npm/d3-flame-graph@4.1.3/dist/d3-flamegraph.css;>
+
+
+  
+  https://d3js.org/d3.v7.js";>
+  https://cdn.jsdelivr.net/npm/d3-flame-graph@4.1.3/dist/d3-flamegraph.min.js";>
+  
+  const stacks = [/** @flamegraph_json **/];
+  // Note, options is unused.
+  const options = [/** @options_json **/];
+
+  var chart = flamegraph();
+  d3.select("#chart")
+.datum(stacks[0])
+.call(chart);
+  
+
+"""
 
 # pylint: disable=too-few-public-methods
 class Node:
@@ -50,16 +72,6 @@ class FlameGraphCLI:
 self.args = args
 self.stack = Node("all", "root")
 
-if self.args.format == "html" and \
-not os.path.isfile(self.args.template):
-print("Flame Graph template {} does not exist. Please install "
-  "the js-d3-flame-graph (RPM) or libjs-d3-flame-graph (deb) "
-  "package, specify an existing flame graph template "
-  "(--template PATH) or another output format "
-  "(--format FORMAT).".format(self.args.template),
-  file=sys.stderr)
-sys.exit(1)
-
 @staticmethod
 def get_libtype_from_dso(dso):
 """
@@ -128,16 +140,63 @@ class FlameGraphCLI:
 }
 options_json = json.dumps(options)
 
+template_md5sum = None
+if self.args.format == "html":
+if os.path.isfile(self.args.template):
+template = f"file://{self.args.template}"
+else:
+if not self.args.allow_download:
+print(f"""Warning: Flame Graph template 
'{self.args.template}'
+does not exist. To avoid this please install a package such as the
+js-d3-flame-graph or libjs-d3-flame-graph, specify an existing flame
+graph template (--template PATH) or use another output format (--format
+FORMAT).""",
+  file=sys.stderr)
+if self.args.input == "-":
+print("""Not attempting to download Flame Graph 
template as script command line
+input is disabled due to using live mode. If you want to download the
+template retry without live mode. For example, use 'perf record -a -g
+-F 99 sleep 60' and 'perf script report flamegraph'. Alternatively,
+download the template from:
+https://cdn.jsdelivr.net/npm/d3-flame-graph@4.1.3/dist/templates/d3-flamegraph-base.html
+and place it at:
+/usr/share/d3-flame-graph/d3-flamegraph-base.html""",
+  file=sys.stderr)
+quit()
+s = None
+while s != "y" and s != "n":
+s = input("Do you wish to download a template from 
cdn.jsdelivr.net? (this warning can be suppressed with --allow-download) [yn] 
").lower()
+if s == "n":
+quit()
+template = 
"https://cdn.jsdelivr.net/npm/d3-flame-graph@4.1.3/dist/templates/d3-flamegraph-base.html;
+template_md5sum = "143e0d06ba69b8370b9848dcd6ae3f36"
+
 try:
-with io.open(self.args.template, encoding="utf-8") as template:
-output_str = (
-template.read()
-.replace("/** @options_json **/", options_json)
-.replace("/** @flamegraph_json **/", stacks_json)
-)
-except IOError as err:
-print("Error reading template file: {}".format(err), 
file=sys.stderr)
-

Bug#996839: [PATCH v2] perf script flamegraph: Avoid d3-flame-graph package dependency

2023-01-17 Thread Ian Rogers

On Tue, Jan 17, 2023 at 7:17 AM Andreas Gerstmayr  wrote:
>
> On 12.01.23 23:00, Ian Rogers wrote:
> > Currently flame graph generation requires a d3-flame-graph template to
> > be installed. Unfortunately this is hard to come by for things like
> > Debian [1]. If the template isn't installed then ask if it should be
> > downloaded from jsdelivr CDN. The downloaded HTML file is validated
> > against an md5sum. If the download fails, generate a minimal flame
> > graph with the javascript coming from links to jsdelivr CDN.
> >
> > v2. Change the warning to a prompt about downloading and add the
> >  --allow-download command line flag. Add an md5sum check for the
> >  downloaded HTML.
> >
> > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996839
> >
> > Signed-off-by: Ian Rogers 
>
> Thank you for the changes. I've tested v2 with:
>
> * d3-flame-graph package installed
> * template not installed, download template from jsdelivr
> * download from jsdelivr, with --allow-download
> * invalid checksum
> * unreachable jsdelivr, creating a minimal template
>
> Everything works great except when I'm invoking "perf script flamegraph
> -a -F 99 sleep 10" (combining perf report + perf script):
>
> [root@agerstmayr-thinkpad tmp]# perf script flamegraph -a -F 99 sleep 10
> 
> [...]
> 
> Warning: Flame Graph template
> '/usr/share/d3-flame-graph/d3-flamegraph-base.html'
> does not exist. To avoid this please install a package such as the
> js-d3-flame-graph or libjs-d3-flame-graph, specify an existing flame
> graph template (--template PATH) or use another output format (--format
> FORMAT).
> Do you wish to download a template from cdn.jsdelivr.net? (this warning
> can be suppressed with --allow-download) [yn] Traceback (most recent
> call last):
>File "/usr/libexec/perf-core/scripts/python/flamegraph.py", line 157,
> in trace_end
>  s = input("Do you wish to download a template from
> cdn.jsdelivr.net? (this warning can be suppressed with --allow-download)
> [yn] ").lower()
>
> ^^^
> OSError: [Errno 9] Bad file descriptor
> Fatal Python error: handler_call_die: problem in Python trace event handler
> Python runtime state: initialized
>
> Current thread 0x7ff4053a3cc0 (most recent call first):
>
>
> Extension modules: systemd._journal, systemd._reader, systemd.id128
> (total: 3)
> /usr/libexec/perf-core/scripts/python/bin/flamegraph-report: line 3:
> 2135491 Aborted (core dumped) perf script -s
> "$PERF_EXEC_PATH"/scripts/python/flamegraph.py -- "$@"
>
>
> iirc when running "perf script flamegraph" the perf.data gets piped to
> stdin of the flamegraph script, so we can't ask the user in this case.
> You can check this condition with `self.args.input == "-". Not sure
> what's the best action in this case, maybe just exit?

Thanks Andreas,

There's no way to handle command line arguments to the script in
"live" mode and so I sent a v3 where the script warns and then
quit()s. The only other option would have been to assume downloading,
and we'd agreed to avoid that. Hopefully v3 is in the right shape now.

Thanks again,
Ian

>
> Cheers,
> Andreas
>
>
> > ---
> >   tools/perf/scripts/python/flamegraph.py | 96 +++--
> >   1 file changed, 74 insertions(+), 22 deletions(-)
> >
> > diff --git a/tools/perf/scripts/python/flamegraph.py 
> > b/tools/perf/scripts/python/flamegraph.py
> > index b6af1dd5f816..086619053e4e 100755
> > --- a/tools/perf/scripts/python/flamegraph.py
> > +++ b/tools/perf/scripts/python/flamegraph.py
> > @@ -19,12 +19,34 @@
> >   # pylint: disable=missing-function-docstring
> >
> >   from __future__ import print_function
> > -import sys
> > -import os
> > -import io
> >   import argparse
> > +import hashlib
> > +import io
> >   import json
> > +import os
> >   import subprocess
> > +import sys
> > +import urllib.request
> > +
> > +minimal_html = """
> > +   > href="https://cdn.jsdelivr.net/npm/d3-flame-graph@4.1.3/dist/d3-flamegraph.css;>
> > +
> > +
> > +  
> > +  https://d3js.org/d3.v7.js";>
> > +   > src="https://cdn.jsdelivr.net/npm/d3-flame-graph@4.1.3/dist/d3-flamegraph.min.js";>
> > +  
> > +  const stacks = [/** @flamegraph_json **/];
> > +  // Note, options is unused.
> > +  const options = [/** @options_json **/];
> > +
> > +  var chart = flamegraph();
> > +  d3.select("#chart")
> > +.datum(stacks[0])
> > +.call(chart);
> > +  
> > +
> > +"""
> >
> >   # pylint: disable=too-few-public-methods
> >   class Node:
> > @@ -50,16 +72,6 @@ class FlameGraphCLI:
> >   self.args = args
> >   self.stack = Node("all", "root")
> >
> > -if

Bug#1027753: closed by Andreas Rönnquist (Re: Bug#1027753: geeqie crashes on ssh-forwared remote X)

2023-01-17 Thread Lars Rohwedder


The bug itself is _not_ fixed. The command-line option is just a
workaround, so geeqie is usable again, but it (or one of the used
libraries) still contains the bug.

So the severity might be lower and might be moved to the causing
library, but a segfault is still a thing that should be fixed. Don't you
think so?

Lars R.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1029098: qt6-wayland: Component WaylandClient requires private Qt6WaylandGlobalPrivate

2023-01-17 Thread Lisandro Damián Nicanor Pérez Meyer

Control: tag -1 pending

These are indeed implementation-private modules, adding them does not
requires the use of private headers. The fix has been implemented in
commit 5e44bf5ab207edfbe481090e75478a750271a548. I'll be pushing the
package ASAP.


-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/

Bug#1029103: coreutils: csplit: -z misdocumented

2023-01-17 Thread наб

Package: coreutils
Version: 9.1-1
Severity: normal

Dear Maintainer,

Quoth csplit(1):
-- >8 --
   -z, --elide-empty-files
  remove empty output files
-- >8 --

So given:
-- >8 --
$ (cd nz; printf '%s\n' q w e r t | csplit - 1 4)
0
6
4
$ find nz
nz
nz/xx02
nz/xx01
nz/xx00
$ head nz/*
==> nz/xx00 <==

==> nz/xx01 <==
q
w
e

==> nz/xx02 <==
r
t
-- >8 --

What do you expect the equivalent with -z to be?
Naturally, the manual says "remove", so I'd expect xx01 and xx02
to remain unchanged, but xx00 to be gone.

Let's see:
-- >8 --
$ (cd z; printf '%s\n' q w e r t | csplit -z - 1 4)
6
4
$ find z
z
z/xx01
z/xx00
$ head z/*
==> z/xx00 <==
q
w
e

==> z/xx01 <==
r
t
-- >8 --

Hm. Smells to me like the empty sexions are just ignored entirely
not removed afterward.

наб

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-2
ii  libattr1 1:2.5.1-3
ii  libc62.36-7
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b4

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1029063: reportbug: linux-image-6.0.0-6-amd64 remains unconfigured because of errors

2023-01-17 Thread Diederik de Haas

On Tuesday, 17 January 2023 18:12:30 CET Andreas Beckmann wrote:
> On Tue, 17 Jan 2023 10:56:33 +0100 Bastian Blank  wrote:
> > > Error! Bad return status for module build on kernel: 6.0.0-6-amd64
> > > (x86_64)
> > > Consult /var/lib/dkms/anbox-binder/1/build/make.log for more
> > > information.
> 
> That does not look like a module packaged in Debian ...

These kind of issues get regularly filed against the Debian kernel and it does 
not matter whether the dkms module is packaged in Debian or not. If the dkms 
module is packaged in Debian, we assign it to the specific dkms package.

> > dkms fails the installation if anything it tries to build does not work.
> > This must go, reassigning accordingly.
> 
> What should dkms do instead? Out-of-tree modules break frequently on new
> kernel upstream major versions, that is completely out of dkms' control.
> 
> There are two points in time where these errors could show up:
> * ) at package installation/upgrade time because building the module
>  failed (there is a small chance of the build succeeding ater reboot
>  if a badly packaged module only supports building against the
>  running kernel)
> * ) at reboot due to a missing kernel module
> 
> A failing module could build be 'harmless' if it's e.g. just the
> soundcard driver missing (unless you depend on text-to-speech) but in
> the worst case it's the root file system that is not supported...

It seems fine to print (in all caps afaic) that there is an issue.

But it should not cause the kernel package install/upgrade to fail.
And that does seem in dkms' control afaict.

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

Bug#1029083: mrcal FTBFS with nocheck profile: ModuleNotFoundError: No module named 'numpy'

2023-01-17 Thread Dima Kogan

Thanks for checking, Helmut. After talking to you on the mailing list I
had already solved the problem, but haven't made an upload yet. Doing
that right now. Thanks.

https://lists.debian.org/debian-cross/2023/01/msg1.html

Bug#1029101: Acknowledgement (fontconfig-config: 2.14.1 upload breaks testSimpleText of libreoffice)

2023-01-17 Thread Rene Engelhard


Hi again,

Am 17.01.23 um 18:28 schrieb Rene Engelhard:
I tried to adapt the test to expected values but failed. When I adapt 
some values stuff even further breaks, and at the 50% test I then had no 
idea what to do.)


LO has already a fc_local.conf:

./instdir/share/fonts/truetype/fc_local.conf

but when I add the stuff from the patch  there

rene@frodo:~/Debian/Pakete/LibreOffice/libreoffice/libreoffice-7.4.4.2$ 
cat ./instdir/share/fonts/truetype/fc_local.conf





  Symbol
  
OpenSymbol
  

  


  KDE

mode="append">rgb

  


it still fails. Probably it ignores it since it's already set in /etc 
and that already matches?


Regards,


Rene

Bug#927302: Please send me more ads 梁

2023-01-17 Thread Smantha Mwebaze

Bug#1028439:

2023-01-17 Thread deb-bug . oluj0xj403ou050siy9dpk2z

As this is still open and breaking many computers: Here is one more hand to 
confirm.

Would you mind explaining what an 's.d.o downgrade' entails? I used the 
snapshot archive and pinned the offender, then used aptitude and skipped 
through solutions until I found an acceptable one. (apt wants to kill all of 
X!). That is a pretty convoluted and unreliable process. 'dontbreakdebian' also 
says to never mess around like that.
There is no official SOP as far as I'm aware.

The process on Fedora given here 
https://gitlab.freedesktop.org/mesa/mesa/-/issues/8007 seems a lot more 
straightforward.

I understand this is 'testing' - but Debian testing > Arch regular and many 
people even consider sid to be usable everyday (see 'siduction').

Can we please revert this package instantly while we wait for an upstream fix? 
Testing is so darn stable usually, many 'normal' people use it in prod. This is 
a very severe bug in my book, right next to that kernel one a few months ago 
killing screens. Unless you're rather deep into Debian, you're never going to 
find the workaround, and likely just move on.

Bug#1023608: RFP: pytomlpp


Control: retitle -1 ITP: python-pytomlpp -- Python wrapper for toml++

Please make sure that your draft package's source package name matches the ITP 
name.

Bug#1029074: fatresize: misleading functionality / messed up with GPT table

2023-01-17 Thread Yangfl

Package: fatresize
Version: 1.1.0-2
Severity: important

This program, unlikely other fs resizing utils like `resize2fs` or
`btrfs filesystem resize`, does not only resize fs, but also alter the
partition table, which is not mentioned in the help text or man page
at all. As the result of messing up with partition tables, this
program may lead to one of the following consequences:

* `-s max` will fail if there is any partitions after the current
partition, showing

  Error: Can't have overlapping partitions.

instead of taking the free space after the current partition.

*  `-s max` will silently failed on GPT disk, resulting an unusable
and un-fsck-able fs. `dosfsck` will give the following error message:

  Seek to :Invalid argument

The only way to recover it is to reconstruct the disk with MBR
partition table and create a partition up to the end of disk, to pick
up sectors which is unusable in GPT scheme.

* Once `-i` is specified as one of the options, resizing operation
`-s` will be ignored without any warning, nor is it mentioned in any
help text.

Bug#1029079: akonadi-backend-mysql: Build against default-mysql-{client,server}-core 1.1.0

2023-01-17 Thread Sedat Dilek

Package: akonadi-backend-mysql
Version: 4:22.12.0-2
Severity: normal
X-Debbugs-Cc: sedat.di...@gmail.com

Dear Maintainer,

I removed akonadi-backend-mysql from my Debian/unstable AMD64 box as I need a 
higher version of mariadb.

These changes were done on my latest upgrade:

-ii  mariadb-client-core-10.61:10.6.11-2
+ii  mariadb-client-core 1:10.11.1-1
-ii  mariadb-server-core-10.61:10.6.11-2
+ii  mariadb-server-core 1:10.11.1-1

-ii  default-mysql-client-core   1.0.8
-ii  default-mysql-server-core   1.0.8
+ii  default-mysql-client-core   1.1.0
+ii  default-mysql-server-core   1.1.0
-ii  mysql-common5.8+1.0.8
+ii  mysql-common5.8+1.1.0

Can you please build against latest default-mysql-{client,server}-core v1.1.0 
aka mariadb 10.11?

Thanks.

Best regards,
-Sedat-

P.S.: From my upgrade log:

...
Unpacking default-mysql-server-core (1.1.0) over (1.0.8) ...
dpkg: mariadb-server-core-10.6: dependency problems, but removing anyway as you 
requested:
 akonadi-backend-mysql depends on default-mysql-server-core | 
virtual-mysql-server-core; however:
  Package default-mysql-server-core is not configured yet.
  Package virtual-mysql-server-core is not installed.
  Package mariadb-server-core-10.6 which provides virtual-mysql-server-core is 
to be removed.
...
dpkg: mariadb-client-core-10.6: dependency problems, but removing anyway as you 
requested:
 akonadi-backend-mysql depends on default-mysql-client-core | 
virtual-mysql-client-core; however:
  Package default-mysql-client-core is not configured yet.
  Package virtual-mysql-client-core is not installed.
  Package mariadb-client-core-10.6 which provides virtual-mysql-client-core is 
to be removed.
...

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

Kernel: Linux 6.2.0-rc4-1-amd64-clang15-kcfi (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de:en_US:en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages akonadi-backend-mysql depends on:
ii  default-mysql-client-core1.1.0
ii  default-mysql-server-core1.1.0
ii  libqt5sql5-mysql 5.15.8+dfsg-2
ii  mariadb-client-core [virtual-mysql-client-core]  1:10.11.1-1
ii  mariadb-server-core [virtual-mysql-server-core]  1:10.11.1-1

Versions of packages akonadi-backend-mysql recommends:
ii  akonadi-server  4:22.12.0-2+b1

akonadi-backend-mysql suggests no packages.

-- no debconf information

Bug#1029084: cpmtools FTCBFS: multiple reasons

Source: cpmtools
Version: 2.20-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

cpmtools fails to build from source. The immediate cause is failure to
pass --host to configure. The easiest way of doing so is letting
dh_auto_configure do it. Unfortunately, it also passes dpkg-buildflags,
which adds -Werror=format-security and makes the build fail, but we can
set hardening=-format to avoid that. Consider fixing the underlying
issue though. Later it strips with the build architecture strip during
make install. This also happens to break generation of -dbgsym packages
as well as DEB_BUILD_OPTIONS=nostrip. I'm attaching a patch for all of
these (except the actual causes of -Werror=format-security) for your
convenience.

Helmut
diff --minimal -Nru cpmtools-2.20/debian/changelog 
cpmtools-2.20/debian/changelog
--- cpmtools-2.20/debian/changelog  2017-12-30 07:35:59.0 +0100
+++ cpmtools-2.20/debian/changelog  2023-01-15 22:02:41.0 +0100
@@ -1,3 +1,11 @@
+cpmtools (2.20-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass --host and pass a non-stripping
+install to make install. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 15 Jan 2023 22:02:41 +0100
+
 cpmtools (2.20-2) unstable; urgency=low
 
   * updated to policy 4.1.3
diff --minimal -Nru cpmtools-2.20/debian/rules cpmtools-2.20/debian/rules
--- cpmtools-2.20/debian/rules  2017-12-30 07:35:59.0 +0100
+++ cpmtools-2.20/debian/rules  2023-01-15 22:02:41.0 +0100
@@ -1,5 +1,8 @@
 #!/usr/bin/make -f
 
+# FTBFS with -Werror=format-security
+export DEB_BUILD_MAINT_OPTIONS=hardening=-format
+
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
@@ -8,8 +11,7 @@
dh_testdir
cp /usr/share/misc/config.sub config.sub
cp /usr/share/misc/config.guess config.guess
-   ./configure --prefix=/usr --mandir=\$${prefix}/share/man \
-   --datarootdir=/etc/cpmtools
+   dh_auto_configure -- --datarootdir=/etc/cpmtools
touch configure-stamp
 
 build: build-arch build-indep
@@ -33,7 +35,8 @@
dh_prep
dh_installdirs
$(MAKE) install prefix=$(CURDIR)/debian/cpmtools/usr \
-   datarootdir=$(CURDIR)/debian/cpmtools/etc/cpmtools
+   datarootdir=$(CURDIR)/debian/cpmtools/etc/cpmtools \
+   'INSTALL=install --strip-program=true'
 
 # Build architecture-independent files here.
 binary-indep: build install

Bug#1029085: borgbackup: manage /usr/bin/borg using update-alternatives

Package: borgbackup
Version: 1.2.3-1
Severity: important
Tags: patch
Control: block 1019950 by -1

Hi,

In order to fix #1019950, I would like to manage /usr/bin/borg using
update-alternatives. My idea for managing this is as follows:

 * Rename all command line utilities and manual pages such that they get
   a "1" suffix.
 * Add alternatives for all of the original names such that the previous
   original names keep working.
 * I have uploaded borgbackup2 to experimental (stuck in NEW) such that
   all of its command line utilities and manual pages have a "2" suffix.
 * I want to add update-alternatives to borgbackup2 with a *lower*
   priority than the one of borgbackup 1.x.

I note that these tools are not fully compatible. For instance, "borg
init" becomes "borg rcreate" borg "list" is split into "borg list" and
"borg rlist". Also --glob-archives becomes --match-archives and further
differences. Yet, I think that alternatives are a good compromise.

People installing just one borgbackup package will have it use standard
names. People upgrading from bullseye to bookworm will have borg be
borg 1.x regardless of whether borgbackup2 is installed as part of the
upgrade (due to the lower priority). Therefore prior usage of borg will
continue to work. Machines providing "borg serve" are able to provide
both borg 1.x and borg 2.x repositories due to both borg versions being
coinstallable.

In trixie, I want to either remove borg 1.x or lower its priority below
the priority of borg 2.x.

Release notes shall be extended to advise people to upgrade their borg
repositories after the upgrade and remove the borgbackup package.

Do you agree?

If you happen to not care much, I offer taking over maintenance of
borgbackup as part of the Freexian Packaging Team. Please let me know if
you favour that solution.

A quick reply is appreciated due to the imminent freeze.

Helmut for the Freexian Packaging Team
diff --minimal -Nru borgbackup-1.2.3/debian/borgbackup.alternatives 
borgbackup-1.2.3/debian/borgbackup.alternatives
--- borgbackup-1.2.3/debian/borgbackup.alternatives 1970-01-01 
01:00:00.0 +0100
+++ borgbackup-1.2.3/debian/borgbackup.alternatives 2023-01-16 
17:23:10.0 +0100
@@ -0,0 +1,43 @@
+Name: borg
+Link: /usr/bin/borg
+Alternative: /usr/bin/borg1
+Priority: 50
+Dependents:
+ /usr/bin/borgbackup borgbackup /usr/bin/borgbackup1
+ /usr/bin/borgfs borgfs /usr/bin/borgfs1
+ /usr/share/man/man1/borg-benchmark-crud.1.gz borg-benchmark-crud.1.gz 
/usr/share/man/man1/borg1-benchmark-crud.1.gz
+ /usr/share/man/man1/borg-benchmark.1.gz borg-benchmark.1.gz 
/usr/share/man/man1/borg1-benchmark.1.gz
+ /usr/share/man/man1/borg-break-lock.1.gz borg-break-lock.1.gz 
/usr/share/man/man1/borg1-break-lock.1.gz
+ /usr/share/man/man1/borg-change-passphrase.1.gz borg-change-passphrase.1.gz 
/usr/share/man/man1/borg1-change-passphrase.1.gz
+ /usr/share/man/man1/borg-check.1.gz borg-check.1.gz 
/usr/share/man/man1/borg1-check.1.gz
+ /usr/share/man/man1/borg-common.1.gz borg-common.1.gz 
/usr/share/man/man1/borg1-common.1.gz
+ /usr/share/man/man1/borg-compact.1.gz borg-compact.1.gz 
/usr/share/man/man1/borg1-compact.1.gz
+ /usr/share/man/man1/borg-compression.1.gz borg-compression.1.gz 
/usr/share/man/man1/borg1-compression.1.gz
+ /usr/share/man/man1/borg-config.1.gz borg-config.1.gz 
/usr/share/man/man1/borg1-config.1.gz
+ /usr/share/man/man1/borg-create.1.gz borg-create.1.gz 
/usr/share/man/man1/borg1-create.1.gz
+ /usr/share/man/man1/borg-delete.1.gz borg-delete.1.gz 
/usr/share/man/man1/borg1-delete.1.gz
+ /usr/share/man/man1/borg-diff.1.gz borg-diff.1.gz 
/usr/share/man/man1/borg1-diff.1.gz
+ /usr/share/man/man1/borg-export-tar.1.gz borg-export-tar.1.gz 
/usr/share/man/man1/borg1-export-tar.1.gz
+ /usr/share/man/man1/borg-extract.1.gz borg-extract.1.gz 
/usr/share/man/man1/borg1-extract.1.gz
+ /usr/share/man/man1/borg-import-tar.1.gz borg-import-tar.1.gz 
/usr/share/man/man1/borg1-import-tar.1.gz
+ /usr/share/man/man1/borg-info.1.gz borg-info.1.gz 
/usr/share/man/man1/borg1-info.1.gz
+ /usr/share/man/man1/borg-init.1.gz borg-init.1.gz 
/usr/share/man/man1/borg1-init.1.gz
+ /usr/share/man/man1/borg-key-change-passphrase.1.gz 
borg-key-change-passphrase.1.gz 
/usr/share/man/man1/borg1-key-change-passphrase.1.gz
+ /usr/share/man/man1/borg-key-export.1.gz borg-key-export.1.gz 
/usr/share/man/man1/borg1-key-export.1.gz
+ /usr/share/man/man1/borg-key-import.1.gz borg-key-import.1.gz 
/usr/share/man/man1/borg1-key-import.1.gz
+ /usr/share/man/man1/borg-key-migrate-to-repokey.1.gz 
borg-key-migrate-to-repokey.1.gz 
/usr/share/man/man1/borg1-key-migrate-to-repokey.1.gz
+ /usr/share/man/man1/borg-key.1.gz borg-key.1.gz 
/usr/share/man/man1/borg1-key.1.gz
+ /usr/share/man/man1/borg-list.1.gz borg-list.1.gz 
/usr/share/man/man1/borg1-list.1.gz
+ /usr/share/man/man1/borg-mount.1.gz borg-mount.1.gz 
/usr/share/man/man1/borg1-mount.1.gz
+ /usr/share/man/man1/borg-patterns.1.gz borg-patterns.1.gz

Bug#1011049: freetype: breaks architecture bootstrap by depending on librsvg2-dev

Hi,

On Tue, Jan 17, 2023 at 10:43:10PM +1100, Hugh McMaster wrote:
> freetype2-demos only contains programs used to test and showcase the
> FreeType 2 font engine. They aren't general-purpose utilities.
> 
> Would this mean the binary package qualifies for the noinsttest build profile?

Like Simon, I also think that freetype2-demos is a corner case where it
is not clear whether noinsttest is a reasonable profile. Simon certainly
made a good argument in favour. My personal judgement thus far was that
it is on the other side of the border, but clearly this is a trade-off
and I may be wrong. Beyond what was argued, I think that we typically do
not expect any reverse dependencies on packages tagged 
(other than autopkgtests). In this case, we have one reverse dependency
open-font-design-toolkit and one reverse recommends
check-all-the-things. That still makes it a corner case from my point of
view.

I'm fine with both noinsttest and a package-specific profile and leave
it up to you. There is no "wrong" outcome to this.

A minor argument in favour of noinsttest is that rebootstrap enables
this profile for all packages, so freetype need no special handling
here.

Helmut

Bug#1029086: rblcheck FTCBFS: uses the build architecture compiler as a make default