Bug#1033442: unblock: golang-go.opencensus/0.24.0-1

[Anthony Fok]

On Fri, Mar 24, 2023 at 3:33 PM Anthony Fok  wrote:

> ratt finds 89 packages with direct or indirect dependency on
> golang-go.opencensus and is able to build all of them with
> with golang-go.opencensus/0.24.0-1 smoothly with no hiccup.

Clarification: Out of the 89 packages, 4 failed but not due to
golang-go.opencensus:

  FAILED: cadvisor (see buildlogs/cadvisor_0.38.7+ds1-2)
  FAILED: golang-github-prometheus-common
(see buildlogs/golang-github-prometheus-common_0.15.0-2)
  FAILED: nomad (see buildlogs/nomad_0.12.10+dfsg1-3)
  FAILED: nomad-driver-podman (see buildlogs/nomad-driver-podman_0.1.0-2)

3 of them, cadvisor, nomad and nomad-driver-podman are currently FTBFS
in the archive and are not in "testing".

As for golang-github-prometheus-common_0.15.0-2, ratt picked the wrong
version in stable (bullseye) instead of 0.39.0-2 in sid.
Apparently, ratt's dependency dose-ceve does not handle the multiple
"same Package, different Version" entries in the source list
and simply picks the first one:

  $ grep -A2 '^Package: golang-github-prometheus-common' \
/var/lib/apt/lists/deb.debian.org_debian_dists_sid_main_source_Sources
  Package: golang-github-prometheus-common
  Binary: golang-github-prometheus-common-dev
  Version: 0.15.0-2
  --
  Package: golang-github-prometheus-common
  Binary: golang-github-prometheus-common-dev
  Version: 0.39.0-2

So, while this erroneous sbuild command fails:
  sbuild --arch-all --dist=unstable --nolog \
  golang-github-prometheus-common_0.15.0-2 \
  --extra-package=../golang-go.opencensus-dev_0.24.0-1_all.deb

the correct sbuild command pointing to the correct version in sid passes:
  sbuild --arch-all --dist=unstable --nolog \
  golang-github-prometheus-common_0.39.0-2 \
  --extra-package=../golang-go.opencensus-dev_0.24.0-1_all.deb

So, yes, it is perfectly safe to upgrade golang-go.opencensus 0.23.0-4
to 0.24.0-1.

Many thanks!

Cheers,
Anthony Fok

Bug#1032091: py7zr: CVE-2022-44900

[yokota]

Hello, py7zr maintainer.

I was pushed some commits for Debain salsa repository to fix CVE-2022-44900 .
https://salsa.debian.org/python-team/packages/py7zr/-/merge_requests/2

--
YOKOTA

Bug#1030200: linux-image-6.1.0-3-amd64: "Loading of module with unavailable key is rejected", /proc/keys says key is loaded; system unbootable

[наб]

If anyone has a faintest idea so as to what the problem may be, please help;
the only vaguely-related config change is
INTEGRITY_MACHINE_KEYRING going from unset to y,
but that shouldn't(! not that it doesn't, the code is an enigma to me,
 but as i understand it and as i read the kconfig, it shouldn't)
change anything if you aren't a MOK user, and I'm not.

Please advise.

наб


signature.asc
Description: PGP signature

Bug#837741: Pithos important bugs

[gary]

How can a nine year old bug be considered important?
Has Pithos been abandoned?

It's the only GUI for accessing pandora and has recently become a 
popular tool for linux mobile phones. The author has made many 
improvements toward this end and Pithos is of great value to the future 
of mobile debian. It should be updated to the newest source and moved to 
bookworm.


Thanks,
Gary

Bug#1030200: linux-image-6.1.0-3-amd64: "Loading of module with unavailable key is rejected", /proc/keys says key is loaded; system unbootable

[наб]

Control: found -1 6.1.20-1

Updated to linux-image-6.1.0-7-amd64 (6.1.20-1);
still happens.

наб
Mar 25 01:38:54 babtop kernel: microcode: microcode updated early to revision 
0xf4, date = 2022-07-31
Mar 25 01:38:54 babtop kernel: Linux version 6.1.0-7-amd64 
(debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU 
Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1 (2023-03-19)
Mar 25 01:38:54 babtop kernel: Command line: 
initrd=\klapki\731b69f0dac147efadfed92f12712736\6.1.0-7-amd64\initrd.img-6.1.0-7-amd64
 root=zfs:AUTO fbcon=rotate:3 intel_iommu=on zfs.zfs_arc_max=12884901888 quiet 
module.sig_enforce=1
Mar 25 01:38:54 babtop kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 
floating point registers'
Mar 25 01:38:54 babtop kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE 
registers'
Mar 25 01:38:54 babtop kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX 
registers'
Mar 25 01:38:54 babtop kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX 
bounds registers'
Mar 25 01:38:54 babtop kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX 
CSR'
Mar 25 01:38:54 babtop kernel: x86/fpu: xstate_offset[2]:  576, 
xstate_sizes[2]:  256
Mar 25 01:38:54 babtop kernel: x86/fpu: xstate_offset[3]:  832, 
xstate_sizes[3]:   64
Mar 25 01:38:54 babtop kernel: x86/fpu: xstate_offset[4]:  896, 
xstate_sizes[4]:   64
Mar 25 01:38:54 babtop kernel: x86/fpu: Enabled xstate features 0x1f, context 
size is 960 bytes, using 'compacted' format.
Mar 25 01:38:54 babtop kernel: signal: max sigframe size: 2032
Mar 25 01:38:54 babtop kernel: BIOS-provided physical RAM map:
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x-0x00057fff] usable
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x00058000-0x00058fff] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x00059000-0x0009dfff] usable
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x0009e000-0x000f] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x0010-0x3fff] usable
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x4000-0x403f] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x4040-0x84ff0fff] usable
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x84ff1000-0x84ff1fff] ACPI NVS
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x84ff2000-0x84ff2fff] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x84ff3000-0x8bc66fff] usable
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x8bc67000-0x8c8b5fff] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x8c8b6000-0x8c90bfff] ACPI data
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x8c90c000-0x8c96bfff] ACPI NVS
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x8c96c000-0x8cffefff] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x8cfff000-0x8cff] usable
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x8d00-0x8fff] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0xe000-0xefff] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0xfe00-0xfe010fff] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0xfec0-0xfec00fff] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0xfed0-0xfed00fff] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0xfee0-0xfee00fff] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0xff00-0x] reserved
Mar 25 01:38:54 babtop kernel: BIOS-e820: [mem 
0x0001-0x00046eff] usable
Mar 25 01:38:54 babtop kernel: NX (Execute Disable) protection: active
Mar 25 01:38:54 babtop kernel: efi: EFI v2.70 by American Megatrends
Mar 25 01:38:54 babtop kernel: efi: ACPI 2.0=0x8c8c7000 ACPI=0x8c8c7000 
SMBIOS=0x8ce15000 SMBIOS 3.0=0x8ce14000 MEMATTR=0x88601418 ESRT=0x8a712c98 
INITRD=0x8510df18 RNG=0x8c8c6018 
Mar 25 01:38:54 babtop kernel: random: crng init done
Mar 25 01:38:54 babtop kernel: Kernel is locked down from EFI Secure Boot; see 
man kernel_lockdown.7
Mar 25 01:38:54 babtop kernel: secureboot: Secure boot enabled
Mar 25 01:38:54 babtop kernel: SMBIOS 3.0.0 present.
Mar 25 01:38:54 babtop kernel: DMI: ONE-NETBOOK TECHNOLOGY CO., LTD. One-Mix3 
Pro/One-Mix3 Pro, BIOS 5.12 12/10/2019
Mar 25 01:38:54 babtop kernel: tsc: Detected 1300.000 MHz processor
Mar 25 01:38:54 babtop kernel: tsc: Detected 1299.996 MHz TSC
Mar 25 01:38:54 babtop kernel: e820: update [mem 0x-0x0fff] usable 
==> reserved
Mar 25 01:38:54 babtop kernel: e820: remove [mem 0x000a-0x000f] usable
Mar 25 01:38:54 babtop kernel: last_pfn = 0x46f000 max_arch_pfn = 0x4
Mar 25 01:38:54 babtop kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB 
 WP 

Bug#1033422: base-passwd: missing Build-Depends docbook

[Colin Watson]

Control: severity -1 normal

On Fri, Mar 24, 2023 at 07:30:26PM +, henrynmail-deb...@yahoo.com wrote:
> Package: base-passwd
> Version: 3.6.1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> Usertags: rebootstrap
> 
> Dear Maintainer,
> 
> build in a minimal build environmet fails for docbook2html.
> 
> # apt remove docbook && apt autoremove
> # apt build-dep base-passwd
> ... some dependency installed ...
> # dpkg-buildpackage -j1 -B "-Pnocheck noinsttest noudeb" -uc -us

It builds fine for me in sbuild with an unstable chroot, which
definitely doesn't have docbook installed; and similarly, when I follow
your reproduction recipe in a clean chroot, it still builds fine.

In fact, your build environment isn't minimal.  Here's the true
reproduction recipe:

  apt install docbook-xml
  apt build-dep base-passwd
  dpkg-buildpackage [etc.]

base-passwd Build-Depends: docbook-utils Depends: docbook-dsssl Depends:
docbook (>= 3.1) | docbook-xml.  This means that having docbook-xml
already installed causes apt not to install docbook.

The RC policy (https://release.debian.org/testing/rc_policy.txt) is that
packages must autobuild, and autobuilders don't randomly have
non-build-essential packages such as docbook-xml installed, so this is
not release-critical.  It seems reasonable to add an explicit
Build-Depends to fix it, but I don't think I need to trouble the release
team requesting a freeze exception to get it into bookworm; it can wait
until the next release.  In the meantime, I recommend that you make your
minimal build environment truly minimal - it shouldn't have
non-build-essential packages installed.

Thanks,

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#1033446: [INTL:ro] Romanian debconf templates translation of quota

[Remus-Gabriel Chelu]

Package: quota
Version: N/A
Severity: wishlist
Tags: l10n, patch

Dear Maintainer,

Please find attached the Romanian translation of the «quota» file.

Thanks,
Remus-Gabriel

quota_debconf_ro.po
Description: Binary data

Bug#1032642: iproute2: ip tunnel change ip6gre to gre crashes with stack smash

[Bernhard Übelacker]

Dear Maintainer,
I tried to find out where exactly the stack smashing takes place.
And found the ioctl SIOCCHGTUNNEL did write more than the 52 bytes
allocated in variable old_p, by that overwriting the stack canary.

Kind regards,
Bernhard


(gdb)
0x5557589f  62  {
1: x/i $pc
=> 0x5557589f :  mov%fs:0x28,%rax
(gdb)
0x555758a8  62  {
1: x/i $pc
=> 0x555758a8 :  mov%rax,0x68(%rsp)
(gdb) print/x $rax
$1 = 0xbf9b77d893accd00
(gdb) print/x $rsp + 0x68
$2 = 0x7fffea28


(gdb)
0x77e575f5  120 in ../sysdeps/unix/syscall-template.S
1: x/i $pc
=> 0x77e575f5 :syscall
2: /x *(uint64_t*)0x7fffea28 = 0xbf9b77d893accd00
(gdb) bt
#0  0x77e575f5 in ioctl () at ../sysdeps/unix/syscall-template.S:120
#1  0x55578230 in tnl_get_ioctl (basedev=0x7fffee8f "gre1", 
p=) at tunnel.c:77
#2  0x55576243 in parse_args (argc=9, argv=0x7fffec50, cmd=35315, 
p=0x7fffea70) at iptunnel.c:181
#3  0x555762fb in do_add (cmd=35315, argc=, argv=) at iptunnel.c:260
#4  0x5556258b in do_cmd (argv0=0x7fffee81 "tunnel", argc=11, 
argv=0x7fffec40) at ip.c:133
#5  0x55561fc2 in main (argc=12, argv=0x7fffec38) at ip.c:344
(gdb) stepi
0x77e575f7  120 in ../sysdeps/unix/syscall-template.S
1: x/i $pc
=> 0x77e575f7 :cmp$0xf001,%rax
2: /x *(uint64_t*)0x7fffea28 = 0x200

(gdb) print _p
$7 = (struct ip_tunnel_parm *) 0x7fffe9f0
(gdb) print sizeof(old_p)
$8 = 52
(gdb) print/x 0x7fffe9f0 + 52
$9 = 0x7fffea24

(gdb) list iptunnel.c:181
178 if (cmd == SIOCCHGTUNNEL && count == 0) {
179 struct ip_tunnel_parm old_p = {};
180
181 if (tnl_get_ioctl(*argv, _p))
182 return -1;

Bug#1033445: [INTL:ro] Romanian debconf templates translation of python-certbot

[Remus-Gabriel Chelu]

Package: python-certbot
Version: N/A
Severity: wishlist
Tags: l10n, patch

Dear Maintainer,

Please find attached the Romanian translation of the «python-certbot» file.

Thanks,
Remus-Gabriel

python-certbot_debconf_ro.po
Description: Binary data

Bug#1033444: [INTL:ro] Romanian debconf templates translation of pure-ftpd

[Remus-Gabriel Chelu]

Package: pure-ftpd
Version: N/A
Severity: wishlist
Tags: l10n, patch

Dear Maintainer,

Please find attached the Romanian translation of the «pure-ftpd» file.

Thanks,
Remus-Gabriel

pure-ftpd_debconf_ro.po
Description: Binary data

Bug#1033006: unblock: openvpn/2.6.1-1 (preapproval)

[Bernhard Schmidt]

On 15/03/23 04:57 PM, Bernhard Schmidt wrote:

Hi,

> The upcoming DCO change will involve a new version of src:openvpn and a new 
> version
> of src:openvpn-dco-dkms. The list of changes on the kernel side is already 
> visible
> on https://github.com/OpenVPN/ovpn-dco/commits/master .
> 
> In the past we managed to break DCO on above mentioned really heavily loaded
> OpenVPN server within a few hours. The new version is a major overhaul and 
> more
> in-line with code upstreamable in Linux, and did survive torture tests.
> 
> I know this is kind of late, but I think it would be better to include it as 
> well
> as soon as it is released because
> 
> - we cannot support the old deprecated module
> - openvpn uses DCO (of the right version) automatically and will transparently
>   fall-back to non-DCO mode if the module is not found (or the wrong version)
> - it has not been in Bullseye previously, so if we see that DCO is too 
> unstable
>   with the new version we can just drop it before the release

So, the release of 2.6.2 with the new DCO module has been done
yesterday, fixing a number of bugs already present in 2.6.0.

https://github.com/OpenVPN/openvpn/blob/release/2.6/Changes.rst

---
New control packets flow for data channel offloading on Linux. 2.6.2+
changes the way OpenVPN control packets are handled on Linux when DCO is
active, fixing the lockups observed with 2.6.0/2.6.1 under high client
connect/disconnect activity. This is an INCOMPATIBLE change and
therefore an ovpn-dco kernel module older than v0.2.20230323 (commit ID
726fdfe0fa21) will not work anymore and must be upgraded. The kernel
module was renamed to "ovpn-dco-v2.ko" in order to highlight this change
and ensure that users and userspace software could easily understand
which version is loaded. Attempting to use the old ovpn-dco with 2.6.2+
will lead to disabling DCO at runtime.
---

So I need some guidance from the release team how to proceed. I can
think of

- abandoning all of this, leading to a bookworm release using a buggy
  OpenVPN version with a DCO kernel interface that noone else uses
- update experimental to 2.6.2 and the new DCO module, then ask for a
  approval for upload to unstable (2.6.1+2.6.2) in one go
- upload 2.6.2 and the new DCO module to unstable right away
- upload 2.6.1 from experimental to unstable, then stage 2.6.2 and the
  new DCO in experimental for the second review round

I would prefer the last option.

Bernhard

Bug#1033443: [INTL:ro] Romanian debconf templates translation of privoxy

[Remus-Gabriel Chelu]

Package: privoxy
Version: N/A
Severity: wishlist
Tags: l10n, patch

Dear Maintainer,

Please find attached the Romanian translation of the «privoxy» file.

Thanks,
Remus-Gabriel

privoxy_debconf_ro.po
Description: Binary data

Bug#913431: Debian Installer Bullseye RC 2 release

[Vincent Danjean]

Le 23/03/2023 à 12:01, Vincent Danjean a écrit :

Le 23/03/2023 à 11:41, Vincent Danjean a écrit :

   Hi,

Le 23/03/2023 à 10:06, Emanuele Rocca a écrit :

There is (now) a function in partman-base called valid_human [1] which
checks if the partition size specified by the user is valid. Probably
when you first wrote the patch this wasn't the case.

That function needs to be modified as well to accept GiB and friends.


  Here is a new patch. There are several improvments:
- when using power-of-ten units, all decimals are taken into account
  (not just the 4 first ones)
- human2longint was concatenating the 5 first arguments. Now it
  concatenates all its arguments (not sure about this part, this is
  a two-lines modification that can easily be reverted
- bigger decimal number are handled (in fact, there are no size limits)
- power-of-two units are accepted and handled
- Peta and Exa units are added

  This patch is using both 'expr' (from busybox) and bash arithmetic
that both are limited to 2^64 (signed) integers (even on 32-bits
platforms, I checked on i386). Both were already used previously.

  To be relatively sure of my code, I wrote a series of test.
It is in the tar.gz file. Just unpack it and run 'make' in it.
For each check, it compares:
- the new implementation and a (local) implementation based on
  'bc' that uses no-size-limit integer operations
  It prints 'OK' if both are the same and else NACK
  (in practice, there are no NACKs)
- if previously OK, it compares to the old implementation.
  - 'OK:' means that both (old and new) implementation returns the
same thing
  - 'OK+': means that they differ.
If there is no 'previously' at the end of the line,
  it means that the old implementation was not handling this case
  (all power-of-two units and the new Peta and Exa prefix)
else
  it means that the old implementation was returning another value
  (seen just after the "previouly: " text)
  Here, you find better precision (more decimals taken into account)
  or wrong results (negative by overflow, etc.)
All these tests are run within the busybox shell and with the busybox
tools added in front of the PATH.

However, I did not rebuild all the installer packages to generate a
new installer and test it in real conditions.

  I hope the patch can be reviewed and applied for the next release.

  Regards
Vincent

diff --git a/lib/base.sh b/lib/base.sh
index d38e101e..492732bf 100644
--- a/lib/base.sh
+++ b/lib/base.sh
@@ -313,9 +313,115 @@ longint2human () {
 	printf "%i%s%i %s\n" $int $deci $frac $suffix
 }
 
+longmult() {
+	local a="$1" # no size limit
+	local b="$2" # <= 2^30
+
+	local carry=0
+	local endres=""
+	local partres
+	local enda
+
+	while [ "${#a}" -gt 6 ]; do
+		enda="${a:$((${#a} - 6))}"
+		a="${a%$enda}"
+		partres="$(expr "$enda" '*' "$b" + "$carry")"
+		if [ "${#partres}" -gt 6 ]; then
+			carry="${partres:0:$((${#partres} - 6))}"
+			endres="${partres#$carry}$endres"
+		else
+			partres="00$partres"
+			carry=0
+			endres="${partres:$((${#partres} - 6))}$endres"
+		fi
+	done
+	partres="$(expr "$a" '*' "$b" + "$carry")"
+	echo "$partres$endres"
+}
+
+longadd() {
+	local a="$1" # no size limit
+	local b="$2" # <= 2^60
+
+	local carry="$b"
+	local endres=""
+	local partres
+	local enda
+
+	while [ "${#a}" -gt 15 ]; do
+		enda="${a:$((${#a} - 15))}"
+		a="${a%$enda}"
+		partres="$(expr "$enda" + "$carry")"
+		if [ "${#partres}" -gt 15 ]; then
+			carry="${partres:0:$((${#partres} - 15))}"
+			endres="${partres#$carry}$endres"
+		else
+			partres="000$partres"
+			echo "${a}${partres:$((${#partres} - 15))}$endres"
+			return
+		fi
+	done 
+	partres="$(expr "$a" + "$carry")"
+	echo "$partres$endres"
+}
+
+human2longint_binary_unit() {
+	local int="$1"
+	local frac="$2"
+	local powbase="$3" # 1 <= powbase <= 6
+	# must return "$int.$frac * 1024^$powbase"
+	# contraints :
+	# - no floating point operation
+	# - no computed values above 2^63-1
+	# - expr has no exponentiation
+	# - bash arithmetics consider that 0-leading numbers are octal
+
+	# max of useful decimals when converting: powbase*10
+	# next ones, when multipled by 1024^powbase, would be <1
+	# so no need to take into account to many decimals
+	frac="${frac:0:$((powbase * 10 ))}"
+	local longint="${int}${frac}"
+	longint="${longint:$(expr "$longint" : '0*' || true)}" # remove leading 0
+	[ "$longint" ] || {
+		echo 0
+		return
+	}
+	while [ "$powbase" -gt 3 ]; do
+		longint="$(longmult "$longint" "$((1024**3))")"
+		powbase=$(( $powbase - 3 ))
+	done
+	longint="$(longmult "$longint" "$((1024**$powbase))")"
+
+	if [ -z "$frac" ]; then
+		# no fractional part, just return the result
+		echo "$longint"
+		return
+	fi
+	# non-null fractional part.
+	# longint must be divided by 10^length(frac)
+	local posfrac="$(( ${#longint} - ${#frac} ))"
+	if [ $posfrac -le 0 ]; then
+		echo 0
+		return
+	fi
+	local res="${longint:0:$posfrac}"
+	# roundup if the next decimal is >= 5
+	

Bug#910015: Re: User is in the plugdev group

[Vincent Adolph]

Date: Tue, 6 Nov 2018 05:32:45 +0800
>From:  adolphvincen...@gmail.com

Bug#1033442: unblock: golang-go.opencensus/0.24.0-1

[Anthony Fok]

On Fri, Mar 24, 2023 at 3:33 PM Anthony Fok  wrote:
> [ Checklist ]
>   [x] all changes are documented in the d/changelog
>   [x] I reviewed all changes and I approve them
>   [x] attach debdiff against the package in testing

Sorry, I forgot to actually attach the debdiff file.  Attached in this
follow-up message.  :-)

Cheers,
Anthony Fok
diff -Nru golang-go.opencensus-0.23.0/debian/changelog golang-go.opencensus-0.24.0/debian/changelog
--- golang-go.opencensus-0.23.0/debian/changelog	2023-01-04 15:26:48.0 -0700
+++ golang-go.opencensus-0.24.0/debian/changelog	2023-03-09 02:33:15.0 -0700
@@ -1,3 +1,14 @@
+golang-go.opencensus (0.24.0-1) unstable; urgency=medium
+
+  * New upstream version 0.24.0
+  * Reorder fields in debian/control and debian/copyright
+  * Bump versioned dependencies as per go.mod:
+- golang-github-google-go-cmp-dev (>= 0.5.3)
+- golang-github-stretchr-testify-dev (>= 1.8.1)
+- golang-google-grpc-dev (>= 1.33.2)
+
+ -- Anthony Fok   Thu, 09 Mar 2023 02:33:15 -0700
+
 golang-go.opencensus (0.23.0-4) unstable; urgency=medium
 
   * Team upload
diff -Nru golang-go.opencensus-0.23.0/debian/control golang-go.opencensus-0.24.0/debian/control
--- golang-go.opencensus-0.23.0/debian/control	2023-01-02 09:30:05.0 -0700
+++ golang-go.opencensus-0.24.0/debian/control	2023-03-09 02:32:16.0 -0700
@@ -1,36 +1,36 @@
 Source: golang-go.opencensus
+Section: golang
+Priority: optional
 Maintainer: Debian Go Packaging Team 
 Uploaders: Stephen Gelman ,
Anthony Fok 
-Section: golang
-Testsuite: autopkgtest-pkg-go
-Priority: optional
+Rules-Requires-Root: no
 Build-Depends: debhelper-compat (= 13),
dh-golang,
golang-any,
-   golang-github-google-go-cmp-dev (>= 0.3.0),
+   golang-github-google-go-cmp-dev (>= 0.5.3),
golang-github-golang-groupcache-dev,
-   golang-github-stretchr-testify-dev (>= 1.4.1),
+   golang-github-stretchr-testify-dev (>= 1.8.1),
golang-golang-x-net-dev,
-   golang-google-grpc-dev (>= 1.20.1),
+   golang-google-grpc-dev (>= 1.33.2),
golang-github-golang-protobuf-1-3-dev
+Testsuite: autopkgtest-pkg-go
 Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-go.opencensus
 Vcs-Git: https://salsa.debian.org/go-team/packages/golang-go.opencensus.git
 Homepage: https://github.com/census-instrumentation/opencensus-go
-Rules-Requires-Root: no
 XS-Go-Import-Path: go.opencensus.io
 
 Package: golang-go.opencensus-dev
 Architecture: all
 Multi-Arch: foreign
-Depends: ${misc:Depends},
- golang-github-google-go-cmp-dev (>= 0.3.0),
+Depends: golang-github-google-go-cmp-dev (>= 0.5.3),
  golang-github-golang-groupcache-dev,
- golang-github-stretchr-testify-dev (>= 1.4.1),
+ golang-github-stretchr-testify-dev (>= 1.8.1),
  golang-golang-x-net-dev,
- golang-google-grpc-dev (>= 1.20.1),
- golang-github-golang-protobuf-1-3-dev | golang-github-golang-protobuf-1-5-dev
+ golang-google-grpc-dev (>= 1.33.2),
+ golang-github-golang-protobuf-1-3-dev | golang-github-golang-protobuf-1-5-dev,
+ ${misc:Depends}
 Description: Stats collection and distributed tracing framework
  OpenCensus Go is a Go implementation of OpenCensus, a toolkit for
  collecting application performance and behavior monitoring data.
diff -Nru golang-go.opencensus-0.23.0/debian/copyright golang-go.opencensus-0.24.0/debian/copyright
--- golang-go.opencensus-0.23.0/debian/copyright	2022-12-31 17:30:47.0 -0700
+++ golang-go.opencensus-0.24.0/debian/copyright	2023-03-09 02:30:39.0 -0700
@@ -1,9 +1,9 @@
 Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
-Upstream-Name: go.opencensus.io
 Source: https://github.com/census-instrumentation/opencensus-go
+Upstream-Name: go.opencensus.io
 
 Files: *
-Copyright: 2017-2019 OpenCensus
+Copyright: 2017-2022 OpenCensus
 License: Apache-2.0
 
 Files: debian/*
@@ -23,6 +23,6 @@
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
- .
+Comment:
  On Debian systems, the complete text of the Apache version 2.0 license
  can be found in "/usr/share/common-licenses/Apache-2.0".
diff -Nru golang-go.opencensus-0.23.0/examples/derived_gauges/derived_gauge.go golang-go.opencensus-0.24.0/examples/derived_gauges/derived_gauge.go
--- golang-go.opencensus-0.23.0/examples/derived_gauges/derived_gauge.go	2021-02-12 09:50:36.0 -0700
+++ golang-go.opencensus-0.24.0/examples/derived_gauges/derived_gauge.go	2022-11-03 14:13:50.0 -0600
@@ -20,7 +20,7 @@
 // items. Consumer randomly consumes 1-5 items in each attempt. It then sleeps randomly
 // between 1-10 seconds before the next attempt. Two metrics collected to monitor the queue.
 

Bug#1033442: unblock: golang-go.opencensus/0.24.0-1

[Anthony Fok]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: golang-go.opencen...@packages.debian.org, 
debian...@lists.debian.org, f...@debian.org
Control: affects -1 + src:golang-go.opencensus

Please unblock package golang-go.opencensus/0.24.0-1

packer/1.6.6+ds1-7 in testing has an RC bug (#1032525) and is scheduled
for autoremoval on 2023-04-06.  The fix was uploaded by its maintainer
Shengjing Zhu in packer/1.6.6+ds2-1 on 2023-03-13, but it is currently
prevented from migrating to testing to due to being blocked by its
indirect dependency on golang-go.opencensus.

My apologies for my untimely upload of golang-go.opencensus/0.24.0-1
on 2023-03-09, assuming that it would enter testing automatically
after 20 days, not knowing that it is a key package that would require
a manual unblock.

Risks of upgrading from 0.23.0 to 0.24.0 is minimal, as the changes
consist of minor bug fixes with a small addition to the API.
ratt finds 89 packages with direct or indirect dependency on
golang-go.opencensus and is able to build all of them with
with golang-go.opencensus/0.24.0-1 smoothly with no hiccup.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock golang-go.opencensus/0.24.0-1

Thanks for your help!

Cheers,

Anthony Fok

Bug#1033438: error in ascii(7)

[Helge Kreutzmann]

tags 1033438 +pending
thanks

On Fri, Mar 24, 2023 at 08:57:19PM +0100, VA wrote:
> Package: manpages-fr
> Version: 4.18.0-1
> 
> ascii(7) contains an error for character 2A (in hex), it indicates "–"
> (U+2013) instead of "+" (U+002A).
> The error can be seen here too:
> https://manpages.debian.org/unstable/manpages-fr/ascii.7.fr.html

Thanks. Fixed in git. Will be part of next upstream release.

Greetings

   Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1032940: 1,5 gig disk not accepted by installer

[Holger Wansing]

Control: tags -1 + pending


Holger Wansing  wrote (Sun, 19 Mar 2023 11:42:20 +0100):
> > But as you say, 2G is not enough these days (a test confirmed that here).
> > 
> > So, we should set this to 4G IMHO.
> > (A test installation with 3G disk space was successful here, when you do
> > not waste to much space for swap, but let's not be that nitpicking.)
> 
> Objections? Comments?

Just pushed to git.


Holger


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

Bug#1033301: linux: arm64 kernel size increased from 31 to 39 MB, causing u-boot-rpi to fail

[Vagrant Cascadian]

Adding u-boot maintainers for rpi (Matthias Brugger, Peter Robinson)
platforms and u-boot list to CC.

On 2023-03-22, Salvatore Bonaccorso wrote:
> Thanks for tracking this down. I would like to loop in Masahiro and
> upstream to see if something can/should be done on upstream side.
>
> Masahiro, in short, upstream change 994b7ac1697b ("arm64: remove
> special treatment for the link order of head.o") (which got backported
> as well to 6.1.14) caused the vmlinuz size to icrease significantly,
> causing boot failures on Raspberry Pi 3 Model B Plus with u-boot
> parameters previously working. Full quoting the Debian report below

In general it would be nice to not have the kernel grow nearly 25% in
size from a single commit; was that an expected outcome from the above
upstream change? Was the "special treament" originally done to keep the
kernel size down?

As for u-boot, It seems u-boot might need to update the various load
addresses for the kernel, device tree and ramdisk at some point
regardless of weather this particular issue gets fixed in the kernel, as
the kernel will likely continue to grow a bit over time...

Aurelien Jarno included a patch referenced below which bumps the
tolerances in u-boot from 36MB to 42MB.


> On Tue, Mar 21, 2023 at 11:11:13PM +0100, Aurelien Jarno wrote:
>> Following the upgrade of the kernel from 6.1.12-1 to 6.1.15-1 on a
>> Raspberry Pi 3 Model B Plus, u-boot (from the u-boot-rpi package) failed
>> to boot with:
>> 
>> | 40175552 bytes read in 1695 ms (23 MiB/s)
>> | 43794863 bytes read in 1817 ms (23 MiB/s)
>> | Moving Image from 0x8 to 0x20, end=299
>> | ERROR: RD image overlaps OS image (OS=0x20..0x299)
>> 
>> I tracked the issue to a significant increase of the kernel size between
>> version 6.1.12-1 and 6.15-1:
>> 
>> | 31492   /boot/vmlinuz-6.1.0-5-arm64
>> | 39236   /boot/vmlinuz-6.1.0-6-arm64
>> 
>> This is more than the 36MB that is allowed by u-boot with the default
>> load addresses. A workaround is to shift the load addresses at the
>> u-boot level as in the attached patch.
>> 
>> I have tracked issue on the upstream kernel side to the following commit
>> on the stable tree:
>> 
>> | commit 3e3e4d234d46e48480a7c7c35399fa811182e8ef
>> | Author: Masahiro Yamada 
>> | Date:   Thu Oct 13 08:35:00 2022 +0900
>> | 
>> | arm64: remove special treatment for the link order of head.o
>> | 
>> | commit 994b7ac1697b4581b7726d2ac64321e3c840229b upstream.
>> | 
>> | In the previous discussion (see the Link tag), Ard pointed out that
>> | arm/arm64/kernel/head.o does not need any special treatment - the only
>> | piece that must appear right at the start of the binary image is the
>> | image header which is emitted into .head.text.
>> | 
>> | The linker script does the right thing to do. The build system does
>> | not need to manipulate the link order of head.o.
>> | 
>> | Link: 
>> https://lore.kernel.org/lkml/CAMj1kXH77Ja8bSsq2Qj8Ck9iSZKw=1F8Uy-uAWGVDm4-CG=e...@mail.gmail.com/
>> | Suggested-by: Ard Biesheuvel 
>> | Signed-off-by: Masahiro Yamada 
>> | Reviewed-by: Nicolas Schier 
>> | Link: 
>> https://lore.kernel.org/r/20221012233500.156764-1-masahi...@kernel.org
>> | Signed-off-by: Will Deacon 
>> | Signed-off-by: Tom Saeger 
>> | Signed-off-by: Greg Kroah-Hartman 
>> 
>> The problem is still reproducible on Linus' master.
>> 
>> I am reporting the bug to the linux package as I believed there is no
>> real reason for such an increase in the kernel size. In case I missed
>> something and this is actually wanted, the bug can be reassigned to the
>> u-boot package.
>> 
>> Regards
>> Aurelien
>
>> --- u-boot-2023.01+dfsg.orig/include/configs/rpi.h
>> +++ u-boot-2023.01+dfsg/include/configs/rpi.h
>> @@ -95,32 +95,32 @@
>>   *   text_offset bytes (specified in the header of the Image) into a 2MB
>>   *   boundary. The 'booti' command relocates the image if necessary. Linux 
>> uses
>>   *   a default text_offset of 0x8.  In summary, loading at 0x8
>> - *   satisfies all these constraints and reserving memory up to 0x0240
>> - *   permits fairly large (roughly 36M) kernels.
>> + *   satisfies all these constraints and reserving memory up to 0x02a0
>> + *   permits fairly large (roughly 42M) kernels.
>>   *
>>   * scriptaddr and pxefile_addr_r can be pretty much anywhere that doesn't
>>   * conflict with something else. Reserving 1M for each of them at
>> - * 0x0240-0x0250 and 0x0250-0x0260 should be plenty.
>> + * 0x02a0-0x02b0 and 0x02c0-0x02d0 should be plenty.
>>   *
>>   * On ARM, both the DTB and any possible initrd must be loaded such that 
>> they
>>   * fit inside the lowmem mapping in Linux. In practice, this usually means 
>> not
>>   * more than ~700M away from the start of the kernel image but this number 
>> can
>>   * be larger OR smaller depending on e.g. the 'vmalloc=xxxM' command line
>>   * parameter given to the 

Bug#1033437: bugs.debian.org: version-tracking broken for bugs filed against source which is also a binary from another source

[Lucas Nussbaum]

On 24/03/23 at 21:12 +0100, Lucas Nussbaum wrote:
> On 24/03/23 at 20:52 +0100, Lucas Nussbaum wrote:
> > Package: bugs.debian.org
> > Severity: normal
> > 
> > Hi,
> > 
> > Two examples:
> > 
> > 1/ #999526 is filed against the 'mdp' source. It affects testing, but
> > there's no version-tracking graph, and the BTS does not recognize it
> > affects testing.
> > 'mdp' also happens to be a binary package from the 'mdp-src' source.
> > 
> > 2/ Same situation with #965794, filed against the python-ooolib source.
> > python-ooolib is also a binary package from the ooolib-python source.
> 
> A UDD query to identify those (with some false positives):
> select distinct b.* from bugs b
> inner join packages_summary ps on (b.source = ps.package and b.source != 
> ps.source)
> where severity>='serious' and b.package ~ '^src:'
> order by id asc;
> 
> Other occurences are:
> #1031747 (not seen as affecting unstable).
> #1025894 (not seen as affecting testing and unstable)
> #997084 (not seen as affecting stable, testing, unstable)

Better SQL query:

select distinct b.* from bugs b
inner join packages_summary ps on (b.source = ps.package and b.source != 
ps.source)
inner join packages_summary ps2 on (b.source = ps2.source)
where b.package ~ '^src:'
and not affects_oldstable
and not affects_stable
and not affects_testing
and not affects_unstable
and not affects_experimental
order by id asc;

Lucas

Bug#1033437: bugs.debian.org: version-tracking broken for bugs filed against source which is also a binary from another source

[Lucas Nussbaum]

On 24/03/23 at 20:52 +0100, Lucas Nussbaum wrote:
> Package: bugs.debian.org
> Severity: normal
> 
> Hi,
> 
> Two examples:
> 
> 1/ #999526 is filed against the 'mdp' source. It affects testing, but
> there's no version-tracking graph, and the BTS does not recognize it
> affects testing.
> 'mdp' also happens to be a binary package from the 'mdp-src' source.
> 
> 2/ Same situation with #965794, filed against the python-ooolib source.
> python-ooolib is also a binary package from the ooolib-python source.

A UDD query to identify those (with some false positives):
select distinct b.* from bugs b
inner join packages_summary ps on (b.source = ps.package and b.source != 
ps.source)
where severity>='serious' and b.package ~ '^src:'
order by id asc;

Other occurences are:
#1031747 (not seen as affecting unstable).
#1025894 (not seen as affecting testing and unstable)
#997084 (not seen as affecting stable, testing, unstable)

Lucas

Bug#1033440: leocad: yet another application deeply broken by triple buffering patch

[Jérémy Lal]

Package: leocad
Version: 23.03-1
Severity: important

Leocad rendering is broken, with the mouse pointer leaving trail,
and everything being drawn several times before being erased from the display.

I strongly suspect the triple buffering patch that was enabled at the last 
minute :(

I've rebuilt leocad to latest version, just in case it was already fixed, no 
luck.

Jérémy


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

Kernel: Linux 6.1.0-7-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (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 leocad depends on:
ii  libc62.36-8
ii  libgcc-s112.2.0-14
ii  libgl1   1.6.0-1
ii  libqt5concurrent55.15.8+dfsg-3
ii  libqt5core5a 5.15.8+dfsg-3
ii  libqt5gui5   5.15.8+dfsg-3
ii  libqt5network5   5.15.8+dfsg-3
ii  libqt5printsupport5  5.15.8+dfsg-3
ii  libqt5widgets5   5.15.8+dfsg-3
ii  libqt5xml5   5.15.8+dfsg-3
ii  libstdc++6   12.2.0-14
ii  zlib1g   1:1.2.13.dfsg-1

leocad recommends no packages.

Versions of packages leocad suggests:
pn  ldraw-parts  

-- no debconf information

Bug#1033439: pre-unblock: monitoring-plugins/2.3.3-5

[Jan Wagner]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pkg-nagios-de...@lists.alioth.debian.org
Control: affects -1 + src:monitoring-plugins

Please see these changes for monitoring-plugins. 2.3.3-4 is already 
uploaded into unstable (containing one fix from upstream) but is blocked 
due missing autopkgtests. I prepared another upload containing two fixes 
from upstream, which is not uploaded yet.


[ Reason ]
This release targets several fixes that should go into bookworm:

* [953ee52] Adding d/p/13_check_icmp_improvements from upstream
* [6fb8e25] Adding d/p/14_check_curl_fix_SSL_with_multiple_IPs from upstream
* [eab1e1d] Adding d/p/15_check_swap_remove_includes from upstream

[ Impact ]
Included patches fixes regressions from latest upstream release.

[ Tests ]
Upstream testsuite passes as well as Salsa CI 
(https://salsa.debian.org/nagios-team/monitoring-plugins/-/pipelines/514242) 
tests (ignoring the blhc).


[ Risks ]
The code changes are trivial enough to not expect regressions.

[ Checklist ]
 [x] all changes are documented in the d/changelog
 [x] I reviewed all changes and I approve them
 [x] attach debdiff against the package in testing

[ Other info ]

unblock monitoring-plugins/2.3.3-5diff --git a/debian/changelog b/debian/changelog
index caf2e31..c738c88 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+monitoring-plugins (2.3.3-5) unstable; urgency=medium
+
+  * [6fb8e25] Adding d/p/14_check_curl_fix_SSL_with_multiple_IPs from upstream
+  * [eab1e1d] Adding d/p/15_check_swap_remove_includes from upstream
+
+ -- Jan Wagner   Fri, 24 Mar 2023 19:16:16 +
+
+monitoring-plugins (2.3.3-4) unstable; urgency=medium
+
+  * [953ee52] Adding d/p/13_check_icmp_improvements from upstream
+
+ -- Jan Wagner   Tue, 07 Mar 2023 13:29:35 +
+
 monitoring-plugins (2.3.3-3) unstable; urgency=medium
 
   * [15d0c56] Adding d/p/12_check_curl_improvements from upstream
diff --git a/debian/patches/13_check_icmp_improvements b/debian/patches/13_check_icmp_improvements
new file mode 100644
index 000..0eb2748
--- /dev/null
+++ b/debian/patches/13_check_icmp_improvements
@@ -0,0 +1,200 @@
+From 413af1955538b06803458c628099f1ba9da1966b Mon Sep 17 00:00:00 2001
+From: RincewindsHat <12514511+rincewinds...@users.noreply.github.com>
+Date: Fri, 4 Nov 2022 16:51:32 +0100
+Subject: [PATCH 1/5] Remove trailing whitespaces
+
+---
+ plugins-root/check_icmp.c | 24 
+ 1 file changed, 12 insertions(+), 12 deletions(-)
+
+diff --git a/plugins-root/check_icmp.c b/plugins-root/check_icmp.c
+index f8f153512..abd88c4e7 100644
+--- a/plugins-root/check_icmp.c
 b/plugins-root/check_icmp.c
+@@ -1,39 +1,39 @@
+ /*
+-* 
++*
+ * Monitoring check_icmp plugin
+-* 
++*
+ * License: GPL
+ * Copyright (c) 2005-2008 Monitoring Plugins Development Team
+ * Original Author : Andreas Ericsson 
+-* 
++*
+ * Description:
+-* 
++*
+ * This file contains the check_icmp plugin
+-* 
++*
+ * Relevant RFC's: 792 (ICMP), 791 (IP)
+-* 
++*
+ * This program was modeled somewhat after the check_icmp program,
+ * which was in turn a hack of fping (www.fping.org) but has been
+ * completely rewritten since to generate higher precision rta values,
+ * and support several different modes as well as setting ttl to control.
+ * redundant routes. The only remainders of fping is currently a few
+ * function names.
+-* 
+-* 
++*
++*
+ * 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 .
+-* 
+-* 
++*
++*
+ */
+ 
+ /* progname may change */
+
+From 7d074091dba8c1d4081971bf62e694d0b1a03d41 Mon Sep 17 00:00:00 2001
+From: RincewindsHat <12514511+rincewinds...@users.noreply.github.com>
+Date: Fri, 4 Nov 2022 16:53:57 +0100
+Subject: [PATCH 2/5] Remove hardcoded DBL_MAX definition
+
+---
+ plugins-root/check_icmp.c | 4 
+ 1 file changed, 4 deletions(-)
+
+diff --git a/plugins-root/check_icmp.c b/plugins-root/check_icmp.c
+index abd88c4e7..0d10d22db 100644
+--- a/plugins-root/check_icmp.c
 b/plugins-root/check_icmp.c
+@@ -95,10 +95,6 @@ const char *email = "de...@monitoring-plugins.org";
+ # define ICMP_UNREACH_PRECEDENCE_CUTOFF 15
+ #endif
+ 
+-#ifndef DBL_MAX
+-# define DBL_MAX 

Bug#1033438: error in ascii(7)

[VA]

Package: manpages-fr
Version: 4.18.0-1

ascii(7) contains an error for character 2A (in hex), it indicates "–" 
(U+2013) instead of "+" (U+002A).
The error can be seen here too: 
https://manpages.debian.org/unstable/manpages-fr/ascii.7.fr.html

Bug#1033408: apache2: Segmentation fault + 503 on frontpage on 2.4.56-1

[Salvatore Bonaccorso]

Hi,

On Fri, Mar 24, 2023 at 05:17:34PM +0100, Fabien LE BERRE wrote:
> Yes it does look like the bug. The Backtrace looks a lot like the coredump
> I've seen.
> Thanks for the heads up. Looking forward for the patch to be applied
> officially.

Would you be able to have additionally test the patch on your case to
confirm? That would be great and helpful for releasing the regression
update.

Regards,
Salvatore

Bug#1033437: bugs.debian.org: version-tracking broken for bugs filed against source which is also a binary from another source

[Lucas Nussbaum]

Package: bugs.debian.org
Severity: normal

Hi,

Two examples:

1/ #999526 is filed against the 'mdp' source. It affects testing, but
there's no version-tracking graph, and the BTS does not recognize it
affects testing.
'mdp' also happens to be a binary package from the 'mdp-src' source.

2/ Same situation with #965794, filed against the python-ooolib source.
python-ooolib is also a binary package from the ooolib-python source.

Lucas

Bug#1033435: cloud-sptheme: FTBFS in testing: Could not import extension cloud_sptheme.ext.autodoc_sections (exception: cannot import name 'Markup' from 'jinja2' (/usr/lib/python3/dist-packages/jinja2

[Lucas Nussbaum]

Source: cloud-sptheme
Version: 1.10.1.post20200504175005-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/cloud_sptheme
> copying cloud_sptheme/make_helper.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme
> copying cloud_sptheme/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme
> copying cloud_sptheme/utils.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme
> creating /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/escaped_samp_literals.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/autodoc_sections.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/table_styling.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/auto_redirect.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/docfield_markup.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/relbar_toc.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/autoattribute_search_bases.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/page_only.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/perpage.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/index_styling.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/issue_tracker.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/allow_unreferenced_footnotes.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/role_index.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/relbar_links.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext
> creating /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/tests
> copying cloud_sptheme/tests/test_ext_relbar_toc.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/tests
> copying cloud_sptheme/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/tests
> copying cloud_sptheme/tests/utils.py -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/tests
> creating 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext/static
> copying cloud_sptheme/ext/static/auto_redirect.css -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext/static
> copying cloud_sptheme/ext/static/auto_redirect.html_t -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext/static
> copying cloud_sptheme/ext/static/table_styling.css -> 
> /<>/.pybuild/cpython3_3.11/build/cloud_sptheme/ext/static
> I: pybuild pybuild:333: SPHINX_THEME="classic" http_proxy="127.0.0.1:9" 
> python3.11 -m sphinx -N -b html docs/ 
> /<>/debian/cloud-sptheme/docs/html
> Running Sphinx v5.3.0
> 
> Extension error:
> Could not import extension cloud_sptheme.ext.autodoc_sections (exception: 
> cannot import name 'Markup' from 'jinja2' 
> (/usr/lib/python3/dist-packages/jinja2/__init__.py))
> E: pybuild pybuild:388: build: plugin distutils failed with: exit code=2: 
> SPHINX_THEME="classic" http_proxy="127.0.0.1:9" python3.11 -m sphinx -N -b 
> html docs/ /<>/debian/cloud-sptheme/docs/html
> dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned 
> exit code 13
> make: *** [debian/rules:4: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/03/23/cloud-sptheme_1.10.1.post20200504175005-5_testing.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230323;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230323=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something 

Bug#1033434: devscripts: FTBFS in testing: AssertionError: pylint found issues:

[Lucas Nussbaum]

Source: devscripts
Version: 2.23.2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> make[3]: Entering directory '/<>/scripts'
> perl -I ../lib -c bts; \
> 
> perl -I ../lib -c build-rdeps; \
> 
> perl -I ../lib -c chdist; \
> 
> perl -I ../lib -c checkbashisms; \
> 
> perl -I ../lib -c cvs-debuild; \
> 
> perl -I ../lib -c dd-list; \
> 
> perl -I ../lib -c deb-why-removed; \
> 
> perl -I ../lib -c debc; \
> 
> cvs-debuild syntax OK
> perl -I ../lib -c debchange; \
> 
> checkbashisms syntax OK
> perl -I ../lib -c debcheckout; \
> 
> build-rdeps syntax OK
> perl -I ../lib -c debcommit; \
> 
> debc syntax OK
> perl -I ../lib -c debdiff; \
> 
> dd-list syntax OK
> perl -I ../lib -c debi; \
> 
> chdist syntax OK
> perl -I ../lib -c debpkg; \
> 
> deb-why-removed syntax OK
> perl -I ../lib -c debrebuild; \
> 
> debpkg syntax OK
> perl -I ../lib -c debsnap; \
> 
> debcommit syntax OK
> perl -I ../lib -c debuild; \
> 
> debchange syntax OK
> perl -I ../lib -c dep3changelog; \
> 
> debdiff syntax OK
> perl -I ../lib -c desktop2menu; \
> 
> debi syntax OK
> perl -I ../lib -c dget; \
> 
> debcheckout syntax OK
> perl -I ../lib -c dpkg-depcheck; \
> 
> dep3changelog syntax OK
> perl -I ../lib -c dscverify; \
> 
> debsnap syntax OK
> perl -I ../lib -c git-deborig; \
> 
> debuild syntax OK
> bts syntax OK
> perl -I ../lib -c grep-excuses; \
> 
> perl -I ../lib -c hardening-check; \
> 
> desktop2menu syntax OK
> perl -I ../lib -c mass-bug; \
> 
> grep-excuses syntax OK
> perl -I ../lib -c mk-build-deps; \
> 
> mass-bug syntax OK
> perl -I ../lib -c mk-origtargz; \
> 
> dpkg-depcheck syntax OK
> dget syntax OK
> perl -I ../lib -c namecheck; \
> 
> perl -I ../lib -c origtargz; \
> 
> dscverify syntax OK
> perl -I ../lib -c plotchangelog; \
> 
> hardening-check syntax OK
> perl -I ../lib -c rc-alert; \
> 
> debrebuild syntax OK
> git-deborig syntax OK
> perl -I ../lib -c rmadison; \
> 
> perl -I ../lib -c salsa; \
> 
> namecheck syntax OK
> plotchangelog syntax OK
> perl -I ../lib -c svnpath; \
> 
> perl -I ../lib -c tagpending; \
> 
> rmadison syntax OK
> perl -I ../lib -c transition-check; \
> 
> svnpath syntax OK
> perl -I ../lib -c uscan; \
> 
> origtargz syntax OK
> perl -I ../lib -c who-permits-upload; \
> 
> mk-build-deps syntax OK
> bash -n annotate-output
> transition-check syntax OK
> bash -n archpath
> bash -n cowpoke
> bash -n cvs-debi
> bash -n cvs-debrelease
> bash -n dcmd
> bash -n deb-reversion
> bash -n debclean
> bash -n debrelease
> bash -n debrepro
> bash -n debrsign
> bash -n debsign
> bash -n diff2patches
> bash -n dpkg-genbuilddeps
> bash -n dscextract
> bash -n edit-patch
> rc-alert syntax OK
> bash -n getbuildlog
> bash -n list-unreleased
> bash -n ltnu
> bash -n manpage-alert
> bash -n mergechanges
> bash -n nmudiff
> bash -n pts-subscribe
> bash -n run_bisect
> bash -n run_bisect_qemu
> bash -n uupdate
> bash -n what-patch
> bash -n who-uploads
> bash -n whodepends
> bash -n wnpp-alert
> bash -n wnpp-check
> tagpending syntax OK
> mk-origtargz syntax OK
> py3versions: no X-Python3-Version in control file, using supported versions
> python3.11 setup.py test
> who-permits-upload syntax OK
> uscan syntax OK
> salsa syntax OK
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> creating devscripts.egg-info
> writing devscripts.egg-info/PKG-INFO
> writing dependency_links to devscripts.egg-info/dependency_links.txt
> writing top-level names to devscripts.egg-info/top_level.txt
> writing manifest file 'devscripts.egg-info/SOURCES.txt'
> reading manifest file 'devscripts.egg-info/SOURCES.txt'
> writing manifest file 'devscripts.egg-info/SOURCES.txt'
> running build_ext
> test_flake8 (devscripts.test.test_flake8.Flake8TestCase.test_flake8)
> Test: Run flake8 on Python source code. ... Running following command:
> /usr/bin/python3.11 -m flake8 --ignore=E203,W503 --max-line-length=88 
> debbisect debdiff-apply debootsnap deb-janitor reproducible-check sadt 
> suspicious-source wrap-and-sort devscripts setup.py
> ok
> test_isort (devscripts.test.test_isort.IsortTestCase.test_isort)
> Test: Run isort on Python source code. ... Running following command:
> isort --check-only --diff debbisect debdiff-apply debootsnap deb-janitor 
> reproducible-check sadt suspicious-source wrap-and-sort devscripts setup.py
> ok
> test_args (devscripts.test.test_logger.LoggerTestCase.test_args) ... ok
> test_command (devscripts.test.test_logger.LoggerTestCase.test_command) ... ok
> test_no_args (devscripts.test.test_logger.LoggerTestCase.test_no_args) ... ok
> test_rts_formatter 
> (devscripts.test.test_control.ControlTestCase.test_rts_formatter) 

Bug#1033432: pyramid-jinja2: FTBFS in testing: ImportError: cannot import name 'contextfilter' from 'jinja2' (/usr/lib/python3/dist-packages/jinja2/__init__.py)

[Lucas Nussbaum]

Source: pyramid-jinja2
Version: 2.7+dfsg-1.2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2
> copying pyramid_jinja2/i18n.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2
> copying pyramid_jinja2/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2
> copying pyramid_jinja2/compat.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2
> copying pyramid_jinja2/settings.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2
> copying pyramid_jinja2/filters.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2
> creating 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/scaffolds
> copying pyramid_jinja2/scaffolds/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/scaffolds
> creating 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/demo
> copying pyramid_jinja2/demo/tests.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/demo
> copying pyramid_jinja2/demo/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/demo
> creating 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests
> copying pyramid_jinja2/tests/base.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests
> copying pyramid_jinja2/tests/extensions.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests
> copying pyramid_jinja2/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests
> copying pyramid_jinja2/tests/test_filters.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests
> copying pyramid_jinja2/tests/test_settings.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests
> copying pyramid_jinja2/tests/test_ext.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests
> copying pyramid_jinja2/tests/test_it.py -> 
> /<>/.pybuild/cpython3_3.11_pyramid-jinja2/build/pyramid_jinja2/tests
> running egg_info
> writing pyramid_jinja2.egg-info/PKG-INFO
> writing dependency_links to pyramid_jinja2.egg-info/dependency_links.txt
> writing entry points to pyramid_jinja2.egg-info/entry_points.txt
> writing requirements to pyramid_jinja2.egg-info/requires.txt
> writing top-level names to pyramid_jinja2.egg-info/top_level.txt
> reading manifest file 'pyramid_jinja2.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.pyc' found under directory 
> 'docs'
> warning: no previously-included files matching '*.pyc' found under directory 
> 'pyramid_jinja2'
> adding license file 'LICENSE.txt'
> writing manifest file 'pyramid_jinja2.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: 
> SetuptoolsDeprecationWarning: Installing 'pyramid_jinja2.demo.locale' as 
> data is deprecated, please list it in `packages`.
> !!
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'pyramid_jinja2.demo.locale' as an importable package,
> but it is not listed in the `packages` configuration of setuptools.
> 
> 'pyramid_jinja2.demo.locale' has been automatically added to the 
> distribution only
> because it may contain data files, but this behavior is likely to change
> in future versions of setuptools (and therefore is considered deprecated).
> 
> Please make sure that 'pyramid_jinja2.demo.locale' is included as a 
> package by using
> the `packages` configuration field or the proper discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
> 
> You can read more about "package discovery" and "data files" on setuptools
> documentation page.
> 
> 
> !!
> 
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: 
> SetuptoolsDeprecationWarning: Installing 

Bug#1033433: cfgrib: FTBFS in testing: make[1]: *** [debian/rules:21: override_dh_auto_test] Error 13

[Lucas Nussbaum]

Source: cfgrib
Version: 0.9.10.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for p in python3.11; do \
> PY3VERNUM=`echo $p | sed -e 's/python//' `; \
>   pybuild --test --test-pytest -i $p -p $PY3VERNUM  ;  \
> done
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_cfgrib/build; 
> python3.11 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: pyproject.toml
> collected 117 items / 1 skipped
> 
> tests/test_10_cfunits.py .   [  
> 0%]
> tests/test_20_cfcoords.py .  [  
> 5%]
> tests/test_20_main.py .  [  
> 5%]
> tests/test_20_messages.py .  [ 
> 13%]
> tests/test_25_cfmessage.py . [ 
> 17%]
> tests/test_30_dataset.py [ 
> 41%]
> tests/test_40_xarray_store.py .X..   [ 
> 48%]
> tests/test_40_xarray_to_grib_regular_ll.py . [ 
> 52%]
> tests/test_50_datamodels.py ..   [ 
> 54%]
> tests/test_50_sample_data.py .X.x.FF.x.X.x.XX.   [ 
> 86%]
> tests/test_50_xarray_getitem.py ..   [ 
> 94%]
> tests/test_50_xarray_plugin.py ..
> [100%]
> 
> === FAILURES 
> ===
>  test_canonical_dataset_to_grib[regular_gg_sfc] 
> 
> 
> grib_name = 'regular_gg_sfc'
> tmpdir = 
> local('/tmp/pytest-of-user42/pytest-5/test_canonical_dataset_to_grib5')
> 
> @pytest.mark.parametrize(
> "grib_name",
> [
> pytest.param("era5-levels-members", marks=pytest.mark.xfail),
> "fields_with_missing_values",
> pytest.param("lambert_grid", marks=pytest.mark.xfail),
> "reduced_gg",
> "regular_gg_sfc",
> "regular_gg_pl",
> "regular_gg_ml",
> pytest.param("regular_gg_ml_g2", marks=pytest.mark.xfail),
> "regular_ll_sfc",
> pytest.param("regular_ll_msl", marks=pytest.mark.xfail),
> "scanning_mode_64",
> pytest.param("spherical_harmonics", marks=pytest.mark.xfail),
> "t_analysis_and_fc_0",
> ],
> )
> def test_canonical_dataset_to_grib(grib_name: str, tmpdir: py.path.local) 
> -> None:
> grib_path = os.path.join(SAMPLE_DATA_FOLDER, grib_name + ".grib")
> out_path = str(tmpdir.join(grib_name + ".grib"))
> 
> res = xarray_store.open_dataset(grib_path)
> 
> with pytest.warns(FutureWarning):
> xarray_to_grib.canonical_dataset_to_grib(res, out_path)
> >   reread = xarray_store.open_dataset(out_path)
> 
> tests/test_50_sample_data.py:93: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> cfgrib/xarray_store.py:39: in open_dataset
> return xr.open_dataset(path, **kwargs)  # type: ignore
> /usr/lib/python3/dist-packages/xarray/backends/api.py:541: in open_dataset
> backend_ds = backend.open_dataset(
> cfgrib/xarray_plugin.py:109: in open_dataset
> store = CfGribDataStore(
> cfgrib/xarray_plugin.py:40: in __init__
> self.ds = opener(filename, **backend_kwargs)
> cfgrib/dataset.py:780: in open_file
> return open_from_index(index, read_keys, time_dims, extra_coords, 
> **kwargs)
> cfgrib/dataset.py:722: in open_from_index
> dimensions, variables, attributes, encoding = build_dataset_components(
> cfgrib/dataset.py:649: in build_dataset_components
> dims, data_var, coord_vars = build_variable_components(
> cfgrib/dataset.py:525: in build_variable_components
> geo_dims, geo_shape, geo_coord_vars = build_geography_coordinates(first, 
> encode_cf, errors)
> cfgrib/dataset.py:388: in build_geography_coordinates
> latitudes = np.array(first["distinctLatitudes"], ndmin=1)
> cfgrib/messages.py:246: in __getitem__
> return self.context[item]
> cfgrib/messages.py:168: in __getitem__
> return self.message_get(key, key_type=key_type)
> cfgrib/messages.py:130: in message_get
> if eccodes.codes_get_size(self.codes_id, item) > 1:
> /usr/lib/python3/dist-packages/gribapi/gribapi.py:599: in grib_get_size
> GRIB_CHECK(err)
> /usr/lib/python3/dist-packages/gribapi/gribapi.py:230: in GRIB_CHECK
> errors.raise_grib_error(errid)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Bug#1033431: cookiecutter: FTBFS in testing: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13

[Lucas Nussbaum]

Source: cookiecutter
Version: 1.7.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/hooks.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/extensions.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/__main__.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/main.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/prompt.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/config.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/log.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/repository.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/generate.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/replay.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/find.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/vcs.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/zipfile.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/cli.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/utils.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> copying cookiecutter/environment.py -> 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build/cookiecutter
> running egg_info
> creating cookiecutter.egg-info
> writing cookiecutter.egg-info/PKG-INFO
> writing dependency_links to cookiecutter.egg-info/dependency_links.txt
> writing entry points to cookiecutter.egg-info/entry_points.txt
> writing requirements to cookiecutter.egg-info/requires.txt
> writing top-level names to cookiecutter.egg-info/top_level.txt
> writing manifest file 'cookiecutter.egg-info/SOURCES.txt'
> reading manifest file 'cookiecutter.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'AUTHORS.rst'
> warning: no files found matching 'CONTRIBUTING.rst'
> warning: no files found matching 'HISTORY.rst'
> warning: no files found matching 'README.rst'
> warning: no previously-included files matching '__pycache__' found under 
> directory '*'
> warning: no previously-included files matching '*.py[co]' found under 
> directory '*'
> adding license file 'LICENSE'
> adding license file 'AUTHORS.md'
> writing manifest file 'cookiecutter.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd 
> /<>/.pybuild/cpython3_3.11_cookiecutter/build; python3.11 -m 
> pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack -- 
> /usr/bin/python3.11
> cachedir: .pytest_cache
> rootdir: /<>, configfile: setup.cfg
> plugins: mock-3.8.2, cov-4.0.0
> collecting ... collected 276 items
> 
> tests/test_abort_generate_on_hook_error.py::test_hooks_raises_errors[pre_gen_hook_raises_error]
>  PASSED [  0%]
> tests/test_abort_generate_on_hook_error.py::test_hooks_raises_errors[post_gen_hook_raises_error]
>  PASSED [  0%]
> tests/test_cli.py::test_cli_version[-V] PASSED   [  
> 1%]
> tests/test_cli.py::test_cli_version[--version] PASSED[  
> 1%]
> tests/test_cli.py::test_cli_error_on_existing_output_directory PASSED[  
> 1%]
> tests/test_cli.py::test_cli PASSED   [  
> 2%]
> tests/test_cli.py::test_cli_verbose PASSED   [  
> 2%]
> tests/test_cli.py::test_cli_replay PASSED[  
> 2%]
> tests/test_cli.py::test_cli_exit_on_noinput_and_replay PASSED[  
> 3%]
> tests/test_cli.py::test_run_cookiecutter_on_overwrite_if_exists_and_replay[-f]
>  PASSED [  3%]
> 

Bug#1033429: simutrans-pak128.britain: FTBFS in testing: make[2]: *** [Makefile:135: industry] Error 1

[Lucas Nussbaum]

Source: simutrans-pak128.britain
Version: 1.18-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> ===> COPY
> ===> OUTSIDE with REVISION and grounds
> #@svnversion >>grounds/outsiderev.dat
> echo 1991 >>grounds/outsiderev.dat
> Warning: tabfile_t::read: No data in "1991"
> Warning: :Entry "copyright=pak128.Britain 1.18 120.3 r" ignored (check 
> spelling)
> ===> PAK32 boats/holds
> Message: Image size:  Now set to 32x32
> ===> PAK64 gui/gui64
> libpng warning: Interlace handling should be turned on when using 
> png_read_image
> libpng warning: iCCP: known incorrect sRGB profile
> libpng warning: Interlace handling should be turned on when using 
> png_read_image
> libpng warning: iCCP: known incorrect sRGB profile
> ===> PAK128 air
> Message: Image size:  Now set to 128x128
> Warning: AirbusA320(Thomson): Entry "comfort=100" ignored (check spelling)
> Warning: AirbusA320(Thomson): Entry "increase_maintenance_after_years=30" 
> ignored (check spelling)
> Warning: HandleyPageW8b_Mail: Entry "minimum_runway_length=600" ignored 
> (check spelling)
> Warning: HandleyPageW8b_Mail: Entry "min_loading_time=1800" ignored (check 
> spelling)
> Warning: HandleyPageW8b_Mail: Entry "max_loading_time=2000" ignored (check 
> spelling)
> Warning: HandleyPageW8b_Mail: Entry "tractive_effort=13" ignored (check 
> spelling)
> Warning: Vickers_Viscount_802(BEA):   Entry "catering_level=3" ignored (check 
> spelling)
> Warning: Bristol_Type170_Mk32_BritishUnitedAirFerries:Entry 
> "range=2140" ignored (check spelling)
> Warning: Bristol_Type170_Mk32_BritishUnitedAirFerries:Entry 
> "minimum_runway_length=1250" ignored (check spelling)
> Warning: Bristol_Type170_Mk32_BritishUnitedAirFerries:Entry 
> "comfort=90" ignored (check spelling)
> Warning: Bristol_Type170_Mk32_BritishUnitedAirFerries:Entry 
> "catering_level=1" ignored (check spelling)
> Warning: Bristol_Type170_Mk32_BritishUnitedAirFerries:Entry 
> "min_loading_time=2200" ignored (check spelling)
> Warning: Bristol_Type170_Mk32_BritishUnitedAirFerries:Entry 
> "max_loading_time=2200" ignored (check spelling)
> Warning: Bristol_Type170_Mk32_BritishUnitedAirFerries:Entry 
> "tractive_effort=38" ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoCar:   Entry "range=2140" ignored 
> (check spelling)
> Warning: Bristol_Type170_Mk32_CargoCar:   Entry 
> "minimum_runway_length=1250" ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoCar:   Entry "min_loading_time=2200" 
> ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoCar:   Entry "max_loading_time=2200" 
> ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoCar:   Entry "tractive_effort=38" 
> ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoPiece: Entry "range=2140" ignored 
> (check spelling)
> Warning: Bristol_Type170_Mk32_CargoPiece: Entry 
> "minimum_runway_length=1250" ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoPiece: Entry "min_loading_time=2200" 
> ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoPiece: Entry "max_loading_time=2200" 
> ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoPiece: Entry "tractive_effort=38" 
> ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoCool:  Entry "range=2140" ignored 
> (check spelling)
> Warning: Bristol_Type170_Mk32_CargoCool:  Entry 
> "minimum_runway_length=1250" ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoCool:  Entry "min_loading_time=2200" 
> ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoCool:  Entry "max_loading_time=2200" 
> ignored (check spelling)
> Warning: Bristol_Type170_Mk32_CargoCool:  Entry "tractive_effort=38" 
> ignored (check spelling)
> Warning: BAC_111_500(Caledonian): Entry "comfort=95" ignored (check 
> spelling)
> Warning: BAC_111_500(Caledonian): Entry "min_loading_time=2400" ignored 
> (check spelling)
> Warning: BAC_111_500(Caledonian): Entry "max_loading_time=2400" ignored 
> (check spelling)
> Warning: ATR_42_320(BlueIslands): Entry "comfort=100" ignored (check 
> spelling)
> Warning: Douglas_DC2: Entry "minimum_runway_length=600" ignored (check 
> spelling)
> Warning: Douglas_DC2: Entry "comfort=90" ignored (check spelling)
> Warning: Douglas_DC2: Entry "min_loading_time=1800" ignored (check spelling)
> Warning: Douglas_DC2: Entry "max_loading_time=1800" ignored (check spelling)
> Warning: Douglas_DC2: Entry "tractive_effort=11" ignored (check spelling)
> Warning: Douglas_DC4_C54_Mail:Entry "range=4050" ignored (check 
> spelling)
> Warning: Douglas_DC4_C54_Mail:Entry "minimum_runway_length=1250" 
> ignored 

Bug#1033428: tycho: FTBFS in testing: make[1]: *** [debian/rules:9: override_dh_auto_build] Error 25

[Lucas Nussbaum]

Source: tycho
Version: 1.6.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- package -Dmaven.test.skip=true
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -Dmaven.test.skip=true -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [WARNING] The project org.eclipse.tycho:tycho:pom:1.6.0 uses prerequisites 
> which is only intended for maven-plugin projects but not for non maven-plugin 
> projects. For such purposes you should use the maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Tycho  
> [pom]
> [INFO] Tycho OSGi Bundles Parent  
> [pom]
> [INFO] Tycho Embedder API Maven/OSGi Shared Classes   
> [jar]
> [INFO] Tycho Core Maven/OSGi Shared Classes   
> [jar]
> [INFO] Tycho p2 Resolver Maven/OSGi Shared Classes
> [jar]
> [INFO] Tycho p2 Tools Maven/OSGi Shared Classes   
> [jar]
> [INFO] Tycho Maven/p2 Repository Integration  
> [jar]
> [INFO] Tycho p2 Resolver Bundle   
> [jar]
> [INFO] Tycho p2 Tools Bundle  
> [jar]
> [INFO] Tycho OSGi Runtime External Bundles
> [jar]
> [INFO] Sisu Equinox/Plexus bridge 
> [pom]
> [INFO] Sisu Equinox Services API  
> [jar]
> [INFO] Sisu Equinox Embedder  
> [jar]
> [INFO] Tycho Eclipse Project Metadata Model   
> [jar]
> [INFO] Tycho Embedder API 
> [jar]
> [INFO] Tycho Core 
> [jar]
> [INFO] Sisu Equinox Launching 
> [jar]
> [INFO] Tycho JVM Library Detector 
> [jar]
> [INFO] Tycho JDT Compiler Component   
> [jar]
> [INFO] Tycho OSGi Compiler Plugin
> [maven-plugin]
> [INFO] Tycho OSGi Packaging Plugin   
> [maven-plugin]
> [INFO] Tycho Target Platform Configuration Plugin
> [maven-plugin]
> [INFO] Tycho p2 Tools Parent  
> [pom]
> [INFO] Tycho p2 Resolver Component
> [jar]
> [INFO] Tycho Maven Build Extension   
> [maven-plugin]
> [INFO] Tycho Artifactor Comparator Plugin 
> [jar]
> [INFO] Tycho p2 Metadata Plugin  
> [maven-plugin]
> [INFO] Tycho p2 Publisher Plugin 
> [maven-plugin]
> [INFO] Tycho p2 Repository Plugin
> [maven-plugin]
> [INFO] 
> [INFO] --< org.eclipse.tycho:tycho 
> >---
> [INFO] Building Tycho 1.6.0  
> [1/29]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] --< org.eclipse.tycho:tycho-bundles 
> >---
> [INFO] Building Tycho OSGi Bundles Parent 1.6.0  
> [2/29]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] < org.eclipse.tycho:org.eclipse.tycho.embedder.shared 
> >-
> [INFO] Building Tycho Embedder API Maven/OSGi Shared Classes 1.6.0   
> [3/29]
> [INFO] [ jar 
> ]-
> [INFO] 
> [INFO] --- maven-resources-plugin:3.3.0:resources (default-resources) @ 
> org.eclipse.tycho.embedder.shared ---
> [INFO] Copying 1 resource
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.10.1:compile (default-compile) @ 
> 

Bug#1033426: python-uhashring: FTBFS in testing: tests fail

[Lucas Nussbaum]

Source: python-uhashring
Version: 2.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2 --in-tmp
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + PKGOS_IN_TMP=yes
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-uhashring
> + echo python-uhashring
> + sed s/python-//
> + PY_MODULE_NAME=uhashring
> + py3versions -vr
> + PYTHON3S=3.11
> + [ yes = yes ]
> + TARGET_DIR=tmp
> + pwd
> + python3.11 setup.py install --install-layout=deb --root 
> /<>/debian/tmp
> running install
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/uhashring
> copying uhashring/ring.py -> build/lib/uhashring
> copying uhashring/ring_meta.py -> build/lib/uhashring
> copying uhashring/ring_ketama.py -> build/lib/uhashring
> copying uhashring/__init__.py -> build/lib/uhashring
> copying uhashring/monkey.py -> build/lib/uhashring
> running egg_info
> creating uhashring.egg-info
> writing uhashring.egg-info/PKG-INFO
> writing dependency_links to uhashring.egg-info/dependency_links.txt
> writing top-level names to uhashring.egg-info/top_level.txt
> writing manifest file 'uhashring.egg-info/SOURCES.txt'
> reading manifest file 'uhashring.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'uhashring.egg-info/SOURCES.txt'
> running install_lib
> creating /<>/debian/tmp
> creating /<>/debian/tmp/usr
> creating /<>/debian/tmp/usr/lib
> creating /<>/debian/tmp/usr/lib/python3
> creating /<>/debian/tmp/usr/lib/python3/dist-packages
> creating /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring
> copying build/lib/uhashring/ring.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring
> copying build/lib/uhashring/ring_meta.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring
> copying build/lib/uhashring/ring_ketama.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring
> copying build/lib/uhashring/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring
> copying build/lib/uhashring/monkey.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring/ring.py 
> to ring.cpython-311.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring/ring_meta.py
>  to ring_meta.cpython-311.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring/ring_ketama.py
>  to ring_ketama.cpython-311.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring/__init__.py
>  to __init__.cpython-311.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring/monkey.py 
> to monkey.cpython-311.pyc
> running install_egg_info
> Copying uhashring.egg-info to 
> /<>/debian/tmp/usr/lib/python3/dist-packages/uhashring-2.1.egg-info
> Skipping SOURCES.txt
> running install_scripts
> + pwd
> + rm -rf /<>/debian/python*/usr/lib/python*/dist-packages/*.pth
> + pwd
> + rm -rf /<>/debian/tmp/usr/lib/python*/dist-packages/*.pth
> set -e ; for pyvers in 3.11; do \
>   PYTHONPATH=. python$pyvers -m pytest ; \
> done
> = test session starts 
> ==
> platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: tox.ini
> collected 21 items
> 
> tests/test_distribution.py F [  
> 4%]
> tests/test_implementation.py .s...   [ 
> 85%]
> tests/test_ketama_compatibility.py ..[ 
> 95%]
> tests/test_monkey.py .   
> [100%]
> 
> === FAILURES 
> ===
> __ test_distribution 
> ___
> 
> def test_distribution():
> ring = HashRing()
> 
> numnodes = 10
> numhits = 1000
> numvalues = 1
> 
> for i in range(1, numnodes + 1):
> ring["node{}".format(i)] = {"instance": "node_value{}".format(i)}
> 
> distribution = Counter()
> for i in range(numhits):
> key = str(randint(1, numvalues))
> node = ring[key]
>

Bug#1033427: emoslib: FTBFS in testing: intf2.c:251:27: error: ‘GRIB_UTIL_SET_SPEC_FLAGS_ONLY_PACKING’ undeclared (first use in this function)

[Lucas Nussbaum]

Source: emoslib
Version: 2:4.5.9-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/libemos-sp-shared && /usr/bin/cc 
> -DBUFR_TABLES_PATH=\"/usr/share/emos/bufrtables\" -DFOPEN64 -DINTEGER_IS_INT 
> -DPOINTER_64 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE 
> -Demos_sp_shared_EXPORTS -Dgfortran -Dlinux 
> -I/<>/obj-x86_64-linux-gnu/module -I/<> 
> -I/<>/obj-x86_64-linux-gnu -I/<>/interpolation 
> -I/<>/bufrdc_wmo -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -pipe -O3 -DNDEBUG -fPIC -fPIC -mcmodel=medium   -MD -MT 
> libemos-sp-shared/CMakeFiles/emos_sp_shared.dir/__/interpolation/intuvs2.c.o 
> -MF CMakeFiles/emos_sp_shared.dir/__/interpolation/intuvs2.c.o.d -o 
> CMakeFiles/emos_sp_shared.dir/__/interpolation/intuvs2.c.o -c 
> /<>/interpolation/intuvs2.c
> /<>/interpolation/intf2.c:251:27: error: 
> ‘GRIB_UTIL_SET_SPEC_FLAGS_ONLY_PACKING’ undeclared (first use in this 
> function)
>   251 | set_spec_flags |= GRIB_UTIL_SET_SPEC_FLAGS_ONLY_PACKING;
>   |   ^
> /<>/interpolation/intf2.c:251:27: note: each undeclared 
> identifier is reported only once for each function it appears in
> make[3]: *** 
> [libemos-sp-shared/CMakeFiles/emos_sp_shared.dir/build.make:3127: 
> libemos-sp-shared/CMakeFiles/emos_sp_shared.dir/__/interpolation/intf2.c.o] 
> Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/03/23/emoslib_4.5.9-7_testing.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230323;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230323=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1033425: python-scrapy: FTBFS in testing: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: python-scrapy
Version: 2.8.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> tests/test_linkextractors.py ... [ 
> 60%]
> tests/test_loader.py ... [ 
> 61%]
>  [ 
> 62%]
> tests/test_loader_deprecated.py  [ 
> 63%]
> ...  [ 
> 64%]
> tests/test_logformatter.py   [ 
> 64%]
> tests/test_mail.py ...   [ 
> 65%]
> tests/test_middleware.py [ 
> 65%]
> tests/test_pipeline_crawl.py [ 
> 65%]
> tests/test_pipeline_files.py sss [ 
> 66%]
> tests/test_pipeline_images.py .  [ 
> 67%]
> tests/test_pipeline_media.py ..  [ 
> 68%]
> tests/test_pipelines.py s[ 
> 68%]
> tests/test_pqueues.py s...s..[ 
> 68%]
> tests/test_proxy_connect.py 
> E: Build killed with signal TERM after 150 minutes of inactivity

I don't think this is #921803.


The full build log is available from:
http://qa-logs.debian.net/2023/03/23/python-scrapy_2.8.0-1_testing.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230323;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230323=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1033424: image-factory: FTBFS in testing: AssertionError: pylint found issues:

[Lucas Nussbaum]

Source: image-factory
Version: 1.0.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230323 ftbfs-bookworm

Hi,

During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 -m unittest discover -v
> test_black (tests.test_black.BlackTestCase.test_black)
> Test: Run black code formatter on Python source code. ... Running following 
> command:
> black --check --diff -l 99 image-factory tests
> ok
> test_empty_config (tests.test_cli.TestCLI.test_empty_config)
> Test empty configuration file. ... ok
> test_example_config (tests.test_cli.TestCLI.test_example_config)
> Test exapmle image-factory.conf file. ... ok
> test_override_cache_dir (tests.test_cli.TestCLI.test_override_cache_dir)
> Test overriding the cache directory. ... ok
> test_flake8 (tests.test_flake8.Flake8TestCase.test_flake8)
> Test: Run flake8 on Python source code. ... Running following command:
> /usr/bin/python3 -m flake8 --max-line-length=99 image-factory tests
> ok
> test_invalid (tests.test_helper.TestParseBytes.test_invalid)
> Test parse_bytes("invalid") ... ok
> test_parse_1_g (tests.test_helper.TestParseBytes.test_parse_1_g)
> Test parse_bytes("1G") ... ok
> test_parse_2_tb (tests.test_helper.TestParseBytes.test_parse_2_tb)
> Test parse_bytes("2 TB") ... ok
> test_parse_512_mib (tests.test_helper.TestParseBytes.test_parse_512_mib)
> Test parse_bytes("512 MiB") ... ok
> test_isort (tests.test_isort.IsortTestCase.test_isort)
> Test: Run isort on Python source code. ... Running following command:
> isort --check-only --diff -l 99 image-factory tests
> ok
> test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
> Test: Run pylint on Python source code. ... Running following command:
> /usr/bin/python3 -m pylint --rcfile=/<>/tests/pylint.conf -- 
> image-factory tests
> FAIL
> test_chmod_dnf_log (tests.test_sudo_helper.TestSudoHelper.test_chmod_dnf_log)
> Test read access for dnf log file. ... ok
> test_chmod_log_file 
> (tests.test_sudo_helper.TestSudoHelper.test_chmod_log_file)
> Test read access for mounted /var/log/... ... ok
> test_chmod_recursive 
> (tests.test_sudo_helper.TestSudoHelper.test_chmod_recursive)
> Test chmod recursively ... ok
> test_chmod_remove_root 
> (tests.test_sudo_helper.TestSudoHelper.test_chmod_remove_root)
> Test chmod remove mounted /root permission ... ok
> test_chmod_root (tests.test_sudo_helper.TestSudoHelper.test_chmod_root)
> Test chmod mounted /root ... ok
> test_chmod_var_log (tests.test_sudo_helper.TestSudoHelper.test_chmod_var_log)
> Test write access for mounted /var/log/... ... ok
> test_mount (tests.test_sudo_helper.TestSudoHelper.test_mount)
> Test mounting. ... ok
> test_reject_escaping 
> (tests.test_sudo_helper.TestSudoHelper.test_reject_escaping)
> Test rejecting ../../etc/shadow. ... ok
> test_umount (tests.test_sudo_helper.TestSudoHelper.test_umount)
> Test unmounting. ... ok
> 
> ==
> FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
> Test: Run pylint on Python source code.
> --
> Traceback (most recent call last):
>   File "/<>/tests/test_pylint.py", line 74, in test_pylint
> self.fail("\n".join(msgs))
> AssertionError: pylint found issues:
> * Module image-factory
> image-factory:64:12: W0719: Raising too general exception: Exception 
> (broad-exception-raised)
> image-factory:138:8: W0719: Raising too general exception: Exception 
> (broad-exception-raised)
> image-factory:166:8: W0719: Raising too general exception: Exception 
> (broad-exception-raised)
> 
> --
> Ran 20 tests in 8.079s
> 
> FAILED (failures=1)
> make[1]: *** [Makefile:13: check] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 check returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2023/03/23/image-factory_1.0.2-1_testing.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230323;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230323=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1033423: lynx: Status line stuck on "HTTP/1.1 200 OK", body not rendered, no input accepted when receiving a specifically-formatted response

[наб]

Package: lynx
Version: 2.9.0dev.6-3~deb11u1
Version: 2.9.0dev.12-1
Severity: normal

Dear Maintainer,

The ESP-IDF code for the server is:
-- >8 --
static bool gpio_state = CONFIG_ESP32PSKO_INITIAL;

#define ROOT_GET_START \
"" \
"" \
"esp32psko" \
""   \
""  \
"Current:"
#define ROOT_GET_PART2 \
""   \
"New: " \
""  \
""


static esp_err_t http_root_get_handler(httpd_req_t *req)
{
httpd_resp_send_chunk(req, ROOT_GET_START, sizeof(ROOT_GET_START) - 1);
httpd_resp_send_chunk(req, gpio_state ? "UP" : "DOWN", 
HTTPD_RESP_USE_STRLEN);
httpd_resp_send_chunk(req, ROOT_GET_PART2, sizeof(ROOT_GET_PART2) - 1);
if(gpio_state)
httpd_resp_send_chunk(req, " checked", sizeof(" checked") - 1);
httpd_resp_send_chunk(req, ROOT_GET_PART3, sizeof(ROOT_GET_PART3) - 1);
return httpd_resp_send_chunk(req, NULL, 0);
}
-- >8 --
driven by the ESP HTTP server.

When I call this by running "lynx 192.168.1.136",
lynx shows "HTTP/1.1 200 OK" in the status line,
and the rest of the screen is black;
here's a video:
  
https://lfs.nabijaczleweli.xyz/0015-cohost-images/2023-03-24-1227171-uhhh-anyone-els-2023-03-24%2019-26-20.mp4

Naturally, this isn't an ergonomic way to test this, so here are two
recorded transactions, which behave identically:
-- >8 --
$ printf '%s\r\n' 'GET / HTTP/1.1' 'Host: 192.168.1.136' '' | nc -N 
192.168.1.136 80 | hd
  48 54 54 50 2f 31 2e 31  20 32 30 30 20 4f 4b 0d  |HTTP/1.1 200 OK.|
0010  0a 43 6f 6e 74 65 6e 74  2d 54 79 70 65 3a 20 74  |.Content-Type: t|
0020  65 78 74 2f 68 74 6d 6c  0d 0a 54 72 61 6e 73 66  |ext/html..Transf|
0030  65 72 2d 45 6e 63 6f 64  69 6e 67 3a 20 63 68 75  |er-Encoding: chu|
0040  6e 6b 65 64 0d 0a 0d 0a  33 35 0d 0a 3c 6d 65 74  |nked35..|
0060  3c 74 69 74 6c 65 3e 65  73 70 33 32 70 73 6b 6f  |esp32psko|
0070  3c 2f 74 69 74 6c 65 3e  43 75 72 72 65 6e 74 3a  |Current:|
0080  20 0d 0a 34 0d 0a 44 4f  57 4e 0d 0a 34 33 0d 0a  | ..4..DOWN..43..|
0090  3c 62 72 20 2f 3e 3c 66  6f 72 6d 20 6d 65 74 68  |N|
00b0  65 77 3a 20 3c 69 6e 70  75 74 20 74 79 70 65 3d  |ew: <|
0100  2f 66 6f 72 6d 3e 0d 0a  30 0d 0a 0d 0a   |/form>..0|
010d

$ printf '%s\r\n' 'GET / HTTP/1.1' 'Host: 192.168.1.136' '' | nc -N 
192.168.1.136 80 | hd
  48 54 54 50 2f 31 2e 31  20 32 30 30 20 4f 4b 0d  |HTTP/1.1 200 OK.|
0010  0a 43 6f 6e 74 65 6e 74  2d 54 79 70 65 3a 20 74  |.Content-Type: t|
0020  65 78 74 2f 68 74 6d 6c  0d 0a 54 72 61 6e 73 66  |ext/html..Transf|
0030  65 72 2d 45 6e 63 6f 64  69 6e 67 3a 20 63 68 75  |er-Encoding: chu|
0040  6e 6b 65 64 0d 0a 0d 0a  61 30 0d 0a 3c 6d 65 74  |nkeda0..|
0060  3c 6d 65 74 61 20 6e 61  6d 65 3d 76 69 65 77 70  |esp32ps|
00b0  6b 6f 3c 2f 74 69 74 6c  65 3e 3c 66 6f 72 6d 20  |koCurre|
00e0  6e 74 3a 3c 2f 74 64 3e  3c 74 64 3e 0d 0a 34 0d  |nt:..4.|
00f0  0a 44 4f 57 4e 0d 0a 36  30 0d 0a 3c 2f 74 64 3e  |.DOWN..60..|
0100  3c 2f 74 72 3e 3c 74 72  3e 3c 74 64 3e 3c 6c 61  |Ne|
0120  77 3a 3c 2f 6c 61 62 65  6c 3e 3c 2f 74 64 3e 3c  |w:<|
0130  74 64 3e 3c 69 6e 70 75  74 20 74 79 70 65 3d 63  |td> |
0180  3c 2f 74 64 3e 3c 2f 74  72 3e 3c 2f 74 61 62 6c  |..0|
01a0
-- >8 --

I get the same thing when I run
  echo 
485454502F312E3120323030204F4B0D0A436F6E74656E742D547970653A20746578742F68746D6C0D0A5472616E736665722D456E636F64696E673A206368756E6B65640D0A0D0A33350D0A3C6D65746120636861727365743D7574662D383E3C7469746C653E657370333270736B6F3C2F7469746C653E43757272656E743A200D0A340D0A444F574E0D0A34330D0A3C6272202F3E3C666F726D206D6574686F643D706F73743E3C6C6162656C3E4E65773A203C696E70757420747970653D636865636B626F78206E616D653D76616C75650D0A32640D0A3E3C2F6C6162656C3E3C696E70757420747970653D7375626D69742076616C75653D5365743E3C2F666F726D3E0D0A300D0A0D0A
 | base16 -d | nc -lp 8000
and open localhost:8000, for a cheaper repro.

Best,
наб

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

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

Versions of packages lynx depends on:
ii  libbsd0   0.11.3-1
ii  libbz2-1.01.0.8-4
ii  libc6 2.31-13+deb11u5
ii  libgnutls30   3.7.1-5+deb11u3
ii  libidn11  1.33-3
ii  libncursesw6  6.2+20201114-2
ii  libtinfo6 6.2+20201114-2
ii  lynx-common   2.9.0dev.6-3~deb11u1
ii  zlib1g1:1.2.11.dfsg-2+deb11u2

Versions of packages lynx recommends:
ii  

Bug#1033422: base-passwd: missing Build-Depends docbook

[henrynmail-deb...@yahoo.com]

Package: base-passwd
Version: 3.6.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Usertags: rebootstrap

Dear Maintainer,

build in a minimal build environmet fails for docbook2html.

# apt remove docbook && apt autoremove
# apt build-dep base-passwd
... some dependency installed ...
# dpkg-buildpackage -j1 -B "-Pnocheck noinsttest noudeb" -uc -us
...
make[3]: Entering directory '/tmp/base-passwd-3.6.1/doc'
docbook2html --nochunks users-and-groups.sgml
...
openjade:/tmp/base-passwd-3.6.1/doc/users-and-groups.sgml:1:54:W: 
cannotgenerate system identifier for public text "-//OASIS//DTD DocBookV4.2//EN"
openjade:/tmp/base-passwd-3.6.1/doc/users-and-groups.sgml:1:54:E:
reference to entity "BOOK" for which no system identifier could be generated
...
openjade:I: maximum number of errors (200) reached; change with -E
option
make[3]: *** [Makefile:455: users-and-groups.html] Error 8
make[3]: Leaving directory '/tmp/base-passwd-3.6.1/doc'
make[2]: *** [Makefile:524: all-recursive] Error 1
make[2]: Leaving directory '/tmp/base-passwd-3.6.1'
make[1]: *** [Makefile:348: all] Error 2
make[1]: Leaving directory '/tmp/base-passwd-3.6.1'
dh_auto_build: error: make -j1 returned exit code 2
make: *** [debian/rules:3: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned
exit status 2

Workaround:
After installing "docbook" it works.

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

Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: unable to detect

Versions of packages base-passwd depends on:
ii  libc6  2.36-8
ii  libdebconfclient0  0.267
ii  libselinux1    3.4-1+b5

Versions of packages base-passwd recommends:
ii  debconf [debconf-2.0]  1.5.82

base-passwd suggests no packages.

-- debconf information excluded

Bug#894098: gdm3: HDMI still buggy, DisplayPort not tested

[Bud Heal]

Package: gdm3
Version: 43.0-3
Followup-For: Bug #894098
X-Debbugs-Cc: budheal...@gmail.com

Dear Maintainer,

   * What led up to the situation?
Fresh install of bookworm weekly build (2023-03-20)
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
HDMI showed extended desktop in both the login screen and now after logged in. 
I will submit a separate bug report for the "Displays" accessory but its 
failures could show that gdm3 can lose the frame buffer addresses. If one 
changes the external display location, either or both displays may go dark, or 
the laptop's display can show enlarged pixels at a translated place with wrong 
colors (aha, I remember those fights with the frame buffers, long ago now) and 
the external monitor may be dark with only the cursor (mouse pointer) showing 
but not the windows being dragged around). We can't have gdm3 thinking it can 
scribble at the wrong location.
I did not check DisplayPort and will rummage around for a cable.
   * What was the outcome of this action?
When an HDMI-enabled display was plugged, it was shown as directly to the right 
of the internal laptop's display. Trying to move the display's location had 
unexpected results. The displays may go dark or the internal display may show 
artifccts and dragging fails in those cases.
   * What outcome did you expect instead?
Allow multiple displays extend the desktop display.

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

Kernel: Linux 6.1.0-6-amd64 (SMP w/20 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 gdm3 depends on:
ii  accountsservice  22.08.8-6
ii  adduser  3.131
ii  dbus [default-dbus-system-bus]   1.14.6-1
ii  dbus-bin 1.14.6-1
ii  dbus-daemon  1.14.6-1
ii  dconf-cli0.40.0-4
ii  dconf-gsettings-backend  0.40.0-4
ii  debconf [debconf-2.0]1.5.82
ii  gir1.2-gdm-1.0   43.0-3
ii  gnome-session [x-session-manager]43.0-1
ii  gnome-session-bin43.0-1
ii  gnome-session-common 43.0-1
ii  gnome-session-flashback [x-session-manager]  3.46.0-1
ii  gnome-settings-daemon43.0-4
ii  gnome-shell  43.3-3
ii  gnome-terminal [x-terminal-emulator] 3.46.8-1
ii  gsettings-desktop-schemas43.0-1
ii  libaccountsservice0  22.08.8-6
ii  libaudit11:3.0.9-1
ii  libc62.36-8
ii  libcanberra-gtk3-0   0.30-10
ii  libcanberra0 0.30-10
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgdm1  43.0-3
ii  libglib2.0-0 2.74.6-1
ii  libglib2.0-bin   2.74.6-1
ii  libgtk-3-0   3.24.37-2
ii  libgudev-1.0-0   237-2
ii  libkeyutils1 1.6.3-2
ii  libpam-modules   1.5.2-6
ii  libpam-runtime   1.5.2-6
ii  libpam-systemd [logind]  252.6-1
ii  libpam0g 1.5.2-6
ii  librsvg2-common  2.54.5+dfsg-1
ii  libselinux1  3.4-1+b5
ii  libsystemd0  252.6-1
ii  libx11-6 2:1.8.4-2
ii  libxau6  1:1.0.9-1
ii  libxcb1  1.15-1
ii  libxdmcp61:1.1.2-3
ii  marco [x-window-manager] 1.26.1-1
ii  mate-session-manager [x-session-manager] 1.26.0-1
ii  mate-terminal [x-terminal-emulator]  1.26.0-1
ii  metacity [x-window-manager]  1:3.46.1-1
ii  polkitd  122-3
ii  procps   2:4.0.2-3
ii  systemd-sysv 252.6-1
ii  ucf  3.0043+nmu1
ii  x11-common   1:7.7+23
ii  x11-xserver-utils7.7+9+b1

Versions of packages gdm3 recommends:
ii  at-spi2-core 2.46.0-5
ii  desktop-base 12.0.5
ii  gnome-session [x-session-manager]43.0-1
ii  gnome-session-flashback [x-session-manager]  3.46.0-1
ii  mate-session-manager [x-session-manager] 1.26.0-1

Bug#1033421: newt: nopython not full respected

[henrynmail-deb...@yahoo.com]

Package: newt
Version: 0.52.23-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: ftbfs patch
Usertags: rebootstrap

Dear Maintainer,

the build option "nopython" was not respected in all cases.
In rules exist a check for nopython in DEB_BUILD_PROFILES, but later in
Makefile.in it will overritten by setting PYTHONVERS again.
If libpython*-dev is not installed, the build breaks with

    Python.h: No such file or directory

The fail was detected by cross builing, but also exist in native builds.

# apt remove python3-all libpython3.11-dev libpython3.11-dbg python3-minimal
# dpkg-buildpackage -B "-Pnocheck noinsttest noudeb nopython" -uc -us
...
/bin/sh: 1: python3.11-config: not found
/bin/sh: 1: python3.11-config: not found
/bin/sh: 1: python3.11-config: not found
/bin/sh: 1: python3.11-config: not found
gcc -fPIC -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2
-I/usr/include/tcl8.6 -g -O2 -ffile-prefix-map=/tmp/newt/newt-0.52.23=.
-fstack-protector-strong -Wformat -Werror=format-security
-DMARCH="x86_64-linux-gnu" -fPIC -c -o python3.11/snack.o snack.c
snack.c:2:10: fatal error: Python.h: No such file or directory
    2 | #include "Python.h"
  |  ^~
compilation terminated.

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

Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: unable to detect




newt-nopython.patch
Description: Binary data

Bug#1033420: puppet-agent: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

[Paulo Henrique de Lima Santana]

Package: puppet-agent
Tags: l10n patch
Severity: wishlist

Hello,

Could you please update this Brazilian Portuguese translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and
tested with msgfmt and podebconf-display-po.

Kind regards.

--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450


pt_BR.po.gz
Description: application/gzip


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1033419: nvidia-graphics-drivers-tesla-460: [INTL:tr] turkish translation of debconf messages

[Atila KOÇ]

Package: nvidia-graphics-drivers-tesla-460
Version: N/A
Severity: wishlist
Tags: l10n patch

Hello,

Find attached the updated Turkish translation of the 
nvidia-graphics-drivers-tesla-460 debconf messages.
It has been submitted for review to the debian-l10n-turkish mailing 
list.

Please include it in your next upload.

Regards,
Atila KOÇ
--- YASAL UYARI ---

# Turkish debconf translation of nvidia-graphics-drivers
# This file is distributed under the same license as the nvidia-graphics-drivers package.
# Mert Dirik , 2014.
# Atila KOÇ , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: nvidia-graphics-drivers\n"
"Report-Msgid-Bugs-To: nvidia-graphics-driv...@packages.debian.org\n"
"POT-Creation-Date: 2016-02-12 01:57+0100\n"
"PO-Revision-Date: 2023-03-04 23:34+0300\n"
"Last-Translator: Atila KOÇ \n"
"Language-Team: Debian L10n Turkish \n"
"Language: tr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"

#. Type: boolean
#. Description
#. Translators, do not translate the ${substitution} ${variables}.
#. ${vendor} will be substituted with 'NVIDIA' or 'Fglrx' (without quotes, of
#. course), ${free_name} will become 'Nouveau' or 'Radeon' (no quotes, again)
#. and the ${*driver} variables will be replaced with package names.
#: ../nvidia-legacy-check.templates:3001
msgid "Install ${vendor} driver despite unsupported graphics card?"
msgstr "Grafik kartınızı desteklemediği halde ${vendor} sürücüsü kurulsun mu?"

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"This system has a graphics card which is no longer handled by the ${vendor} "
"driver (package ${driver}). You may wish to keep the package installed - for "
"instance to drive some other card - but the card with the following chipset "
"won't be usable:"
msgstr ""
"Sisteminizde (${driver} paketinin sağladığı) ${vendor} sürücüsüyle artık "
"yönetilmeyen bir grafik kartı var. Başka bir kartı sürmesi için paketi "
"kurulu durumda bırakabilirsiniz, fakat aşağıdaki yonga kümesini kullanan "
"kart bu sürücü ile kullanılamayacaktır:"

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"The above card requires either the non-free legacy ${vendor} driver (package "
"${legacy_driver}) or the free ${free_name} driver (package ${free_driver})."
msgstr ""
"Yukarıdaki kart ya özgür olmayan eski ${vendor} sürücüsünü (${legacy_driver} "
"paketi) ya da özgür ${free_name} sürücüsünü (${free_driver} paketi) "
"gerektirmektedir."

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"Use the update-glx command to switch between different installed drivers."
msgstr ""
"Farklı kurulu sürücüler arasında geçiş yapmak için update-glx komutunu "
"kullanın."

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"Before the ${free_name} driver can be used you must remove ${vendor} "
"configuration from xorg.conf (and xorg.conf.d/)."
msgstr ""
"${free_name} sürücüsünü kullanabilmek için önce xorg.conf (ve xorg.conf.d/) "
"konumundaki ${vendor} yapılandırmasını kaldırmanız gerekmektedir."

Bug#1033418: nvidia-graphics-drivers-tesla-510: [INTL:tr] turkish translation of debconf messages

[Atila KOÇ]

Package: nvidia-graphics-drivers-tesla-510
Version: N/A
Severity: wishlist
Tags: l10n patch

Hello,

Find attached the updated Turkish translation of the 
nvidia-graphics-drivers-tesla-510 debconf messages.
It has been submitted for review to the debian-l10n-turkish mailing 
list.

Please include it in your next upload.

Regards,
Atila KOÇ
--- YASAL UYARI ---

# Turkish debconf translation of nvidia-graphics-drivers
# This file is distributed under the same license as the nvidia-graphics-drivers package.
# Mert Dirik , 2014.
# Atila KOÇ , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: nvidia-graphics-drivers\n"
"Report-Msgid-Bugs-To: nvidia-graphics-driv...@packages.debian.org\n"
"POT-Creation-Date: 2023-01-09 15:40+0100\n"
"PO-Revision-Date: 2023-03-04 23:34+0300\n"
"Last-Translator: Atila KOÇ \n"
"Language-Team: Debian L10n Turkish \n"
"Language: tr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"

#. Type: boolean
#. Description
#. Translators, please only translate this file in src:nvidia-graphics-drivers.
#. From there it will be merged into all other src:nvidia-graphics-drivers-*
#. packages.
#. Translators, do not translate the ${substitution} ${variables}.
#. ${vendor} will be substituted with 'NVIDIA' or 'Fglrx' (without quotes, of
#. course), ${free_name} will become 'Nouveau' or 'Radeon' (no quotes, again)
#. and the ${*driver} variables will be replaced with package names.
#: ../nvidia-legacy-check.templates:3001
msgid "Install ${vendor} driver despite unsupported graphics card?"
msgstr "Grafik kartınızı desteklemediği halde ${vendor} sürücüsü kurulsun mu?"

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"This system has a graphics card which is no longer handled by the ${vendor} "
"driver (package ${driver}). You may wish to keep the package installed - for "
"instance to drive some other card - but the card with the following chipset "
"won't be usable:"
msgstr ""
"Sisteminizde (${driver} paketinin sağladığı) ${vendor} sürücüsüyle artık "
"yönetilmeyen bir grafik kartı var. Başka bir kartı sürmesi için paketi "
"kurulu durumda bırakabilirsiniz, fakat aşağıdaki yonga kümesini kullanan "
"kart bu sürücü ile kullanılamayacaktır:"

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"The above card requires either the non-free legacy ${vendor} driver (package "
"${legacy_driver}) or the free ${free_name} driver (package ${free_driver})."
msgstr ""
"Yukarıdaki kart ya özgür olmayan eski ${vendor} sürücüsünü (${legacy_driver} "
"paketi) ya da özgür ${free_name} sürücüsünü (${free_driver} paketi) "
"gerektirmektedir."

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"Use the update-glx command to switch between different installed drivers."
msgstr ""
"Farklı kurulu sürücüler arasında geçiş yapmak için update-glx komutunu "
"kullanın."

#. Type: boolean
#. Description
#: ../nvidia-legacy-check.templates:3001
msgid ""
"Before the ${free_name} driver can be used you must remove ${vendor} "
"configuration from xorg.conf (and xorg.conf.d/)."
msgstr ""
"${free_name} sürücüsünü kullanabilmek için önce xorg.conf (ve xorg.conf.d/) "
"konumundaki ${vendor} yapılandırmasını kaldırmanız gerekmektedir."

Bug#1033417: newt: missing Build-Depends docbook

[Henry N.]

Package: newt
Version: 0.52.23-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Usertags: rebootstrap

Dear Maintainer,

build in a minimal build environmet fails for docbook2html.

# apt source newt
# cd newt-0.52.23
# apt build-dep newt
... all dependency installed ...
# dpkg-buildpackage -B "-Pnocheck noinsttest noudeb" -uc -us
...
openjade:/tmp/newt-0.52.23/tutorial/../tutorial.sgml:1:61:W: cannot
generate system identifier for public text "-//Davenport//DTD DocBook
V3.0//EN"
openjade:/tmp/newt-0.52.23/tutorial/../tutorial.sgml:1:61:E: reference
to entity "ARTICLE" for which no system identifier could be generated
...
openjade:I: maximum number of errors (200) reached; change with -E
option
make[1]: *** [debian/rules:53: override_dh_auto_build] Error 8
make[1]: Leaving directory '/tmp/newt/newt-0.52.23'
make: *** [debian/rules:14: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned
exit status 2

Workaround: After installing "docbook" it works.

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

Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: unable to detect

Bug#1033401: unblock: src:dino-im/0.4.2-1

[Sebastian Ramacher]

Control: tags -1 moreinfo

On 2023-03-24 12:45:41 +, Martin wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Dear release team,
> 
> I like to get clearance for uploading dino-im 0.4.2 to unstable, to get
> it into bookworm.

Please go ahead and let us know once the package is available in
unstable.

Cheers

> 
> Upstream release text:
> 
> > Maintenance release with fix for CVE-2023-28686 and bug fixes.
> 
> There are eight commits, from which five should definitively go into
> bookworm (1, 2, 6, 7, 8). Two commits are not related to a bug report,
> but solve relevant problems (3, 4). Only one is not relevant at all, but
> it does not touch file we care about anyway (5).
> 
> There are no new features nor unnecessary changes, so I would very much
> prefer to get the new version in instead of adding five to seven
> patches.
> 
> Here is a description of the commits between 0.4.1 (now in testing) and
> 0.4.2 (to be uploaded):
> 
> 1. acf9c694 * Fix C binding for gst_video_frame_get_data
> Fix for: GTK4 - crash when answering video call #1267
> > Fix C binding for gst_video_frame_get_data
> https://github.com/dino/dino/issues/1267
> 
> 2. 89b9110f * Improve history sync
> Fix for: MUC MAM (0313) doesn't work #1386
> > - Ensure we fully fetch desired history if possible (previously, duplicates
> >   from offline message queue could hinder MAM sync)
> > - Early drop illegal MAM messages so they don't pile up in the pending queue
> >   waiting for their query to end (which it never will if they were not
> >   requested in first place).
> https://github.com/dino/dino/issues/1386
> 
> 3. 481a68fd * Improve database performance while reconnecting and syncing
> > Improve database performance while reconnecting and syncing
> > Also move some tasks to low priority idle queue so they won't block UI 
> > updates
> No bug report, but solves startup time issues some users reported.
> 
> 4. 1738bf8d * data: Set StartupNotify to true in .desktop file
> > data: Set StartupNotify to true in .desktop file
> > GTK handles startup notifications, so advertise it in desktop
> > file. This allows splash screens and other startup indications
> > in DEs to work.
> No bug report, but sounds like an issue worth solving.
> 
> 5. b6f9b54d * Remove gspell
> (not relevant to Debian: unused cmake/FindGspell.cmake removed, change
> in github ci file)
> 
> 6. 00482404 * Fix a crash if a message subnode is not found in a carbon
> Fix for: A carbon crashes Dino #1392
> > Fix a crash if a message subnode is not found in a carbon
> https://github.com/dino/dino/issues/1392
> 
> 7. 179c766d * Bind soup session lifetime to File provider/sender lifetime
> Fix for: Dino crashes when sending or receiving files #1395 
> > Bind soup session lifetime to File provider/sender lifetime
> > Required since libsoup 3.4. Fixes #1395
> https://github.com/dino/dino/issues/1395
> 
> 8. baf96d9d * @ v0.4.2 origin/v0.4 Check sender of bookmark:1 updates
> Fix for: dino-im: Insufficient message sender validation in Dino 
> CVE-2023-28686
> > Check sender of bookmark:1 updates
> https://bugs.debian.org/1033370
> 
> Thanks in advance for your comments and decision!
> 
> Cheers
> 
> unblock src:dino-im/0.4.2-1
> 

> diff -Nru dino-im-0.4.1/.github/workflows/build.yml 
> dino-im-0.4.2/.github/workflows/build.yml
> --- dino-im-0.4.1/.github/workflows/build.yml 2023-03-01 23:30:00.0 
> +
> +++ dino-im-0.4.2/.github/workflows/build.yml 2023-03-23 18:00:00.0 
> +
> @@ -7,7 +7,7 @@
>- uses: actions/checkout@v2
>- run: sudo apt-get update
>- run: sudo apt-get remove libunwind-14-dev
> -  - run: sudo apt-get install -y build-essential gettext cmake valac 
> libgee-0.8-dev libsqlite3-dev libgtk-4-dev libnotify-dev libgpgme-dev 
> libsoup2.4-dev libgcrypt20-dev libqrencode-dev libgspell-1-dev libnice-dev 
> libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libsrtp2-dev 
> libwebrtc-audio-processing-dev libadwaita-1-dev
> +  - run: sudo apt-get install -y build-essential gettext cmake valac 
> libgee-0.8-dev libsqlite3-dev libgtk-4-dev libnotify-dev libgpgme-dev 
> libsoup2.4-dev libgcrypt20-dev libqrencode-dev libnice-dev 
> libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libsrtp2-dev 
> libwebrtc-audio-processing-dev libadwaita-1-dev
>- run: ./configure --with-tests --with-libsignal-in-tree
>- run: make
>- run: build/xmpp-vala-test
> diff -Nru dino-im-0.4.1/VERSION dino-im-0.4.2/VERSION
> --- dino-im-0.4.1/VERSION 2023-03-01 23:30:00.0 +
> +++ dino-im-0.4.2/VERSION 2023-03-23 18:00:00.0 +
> @@ -1 +1 @@
> -RELEASE 0.4.1
> +RELEASE 0.4.2
> diff -Nru dino-im-0.4.1/cmake/FindGspell.cmake 
> dino-im-0.4.2/cmake/FindGspell.cmake
> --- dino-im-0.4.1/cmake/FindGspell.cmake  2023-03-01 23:30:00.0 
> +
> +++ dino-im-0.4.2/cmake/FindGspell.cmake  1970-01-01 

Bug#1033399: pre-approve unblock: tryton-server/6.0.29-2

[Sebastian Ramacher]

Control: tags -1 moreinfo

Hi Mathias

On 2023-03-24 13:07:57 +0100, Mathias Behrle wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: tryton-ser...@packages.debian.org
> Control: affects -1 + src:tryton-server
> 
> Please pre-approve the unblock of package tryton-server

Please go ahead and let us know once the package is available in
unstable.

Cheers

> 
> [ Reason ]
> This release targets several fixes that should go into bookworm:
> 
>   * Add missing quotes in maintainer scripts (Closes: #1033055).
>   * Make conf file parsing section aware (Closes: #1033055).
>   * Correct a variable typo (Closes: #1033055).
>   * Remove lsb-base from Depends.
> 
> 
> [ Impact ]
> There can be errors when using spaces or something alike in the debconf 
> related
> questions.
> 
> [ Tests ]
> Salsa CI tests are passing
> https://salsa.debian.org/tryton-team/tryton-server/-/pipelines/513249
> as well as all build tests.
> 
> I did a full manual test over all packages.
> 
> 
> [ Risks ]
> 
> The code changes are trivial enough to not expect regressions.
> 
> [ Checklist ]
>   [x] all changes are documented in the d/changelog
>   [x] I reviewed all changes and I approve them
>   [x] attach debdiff against the package in testing
> 
> 
> unblock tryton-server/6.0.29-2
> 
> 
> 
> -- 
> 
> Mathias Behrle
> PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
> AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6



-- 
Sebastian Ramacher

Bug#1033203: unblock: fuse3/3.14.0-3

[Sebastian Ramacher]

On 2023-03-19 17:22:21 +0100, László Böszörményi wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: Cyril Brulebois 
> Control: affects -1 + src:fuse3
> 
> Hi RMs,
> 
> [ Reason ]
> The self-testing of fuse3 only works on little-endian machines. I've
> already disabled it on big-endian release architectures. Missed hppa
> which is not added to the list.
> Compiling examples didn't work due to outdated Makefile and using an
> outdated header name in one of the files.
> 
> [ Impact ]
> With the changes fuse3 is compiled on hppa now. As the installer needs
> its udeb it can be created on that architecture as well from now on.
> One of the example files was patched to use the current header file
> name and now compiles with all of the other example files.

hppa is not a release architecture, so that wouldn't count as a
targetted fix. But since it comes with a documentation fix, I'll unblock
it.

Cheers

> 
> [ Tests ]
> I've tested the examples compilation and those are OK now. Compilation
> on hppa is now working as can be seen in the buildd logs [1].
> 
> [ Risks ]
> None of the changes affect the working of the package itself.
> As fuse3 has an udeb I put kibi to the loop if extra ACK is needed.
> 
> [ Checklist ]
>   [X] all changes are documented in the d/changelog
>   [X] I reviewed all changes and I approve them
>   [X] attach debdiff against the package in testing
> 
> unblock fuse3/3.14.0-3
> 
> Thanks for considering,
> Laszlo/GCS
> [1] https://buildd.debian.org/status/logs.php?pkg=fuse3=hppa

> diff -Nru fuse3-3.14.0/debian/changelog fuse3-3.14.0/debian/changelog
> --- fuse3-3.14.0/debian/changelog 2023-02-18 07:22:30.0 +0100
> +++ fuse3-3.14.0/debian/changelog 2023-03-17 20:51:05.0 +0100
> @@ -1,3 +1,15 @@
> +fuse3 (3.14.0-3) unstable; urgency=medium
> +
> +  [ Helge Deller  ]
> +  * Add the big-endian hppa platform to the disabled self-testing list
> +(closes: #1032187).
> +
> +  [ Laszlo Boszormenyi (GCS) ]
> +  * Update fuse header name in examples.
> +  * Fix Makefile for examples (closes: #1031544).
> +
> + -- Laszlo Boszormenyi (GCS)   Fri, 17 Mar 2023 20:51:05 
> +0100
> +
>  fuse3 (3.14.0-2) unstable; urgency=medium
>  
>* Revert upgrade of fuse_kernel.h for not being upstreamed yet
> diff -Nru fuse3-3.14.0/debian/examples/Makefile 
> fuse3-3.14.0/debian/examples/Makefile
> --- fuse3-3.14.0/debian/examples/Makefile 2014-06-20 08:23:50.0 
> +0200
> +++ fuse3-3.14.0/debian/examples/Makefile 2023-03-17 20:51:05.0 
> +0100
> @@ -1,12 +1,16 @@
> -CFLAGS := -Wall $(shell pkg-config fuse --cflags)
> -LDFLAGS := $(shell pkg-config fuse --libs)
> +CFLAGS := -Wall $(shell pkg-config fuse3 --cflags)
> +LDFLAGS := $(shell pkg-config fuse3 --libs)
>  
> -targets = fusexmp fusexmp_fh hello hello_ll null
> +targets = cuse cuse_client hello hello_ll \
> +  invalidate_path ioctl ioctl_client \
> +  notify_inval_entry notify_inval_inode notify_store_retrieve \
> +  null passthrough passthrough_fh passthrough_ll \
> +  poll poll_client printcap
>  
> -all: $(targets)
> +%: %.c
> + $(CC) $(CFLAGS) $< -o $@ $(LDFLAGS)
>  
> -fusexmp_fh: fusexmp_fh.c
> - $(CC) $(CFLAGS) $(LDFLAGS) -lulockmgr $< -o $@
> +all: $(targets)
>  
>  clean:
>   rm -f *.o
> diff -Nru fuse3-3.14.0/debian/patches/series 
> fuse3-3.14.0/debian/patches/series
> --- fuse3-3.14.0/debian/patches/series2023-02-18 07:22:30.0 
> +0100
> +++ fuse3-3.14.0/debian/patches/series2023-03-17 20:51:05.0 
> +0100
> @@ -1 +1,2 @@
>  revert_upgrade_of_fuse_kernel.h.patch
> +update_header_name.patch
> diff -Nru fuse3-3.14.0/debian/patches/update_header_name.patch 
> fuse3-3.14.0/debian/patches/update_header_name.patch
> --- fuse3-3.14.0/debian/patches/update_header_name.patch  1970-01-01 
> 01:00:00.0 +0100
> +++ fuse3-3.14.0/debian/patches/update_header_name.patch  2023-03-17 
> 20:51:05.0 +0100
> @@ -0,0 +1,21 @@
> +Description: use new header name of fuse
> + Just rename fuse_config.h to libfuse_config.h
> +Author: Laszlo Boszormenyi (GCS) 
> +Bug-Debian: https://bugs.debian.org/1031544
> +Forwarded: no
> +Last-Update: 2023-03-17
> +
> +---
> +
> +
> +--- fuse3-3.14.0.orig/example/poll_client.c
>  fuse3-3.14.0/example/poll_client.c
> +@@ -19,7 +19,7 @@
> +  * \include poll_client.c
> +  */
> + 
> +-#include 
> ++#include 
> + 
> + #include 
> + #include 
> diff -Nru fuse3-3.14.0/debian/rules fuse3-3.14.0/debian/rules
> --- fuse3-3.14.0/debian/rules 2023-01-22 08:17:08.0 +0100
> +++ fuse3-3.14.0/debian/rules 2023-03-17 20:51:05.0 +0100
> @@ -54,7 +54,7 @@
>  
>  override_dh_auto_test:
>  ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
> -ifeq (,$(findstring $(DEB_BUILD_ARCH),powerpc ppc64 sparc64 s390x))
> +ifeq (,$(findstring $(DEB_BUILD_ARCH),powerpc ppc64 sparc64 s390x hppa))
>   

Bug#1033374: pre-unblock: ruby-rack/2.2.6.4-1

[Sebastian Ramacher]

Control: tags -1 moreinfo

On 2023-03-24 01:50:25 +0530, Pirate Praveen wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: ruby-r...@packages.debian.org
> Control: affects -1 + src:ruby-rack
> 
> Please see these changes for ruby-rack (I have not uploaded yet) is ok.

Please go ahead and let us know once the package is available in
unstable.

Cheers

> 
> [ Reason ]
> It fixes two CVEs (though it includes some other bug fixes too)
> 
> [ Impact ]
> Some of the changes included in this release are already included in the
> debian package as patches, this just reduces maintenance effort.
> 
> [ Tests ]
> Upstream testsuite passes, gitlab is already using the 2.2.6.4 version.
> 
> [ Risks ]
> If this is not unblocked, two CVEs would have to be backported to 2.2.4
> 
> 
> [ Checklist ]
>  [x] all changes are documented in the d/changelog
>  [x] I reviewed all changes and I approve them
>  [x] attach debdiff against the package in testing
> 
> [ Other info ]
> 
> unblock ruby-rack/2.2.6.4-1
> 
> 
> diff -Nru ruby-rack-2.2.4/CHANGELOG.md ruby-rack-2.2.6.4/CHANGELOG.md
> --- ruby-rack-2.2.4/CHANGELOG.md  2022-07-01 03:48:29.0 +0530
> +++ ruby-rack-2.2.6.4/CHANGELOG.md2023-03-13 23:37:51.0 +0530
> @@ -2,6 +2,33 @@
>  
>  All notable changes to this project will be documented in this file. For 
> info on how to format all future additions to this file please reference 
> [Keep A Changelog](https://keepachangelog.com/en/1.0.0/).
>  
> +## [2.2.6.4] - 2023-03-13
> +
> +- [CVE-2023-27539] Avoid ReDoS in header parsing
> +
> +## [2.2.6.3] - 2023-03-02
> +
> +- [CVE-2023-27530] Introduce multipart_total_part_limit to limit total parts
> +
> +## [2.2.6.2] - 2022-01-17
> +
> +- [CVE-2022-44570] Fix ReDoS in Rack::Utils.get_byte_ranges
> +
> +## [2.2.6.1] - 2022-01-17
> +
> +- [CVE-2022-44571] Fix ReDoS vulnerability in multipart parser
> +- [CVE-2022-44572] Forbid control characters in attributes (also ReDoS)
> +
> +## [2.2.6] - 2022-01-17
> +
> +- Extend `Rack::MethodOverride` to handle `QueryParser::ParamsTooDeepError` 
> error. ([#2011](https://github.com/rack/rack/pull/2011), 
> [@byroot](https://github.com/byroot))
> +
> +## [2.2.5] - 2022-12-27
> +
> +### Fixed
> +
> +- `Rack::URLMap` uses non-deprecated form of `Regexp.new`. 
> ([#1998](https://github.com/rack/rack/pull/1998), 
> [@weizheheng](https://github.com/weizheheng))
> +
>  ## [2.2.4] - 2022-06-30
>  
>  - Better support for lower case headers in `Rack::ETag` middleware. 
> ([#1919](https://github.com/rack/rack/pull/1919), 
> [@ioquatix](https://github.com/ioquatix))
> diff -Nru ruby-rack-2.2.4/debian/changelog ruby-rack-2.2.6.4/debian/changelog
> --- ruby-rack-2.2.4/debian/changelog  2023-02-09 16:17:17.0 +0530
> +++ ruby-rack-2.2.6.4/debian/changelog2023-03-24 01:32:43.0 
> +0530
> @@ -1,3 +1,10 @@
> +ruby-rack (2.2.6.4-1) unstable; urgency=medium
> +
> +  * Team Upload
> +  * New upstream version 2.2.6.4 (Fixes: CVE-2023-27530, CVE-2023-27539)
> +
> + -- Pirate Praveen   Fri, 24 Mar 2023 01:32:43 +0530
> +
>  ruby-rack (2.2.4-3) unstable; urgency=high
>  
>* Team upload
> diff -Nru 
> ruby-rack-2.2.4/debian/patches/Fix-ReDoS-in-Rack-Utils.get_byte_ranges.patch 
> ruby-rack-2.2.6.4/debian/patches/Fix-ReDoS-in-Rack-Utils.get_byte_ranges.patch
> --- 
> ruby-rack-2.2.4/debian/patches/Fix-ReDoS-in-Rack-Utils.get_byte_ranges.patch  
> 2023-02-09 16:17:17.0 +0530
> +++ 
> ruby-rack-2.2.6.4/debian/patches/Fix-ReDoS-in-Rack-Utils.get_byte_ranges.patch
> 1970-01-01 05:30:00.0 +0530
> @@ -1,26 +0,0 @@
>  a/lib/rack/utils.rb
> -+++ b/lib/rack/utils.rb
> -@@ -348,17 +348,18 @@
> -   return nil unless http_range && http_range =~ /bytes=([^;]+)/
> -   ranges = []
> -   $1.split(/,\s*/).each do |range_spec|
> --return nil  unless range_spec =~ /(\d*)-(\d*)/
> --r0, r1 = $1, $2
> --if r0.empty?
> --  return nil  if r1.empty?
> -+return nil unless range_spec.include?('-')
> -+range = range_spec.split('-')
> -+r0, r1 = range[0], range[1]
> -+if r0.nil? || r0.empty?
> -+  return nil if r1.nil?
> -   # suffix-byte-range-spec, represents trailing suffix of file
> -   r0 = size - r1.to_i
> -   r0 = 0  if r0 < 0
> -   r1 = size - 1
> - else
> -   r0 = r0.to_i
> --  if r1.empty?
> -+  if r1.nil?
> - r1 = size - 1
> -   else
> - r1 = r1.to_i
> diff -Nru 
> ruby-rack-2.2.4/debian/patches/Fix-ReDoS-vulnerability-in-multipart-parser.patch
>  
> ruby-rack-2.2.6.4/debian/patches/Fix-ReDoS-vulnerability-in-multipart-parser.patch
> --- 
> ruby-rack-2.2.4/debian/patches/Fix-ReDoS-vulnerability-in-multipart-parser.patch
>   2023-02-09 16:17:17.0 +0530
> +++ 
> 

Bug#1033416: unblock: fakeroot/1.31-1.2

[Helge Kreutzmann]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: faker...@packages.debian.org
Control: affects -1 + src:fakeroot

Please unblock package fakeroot

(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)

[ Reason ]
Updated Portuguese and German man page translations.

There is no code change at all. All autopkgtest keep on passing.

[ Impact ]
German and Portuguese users will have a partial english man page.

[ Tests ]
Fakeroot uses autopkgtest. However, the man page generation is not
under test. I looked at the German man pages. Also lintian performs 
some checks on man pages.

[ Risks ]
I don't know any. The exact same code is already in Testing/bookworm.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
The man page translations were outdated. Initially I added them in
early January with the maintainer approval, however, in subsequent
uploads the update somehow got lost. So they were already in Sid for ~
1 month without any problem.


unblock fakeroot/1.31-1.2

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/
diff -Nru fakeroot-1.31/debian/changelog fakeroot-1.31/debian/changelog
--- fakeroot-1.31/debian/changelog  2023-03-02 07:44:38.0 +0100
+++ fakeroot-1.31/debian/changelog  2023-03-18 10:22:00.0 +0100
@@ -1,3 +1,14 @@
+fakeroot (1.31-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload with maintainer approval.
+  * Update manpage translation
+- German translation.
+  Thanks Erik Pfannenstein (Closes: #977854)
+- Portuguese translation.
+  Thanks Américo Monteiro (Closes: #1000794)
+
+ -- Helge Kreutzmann   Sat, 18 Mar 2023 10:22:00 +0100
+
 fakeroot (1.31-1.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru fakeroot-1.31/debian/patches/man_de.patch 
fakeroot-1.31/debian/patches/man_de.patch
--- fakeroot-1.31/debian/patches/man_de.patch   1970-01-01 01:00:00.0 
+0100
+++ fakeroot-1.31/debian/patches/man_de.patch   2023-03-18 10:22:00.0 
+0100
@@ -0,0 +1,419 @@
+Subject: German translation for the manpage (po4a)
+Author: Pfannenstein Erik 
+Date: 2020-12-21
+Bug-Debian: https://bugs.debian.org/977854
+Forwarded: No
+
+I have updated the German translation of fakeroot's manpage.
+Please include it into the package as you see fit.
+
+--- a/doc/po4a/po/de.po
 b/doc/po4a/po/de.po
+@@ -3,20 +3,22 @@
+ #   2009 Regis Duchesne.
+ # This file is distributed under the same license as the fakeroot package.
+ # Copyright (C) of this file 2011 Chris Leick.
++# Copyright (C) of this file 2020 Erik Pfannenstein.
+ #
+ msgid ""
+ msgstr ""
+ "Project-Id-Version: fakeroot 1.18.1-1\n"
+ "Report-Msgid-Bugs-To: faker...@packages.debian.org\n"
+ "POT-Creation-Date: 2020-09-22 16:23-0400\n"
+-"PO-Revision-Date: 2011-10-18 23:27+0200\n"
+-"Last-Translator: Chris Leick \n"
++"PO-Revision-Date: 2020-10-06 01:14+0200\n"
++"Last-Translator: Erik Pfannnenstein \n"
+ "Language-Team: 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: Poedit 2.4.1\n"
+ 
+ # type: TH
+ #. type: TH
+@@ -29,7 +31,7 @@
+ #: ../doc/fakeroot.1:16
+ #, no-wrap
+ msgid "5 October 2014"
+-msgstr ""
++msgstr "5. Oktober 2014"
+ 
+ # type: TH
+ #. type: TH
+@@ -46,8 +48,8 @@
+ msgstr "Debian-Handbuch"
+ 
+ # type: SH
+-#.  Manpage by J.H.M. Dassen 
+-#.  and Clint Adams
++#. Manpage by J.H.M. Dassen 
++#. and Clint Adams
+ #. type: SH
+ #: ../doc/fakeroot.1:19 ../doc/faked.1:19
+ #, no-wrap
+@@ -62,7 +64,7 @@
+ "manipulation"
+ msgstr ""
+ "fakeroot - einen Befehl zur Dateimanipulation in einer Umgebung mit "
+-"gefälschten Root-Rechten ausführen"
++"fingierten Root-Rechten ausführen"
+ 
+ # type: SH
+ #. type: SH
+@@ -80,7 +82,7 @@
+ "fd-base ]> B<[-h|--help ]> B<[-v|--version ]> B<[--]> B<[command]>"
+ msgstr ""
+ "B B<[-l|--lib> I B<[--faked> "
+-"IB<]> B<[-i> IB<]> B<[-s> "
++"IB<]> B<[-i> IB<]> B<[-s> "
+ "IB<]> B<[-u|--unknown-is-real ]> B<[-b|--fd-base ]> "
+ "B<[-h|--help ]> B<[-v|--version ]> B<[--]> B<[Befehl]>"
+ 
+@@ -104,24 +106,17 @@
+ "construct the archives directly, without using the archiver."
+ msgstr ""
+ "B führt einen Befehl in einer Umgebung aus, in der es scheint, als 
"
+-"habe er Root-Rechte zur Dateimanipulation. Dies ist nützlich, um Benutzern "
+-"zu erlauben Archive (tar, ar, .deb etc.) mit Dateien darin zu erstellen, die 
"
+-"Root-Rechte 

Bug#1033415: micro: syntax highlighting doesn't work

[Sebastian Hörberg]

Package: micro
Version: 2.0.11-1+b1
Severity: normal

Dear Maintainer,

After installing micro from bookwork repos syntax highlighting and file 
type specific files does not load.
All files use the terminal's colour scheme and it reports all file types 
as 'unknown'.


The static binary from upstream's github works as expected.

Could the debian package be missing the resource files?

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

Kernel: Linux 6.1.0-6-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

micro depends on no packages.

Versions of packages micro recommends:
ii xclip 0.13-2

micro suggests no packages.

-- no debconf information

Bug#1033414: tgt: localtgt autopkgtest depends on fio-examples

[Danilo Egea Gondolfo]

Package: tgt
Version: 1:1.0.85-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch

Dear Maintainer,

please consider adding "fio-examples" as a dependency of the localtgt
autopkgtest. It is required by the test.

With the new "fio" package (our version is 3.33-3), the tgt's localtgt
autopkgtest requires "fio-examples" to work. Apparently this test is
being skipped on Debian, but it's executed on Ubuntu.

Thanks for considering the patch.


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

Kernel: Linux 6.2.0-18-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru tgt-1.0.85/debian/tests/control tgt-1.0.85/debian/tests/control
--- tgt-1.0.85/debian/tests/control 2023-01-09 11:58:58.0 -0300
+++ tgt-1.0.85/debian/tests/control 2023-03-23 16:46:49.0 -0300
@@ -6,5 +6,5 @@
 Restrictions: needs-root isolation-container allow-stderr
 
 Tests: localtgt
-Depends: tgt, open-iscsi, fio
+Depends: tgt, open-iscsi, fio, fio-examples
 Restrictions: needs-root isolation-machine allow-stderr

Bug#973414: rustc: produces non-baseline opcodes for compiler_builtins::int::udiv::__udivmoddi4 on i386

[James Addison]

Package: rustc
Followup-For: Bug #973414

> On Fri, 24 Mar 2023 14:23:18 +, James wrote:
> > In particular, one area to look at:
> >
> >   
> > https://github.com/llvm/llvm-project/blob/llvmorg-14.0.6/clang/lib/Driver/ToolChains/Arch/X86.cpp#L25-L70
>
> Line range correction:
>
>   
> https://github.com/llvm/llvm-project/blob/llvmorg-14.0.6/clang/lib/Driver/ToolChains/Arch/X86.cpp#L25-L115

Hmm.. we already patch the default CPU fallback (and have done since LLVM 7):

https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/blob/14/debian/patches/clang-baseline-fix-i386.patch

Bug#1020467: Ready to Implement

[Soren Stoutner]

The dependencies are finally in place so this can be implemented.

To make things simpler for dictionary packagers, we are using a virtual package 
and an 
unversioned path for the conversion tool so that dictionary packagers don’t 
have to make 
modifications to their packages when the versions of Qt change in Debian.

All you should need to do is the following:

1.  Build-depend on `convert-bdic`.
2.  Use /usr/bin/convert-bdic to do the dictionary conversion.
3.  Place the .bdic files in /usr/share/hunspell-bdic.

More detailed information can be found in the dictionary packager documentation 
at:

file:///usr/share/doc/dictionaries-common-dev/dsdt-policy.html#hunspell-bdic

Thanks,

Soren

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


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

Bug#1033413: ITP: profile-cleaner -- Reduces browser profile size by cleaning their sqlite databases

[Peter Blackman]

Package: wnpp
Severity: wishlist
Owner: Peter 
X-Debbugs-Cc: debian-de...@lists.debian.org, pe...@pblackman.plus.com

* Package name    : profile-cleaner
  Version : 2.44
* URL : https://github.com/graysky2/profile-cleaner
* License : Expat
  Programming Lang: Bash
  Description : Reduces browser profile size by cleaning their sqlite 
databases


 Reduces the size of browser profiles by organizing their sqlite databases
 using sqlite3's vacuum and reindex functions.

 The term "browser" is used loosely since profile-cleaner happily works
 on some email clients and newsreaders too.


I will maintain the package myself, and will need a sponsor.

Bug#1033408: apache2: Segmentation fault + 503 on frontpage on 2.4.56-1

[Fabien LE BERRE]

Yes it does look like the bug. The Backtrace looks a lot like the coredump
I've seen.
Thanks for the heads up. Looking forward for the patch to be applied
officially.



Le ven. 24 mars 2023 à 17:06, 'Stefan Eissing' via Sysadmin <
sysad...@dutiko.com> a écrit :

> Might be related to https://bz.apache.org/bugzilla/show_bug.cgi?id=66539
>
> > Am 24.03.2023 um 15:30 schrieb root :
> >
> > Package: apache2
> > Version: 2.4.56-1~deb11u1
> > Severity: important
> > X-Debbugs-Cc: t...@security.debian.org
> >
> > Unattended-upgrades applied this new version on 22 march @ 6AM. Had
> > Segmentation faults since then, 503 for customers on websites. Since we
> > reverted back to 2.4.54, we've no more issues. Couldn't make any sense
> > of coredump but can provide one if necessary.
> >
> >
> > -- Package-specific info:
> >
> > -- 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-18-amd64 (SMP w/32 CPU threads)
> > 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 apache2 depends on:
> > ii  apache2-bin  2.4.56-1~deb11u1
> > ii  apache2-data 2.4.56-1~deb11u1
> > ii  apache2-utils2.4.56-1~deb11u1
> > ii  dpkg 1.20.12
> > ii  init-system-helpers  1.60
> > ii  lsb-base 11.1.0
> > ii  mime-support 3.66
> > ii  perl 5.32.1-4+deb11u2
> > ii  procps   2:3.3.17-5
> >
> > Versions of packages apache2 recommends:
> > ii  ssl-cert  1.1.0+nmu1
> >
> > Versions of packages apache2 suggests:
> > pn  apache2-doc  
> > pn  apache2-suexec-pristine | apache2-suexec-custom  
> > ii  lynx [www-browser]   2.9.0dev.6-3~deb11u1
> >
> > Versions of packages apache2-bin depends on:
> > ii  libapr1  1.7.0-6+deb11u2
> > ii  libaprutil1  1.6.1-5+deb11u1
> > ii  libaprutil1-dbd-sqlite3  1.6.1-5+deb11u1
> > ii  libaprutil1-ldap 1.6.1-5+deb11u1
> > ii  libbrotli1   1.0.9-2+b2
> > ii  libc62.31-13+deb11u5
> > ii  libcrypt11:4.4.18-4
> > ii  libcurl4 7.74.0-1.3+deb11u7
> > ii  libjansson4  2.13.1-1.1
> > ii  libldap-2.4-22.4.57+dfsg-3+deb11u1
> > ii  liblua5.3-0  5.3.3-1.1+b1
> > ii  libnghttp2-141.43.0-1
> > ii  libpcre3 2:8.44-2+0~20210301.9+debian11~1.gbpa278ad
> > ii  libssl1.11.1.1n-0+deb11u4
> > ii  libxml2
> 2.9.14+dfsg-0+0~20220524.12+debian11~1.gbpc5dc45
> > ii  perl 5.32.1-4+deb11u2
> > ii  zlib1g   1:1.2.11.dfsg-2+deb11u2
> >
> > Versions of packages apache2-bin suggests:
> > pn  apache2-doc  
> > pn  apache2-suexec-pristine | apache2-suexec-custom  
> > ii  lynx [www-browser]   2.9.0dev.6-3~deb11u1
> >
> > Versions of packages apache2 is related to:
> > ii  apache2  2.4.56-1~deb11u1
> > ii  apache2-bin  2.4.56-1~deb11u1
> >
> > -- Configuration Files:
> > /etc/apache2/apache2.conf changed [not included]
> > /etc/apache2/mods-available/mpm_event.conf changed [not included]
> > /etc/apache2/ports.conf changed [not included]
> > /etc/apache2/sites-available/000-default.conf changed [not included]
> >
> > -- no debconf information
> >
>
>

-- 
*Fabien Le Berre** Homme de la situation*
01 86 95 54 04 - 37 rue des Mathurins - 75008 Paris

Bug#1033408: apache2: Segmentation fault + 503 on frontpage on 2.4.56-1

[Stefan Eissing]

Might be related to https://bz.apache.org/bugzilla/show_bug.cgi?id=66539

> Am 24.03.2023 um 15:30 schrieb root :
> 
> Package: apache2
> Version: 2.4.56-1~deb11u1
> Severity: important
> X-Debbugs-Cc: t...@security.debian.org
> 
> Unattended-upgrades applied this new version on 22 march @ 6AM. Had
> Segmentation faults since then, 503 for customers on websites. Since we
> reverted back to 2.4.54, we've no more issues. Couldn't make any sense
> of coredump but can provide one if necessary.
> 
> 
> -- Package-specific info:
> 
> -- 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-18-amd64 (SMP w/32 CPU threads)
> 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 apache2 depends on:
> ii  apache2-bin  2.4.56-1~deb11u1
> ii  apache2-data 2.4.56-1~deb11u1
> ii  apache2-utils2.4.56-1~deb11u1
> ii  dpkg 1.20.12
> ii  init-system-helpers  1.60
> ii  lsb-base 11.1.0
> ii  mime-support 3.66
> ii  perl 5.32.1-4+deb11u2
> ii  procps   2:3.3.17-5
> 
> Versions of packages apache2 recommends:
> ii  ssl-cert  1.1.0+nmu1
> 
> Versions of packages apache2 suggests:
> pn  apache2-doc  
> pn  apache2-suexec-pristine | apache2-suexec-custom  
> ii  lynx [www-browser]   2.9.0dev.6-3~deb11u1
> 
> Versions of packages apache2-bin depends on:
> ii  libapr1  1.7.0-6+deb11u2
> ii  libaprutil1  1.6.1-5+deb11u1
> ii  libaprutil1-dbd-sqlite3  1.6.1-5+deb11u1
> ii  libaprutil1-ldap 1.6.1-5+deb11u1
> ii  libbrotli1   1.0.9-2+b2
> ii  libc62.31-13+deb11u5
> ii  libcrypt11:4.4.18-4
> ii  libcurl4 7.74.0-1.3+deb11u7
> ii  libjansson4  2.13.1-1.1
> ii  libldap-2.4-22.4.57+dfsg-3+deb11u1
> ii  liblua5.3-0  5.3.3-1.1+b1
> ii  libnghttp2-141.43.0-1
> ii  libpcre3 2:8.44-2+0~20210301.9+debian11~1.gbpa278ad
> ii  libssl1.11.1.1n-0+deb11u4
> ii  libxml2  2.9.14+dfsg-0+0~20220524.12+debian11~1.gbpc5dc45
> ii  perl 5.32.1-4+deb11u2
> ii  zlib1g   1:1.2.11.dfsg-2+deb11u2
> 
> Versions of packages apache2-bin suggests:
> pn  apache2-doc  
> pn  apache2-suexec-pristine | apache2-suexec-custom  
> ii  lynx [www-browser]   2.9.0dev.6-3~deb11u1
> 
> Versions of packages apache2 is related to:
> ii  apache2  2.4.56-1~deb11u1
> ii  apache2-bin  2.4.56-1~deb11u1
> 
> -- Configuration Files:
> /etc/apache2/apache2.conf changed [not included]
> /etc/apache2/mods-available/mpm_event.conf changed [not included]
> /etc/apache2/ports.conf changed [not included]
> /etc/apache2/sites-available/000-default.conf changed [not included]
> 
> -- no debconf information
> 

Bug#1033412: bullseye-pu: package libdatetime-timezone-perl/1:2.47-1+2023b

[gregor herrmann]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: libdatetime-timezone-p...@packages.debian.org, 
debian-p...@lists.debian.org
Control: affects -1 + src:libdatetime-timezone-perl

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I've uploaded libdatetime-timezone-perl/1:2.47-1+2023b to bullseye,
with the changes from the Olson db 2023b release included as a new
quilt patch.


tzdata changes:

2023a:
Egypt now uses DST again, from April through October.
This year Morocco springs forward April 23, not April 30.
Palestine delays the start of DST this year.
Much of Greenland still uses DST from 2024 on.

2023b:
Lebanon delays the start of DST this year.


Manually stripped down debdiff attached.


Thanks in advacne,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmQdzJxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbX8xAAwcp/vWGgjoaZg/Z8nvkRaaGcheJh5ZjQAz5bV7Qdq0NIINPzFVI+qQ3f
bXPUfTxjYRuYln7defgYxpeFkze30temxzLmhZxFq65BlR3ELqnrNTo95FSfA+lR
S5loojeFgTO3ZSMU/1KcjawF4G6jLXqPef4cO/7IC66OY32Z3JbWpK86KyJImO3D
/dohaZ3NFhvTZPWbkQGePFTCQEk0yOtvs7PwIcH3chXhVbeIWxxF9H96QuOQZk/z
5kcQBljccNSh0b5B0yuXhcUTn6o/MR/lmr8luJgTZNbe+p79cnwyzssNJLrAX6OK
rUNBIkfZypZ1kanuR+ZqbWjO3sv/hcHLXrad5A1Ldd1l7QnX7wFHXiyaBjvBmhtB
XFd/1ZzRC1S6P8Co0+3fOaylziGFL4vkZ89JO4//MZfr76iPxodSisQlP9aW4cPI
r9rn7BuQKbTzcdoZW8Oeui2nwgv/gXfBxIaLeAtQE1vsrgTi8wa2/cBb+IlNyeSR
XCwIMx6FReZ1qp2Q+C8iMmeKRv+w2judEOmXglyt538J4l7juIhjv2mVCZRah7rQ
5ZI/nZws8PhGxR622Q/P7VwC/wfkjeCVNXWoGICoqByZ0OHtFhF2FX1/Dc+s+XqN
AYo2er4wwv2rmbf5zygNY/CigSgWI4fp9ydfmqV2mFW9HmzOmDA=
=hp+9
-END PGP SIGNATURE-
diff -Nru libdatetime-timezone-perl-2.47/debian/changelog 
libdatetime-timezone-perl-2.47/debian/changelog
--- libdatetime-timezone-perl-2.47/debian/changelog 2022-11-30 
18:14:07.0 +0100
+++ libdatetime-timezone-perl-2.47/debian/changelog 2023-03-24 
16:58:22.0 +0100
@@ -1,3 +1,11 @@
+libdatetime-timezone-perl (1:2.47-1+2023b) bullseye; urgency=medium
+
+  * Update data to Olson database version 2023b.
+This update contains contemporary changes for Egypt, Greenland, Morocco,
+and Palestine (2023a), and for Lebanon (2023b).
+
+ -- gregor herrmann   Fri, 24 Mar 2023 16:58:22 +0100
+
 libdatetime-timezone-perl (1:2.47-1+2022g) bullseye; urgency=medium
 
   * Update data to Olson database version 2022g.
diff -Nru libdatetime-timezone-perl-2.47/debian/patches/olson-2023b 
libdatetime-timezone-perl-2.47/debian/patches/olson-2023b
--- libdatetime-timezone-perl-2.47/debian/patches/olson-2023b   1970-01-01 
01:00:00.0 +0100
+++ libdatetime-timezone-perl-2.47/debian/patches/olson-2023b   2023-03-24 
16:58:22.0 +0100
@@ -0,0 +1,16906 @@
+Description: Update to Olson DB 2023b
+Origin: vendor
+Author: gregor herrmann 
+Last-Update: 2023-03-24
+
+--- a/lib/DateTime/TimeZone/Africa/Abidjan.pm
 b/lib/DateTime/TimeZone/Africa/Abidjan.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from debian/tzdata/africa.  Olson data version 2022g
++# Generated from debian/tzdata/africa.  Olson data version 2023b
+ #
+ # Do not edit this file directly.
+ #
+@@ -43,11 +43,11 @@
+ ],
+ ];
+ 
+-sub olson_version {'2022g'}
++sub olson_version {'2023b'}
+ 
+ sub has_dst_changes {0}
+ 
+-sub _max_year {2032}
++sub _max_year {2033}
+ 
+ sub _new_instance {
+ return shift->_init( @_, spans => $spans );
+--- a/lib/DateTime/TimeZone/Asia/Beirut.pm
 b/lib/DateTime/TimeZone/Asia/Beirut.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from debian/tzdata/asia.  Olson data version 2022g
++# Generated from debian/tzdata/asia.  Olson data version 2023b
+ #
+ # Do not edit this file directly.
+ #
+@@ -1024,17 +1024,17 @@
+ ],
+ [
+ 63802760400, #utc_start 2022-10-29 21:00:00 (Sat)
+-63815464800, #  utc_end 2023-03-25 22:00:00 (Sat)
++63817711200, #  utc_end 2023-04-20 22:00:00 (Thu)
+ 63802767600, #  local_start 2022-10-29 23:00:00 (Sat)
+-63815472000, #local_end 2023-03-26 00:00:00 (Sun)
++63817718400, #local_end 2023-04-21 00:00:00 (Fri)
+ 7200,
+ 0,
+ 'EET',
+ ],
+ [
+-63815464800, #utc_start 2023-03-25 22:00:00 (Sat)
++63817711200, #utc_start 2023-04-20 22:00:00 (Thu)
+ 6383421, #  utc_end 2023-10-28 21:00:00 (Sat)
+-63815475600, #  local_start 2023-03-26 01:00:00 (Sun)
++63817722000, #  local_start 2023-04-21 01:00:00 (Fri)
+ 63834220800, #local_end 2023-10-29 00:00:00 (Sun)
+ 10800,
+ 1,
+@@ -1220,13 +1220,31 @@
+ 1,
+ 'EEST',
+ ],
++[
++64149915600, #utc_start 2033-10-29 21:00:00 (Sat)
++6416262, #  utc_end 2034-03-25 22:00:00 (Sat)
++64149922800, #  local_start 2033-10-29 23:00:00 (Sat)
++64162627200, #local_end 2034-03-26 

Bug#973414: rustc: produces non-baseline opcodes for compiler_builtins::int::udiv::__udivmoddi4 on i386

[James Addison]

Followup-For: Bug #973414

On Fri, 24 Mar 2023 14:23:18 +, James wrote:
> In particular, one area to look at:
>
>   
> https://github.com/llvm/llvm-project/blob/llvmorg-14.0.6/clang/lib/Driver/ToolChains/Arch/X86.cpp#L25-L70

Line range correction:

  
https://github.com/llvm/llvm-project/blob/llvmorg-14.0.6/clang/lib/Driver/ToolChains/Arch/X86.cpp#L25-L115

(I haven't determined whether that function is relevant yet, but it does seem
possible that anything up to and/or including the fallback at the end could be
relevant)

Bug#1018061: pads: segfault at 3a ip

[Tim McConnell]

Hi Bernhard, 
Well that explains that then, I didn't change anything to pin to the
patched version. 
In that case it was fixed and I broke it. 
Hopefully the patch will be part of a future release and it'll be
peachy again. 
Thanks for explaining what happened. 

-- 
Tim McConnell 


On Fri, 2023-03-24 at 11:52 +0100, Bernhard Übelacker wrote:
> Am 23.03.23 um 17:38 schrieb Tim McConnell:
> > Bernhard,
> > Just cause I said it was fixed this happens to show up in
> > journalctl:
> > systemd-coredump[3614]: Process 1704 (pads) of user 0 dumped core.
> >    
> >    Module
> > libsystemd.so.0 from deb systemd-252.5-2.amd64
> >    Stack trace of
> > thread 1704:
> >    #0
> > 0x5600f24f6954 print_arp_asset_screen (pads + 0x9954)
> >    #1
> > 0x5600f24f66f0 print_arp_asset (pads + 0x96f0)
> >    #2
> > 0x7fdc7fdb54f6 n/a (libpcap.so.0.8 + 0x84f6)
> >    #3
> > 0x7fdc7fdb58ec n/a (libpcap.so.0.8 + 0x88ec)
> >    #4
> > 0x7fdc7fdbcd1d pcap_loop (libpcap.so.0.8 + 0xfd1d)
> >    #5
> > 0x5600f24efe5b main_pads (pads + 0x2e5b)
> >    #6
> > 0x5600f24ef47b main (pads + 0x247b)
> >    #7
> > 0x7fdc7fbec18a __libc_start_call_main (libc.so.6 + 0x2718a)
> >    #8
> > 0x7fdc7fbec245 __libc_start_main_impl (libc.so.6 + 0x27245)
> >    #9
> > 0x5600f24ef4b1 _start (pads + 0x24b1)
> >    ELF object
> > binary
> > architecture: AMD x86-64
> > Mar 04 14:31:02 DebianTim systemd[1]:
> > systemd-coredump@0-3613-0.service: Deactivated successfully.
> > 
> > Well I thought it was fixed :-(
> 
> 
> Hello Time,
> are you sure that your rebuilt package is still in place?
> The offsets in your new backtrace are exactly the same as
> in the email from 8 Feb 2023.
> 
> We have not changed the version of the rebuilt package.
> Additionally built with "-b".
> Then with a "apt dist-upgrade" always
> the Debian version gets reinstalled.
> 
> Sorry for not mentioning that extra care has to be taken
> to hold the rebuilt package version in place.
> 
> Kind regards,
> Bernhard

Bug#1033411: unblock: libdatetime-timezone-perl/1:2.59-1+2023b

[gregor herrmann]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: libdatetime-timezone-p...@packages.debian.org, 
debian-p...@lists.debian.org
Control: affects -1 + src:libdatetime-timezone-perl

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please unblock package libdatetime-timezone-perl:

I've uploaded libdatetime-timezone-perl/1:2.59-1+2023b to unstable.
This is the new upstream release which contains the contents of the
Olson DB version 2023b.

tzdata changes:

2023a
Egypt now uses DST again, from April through October.
This year Morocco springs forward April 23, not April 30.
Palestine delays the start of DST this year.
Much of Greenland still uses DST from 2024 on.

2023b
Lebanon delays the start of DST this year.


The upload does not contain any other relevant changes (neither
upstream nor in packaging).

Tests during build and autopkgtest pass, no other observations …

I'm attaching a manually stripped down debdiff against 1:2.56-1+2022g
in testing.

unblock libdatetime-timezone-perl/1:2.59-1+2023b


Thanks in advance,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmQdxt5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaYgg/+I5kMFw5qi6zCsDI0g4USkiVFRPlJN1ey+1GPJ2D9hv0YNdAyOfRmvrRq
/EY0LVva+ARiIt1MabDRk4BSBnsPzSW+32a7mmrmDjYG/lXoUe5LTjEu2lhoegZ0
YN4gs1t9u2zoeHz+Gfemf1ozhesF34LTNYbI9IzvJLust/bBFtZYJNQULg5pGBmY
b0jotCDWQAGA5bIrhJkm7l5eP3G0v/o1//nttmu5j1uCCerQwXQ/UtZTExzHOc8R
8eyqNnQAl6ldsOMfp9eAjr1//XbWdD/XMeUMA1XApWzdvJ6aAULTkva6o8Z0nXJy
rlE+GeG3p/khtLC0HhUmE7Dwn/tgSd6UDuGUH4ttAAf11We3cmvYoCuwNW7uGbY7
fU9JPHanRl24MCL2rvHcCKBIt+zyS9s2yIXM8GAc1KixR/HoUpraszLwLQ7+h8Dy
X5PBVSdH+UnYwXbd6o6A18ACkaJcprZ1Tj+yhwa7fm9/4oZdGeQSO/aePJ2GFLtU
PqpN7nLFXuXj1ayKaVnIt3f7JgOrhTzSRsIABJbuvcpcFxNasXof9Dopm3qxS0oc
ZzDkdGvEqrrBu4s9eLIgdpqc7Fs60XJYmZoahcMMADRoKNsx6P//kGiaaG1MNrEJ
zVUjlvBCSi4d7t9Anx364C+W5cZjL4P0I5M9W08BZJ23WXtHnaM=
=rndO
-END PGP SIGNATURE-
diff -Nru libdatetime-timezone-perl-2.56/Changes 
libdatetime-timezone-perl-2.59/Changes
--- libdatetime-timezone-perl-2.56/Changes  2022-10-29 05:14:21.0 
+0200
+++ libdatetime-timezone-perl-2.59/Changes  2023-03-24 05:36:13.0 
+0100
@@ -1,3 +1,21 @@
+2.592023-03-23
+
+- This release is based on version 2023b of the Olson database. This release
+  includes contemporary changes for Lebanon.
+
+
+2.582023-03-22
+
+- This release is based on version 2023a of the Olson database. This release
+  includes contemporary changes for Egypt, Greenland, Morocco, and Palestine.
+
+
+2.572022-12-13
+
+- This release is based on version 2022g of the Olson database. This release
+  includes contemporary changes for Greenland and Mexico.
+
+
 2.562022-10-28
 
 - This release is based on version 2022f of the Olson database. This release
diff -Nru libdatetime-timezone-perl-2.56/LICENSE 
libdatetime-timezone-perl-2.59/LICENSE
--- libdatetime-timezone-perl-2.56/LICENSE  2022-10-29 05:14:21.0 
+0200
+++ libdatetime-timezone-perl-2.59/LICENSE  2023-03-24 05:36:13.0 
+0100
@@ -1,4 +1,4 @@
-This software is copyright (c) 2022 by Dave Rolsky.
+This software is copyright (c) 2023 by Dave Rolsky.
 
 This is free software; you can redistribute it and/or modify it under
 the same terms as the Perl 5 programming language system itself.
@@ -12,7 +12,7 @@
 
 --- The GNU General Public License, Version 1, February 1989 ---
 
-This software is Copyright (c) 2022 by Dave Rolsky.
+This software is Copyright (c) 2023 by Dave Rolsky.
 
 This is free software, licensed under:
 
@@ -272,7 +272,7 @@
 
 --- The Artistic License 1.0 ---
 
-This software is Copyright (c) 2022 by Dave Rolsky.
+This software is Copyright (c) 2023 by Dave Rolsky.
 
 This is free software, licensed under:
 
diff -Nru libdatetime-timezone-perl-2.56/MANIFEST 
libdatetime-timezone-perl-2.59/MANIFEST
diff -Nru libdatetime-timezone-perl-2.56/debian/changelog 
libdatetime-timezone-perl-2.59/debian/changelog
--- libdatetime-timezone-perl-2.56/debian/changelog 2022-11-30 
18:03:44.0 +0100
+++ libdatetime-timezone-perl-2.59/debian/changelog 2023-03-24 
16:38:06.0 +0100
@@ -1,3 +1,20 @@
+libdatetime-timezone-perl (1:2.59-1+2023b) unstable; urgency=medium
+
+  * Import upstream version 2.59.
+The 2.57 release was based on version 2022g of the Olson database.
+It includes contemporary changes for Greenland and Mexico (already
+present in 1:2.56-1+2022g).
+The 2.58 release was based on version 2023a of the Olson database.
+It includes contemporary changes for Egypt, Greenland, Morocco, and
+Palestine.
+This release (2.59) is based on version 2023b of the Olson database.
+It includes contemporary changes for Lebanon.
+  * Drop debian/patches/olson-2022g. Version 2022g was included in 2.57.
+  * Update years of 

Bug#1033410: RM: tiledb -- ROM as full builds not possible within Debian

[Dirk Eddelbuettel]

Package: ftp.debian.org
Severity: normal

The TileDB source package uses cmake and find_package for external resources;
the upstream team maintaining the core library is going to switch to vcpkg
soon.

A full featured TileDB really needs the AWS SDK which we still do not have,
would benefit from the GCS SDK (not in Debian), ditto for Azure as well as
integration with several other components which is difficult as upstream pins
some parts we have (CapnProto, Catch2, ...) but in different versions.

TileDB is an excellent product, and a lovely C++ library that can be used
well from Python and R.  But it is not a good fit within Debian, and after
maintaining for about two years as a caretaker maintainer (it was brought and
then left by someone else) I have come to the conclusion that it is not a
good fit for Debian.

Full disclosure: I work at TileDB and build the library all the time (mostly
on current Ubuntu as my dev env) and am hence quite familiar with various
extensions and optional components.  We are short-changing our users by not
enabling them, but we cannot enable them and stay true to Debian packaging
guidelines. 

Happy to expand if there are questions.

Thanks,  Dirk

--
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1031695: dh_installsystemd doesn't handle files in /usr/lib/systemd/system

[Niels Thykier]

Sebastian Ramacher:

[...]

Any progress here? If this issue should be fixed for bookworm, time is
running short.

Cheers


I find that anytime I look at this bug my motivation to work on Debian 
instantly vanishes. In fact, I cannot even motivate myself to read the 
bug log to figure out what the consensus is. Accordingly, I will play 
the constitution 2.1.1 and step out of the way.


If there are any recent debhelper contributors that want to claim this, 
then I will give preference to them and how they want to handle it.


Otherwise, if no debhelper contributor steps up, then I will waive the 
NMU process on this side of the release on the debhelper package to 
anyone, who ones to pick this up. Please keep the following in mind:


 1) Be adviced that you need to look at multiple helpers that interact
with the systemd services.  Notably, dh_installsystemd,
dh_installsystemduser and dh_installinit - all of which assumes
there is one and only one directly for these services.  Good luck

 2) I would that you push the changes to the salsa repo (it is
DD-writable by default, others will have to do a PR) but a nmudiff
CC'ed to this bug on top of the main branch in salsa will do.
- Please use the main branch, there are some translation changes
  since last upload, which should be a non-issue.
- If you are a DD, just push the changes to main and move on. Do not
  expect me to review a PR before you upload.

 3) I expect that you upload and handle any fall out. Fall out here
includes judging consensus, fix FTBFS, RC bugs or deal with
discussions including the tech-ctte or the release team about the
proposed solution, managing the unblock request (etc.).
- Assume I will not be involved in any of these steps.

 3) If you do change any translatable strings, please consider to notify
the translators.  At least pt and de translators recently updated
and I feel it would be a shame if they were not 100%. But not enough
that I expect I will invest in a follow up upload.

My apologies to the release team. Having been on the release team, I 
know this is probably not the message you wanted this close to the 
release. Sadly, it is the "best" I can do.


With that said and done, as far as bug is concerned, I am out!

Best regards,
Niels

Bug#1022964: libselinux FTCBFS: python and ruby extensions

[James Addison]

On Fri, 24 Mar 2023 at 13:50, Helmut Grohne  wrote:
>
> Thank you very much for your review and the attention to detail. I
> concur with your observation and have updated the patch accordingly.
> This part slipped my testing, because I never tried the clean target and
> most cross builds never clean that way.

You're welcome - I was applying the patch manually, line-by-line (my
workflows can be quite inefficient sometimes), and that helped to
notice it.

And yep, those clean steps could be a common area for similar
problems.  I suppose piuparts tests similar functionality for built
package removal/reinstall, but it's less common to build, clean and
then rebuild again in-place.

Bug#1033409: nmu: dbgsym packages affected by fakeroot bug

[Niels Thykier]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: debhel...@packages.debian.org, hel...@subdivi.de

Hi,

I propose the following series of NMUs to close #1024261.  The list is 
based on the set of packages that Helmut found with this script with the 
following modifications:


 * binNMU version have been removed
 * architecture has been removed. I assume we will do ANY binNMUs for
   them to avoid M-A:same issues and it is easier to overshoot than
   clean out the packages that are not M-A:same

This would solve the dbgsym problems caused by fakeroot.  For the 
changelog entry, allegedly fakeroot fixed the problem by now and we can 
reference that. Alternatively, debhelper has worked around the fakeroot 
problem as well in 13.11.


This does not solve the non-dbgsym packages but at least we get the ball 
rolling on the part of the problem we have clearly identified and would 
enable us to close #1024261.


Best regards,
Nielsacm-dbgsym_6.0+20200416-1.1
alure-utils-dbgsym_1.2-9
ann-tools-dbgsym_1.1.2+doc-9
aprsdigi-dbgsym_3.10.0-5
argus-client-dbgsym_1:3.0.8.2-6.1
audacious-plugins-dbgsym_4.2-1
ax25mail-utils-dbgsym_0.15-1
colobot-dbgsym_0.2.0-2
connman-dbgsym_1.41-2
connman-vpn-dbgsym_1.41-2
conntrackd-dbgsym_1:1.4.7-1
conserver-server-dbgsym_8.2.7-2
courier-authdaemon-dbgsym_0.71.4-1
courier-authlib-dbgsym_0.71.4-1
courier-authlib-userdb-dbgsym_0.71.4-1
courier-base-dbgsym_1.0.16-3
courier-imap-dbgsym_5.0.13+1.0.16-3
courier-mlm-dbgsym_1.0.16-3
courier-mta-dbgsym_1.0.16-3
courier-pop-dbgsym_1.0.16-3
cutils-dbgsym_1.6-6
dablin-dbgsym_1.14.0-2
dolphin-owncloud-dbgsym_2.11.0.8354+dfsg-1
dvb-tools-dbgsym_1.22.1-5
fastforward-dbgsym_1:0.51-8
fido2-tools-dbgsym_1.12.0-2
freeipmi-ipmidetect-dbgsym_1.6.10-1
freeipmi-tools-dbgsym_1.6.10-1
fuse-dbgsym_2.9.9-6
geomview-dbgsym_1.9.5-4
giggle-dbgsym_0.7-5
globus-gatekeeper-dbgsym_11.4-2
gnome-applets-dbgsym_3.46.0-1
gnome-keyring-dbgsym_42.1-1
gnome-panel-dbgsym_3.46.0-1
gpsshogi-dbgsym_0.7.0-3.1
gspell-1-tests-dbgsym_1.12.0-1
gtklp-dbgsym_1.3.4-3
harp-dbgsym_1.16-1
hashcat-dbgsym_6.2.6+ds1-1
herbstluftwm-dbgsym_0.9.5-3
ibus-kkc-dbgsym_1.5.22-3
ibus-skk-dbgsym_1.4.3-2
ifcico-dbgsym_2.14tx8.10-27
ifgate-dbgsym_2.14tx8.10-27
invada-studio-plugins-ladspa-dbgsym_0.3.1-6
ipe-dbgsym_7.2.26+dfsg1-3
kbd-dbgsym_2.5.1-1
knockd-dbgsym_0.8-2
krb5-admin-server-dbgsym_1.20.1-1
krb5-auth-dialog-dbgsym_43.0-1
krb5-gss-samples-dbgsym_1.20.1-1
krb5-kdc-dbgsym_1.20.1-1
krb5-kdc-ldap-dbgsym_1.20.1-1
krb5-user-dbgsym_1.20.1-1
kup-backup-dbgsym_0.9.1-1
kyotocabinet-utils-dbgsym_1.2.79-2
lcdproc-dbgsym_0.5.9-6
lcdproc-extra-drivers-dbgsym_0.5.9-6
libbabl-0.1-0-dbgsym_1:0.1.98-1
libcoarrays-mpich-dev-dbgsym_2.10.1-1
libcoarrays-openmpi-dev-dbgsym_2.10.1-1
libdb1-compat-dbgsym_2.1.3-22
libdrm-tests-dbgsym_2.4.114-1
libfuse2-dbgsym_2.9.9-6
libiec61883-dev-dbgsym_1.2.0-6
libipe7.2.26-dbgsym_7.2.26+dfsg1-3
libkim-api2-dbgsym_2.3.0-1
libkim-api-dev-dbgsym_2.3.0-1
libleatherman1.12.1-dbgsym_1.12.1+dfsg-1.2
libopenmesh1-dbgsym_9.0-4
libopenmesh-apps-dbgsym_9.0-4
libopenmpi3-dbgsym_4.1.4-3
libopenms2.6.0-dbgsym_2.6.0+cleaned1-3
libowncloudsync0-dbgsym_2.11.0.8354+dfsg-1
libpdl-linearalgebra-perl-dbgsym_0.35-1
libplib1-dbgsym_1.8.5-14
libpmix2-dbgsym_4.2.2-1
libpmix-bin-dbgsym_4.2.2-1
libruli-bin-dbgsym_0.36-3
libsuperlu-dist8-dbgsym_8.1.2+dfsg1-1
libsuperlu-dist-dev-dbgsym_8.1.2+dfsg1-1
libtheora0-dbgsym_1.1.1+dfsg.1-16.1
libtheora-bin-dbgsym_1.1.1+dfsg.1-16.1
libv4l-0-dbgsym_1.22.1-5
libv4lconvert0-dbgsym_1.22.1-5
libxtrxll0-dbgsym_0.0.1+git20201202.1b6eddf-1
linuxptp-dbgsym_3.1.1-4
lldpd-dbgsym_1.0.16-1
login-dbgsym_1:4.13+dfsg1-1
lua-readline-dbgsym_3.2-1
lua-socket-dbgsym_3.1.0-1
miredo-dbgsym_1.2.6-7.1
mutt-dbgsym_2.2.9-1
myproxy-admin-dbgsym_6.2.14-2
myproxy-dbgsym_6.2.14-2
ndisc6-dbgsym_1.0.5-1
nethack-common-dbgsym_3.6.6-3
ntfs-3g-dbgsym_1:2022.10.3-1
ntfs-3g-dev-dbgsym_1:2022.10.3-1
oddjob-dbgsym_0.34.7-1
oddjob-mkhomedir-dbgsym_0.34.7-1
odr-dabmux-dbgsym_4.2.1-1
openmpi-bin-dbgsym_4.1.4-3
opensmtpd-dbgsym_6.8.0p2-4
orthanc-postgresql-dbgsym_4.0-7
osdsh-dbgsym_0.7.0-11
osmo-bsc-bs11-utils-dbgsym_1.9.0-3
osmo-bsc-ipaccess-utils-dbgsym_1.9.0-3
osmo-bsc-meas-utils-dbgsym_1.9.0-3
osmo-bts-dbgsym_1.5.0+dfsg1-2
osmo-ggsn-dbgsym_1.9.0-3
osmo-hlr-dbgsym_1.5.0+dfsg1-3
passwd-dbgsym_1:4.13+dfsg1-1
pdl-dbgsym_1:2.081-1
perl-tk-dbgsym_1:804.036-1
ploop-dbgsym_1.15-12
pmacct-dbgsym_1.7.7-1
postgresql-15-ogr-fdw-dbgsym_1.1.3-1
qflow-dbgsym_1.3.17+dfsg.1-3
r-cran-zip-dbgsym_2.2.2-1
roger-router-dbgsym_2.4.2-3
rxvt-unicode-dbgsym_9.30-2
scalapack-mpi-test-dbgsym_2.2.1-2
schroot-dbgsym_1.6.13-3
scitokens-cpp-dbgsym_0.7.3-1
shapelib-dbgsym_1.5.0-3
shotwell-dbgsym_0.30.17-1
sndio-tools-dbgsym_1.9.0-0.3
source-highlight-dbgsym_3.1.9-4.2
spice-vdagent-dbgsym_0.22.1-3
squid-dbgsym_5.7-1
squid-openssl-dbgsym_5.7-1
sqwebmail-dbgsym_6.0.5+1.0.16-3
sslh-dbgsym_1.20-1
sysrepo-dbgsym_2.0.53-6
topp-dbgsym_2.6.0+cleaned1-3
torcs-dbgsym_1.3.7+dfsg-5

Bug#824651: ostree: initramfs-tools integration

[bauen1]

Hi,

I've been successfully experimenting with ostree-ifying debian, using the 
attached script with initramfs-tools.
It's not particularly polished, and essentially assumes:
- The `systemd-remount-fs.service` unit is masked
- You passed `boot=ostree` on the cmdline, so initramfs-tools sources the script
- That you want to use the `sysroot.readonly=true` option

Ideally the `/usr/lib/ostree/ostree-prepare-root` utility could be used, but I 
found it easier start experimenting with manually mounting everything.

Perhaps that script is of use to someone.

I'm not sure how much interest there is in building something similar to Fedora 
Silverblue using Debian, but there are a couple of other things, that would be 
useful:

- A udeb with just the ostree utility for use in the installer, that would 
allow building a installer using the existing d-i components.
  I currently use the `copy_exec` function from initramfs-tools to build such a 
udeb, and while some libraries are already packaged as udeb, ostree has a lot 
of dependencies, and gpg verification doesn't work.

- Shipping sysuser and tmpfiles for every debian package

--
bauen1#!/bin/sh
# Author: Jonathan Hettwer (bauen1) 

PREREQS=""

prereqs() {
echo "$PREREQS" ;
}

case "$1" in
prereqs)
prereqs
exit 0
;;
esac

# The local script is sourced unconditionally, so in most places we defer to it.

ostree_top()
{
local_top
}

ostree_block()
{
local_block
}

ostree_premount()
{
local_premount
}

ostree_bottom()
{
local_bottom
}

ostree_mount_root()
{
# Force the initial mount to be read-only
readonly=y
# First use the local boot script to mount the actual $rootmnt
log_warning_msg "ostree: before local_mount_root"
local_mount_root
log_warning_msg "ostree: after local_mount_root"

# FIXME: this may not be the most appropiate place to parse the cmdline:
export ostree_deploy_tree=
for x in $(cat /proc/cmdline); do
case $x in
ostree=*)
ostree_deploy_tree=${x#ostree=}
;;
esac
done

if [ -z "${ostree_deploy_tree}" ]; then
panic "No ostree deployment path specified!"
fi

log_warning_msg "ostree_deploy_tree: ${ostree_deploy_tree}"

# TODO: We don't really respect the rw cmdline argument, or the 
sysroot.readonly configuration
#   in the ostree repository, we simply assume that 
sysroot.readonly is set and mount accordingly
# TODO: Most of this could be replaced by the 
/usr/lib/ostree/ostree-prepare-root
# XXX: The ostree system I'm using this has the 
`systemd-remount-fs.service` unit masked, enabling it could mess up the mount 
setup, see the ostree-boot package.


# Bind mount the ostree deployment in preparation of moving it onto /
if ! mount -o bind "${rootmnt}${ostree_deploy_tree}" 
"${rootmnt}${ostree_deploy_tree}"; then
panic "Failed to bind mount ${rootmnt}${ostree_deploy_tree}"
fi
if ! mount -o remount,ro dummy "${rootmnt}${ostree_deploy_tree}"; then
panic "Failed to make ${rootmnt}${ostree_deploy_tree} mount 
read-only"
fi

# Bind mount the actual root onto the /sysroot directory in the 
deployment
if ! mount -o bind "${rootmnt}" 
"${rootmnt}${ostree_deploy_tree}/sysroot"; then
panic "Failed to bind mount the physical root (${rootmnt}) onto 
the ostree deployment /sysroot directory 
(${rootmnt}${ostree_deploy_tree}/sysroot)"
fi

# Prepare /boot
if ! read_fstab_entry /boot; then
log_warning_msg "Found /boot entry in fstab, not mounting"
# If we where to bind-mount here, systemd would not mount /boot 
itself
else
log_warning "Found no /boot entry in fstab, bind mounting"

if ! mount -o bind "${rootmnt}/boot" 
"${rootmnt}${ostree_deploy_tree}/boot"; then
panic "Failed to bind mount /boot from physical root to 
deployment root /boot!"
fi
fi

# Prepare /etc
log_warning_msg "ostree: attempting to bind mount 
${rootmnt}${ostree_deploy_tree}/etc"
if ! mount -o bind "${rootmnt}${ostree_deploy_tree}"/etc 
"${rootmnt}${ostree_deploy_tree}"/etc ; then
panic "Failed to bind mount /etc while preparing /sysroot"
fi
if ! mount -o remount,rw dummy "${rootmnt}${ostree_deploy_tree}"/etc ; 
then
# It might be possible to continue at this point
panic "Failed to make /etc read-write"
fi

# Prepare /usr
if ! mount -o bind "${rootmnt}${ostree_deploy_tree}"/usr 
"${rootmnt}${ostree_deploy_tree}"/usr ; then
panic "Failed to bind mount /usr while preparing /sysroot"
fi
if ! mount -o remount,ro dummy 

Bug#828941: licensecheck: use binwalk to parse binary blobs?

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2019-11-13 16:44:38)
> Licensecheck currently expects to be handed only sourcecode.
[...]
> For use right now, I recommend to combine licensecheck with helper 
> scripts part of cdbs (but *not* build-depend on or otherwise use cdbs).  
> For examples of using those helper scripts to pre-parse some binary 
> files and skip select other ones, while not accidentally silencing later 
> introduced unknown types of files, see file debian/copyright-check in 
> the source code of ghostscript (or pandoc or valentina), and the files 
> /usr/lib/cdbs/license-miner and /usr/lib/cdbs/licensecheck2dep5 in 
> package cdbs.

Update: See https://wiki.debian.org/CopyrightReviewTools#licensecheck
for best practice on using licensecheck with sources involving binary
data (no need for CDBS).

Thanks to Vignesh Raman in bug#103340 for pointing out the above
outdated advice.


 - 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#1033406: licensecheck: scan-copyrights fails to create copyright file for texlive-extra

[Jonas Smedegaard]

Hi Vignesh,

Quoting Vignesh Raman (2023-03-24 15:08:53)
> scan-copyrights is unable to create the copyright file when using 
> texlive-extra sources 
> (https://deb.debian.org/debian/pool/main/t/texlive-extra/texlive-extra_2020.20210202-3.dsc).

As you most likely know, but mentioning for reference, the script
scan-copyrights is part of libconfig-model-dpkg-perl (not licensecheck).


> It appears that the following files may be causing the issue:
> ./texmf-dist/fonts/type1/public/baskervillef/BaskervilleF-Bold.pfb
> ./texmf-dist/fonts/type1/public/baskervillef/BaskervilleF-BoldItalic.pfb
> ./texmf-dist/tex/latex/exp-testopt/exp-testopt.sty
> 
> Removing these files prevents the program from crashing, but individual runs 
> of licensecheck on
> these files do not result in any issues. This issue has been observed with 
> libconfig-model-dpkg-perl versions 2.143 and 2.165,
> licensecheck version 3.1.1-2 and 3.3.5-1. This issue is not consistently 
> reproducible.

Please try isolate the exact licensecheck command that scan-copyrights
executes (e.g. by hacking that script to print to stderr before
executing).

When that exact command - including options and arguments - is known, we
can move on to examine why the failure isn't deterministic.


> scan-copyrights crashes because the output from licensecheck looks invalid.
> licensecheck tries to parse the binary file (pfb) and returns invalid data.

Yes, licensecheck does not (in its current form) support non-text
sources at all.  That is not a bug but a limitation of the tool - i.e.
at most a wishlist issue.

Your mentioning above that licensecheck failing is "not consistently
reproducible" is another bug that is more serious, however: Licensecheck
should - with same version also of its libraries - behave the same at
each execution.

So it would be helpful to me, independent of the issue of not parsing
binary data - if you can help isolate the command which is unreliable.


> As per the comment in 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828941, it is mentioned,
> For use right now, I recommend to combine licensecheck with helper 
> scripts part of cdbs (but *not* build-depend on or otherwise use cdbs).  
> For examples of using those helper scripts to pre-parse some binary 
> files and skip select other ones, while not accidentally silencing later 
> introduced unknown types of files, see file debian/copyright-check in 
> the source code of ghostscript (or pandoc or valentina), and the files 
> /usr/lib/cdbs/license-miner and /usr/lib/cdbs/licensecheck2dep5 in 
> package cdbs.
> 
> Please let me know if this recommendation can be followed or if there are any 
> other fixes for this issue.

It is unclear what you are referring to as "this issue": What you
summarise in the subject of this bugreport strictly speaking is an issue
with libconfig-model-dpkg-perl, and above I have mentioned 2 potential
underlying issues that might be your main concern here (as I assume you
deliberately chose to file this bugreport against licensecheck).

If you are not really reporting a new issue here, but instead are asking
for best practice of using licensecheck with sources that include binary
data, then my most up-to-date notes on that is here:
https://wiki.debian.org/CopyrightReviewTools#licensecheck


Kind regards,

 - 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#1033408: apache2: Segmentation fault + 503 on frontpage on 2.4.56-1

[root]

Package: apache2
Version: 2.4.56-1~deb11u1
Severity: important
X-Debbugs-Cc: t...@security.debian.org

Unattended-upgrades applied this new version on 22 march @ 6AM. Had
Segmentation faults since then, 503 for customers on websites. Since we
reverted back to 2.4.54, we've no more issues. Couldn't make any sense
of coredump but can provide one if necessary.


-- Package-specific info:

-- 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-18-amd64 (SMP w/32 CPU threads)
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 apache2 depends on:
ii  apache2-bin  2.4.56-1~deb11u1
ii  apache2-data 2.4.56-1~deb11u1
ii  apache2-utils2.4.56-1~deb11u1
ii  dpkg 1.20.12
ii  init-system-helpers  1.60
ii  lsb-base 11.1.0
ii  mime-support 3.66
ii  perl 5.32.1-4+deb11u2
ii  procps   2:3.3.17-5

Versions of packages apache2 recommends:
ii  ssl-cert  1.1.0+nmu1

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  lynx [www-browser]   2.9.0dev.6-3~deb11u1

Versions of packages apache2-bin depends on:
ii  libapr1  1.7.0-6+deb11u2
ii  libaprutil1  1.6.1-5+deb11u1
ii  libaprutil1-dbd-sqlite3  1.6.1-5+deb11u1
ii  libaprutil1-ldap 1.6.1-5+deb11u1
ii  libbrotli1   1.0.9-2+b2
ii  libc62.31-13+deb11u5
ii  libcrypt11:4.4.18-4
ii  libcurl4 7.74.0-1.3+deb11u7
ii  libjansson4  2.13.1-1.1
ii  libldap-2.4-22.4.57+dfsg-3+deb11u1
ii  liblua5.3-0  5.3.3-1.1+b1
ii  libnghttp2-141.43.0-1
ii  libpcre3 2:8.44-2+0~20210301.9+debian11~1.gbpa278ad
ii  libssl1.11.1.1n-0+deb11u4
ii  libxml2  2.9.14+dfsg-0+0~20220524.12+debian11~1.gbpc5dc45
ii  perl 5.32.1-4+deb11u2
ii  zlib1g   1:1.2.11.dfsg-2+deb11u2

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  lynx [www-browser]   2.9.0dev.6-3~deb11u1

Versions of packages apache2 is related to:
ii  apache2  2.4.56-1~deb11u1
ii  apache2-bin  2.4.56-1~deb11u1

-- Configuration Files:
/etc/apache2/apache2.conf changed [not included]
/etc/apache2/mods-available/mpm_event.conf changed [not included]
/etc/apache2/ports.conf changed [not included]
/etc/apache2/sites-available/000-default.conf changed [not included]

-- no debconf information

Bug#1033333: Don't include in Bookworm

[Moritz Muehlenhoff]

Hi Peter,

On Thu, Mar 23, 2023 at 09:23:18PM +, Peter Green wrote:
> severity 103 normal
> retitle 103 rust-encoding is unmaintained upstream
> severity 104 normal
> retitle 104 rust-boxfnonce is unmaintained upstream
> severity 105 normal
> retitle 105 rust-const-cstr is unmaintained upstream
> 
> (summarising several bugs)
> > there is https://rustsec.org/advisories/RUSTSEC-{advisory}.html which flags
> > that rust-{crate} is unmaintained. Since there are no reverse deps in the
> > archive, let's exclude it from bookworm (or rather remove rightaway)?
> 
> I don't know what tool you are using to check for reverse dependencies but
> whatever it is does not seem to take account of virtual packages correctly.

I've been running a simulated removal using dak itself, as documented here:
https://wiki.debian.org/ftpmaster_Removals#Before_requesting_removal

Which I suppose also means that ftp.debian.org removals might leave packages 
behind?

> While I agree it's good to move away from crates that are abandoned upstream,
> I think it's too late to do so for bookworm and I don't think any of these
> crates are sensitive enough to consider such maintenance issues as rc.

Sure, that's fair enough, of course. I filed those bugs under the assumption 
that these
already were without rdeps.

Cheers,
Moritz

Bug#973414: rustc: produces non-baseline opcodes for compiler_builtins::int::udiv::__udivmoddi4 on i386

[James Addison]

Package: rustc
Followup-For: Bug #973414
X-Debbugs-Cc: martin-eric.rac...@iki.fi, fierel...@gmail.com, s...@debian.org, 
ru...@packages.debian.org

I've been trying to track down 'NOPL' opcodes in Debian's i386 bookworm archive
and many of the affected cases appear Rust and/or LLVM-related.

The simplest way to repro a Rust example that I've found so far is to build
the src:rust-lscolors[1] package from source in an i386 bookworm environment,
and then to 'objdump -d' the resulting 'lscolors' binary to grep for 'nopl'.

During that investigation, I learned about the existence of this bug, because
it sounds similar (unsupported opcodes, Rust toolchain, i386).


On Fri, 10 Mar 2023 09:58:42 +0200, Éric wrote:
> It's just a hunch, but I don't think that this issue will be resolved
> until Debian switches to the Rust compiler that has been merged with
> GCC 13, since GCC tends to respect CPU flags across the board.

That might be true, but I'd like to hope that we might be able to do better, or
at least determine where the opcodes (division and nopl) are originating from.

Although I understand that Debian has a rustc patch[2] in place to adjust the
intended baseline, my current/next area of focus is going to be llvm-14.0.6
because as Éric notes, something doesn't seem to be functioning as intended.

In particular, one area to look at:

  
https://github.com/llvm/llvm-project/blob/llvmorg-14.0.6/clang/lib/Driver/ToolChains/Arch/X86.cpp#L25-L70

(with credit to an upstream thread[3] where Fierelier is also chasing this)


[1] - https://packages.debian.org/source/bookworm/rust-lscolors

[2] - 
https://sources.debian.org/src/rustc/1.63.0%2Bdfsg1-2/debian/patches/d-rustc-i686-baseline.patch/

[3] - https://github.com/llvm/llvm-project/issues/61347

Bug#1033311: sysvinit-utils: pidof not always returning a pid when using the full path to a program

[Jesse Smith]

On 2023-03-24 6:44 a.m., Markus Fischer wrote:
> I think I've figured it out. With the following patch I don't see the
> unexpected behaviour anymore:
>
> --- a/src/killall5.c
> +++ b/src/killall5.c
> @@ -662,6 +662,7 @@ int readproc()
>     /* Try to stat the executable. */
>     snprintf(path, sizeof(path), "/proc/%s/exe", d->d_name);
>  p->pathname = (char *)xmalloc(PATH_MAX);
> +   memset(p->pathname, 0, PATH_MAX);
>     if (readlink(path, p->pathname, PATH_MAX) == -1) {
>     p->pathname = NULL;
>     }
>

This patch looks good to me. I'm adding it upstream.

Will run some more tests before publishing 3.07. And would appreciate it
if everyone following this issue could test too and provide feedback.

- Jesse

Bug#1033407: liferea: After bookworm upgrade liferea startup aborts with „Segmentation fault“

[H . -Dirk Schmitt]

Package: liferea
Version: 1.14.1-1
Severity: grave
X-Debbugs-Cc: none, H.-Dirk Schmitt 

Before bookworm upgrade liferea was working o.k.

Now – on bookworm – the startup fails with „Segmentation fault“.

The problem occured also on 2nd hardware with different user.

The problem is also occuring after removigng user data:
  `rm -vfr  .config/liferea/ .local/share/liferea/ .cache/liferea/`


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

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

Versions of packages liferea depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.6-1
ii  dbus-x11 [dbus-session-bus]   1.14.6-1
ii  dconf-gsettings-backend [gsettings-backend]   0.40.0-4
ii  gir1.2-freedesktop1.74.0-3
ii  gir1.2-gtk-3.03.24.37-2
ii  gir1.2-peas-1.0   1.34.0-1+b1
ii  libc6 2.36-8
ii  libfribidi0   1.0.8-2.1
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1+b1
ii  libgirepository-1.0-1 1.74.0-3
ii  libglib2.0-0  2.74.6-1
ii  libgtk-3-03.24.37-2
ii  libjavascriptcoregtk-4.0-18   2.38.5-1
ii  libjson-glib-1.0-01.6.6-1
ii  libpango-1.0-01.50.12+ds-1
ii  libpeas-1.0-0 1.34.0-1+b1
ii  libsoup2.4-1  2.74.3-1
ii  libsqlite3-0  3.40.1-2
ii  libwebkit2gtk-4.0-37  2.38.5-1
ii  libxml2   2.9.14+dfsg-1.1+b3
ii  libxslt1.11.1.35-1
ii  liferea-data  1.14.1-1
ii  python3   3.11.2-1
ii  python3-cairo 1.20.1-5+b1
ii  python3-gi3.42.2-3+b1
ii  python3-gi-cairo  3.42.2-3+b1
ii  python3-notify2   0.3-5
ii  python3.113.11.2-6

Versions of packages liferea recommends:
ii  gir1.2-gstreamer-1.0  1.22.0-2
ii  gir1.2-notify-0.7 0.8.1-1

Versions of packages liferea suggests:
pn  kget 
ii  network-manager  1.42.0-1

-- no debconf information


--

---

H.-Dirk_Schmitt
Dipl.Math.
eMail:dirk.schm...@computer42.org
pgp: http://www.computer42.org/~dirk/OpenPGP-fingerprint.html

Bug#1033406: licensecheck: scan-copyrights fails to create copyright file for texlive-extra

[Vignesh Raman]

Package: licensecheck
Version: 3.3.5-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: vignesh.ra...@collabora.com

Dear Maintainer,

scan-copyrights is unable to create the copyright file when using texlive-extra 
sources 
(https://deb.debian.org/debian/pool/main/t/texlive-extra/texlive-extra_2020.20210202-3.dsc).

The below program crashes,
#!/usr/bin/env python3

import sh

scan_copyrights = sh.Command('scan-copyrights')

def main():
    try:
        scan_copyrights()
    except sh.ErrorReturnCode as e:
        print("An error occurred:", e.stderr, file=sys.stderr)
        sys.exit(1)
    except Exception as e:
        print("An unknown error occurred:", e, file=sys.stderr)
        sys.exit(1)

if __name__ == '__main__':
    main()

Output:
raise exc
sh.ErrorReturnCode_255: 
RAN: /usr/bin/scan-copyrights

It appears that the following files may be causing the issue:
./texmf-dist/fonts/type1/public/baskervillef/BaskervilleF-Bold.pfb
./texmf-dist/fonts/type1/public/baskervillef/BaskervilleF-BoldItalic.pfb
./texmf-dist/tex/latex/exp-testopt/exp-testopt.sty

Removing these files prevents the program from crashing, but individual runs of 
licensecheck on
these files do not result in any issues. This issue has been observed with 
libconfig-model-dpkg-perl versions 2.143 and 2.165,
licensecheck version 3.1.1-2 and 3.3.5-1. This issue is not consistently 
reproducible.

scan-copyrights crashes because the output from licensecheck looks invalid.
licensecheck tries to parse the binary file (pfb) and returns invalid data.

As per the comment in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828941, 
it is mentioned,
For use right now, I recommend to combine licensecheck with helper 
scripts part of cdbs (but *not* build-depend on or otherwise use cdbs).  
For examples of using those helper scripts to pre-parse some binary 
files and skip select other ones, while not accidentally silencing later 
introduced unknown types of files, see file debian/copyright-check in 
the source code of ghostscript (or pandoc or valentina), and the files 
/usr/lib/cdbs/license-miner and /usr/lib/cdbs/licensecheck2dep5 in 
package cdbs.

Please let me know if this recommendation can be followed or if there are any 
other fixes for this issue.

Thank you.

Regards,
Vignesh

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

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

Versions of packages licensecheck depends on:
ii  libfeature-compat-class-perl0.05-1
ii  libfeature-compat-try-perl  0.05-1
ii  libio-interactive-perl  1.023-2
ii  liblist-someutils-perl  0.59-1
ii  liblog-any-adapter-screen-perl  0.140-2
ii  liblog-any-perl 1.713-1
ii  libnamespace-clean-perl 0.27-2
ii  libpath-iterator-rule-perl  1.015-2
ii  libpath-tiny-perl   0.144-1
ii  libpod-constants-perl   0.19-2
ii  libstrictures-perl  2.06-1
ii  libstring-copyright-perl0.003014-1
ii  libstring-escape-perl   2010.002-3
ii  libstring-license-perl  0.0.2-1
ii  perl5.36.0-7

Versions of packages licensecheck recommends:
ii  libregexp-pattern-license-perl  3.9.4-3

Versions of packages licensecheck suggests:
ii  bash-completion  1:2.11-6

-- no debconf information

Bug#1033212: Fwd: plasma-mobile fails to start on PP after kwin's commit eef9bd5c with "libkwinglutils: Shaders are not supported"

[Marco Mattiolo]

Prepared the patch to be included in order to fix this [1] and built 
patched kwin myself to confirm this solves the issue.


Marco

[1] https://salsa.debian.org/qt-kde-team/kde/kwin/-/merge_requests/6

Bug#1033405: rename: Switch --nono is sensitive to location

[Max Görner]

Package: rename
Version: 2.01-1
Severity: important

Dear Maintainer,

I tried to rename a bunch of files using `rename`/`file-rename`. I
checked carefully that both names point to the same program.

Since I wasn't sure about the correctness of renaming rule, I
**appended** the switch `--nono`. So, the final command I executed was
`rename 's/.*(S\d\d)_(E\d\d).*/$1$2$_/' --nono *`. Unfortunately, this
directly renamed all files! If I move `--nono` before the pattern,
everything behaves as expected: `rename --nono 's/.*(S\d\d)_(E\d\d).*/$1$2$_/' 
*`

The man page does not point out this behaviour as well. According to the
man page, giving `--nono` will stop `file-rename` to apply any changes.
In particular it is not mentioned that `--nono` must be given as first
argument and will have no effect otherwise.

I find this behaviour highly dangerous and it deleted some important
files I need to dig out from my backups now.

I think the preferred fix would be make `--nono` work regardless of its
position. A less favourable improvement could be to explicitly mention
the behaviour in the man page.

Thank you very much.

Regards
Max Görner


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

Kernel: Linux 6.2.8+ (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de:en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rename depends on:
ii  perl  5.36.0-7

rename recommends no packages.

rename suggests no packages.

-- no debconf information

Bug#815539: Fixed in 4.0

[Emmanuel Charpentier]

On Mon, 27 Dec 2021 23:54:09 -0500 Istiak Ferdous
 wrote:
> Hello,
> 
> This looks fixed in upstream 4.0 by original maintainer. Yet to be
> packaged.

As of March 24, 2023, this does not appear to have been packaged.

Could you suggest a workaround ?

Sincerely,

Bug#1033404: unblock: debvm/0.2.10

[Helmut Grohne]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: de...@packages.debian.org
Control: affects -1 + src:debvm

Please unblock package debvm

[ Reason ]

debvm is fairly new and was stabilizing right into the freeze. Thus
there are a few late changes that I hope to get into bookworm.

[ Impact ]

There are some notable changes indeed:
 * The biggest chunk of difference is documentation updates in various
   places. In particular, this includes adding examples for usage.
 * The biggest user facing change is the deprecation of the
   --architecture option for debvm-create. I paid attention to not just
   delete it (to avoid breaking things that already use it), but it no
   longer is documented and getting rid of it in bookworm already would
   make phasing it out later easier.
 * The --graphical option to debvm-run is fixed and improved.
 * Support for using 64bit kernels on mipsel.
 * An autopkgtest workaround for kernel bug #1029270 is being deleted.

[ Tests ]

autopkgtests succeed. The reason for the need on an unblock is that I
had to disable 32bit arm, because qemu tcg emulation is too slow to boot
Linux there. Other than that, it would migrate as a non-key package with
autopkgtests. On salsa, more tests are run. I've used the updated
version for quite some time now and not encountered more issues.

[ Risks ]

The affected functionality is not central to debvm or (in case of
--architecture) explicitly kept backwards-compatible. Thus I see little
risk for breakage.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

There is one possible change missing. Due to the archival of jessie,
using it with debvm now requires passing a mirror. If there is a need
for another update of debvm in bookworm, I intend to piggy-back an
example to the documentation about how to use jessie with
archive.debian.org.

unblock debvm/0.2.10

Thanks in advance

Helmut
diff --git a/README.md b/README.md
index 6fdda9e..1ccda36 100644
--- a/README.md
+++ b/README.md
@@ -77,9 +77,11 @@ The debvm tools are licensed under the MIT license.
 Contributors
 
 
+ * Arnd Bergmann
+ * Gioele Barabucci
  * Helmut Grohne (main author)
- * Johannes Schauer Marin Rodrigues (main author of `mmdebstrap`)
  * Jochen Sprickerhof
+ * Johannes Schauer Marin Rodrigues (main author of `mmdebstrap`)
 
 [^1] This technically is a lie. It employs user namespaces and thus requires
  the setuid binary `newuidmap` as well as a suitable subuid allocation.
diff --git a/bin/debvm-create b/bin/debvm-create
index 89256eb..1c7c29d 100755
--- a/bin/debvm-create
+++ b/bin/debvm-create
@@ -11,7 +11,7 @@ debvm-create - Create a VM image for various Debian releases and architectures
 
 =head1 SYNOPSIS
 
-B [B<-a> I] [B<-h> I] [B<-k> F] [B<-o> F] [B<-r> I] [B<-s> ] [B<-z> I] [B<--> I]
+B [B<-h> I] [B<-k> F] [B<-o> F] [B<-r> I] [B<-s> ] [B<-z> I] [B<--> I]
 
 =head1 DESCRIPTION
 
@@ -26,12 +26,6 @@ No user account is created and root can login without specifying a password.
 
 =over 8
 
-=item B<-a> I, B<--architecture>=I
-
-Specify a Debian architecture name.
-By default, the native architecture is being used.
-A suitable kernel image is automatically selected and installed into the image.
-
 =item B<-h> I, B<--hostname>=I
 
 Set the hostname of the virtual machine.
@@ -131,15 +125,43 @@ All options beyond a double dash are passed to B after the suite and
 This can be used to provide additional hooks for image customization.
 You can also request additional packages to be installed into the image using B's B<--include> option.
 Any positional arguments passed here will be treated as mirror specifications by B.
+In particular, you can also change the architecture of the resulting image using the B<--architecture> option.
 
 =back
 
 =head1 EXAMPLES
 
-In order to create images for Debian ports architectures, you can pass two options to mmdebstrap:
+When creating an image with multiple architectures, the kernel selection will prefer the sibling 64bit architecture.
+
+debvm-create ... -- --architecture=armhf,arm64
+
+In order to create images for Debian ports architectures, you can pass two options to mmdebstrap.
 
 debvm-create ... -- http://deb.debian.org/debian-ports --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg
 
+You can also install a graphical desktop environment.
+
+debvm-create ... -- --hook-dir=/usr/share/mmdebstrap/hooks/useradd --aptopt='Apt::Install-Recommends "true"' --include=linux-image-generic,task-gnome-desktop
+
+Here the hook creates a password-less user C.
+In order for C to work reasonably well, C should be enabled.
+By default a C<-cloud> kernel that lacks graphics drivers is installed.
+
+Installing Ubuntu is also supported somewhat.
+
+debvm-create --release kinetic -- 

Bug#1022964: libselinux FTCBFS: python and ruby extensions

[Helmut Grohne]

Hi James,

On Fri, Mar 24, 2023 at 11:09:32AM +, James Addison wrote:
> Could you check whether the patch is missing a 'call ruby_env' line in the
> debian/rules 'override_dh_auto_clean' target?

Thank you very much for your review and the attention to detail. I
concur with your observation and have updated the patch accordingly.
This part slipped my testing, because I never tried the clean target and
most cross builds never clean that way.

Helmut
diff --minimal -Nru libselinux-3.4/debian/changelog 
libselinux-3.4/debian/changelog
--- libselinux-3.4/debian/changelog 2022-06-04 12:41:40.0 +0200
+++ libselinux-3.4/debian/changelog 2022-10-28 10:33:35.0 +0200
@@ -1,3 +1,11 @@
+libselinux (3.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Support cross building python and ruby extensions.
+(Closes: #-1)
+
+ -- Helmut Grohne   Fri, 28 Oct 2022 10:33:35 +0200
+
 libselinux (3.4-1) unstable; urgency=medium
 
   [ Laurent Bigonville ]
diff --minimal -Nru libselinux-3.4/debian/control libselinux-3.4/debian/control
--- libselinux-3.4/debian/control   2022-06-04 12:41:40.0 +0200
+++ libselinux-3.4/debian/control   2022-10-28 10:33:35.0 +0200
@@ -8,13 +8,14 @@
Russell Coker 
 Standards-Version: 4.6.0
 Build-Depends: debhelper-compat (= 13),
-   dh-python ,
+   dh-sequence-python3 ,
+   dh-sequence-ruby ,
file,
-   gem2deb ,
libsepol-dev (>= 3.4),
libpcre2-dev,
+   libpython3-all-dev ,
pkg-config,
-   python3-all-dev ,
+   python3-all-dev:any ,
swig  
 XS-Ruby-Versions: all
 Homepage: https://selinuxproject.org
diff --minimal -Nru libselinux-3.4/debian/rules libselinux-3.4/debian/rules
--- libselinux-3.4/debian/rules 2022-06-04 12:41:40.0 +0200
+++ libselinux-3.4/debian/rules 2022-10-28 10:33:35.0 +0200
@@ -10,6 +10,13 @@
 ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE))
 export CC := $(DEB_HOST_GNU_TYPE)-gcc
 export PKG_CONFIG := $(DEB_HOST_GNU_TYPE)-pkg-config
+export _PYTHON_SYSCONFIGDATA_NAME=_sysconfigdata__$(DEB_HOST_MULTIARCH)
+define ruby_env
+  RUBYLIB=/usr/lib/$(DEB_HOST_MULTIARCH)/ruby-crossbuild/$$($(1) -e "puts 
RbConfig::CONFIG['ruby_version']")
+endef
+else
+define ruby_env
+endef
 endif
 
 ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
@@ -27,18 +34,15 @@
 ## missing (hardening) flags. Also enable Wall and Wextra to spot basic 
irregularities.
 export DEB_CFLAGS_MAINT_APPEND += $(shell dpkg-buildflags --get CPPFLAGS) 
-Wall -Wextra
 
-DH_ADDONS =
 ifneq ($(filter python3-selinux,$(DOPACKAGES)),)
 PY3VERSIONS = $(shell py3versions -rv)
-DH_ADDONS += --with=python3
 endif
 ifneq ($(filter ruby-selinux,$(DOPACKAGES)),)
 RUBY_VERSIONS := $(shell dh_ruby --print-supported)
-DH_ADDONS += --with=ruby
 endif
 
 %:
-   @dh $@ $(DH_ADDONS)
+   @dh $@
 
 ## Set up some variables to be passed to the upstream Makefile
 extra_make_args = ARCH=$(patsubst i%86,i386,$(DEB_HOST_GNU_CPU))
@@ -52,6 +56,7 @@
 endif
 ifneq ($(filter ruby-selinux,$(DOPACKAGES)),)
set -e; for version in $(RUBY_VERSIONS); do  \
+ $(call ruby_env,$$version) \
  $(MAKE) rubywrap $(extra_make_args) RUBY=$$version; \
done;
 endif
@@ -67,6 +72,7 @@
 endif
 ifneq ($(filter ruby-selinux,$(DOPACKAGES)),)
set -e; for version in $(RUBY_VERSIONS); do \
+ $(call ruby_env,$$version) \
  $(MAKE) install-rubywrap $(extra_make_args) RUBY=$$version 
DESTDIR="${CURDIR}/debian/tmp"; \
done;
 endif
@@ -80,6 +86,7 @@
 endif
 ifneq ($(filter ruby-selinux,$(DOPACKAGES)),)
set -e; for version in $(RUBY_VERSIONS); do  \
+ $(call ruby_env,$$version) \
  $(MAKE) clean-rubywrap $(extra_make_args) RUBY=$$version; \
done;
 endif

Bug#1033403: mpdecimal: Packet missing in bookworm

[henrynmail-deb...@yahoo.com]

Package: mpdecimal
Version: 2.4.2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: ftbfs
Usertags: rebootstrap

Dear Maintainer,

Source information for mpdecimal are missing for Debian bookworm.
No Source package available. Detected by rebootstrap, is market as 'add_need'.

Source for sid exist.

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

Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: unable to detect

Bug#1033402: mpdecimal: Packet mpdecimal missing in bookworm

[Henry N.]

Package: mpdecimal
Version: 2.4.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Usertags: rebootstrap

Dear Maintainer,

Source information for mpdecimal are missing for Debian bookworm.
No Source package available. Detected by rebootstrap, is market as 'add_need'.

Source for sid exist.

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

Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: unable to detect

Bug#1031816: [Pkg-freeipa-devel] Bug#1031816: Bug#1031816: tomcatjss: Migrate to Tomcat 10

[Markus Koschany]

Am Freitag, dem 24.03.2023 um 09:21 +0200 schrieb Timo Aaltonen:
> Markus Koschany kirjoitti 23.3.2023 klo 19.00:
> > Control: severity -1 serious
> > 
> > On Fri, 24 Feb 2023 11:48:36 +0200 Timo Aaltonen 
> > wrote:
> >   
> > > Upstream doesn't support tomcat10 yet, and tomcatjss fails to build with
> > > it.
> > 
> > Unfortunately we can only support one Tomcat version per release. We should
> > either migrate to tomcat10 or maybe it is possible to embed some of the
> > required tomcat9 classes in your source package as a workaround provided
> > the
> > changes are rather small and the security impact is negligible.
> 
> Right, but that's for bookworm+1? By that time I'm sure 
> jss/tomcatjss/dogtag have gained upstream support for tomcat10.

We are targeting Bookworm. We had Tomcat 8 in Stretch and Tomcat 9 in Buster
and Bullseye already. Tomcat 10 also targets Java 11 and later while Tomcat 9
was intended for Java 8 and later. We ship OpenJDK 17 in Bookworm. resteasy3.0
and tomcatjss are the only packages apart from i2p that still depend on
libtomcat9-java.


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

Bug#1033400: elpa-org-contrib

[H.-Dirk Schmitt]

In addition the emacs-el package should provide *elpa-org* to allow
installation of *elpa-org-contrib*.

Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+

[Florian Lehner]

Hi,

maybe some additional information.

The eBPF program is of type BPF_PROG_TYPE_PERF_EVENT and attached to all 
CPUs via the perf subsystem and the use of PERF_COUNT_SW_CPU_CLOCK. It 
is executed on a constant sampling frequency (usually 20 Hz).


We also do have qemus guest memory dumps available if this would help 
investigate the issue.


- florian

On Fri, 24 Mar 2023 12:44:33 +0100 =?utf-8?q?Tim_R=C3=BChsen?= 
 wrote:

Package: linux-image-amd64
Version: 6.1.20-1
Severity: important
X-Debbugs-Cc: tim.rueh...@gmx.de

Dear Maintainer,

   * What led up to the situation?

We run a priviledged eBPF based tool with a communication between kernel and 
user space.
It runs without issues on kernels 4.15 to 5.18.
On kernels 5.19+, the whole system freezes after a few minutes.
It seems that with more system activities (load, forks) the freeze happens 
earlier.
The underlying hardware seems to play no role, we could reproduce this on 
different
bare metal systems as well as within a qemu based VM.

Since the running program is rather complex, it is not easily possible to carve 
out a small reproducer.
We can provide gdb backtraces from freezes inside qemu.


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: No such file or directory
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 linux-image-amd64 depends on:
ii  linux-image-6.1.0-7-amd64  6.1.20-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LC_MONETARY = "en_DE.UTF-8",
LC_COLLATE = "en_DE.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory

Bug#1033401: unblock: src:dino-im/0.4.2-1

[Martin]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear release team,

I like to get clearance for uploading dino-im 0.4.2 to unstable, to get
it into bookworm.

Upstream release text:

> Maintenance release with fix for CVE-2023-28686 and bug fixes.

There are eight commits, from which five should definitively go into
bookworm (1, 2, 6, 7, 8). Two commits are not related to a bug report,
but solve relevant problems (3, 4). Only one is not relevant at all, but
it does not touch file we care about anyway (5).

There are no new features nor unnecessary changes, so I would very much
prefer to get the new version in instead of adding five to seven
patches.

Here is a description of the commits between 0.4.1 (now in testing) and
0.4.2 (to be uploaded):

1. acf9c694 * Fix C binding for gst_video_frame_get_data
Fix for: GTK4 - crash when answering video call #1267
> Fix C binding for gst_video_frame_get_data
https://github.com/dino/dino/issues/1267

2. 89b9110f * Improve history sync
Fix for: MUC MAM (0313) doesn't work #1386
> - Ensure we fully fetch desired history if possible (previously, duplicates
>   from offline message queue could hinder MAM sync)
> - Early drop illegal MAM messages so they don't pile up in the pending queue
>   waiting for their query to end (which it never will if they were not
>   requested in first place).
https://github.com/dino/dino/issues/1386

3. 481a68fd * Improve database performance while reconnecting and syncing
> Improve database performance while reconnecting and syncing
> Also move some tasks to low priority idle queue so they won't block UI updates
No bug report, but solves startup time issues some users reported.

4. 1738bf8d * data: Set StartupNotify to true in .desktop file
> data: Set StartupNotify to true in .desktop file
> GTK handles startup notifications, so advertise it in desktop
> file. This allows splash screens and other startup indications
> in DEs to work.
No bug report, but sounds like an issue worth solving.

5. b6f9b54d * Remove gspell
(not relevant to Debian: unused cmake/FindGspell.cmake removed, change
in github ci file)

6. 00482404 * Fix a crash if a message subnode is not found in a carbon
Fix for: A carbon crashes Dino #1392
> Fix a crash if a message subnode is not found in a carbon
https://github.com/dino/dino/issues/1392

7. 179c766d * Bind soup session lifetime to File provider/sender lifetime
Fix for: Dino crashes when sending or receiving files #1395 
> Bind soup session lifetime to File provider/sender lifetime
> Required since libsoup 3.4. Fixes #1395
https://github.com/dino/dino/issues/1395

8. baf96d9d * @ v0.4.2 origin/v0.4 Check sender of bookmark:1 updates
Fix for: dino-im: Insufficient message sender validation in Dino CVE-2023-28686
> Check sender of bookmark:1 updates
https://bugs.debian.org/1033370

Thanks in advance for your comments and decision!

Cheers

unblock src:dino-im/0.4.2-1

diff -Nru dino-im-0.4.1/.github/workflows/build.yml dino-im-0.4.2/.github/workflows/build.yml
--- dino-im-0.4.1/.github/workflows/build.yml	2023-03-01 23:30:00.0 +
+++ dino-im-0.4.2/.github/workflows/build.yml	2023-03-23 18:00:00.0 +
@@ -7,7 +7,7 @@
   - uses: actions/checkout@v2
   - run: sudo apt-get update
   - run: sudo apt-get remove libunwind-14-dev
-  - run: sudo apt-get install -y build-essential gettext cmake valac libgee-0.8-dev libsqlite3-dev libgtk-4-dev libnotify-dev libgpgme-dev libsoup2.4-dev libgcrypt20-dev libqrencode-dev libgspell-1-dev libnice-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libsrtp2-dev libwebrtc-audio-processing-dev libadwaita-1-dev
+  - run: sudo apt-get install -y build-essential gettext cmake valac libgee-0.8-dev libsqlite3-dev libgtk-4-dev libnotify-dev libgpgme-dev libsoup2.4-dev libgcrypt20-dev libqrencode-dev libnice-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libsrtp2-dev libwebrtc-audio-processing-dev libadwaita-1-dev
   - run: ./configure --with-tests --with-libsignal-in-tree
   - run: make
   - run: build/xmpp-vala-test
diff -Nru dino-im-0.4.1/VERSION dino-im-0.4.2/VERSION
--- dino-im-0.4.1/VERSION	2023-03-01 23:30:00.0 +
+++ dino-im-0.4.2/VERSION	2023-03-23 18:00:00.0 +
@@ -1 +1 @@
-RELEASE 0.4.1
+RELEASE 0.4.2
diff -Nru dino-im-0.4.1/cmake/FindGspell.cmake dino-im-0.4.2/cmake/FindGspell.cmake
--- dino-im-0.4.1/cmake/FindGspell.cmake	2023-03-01 23:30:00.0 +
+++ dino-im-0.4.2/cmake/FindGspell.cmake	1970-01-01 00:00:00.0 +
@@ -1,14 +0,0 @@
-include(PkgConfigWithFallback)
-find_pkg_config_with_fallback(Gspell
-PKG_CONFIG_NAME gspell-1
-LIB_NAMES gspell-1
-INCLUDE_NAMES gspell.h
-INCLUDE_DIR_SUFFIXES gspell-1 gspell-1/gspell
-DEPENDS GTK3
-)
-
-include(FindPackageHandleStandardArgs)
-find_package_handle_standard_args(Gspell
-REQUIRED_VARS Gspell_LIBRARY
-VERSION_VAR Gspell_VERSION)
-
diff -Nru 

Bug#1033106: safeeyes fails to load plugins with Python 3.11

[Julian Gilbey]

Hi!

With no response to the RC bug in 7 days, I've just uploaded an NMU to
DELAYED/7-days.

I have also fixed #1006942 at the same time by upgrading to version
2.1.5 and updating the Depends field; the differences between 2.1.3
and 2.1.5 are only minor.  (The diff-file attached is large primarily
because the new version has updated the translation files.)

The only file differences shown by debdiff on the generated debs is
that the egg-info files are now 2.1.5 rather than 2.1.3.

If you are happy with this new version, I will push the changes to
salsa once it is accepted into unstable.  If you would like me to skip
the delayed queue, I'm happy to do that, and if you would prefer me to
delete the updated version and fix it yourself, I can do that too.

Best wishes,

   Julian

On Fri, Mar 17, 2023 at 12:25:22PM +, Julian Gilbey wrote:
> Package: safeeyes
> Version: 2.1.3-1
> Severity: serious
> Tags: patch upstream
> 
> Safeeyes uses the deprecated inspect.getargspec() function, which was
> dropped in Python 3.11, so no plugins are loaded, significantly
> impairing the functionality of this package.
> 
> There is a one-line patch at
> https://github.com/slgobinath/SafeEyes/pull/505 (and a discussion at
> https://github.com/slgobinath/SafeEyes/issues/491)
> 
> Please could you apply it for bookworm?
> 
> Many thanks,
> 
>Julian
diff -Nru safeeyes-2.1.3/debian/changelog safeeyes-2.1.5/debian/changelog
--- safeeyes-2.1.3/debian/changelog	2021-09-04 19:00:04.0 +0100
+++ safeeyes-2.1.5/debian/changelog	2023-03-24 12:32:08.0 +
@@ -1,3 +1,12 @@
+safeeyes (2.1.5-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * New upstream version makes icon appear in KDE/Plasma and XFCE4 system
+tray once again (Closes: #1006942)
+  * Support Python 3.11 (Closes: #1033106)
+
+ -- Julian Gilbey   Fri, 24 Mar 2023 12:32:08 +
+
 safeeyes (2.1.3-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru safeeyes-2.1.3/debian/control safeeyes-2.1.5/debian/control
--- safeeyes-2.1.3/debian/control	2021-09-04 19:00:04.0 +0100
+++ safeeyes-2.1.5/debian/control	2023-03-24 12:32:08.0 +
@@ -13,8 +13,8 @@
 
 Package: safeeyes
 Architecture: all
-Depends: ${misc:Depends}, ${python3:Depends}, python3-gi, python3-dbus, gir1.2-gtk-3.0
-Recommends: gir1.2-appindicator3-0.1, xprintidle
+Depends: ${misc:Depends}, ${python3:Depends}, python3-gi, python3-dbus, gir1.2-gtk-3.0, gir1.2-notify-0.7
+Recommends: gir1.2-ayatanaappindicator3-0.1, xprintidle
 Description: Protect your eyes from eye strain using this continuous breaks
  Safe Eyes is a simple tool to remind you to take periodic breaks for your
  eyes. This is essential for anyone spending more time on the computer to
diff -Nru safeeyes-2.1.3/debian/patches/series safeeyes-2.1.5/debian/patches/series
--- safeeyes-2.1.3/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ safeeyes-2.1.5/debian/patches/series	2023-03-24 12:32:08.0 +
@@ -0,0 +1 @@
+support-python311.patch
diff -Nru safeeyes-2.1.3/debian/patches/support-python311.patch safeeyes-2.1.5/debian/patches/support-python311.patch
--- safeeyes-2.1.3/debian/patches/support-python311.patch	1970-01-01 01:00:00.0 +0100
+++ safeeyes-2.1.5/debian/patches/support-python311.patch	2023-03-24 12:32:08.0 +
@@ -0,0 +1,11 @@
+--- a/safeeyes/utility.py
 b/safeeyes/utility.py
+@@ -666,7 +666,7 @@
+ Check whether the given function is defined in the module or not.
+ """
+ if hasattr(module, method_name):
+-if len(inspect.getargspec(getattr(module, method_name)).args) == no_of_args:
++if len(inspect.getfullargspec(getattr(module, method_name)).args) == no_of_args:
+ return True
+ return False
+ 
diff -Nru safeeyes-2.1.3/.github/FUNDING.yml safeeyes-2.1.5/.github/FUNDING.yml
--- safeeyes-2.1.3/.github/FUNDING.yml	1970-01-01 01:00:00.0 +0100
+++ safeeyes-2.1.5/.github/FUNDING.yml	2023-03-09 12:28:03.0 +
@@ -0,0 +1,12 @@
+# These are supported funding model platforms
+
+github: slgobinath
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: 'https://www.paypal.com/paypalme/slgobinath'
diff -Nru safeeyes-2.1.3/.github/ISSUE_TEMPLATE/bug_report.md safeeyes-2.1.5/.github/ISSUE_TEMPLATE/bug_report.md
--- safeeyes-2.1.3/.github/ISSUE_TEMPLATE/bug_report.md	1970-01-01 01:00:00.0 +0100
+++ safeeyes-2.1.5/.github/ISSUE_TEMPLATE/bug_report.md	2023-03-09 12:28:03.0 +
@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: 

Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+

[Diederik de Haas]

Control: reassign -1 src:linux 6.1.20-1

On Friday, 24 March 2023 12:44:33 CET Tim Rühsen wrote:
> Package: linux-image-amd64
> Version: 6.1.20-1
> 
> We run a priviledged eBPF based tool with a communication between kernel and
> user space. It runs without issues on kernels 4.15 to 5.18.
> On kernels 5.19+, the whole system freezes after a few minutes.

Via https://snapshot.debian.org/binary/linux-image-amd64/ you can easily test 
various kernel versions. Could you try whether 5.19~rc4-1~exp1 indeed produces 
the problem?

> Since the running program is rather complex, it is not easily possible to
> carve out a small reproducer. We can provide gdb backtraces from freezes
> inside qemu.

Someone else would have to chime in for the backtraces; that's beyond my skill 
set.
Verifying in which kernel version/commit the issue started is still useful.

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

Bug#904211: maybe not 3.0.0

[Matthias Urlichs]

Well, updating to 3.0 alpha might be a bit too much right before a 
release, but please at least update to the latest 2.x version. Packages 
like scikit-learn depend on it.


--
-- regards
--
-- Matthias Urlichs

BEGIN:VCARD
VERSION:4.0
N:Urlichs;Matthias;;;
NICKNAME:Smurf
EMAIL;PREF=1:matth...@urlichs.de
TEL;TYPE=work;VALUE=TEXT:+49 911 59818 0
URL;TYPE=home:https://matthias.urlichs.de
END:VCARD


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1032380: arriero: AttributeError: module 'collections' has no attribute 'MutableSet'

[Josef Schneider]

Hello,

I have attached a debdiff where I import the collections.abc package 
which has the MutableSet attribute. With this fix, the package builds 
and `arriero --help` outputs the expected help menu. I can upload this 
RC bug fix as a NMU if you want. Thanks!


--
Josef Schneider

GPG Fingerprint 3267 0331 DB61 A817 7D25 4D05 5A44 BC12 F2A8 E58F
diff -Nru arriero-0.7~20161228/debian/changelog 
arriero-0.7~20161228/debian/changelog
--- arriero-0.7~20161228/debian/changelog   2022-04-29 01:44:11.0 
+0200
+++ arriero-0.7~20161228/debian/changelog   2023-03-24 13:10:39.0 
+0100
@@ -1,3 +1,10 @@
+arriero (0.7~20161228-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to import collections.abc in util.py (Closes: #1032380).
+
+ -- Josef Schneider   Fri, 24 Mar 2023 13:10:39 +0100
+
 arriero (0.7~20161228-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru arriero-0.7~20161228/debian/patches/0001-import-collections-abc.patch 
arriero-0.7~20161228/debian/patches/0001-import-collections-abc.patch
--- arriero-0.7~20161228/debian/patches/0001-import-collections-abc.patch   
1970-01-01 01:00:00.0 +0100
+++ arriero-0.7~20161228/debian/patches/0001-import-collections-abc.patch   
2023-03-24 13:10:39.0 +0100
@@ -0,0 +1,33 @@
+From 409dd804c2abb119582378cd6fa098ad8df01f3d Mon Sep 17 00:00:00 2001
+From: Josef Schneider 
+Date: Fri, 17 Mar 2023 13:16:43 +0100
+Subject: [PATCH] import collections.abc
+
+---
+ arriero/util.py | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/arriero/util.py b/arriero/util.py
+index 91e4121..07f877a 100644
+--- a/arriero/util.py
 b/arriero/util.py
+@@ -17,6 +17,7 @@
+ # Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+ 
+ import collections
++import collections.abc
+ import fcntl
+ import io
+ import itertools
+@@ -185,7 +186,7 @@ def chain_map(*ds, **kw):
+ return ChainMap(*itertools.chain(ds, [kw]))
+ 
+ 
+-class OrderedSet(deb822.OrderedSet, collections.MutableSet):
++class OrderedSet(deb822.OrderedSet, collections.abc.MutableSet):
+ 
+ discard = deb822.OrderedSet.remove
+ 
+-- 
+2.38.1
+
diff -Nru arriero-0.7~20161228/debian/patches/series 
arriero-0.7~20161228/debian/patches/series
--- arriero-0.7~20161228/debian/patches/series  1970-01-01 01:00:00.0 
+0100
+++ arriero-0.7~20161228/debian/patches/series  2023-03-24 13:10:39.0 
+0100
@@ -0,0 +1 @@
+0001-import-collections-abc.patch


OpenPGP_0x5A44BC12F2A8E58F.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1033400: elpa-org: Bookworm emacs 28 has org-mode included in newer version as provided here.

[H . -Dirk Schmitt]

Package: elpa-org
Version: 9.5.2+dfsh-4
Severity: normal
X-Debbugs-Cc: none, H.-Dirk Schmitt 

The *emacs-el* package (source: emacs) has org-mode 9.5.5.
The *elpa-org* package hast org-mode in the older version 9.5.2.

This is not a cosmetic problem.
In emacs M-x `org-version` shows that the „outdated“ elpa-org package is used.

I suggest that either emacs-el or elpa-org package should set a conflict againt 
the other package.


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

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

Versions of packages elpa-org depends on:
ii  dh-elpa-helper  2.0.16
ii  elpa-htmlize1.56-1
ii  emacsen-common  3.0.5

Versions of packages elpa-org recommends:
ii  emacs  1:28.2+1-13
ii  emacs-gtk [emacs]  1:28.2+1-13

Versions of packages elpa-org suggests:
pn  ditaa  
pn  org-mode-doc   
ii  texinfo6.8-6+b1
ii  texlive-fonts-recommended  2022.20230122-2
ii  texlive-latex-extra2022.20230122-2

-- no debconf information

Bug#1032471: gxemul: non-working TAP networking support

[Göran Weinholt]

On Fri, Mar 24, 2023 at 11:37:17AM +0100, Jan-Benedict Glaw wrote:
> Hi!
> 
> How about adding the patch I suggested to gxemul's Debian package?
> That works and makes gxemul _much_ more useable.

Bookwork is being released and unstable is in freeze.



The patch sounds like it would be a good addition to the package and I
will have a look at adding it after the freeze.

/Göran

Bug#1033399: pre-approve unblock: tryton-server/6.0.29-2

[Mathias Behrle]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: tryton-ser...@packages.debian.org
Control: affects -1 + src:tryton-server

Please pre-approve the unblock of package tryton-server

[ Reason ]
This release targets several fixes that should go into bookworm:

  * Add missing quotes in maintainer scripts (Closes: #1033055).
  * Make conf file parsing section aware (Closes: #1033055).
  * Correct a variable typo (Closes: #1033055).
  * Remove lsb-base from Depends.


[ Impact ]
There can be errors when using spaces or something alike in the debconf related
questions.

[ Tests ]
Salsa CI tests are passing
https://salsa.debian.org/tryton-team/tryton-server/-/pipelines/513249
as well as all build tests.

I did a full manual test over all packages.


[ Risks ]

The code changes are trivial enough to not expect regressions.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing


unblock tryton-server/6.0.29-2



-- 

Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6


tryton-server_6.0.29_-1_tryton-server_6.0.29-2.debdiff
Description: Binary data

Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+

[Tim Rühsen]

Package: linux-image-amd64
Version: 6.1.20-1
Severity: important
X-Debbugs-Cc: tim.rueh...@gmx.de

Dear Maintainer,

   * What led up to the situation?

We run a priviledged eBPF based tool with a communication between kernel and 
user space.
It runs without issues on kernels 4.15 to 5.18.
On kernels 5.19+, the whole system freezes after a few minutes.
It seems that with more system activities (load, forks) the freeze happens 
earlier.
The underlying hardware seems to play no role, we could reproduce this on 
different
bare metal systems as well as within a qemu based VM.

Since the running program is rather complex, it is not easily possible to carve 
out a small reproducer.
We can provide gdb backtraces from freezes inside qemu.


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: No such file or directory
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 linux-image-amd64 depends on:
ii  linux-image-6.1.0-7-amd64  6.1.20-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "en_DE.UTF-8",
LC_MONETARY = "en_DE.UTF-8",
LC_COLLATE = "en_DE.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory
(gdb) thread apply all bt full

Thread 8 (Thread 1.8 (CPU#7 [running])):
#0  arch_atomic_read (v=0x837c2b4c ) at 
arch/x86/include/asm/atomic.h:29
No locals.
#1  atomic_read (v=0x837c2b4c ) at 
include/linux/atomic/atomic-instrumented.h:28
No locals.
#2  pv_hybrid_queued_unfair_trylock (lock=0x837c2b4c ) 
at kernel/locking/qspinlock_paravirt.h:88
val = 
#3  __pv_queued_spin_lock_slowpath (lock=0x837c2b4c , 
val=) at kernel/locking/qspinlock.c:446
prev = 
next = 
node = 0x88813bdf1b40
old = 
tail = 2097152
idx = 0
queue = 
cnt = 
__PTR = 
VAL = 
_val = 
__PTR = 
VAL = 
__vpp_verify = 
_val = 
__PTR = 
VAL = 
__vpp_verify = 
pao_ID__ = 
pao_tmp__ = 
pto_val__ = 
pto_tmp__ = 
pao_ID__ = 
pao_tmp__ = 
pto_val__ = 
pto_tmp__ = 
pao_ID__ = 
pao_tmp__ = 
pto_val__ = 
pto_tmp__ = 
#4  0x81a2b6f0 in pv_queued_spin_lock_slowpath (val=7, 
lock=0x837c2b4c ) at arch/x86/include/asm/paravirt.h:591
__esi = 
__edx = 
__edi = 
__ecx = 
__eax = 
#5  queued_spin_lock_slowpath (val=7, lock=0x837c2b4c ) 
at arch/x86/include/asm/qspinlock.h:51
No locals.
#6  queued_spin_lock (lock=0x837c2b4c ) at 
include/asm-generic/qspinlock.h:114
val = 7
val = 
#7  do_raw_spin_lock (lock=0x837c2b4c ) at 
include/linux/spinlock.h:186
No locals.
#8  __raw_spin_lock (lock=0x837c2b4c ) at 
include/linux/spinlock_api_smp.h:134
No locals.
#9  _raw_spin_lock (lock=lock@entry=0x837c2b4c ) at 
kernel/locking/spinlock.c:154
No locals.
#10 0x812e1ba7 in spin_lock (lock=0x837c2b4c ) 
at include/linux/spinlock.h:350
No locals.
#11 alloc_vmap_area (size=size@entry=20480, align=align@entry=16384, 
vstart=vstart@entry=18446683600570023936, vend=vend@entry=18446718784942112767, 
node=node@entry=-1, gfp_mask=3264, gfp_mask@entry=3520) at mm/vmalloc.c:1634
va = 0x88802dbb05c0
freed = 0
addr = 
purged = 0
ret = 
retry = 
__func__ = "alloc_vmap_area"
#12 0x812e2111 in __get_vm_area_node (size=20480, size@entry=16384, 
align=align@entry=16384, shift=shift@entry=12, flags=flags@entry=34, 
start=start@entry=18446683600570023936, end=end@entry=18446718784942112767, 
node=-1, gfp_mask=3520, caller=0x8109ad0f ) at 
mm/vmalloc.c:2501
va = 
area = 0x888113d8dfc0
requested_size = 16384
#13 0x812e52c4 in __vmalloc_node_range (size=, 
size@entry=16384, align=align@entry=16384, start=, 
end=, gfp_mask=gfp_mask@entry=3520, prot=..., 
vm_flags=, node=, caller=) at 
mm/vmalloc.c:3173
area = 
ret = 
kasan_flags = 
real_size = 16384
real_align = 16384
shift = 12
again = 
#14 

Bug#1033344: unblock: src:texlive-extra/2022.20230122-3

[Preuße]

Control: tags -1 - moreinfo

On 24.03.2023 09:26, Sebastian Ramacher wrote:

On 2023-03-22 23:33:28 +0100, Hilmar Preusse wrote:


Hi,


Package: release.debian.org Severity: normal User:
release.debian@packages.debian.org Usertags: unblock

Please unblock package src:texlive-extra. I did not upload the
package to unstable, I'd like to hear your decision beforehand.


The diff looks reasonable. Please let us know once the version is
available in unstable.


Uploaded right now.

Hilmar
--
sigfault

Bug#1022964: libselinux FTCBFS: python and ruby extensions

[James Addison]

Source: libselinux
Followup-For: Bug #1022964
X-Debbugs-Cc: hel...@subdivi.de

Hi Helmut,

Could you check whether the patch is missing a 'call ruby_env' line in the
debian/rules 'override_dh_auto_clean' target?

(it looks like it could be, but I may be mistaken)

Thanks,
James

Bug#1033304: request-tracker5: debianisation of version interferes with doc linking

[Andrew Ruthven]

Hey,

Thank you for the bug report. I'm just testing a fix now.

This doesn't affect the RT4 packages as RT4 doesn't have a web
interface for configuring RT, and even when viewing the config, it
doesn't link to the docs.

Cheers,
Andrew

On Wed, 2023-03-22 at 11:51 +1100, AP wrote:
> 
> RT5 (and possibly RT4) uses the version number to generate a URL for
> its documentation.
> This URL is in use when configuring the system via the web interface
> (click on a config
> name and it takes you to the help for it).
> 
> As a result the help results in a 404 until you manually remove the
> debian component of
> the version.
> 
> This error is the result of the debianize_version.diff patch which
> changes the version
> globally.
-- 
Andrew Ruthven, Wellington, New Zealand
and...@etc.gen.nz |
Catalyst Cloud:   | This space intentionally left blank
 https://catalystcloud.nz |

Bug#1005863: gcc: should reject combination of i686 architecture and fcf-protection feature

[James Addison]

Followup-For: Bug #1005863
Control: affects -1 = sudo

Bug#1018061: pads: segfault at 3a ip

[Bernhard Übelacker]

Am 23.03.23 um 17:38 schrieb Tim McConnell:

Bernhard,
Just cause I said it was fixed this happens to show up in journalctl:
systemd-coredump[3614]: Process 1704 (pads) of user 0 dumped core.
   
   Module

libsystemd.so.0 from deb systemd-252.5-2.amd64
   Stack trace of thread 1704:
   #0 0x5600f24f6954 
print_arp_asset_screen (pads + 0x9954)
   #1 0x5600f24f66f0 
print_arp_asset (pads + 0x96f0)
   #2 0x7fdc7fdb54f6 n/a 
(libpcap.so.0.8 + 0x84f6)
   #3 0x7fdc7fdb58ec n/a 
(libpcap.so.0.8 + 0x88ec)
   #4 0x7fdc7fdbcd1d 
pcap_loop (libpcap.so.0.8 + 0xfd1d)
   #5 0x5600f24efe5b 
main_pads (pads + 0x2e5b)
   #6 0x5600f24ef47b main 
(pads + 0x247b)
   #7 0x7fdc7fbec18a 
__libc_start_call_main (libc.so.6 + 0x2718a)
   #8 0x7fdc7fbec245 
__libc_start_main_impl (libc.so.6 + 0x27245)
   #9 0x5600f24ef4b1 _start 
(pads + 0x24b1)
   ELF object binary
architecture: AMD x86-64
Mar 04 14:31:02 DebianTim systemd[1]:
systemd-coredump@0-3613-0.service: Deactivated successfully.

Well I thought it was fixed :-(



Hello Time,
are you sure that your rebuilt package is still in place?
The offsets in your new backtrace are exactly the same as
in the email from 8 Feb 2023.

We have not changed the version of the rebuilt package.
Additionally built with "-b".
Then with a "apt dist-upgrade" always
the Debian version gets reinstalled.

Sorry for not mentioning that extra care has to be taken
to hold the rebuilt package version in place.

Kind regards,
Bernhard

Bug#1032471: gxemul: non-working TAP networking support

[Jan-Benedict Glaw]

Hi!

How about adding the patch I suggested to gxemul's Debian package?
That works and makes gxemul _much_ more useable.

Thanks,
  Jan-Benedict

-- 


signature.asc
Description: PGP signature

Bug#1033397: Gnus cannot store some incoming mail into nnml

[Florian Weimer]

Package: emacs
Version: 1:28.2+1-13
Severity: important

A regression in Emacs 28 prevents Gnus from importing any further mail
into its nnml sotre once a message with certain (valid) header is
encountered in incoming mail.  The gnu.org systems seem to be having
problems right now, but it's discussed in this subthread:

From: Florian Weimer 
Subject: Re: master ef14acf: Make nnml handle invalid non-ASCII headers more
 consistently
To: emacs-de...@gnu.org
Cc: Lars Ingebrigtsen , d...@gnus.org
Date: Fri, 16 Dec 2022 23:42:21 +0100 (13 weeks, 6 days, 11 hours ago)
Message-ID: <874jtvq8c2@oldenburg.str.redhat.com>
  
Please backport the commit below; it fixes the issue and is supposed
not to break the .overview file encoded.

This does not impact all Emacs users (or even all Gnus users), so I'm
not setting severity to serious, but it's an upgrade blocker for nnml
users.

commit 23f7c9c2a92e4619b7c4d2286d4249f812cd695d
Author: Eli Zaretskii 
Date:   Mon Dec 19 19:01:04 2022 +0200

Fix storing email into nnmail by Gnus

* lisp/gnus/nnml.el (nnml--encode-headers): Wrap
'rfc2047-encode-string' calls with 'ignore-errors', to avoid
disrupting email workflows due to possibly-invalid headers.
Reported by Florian Weimer .

diff --git a/lisp/gnus/nnml.el b/lisp/gnus/nnml.el
index 40e4b9ea828..7aa445e6646 100644
--- a/lisp/gnus/nnml.el
+++ b/lisp/gnus/nnml.el
@@ -776,17 +776,22 @@ article number.  This function is called narrowed to an 
article."
(nnml--encode-headers headers)
headers
 
+;; RFC2047-encode Subject and From, but leave invalid headers unencoded.
 (defun nnml--encode-headers (headers)
   (let ((subject (mail-header-subject headers))
(rfc2047-encoding-type 'mime))
 (unless (string-match "\\`[[:ascii:]]*\\'" subject)
-  (setf (mail-header-subject headers)
-   (mail-encode-encoded-word-string subject t
+  (let ((encoded-subject
+ (ignore-errors (mail-encode-encoded-word-string subject t
+(if encoded-subject
+(setf (mail-header-subject headers) encoded-subject)
   (let ((from (mail-header-from headers))
(rfc2047-encoding-type 'address-mime))
 (unless (string-match "\\`[[:ascii:]]*\\'" from)
-  (setf (mail-header-from headers)
-   (rfc2047-encode-string from t)
+  (let ((encoded-from
+ (ignore-errors (rfc2047-encode-string from t
+(if encoded-from
+(setf (mail-header-from headers) encoded-from))
 
 (defun nnml-get-nov-buffer (group  incrementalp)
   (let ((buffer (gnus-get-buffer-create