Bug#1074384: slurm-wlm-basic-plugins, depends on 64-bit only library

[Chris Hofstaedtler]

Hi,

this bug is blocking migration of 23.11.7-1 to testing, thereby
blocking other bug fixes.

On Thu, Jun 27, 2024 at 04:52:23PM +0100, Peter Green wrote:
> slurm-wlm-basic-plugins depends on libpmix2t64 and slum-wlm
> build-depends on , which is no longer
> available on 32-bit architectures.

Could you please take care of it?

Chris

Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device)

[Chris Hofstaedtler]

Control: retitle -1 initramfs-tools: duplicates nvidia firmware files

On Fri, Jul 19, 2024 at 04:43:47PM +0200, Diederik de Haas wrote:
> > In any case, the upgrade should work for any user, including when
> > all these packages are needed.
> 
> The real problem seems to be the size of /boot/ ...

Not really. A large part of the problem is that initramfs explodes
the size of the nvidia firmware.

On the root file system, in /usr/lib/firmware, the nvidia firmware
files are 66MB (uncompressed!).
However, the initrd.img grows from 64M to 250M (compressed!) when
firmware-nvidia-graphics is installed. There is something seriously
wrong here.

One of the things I've noticed:

/usr/lib/firmware/nvidia/tu104/gsp is supposed to be a symlink to
/usr/lib/firmware/nvidia/tu102/gsp. However, in initrd.img, this is
a copy of the directory; accounting for 25M on its own.

No wonder the initrd is way too large.

There are probably more cases where the symlinks are not preserved.
This needs to be fixed in initramfs (or whatever hook script copies
the firmware files).

Chris

Bug#1010445: mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12)

[Chris Hofstaedtler]

On Thu, Jul 18, 2024 at 06:55:03PM +0200, Paul Gevers wrote:
> Release Team member here. mono is a key package [1], meaning it's hard to
> remove. I note that src:mono is at least needed for src:gdcm which is at
> least needed for src:opencv which is at least needed for src:ffmpeg.

src:gdcm could likely easily drop its -cil packages.

> If mono should be removed

That's the question that needs to be answered somehow, first.

Chris

Bug#1076374: libplayeronecamera2t64: ineffective replaces for /usr/lib/udev/rules.d/99-player_one_astronomy.rules causes file loss

[Chris Hofstaedtler]

Thorsten, Helmut,

On Mon, Jul 15, 2024 at 01:09:09PM +0200, Helmut Grohne wrote:
> Package: libplayeronecamera2t64
> Version: 3.1.0+20221218103507-2
> Severity: serious
[..]
> thank you for applying our /usr-move patches. Unfortunately, this one
> went wrong and it went to unstable rather than experimental.

I'm very sorry this one slipped through. I should have rechecked
this patch after the t64 migration mostly settled.

The following upgrade scenario demonstrates the loss. It may be
possible to construct a simpler scenario. (This needs mmdebstrap 1.5.1-4 or
better.)

mmdebstrap \
  --components="main non-free" \
  --include=libplayeronecamera2 \
  --hook-dir=/usr/share/mmdebstrap/hooks/no-merged-usr \
  --chrooted-customize-hook='rm /etc/unsupported-skip-usrmerge-conversion' \
  --chrooted-customize-hook='apt update' \
  --chrooted-customize-hook='apt install --reinstall -y usrmerge' \
  --chrooted-customize-hook='ls -l /' \
  --chrooted-customize-hook='dpkg -L libplayeronecamera2' \
  --chrooted-customize-hook='sed -i -e s/bookworm/unstable/ -e /unstable-/d  
/etc/apt/sources.list' \
  --chrooted-customize-hook='apt update' \
  --chrooted-customize-hook='apt upgrade -y libc6 systemd' \
  --chrooted-customize-hook='cd /tmp && apt download libplayeronecamera2t64' \
  --chrooted-customize-hook='cd /tmp && dpkg --auto-deconfigure --unpack *.deb' 
\
  --chrooted-customize-hook='dpkg -l libplayerone*' \
  --chrooted-customize-hook='ls -la 
/lib/udev/rules.d/99-player_one_astronomy.rules' \
  --chrooted-customize-hook='apt install -f -y' \
  --chrooted-customize-hook='dpkg -l libplayerone*' \
  --chrooted-customize-hook='ls -la 
/lib/udev/rules.d/99-player_one_astronomy.rules' \
  bookworm /dev/null

> If you feel that a stronger mitigation is necessary, I can supply a
> patch adding protective diversions (via maintainer scripts).
> 
> Please let me know your preference. Roughly speaking your options now
> are:
>  * rename the rules file (closing both bugs)
>  * move the rules file to a -common package (closing the -2 bug)
>  * upgrade Replaces to Conflicts (closing the -1 bug)
>  * request diversion-based mitigation (closing the -1 bug)

I'll attach a patch implementing the last option. As you can see this is far
from beautiful. I'd suggest applying the patch _and_ switching
Replaces to Conflicts to be extra safe.

Testing the new version could be done with the same script as above, but
replacing this line:

-  --chrooted-customize-hook='cd /tmp && apt download libplayeronecamera2t64' \
+  --customize-hook='upload 
'$(pwd)'/libplayeronecamera2t64_3.1.0+20221218103507-2.1_arm64.deb 
/tmp/new.deb' \

Once again, I'm sorry this slipped through.

Chris

diff -Nru libplayerone-3.1.0+20221218103507/debian/changelog 
libplayerone-3.1.0+20221218103507/debian/changelog
--- libplayerone-3.1.0+20221218103507/debian/changelog  2024-07-13 
12:36:28.0 +0200
+++ libplayerone-3.1.0+20221218103507/debian/changelog  2024-07-15 
18:53:25.0 +0200
@@ -1,3 +1,10 @@
+libplayerone (3.1.0+20221218103507-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add DEP17 P1 mitigations. (Closes: #1076374)
+
+ -- Chris Hofstaedtler   Mon, 15 Jul 2024 18:53:25 +0200
+
 libplayerone (3.1.0+20221218103507-2) unstable; urgency=medium
 
   * upload to unstable
diff -Nru 
libplayerone-3.1.0+20221218103507/debian/libplayeronecamera2t64.lintian-overrides
 
libplayerone-3.1.0+20221218103507/debian/libplayeronecamera2t64.lintian-overrides
--- 
libplayerone-3.1.0+20221218103507/debian/libplayeronecamera2t64.lintian-overrides
   2024-07-13 12:36:28.0 +0200
+++ 
libplayerone-3.1.0+20221218103507/debian/libplayeronecamera2t64.lintian-overrides
   2024-07-15 18:53:25.0 +0200
@@ -1,3 +1,7 @@
 # that is the way upstream delivers stuff
 hardening-no-bindnow
 libplayeronecamera2t64: package-name-doesnt-match-sonames libPlayerOneCamera3
+# begin-remove-after: released:trixie
+# DEP17P7 mitigation
+diversion-for-unknown-file lib/udev/rules.d/99-player_one_astronomy.rules [*]
+# end-remove-after
diff -Nru 
libplayerone-3.1.0+20221218103507/debian/libplayeronecamera2t64.postinst 
libplayerone-3.1.0+20221218103507/debian/libplayeronecamera2t64.postinst
--- libplayerone-3.1.0+20221218103507/debian/libplayeronecamera2t64.postinst
1970-01-01 01:00:00.0 +0100
+++ libplayerone-3.1.0+20221218103507/debian/libplayeronecamera2t64.postinst
2024-07-15 18:53:25.0 +0200
@@ -0,0 +1,9 @@
+#!/bin/sh
+
+# begin-remove-after: released:trixie
+if test "$1" = configure; then
+   dpkg-divert --no-rename --package libplayeronecamera2t64 --divert 
/lib/udev/rules.d/99-player_one_astronomy.rules.usr-is-merged --remove 
/lib/udev/rules.d/99-player_one_astronomy.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
diff -Nru 
libplayerone-3.1.0+20221218103507/debian/libplayeronecamera2t64.preinst 
libplayerone-3.1.0+20221218103

Bug#1076381: librav1e0.7: trying to overwrite librav1e.so.0.7.1', which is also in package librav1e0:amd64 0.7.1-2

[Chris Hofstaedtler]

On Mon, Jul 15, 2024 at 02:18:46PM +0200, Christian Marillat wrote:
> | dpkg: error processing archive 
> /var/cache/apt/archives/librav1e0.7_0.7.1-3+b1_amd64.deb (--unpack):
> |  trying to overwrite '/usr/lib/x86_64-linux-gnu/librav1e.so.0.7.1', which 
> is also in package librav1e0:amd64 0.7.1-2

Unsurprisingly, the same is true on arm64:

| Selecting previously unselected package librav1e0.7:arm64.
| Preparing to unpack .../04-librav1e0.7_0.7.1-3+b1_arm64.deb ...
| Unpacking librav1e0.7:arm64 (0.7.1-3+b1) ...
| dpkg: error processing archive 
/tmp/apt-dpkg-install-v30v4R/04-librav1e0.7_0.7.1-3+b1_arm64.deb (--unpack):
|  trying to overwrite '/usr/lib/aarch64-linux-gnu/librav1e.so.0.7.1', which is 
also in package librav1e0:arm64 0.7.1-2

Bug#1076298: src:dput: fails to migrate to testing for too long: uploader built arch:all binary

[Chris Hofstaedtler]

On Sun, Jul 14, 2024 at 08:19:29PM +1000, Ben Finney wrote:
> On 14-Jul-2024, Paul Gevers wrote:
> 
> > You should only upload the source, not the arch:all binary.
> 
> Thank you, I'll do that. But I'm still concerned about a couple of issues
> this raises:
> 
> That admonition appears to conflict with a different policy I'd learned:
> 
> The package upload should include a built binary package, to demonstrate
> that it *can* build and to lower the incidence of uploads that are destined
> to fail to build from source.
> 
> Has that policy been rescinded?

I am not aware that this is written down anywhere.

> If not, how is it compatible with the
> advice you cited?

TTBOMK the rules currently are: source-only uploads are perfectly
fine and desirable. In a few exceptional cases, binaries must be
provided; these are (at least): introduction of new source package
(= "NEW"), introduction of new binary package (= "binNEW"), upload
of a non-free package that is not auto-built.

> > > Where can I read more to understand what went wrong here and
> > > how to not have a package blocked this way?
> > 
> > https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
> > second section.
> 
> Oh, I had interpreted that differently: that the binary packages would not
> migrate, but that the source package would be re-built and *that* would
> migrate to testing.
> 
> You mentioned that the build daemons do not build “Architecture: all”
> packages? Is that a temporary fault, or is it intentional?

The buildds can build "Architecture: all" packages. However, large
parts of our infrastructure and customs are not prepared to deal
with rebuilds of "Architecture: all" packages, so this is not done.

I'll point out that any rebuilds on buildds also change the version
number, e.g. by appending +b1 (or higher).

Hope this helps,
Chris

PS: thinking about all this a bit more, ISTM we are missing the
"throw away" parts.

Bug#1076235: grub-efi-arm64-unsigned: trying to overwrite '/usr/lib/grub/arm64-efi/monolithic/gcdaa64.efi', which is also in package grub-efi-arm64-bin 2.12-2

[Chris Hofstaedtler]

Package: grub-efi-arm64-unsigned
Version: 2.12-4
Severity: serious
Control: tags -1 + sid

Upgrading grub on aarch64 fails, like this:

Preparing to unpack .../12-grub-efi-arm64_2.12-4_arm64.deb ...
Unpacking grub-efi-arm64 (2.12-4) over (2.12-2) ...
Preparing to unpack .../13-grub2-common_2.12-4_arm64.deb ...
Unpacking grub2-common (2.12-4) over (2.12-2) ...
Selecting previously unselected package grub-efi-arm64-unsigned.
Preparing to unpack .../14-grub-efi-arm64-unsigned_2.12-4_arm64.deb ...
Unpacking grub-efi-arm64-unsigned (2.12-4) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-GFZQXm/14-grub-efi-arm64-unsigned_2.12-4_arm64.deb 
(--unpack):
 trying to overwrite '/usr/lib/grub/arm64-efi/monolithic/gcdaa64.efi', which is 
also in package grub-efi-arm64-bin 2.12-2
Preparing to unpack .../15-grub-efi-arm64-bin_2.12-4_arm64.deb ...
Unpacking grub-efi-arm64-bin (2.12-4) over (2.12-2) ...
Preparing to unpack .../16-grub-common_2.12-4_arm64.deb ...
Unpacking grub-common (2.12-4) over (2.12-2) ...
...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-GFZQXm/14-grub-efi-arm64-unsigned_2.12-4_arm64.deb
Error: Sub-process /usr/bin/dpkg returned an error code (1)

I imagine additional relationships need to be declared.

Chris

Bug#1076069: python-django: CVE-2024-38875 CVE-2024-39329 CVE-2024-39330 CVE-2024-39614

[Chris Lamb]

Package: python-django
Version: 1:1.11.29-1+deb10u11
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

Django upstream have reported the following four vulnerabilities:

https://www.djangoproject.com/weblog/2024/jul/09/security-releases/

I have not yet investigated which, if any, of these vulnerabilities
apply to which versions of src:python-django.

However, an upload to unstable will follow the reporting of this bug,
and an upload to experimental will take place once a new 5.1 beta is
released.


CVE-2024-38875[0]:
| An issue was discovered in Django 4.2 before 4.2.14 and 5.0 before
| 5.0.7. urlize and urlizetrunc were subject to a potential denial of
| service attack via certain inputs with a very large number of
| brackets.


CVE-2024-39329[1]:
| An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before
| 4.2.14. The django.contrib.auth.backends.ModelBackend.authenticate()
| method allows remote attackers to enumerate users via a timing
| attack involving login requests for users with an unusable password.


CVE-2024-39330[2]:
| An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before
| 4.2.14. Derived classes of the django.core.files.storage.Storage
| base class, when they override generate_filename() without
| replicating the file-path validations from the parent class,
| potentially allow directory traversal via certain inputs during a
| save() call. (Built-in Storage sub-classes are unaffected.)


CVE-2024-39614[3]:
| An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before
| 4.2.14. get_supported_language_variant() was subject to a potential
| denial-of-service attack when used with very long strings containing
| specific characters.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-38875
https://www.cve.org/CVERecord?id=CVE-2024-38875
[1] https://security-tracker.debian.org/tracker/CVE-2024-39329
https://www.cve.org/CVERecord?id=CVE-2024-39329
[2] https://security-tracker.debian.org/tracker/CVE-2024-39330
https://www.cve.org/CVERecord?id=CVE-2024-39330
[3] https://security-tracker.debian.org/tracker/CVE-2024-39614
https://www.cve.org/CVERecord?id=CVE-2024-39614


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#1070350: xorg: diff for NMU version 1:7.7+23.1

[Chris Hofstaedtler]

Control: tags 1070350 + patch
Control: tags 1070350 + pending


I've checked the archive and apparently nothing (build-)depends on
xorg-dev. Thus it seems safe to remove libdmx-dev from this
metapackage.

I've uploaded an NMU as 1:7.7+23.1 to DELAYED/10.

Feel free to reschedule / supersede / cancel.

Best,
Chris

diff -Nru xorg-7.7+23/debian/changelog xorg-7.7+23.1/debian/changelog
--- xorg-7.7+23/debian/changelog	2021-08-18 13:00:51.0 +0200
+++ xorg-7.7+23.1/debian/changelog	2024-07-08 14:45:55.0 +0200
@@ -1,3 +1,10 @@
+xorg (1:7.7+23.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop libdmx-dev from xorg-dev meta-package. (Closes: #1070350)
+
+ -- Chris Hofstaedtler   Mon, 08 Jul 2024 14:45:55 +0200
+
 xorg (1:7.7+23) unstable; urgency=medium
 
   [ Timo Aaltonen ]
diff -Nru xorg-7.7+23/debian/control xorg-7.7+23.1/debian/control
--- xorg-7.7+23/debian/control	2021-08-18 09:24:40.0 +0200
+++ xorg-7.7+23.1/debian/control	2024-07-08 14:45:44.0 +0200
@@ -125,7 +125,6 @@
 Package: xorg-dev
 Architecture: all
 Depends:
- libdmx-dev,
  libfontenc-dev,
  libfs-dev,
  libice-dev,

Bug#1075961: FTBFS: hep.c:985:41: error: implicit declaration of function ‘inet_ntop’

[Chris Hofstaedtler]

Source: kamailio
Version: 5.6.3-2
Severity: serious
Tags: ftbfs

kamailio currently FTBFS on s390x, but built there before.
The same problem can be observed on ppc64:

https://buildd.debian.org/status/fetch.php?pkg=kamailio=s390x=5.8.2-2=1720212227=0

hep.c: In function ‘hepv3_get_chunk’:
hep.c:985:41: error: implicit declaration of function ‘inet_ntop’ 
[-Werror=implicit-function-declaration]
  985 | inet_ntop(AF_INET, 
&(hg->hep_src_ip4->data), ipstr,
  | ^
gcc -fPIC -DPIC -pthread -DKSR_PTHREAD_MUTEX_SHARED -Wall -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DVERSION_NODATE   -DNAME='"kamailio"' 
-DVERSION='"5.8.2"' -DARCH='"s390x"' -DOS='linux_' -DOS_QUOTED='"linux"' 
-DCOMPILER='"gcc 13.3.0"' -D__CPU_s390x -D__OS_linux -DVERSIONVAL=5008002 
-DCFG_DIR='"/etc/kamailio/"' -DSHARE_DIR='"/usr/share/kamailio/"' 
-DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MMAP -DDNS_IP_HACK 
-DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE 
-DUSE_DNS_FAILOVER -DUSE_DST_BLOCKLIST -DUSE_NAPTR -DMEM_JOIN_FREE -DF_MALLOC 
-DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS 
-DSTATISTICS -DMALLOC_STATS -DUSE_SCTP -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN 
-DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL 
-DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_IP_MREQN 
-DUSE_RAW_SOCKS -DUSE_PTHREAD_MUTEX -DHAVE_EPOLL -DHAVE_SIGIO_RT 
-DSIGINFO64_WORKAROUND -DUSE_FUTEX -DHAVE_SELECT  -DMOD_NAME='"sipcapture"' 
-DMOD_NAMEID='sipcapture' -c sipcapture.c -o sipcapture.o -MMD -MP
In file included from ../../core/atomic_ops.h:180,
 from ../../core/locking.h:72,
 from ../../core/rpc.h:34,
 from ../../core/sr_module.h:36,
 from sipcapture.c:54:
...
make[4]: *** [../../Makefile.rules:100: hep.o] Error 1
...

Bug#1074175: netkit-rwho: remove for trixie?

[Chris Hofstaedtler]

On Fri, Jul 05, 2024 at 09:24:18AM +0200, Simon Josefsson wrote:
> First, I think we need to understand the rationale for doing anything
> about 'netkit-rwho': do we want to do something because 1) it is not
> maintained upstream? or 2) because it is an insecure design?, or 3)
> something else?

At least 1) and 2).

> [..]

> So, are our reason for doing anything about netkit-rwho really because
> netkit upstream is not maintained?

There is no upstream. Arch uses _us_ as their upstream.

The last release tarball is stamped in the year 2000.

> I haven't analyzed what rwho(d) implementations are out there.  I see
> NetBSD/FreeBSD has one still in -current, but OpenBSD removed it during
> 5.x.  Are people aware of any other implementations worth considering?

IMO we should follow OpenBSD's 2015 (or earlier) decision.

Chris

Bug#1074399: libcgi-application-plugin-authentication-perl: autopkgtest regression: libcgi-application-plugin-authentication-perl vs libcgi-pm-perl

[Chris Peterson]

Package: libcgi-application-plugin-authentication-perl
Version: 0.24+~cs0.5-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: chris.peter...@canonical.com
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oracular ubuntu-patch




libcgi-application-plugin-authentication-perl's build time tests fail
due to a change in behavior in libcgi-pm-perl with trailing slashes in
URLs. In particular, a test was failing which compared generated output
with a reference output that was generated with an older version of
libcgi-pm-perl. I applied the attached patch to fix the issue Ubuntu and
also forwarded it upstream.

Thanks for considering the patch.

- cpete
diff -Nru 
libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch
 
libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch
--- 
libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch
  1969-12-31 16:00:00.0 -0800
+++ 
libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch
  2024-06-27 16:02:21.0 -0700
@@ -0,0 +1,23 @@
+Description: Update test for CGI.pm >=4.66
+  CGI.pm made changes to "restore the trailing slash in ->url" in 4.66[1],
+  which causes a test failure in one of the tests comparing output with
+  a reference generated by a previous version of CGI.pm. This patch
+  updates the reference file for compatibility with CGI.pm >= 4.66.
+
+  [1] 
https://github.com/leejo/CGI.pm/commit/a5485b5f3b2b1cc85761b6781ff6660b4f377498
+Author: Chris Peterson 
+Forwarded: 
https://github.com/MicroTechnology-Services/cgi-application-plugin-authentication/pull/2
+Bug-Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/libcgi-application-plugin-authentication-perl/+bug/2071369
+Last-Update: 2024-06-27
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/t/out/basic_login_box
 b/t/out/basic_login_box
+@@ -28,6 +28,6 @@
+   
+ 
+   
+-  http://localhost; />
++  http://localhost/; />
+   
+ 
diff -Nru 
libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series 
libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series
--- 
libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series 
1969-12-31 16:00:00.0 -0800
+++ 
libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series 
2024-06-27 11:32:51.0 -0700
@@ -0,0 +1 @@
+login-box-basic.patch

Bug#1074175: netkit-rwho: remove for trixie?

[Chris Hofstaedtler]

Source: netkit-rwho
Version: 0.17-15
Severity: serious

rwho(d) is a design from a different time, when networks were
trusted, and so on. It seems to me, we should and could stop
shipping it for trixie.

I'm raising this bug now, to:
1) establish awareness
2) auto-rm it from trixie
3) give people time to chime in / secure replacements to show up

After a while I intend to clone this bug to ftp.debian.org for
removal from unstable.

Chris

Bug#1074086: kexec-tools: diff for NMU version 1:2.0.27-1.3

[Chris Hofstaedtler]

On Sun, Jun 23, 2024 at 12:56:13PM +0200, Chris Hofstaedtler wrote:
> I've prepared an NMU for kexec-tools (versioned as 1:2.0.27-1.3) and
> uploaded it to DELAYED/5.

Given I'm fixing my own NMU, I've rescheduled to immediate per
another DD's advice.

Sorry if that's surprising.

Chris

Bug#1074086: kexec-tools: diff for NMU version 1:2.0.27-1.3

[Chris Hofstaedtler]

Control: tags 1074086 + patch
Control: tags 1074086 + pending


Dear maintainer,

I've prepared an NMU for kexec-tools (versioned as 1:2.0.27-1.3) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru kexec-tools-2.0.27/debian/changelog kexec-tools-2.0.27/debian/changelog
--- kexec-tools-2.0.27/debian/changelog	2024-06-12 00:36:59.0 +0200
+++ kexec-tools-2.0.27/debian/changelog	2024-06-23 12:26:20.0 +0200
@@ -1,3 +1,11 @@
+kexec-tools (1:2.0.27-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Conflict with DEP17-unmitigated versions of molly-guard, bfh-container,
+progress-linux-container. (Closes: #1074086)
+
+ -- Chris Hofstaedtler   Sun, 23 Jun 2024 12:26:20 +0200
+
 kexec-tools (1:2.0.27-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru kexec-tools-2.0.27/debian/control kexec-tools-2.0.27/debian/control
--- kexec-tools-2.0.27/debian/control	2023-10-04 23:20:54.0 +0200
+++ kexec-tools-2.0.27/debian/control	2024-06-23 12:26:20.0 +0200
@@ -10,6 +10,7 @@
 Package: kexec-tools
 Architecture: linux-any
 Depends: ${shlibs:Depends}, ${misc:Depends}, debconf, dpkg (>= 1.15.7.2)
+Conflicts: molly-guard (<< 0.8.4~), bfh-container (<< 20211009-22~), progress-linux-container (<< 20221002-11~)
 Description: tools to support fast kexec reboots
  This package provides tools to load a kernel into memory and then
  "reboot" directly into that kernel using the kexec system call,

Bug#1074111: [arm64] boot stops at 'Starting kernel ...' without any further output when kernel built with recent binutils

[Chris Hofstaedtler]

Control: clone -1 -2
Control: reassign -2 src:binutils
Control: found -2 binutils/2.42.50.20240618-1

I'm cloning this to src:binutils as the problem is likely either
there or in gcc; as Johannes stated below, the newer gcc requires
the new binutils. If it's gcc, please reassign there.

CC-ed debian-arm@ to also reach the ARM64 porters.

On Sun, Jun 23, 2024 at 11:44:05AM +0200, Johannes Schauer Marin Rodrigues 
wrote:
> [..] Compiling the
> same kernel version 6.8.12 in *unstable* within a more recent build 
> environment
> results in a vmlinuz that just prints on boot:
> 
> Starting kernel ...
> 
> And then nothing else. Since neither the linux sources in debian unstable
> changed, nor our patch stack changed between these rebuilds, the culprit is
> likely in the build environment. [..]
> [..] We also observed how the good vmlinuz has a size of 31M and
> the bad vmlinuz a size of only 26M.
> This is with the same sources, just different build chroot environment. An
> old-enough build environment can be constructed using snapshot.d.o.

> One of the differences in the build environment between good and bad builds is
> binutils-arm-linux-gnueabihf with version 2.42-4 in the good environment and
> version 2.42.50.20240618-1 in the bad environment. To test whether this indeed
> triggers the problem, we tested building our kernel with current unstable but
> with binutils (= 2.42-4) and gcc-13 (= 13.2.0-25). We also have to choose an
> older gcc from snapshot.d.o because recent gcc-13 requires recent binutils.
> This makes the kernel work again.

> So, given that the problem affects linux in unstable *if* built with a more
> recent build environment, the problem might not be in src:linux but elsewhere
> (maybe binutils or gcc-13). I'm still filing it here as I lack the skills to
> investigate this problem further. Since the issue shows up with qemu, I'm sure
> that you can get to the bottom of it and can re-assign this bug to the package
> to which it belongs.

I think this also means rebuilding an existing kernel in unstable
or testing will also break.

Chris

Bug#1074051: libpam-pgsql: remove from Debian?

[Chris Hofstaedtler]

Package: libpam-pgsql
Version: 0.7.3.2-1+b1
Severity: serious

pam-pgsql's last upload was in 2014. This was a maintainer upload. 
There are currently open release-critical bugs, preventing pam-pgsql
from being released with Debian, since 2017 - 6+ years already.

PAM modules should IMO be held to high standards of being up to date
and maintained.

I propose removing pam-pgsql from Debian, as it seems to be effectively
unmaintained for a very long time already and it looks like interest has
vanished over time.

I propose reassigning this bug to ftp.debian.org on or after July 9th.

Chris

Bug#1071058: mumble-server: prompting due to modified conffiles which were not modified by the user: /etc/mumble/mumble-server.ini

[Chris Knadle]

Hopefully this bug will be fixed with the addition of the following file

==

debian/mumble-server.maintscript:

mv_conffile /etc/mumble-server.ini /etc/mumble/mumble-server.ini 1.5.517-1~

==

Thanks

On 5/13/24 12:19, Andreas Beckmann wrote:

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.


--
Chris Knadle
chris.kna...@coredump.us

Bug#1071058: mumble-server: prompting due to modified conffiles which were not modified by the user: /etc/mumble/mumble-server.ini

[Chris Knadle]

Upstream has changed the location for the mumble-server.ini file from 
/etc/ to /etc/mumble/ which I'm assuming is why this is happening. 
Somehow the logic the package install is currently configured for 
probably misses this case, and I'll need to figure out how to handle it.


I also missed this email for a couple of weeks -- I just realized that I 
might be able to create a Sieve rule to catch mumble bugs sent to the 
mailing list and copy them to my Debian-Bugs folder so that I'll be able 
to catch them quicker.


Thank you for the links to the policy and hints on how this bug might be 
addressed. https://wiki.debian.org/DpkgConffileHandling in particular 
discusses moving a conffile which is what I think I need.


  -- Chris

--
Chris Knadle
chris.kna...@coredump.us

On 5/13/24 12:19, Andreas Beckmann wrote:

Package: mumble-server
Version: 1.5.517-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

 From the attached log (scroll to the bottom...):

   Setting up mumble-server (1.5.517-2) ...
   
   Configuration file '/etc/mumble/mumble-server.ini'

==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
  What would you like to do about it ?  Your options are:
   Y or I  : install the package maintainer's version
   N or O  : keep your currently-installed version
 D : show the differences between the versions
 Z : start a shell to examine the situation
The default action is to keep your current version.
   *** mumble-server.ini (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package mumble-server (--configure):
end of file on stdin at conffile prompt


cheers,

Andreas

Bug#1073831: xfsprogs: diff for NMU version 6.8.0-2.2

[Chris Hofstaedtler]

Control: tags 1073831 + patch
Control: tags 1073831 + pending
Control: affects -1 + src:partclone

I'm sorry about this oversight.

Attached is an NMU patch; I'll upload to DELAYED/5.
I've also sent a new patch version towards upstream.

Chris

diff -Nru xfsprogs-6.8.0/debian/changelog xfsprogs-6.8.0/debian/changelog
--- xfsprogs-6.8.0/debian/changelog	2024-06-12 17:50:50.0 +0200
+++ xfsprogs-6.8.0/debian/changelog	2024-06-19 23:33:58.0 +0200
@@ -1,3 +1,10 @@
+xfsprogs (6.8.0-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix installation of files into xfslibs-dev (Closes: #1073831)
+
+ -- Chris Hofstaedtler   Wed, 19 Jun 2024 23:33:58 +0200
+
 xfsprogs (6.8.0-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru xfsprogs-6.8.0/debian/rules xfsprogs-6.8.0/debian/rules
--- xfsprogs-6.8.0/debian/rules	2024-05-12 19:03:34.0 +0200
+++ xfsprogs-6.8.0/debian/rules	2024-06-19 23:33:58.0 +0200
@@ -103,9 +103,8 @@
 	$(pkgdev) $(MAKE) -C . install-dev
 	$(pkgdi)  $(MAKE) -C debian install-d-i
 	install -D -m 0755 debian/local/initramfs.hook debian/xfsprogs/usr/share/initramfs-tools/hooks/xfs
-	rm -f debian/xfslibs-dev/lib/$(DEB_HOST_MULTIARCH)/libhandle.la
-	rm -f debian/xfslibs-dev/lib/$(DEB_HOST_MULTIARCH)/libhandle.a
-	rm -fr debian/xfslibs-dev/usr/lib
+	rm -f debian/xfslibs-dev/usr/lib/$(DEB_HOST_MULTIARCH)/libhandle.la
+	rm -f debian/xfslibs-dev/usr/lib/$(DEB_HOST_MULTIARCH)/libhandle.a
 	dh_installdocs -XCHANGES
 	dh_installchangelogs
 	dh_strip

Bug#1073831: xfsdump:FATAL ERROR: could not find a current XFS handle library

[Chris Hofstaedtler]

Control: reassign -1 xfslibs-dev
Control: found -1 xfslibs-dev/6.8.0-2.1
Control: affects -1 src:xfsdump

On Wed, Jun 19, 2024 at 07:28:59PM +0800, Bo YU wrote:
> FATAL ERROR: could not find a current XFS handle library.
> Install or upgrade the XFS library package.

As pointed out by Aurelien Jarno, I broke xfsprogs' devel so
symlink.

Bug#1073516: tree-style-tab: remove?

[Chris Hofstaedtler]

Source: tree-style-tab
Version: 3.5.20-1
Severity: serious
Tags: sid trixie

tree-style-tab wasn't updated since 2020, currently build-depends on
mozilla-devscripts (to be removed), and doesn't build because
python3-librdf disappeared (#1071896).

#993548 also suggests it does not work with current Firefox
releases.

Is it time to remove tree-style-tab then?

If nobody speak up and deals with the open problems, I'll reassign
this bug to ftp.debian.org for removal in about a month or so.

Best,
Chris

Bug#1072952: krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity

[Chris Hofstaedtler]

* Sam Hartman  [240614 22:52]:
> >>>>> "Chris" == Chris Hofstaedtler  writes:
> 
> Chris> When building krb5 with sbuild, configured to use the unshare
> Chris> backend, the t_iprop.py test apparently times out without any
> Chris> output.
> 
> I'm guessing, but have not confirmed that sbuild unshare is setting up a
> network namespace with nothing but lo in it.

Yeah. For details, you can check:
https://sources.debian.org/src/sbuild/0.85.10/lib/Sbuild/ChrootUnshare.pm/#L320

> I've certainly seen the same behavior you see in such a configuration.
> What's happening is that get_wildcard_address in kpropd.c passes
> AI_ADDRCONFIG into getaddrinfo.  Since loopback addresses are ignored by
> AI_ADDRCONFIG, there is no valid v4 or v6 address and  the routine fails
> to find a wildcard address to bind to.
> 
> I'm mistified why the daemon doesn't just fail at thait point, but I
> have not looked into that.

Having it stuck there is certainly annoying.

> I did modify get_wildcard_address to prefer AI_ADDRCONFIG but to fall
> back to calling getaddrinfo without AI_ADDRCONFIG if that's all that
> will work.
> 
> That's enough for t_kpropd.py to succeed.
> I'm working through a few other FTBFS issues in a container, some of
> which apparently didn't show up for sbuild unshare (they happen earlier
> in the build) but which are getting in my way.
> I hope to have 1.21.2 uploaded and building by end of weekend.

Great. Thanks for your work!

Chris

Bug#1071681: Need rebuild with newer pkg-php-tools

[Chris Hofstaedtler]

php-ml-iri and php-mockery will need a rebuild with 
pkg-php-tools >= 1.45+nmu2 once that has landed.

As they are both Architecture: all, they will need a sourceful
(NM)Upload. At that point, bumping the pkg-php-tools would also be
good.

Bug#1073114: unburden-home-dir: stop build-depending on pcre3

[Chris Hofstaedtler]

Source: unburden-home-dir
Severity: serious
Tags: trixie sid

Hi,

we want to get rid of pcre3 in trixie. As such unburden-home-dir's
Build-Depends on pcregrep dependency will become unsatisfiable.

Chris

Bug#1073108: tools-nrepl-clojure: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: tools-nrepl-clojure
Version: 0.2.13-2
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073110: vsearch: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: vsearch
Version: 2.28.1-1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073109: vowpal-wabbit: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: vowpal-wabbit
Version: 8.6.1.dfsg1-1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073107: tools-namespace-clojure: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: tools-namespace-clojure
Version: 0.2.11-1.1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073106: swarm-cluster: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: swarm-cluster
Version: 3.1.5+dfsg-1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073105: ssake: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: ssake
Version: 4.0.1-1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073104: srst2: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: srst2
Version: 0.2.0-11
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073103: scythe: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: scythe
Version: 0.994+git20141017.20d3cff-4
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073102: rtpengine: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: rtpengine
Version: 11.5.1.24-1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073101: math-numeric-tower-clojure: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: math-numeric-tower-clojure
Version: 0.0.4-1.1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073100: math-combinatorics-clojure: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: math-combinatorics-clojure
Version: 0.1.4-1.1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073099: markdown-mode: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: markdown-mode
Version: 2.6-1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073098: libvcflib: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: libvcflib
Version: 1.0.9+dfsg1-3
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073097: lazymap-clojure: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: lazymap-clojure
Version: 3.1.1-2
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073096: keras: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: keras
Version: 2.3.1+dfsg2-1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073095: hilive: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: hilive
Version: 2.0a-3
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073094: gtk3-nocsd: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: gtk3-nocsd
Version: 3-1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073093: glogg: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: glogg
Version: 1.1.4-1.2
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073092: erlang-cowlib: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: erlang-cowlib
Version: 1.3.0-3
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073091: belenios: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: belenios
Version: 2.2+git10-gbb6b7ea8+dfsg-1
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073090: alter-sequence-alignment: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: alter-sequence-alignment
Version: 1.3.4-7
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073089: adapterremoval: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: adapterremoval
Version: 2.3.3-2
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1073088: abinit: replace to-be-removed markdown build-dependency

[Chris Hofstaedtler]

Source: abinit
Version: 9.10.4-3
Severity: serious
Control: block 1072958 by -1

Your package build-depends on markdown. Per bug #1063645, markdown is not
maintained upstream or in Debian and should be removed.
Drop-in alternatives, for examples the suggested `discount` or
`python3-markdown` or `libtext-markdown-perl`.

`discount` and `libtext-markdown-perl` provide a `markdown` program if your
package needs that.

Bug#1065385: btrfs-progs: diff for NMU version 6.6.3-1.2

[Chris Hofstaedtler]

Control: tags -1 + patch pending


Dear maintainer,

I've prepared an NMU for btrfs-progs (versioned as 6.6.3-1.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru btrfs-progs-6.6.3/debian/btrfs-progs.install btrfs-progs-6.6.3/debian/btrfs-progs.install
--- btrfs-progs-6.6.3/debian/btrfs-progs.install	2023-12-29 17:48:37.0 +0100
+++ btrfs-progs-6.6.3/debian/btrfs-progs.install	2024-06-12 21:22:17.0 +0200
@@ -1,3 +1,3 @@
-bin/
-sbin/
+usr/bin/
+usr/sbin/
 usr/share/
diff -Nru btrfs-progs-6.6.3/debian/changelog btrfs-progs-6.6.3/debian/changelog
--- btrfs-progs-6.6.3/debian/changelog	2024-02-28 06:21:59.0 +0100
+++ btrfs-progs-6.6.3/debian/changelog	2024-06-12 21:22:17.0 +0200
@@ -1,3 +1,15 @@
+btrfs-progs (6.6.3-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch Build-Depends from udev to systemd-dev (Closes: #1065385)
+  * Install files into UsrMerged layout (DEP17 M2) (Closes: #1073073)
+
+  [ Peter Michael Green ]
+  * Change inode_includes to ext2fs_inode_includes (Closes: #1071297)
+  * Bump dependency on libext2fs-dev.
+
+ -- Chris Hofstaedtler   Wed, 12 Jun 2024 21:22:17 +0200
+
 btrfs-progs (6.6.3-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru btrfs-progs-6.6.3/debian/control btrfs-progs-6.6.3/debian/control
--- btrfs-progs-6.6.3/debian/control	2024-02-28 06:21:59.0 +0100
+++ btrfs-progs-6.6.3/debian/control	2024-06-12 21:22:17.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Adam Borowski 
 Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13),
-   libext2fs-dev,
+   libext2fs-dev (>= 1.47.1),
pkg-config,
libacl1-dev,
libblkid-dev,
@@ -12,7 +12,7 @@
libudev-dev,
libzstd-dev,
uuid-dev,
-   udev,
+   systemd-dev,
zlib1g-dev,
sphinx,
python3-sphinx-rtd-theme,
diff -Nru btrfs-progs-6.6.3/debian/patches/debian-changes btrfs-progs-6.6.3/debian/patches/debian-changes
--- btrfs-progs-6.6.3/debian/patches/debian-changes	1970-01-01 01:00:00.0 +0100
+++ btrfs-progs-6.6.3/debian/patches/debian-changes	2024-06-12 21:22:17.0 +0200
@@ -0,0 +1,27 @@
+Description: Autogenerated patch header for a single-debian-patch file.
+ The delta against upstream is either kept as a single patch, or maintained
+ in some VCS, and exported as a single patch instead of more manageable
+ atomic patches.
+Forwarded: not-needed
+
+---
+--- btrfs-progs-6.6.3.orig/convert/source-ext2.c
 btrfs-progs-6.6.3/convert/source-ext2.c
+@@ -730,7 +730,7 @@ static inline void ext4_decode_extra_tim
+ #define EXT4_COPY_XTIME(xtime, dst, tv_sec, tv_nsec)	\
+ do {			\
+ 	tv_sec = src->i_ ## xtime ;			\
+-	if (inode_includes(inode_size, i_ ## xtime ## _extra)) {			\
++	if (ext2fs_inode_includes(inode_size, i_ ## xtime ## _extra)) {			\
+ 		tv_sec = src->i_ ## xtime ;		\
+ 		ext4_decode_extra_time(_sec, _nsec, src->i_ ## xtime ## _extra);	\
+ 		btrfs_set_stack_timespec_sec(>xtime , tv_sec);			\
+@@ -771,7 +771,7 @@ static int ext4_copy_inode_timespec_extr
+ 	EXT4_COPY_XTIME(ctime, dst, tv_sec, tv_nsec);
+ 
+ 	tv_sec = src->i_crtime;
+-	if (inode_includes(inode_size, i_crtime_extra)) {
++	if (ext2fs_inode_includes(inode_size, i_crtime_extra)) {
+ 		tv_sec = src->i_crtime;
+ 		ext4_decode_extra_time(_sec, _nsec, src->i_crtime_extra);
+ 		btrfs_set_stack_timespec_sec(>otime, tv_sec);
diff -Nru btrfs-progs-6.6.3/debian/patches/series btrfs-progs-6.6.3/debian/patches/series
--- btrfs-progs-6.6.3/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ btrfs-progs-6.6.3/debian/patches/series	2024-06-12 21:22:16.0 +0200
@@ -0,0 +1 @@
+debian-changes
diff -Nru btrfs-progs-6.6.3/debian/rules btrfs-progs-6.6.3/debian/rules
--- btrfs-progs-6.6.3/debian/rules	2023-12-29 18:00:59.0 +0100
+++ btrfs-progs-6.6.3/debian/rules	2024-06-12 21:22:17.0 +0200
@@ -14,7 +14,7 @@
 	dh_autoreconf ./autogen.sh
 
 override_dh_auto_configure:
-	dh_auto_configure -- --bindir=/bin
+	dh_auto_configure
 
 override_dh_auto_build:
 	dh_auto_build -- V=1
@@ -23,9 +23,9 @@
 	dh_auto_install -- install
 	cd libbtrfsutil/python; \
 		python3 setup.py install --install-layout=deb --skip-build --root ../../debian/tmp --prefix /usr
-	mkdir -p debian/tmp/sbin
-	mv debian/tmp/bin/fsck.btrfs debian/tmp/sbin/fsck.btrfs
-	mv debian/tmp/bin/mkfs.btrfs debian/tmp/sbin/mkfs.btrfs
+	mkdir -p debian/tmp/usr/sbin
+	mv debian/tmp/usr/bin/fsck.btrfs debian/tmp/usr/sbin/fsck.btrfs
+	mv debian/tmp/usr/bin/mkfs.btrfs debian/tmp/usr/sbin/mkfs.btrfs
 
 	# Adding initramfs-tools integration
 	install -D -m 0755 debian/local/btrfs.hook debian/btrfs-progs/usr/share/initramfs-tools/hooks/btrfs

Bug#1066632: djbdns: diff for NMU version 1:1.05-15.1

[Chris Hofstaedtler]

Package: djbdns
Version: 1:1.05-15
Severity: normal
Tags: patch  pending


Dear maintainer,

I've prepared an NMU for djbdns (versioned as 1:1.05-15.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru djbdns-1.05/debian/axfrdns.sysuser djbdns-1.05/debian/axfrdns.sysuser
--- djbdns-1.05/debian/axfrdns.sysuser	2021-11-15 01:21:04.0 +0100
+++ djbdns-1.05/debian/axfrdns.sysuser	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-axfrdns defaults
diff -Nru djbdns-1.05/debian/axfrdns.sysusers djbdns-1.05/debian/axfrdns.sysusers
--- djbdns-1.05/debian/axfrdns.sysusers	1970-01-01 01:00:00.0 +0100
+++ djbdns-1.05/debian/axfrdns.sysusers	2024-06-12 21:17:35.0 +0200
@@ -0,0 +1 @@
+u axfrdns	-	-	/nonexistent
diff -Nru djbdns-1.05/debian/changelog djbdns-1.05/debian/changelog
--- djbdns-1.05/debian/changelog	2021-11-15 01:21:04.0 +0100
+++ djbdns-1.05/debian/changelog	2024-06-12 21:17:37.0 +0200
@@ -1,3 +1,13 @@
+djbdns (1:1.05-15.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Move from dh-sysuser to standard dh_installsysusers (Closes: #1071526)
+  * Fix FTBFS. (Closes: #1066632)
+
+ -- Chris Hofstaedtler   Wed, 12 Jun 2024 21:17:37 +0200
+
 djbdns (1:1.05-15) unstable; urgency=medium
 
   * Fix the setgid directory FTBFS on kFreeBSD: let the test tool
diff -Nru djbdns-1.05/debian/control djbdns-1.05/debian/control
--- djbdns-1.05/debian/control	2021-11-15 01:21:04.0 +0100
+++ djbdns-1.05/debian/control	2024-06-12 21:17:35.0 +0200
@@ -6,7 +6,7 @@
  po-debconf,
  debhelper-compat (= 13),
  dh-runit (>= 2.8.13),
- dh-sysuser,
+ dh-sequence-installsysusers,
  ionit,
  python3 ,
  timelimit ,
diff -Nru djbdns-1.05/debian/dnscache.sysuser djbdns-1.05/debian/dnscache.sysuser
--- djbdns-1.05/debian/dnscache.sysuser	2021-11-15 01:21:04.0 +0100
+++ djbdns-1.05/debian/dnscache.sysuser	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-dnscache defaults
diff -Nru djbdns-1.05/debian/dnscache.sysusers djbdns-1.05/debian/dnscache.sysusers
--- djbdns-1.05/debian/dnscache.sysusers	1970-01-01 01:00:00.0 +0100
+++ djbdns-1.05/debian/dnscache.sysusers	2024-06-12 21:17:35.0 +0200
@@ -0,0 +1 @@
+u dnscache	-	-	/nonexistent
diff -Nru djbdns-1.05/debian/patches/ftbfs-implicit-declaration.patch djbdns-1.05/debian/patches/ftbfs-implicit-declaration.patch
--- djbdns-1.05/debian/patches/ftbfs-implicit-declaration.patch	1970-01-01 01:00:00.0 +0100
+++ djbdns-1.05/debian/patches/ftbfs-implicit-declaration.patch	2024-06-12 21:17:35.0 +0200
@@ -0,0 +1,82 @@
+Bug-Debian: https://bugs.debian.org/1066632
+--- djbdns-1.05.orig/seek_set.c
 djbdns-1.05/seek_set.c
+@@ -1,4 +1,5 @@
+ #include 
++#include 
+ #include "seek.h"
+ 
+ #define SET 0 /* sigh */
+--- djbdns-1.05.orig/chkshsgr.c
 djbdns-1.05/chkshsgr.c
+@@ -1,3 +1,5 @@
++#include 
++#include 
+ #include "exit.h"
+ 
+ int main()
+--- djbdns-1.05.orig/hier.c
 djbdns-1.05/hier.c
+@@ -1,5 +1,9 @@
+ #include "auto_home.h"
+ 
++void h(const char *home, int uid, int gid, int mode);
++void d(char *home, char *subdir, int uid, int gid, int mode);
++void c(const char *home, const char *subdir, char *file, int uid, int gid, int mode);
++
+ void hier()
+ {
+ /*
+--- djbdns-1.05.orig/install.c
 djbdns-1.05/install.c
+@@ -14,7 +14,7 @@
+ int fdsourcedir = -1;
+ 
+ void h(home,uid,gid,mode)
+-char *home;
++const char *home;
+ int uid;
+ int gid;
+ int mode;
+@@ -52,8 +52,8 @@
+ buffer ssout;
+ 
+ void c(home,subdir,file,uid,gid,mode)
+-char *home;
+-char *subdir;
++const char *home;
++const char *subdir;
+ char *file;
+ int uid;
+ int gid;
+--- djbdns-1.05.orig/utime.c
 djbdns-1.05/utime.c
+@@ -1,5 +1,6 @@
+ #include 
+ #include 
++#include 
+ #include "scan.h"
+ #include "exit.h"
+ 
+--- djbdns-1.05.orig/dnsq.c
 djbdns-1.05/dnsq.c
+@@ -1,3 +1,4 @@
++#include 
+ #include "uint16.h"
+ #include "strerr.h"
+ #include "buffer.h"
+--- djbdns-1.05.orig/dnsqr.c
 djbdns-1.05/dnsqr.c
+@@ -1,3 +1,4 @@
++#include 
+ #include "uint16.h"
+ #include "strerr.h"
+ #include "buffer.h"
+--- djbdns-1.05.orig/prot.c
 djbdns-1.05/prot.c
+@@ -1,3 +1,5 @@
++#include 
++#include 
+ #include "hasshsgr.h"
+ #include "prot.h"
+ 
diff -Nru djbdns-1.05/debian/patches/series djbdns-1.05/debian/patches/series
--- djbdns-1.05/debian/patches/series	2021-11-15 01:21:04.0 +0100
+++ djbdns-1.05/debian/patches/series	2024-06-12 21:17:35.0 +0200
@@ -9,3 +9,4 @@
 0009-usr-sbin.patch
 0010-dnsroots.global.patch
 0011-datalimit.patch
+ftbfs-implicit-declaration.patch
diff -Nru djbdns-1.05/debian/rbldns.sysuser djbdns-1.05/debian/rbldns.sysuser
--- djbdns-1.05/debian/rbldns.sysuser	2021-11-15 01:21:04.0 +0100
+++ djbdns-1.05/debian/rbldns.sysuser	1970-01-01 01:00:00.0

Bug#1072963: jpeg-xl: Failing autopkgtests on non-amd64

[Chris Hofstaedtler]

On Tue, Jun 11, 2024 at 01:04:06PM +0200, Julian Wollrath wrote:
> > > Specifically, the problem is that debian/libjxl-gdk-pixbuf.postinst
> > > and debian/libjxl-gdk-pixbuf.postrm have hardcoded the amd64
> > > architecture which means that libjxl-gdk-pixbuf is uninstallable on
> > > architectures other than amd64.
> > 
> > Could you comment on the above ?
> 
> hmm, in principle that utility should be called, to make gdk-pixbuf
> aware of the jpeg-xl loader. Maybe a workaround would be to have
> $ cat libjxl-gdk-pixbuf.postinst
> #!/bin/sh -e
> for X in /usr/lib/*/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
> do
>   if [ -x ${X} ]; then
>   ${X} --update-cache
[..]
 
> instead? And for libjxl-gdk-pixbuf.postrm this should also work. Or is
> there a better way, to get the library triplet for the architecture of
> the packet, that is being installed?

https://manpages.debian.org/bookworm/debhelper/dh_installdeb.1.en.html#SUBSTITUTION_IN_MAINTAINER_SCRIPTS
documents which tokens are available at build time to generate the
maintscripts.

I've CCed smcv@, as I think there is a better way than running a
postinst script in each individual package (triggers?). Maybe smcv
can chime in here.

Chris

Bug#1060985: prewikka: diff for NMU version 5.2.0-2.1

[Chris Hofstaedtler]

Control: tags 1060985 + pending


Dear maintainer,

I've prepared an NMU for prewikka (versioned as 5.2.0-2.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru prewikka-5.2.0/debian/changelog prewikka-5.2.0/debian/changelog
--- prewikka-5.2.0/debian/changelog	2021-08-25 20:53:39.0 +0200
+++ prewikka-5.2.0/debian/changelog	2024-06-11 09:24:23.0 +0200
@@ -1,3 +1,13 @@
+prewikka (5.2.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install programs into /usr/bin instead of /bin (DEP17 M2)
+
+  [ Hans Joachim Desserud ]
+  * Build-Depend on python3-six to fix FTBFS (Closes: #1060985)
+
+ -- Chris Hofstaedtler   Tue, 11 Jun 2024 09:24:23 +0200
+
 prewikka (5.2.0-2) unstable; urgency=medium
 
   * d.patches:
diff -Nru prewikka-5.2.0/debian/control prewikka-5.2.0/debian/control
--- prewikka-5.2.0/debian/control	2021-08-25 20:53:39.0 +0200
+++ prewikka-5.2.0/debian/control	2024-06-11 09:22:23.0 +0200
@@ -10,6 +10,7 @@
 python3-setuptools,
 python3-babel,
 python3-lesscpy,
+python3-six,
 gettext,
 Standards-Version: 4.6.0
 Homepage: https://www.prelude-siem.org/
diff -Nru prewikka-5.2.0/debian/rules prewikka-5.2.0/debian/rules
--- prewikka-5.2.0/debian/rules	2020-11-09 11:33:17.0 +0100
+++ prewikka-5.2.0/debian/rules	2024-06-11 09:24:18.0 +0200
@@ -10,6 +10,8 @@
 
 override_dh_install:
 	dh_install
+	mkdir -pv $(CURDIR)/debian/prewikka/usr
+	mv $(CURDIR)/debian/prewikka/bin $(CURDIR)/debian/prewikka/usr/
 	mkdir -pv $(CURDIR)/debian/prewikka/usr/share/prewikka/
 	mv -v $(CURDIR)/debian/prewikka/etc/prewikka/prewikka.conf $(CURDIR)/debian/prewikka/usr/share/prewikka/
 	rm -rvf $(CURDIR)/debian/prewikka/usr/lib/python*/dist-packages/prewikka/htdocs/fonts

Bug#1071295: apt-cacher-ng: diff for NMU version 3.7.4-1.1

[Chris Hofstaedtler]

Control: tags -1 + patch pending

Dear maintainer,

I've prepared an NMU for apt-cacher-ng (versioned as 3.7.4-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru apt-cacher-ng-3.7.4/debian/changelog apt-cacher-ng-3.7.4/debian/changelog
--- apt-cacher-ng-3.7.4/debian/changelog	2021-12-07 14:50:20.0 +0100
+++ apt-cacher-ng-3.7.4/debian/changelog	2024-06-11 00:41:08.0 +0200
@@ -1,3 +1,11 @@
+apt-cacher-ng (3.7.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Simplify !defined(HAVE_STRLCPY) check to fix FTBFS (Closes: #1071295)
+  * Avoid installing empty /lib/systemd/system directory (Closes: #1059190)
+
+ -- Chris Hofstaedtler   Tue, 11 Jun 2024 00:41:08 +0200
+
 apt-cacher-ng (3.7.4-1) unstable; urgency=medium
 
   * New upstream version
@@ -514,7 +522,7 @@
 
 apt-cacher-ng (0.8.0~rc3-1) unstable; urgency=low
 
-  * New upstream version, first Sid upload of 0.8.x 
+  * New upstream version, first Sid upload of 0.8.x
 + systemd related changes: startup notification, restart on crashes
   (closes: #752255)
 + Now really fixes lookup of .default files in the resource directory
@@ -617,7 +625,7 @@
   * Review of maintainer scripts, now responsive to modification of
 CacheDir in existing configuration file(s)
   * Defensive behavior of Debconf integration (closes: #732606) and including
-NEWS.Debian to explain the extended config handling 
+NEWS.Debian to explain the extended config handling
   * added libssl-dev to build dependencies (now really closes: #729508)
   * fixing build failure on architectures where ancgfs is not built (i.e. Hurd)
   * Debconf description improvement in better German translation
@@ -630,7 +638,7 @@
 + fixes reading of certain .xz files (closes: #729941, #731804)
 + HTTPS support (closes: #729508)
   * more debconf controlled settings injected through a separate config
-file, partially based on the patch from 
+file, partially based on the patch from
 Geert Stappers  (closes: #726656)
   * policy version bump, and no longer recommending perl, there are enough
 functionality replacements implemented to work with just perl-base
@@ -812,7 +820,7 @@
 
 apt-cacher-ng (0.7.4-1) unstable; urgency=medium
 
-  * New upstream release 
+  * New upstream release
 + prevents endless looping in certain situations (LP: #15)
 + more tolerance to unstable connections and behavior fix for conflicting
   downloads in maintenance mode (closes: #672801)
@@ -1113,7 +1121,7 @@
 
 apt-cacher-ng (0.4.9-2) unstable; urgency=low
 
-  * Minor change to support Ubuntu release notes delivery with GET 
+  * Minor change to support Ubuntu release notes delivery with GET
 parameters (closes: #588662)
 
  -- Eduard Bloch   Sun, 11 Jul 2010 11:06:49 +0200
@@ -1139,7 +1147,7 @@
 
 apt-cacher-ng (0.4.7-1) unstable; urgency=low
 
-  * New upstream version 
+  * New upstream version
 + supports fallback backends descriptions which are used when the file is
   specified in the config but not configured properly. Intended to help
   in a heterogeneous Debian/Ubuntu environment (closes Ubuntu tasks
@@ -1164,7 +1172,7 @@
 
   * New upstream release
 + documented DnsCacheSeconds (Ubuntu bug 530524)
-+ Added simple implementation of SOAP request forwarding for PTS 
++ Added simple implementation of SOAP request forwarding for PTS
   access (closes: #453277)
 + Typo fix in userinfo.html (closes: #572171)
 
@@ -1224,7 +1232,7 @@
 + passing HTTP redirection target through to user (closes: #556234)
   * Unconfuse crontab expiration script when BindAdress contains multiple
 entries (patch by Hellekin O\. Wolf, closes: #554707)
- 
+
  -- Eduard Bloch   Sun, 22 Nov 2009 19:06:32 +0100
 
 apt-cacher-ng (0.4-1) unstable; urgency=low
diff -Nru apt-cacher-ng-3.7.4/debian/patches/cmakedefines.patch apt-cacher-ng-3.7.4/debian/patches/cmakedefines.patch
--- apt-cacher-ng-3.7.4/debian/patches/cmakedefines.patch	1970-01-01 01:00:00.0 +0100
+++ apt-cacher-ng-3.7.4/debian/patches/cmakedefines.patch	2024-06-11 00:36:51.0 +0200
@@ -0,0 +1,26 @@
+Index: apt-cacher-ng-3.7.4/src/meta.h
+===
+--- apt-cacher-ng-3.7.4.orig/src/meta.h
 apt-cacher-ng-3.7.4/src/meta.h
+@@ -323,7 +323,7 @@ class NoCaseStringMap : public std::map<
+ static constexpr string_view svRN = szRN;
+ static constexpr string_view svLF = "\n";
+ 
+-#if !defined(HAVE_STRLCPY) || !HAVE_STRLCPY
++#if !defined(HAVE_STRLCPY)
+ size_t strlcpy(char *tgt, const char *src, size_t tgtSize);
+ #endif
+ }
+Index: apt-cacher-ng-3.7.4/src/meta.cc
+===
+--- apt-cacher-ng-3.7.4.orig/src/meta.cc
 apt-cacher-ng-3.7.4/src/meta.cc
+@@ -831,7 +831,7 @@ bool scaseequals(string_view a, string_v
+ return true;
+ }
+ 
+-#if !defined

Bug#1060474: pulseaudio: diff for NMU version 16.1+dfsg1-5.1

[Chris Hofstaedtler]

Control: tags -1 + patch pending


Dear maintainer,

I've prepared an NMU for pulseaudio (versioned as 16.1+dfsg1-5.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru pulseaudio-16.1+dfsg1/debian/changelog pulseaudio-16.1+dfsg1/debian/changelog
--- pulseaudio-16.1+dfsg1/debian/changelog	2024-04-03 14:06:33.0 +0200
+++ pulseaudio-16.1+dfsg1/debian/changelog	2024-06-10 23:50:35.0 +0200
@@ -1,3 +1,12 @@
+pulseaudio (16.1+dfsg1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch Build-Depends to systemd-dev, fixing FTBFS. (Closes: #1060474)
+  * Install systemd masking symlink and udev rule into /usr (DEP17).
+(Closes: #1072960)
+
+ -- Chris Hofstaedtler   Mon, 10 Jun 2024 23:50:35 +0200
+
 pulseaudio (16.1+dfsg1-5) unstable; urgency=medium
 
   * Team upload
diff -Nru pulseaudio-16.1+dfsg1/debian/control pulseaudio-16.1+dfsg1/debian/control
--- pulseaudio-16.1+dfsg1/debian/control	2024-04-03 14:06:33.0 +0200
+++ pulseaudio-16.1+dfsg1/debian/control	2024-06-10 23:50:35.0 +0200
@@ -41,7 +41,7 @@
 libxcb1-dev,
 libxml2-utils ,
 libxtst-dev,
-systemd [linux-any]
+systemd-dev [linux-any]
 Standards-Version: 4.6.2
 Rules-Requires-Root: no
 Vcs-Browser: https://salsa.debian.org/pulseaudio-team/pulseaudio
diff -Nru pulseaudio-16.1+dfsg1/debian/pulseaudio.install pulseaudio-16.1+dfsg1/debian/pulseaudio.install
--- pulseaudio-16.1+dfsg1/debian/pulseaudio.install	2024-04-03 14:06:33.0 +0200
+++ pulseaudio-16.1+dfsg1/debian/pulseaudio.install	2024-06-10 23:50:35.0 +0200
@@ -5,7 +5,7 @@
 etc/pulse/daemon.conf
 etc/xdg/autostart/pulseaudio.desktop
 etc/xdg/Xwayland-session.d/00-pulseaudio-x11
-[linux-any] lib/udev/rules.d/90-pulseaudio.rules
+[linux-any] usr/lib/udev/rules.d/90-pulseaudio.rules
 usr/bin/pulseaudio
 usr/bin/start-pulseaudio-x11
 usr/lib/*/pulseaudio/libpulsecore-*.so
diff -Nru pulseaudio-16.1+dfsg1/debian/pulseaudio.links pulseaudio-16.1+dfsg1/debian/pulseaudio.links
--- pulseaudio-16.1+dfsg1/debian/pulseaudio.links	2024-04-03 14:06:33.0 +0200
+++ pulseaudio-16.1+dfsg1/debian/pulseaudio.links	2024-06-10 23:50:34.0 +0200
@@ -2,6 +2,6 @@
 
 [linux-any] /usr/share/alsa/alsa.conf.d/pulse.conf /etc/alsa/conf.d/99-pulse.conf
 
-/dev/null /lib/systemd/system/pulseaudio-enable-autospawn.service
+/dev/null /usr/lib/systemd/system/pulseaudio-enable-autospawn.service
 /run/pulseaudio-enable-autospawn /etc/pulse/client.conf.d/01-enable-autospawn.conf
 
diff -Nru pulseaudio-16.1+dfsg1/debian/rules pulseaudio-16.1+dfsg1/debian/rules
--- pulseaudio-16.1+dfsg1/debian/rules	2024-04-03 14:06:33.0 +0200
+++ pulseaudio-16.1+dfsg1/debian/rules	2024-06-10 23:50:35.0 +0200
@@ -39,6 +39,7 @@
   -Dstream-restore-clear-old-devices=true \
   -Dzshcompletiondir=/usr/share/zsh/vendor-completions \
   -Dsystemduserunitdir=/usr/lib/systemd/user \
+  -Dudevrulesdir=/usr/lib/udev/rules.d \
   -Dmodlibexecdir=/usr/lib/pulse-$(DEB_VERSION_UPSTREAM)/modules \
   -Dpulsedsp-location=/usr/\\'$$'LIB/pulseaudio \
   -Dgtk=enabled \

Bug#1072952: krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity

[Chris Hofstaedtler]

* Sam Hartman  [240610 23:13]:
> control: tags -1 +help
> 
> 
> Chris> Filing with severity: serious as the buildd network has
> Chris> started switching to sbuild with unshare backend, and
> Chris> multiple people have reproduced this problem.
> 
> I'm not running sbuild these days; I'm mostly moving toward
> containerized builds for my local development.
> I am currently setting up a new environment and if I can reproduce
> there, I'm happy to  look into it.

> But if it literally happens only on sbuild unshare, I'm going to need
> help because that's not a beast I have a desire to deal with.

A reduced version of the sbuild wiki page [1], which should give you a
working sbuild+unshare on top of a normal, amd64 Debian stable
install (not a container - VM is fine):

$ sudo apt install mmdebstrap uidmap
$ sudo apt install -t stable-backports sbuild
$ mkdir -p ~/.cache/sbuild
$ mmdebstrap --variant=buildd unstable ~/.cache/sbuild/unstable-amd64.tar
$ cat << "EOF" > ~/.sbuildrc
$chroot_mode = 'unshare';
EOF

This assumes you have a recently enough installed Debian stable,
otherwise /etc/subuid and /etc/subgid also need setting up. Example
contents:

% cat /etc/subuid
chris:10:65536
% cat /etc/subgid
chris:10:65536

Might need to logout/login after this.

To build/repro the failure:

$ apt source krb5
$ sbuild -d unstable
(...wait...)

Hope this helps,
Chris

[1] 
https://wiki.debian.org/sbuild#Option_1:_Using_unshare_with_mmdebstrap_.28no_root_needed.29

Bug#1072952: krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity

[Chris Hofstaedtler]

Source: krb5
Version: 1.20.1-6
Severity: serious
Tags: ftbfs
X-Debbugs-CC: jspri...@debian.org

Filing with severity: serious as the buildd network has started
switching to sbuild with unshare backend, and multiple people have
reproduced this problem.

When building krb5 with sbuild, configured to use the unshare
backend, the t_iprop.py test apparently times out without any
output.

Last few lines:

| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_general.py
| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_hooks.py
| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_dump.py
| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_iprop.py
| E: Build killed with signal TERM after 60 minutes of inactivity

I'm attaching my own build log, running on arm64. Another build log
showing the same problem can be found here (ran on amd64):

https://people.debian.org/~sanvila/unshare/unstable-20240529/krb5_1.20.1-6_amd64-20240529T214515.396Z

My build log shows the result of an external SIGTERM instead of
sbuild killing it, but that's just a distracting detail.

I'll note this appears unrelated to #1063648.

Chris



krb5_1.20.1-6_arm64-killed.build.gz
Description: application/gzip

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

[Chris Hofstaedtler]

On Mon, Jun 10, 2024 at 11:59:34AM +0200, Chris Hofstaedtler wrote:
> Hi,
> 
> On Mon, Feb 12, 2024 at 08:43:07AM -0700, Sam Hartman wrote:
> > >>>>> "Simon" == Simon McVittie  writes:
[..]
> > Simon> However, even with both of those, if the krb5 test suite (or
> > Simon> protocol) is resolving the local hostname with AF_INET
> > Simon> (IPv4-only), and with either AI_ADDRCONFIG or NULL hints,
> > Simon> then that will not yield any results on an IPv6-only system
> > Simon> for the reasons discussed in #952740 and related bug reports.
> > 
> > Krb5 is very v6-happy.
> 
> It really seems like krb5 is not quite as ipv6-*only*-happy as one
> would like to think.

Adam (adsb) points out that the test code in
lib/rpc/unit-test/client.c [1] uses code that does not support
IPv6(-only). I.e. gethostbyname for a name that has no IPv4 address
will fail.

Please try fixing this before adding workarounds?

Chris

[1] 
https://sources.debian.org/src/krb5/1.20.1-6/src/lib/rpc/unit-test/client.c/#L127

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

[Chris Hofstaedtler]

Hi,

On Mon, Feb 12, 2024 at 08:43:07AM -0700, Sam Hartman wrote:
> >>>>> "Simon" == Simon McVittie  writes:
[..]
> Simon> I am unsure whether there is consensus that "the result of
> Simon> gethostname() resolves to some address of the local machine"
> Simon> is also a reasonable thing to demand from all buildds as part
> Simon> of build-essential: /etc/hosts typically makes this true, but
> Simon> is not *guaranteed* to do so. On Linux, packages can ensure
> Simon> that it happens by build-depending on libnss-myhostname
> Simon> [linux-any], if necessary.

I have asked on #debian-buildd, and got the answer that all buildds
have their own hostname in /etc/hosts. Thus this is not the source
of the problem.

> Simon> However, even with both of those, if the krb5 test suite (or
> Simon> protocol) is resolving the local hostname with AF_INET
> Simon> (IPv4-only), and with either AI_ADDRCONFIG or NULL hints,
> Simon> then that will not yield any results on an IPv6-only system
> Simon> for the reasons discussed in #952740 and related bug reports.
> 
> Krb5 is very v6-happy.

It really seems like krb5 is not quite as ipv6-*only*-happy as one
would like to think.

> So, you're suggesting that I fix this by build-depending on
> libnss-myhostname [linux-any] assuming tests are enabled?
> If so, that's easy.

That might or might not help to swipe the problem under a large
enough carpet.

I'll note that on buildds using sbuild with unshare backend, the
setup will look slightly differently. More testing might be
required.

Chris

Bug#1052282: mythtv-status: diff for NMU version 1.1.0-1.1

[Chris Hofstaedtler]

Control: tags 1052282 + patch
Control: tags 1052282 + pending


Dear maintainer,

I've prepared an NMU for mythtv-status (versioned as 1.1.0-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

The patch also moves the systemd units into /usr.

Regards.

diff -Nru mythtv-status-1.1.0/debian/changelog mythtv-status-1.1.0/debian/changelog
--- mythtv-status-1.1.0/debian/changelog	2023-07-22 14:16:49.0 +0200
+++ mythtv-status-1.1.0/debian/changelog	2024-06-10 11:26:48.0 +0200
@@ -1,3 +1,12 @@
+mythtv-status (1.1.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch makefile to stop running tests during dh_auto_build
+(Closes: #1052282)
+  * Patch makefile to install systemd units into /usr. (DEP17)
+
+ -- Chris Hofstaedtler   Mon, 10 Jun 2024 11:26:48 +0200
+
 mythtv-status (1.1.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru mythtv-status-1.1.0/debian/patches/makefile-man-path.patch mythtv-status-1.1.0/debian/patches/makefile-man-path.patch
--- mythtv-status-1.1.0/debian/patches/makefile-man-path.patch	2023-07-16 06:17:12.0 +0200
+++ mythtv-status-1.1.0/debian/patches/makefile-man-path.patch	1970-01-01 01:00:00.0 +0100
@@ -1,17 +0,0 @@
-Description: Install man pages to Debian location
-Author: Andrew Ruthven 
-Forwarded: not-needed
-Last-Update: 2023-07-16

-This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
 a/Makefile
-+++ b/Makefile
-@@ -2,7 +2,7 @@
- 
- BINDIR=$(DESTDIR)/usr/bin
- LIBEXECDIR=$(DESTDIR)/usr/libexec/mythtv-status
--MANDIR=$(DESTDIR)/usr/man
-+MANDIR=$(DESTDIR)/usr/share/man
- SYSTEMDDIR=$(DESTDIR)/lib/systemd/system
- 
- package=mythtv-status
diff -Nru mythtv-status-1.1.0/debian/patches/makefile.patch mythtv-status-1.1.0/debian/patches/makefile.patch
--- mythtv-status-1.1.0/debian/patches/makefile.patch	1970-01-01 01:00:00.0 +0100
+++ mythtv-status-1.1.0/debian/patches/makefile.patch	2024-06-10 11:26:48.0 +0200
@@ -0,0 +1,35 @@
+Description: Adapt Makefile for Debian build
+Author: Andrew Ruthven 
+Forwarded: not-needed
+Last-Update: 2024-06-10
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+* Install man pages to Debian location
+* Install systemd units into upstream location
+* Do not run tests while building "all" target
+
+Index: mythtv-status-1.1.0/Makefile
+===
+--- mythtv-status-1.1.0.orig/Makefile
 mythtv-status-1.1.0/Makefile
+@@ -2,8 +2,8 @@
+ 
+ BINDIR=$(DESTDIR)/usr/bin
+ LIBEXECDIR=$(DESTDIR)/usr/libexec/mythtv-status
+-MANDIR=$(DESTDIR)/usr/man
+-SYSTEMDDIR=$(DESTDIR)/lib/systemd/system
++MANDIR=$(DESTDIR)/usr/share/man
++SYSTEMDDIR=$(DESTDIR)/usr/lib/systemd/system
+ 
+ package=mythtv-status
+ releases=sid
+@@ -30,7 +30,7 @@ endif
+ TEST_VERBOSE=0
+ TEST_FILES=t/*.t
+ 
+-all: test
++all:
+ dist: test release
+ 
+ release: $(RELEASE_FILES)
diff -Nru mythtv-status-1.1.0/debian/patches/series mythtv-status-1.1.0/debian/patches/series
--- mythtv-status-1.1.0/debian/patches/series	2023-07-16 06:17:12.0 +0200
+++ mythtv-status-1.1.0/debian/patches/series	2024-06-10 11:26:48.0 +0200
@@ -1 +1 @@
-makefile-man-path.patch
+makefile.patch

Bug#1072913: libnss-pgsql: remove from Debian?

[Chris Hofstaedtler]

Source: libnss-pgsql
Version: 1.4.0debian-8
Severity: serious

libnss-pgsql's last upload was in 2014. This was a maintainer
upload. The last upstream release apparently happened in 2007. This
is about 17 years ago at the time of writing.

libnss-pgsql currently has an open FTBFS bug, pointing to outdated C
coding standards. Various existing patches also point into this
direction.

NSS plugins should IMO be held to high standards of being up to date
and maintained.

I propose removing libnss-pgsql from Debian, as it seems to be
effectively unmaintained for a very long time already and it looks
like interest has vanished over time.

I propose reassigning this bug to ftp.debian.org in about a month
from now.

Chris

Bug#1060467: irker: diff for NMU version 2.23+dfsg-1.1

[Chris Hofstaedtler]

Control: tags 1060467 + patch
Control: tags 1060467 + pending


Dear maintainer,

I've prepared an NMU for irker (versioned as 2.23+dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru irker-2.23+dfsg/debian/changelog irker-2.23+dfsg/debian/changelog
--- irker-2.23+dfsg/debian/changelog	2023-02-14 15:37:08.0 +0100
+++ irker-2.23+dfsg/debian/changelog	2024-06-10 11:04:35.0 +0200
@@ -1,3 +1,10 @@
+irker (2.23+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-Depend on systemd-dev (Closes: #1060467)
+
+ -- Chris Hofstaedtler   Mon, 10 Jun 2024 11:04:35 +0200
+
 irker (2.23+dfsg-1) unstable; urgency=low
 
   [ Debian Janitor ]
diff -Nru irker-2.23+dfsg/debian/control irker-2.23+dfsg/debian/control
--- irker-2.23+dfsg/debian/control	2023-02-14 15:37:08.0 +0100
+++ irker-2.23+dfsg/debian/control	2024-06-10 11:04:15.0 +0200
@@ -7,7 +7,7 @@
  debhelper-compat (= 13),
  pkg-config,
  python3,
- systemd,
+ systemd-dev,
  xmlto,
  dh-python
 Standards-Version: 4.6.2

Bug#1072912: supermin: /lib64: No such file or directory

[Chris Hofstaedtler]

Source: libguestfs
Version: 1:1.52.0-6.1
Severity: serious
User: helm...@debian.org
Usertags: dep17
X-Debbugs-CC: helm...@debian.org

The debootstrap set was uploaded, including a new glibc and
base-files. The owner and exact management of /lib64 has changed.

libguestfs tests now fail, possibly indicating it relies on some
intricate details of the /lib64 symlink. Please investigate and
update the source/tests.

https://ci.debian.net/packages/libg/libguestfs/testing/amd64/47493845/

> 3078 233s execl: /init: No such file or directory
[..]
> 3683 233s supermin: debug: listing directory /lib64
> 3684 233s /lib64: No such file or directory

Chris

Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py

[Chris Hofstaedtler]

* Samuel Henrique  [240608 20:37]:
> > If they share a name but none of the API / features, then it is not
> > a correct solution.
> 
> They do not share the same API.
> 
> > These descriptions do not sound related at all. In this case,
> > Conflicts/Replaces is not appropriate.
> 
> I see your point now, it seems like it should be just "Conflicts", do you
> agree? None of those 2 packages can/should be renamed.

Please see https://www.debian.org/doc/debian-policy/ch-files.html#binaries

Conflicts is not appropriate for programs with different
functionality.

Chris

Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py

[Chris Hofstaedtler]

Hi Samuel,

only replying to your question below, with new questions.

* Samuel Henrique  [240608 14:04]:
> For #1072733:
> 
> Chris
> > Per Debian policy this is not the correct solution for naming conflicts. 
> > Both
> > maintainer (teams), please find a policy compliant solution together.
> 
> The solution for this one seems correct, it's a Conflict + Replaces because
> both packages provide a "sherlock" library. Am I missing something?

Do both packages provide the same API? IOW: do they provide the same
"type" of library?
If so, then Conficts/Replaces may be appropriate.

If they share a name but none of the API / features, then it is not
a correct solution. 

Looking at the package descriptions on tracker.d.o:

python-sherlock:
  distributed inter-process locks with a choice of backend

sherlock:
  Find usernames across social networks

These descriptions do not sound related at all. In this case,
Conflicts/Replaces is not appropriate.

Chris

Bug#1063945: ipython: Ubuntu patch for pytest 8 support

[Chris Peterson]

Package: ipython
Version: 8.20.0-1
Followup-For: Bug #1063945
X-Debbugs-Cc: chris.peter...@canonical.com
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oracular ubuntu-patch
Control: tags -1 patch



Hi,

I identified two patches from upstream that solved this issue but
aren't available in the currently packaged version. I applied the
following in Ubuntu to solve the issue:

  * Update pytest and tests for pytest 8 compatibility (LP: #2068674).
- d/p/pytest8-nose-tests.patch: update nose-style tests for pytest 8.2+
- d/p/support-pytest-plugin.patch: update pytest plugin for pytest 8.1+


Thanks for considering the patches.


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

Kernel: Linux 6.8.0-31-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ipython-8.20.0/debian/patches/pytest8-nose-tests.patch 
ipython-8.20.0/debian/patches/pytest8-nose-tests.patch
--- ipython-8.20.0/debian/patches/pytest8-nose-tests.patch  1969-12-31 
16:00:00.0 -0800
+++ ipython-8.20.0/debian/patches/pytest8-nose-tests.patch  2024-06-06 
17:10:18.0 -0700
@@ -0,0 +1,32 @@
+Description: Update nose-style tests for pytest 8 compatbility
+ Pytest dropped support for nose-style tests in pytest 8. This patch cherry-
+ picks the patch from upstream to fix the offending tests. This patch can
+ be dropped in version 8.24.0.
+Author: Chris Peterson 
+Origin: upstream, 
https://github.com/ipython/ipython/commit/cdacafdccaf1f562e59b21b3c9f2c1a28eba54da
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ipython/+bug/2068674
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063945
+Forwarded: not-needed
+Last-Update: 2024-06-06
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/IPython/core/tests/test_pylabtools.py
 b/IPython/core/tests/test_pylabtools.py
+@@ -165,7 +165,7 @@
+ def enable_gui(self, gui):
+ pass
+ 
+-def setup(self):
++def setup_method(self):
+ import matplotlib
+ def act_mpl(backend):
+ matplotlib.rcParams['backend'] = backend
+@@ -184,7 +184,7 @@
+ self._save_cis = backend_inline.configure_inline_support
+ backend_inline.configure_inline_support = lambda *a, **kw: None
+ 
+-def teardown(self):
++def teardown_method(self):
+ pt.activate_matplotlib = self._save_am
+ pt.import_pylab = self._save_ip
+ backend_inline.configure_inline_support = self._save_cis
diff -Nru ipython-8.20.0/debian/patches/series 
ipython-8.20.0/debian/patches/series
--- ipython-8.20.0/debian/patches/series2024-01-14 16:32:19.0 
-0800
+++ ipython-8.20.0/debian/patches/series2024-06-06 17:10:38.0 
-0700
@@ -1,2 +1,4 @@
 0002-Update-intersphinx-links-for-local-access.patch
 0003-Drop-setuptools-data_files.patch
+pytest8-nose-tests.patch
+support-pytest-plugin.patch
diff -Nru ipython-8.20.0/debian/patches/support-pytest-plugin.patch 
ipython-8.20.0/debian/patches/support-pytest-plugin.patch
--- ipython-8.20.0/debian/patches/support-pytest-plugin.patch   1969-12-31 
16:00:00.0 -0800
+++ ipython-8.20.0/debian/patches/support-pytest-plugin.patch   2024-06-06 
17:22:13.0 -0700
@@ -0,0 +1,120 @@
+Description: Update pytest plugin for pytest 8
+ Pytest 8.1 changed the plugin API. This patch cherry-picks the upstream
+ modifications to the plugin for pytest 8.1+ support. This patch can be
+ dropped with upstream version 8.25.0.
+Author: Chris Peterson 
+Origin: upstream, 
https://github.com/ipython/ipython/commit/7df70a3cd79068be6f98596e427d60a5d0cfe5b3
+Bug: https://github.com/ipython/ipython/issues/14390
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ipython/+bug/2068674
+Forwarded: not-needed
+Last-Update: 2024-06-06
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/IPython/testing/plugin/pytest_ipdoctest.py
 b/IPython/testing/plugin/pytest_ipdoctest.py
+@@ -38,7 +38,11 @@
+ from _pytest.compat import safe_getattr
+ from _pytest.config import Config
+ from _pytest.config.argparsing import Parser
+-from _pytest.fixtures import FixtureRequest
++
++try:
++from _pytest.fixtures import TopRequest as FixtureRequest
++except ImportError:
++from _pytest.fixtures import FixtureRequest
+ from _pytest.nodes import Collector
+ from _pytest.outcomes import OutcomeException
+ from _pytest.pathlib import fnmatch_ex
+@@ -68,6 +72,8 @@
+ # Lazy definition of output checker class
+ CHECKER_CLASS: Optional[Type["IPDoctestOutputChecker"]] = None
+ 
++pytest_version = tuple([int(part) for part in pytest.__version__.split(".&

Bug#1070112: ipykernel: Ubuntu patch for pytest 8 support

[Chris Peterson]

Package: ipykernel
Version: 6.29.3-1
Followup-For: Bug #1070112
X-Debbugs-Cc: chris.peter...@canonical.com
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oracular ubuntu-patch
Control: tags -1 patch



Hi,

I applied the following patch in Ubuntu to fix this issue.

  * pytest8-nose-deprecation.patch: update tests for pytest 8 compatibility
(LP: #2068672).


Thanks for considering the patch.


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

Kernel: Linux 6.8.0-31-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ipykernel-6.29.3/debian/patches/pytest8-nose-deprecation.patch 
ipykernel-6.29.3/debian/patches/pytest8-nose-deprecation.patch
--- ipykernel-6.29.3/debian/patches/pytest8-nose-deprecation.patch  
1969-12-31 16:00:00.0 -0800
+++ ipykernel-6.29.3/debian/patches/pytest8-nose-deprecation.patch  
2024-06-06 16:39:16.0 -0700
@@ -0,0 +1,95 @@
+Description: Update tests for pytest 8 compatibility
+ Pytest 8 deprecated support for nose-style tests. This patch cherrry-picks
+ changes from upstream to modify tests to run with pytest 8.
+Author: Chris Peterson 
+Origin: upstream, 
https://github.com/ipython/ipykernel/commit/a7d66ae2197e0d7471ba160542cf5ff7713084b5
+Bug: https://github.com/ipython/ipykernel/issues/1230
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ipykernel/+bug/2068672
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070112
+Forwarded: not-needed
+Last-Update: 2024-06-06
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/tests/__init__.py
 b/tests/__init__.py
+@@ -7,6 +7,8 @@
+ import tempfile
+ from unittest.mock import patch
+ 
++import pytest
++
+ from ipykernel.kernelspec import install
+ 
+ pjoin = os.path.join
+@@ -15,7 +17,8 @@
+ patchers: list = []
+ 
+ 
+-def setup():
++@pytest.fixture(autouse=True)
++def _global_setup():
+ """setup temporary env for tests"""
+ global tmp
+ tmp = tempfile.mkdtemp()
+@@ -35,8 +38,8 @@
+ # install IPython in the temp home:
+ install(user=True)
+ 
++yield
+ 
+-def teardown():
+ for p in patchers:
+ p.stop()
+ 
+--- a/tests/test_eventloop.py
 b/tests/test_eventloop.py
+@@ -42,14 +42,15 @@
+ _get_qt_vers()
+ 
+ 
+-def setup():
++@pytest.fixture(autouse=True)
++def _setup_env():
+ """start the global kernel (if it isn't running) and return its client"""
+ global KM, KC
+ KM, KC = start_new_kernel()
+ flush_channels(KC)
+ 
++yield
+ 
+-def teardown():
+ assert KM is not None
+ assert KC is not None
+ KC.stop_channels()
+--- a/tests/test_message_spec.py
 b/tests/test_message_spec.py
+@@ -21,7 +21,8 @@
+ KC: BlockingKernelClient = None  # type:ignore
+ 
+ 
+-def setup():
++@pytest.fixture(autouse=True)
++def _setup_env():
+ global KC
+ KC = start_global_kernel()
+ 
+--- a/tests/test_async.py
 b/tests/test_async.py
+@@ -8,14 +8,15 @@
+ KC = KM = None
+ 
+ 
+-def setup_function():
++@pytest.fixture(autouse=True)
++def _setup_env():
+ """start the global kernel (if it isn't running) and return its client"""
+ global KM, KC
+ KM, KC = start_new_kernel()
+ flush_channels(KC)
+ 
++yield
+ 
+-def teardown_function():
+ assert KC is not None
+ assert KM is not None
+ KC.stop_channels()
diff -Nru ipykernel-6.29.3/debian/patches/series 
ipykernel-6.29.3/debian/patches/series
--- ipykernel-6.29.3/debian/patches/series  2024-01-11 14:25:38.0 
-0800
+++ ipykernel-6.29.3/debian/patches/series  2024-06-06 16:22:48.0 
-0700
@@ -1,2 +1,3 @@
 0002-test_simple_print-may-produce-stderr-content-when-ex.patch
 0003-Made-build-reproducible-patch-by-Daniel-Shahaf.patch
+pytest8-nose-deprecation.patch

Bug#1063967: protontricks: Forward pytest 8 support patch from Ubuntu

[Chris Peterson]

Package: protontricks
Version: 1.10.5-1
Followup-For: Bug #1063967
X-Debbugs-Cc: chris.peter...@canonical.com
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oracular ubuntu-patch
Control: tags -1 patch



Hi,

I applied the following patch in Ubuntu to fix this issue.


  * pytest8-caplog.patch: Update tests for pytest 8 compatibility
(LP: #2068659).


Thanks for considering the patch.


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

Kernel: Linux 6.8.0-31-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru protontricks-1.10.5/debian/patches/pytest8-caplog.patch 
protontricks-1.10.5/debian/patches/pytest8-caplog.patch
--- protontricks-1.10.5/debian/patches/pytest8-caplog.patch 1969-12-31 
16:00:00.0 -0800
+++ protontricks-1.10.5/debian/patches/pytest8-caplog.patch 2024-06-06 
12:27:04.0 -0700
@@ -0,0 +1,37 @@
+Description: Update test for pytest 8 comptability
+ Pytest 8 now includes all log levels in the caplog fixture. Apply upstream
+ changes to test case which ensures warning messages are logged. Can be dropped
+ in upstream version 1.11.1
+Author: Chris Peterson 
+Origin: upstream, 
https://github.com/Matoking/protontricks/commit/bb1da5a0ddcac1cbd577fd54fe947ff6ad1731bc
+Bug: https://github.com/Matoking/protontricks/issues/283
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/pytest/+bug/2068659
+Forwarded: not-needed
+Last-Update: 2024-06-06
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/tests/test_gui.py
 b/tests/test_gui.py
+@@ -207,7 +207,7 @@
+ assert steam_app == steam_apps[1]
+ assert (
+ "Your system locale is incapable of displaying all characters"
+-in caplog.records[0].message
++in caplog.records[-1].message
+ )
+ 
+ @pytest.mark.parametrize("gui_cmd", ["yad", "zenity"])
+--- a/tests/conftest.py
 b/tests/conftest.py
+@@ -44,6 +44,11 @@
+ logging.getLogger("protontricks").handlers.clear()
+ 
+ 
++@pytest.fixture(scope="function", autouse=True)
++def default_caplog(caplog):
++caplog.set_level(logging.INFO)
++
++
+ @pytest.fixture(scope="function")
+ def verbose_logging():
+ """
diff -Nru protontricks-1.10.5/debian/patches/series 
protontricks-1.10.5/debian/patches/series
--- protontricks-1.10.5/debian/patches/series   1969-12-31 16:00:00.0 
-0800
+++ protontricks-1.10.5/debian/patches/series   2024-06-06 12:26:50.0 
-0700
@@ -0,0 +1 @@
+pytest8-caplog.patch

Bug#909352: Clone to ftp.d.o

[Chris Hofstaedtler]

clone 909352 -1
reassign -1 ftp.debian.org
severity -1 normal
retitle -1 RM: squeak-plugins-scratch -- RoQA; obsolete plugin
affects -1 src:squeak-plugins-scratch
thanks

Dear ftpmasters,

as explained in 909352, squeak-plugins-scratch ships a plugin to
squeak-vm that is already bundled with squeak-vm.
It was not in testing since 2018 due to rc bugs and has apparently
missed bullseye and bookworm.

Please remove it.

Chris

Bug#1072753: neutron-taas: FTBFS: Session.begin() got an unexpected keyword argument 'subtransactions'

[Chris Hofstaedtler]

Source: neutron-taas
Version: 12.0.0-1
Severity: serious
Tags: ftbfs

Hi,

your package apparently FTBFS, probably due to changes in
sqlalchemy?
Please find the build log attached, and a hopefully relevant
fragment below:

==
FAIL: 
neutron_taas.tests.unit.db.test_taas_db.TaaSDbTestCase.test_tap_flow_create
neutron_taas.tests.unit.db.test_taas_db.TaaSDbTestCase.test_tap_flow_create
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/neutron/tests/base.py", line 178, in func
return f(self, *args, **kwargs)
   
  File "/<>/neutron_taas/tests/unit/db/test_taas_db.py", line 173, 
in test_tap_flow_create
ts = self._create_tap_service(ts_data)
 ^
  File "/<>/neutron_taas/tests/unit/db/test_taas_db.py", line 73, 
in _create_tap_service
with self.ctx.session.begin(subtransactions=True):
 
TypeError: Session.begin() got an unexpected keyword argument 'subtransactions'



neutron-taas_12.0.0-1.1_amd64-2024-06-07T13:37:14Z.build.gz
Description: application/gzip

Bug#1072733: closed by Debian FTP Masters (reply to Francisco Vilmar Cardoso Ruviaro ) (Bug#1072733: fixed in sherlock 0.14.4+git20240531.e5ad3c4-2

[Chris Hofstaedtler]

Control: reopen -1
Control: reassign -1 sherlock,python3-sherlock

On Fri, Jun 07, 2024 at 12:09:08PM +, Debian Bug Tracking System wrote:
>  sherlock (0.14.4+git20240531.e5ad3c4-2) unstable; urgency=medium
>  .
>* Add Conflicts and Replaces fields in the sherlock binary. (Closes: 
> #1072733)

Per Debian policy this is not the correct solution for naming
conflicts.

Both maintainer (teams), please find a policy compliant solution
together.


Chris

Bug#1072532: dh-sequence-phpcomposer: stop creating libpcre3 dependencies

[Chris Hofstaedtler]

Control: affects 1072532 src:php-ml-iri
Control: affects 1072532 src:php-mockery

On Thu, May 23, 2024 at 08:18:45PM +0200, Bastian Germann wrote:
> The dependency generation in share/php/pkgtools/base/dependency.php for
> "lib-" prefixed composer dependencies needs fixing. I caught it by it using
> libpcre3, which should be libpcre2-8-0 now. But some other generated names
> are also outdated and should be brought in sync with the current php
> interpreter version.

I've cloned #1071684 as #1072532 and set it to serious, as libpcre3
dependencies really must go away now.
Given the interpreter already uses libpcre2*, they are wrong and
probably useless. Please stop generating them ASAP, so pcre3 can be
removed from testing.

Chris

Bug#1000015: mp4h: diff for NMU version 1.3.1-17.1

[Chris Hofstaedtler]

Dear maintainer,

I've prepared an NMU for mp4h (versioned as 1.3.1-17.1). The diff
is attached to this message.

Regards.

diff -Nru mp4h-1.3.1/debian/changelog mp4h-1.3.1/debian/changelog
--- mp4h-1.3.1/debian/changelog	2018-06-27 02:04:54.0 +0200
+++ mp4h-1.3.1/debian/changelog	2024-06-03 21:06:36.0 +0200
@@ -1,3 +1,13 @@
+mp4h (1.3.1-17.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Yavor Doganov ]
+  * debian/patches/pcre2.patch: New; port to PCRE2 (Closes: #115).
+  * debian/control (Build-Depends): Replace libpcre3-dev with libpcre2-dev.
+
+ -- Chris Hofstaedtler   Mon, 03 Jun 2024 21:06:36 +0200
+
 mp4h (1.3.1-17) unstable; urgency=medium
 
   [ Axel Beckert ]
diff -Nru mp4h-1.3.1/debian/control mp4h-1.3.1/debian/control
--- mp4h-1.3.1/debian/control	2018-06-27 01:46:42.0 +0200
+++ mp4h-1.3.1/debian/control	2024-06-03 21:06:14.0 +0200
@@ -9,7 +9,7 @@
fakeroot,
gettext,
libltdl-dev,
-   libpcre3-dev,
+   libpcre2-dev,
libtool,
tidy
 Build-Conflicts: autoconf2.13,
diff -Nru mp4h-1.3.1/debian/patches/pcre2.patch mp4h-1.3.1/debian/patches/pcre2.patch
--- mp4h-1.3.1/debian/patches/pcre2.patch	1970-01-01 01:00:00.0 +0100
+++ mp4h-1.3.1/debian/patches/pcre2.patch	2024-06-03 21:06:14.0 +0200
@@ -0,0 +1,449 @@
+Description: Port to PCRE2.
+Bug-Debian: https://bugs.debian.org/115
+Author: Yavor Doganov 
+Forwarded: no
+Last-Update: 2023-12-10
+---
+
+--- mp4h.orig/src/Makefile.am
 mp4h/src/Makefile.am
+@@ -17,7 +17,7 @@
+ if LOADABLE_MODULES
+ mp4h_LDFLAGS = -export-dynamic
+ endif
+-mp4h_LDADD   = -lm $(top_builddir)/lib/libmp4h.a -lpcre @LIBINTL@ $(MODULE_LDADD)
++mp4h_LDADD   = -lm $(top_builddir)/lib/libmp4h.a -lpcre2-8 @LIBINTL@ $(MODULE_LDADD)
+ 
+ include_HEADERS = mp4h.h
+ noinst_HEADERS  = builtin.h
+--- mp4h.orig/src/builtin.c
 mp4h/src/builtin.c
+@@ -373,7 +373,7 @@
+ static char * utf8char_skip __P ((char *, int));
+ static int utf8char_strlen __P ((char *));
+ static int encoding_strlen __P ((char *));
+-static void substitute __P ((struct obstack *, const char *, const char *, int *));
++static void substitute __P ((struct obstack *, const char *, const char *, size_t *));
+ static void string_regexp __P ((struct obstack *, int, token_data **, int, const char *));
+ static void subst_in_string __P ((struct obstack *, int, token_data **, int));
+ static void generic_variable_lookup __P ((MP4H_BUILTIN_PROTO, boolean));
+@@ -382,6 +382,8 @@
+ static int array_member __P ((const char *, symbol *, boolean));
+ static int sort_function __P ((const void *, const void *));
+ static void logical_to_physical_paths __P ((char **));
++static void * pcre_malloc (size_t, void *);
++static void pcre_free (void *, void *);
+ 
+ /*  This symbol controls breakings of flow statements.  */
+ static symbol varbreak;
+@@ -398,7 +400,12 @@
+ struct lconv *my_locale;
+ 
+ /*  Table of characters used by PCRE with non-C locales  */
+-static const unsigned char *re_tableptr = NULL;
++static const uint8_t *re_tableptr = NULL;
++
++/*  PCRE contexts needed for custom memory management and adding
++non-builtin character tables.  */
++static pcre2_general_context *gen_ctxt;
++static pcre2_compile_context *comp_ctxt;
+ 
+ /*  Timer  */
+ static struct tms elapsed_time;
+@@ -662,12 +669,22 @@
+ | Initialise all builtin and predefined macros.  |
+ `---*/
+ 
++static void *
++pcre_malloc (size_t size, void *ptr)
++{
++  return xmalloc (size);
++}
++
++static void
++pcre_free (void *ptr, void *tag)
++{
++  xfree (ptr);
++}
++
+ void
+ builtin_init (void)
+ {
+   install_builtin_table (builtin_tab);
+-  pcre_malloc = xmalloc;
+-  pcre_free   = xfree;
+ }
+ 
+ /*---.
+@@ -688,18 +705,22 @@
+   varstack_check ();
+ }
+ 
+-static pcre *
++static pcre2_code *
+ xre_compile (const char *pattern, int cflags)
+ {
+-  pcre *patcomp;
+-  const char *errbuf;
+-  int erroffset;
++  pcre2_code *patcomp;
++  PCRE2_UCHAR errbuf[120];
++  int errcode;
++  size_t erroffset;
+ 
+   if (document_encoding == ENCODING_UTF8)
+-  cflags |= PCRE_UTF8;
+-  patcomp = pcre_compile (pattern, cflags, , , re_tableptr);
++  cflags |= PCRE2_UTF;
++  pcre2_set_character_tables (comp_ctxt, re_tableptr);
++  patcomp = pcre2_compile ((PCRE2_SPTR) pattern, PCRE2_ZERO_TERMINATED,
++   cflags, , , comp_ctxt);
+   if (patcomp == 0)
+ {
++  pcre2_get_error_message (errcode, errbuf, sizeof (errbuf));
+   MP4HERROR ((warning_status, 0,
+ _("Warning:%s:%d: Bad regular expression `%s' at position %d: %s"),
+  CURRENT_FILE_LINE, pattern, erroffset, errbuf));
+@@ -822,11 +843,10 @@
+   register char *cp;
+   char *name;
+   int i, j, special_chars;
+-  pcre *re;
+-  pcre_extra *re_extra = NULL;
+-  const char *err

Bug#1072355: nss-pam-ldapd: upload with maintainer-built binaries cannot migrate

[Chris Hofstaedtler]

Source: nss-pam-ldapd
Version: 0.9.12-6
Severity: serious

Hi,

thanks for uploading to unstable. However the upload included
maintainer-built binaries (for Arch: all and amd64). Migration to
testing of these is forbidden by release team policy.
Please upload a new version (no further changes needed) without any
binaries to let the package migrate.

Chris

Bug#1072353: sysbench: replace luajit2 with luajit

[Chris Hofstaedtler]

Source: sysbench
Version: 1.0.20+ds-6
Severity: serious
Control: block 1069780 by -1

luajit2 was requested to be removed, see #1069780. Please switch
your (Build-Depends) over to luajit, which has become the openresty
luajit(2) source.

Bug#1072352: lua-vips: replace luajit2 with luajit

[Chris Hofstaedtler]

Source: lua-vips
Version: 1.1.11-1
Severity: serious
Control: block 1069780 by -1

luajit2 was requested to be removed, see #1069780. Please switch
your (Build-Depends) over to luajit, which has become the openresty
luajit(2) source.

Bug#1072351: love: replace luajit2 with luajit

[Chris Hofstaedtler]

Source: love
Version: 11.5-1
Severity: serious
Control: block 1069780 by -1

luajit2 was requested to be removed, see #1069780. Please switch
your (Build-Depends) over to luajit, which has become the openresty
luajit(2) source.

Bug#1072350: libnginx-mod-http-lua: replace luajit2 with luajit

[Chris Hofstaedtler]

Source: libnginx-mod-http-lua
Version: 1:0.10.26-2
Severity: serious
Control: block 1069780 by -1

luajit2 was requested to be removed, see #1069780. Please switch
your (Build-Depends) over to luajit, which has become the openresty
luajit(2) source.

Bug#1072349: lua-resty-lrucache: replace luajit2 with luajit

[Chris Hofstaedtler]

Source: lua-resty-lrucache
Version: 0.13-10
Severity: serious
Control: block 1069780 by -1

luajit2 was requested to be removed, see #1069780. Please switch
your (Build-Depends) over to luajit, which has become the openresty
luajit(2) source.

Bug#1072348: lua-resty-core: replace luajit2 with luajit

[Chris Hofstaedtler]

Source: lua-resty-core
Version: 0.1.28-2
Severity: serious
Control: block 1069780 by -1

luajit2 was requested to be removed, see #1069780. Please switch
your (Build-Depends) over to luajit, which has become the openresty
luajit(2) source.

Bug#1072347: luajit2: should not be shipped with trixie

[Chris Hofstaedtler]

Source: luajit2
Version: 2.1-20230410-1
Severity: serious

src:luajit2 now duplicates src:luajit, see #1069780. As such it
should not be part of trixie.

Bug#1072085: FTBFS: PermissionError: [Errno 13] Permission denied: '/dev/stdout'

[Chris Hofstaedtler]

Source: supervisor
Version: 4.2.5-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: z...@debian.org

Dear Maintainer,

your package fails to build from source, see below and the attached
build log.

This build was done in sbuild with unshare backend. As this is now a
configuration used by the buildds, people consider such problems to be
release-critical.

Chris

==
ERROR: test_ctor_with_dev_stdout 
(supervisor.tests.test_loggers.StdoutTests.test_ctor_with_dev_stdout)
--
Traceback (most recent call last):
  File "/<>/supervisor/tests/test_loggers.py", line 232, in 
test_ctor_with_dev_stdout
handler = self._makeOne('/dev/stdout')
  
  File "/<>/supervisor/tests/test_loggers.py", line 37, in _makeOne
return klass(*arg, **kw)
   ^
  File "/<>/supervisor/loggers.py", line 160, in __init__
self.stream = open(filename, mode)
  
PermissionError: [Errno 13] Permission denied: '/dev/stdout'

--
Ran 1369 tests in 9.365s

FAILED (errors=1)
Test failed: 
error: Test failed: 
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: 
python3.11 setup.py test
dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned 
exit code 13
make: *** [debian/rules:4: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


supervisor_4.2.5-1_arm64.build.gz
Description: application/gzip

Bug#1071983: netctl: puts .service files into /

[Chris Hofstaedtler]

Source: netctl
Version: 1.28-1
Severity: serious
Justification: FHS violation

Rebuilding your package in current unstable leads to .service files
being installed into /:

-rw-r--r-- root/root   512 2023-08-06 22:20 ./netctl-auto@.service
-rw-r--r-- root/root   445 2023-08-06 22:20 ./netctl-ifplugd@.service
-rw-r--r-- root/root   284 2023-08-06 22:20 ./netctl-sleep.service
-rw-r--r-- root/root   289 2023-08-06 22:20 ./netctl-wait-online.service
-rw-r--r-- root/root   260 2023-08-06 22:20 ./netctl.service
-rw-r--r-- root/root   316 2023-08-06 22:20 ./netctl@.service

Please investigate and fix this for trixie.

Chris



netctl_1.28-1_arm64-2024-05.build.gz
Description: application/gunzip

Bug#1071982: FTBFS: help2man fails

[Chris Hofstaedtler]

Source: jupyterhub
Version: 3.0.0+ds1-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: z...@debian.org

Your package currently fails to build, see below and the attached build
log:

PYTHONPATH=debian/jupyterhub/usr/lib/python3.11/dist-packages help2man 
--output=jupyterhub-singleuser.1 --name="Single-user server for Jupyter 
notebooks" --version-string=$(dpkg-parsechangelog -S Version | sed s/-[^-]*$//) 
debian/jupyterhub/usr/bin/j
upyterhub-singleuser
help2man: can't get `--help' info from 
debian/jupyterhub/usr/bin/jupyterhub-singleuser
Try `--no-discard-stderr' if option outputs to stderr
make[1]: *** [debian/rules:14: override_dh_auto_install] Error 1

Bug#1071749: bidentd: Cannot work with current kernels - remove?

[Chris Hofstaedtler]

Source: bidentd
Version: 1.1.4-1.2
Severity: serious

Inspection of the source reveals bidentd uses /proc/net/ip_conntrack
and/or /proc/net_ip_masquerade to identify connections.
These files have long been removed from Linux.

I believe bidentd thus cannot work at all and propose its removal.

I'm filing with sev: serious, because it's been a really really long
time already since when bidentd could have become useful, and IMO we
should not have it in trixie.

Chris

Bug#1070965: rtorrent: does not start due to soname update

[Chris Lamb]

Liam Stitt wrote:

> libxmlrpc-core-c3t64 has bumped that soname to .4, so presumably a rebuild 
> will
> fix this.

A rebuild will indeed fix this, or at least rebuilding rtorrent
locally fixes this for me.

Can the maintainer therefore please request a binNMU?


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#1071063: screenkey: malformed debian/changelog

[Chris Lamb]

Package: screenkey
Version: 1:1.5-4
Severity: serious
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org


Hi,

This might not *strictly* be an RC bug, but the latest upload of
screenkey has the following entry in debian/changelog:

<<<
screenkey (1:1.5-4) unstable; urgency=medium

  * fixed d/watch
  * bumped Standards-Version: 4.7.0
  * removed the stance X-Python-Version

 --
>>>

Note in particular the missing date. This doesn't break dak, otherwise
it would not have been accepted by the archive, but it breaks many
other tools (eg. gbp-buildpackage, etc.) as well as other things. For
example, the package is not reproducible because SOURCE_DATE_EPOCH
cannot be extracted from the debian/changelog.

When building the package you should have seen warnings by, for
instance, dh_installchangelogs, dpkg-gencontrol, dpkg-genchanges,
etc. :)

Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#1070416: src:diffoscope: unsatisfied build dependency in testing: aapt

[Chris Lamb]

Paul Gevers wrote:

> Dose [1] is reporting a build issue with your package, it's missing a
> build dependency. Obviously your build dependencies shouldn't be
> removed from testing, but unfortunately there are multiple scenarios
> where that can happen nevertheless.

Looks like this happened due to these RC bugs:

  https://bugs.debian.org/1062206
  https://bugs.debian.org/1062110
  https://bugs.debian.org/1062209

i.e. it wasn't that aapt was removed or barred from testing for some
reason specific to aapt's code or license, etc. It is, as I understand
it, not impossible that it might return to testing without further
intervention on our part..?

Otherwise, we can very cleanly remove this build dependency, even
keeping the .arsc file support in diffoscope itself.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#1069538: zeroc-ice: FTBFS on armel: Gradle / Java heap space out-of-memory error

[Chris Knadle]

retitle 1069538 zeroc-ice: FTBFS on armel: Gradle / Java heap space 
out-of-memory-error


tags 1069538 - moreinfo

thanks

I've done additional test builds of zeroc-ice-3.7.10-2.2 on armel on 
porter boxes amdahl and abel and the build fails with the same error 
which seems to be during a Java memory check. It is still unclear as to 
why this error is happening now but not previously.


   -- Chris

--
Chris Knadle
chris.kna...@coredump.us

Bug#1070019: [Pkg-utopia-maintainers] Bug#1070019: udisks2: autopkgtest failure: fsconfig system call failed: /dev/sr1: Can't open blockdev

[Chris Hofstaedtler]

* Chris Hofstaedtler  [240429 15:24]:
> > udisks2's autopkgtest fails when tried together with util-linux 2.40. An
> > example can be seen here:
> > https://ci.debian.net/packages/u/udisks2/testing/amd64/46012968/
> > 
> > 537s ==
> > 537s FAIL: test_ext4 (__main__.FS.test_ext4)
> > 537s fs: ext4
> > 537s --
> > 537s Traceback (most recent call last):
> > 537s   File 
> > "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 
> > 1107, in _do_udisks_check
> > 537s cd_fs.call_mount_sync(ro_options, None)
> > 537s gi.repository.GLib.GError: udisks-error-quark: 
> > GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 
> > at /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call 
> > failed: /dev/sr1: Can't open blockdev (0)
> > 537s
> > 537s During handling of the above exception, another exception occurred:
> > 537s
> > 537s Traceback (most recent call last):
> > 537s   File 
> > "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 
> > 725, in test_ext4
> > 537s self._do_fs_check('ext4')
> > 537s   File 
> > "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 
> > 894, in _do_fs_check
> > 537s self._do_udisks_check(fs_type)
> > 537s   File 
> > "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 
> > 1112, in _do_udisks_check
> > 537s self.fail('Mounting read-only device with \'rw\' option failed'
> > 537s AssertionError: Mounting read-only device with 'rw' option failedwith 
> > an unexpected error.
> > 537s Got: udisks-error-quark: 
> > GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 
> > at /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call 
> > failed: /dev/sr1: Can't open blockdev (0)
> > 537s Expected: 'is write-protected but explicit read-write mode requested' 
> > or 'is write-protected but `rw' option given'
 

> I won't get to it this week (also re: stable v2.40.1), but maybe
> someone else has seen this failure already?

Having said that, it seems likely the test was broken by this
change in util-linux:
  libmount: report kernel message from new API
  
https://github.com/util-linux/util-linux/commit/9da5644e414cdc318f0311260dabc6035c85b58e

I don't know if the error messages are supposed to be stable or not,
but it looks like a very intentional change :-)

Orthogonally, "/dev/sr1: Can't open blockdev" seems not very
informative if it's supposed to mean "write-protected but `rw'
option given".

Chris

Bug#1070019: [Pkg-utopia-maintainers] Bug#1070019: udisks2: autopkgtest failure: fsconfig system call failed: /dev/sr1: Can't open blockdev

[Chris Hofstaedtler]

Dear util-linux@,

in Debian, udisks2 2.10.1-6 (autopkg-)tests fail with util-linux
2.40, but passed with 2.39. We are not yet sure if this is directly
caused by util-linux, but it seems somewhat likely.

I won't get to it this week (also re: stable v2.40.1), but maybe
someone else has seen this failure already?

> udisks2's autopkgtest fails when tried together with util-linux 2.40. An
> example can be seen here:
> https://ci.debian.net/packages/u/udisks2/testing/amd64/46012968/
> 
> 537s ==
> 537s FAIL: test_ext4 (__main__.FS.test_ext4)
> 537s fs: ext4
> 537s --
> 537s Traceback (most recent call last):
> 537s   File 
> "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 
> 1107, in _do_udisks_check
> 537s cd_fs.call_mount_sync(ro_options, None)
> 537s gi.repository.GLib.GError: udisks-error-quark: 
> GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 at 
> /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call 
> failed: /dev/sr1: Can't open blockdev (0)
> 537s
> 537s During handling of the above exception, another exception occurred:
> 537s
> 537s Traceback (most recent call last):
> 537s   File 
> "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 725, 
> in test_ext4
> 537s self._do_fs_check('ext4')
> 537s   File 
> "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 894, 
> in _do_fs_check
> 537s self._do_udisks_check(fs_type)
> 537s   File 
> "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 
> 1112, in _do_udisks_check
> 537s self.fail('Mounting read-only device with \'rw\' option failed'
> 537s AssertionError: Mounting read-only device with 'rw' option failedwith an 
> unexpected error.
> 537s Got: udisks-error-quark: 
> GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 at 
> /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call 
> failed: /dev/sr1: Can't open blockdev (0)
> 537s Expected: 'is write-protected but explicit read-write mode requested' or 
> 'is write-protected but `rw' option given'
> 
> I do not understand what this error means, or what the underlying problem is.
> Please investigate.

For context, Debian's util-linux 2.40-7 should have everything from
2.40 stable up to a8aa0b5f154a44557f5bae5a4027bdbfe42b0323.

Chris

Bug#1070027: fdisk: dependency problems prevent configuration of fdisk

[Chris Hofstaedtler]

Control: reassign -1 dpkg

* Vincent Lefevre  [240428 22:33]:
> Package: fdisk
> Version: 2.40-8
> Severity: serious
...
> Setting up util-linux (2.40-8) ...
> fstrim.service is a disabled or a static unit not running, not starting it.
> dpkg: error: dpkg frontend lock was locked by another process with pid 58569
> Note: removing the lock file is always wrong, can damage the locked area
> and the entire system. See .
> ==  How can you help?  (doc: https://wiki.debian.org/how-can-i-help ) 
> ==
> 
> -  Show old opportunities as well as new ones: how-can-i-help --old  -
> E: Sub-process /usr/bin/dpkg returned an error code (2)
> Setting up bsdextrautils (2.40-8) ...
> dpkg: dependency problems prevent configuration of fdisk:
>  fdisk depends on libfdisk1 (= 2.40-8); however:
>   Version of libfdisk1:amd64 on system is 2.40-6.
> 
> dpkg: error processing package fdisk (--configure):
>  dependency problems - leaving unconfigured
> Setting up eject (2.40-8) ...
> Setting up perl-modules-5.38 (5.38.2-4) ...
> Setting up mount (2.40-8) ...
> Setting up libperl5.38t64:amd64 (5.38.2-4) ...
> Setting up util-linux-extra (2.40-8) ...
> Setting up perl (5.38.2-4) ...
> Processing triggers for libc-bin (2.37-19) ...
> Processing triggers for man-db (2.12.1-1) ...
> Processing triggers for mailcap (3.70+nmu1) ...
> Errors were encountered while processing:
>  fdisk
> 
> There seem to be 2 issues: one with the dpkg lock (which may be
> bug 1069183 in aptitude) and one
Possible.

> with fdisk.

I see no evidence of that in the log.

C

Bug#1070020: autopkgtest: (unrelated) packages not found

[Chris Hofstaedtler]

Source: mmdebstrap
Version: 1.4.3-6
Severity: serious
X-Debbugs-Cc: debian-rele...@lists.debian.org

Hi,

the autopkgtests for mmdebstrap as part of migration tests for
testing/amd64 fail with apt reporting 'Not found' errors.

As an example, for this scenario:
mmdebstrap 1.4.3-6
util-linux/2.40-8 gdm3/46.0-2 sssd/2
src:util-linux from unstable
src:gdm3 from unstable
src:sssd from unstable
https://ci.debian.net/packages/m/mmdebstrap/testing/amd64/46033215/

1085s Err:22 http://127.0.0.1/debian unstable/main amd64 libssl3 amd64 3.1.5-1
1085s   404  File not found [IP: 127.0.0.1 80]
...
1085s Err:41 http://127.0.0.1/debian unstable/main amd64 libdb5.3 amd64 
5.3.28+dfsg2-4+b1
1085s   404  File not found [IP: 127.0.0.1 80]
...
1085s Err:73 http://127.0.0.1/debian unstable/main amd64 libgdbm6 amd64 
1.23-5+b1
1085s   404  File not found [IP: 127.0.0.1 80]
1085s Err:74 http://127.0.0.1/debian unstable/main amd64 libgdbm-compat4 amd64 
1.23-5+b1
1085s   404  File not found [IP: 127.0.0.1 80]

This looks like a pinning problem or some other issue. Given libssl3 is
a problem here, which is NOT a package considered for migration in this
test, I don't see how the test failure is actually related to the
involved packages.
If this is a transient situation, please detect it and exit with status
77.

Chris

Bug#1070019: udisks2: autopkgtest failure: fsconfig system call failed: /dev/sr1: Can't open blockdev

[Chris Hofstaedtler]

Source: udisks2
Version: 2.10.1-6
Severity: serious

Hi,

udisks2's autopkgtest fails when tried together with util-linux 2.40. An
example can be seen here:
https://ci.debian.net/packages/u/udisks2/testing/amd64/46012968/

537s ==
537s FAIL: test_ext4 (__main__.FS.test_ext4)
537s fs: ext4
537s --
537s Traceback (most recent call last):
537s   File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", 
line 1107, in _do_udisks_check
537s cd_fs.call_mount_sync(ro_options, None)
537s gi.repository.GLib.GError: udisks-error-quark: 
GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 at 
/media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call failed: 
/dev/sr1: Can't open blockdev (0)
537s 
537s During handling of the above exception, another exception occurred:
537s 
537s Traceback (most recent call last):
537s   File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", 
line 725, in test_ext4
537s self._do_fs_check('ext4')
537s   File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", 
line 894, in _do_fs_check
537s self._do_udisks_check(fs_type)
537s   File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", 
line 1112, in _do_udisks_check
537s self.fail('Mounting read-only device with \'rw\' option failed'
537s AssertionError: Mounting read-only device with 'rw' option failedwith an 
unexpected error.
537s Got: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: 
Error mounting /dev/sr1 at /media/root/41b1acb1-744c-422a-9071-2dba5368a683: 
fsconfig system call failed: /dev/sr1: Can't open blockdev (0)
537s Expected: 'is write-protected but explicit read-write mode requested' or 
'is write-protected but `rw' option given'

I do not understand what this error means, or what the underlying problem is.
Please investigate.

Chris

Bug#1069923: marked as pending in util-linux

[Chris Hofstaedtler]

Control: tag -1 pending

Hello,

Bug #1069923 in util-linux reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/util-linux/-/commit/c75d35c930036610bc82b92152daa6975e8c2a98


Also cover ctrlaltdel in /usr-move mitigation

Closes: #1069923


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1069923

Bug#1069064: marked as pending in util-linux

[Chris Hofstaedtler]

Control: tag -1 pending

Hello,

Bug #1069064 in util-linux reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/util-linux/-/commit/e7b4b439820d215cc81e1b37d1950216378a2289


Fix /usr-move mitigation

Closes: #1069064


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1069064

Bug#1069762: pdns-recursor: CVE-2024-25583 - 4.8.8 for stable

[Chris Hofstaedtler]

* Moritz Muehlenhoff  [240425 08:44]:
> On Thu, Apr 25, 2024 at 08:37:14AM +0200, Chris Hofstaedtler wrote:
> > Hi Moritz,
> > 
> > could we once again use the upstream release for stable?
> > debdiff 4.8.7-1 -> 4.8.8-1 is attached.
> 
> Ack. Following the 4.8 releases has served us well. debdiff looks fine,
> please build with -sa and upload to security-master.

Done.

Thanks,
Chris

Bug#1064311: rdkit: NMU diff for 64-bit time_t transition

[Chris Hofstaedtler]

On Wed, Apr 24, 2024 at 09:25:29AM +0300, Andrius Merkys wrote:
> Hi,
> 
> On Mon, 19 Feb 2024 21:35:16 + Steve Langasek 
> wrote:> Since turning on 64-bit time_t is being handled centrally through a
> change
> > to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
> > important that libraries affected by this ABI change all be uploaded close
> > together in time.  Therefore I have prepared a 0-day NMU for rdkit
> > which will initially be uploaded to experimental if possible, then to
> > unstable after packages have cleared binary NEW.
> > 
> > Please find the patch for this NMU attached.
> 
> It is most likely my fault this has not been resolved yet - by uploading
> 202309.3-3 I trashed 202309.3-2.1~exp1. Am I right that I should reupload
> rdkit with t64 binaries to experimental now?

t64 is already in unstable and making its way to testing. So you are
a bit late with getting rdkit fixed for t64.

An upload with t64 binaries is required as soon as possible. Given
the packages have to go to binary-NEW, you must upload with
binaries, and then probably follow up with a source-only upload once
they are ACCEPTed.

Chris

Bug#1065100: efingerd: Depends on libident, which is NBS

[Chris Hofstaedtler]

Control: reassign -1 release.debian.org
Control: retitle -1 nmu: efingerd_1.6.7-1
Control: severity -1 normal

On Thu, Feb 29, 2024 at 02:41:54PM -0500, Boyuan Yang wrote:
> Severity: serious
> Justification: Policy 2.2.1
> 
> Package efingerd depends on binary package libident, but this package has
> been renamed to libident0 due to time64 transition.
...
> You may need to rebuild the package.

This should just have been filed as a binNMU request to
release.debian.org. There was no need to remove the package from
testing. A local no-change rebuild shows that it picks up the new
libident0 name just fine.

Release team, please schedule binNMU for this package.


Chris

Bug#1069538: zeroc-ice: FTBFS on armel: make[3]: out of memory error

[Chris Knadle]

Hello Lucas.

The zeroc-ice 3.7.10-2.2 package built correctly on an armel buildd 
within two weeks ago:


https://buildd.debian.org/status/logs.php?pkg=zeroc-ice=3.7.10-2.2=armel

The underlying error in the build logs you sent looks like an 
out-of-memory condition:


> Failed to execute 
org.gradle.process.internal.health.memory.DefaultMemoryManager$MemoryCheck@12c1b75.

> java.lang.OutOfMemoryError: Java heap space
> An exception has occurred in the compiler (17.0.11). Please file a 
bug against the Java compiler via the Java bug reporting page 
(https://bugreport.java.com) after checking the Bug Database 
(https://bugs.java.com) for duplicates. Include your program, the 
following diagnostic, and the parameters passed to the Java compiler in 
your report. Thank you.

> java.lang.OutOfMemoryError: Java heap space
> :test:compileJava FAILED
> :test:compileJava (Thread[Task worker for ':' Thread 3,5,main]) 
completed. Took 5 mins 20.937 secs.


I suspect this isn't a bug in the zeroc-ice package.

   -- Chris

--
Chris Knadle
chris.kna...@coredump.us

Bug#1069538: zeroc-ice: FTBFS on armel: appears to be out-of-memory condition

[Chris Knadle]

tags 1069538 + moreinfo

thanks