Bug#1072211: texlive-base: pdflatex very slow after upgrading to texlive 2024.20240401-2

[Preuße]

On 30.05.2024 13:23, J.L.G. Pallero wrote:

Hi,


After the last upgrade of texlive packages in Sid, from
2023.20240207-1 to 2024.20240401-2, I found pdflatex very slow in the
compilation. The same documents compiled with the 2023.20240207-1
version were built quicker. Is it a problem on my side or is a
general behavior?




See the discussion in Bug#1070150. Does that sound familiar.

H.
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1071754: Upload to experimental to test rebuild (nghttp3 transition)

[Bálint Réczey]

Control: tags -1 moreinfo

Hi Sakirnth,

Sakirnth Nagarasa  ezt írta (időpont: 2024. máj.
24., P, 17:31):
>
> Source: wireshark
> X-Debbugs-Cc: c...@packages.debian.org
> Version: 4.2.5-1
> Severity: wishlist
>
> Hello
>
> I uploaded the recent nghttp3 version to experimental. Is it possible to
> upload Wireshark version 4.2.5 to experimental to test that it builds on
> every release architecture with the new nghttp3 version 1.3.0-1 binary
> packages. That I can request a transition slot.

I'm surprised about this request despite having managed multiple
transitions myself.
AFAIK it is enough to test rebuild reverse dependencies on a single
architecture as a prerequisite for requesting a transition slot.
Is there any reason to expect that the test builds would fail due to
differences between architectures?
If there is none I suggest just asking for the transition slot since
as I see (in #1070079) wireshark builds fine on amd64.

BTW I recommend using ratt for reverse dependency test rebuilds.

Cheers,
Balint

Bug#1072213: Latest package solve the

[Stewart Ferguson]

Correction to the original issue.

I said "linux-image-amd64 for bookworm"
I meant "linux-image-amd64 for bullseye"

From: Stewart Ferguson
Sent: 30 May 2024 15:00
To: 1072...@bugs.debian.org <1072...@bugs.debian.org>
Subject: Latest package solve the

I was able to solve the problem on a private archive by building the
latest package status available in salsa [1] using branch origin/470
(commit 2775490611e205a6fed787e7ff6d69d241f8ed8f)

That branch has been idle since Mar 5 2024.  I think we just need the
Maintainer to release and upload this to the archive.

[1] https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers/-/tree/470

Bug#1072213: Latest package solve the

[Stewart Ferguson]

I was able to solve the problem on a private archive by building the 
latest package status available in salsa [1] using branch origin/470 
(commit 2775490611e205a6fed787e7ff6d69d241f8ed8f)

That branch has been idle since Mar 5 2024.  I think we just need the 
Maintainer to release and upload this to the archive.

[1] https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers/-/tree/470

Bug#1057290: bpftool: please build from https://github.com/libbpf/bpftool

[Luca Boccassi]

On Thu, 30 May 2024 at 00:17, Sudip Mukherjee
 wrote:
>
> On Wed, 29 May 2024 at 23:27, Luca Boccassi  wrote:
> >
> > On Wed, 29 May 2024 19:00:59 +0100 Ben Hutchings 
> > wrote:
> > > On Sat, 2023-12-02 at 20:04 +, Sudip Mukherjee wrote:
> > > > And so, it will be great if kernel team will like to package and
> > > > maintain it, if not, then I will be happy to do it. Please
> > > > reject this bug report if you think bpftool should not be done
> > > > separately and should live inside kernel source package.
> > >
> > > Since you are already maintaining libbpf I would be happy to hand
> > over
> > > bpftool to you.  I will try to discuss this at this evening's team
> > > meeting.
> >
> > What about moving libbpf and bpftool to the kernel team area under
> > Salsa? That way more people can help, and it can use salsa-ci too
>
> bpftool is already with the kernel team and being built from kernel
> source. And I anticipated that bpftool will move to github like
> upstream libbpf did and also mentioned that at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948041#83. So, its
> upto the kernel team what they want to do with bpftool -
> 1. continue to build from kernel source and we can just close this bug
> 2. Split bpftool from kernel source and package it from github. The
> kernel team can maintain if they want to maintain an userspace
> package. If the kernel team does not want to maintain it, I can do
> that.
>
> About libbpf, I am confused with your message. What kind of help? Are
> you seeing that libbpf is not maintained properly?

I'm not talking about the upstream source, but about the debian
repository: given both of these are inextricably tied to the kernel, I
think it would be good to have the downstream repositories in salsa,
in the kernel-team area - and of course, still including yourself as
repo owner. The kernel team is not only for the kernel package, but
also other kernel-adjacent packages like ethtool, iproute2, firmware,
iw, etc: https://salsa.debian.org/kernel-team

Bug#1039883: The issue impacts SSD disks as well

[Emanuele Rocca]

Hey,

On 2023-11-05 04:12, Hervé Werner wrote:
> I faced this issue on real data but I struggled to find a reliable scenario 
> to reproduce it. Here is what I just came up with:
>   sudo mkfs -t ext4 -O fast_commit,inline_data /dev/sdb
>   sudo mount /dev/sdb /mnt/
>   sudo install -d -o myuser /mnt/annex
>   cd /mnt/annex
>   git init && git annex init
>   for i in {1..2}; do
> for i in {1..1}; do
>   dd if=/dev/urandom of=file-${i} bs=1K count=1 2>/dev/null
> done
> git annex add -J cpus . >/dev/null && git annex sync -J cpus && git annex 
> fsck -J cpus >/dev/null
> git rm * && git annex sync  && git annex dropunused all
>   done
> 
> Then at some point the following error appears:
>   EXT4-fs error (device sdb): ext4_map_blocks:577: inode #3942343: block 4: 
> comm git-annex:w: lblock 1 mapped to illegal pblock 4 (length 1)

Just a quick note to confirm that I can reliably reproduce the issue
using a USB stick and the above script on Bookworm. After running the
reproducer for a few minutes I start getting the following in dmesg:

kernel: EXT4-fs error (device sdf): ext4_map_blocks:607: inode #9971675: block 
4: comm git-annex:w: lblock 1 mapped to illegal pblock 4 (length 1)

uname -a is:
Linux ariel 6.1.0-21-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) 
x86_64 GNU/Linux

Bug#1072216: reuse: Rejects annotating .taprc file

[Wesley Schwengle]

Package: reuse
Version: 3.0.1-1
Severity: important
X-Debbugs-Cc: wes...@schwengle.net

Dear Maintainer,

I'm unable to use `reuse annotate' on a `.taprc' file (from node-tap).

$ cat .taprc
---

color: false
#coverage: false
disable-coverage: true
allow-incomplete-coverage: true
allow-empty-coverage: true
debug: false
reporter: tap
reporter-arg: []
include:
  - t/*.@([mc]js|[jt]sx?)

$ reuse annotate --copyright "Wesley Schwengle" --license MIT --style python 
.taprc
usage: reuse annotate [-h] [--copyright COPYRIGHT] [--license LICENSE]
  [--contributor CONTRIBUTOR] [--year YEAR]
  [--style 
{applescript,aspx,bat,bibtex,c,csingle,css,f,ftl,handlebars,haskell,html,jinja,julia,lisp,m4,ml,f90,plantuml,python,rst,semicolon,tex,vst,vim,xquery}]
  [--copyright-style 
{spdx,spdx-c,spdx-symbol,string,string-c,string-symbol,symbol}]
  [--template TEMPLATE] [--exclude-year] 
[--merge-copyrights]
  [--single-line | --multi-line] [--recursive] 
[--no-replace]
  [--force-dot-license | --fallback-dot-license | 
--skip-unrecognised]
  [--skip-existing]
  path [path ...]
reuse annotate: error: The following files do not have a recognised file 
extension. Please use --style, --force-dot-license, --fallback-dot-license, or 
--skip-unrecognised:

.taprc

Please notice the --style python in the annotate function and thus should work.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'testing'), (100, 'experimental'), (10, 
'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 
'oldoldstable'), (10, 'stable'), (10, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages reuse depends on:
ii  python3 3.11.8-1
ii  python3-binaryornot 0.4.4+git20230412.ac4f56e+dfsg-2
ii  python3-boolean 4.0-4
ii  python3-debian  0.1.49
ii  python3-jinja2  3.1.3-1
ii  python3-license-expression  30.3.0-1

reuse recommends no packages.

reuse suggests no packages.

-- no debconf information

Bug#1072035: bookworm-pu: package dns-root-data/2024041801

[Marco d'Itri]

On May 27, Jonas Meier  wrote:

>   [ ] attach debdiff against the package in (old)stable

diff -Nru dns-root-data-2023010101/debian/changelog 
dns-root-data-2024041801~deb12u1/debian/changelog
--- dns-root-data-2023010101/debian/changelog   2023-01-11 16:00:11.0 
+0100
+++ dns-root-data-2024041801~deb12u1/debian/changelog   2024-05-30 
14:02:49.0 +0200
@@ -1,3 +1,19 @@
+dns-root-data (2024041801~deb12u1) bookworm; urgency=medium
+
+  * Rebuild for bookworm. (Closes: #1072035)
+
+ -- Marco d'Itri   Thu, 30 May 2024 14:02:49 +0200
+
+dns-root-data (2024041801) unstable; urgency=medium
+
+  * Add myself to the Uploaders field, as discussed with Ondřej.
+  * Fix the package description. (Closes: #1064829)
+  * Update the expired Verisign GRS PGP key.
+  * Update the root hints file to version 2024041801, with:
++ updated A and  records for B. (Closes: #1054393)
+
+ -- Marco d'Itri   Tue, 21 May 2024 16:25:44 +0200
+
 dns-root-data (2023010101) unstable; urgency=medium
 
   * merge current root hints and signatures (same contents as before)
diff -Nru dns-root-data-2023010101/debian/control 
dns-root-data-2024041801~deb12u1/debian/control
--- dns-root-data-2023010101/debian/control 2022-12-21 00:52:11.0 
+0100
+++ dns-root-data-2024041801~deb12u1/debian/control 2024-05-21 
16:25:42.0 +0200
@@ -4,6 +4,7 @@
 Maintainer: dns-root-data packagers 
 Uploaders:
  Daniel Kahn Gillmor ,
+ Marco d'Itri ,
  Ondřej Surý ,
  Robert Edmonds ,
 Build-Depends:
@@ -13,7 +14,7 @@
  openssl,
  unbound-anchor,
  xml2,
-Standards-Version: 4.6.1
+Standards-Version: 4.7.0.0
 Homepage: https://data.iana.org/root-anchors/
 Vcs-Git: https://salsa.debian.org/dns-team/dns-root-data.git
 Vcs-Browser: https://salsa.debian.org/dns-team/dns-root-data
@@ -24,7 +25,7 @@
 Multi-Arch: foreign
 Depends:
  ${misc:Depends},
-Description: DNS root data including root zone and DNSSEC key
+Description: DNS root hints and DNSSEC trust anchor
  This package contains various root zone related data as published
  by IANA to be used by various DNS software as a common source
  of DNS root zone data, namely:
Binary files /tmp/osYYJAlpQA/dns-root-data-2023010101/registry-admin.key and 
/tmp/1ohQbBsBE0/dns-root-data-2024041801~deb12u1/registry-admin.key differ
diff -Nru dns-root-data-2023010101/root.hints 
dns-root-data-2024041801~deb12u1/root.hints
--- dns-root-data-2023010101/root.hints 2023-01-11 08:22:00.0 +0100
+++ dns-root-data-2024041801~deb12u1/root.hints 2024-05-21 16:25:42.0 
+0200
@@ -9,8 +9,8 @@
 ;   on server   FTP.INTERNIC.NET
 ;   -OR-RS.INTERNIC.NET
 ;
-;   last update: January 01, 2023
-;   related version of root zone: 2023010101
+;   last update: April 18, 2024
+;   related version of root zone: 2024041801
 ; 
 ; FORMERLY NS.INTERNIC.NET 
 ;
@@ -21,8 +21,8 @@
 ; FORMERLY NS1.ISI.EDU 
 ;
 .360  NSB.ROOT-SERVERS.NET.
-B.ROOT-SERVERS.NET.  360  A 199.9.14.201
-B.ROOT-SERVERS.NET.  360    2001:500:200::b
+B.ROOT-SERVERS.NET.  360  A 170.247.170.2
+B.ROOT-SERVERS.NET.  360    2801:1b8:10::b
 ; 
 ; FORMERLY C.PSI.NET 
 ;
Binary files /tmp/osYYJAlpQA/dns-root-data-2023010101/root.hints.sig and 
/tmp/1ohQbBsBE0/dns-root-data-2024041801~deb12u1/root.hints.sig differ

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1070429: libcapi20-dev: copyright file missing (policy 12.5)

[Andreas Beckmann]

Followup-For: Bug #1070429
Control: tag -1 patch pending

Hi,

I've just uploaded the attached patch to DELAYED/5. Please let me know
if I should delay it longer.


Andreas
diff -Nru libcapi20-3-3.27/debian/changelog libcapi20-3-3.27/debian/changelog
--- libcapi20-3-3.27/debian/changelog   2024-02-29 11:33:37.0 +0100
+++ libcapi20-3-3.27/debian/changelog   2024-05-30 13:55:52.0 +0200
@@ -1,3 +1,10 @@
+libcapi20-3 (1:3.27-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix documentation symlink after t64 rename.  (Closes: #1070429)
+
+ -- Andreas Beckmann   Thu, 30 May 2024 13:55:52 +0200
+
 libcapi20-3 (1:3.27-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libcapi20-3-3.27/debian/control libcapi20-3-3.27/debian/control
--- libcapi20-3-3.27/debian/control 2024-02-29 11:33:37.0 +0100
+++ libcapi20-3-3.27/debian/control 2024-05-30 13:06:56.0 +0200
@@ -4,7 +4,11 @@
 Maintainer: Rolf Leggewie 
 Uploaders: Jan-Michael Brummer 
 Standards-Version: 4.1.4
-Build-Depends: dpkg-dev (>= 1.22.5), debhelper (>= 9), dh-autoreconf
+Build-Depends:
+ debhelper (>= 9),
+ dh-autoreconf,
+# prevent accidental backports after the 64-bit time_t transition
+ dpkg-dev (>= 1.22.5),
 Homepage: http://www.isdn4linux.de
 Vcs-Browser: https://github.com/leggewie-DM/libcapi20
 Vcs-Git: g...@github.com:leggewie-DM/libcapi20.git
diff -Nru libcapi20-3-3.27/debian/copyright libcapi20-3-3.27/debian/copyright
--- libcapi20-3-3.27/debian/copyright   2018-04-15 14:19:12.0 +0200
+++ libcapi20-3-3.27/debian/copyright   2024-05-30 13:46:39.0 +0200
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Source: http://git.misdn.eu/?p=projects/isdn4k-utils.git
 
 Files: *
diff -Nru libcapi20-3-3.27/debian/libcapi20-dev.links 
libcapi20-3-3.27/debian/libcapi20-dev.links
--- libcapi20-3-3.27/debian/libcapi20-dev.links 2014-04-25 08:50:57.0 
+0200
+++ libcapi20-3-3.27/debian/libcapi20-dev.links 2024-05-30 13:01:55.0 
+0200
@@ -1 +1 @@
-usr/share/doc/libcapi20-3 usr/share/doc/libcapi20-dev
+usr/share/doc/libcapi20-3t64 usr/share/doc/libcapi20-dev

Bug#1072215: USB wireless Netgear WNA1100 fails to load

[Tom Overlund]

Package: installation-reports

Boot method: Netboot over TFTP
Image version: Debian version: 12 (bookworm); Installer build: 
20230607+deb12u5; URLs: 
https://deb.debian.org/debian/dists/bookworm/main/installer-amd64/current/images/netboot/netboot.tar.gz
 + https://cdimage.debian.org/cdimage/firmware/bookworm/current/firmware.cpio.gz
Date: May 29 ~9:30am

Machine: Generic desktop PC
Processor: AMD Athlon 200GE
Memory: 16GB
Partitions: Not applicable

Output of lspci -knn (or lspci -nn):

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Root Complex [1022:15d0]
Subsystem: ASRock Incorporation Raven/Raven2 Root Complex [1849:15d0]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 
[1022:15d1]
Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 
[1022:15d1]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe 
GPP Bridge [6:0] [1022:15d3]
Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP 
Bridge [6:0] [1022:1453]
Kernel driver in use: pcieport
00:01.6 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe 
GPP Bridge [6:0] [1022:15d3]
Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP 
Bridge [6:0] [1022:1453]
Kernel driver in use: pcieport
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Internal PCIe GPP Bridge 0 to Bus A [1022:15db]
Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal 
PCIe GPP Bridge 0 to Bus A [1022:]
Kernel driver in use: pcieport
00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Internal PCIe GPP Bridge 0 to Bus B [1022:15dc]
Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal 
PCIe GPP Bridge 0 to Bus B [1022:]
Kernel driver in use: pcieport
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 61)
Subsystem: ASRock Incorporation FCH SMBus Controller [1849:790b]
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge 
[1022:790e] (rev 51)
Subsystem: ASRock Incorporation FCH LPC Bridge [1849:790e]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 0 [1022:15e8]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 1 [1022:15e9]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 2 [1022:15ea]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 3 [1022:15eb]
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 4 [1022:15ec]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 5 [1022:15ed]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 6 [1022:15ee]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 
Device 24: Function 7 [1022:15ef]
15:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset USB 3.1 xHCI Compliant Host Controller [1022:43d5] (rev 01)
Subsystem: ASRock Incorporation 400 Series Chipset USB 3.1 xHCI 
Compliant Host Controller [1849:43d0]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
15:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset SATA Controller [1022:43c8] (rev 01)
Subsystem: ASRock Incorporation 400 Series Chipset SATA Controller 
[1849:43c8]
Kernel driver in use: ahci
Kernel modules: ahci
15:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset PCIe Bridge [1022:43c6] (rev 01)
Subsystem: ASRock Incorporation 400 Series Chipset PCIe Bridge 
[1849:43c6]
Kernel driver in use: pcieport
1d:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset PCIe Port [1022:43c7] (rev 01)
Subsystem: ASRock Incorporation 400 Series Chipset PCIe Port [1849:43c7]
Kernel driver in use: pcieport
1d:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset PCIe Port [1022:43c7] (rev 01)
Subsystem: ASRock Incorporation 400 Series Chipset PCIe Port [1849:43c7]
Kernel driver in use: pcieport
1d:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series 
Chipset PCIe Port [1022:43c7] (rev 01)
Subsystem: ASRock 

Bug#1057282: linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel upgrade makes systems unresponsive

[Ben Hutchings]

On Thu, 2024-05-16 at 08:09 +0200, Paul Gevers wrote:
> Hi Ben (and all the rest),
> 
> On 15-05-2024 9:56 p.m., Ben Hutchings wrote:
> > Apologies for leaving this bug for so long.
> 
> NP, part of live I guess.
> 
> > Is this bug still occurring?
> 
> I don't know. The problem was severe enough for us to abandon the idea 
> of running the backport kernels on our arm64 hosts, so we went back to 
> the stable kernel there.
> 
> > I had a look for possibly related fixes,
> > and found:
> > 
> > commit 22e111ed6c83dcde3037fc81176012721bc34c0b
> 
> [...]
> 
> > The fix went into
> > 6.8-rc1 and was backported to 6.6.15, so Debian versions 6.6.15-1
> > onward should have it.
> 
> > commit a8b0026847b8c43445c921ad2c85521c92eb175f
> 
> [...]
> 
> > which went into 6.8 but was *not* backported.
> 
> If you think it worth enough knowing if either is the case, I can 
> install the backports kernel again on the arm64 hosts, but obviously 
> that will be annoying for us. Please let me know if I should pursue this 
> (I would be expecting a bit quicker turn around on this bug if you say 
> yes now ;) ).

If you can test with the unstable kernel that would be great.  If you
are limited to only stable and backports, then you should probably wait
until 6.8 is in backports rather than testing the current 6.7 backport
that has only one of the fixes.

> > If the bug is still occurring, can you say what type of filesystem
> > rsync is being run on?
> 
> I'm not sure if this is the answer you're looking for, we use ext4.

Yes that's what I meant.

Ben.

-- 
Ben Hutchings
It is easier to write an incorrect program
than to understand a correct one.



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

Bug#1072214: python3-proto-plus declares Conflicts: nanopb in violation of Debian policy 10.1

[Helmut Grohne]

Package: python3-proto-plus
Version: 1.23.0-2
Severity: serious
Justification: policy 10.1

python3-proto-plus declares a conflict with nanopb. Doing so violates
Debian policy section 10.1. More background can be found in #1072073.

Helmut

Bug#1072212: ripgrep: bash tab completion not working

[Dagfinn Ilmari Mannsåker]

Package: ripgrep
Version: 14.1.0-1
Severity: normal
X-Debbugs-Cc: ilm...@ilmari.org

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

When hitting tab after `rg` in bash, no options are offered, only file
names.  This is because the bash completion file
/usr/share/bash-completion/completions/ripgrep just contains the line:

debian/cargo_out_dir/rg.bash rg

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable'), (90, 'testing'), (80, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages ripgrep depends on:
ii  libc6 2.36-9+deb12u7
ii  libgcc-s1 12.2.0-14
ii  libpcre2-8-0  10.42-1

ripgrep recommends no packages.

ripgrep suggests no packages.

-- no debconf information

Bug#1072211: texlive-base: pdflatex very slow after upgrading to texlive 2024.20240401-2

[J.L.G. Pallero]

Package: texlive-base
Version: 2024.20240401-2
Severity: normal
X-Debbugs-Cc: jgpall...@gmail.com

Dear Maintainer,

After the last upgrade of texlive packages in Sid, from 2023.20240207-1 to 
2024.20240401-2, I found pdflatex very slow in the compilation. The same 
documents
compiled with the 2023.20240207-1 version were bult quicker. Is it a problem on 
my side or is a generalbehavior?


-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-rw-r-- 1 root staff 80 May 25  2023 /usr/local/share/texmf/ls-R
-rw-r--r-- 1 root root 2079 May 27 22:08 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Oct 12  2022 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 May 26 16:01 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 May 26 16:01 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Oct 13  2022 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 May 26 16:01 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 May 26 16:01 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 3512 May 27 22:06 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Feb 22  2016 mktex.cnf
-rw-r--r-- 1 root root 475 Oct 13  2022 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-base depends on:
ii  debconf [debconf-2.0]  1.5.86
ii  libpaper-utils 1.1.29+b1
ii  sensible-utils 0.0.22
ii  tex-common 6.18
ii  texlive-binaries   2024.20240313.70630+ds-2
ii  ucf3.0043+nmu1
ii  xdg-utils  1.1.3-4.1

Versions of packages texlive-base recommends:
ii  lmodern  2.005-1

Versions of packages texlive-base suggests:
ii  ghostscript [postscript-viewer]  10.03.1~dfsg-1
ii  gv [postscript-viewer]   1:3.7.4-2+b2
ii  okular [postscript-viewer]   4:23.08.1-2+b1
ii  perl-tk  1:804.036+dfsg1-2+b1
ii  xpdf [pdf-viewer]3.04+git20240202-1+b2
pn  xzdec

Versions of packages tex-common depends on:
ii  ucf  3.0043+nmu1

Versions of packages tex-common suggests:
ii  debhelper  13.15.3

Versions of packages texlive-base is related to:
ii  tex-common6.18
ii  texlive-binaries  2024.20240313.70630+ds-2

-- debconf information:
  texlive-base/binary_chooser: pdftex, dvips, dvipdfmx, xdvi
  texlive-base/texconfig_ignorant:

Bug#1068017: Y2038-safe replacements for utmp/wtmp and lastlog

[Vincent Lefevre]

On 2024-05-08 16:53:53 +0800, Jun MO wrote:
> For last(1) my concern is that it will be helped to keep the original
> last(1) for back-compatibility to read old wtmp files.

I agree, this may be useful. Unfortunately, the current status is
that one cannot have both: installing wtmpdb forces the upgrade of
util-linux to 2.40.1-3 (at least), where "last" is no longer installed.

However, I think that it is better to archive human-readable text files
(generated by "last" in the past) rather than the wtmp files.

I've used the attached script to get both the IP addresses and the
host names with "last" (I don't know whether there's a better way to
get full information).

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

# Output wtmp logs, based on command 'last' from util-linux.
# This command is called twice:
#   1. without the -d option;
#   2. with the -d option to get the host names.

use strict;

my ($proc) = '$Id: lastf 103313 2017-11-06 01:47:30Z vinc17/joooj $'
  =~ /^.Id: (\S+) \d+ / or die;

@ARGV == 1 or $! = 1, die "Usage: $proc \n";
-f $ARGV[0] or $! = 1, die "$proc: $ARGV[0] is not a regular file\n";
-r $ARGV[0] or $! = 1, die "$proc: $ARGV[0] is not a readable file\n";

sub rdlog ($@)
  {
my $file = shift;
open LAST, '-|', 'last', @_, '-axf', $file
  or die "$proc: can't exec 'last': $!";
my @t = ;
close LAST, or die "$proc: 'last' failed: $!";
$t[-1] =~ / begins / && $t[-2] eq "\n"
  or $! = 2, die "$proc: bad format";
return @t;
  }

my @t1 = rdlog $ARGV[0];
my @t2 = rdlog $ARGV[0], '-d';
$#t1 == $#t2 or $! = 1, die "$proc: bad length ($#t1 vs $#t2)\n";
$t1[-1] eq $t2[-1] or die $! = 1, die "$proc: inconsistent last line\n";

foreach my $i (0..$#t1-2)
  {
$_ = $t1[$i];
chomp;
my ($u1) = /^(.){60}/
  or $! = 2, die "$proc: bad format";
my ($u2,$v2) = $t2[$i] =~ /^(.){60}(.*)$/
  or $! = 2, die "$proc: bad format";
$u1 eq $u2 or $! = 2, die "$proc: bad format";
$v2 eq '0.0.0.0' or $_ .= " ($v2)";
print "$_\n";
  }

print "\n$t1[-1]";

Bug#1061429: tomboy-ng: Copy and paste to/from tomboy-ng does not work under (at least) GNOME

[David Bannon]

Konrad, sorry, very sorry. This message poped up in my Spam folder, I 
only just saw it today. So, earlier today I sent you, and the Debian bug 
system, a message saying I cannot replicate (and can you help me 
reproduce it). If you see that message, please disregard it !


(I suspect Thunderbird refuses to respond to what it considers Spam, OK 
if it tells me!).


Anyway, a real answer. I am afraid this is yet another Wayland/Qt5/6 
problem.


You have a couple of choices -

* If you use the gtk2 version of tomboy-ng, then it works fine. Please 
consider https://github.com/tomboy-notes/tomboy-ng/releases, the package 
without either "Qt5" or "Qt6" is what you need. My test on U2404 Gnome 
indicates no extra dependencies are needed.


* Switch you system back to X11 from Wayland. You may be surprised at 
the number of other things that suddenly start to work !  Logout, from 
the login screen, select your name, lower left there is a now gear 
symbol, click and select the only non-wayland option. Log back in again.


* Change your desktop to a user friendly one, Mate, xfce, Cinnamon, 
Budgie etc.


I suggest one of the above because its going to take me some time to 
track down the actual cause of this problem, if I am right and its 
Qt/Wayland related, even longer to get it fixed !  Maybe, we will be 
lucky and its a known issue with a know fix but even that will take some 
time to establish. If we are really lucky, its in my code but don't hold 
your breath.


*Konrad, please answer direct to me or log an issue* at 
https://github.com/tomboy-notes/tomboy-ng/issues - I don't know whats 
happening with my account at Debian but right now, but I have other 
things on my plate.


Debian is a fabulous organisation with really great people but their 
infrastructure is not very user friendly !


Again, sorry for the slow response.

Davo



On 18/4/24 04:43, Konrad Schwenke wrote:

Dear David,
I can confirm that I have the same issue with copy-pasting. It appears
to be universal, copying from tomboy-ng to any other application fails
when using ctl+v or the right-click menu for inserting. However, via the
middle mouse button it is possible to paste.

I'm on Ubuntu 23.10 and tomboy is on 0.36a-2.

Kind regards,
Konrad

Bug#1071336: psensor: FTBFS: FAIL test-cppcheck.sh

[Santiago Vila]

reopen 1071336
thanks

El 30/5/24 a las 11:15, xiao sheng wen(肖盛文) escribió:

psensor can build success now:

https://buildd.debian.org/status/fetch.php?pkg=psensor=amd64=1.1.5-1.4%2Bb1=1710303742=0


No, that was 78 days ago.

The build failure started to happen recently, this is my build history:

Status: successful  psensor_1.1.5-1.4_amd64-20231202T192345.966Z
Status: successful  psensor_1.1.5-1.4_amd64-20240203T112315.059Z
Status: successful  psensor_1.1.5-1.4_amd64-20240403T000658.536Z
Status: failed  psensor_1.1.5-1.4_amd64-20240516T030926.907Z
Status: failed  psensor_1.1.5-1.4_amd64-20240517T142601.292Z
Status: failed  psensor_1.1.5-1.4_amd64-20240517T142937.321Z
Status: failed  psensor_1.1.5-1.4_amd64-20240517T172010.206Z
Status: failed  psensor_1.1.5-1.4_amd64-20240517T172503.575Z

Moreover, it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/psensor.html

Thanks.

Bug#1072210: fontconfig-config: leaves broken symlink after purge: /etc/fonts/conf.d/70-no-bitmaps-except-emoji.conf -> /usr/share/fontconfig/conf.avail/70-no-bitmaps-except-emoji.conf

[Andreas Beckmann]

Package: fontconfig-config
Version: 2.15.0-1.1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package.postinst creates
a symlink that is left over as a broken symlink after purge.

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

0m24.7s ERROR: FAIL: Broken symlinks:
  /etc/fonts/conf.d/70-no-bitmaps-except-emoji.conf -> 
/usr/share/fontconfig/conf.avail/70-no-bitmaps-except-emoji.conf


Looks like 70-no-bitmaps-except-emoji.conf is missing from the cleanup
list in fontconfig-config.postrm.


This affects around 11000 packages (transitively) depending on
fontconfig-config and thus renders piuparts tests checking for such
broken links much less useful.


cheers,

Andreas


fontconfig-config_2.15.0-1.1.log.gz
Description: application/gzip

Bug#1072209: slurm-wlm-contrib: uninstallable in sid

[Gianfranco Costamagna]

Package: slurm-wlm-contrib
Version: 23.11.7-1
Severity: Serious


Hello, can you please also consider relaxing a bit the dependency between them?
I'm not even sure if they are compatible or not, this is why I'm not tagging 
"patch"

diff -Nru slurm-wlm-contrib-23.11.7/debian/control 
slurm-wlm-contrib-23.11.7/debian/control
--- slurm-wlm-contrib-23.11.7/debian/control2024-05-22 23:24:00.0 
+0200
+++ slurm-wlm-contrib-23.11.7/debian/control2024-05-30 10:12:16.0 
+0200
@@ -46,8 +46,8 @@
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
- slurm-wlm-basic-plugins (= 23.02.3-2)
-Enhances: slurmd (= 23.02.3-2)
+ slurm-wlm-basic-plugins (= 23.11.7-1)
+Enhances: slurmd (= 23.11.7-1)
 Description: SLURM NVML plugins
  SLURM, the Simple Linux Utility for Resource Management,
  is an open-source cluster resource management and job scheduling.
@@ -60,7 +60,7 @@
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
- slurm-wlm-basic-plugins-dev (= 23.02.3-2),
+ slurm-wlm-basic-plugins-dev (= 23.11.7-1),
  slurm-wlm-nvml-plugin (= ${binary:Version}),
  libnvidia-ml-dev,
 Description: SLURM NVML plugin development files





OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1072208: ITP: python-coriolisclient -- client bindings and cli to the Coriolis migration API

[Thomas Goirand]

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

* Package name: python-coriolisclient
  Version : 1.0.9
  Upstream Contact: Cloudbase Solutions Srl 
* URL : https://github.com/cloudbase/python-coriolisclient
* License : Apache-2.0
  Programming Lang: Python
  Description : client bindings and cli to the Coriolis migration API

 The Coriolis command-line API offers an interface over the REST API provided
 by the Coriolis migration service.
 .
 This package contains the a client for the Coriolis API. There's a Python API
 (the "coriolisclient" module), and a command-line script ("coriolis").

Bug#1072207: click: fails to upgrade from bookworm: prerm fails to run click

[Andreas Beckmann]

Package: click
Version: 0.5.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'bookworm'.
It installed fine in 'bookworm', then the upgrade to 'trixie' fails.

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

  Preparing to unpack .../06-click_0.5.2-3_amd64.deb ...
  Traceback (most recent call last):
File "/usr/bin/click", line 31, in 
  import gi
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 40, in 
  from . import _gi
  ImportError: /lib/x86_64-linux-gnu/libgirepository-1.0.so.1: undefined 
symbol: g_once_init_leave_pointer
  dpkg: warning: old click package pre-removal script subprocess returned error 
exit status 1
  dpkg: trying script from the new package instead ...
  Traceback (most recent call last):
File "/usr/bin/click", line 31, in 
  import gi
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 40, in 
  from . import _gi
  ImportError: /lib/x86_64-linux-gnu/libgirepository-1.0.so.1: undefined 
symbol: g_once_init_leave_pointer
  dpkg: error processing archive 
/tmp/apt-dpkg-install-7xvYff/06-click_0.5.2-3_amd64.deb (--unpack):
   new click package pre-removal script subprocess returned error exit status 1


The .prerm calls 'click hook remove click-desktop' which fails because
python3-gi is temporarily not usable (because libglib2.0-0t64 is not yet
unpacked).
Do you really need to run that command in the 'upgrade' case? Or could
that be restricted to 'remove' (and 'purge')?


cheers,

Andreas

PS: please use 'command -v' instead of 'which'


click_0.5.2-3.log.gz
Description: application/gzip

Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)

[Thorsten Leemhuis]

On 29.05.24 23:12, Emanuele Rocca wrote:
> On 2024-05-27 02:31, Thorsten Leemhuis wrote:
>> Would also help a lot to know if this is a 6.8.y only thing, or happens
>> with 6.9 and mainline as well, as 6.8.y will likely be EOLed soon.
> 
> I could reproduce the issue with 6.9.2 too, will try mainline tomorrow.

Good to know, thx!

> FTR the procedure is quite simple. [...]

Don't tell me (I'm just a man-in-the-middle for triaging here and not a
developer for that code), tell David in a reply to
https://lore.kernel.org/all/531994.1716450...@warthog.procyon.org.uk/ –
ideally while answering his question. He needs to know about this.

Ciao, Thorsten

Bug#1068165: (no subject)

[wuruilong]

Dear Maintainer,

This patch has been merged upstream, please upgrade the version or merge 
the attached patch. The link to merge the PR is as follows: 
https://github.com/gamelinux/prads/pull/56


wuruilong

Bug#1054090: zram-tools: diff for NMU version 0.3.3.1-1.2

[Jonathan Carter]

Hi

On 2024/05/30 02:52, Chris Hofstaedtler wrote:

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


Since this is maintained under /debian (which is basically our 
collab-maint now), please push the changes [there] and just go ahead and 
upload it without any needed delay.


thanks a lot!

-Jonathan

[there] https://salsa.debian.org/debian/zram-tools

Bug#1072183: fenics-dolfinx: FTBFS with nanobind 2.0

[Gianfranco Costamagna]

Hello, I'm attaching a patch that applies cleanly.
I'm testing the build

G.

On Wed, 29 May 2024 23:31:23 +0200 =?utf-8?q?Timo_R=C3=B6hling?= 
 wrote:

Source: fenics-dolfinx
Version: 1:0.8.0-6
Severity: serious
Tags: patch

Dear maintainer,

upgrading to nanobind 2.0 made your package FTBFS. I am sorry that I did not 
check this before uploading to unstable, that is on me. I have seen that 
Francesco has already fixed the issue upstream [1]. Depending on how far away 
the next upstream release is, maybe you can backport that fix?



Cheers
Timo

[1] 
https://github.com/FEniCS/dolfinx/commit/42c43485e81ada306f0b3f1dc735d95539174cbc





diff -Nru fenics-dolfinx-0.8.0/debian/changelog 
fenics-dolfinx-0.8.0/debian/changelog
--- fenics-dolfinx-0.8.0/debian/changelog   2024-05-12 11:17:08.0 
+0200
+++ fenics-dolfinx-0.8.0/debian/changelog   2024-05-30 11:05:39.0 
+0200
@@ -1,3 +1,10 @@
+fenics-dolfinx (1:0.8.0-6ubuntu1) oracular; urgency=medium
+
+  * debian/patches/42c43485e81ada306f0b3f1dc735d95539174cbc.patch:
+- upstream fix for newer nanobind 2.0 (Closes: #1072183)
+
+ -- Gianfranco Costamagna   Thu, 30 May 2024 
11:05:39 +0200
+
 fenics-dolfinx (1:0.8.0-6) unstable; urgency=medium
 
   * debian patch Newton_KSP_ref_counter_PR3190.patch applies upstream
diff -Nru fenics-dolfinx-0.8.0/debian/control 
fenics-dolfinx-0.8.0/debian/control
--- fenics-dolfinx-0.8.0/debian/control 2024-05-12 11:17:08.0 +0200
+++ fenics-dolfinx-0.8.0/debian/control 2024-05-30 11:05:39.0 +0200
@@ -1,7 +1,8 @@
 Source: fenics-dolfinx
 Section: math
 Priority: optional
-Maintainer: Debian Science Team 

+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Debian Science Team 

 Uploaders:
  Drew Parsons ,
  Francesco Ballarin 
diff -Nru 
fenics-dolfinx-0.8.0/debian/patches/42c43485e81ada306f0b3f1dc735d95539174cbc.patch
 
fenics-dolfinx-0.8.0/debian/patches/42c43485e81ada306f0b3f1dc735d95539174cbc.patch
--- 
fenics-dolfinx-0.8.0/debian/patches/42c43485e81ada306f0b3f1dc735d95539174cbc.patch
  1970-01-01 01:00:00.0 +0100
+++ 
fenics-dolfinx-0.8.0/debian/patches/42c43485e81ada306f0b3f1dc735d95539174cbc.patch
  2024-05-30 11:05:39.0 +0200
@@ -0,0 +1,495 @@
+From 42c43485e81ada306f0b3f1dc735d95539174cbc Mon Sep 17 00:00:00 2001
+From: Francesco Ballarin 
+Date: Fri, 24 May 2024 09:02:41 +0200
+Subject: [PATCH] Replace `nb::any` with -1 and add argument to `nb::ndarray`
+ in preparation of next nanobind release (#3105)
+
+* Replace nb::any with -1 in preparation of next nanobind release
+
+* nb::ndarray now requires to pass in the owner argument, which used to have a 
default value. Assign the former defaul value everywhere in nb wrappers
+
+* DROP BEFORE MERGE: install nanobind from source in workflows
+
+* CI update
+
+* Bump min nanobind version
+
+* CI udpates
+
+* System install
+
+* pip install system
+
+* Remove CI change
+
+* More updates
+
+* cmake update
+
+* Run clang-format
+
+-
+
+Co-authored-by: Garth N. Wells 
+---
+ .github/workflows/ccpp.yml | 14 --
+ .github/workflows/conda.yml|  1 -
+ .github/workflows/oneapi.yml   |  6 +++-
+ .github/workflows/redhat.yml   |  7 +++--
+ cpp/cmake/templates/DOLFINXConfig.cmake.in |  2 +-
+ docker/Dockerfile.test-env |  2 +-
+ python/build-requirements.txt  |  2 +-
+ python/dolfinx/wrappers/assemble.cpp   | 13 +
+ python/dolfinx/wrappers/common.cpp |  6 ++--
+ python/dolfinx/wrappers/fem.cpp| 30 ++--
+ python/dolfinx/wrappers/geometry.cpp   | 17 +++-
+ python/dolfinx/wrappers/graph.cpp  |  9 +++---
+ python/dolfinx/wrappers/la.cpp | 17 ++--
+ python/dolfinx/wrappers/log.cpp|  5 ++--
+ python/dolfinx/wrappers/mesh.cpp   | 32 --
+ python/pyproject.toml  |  2 +-
+ 16 files changed, 94 insertions(+), 71 deletions(-)
+
+diff --git a/cpp/cmake/templates/DOLFINXConfig.cmake.in 
b/cpp/cmake/templates/DOLFINXConfig.cmake.in
+index 5e22232d333..dfcf1eaa81d 100644
+--- a/cpp/cmake/templates/DOLFINXConfig.cmake.in
 b/cpp/cmake/templates/DOLFINXConfig.cmake.in
+@@ -18,7 +18,7 @@ if(DEFINED ENV{BOOST_ROOT} OR DEFINED BOOST_ROOT)
+ endif()
+ set(Boost_USE_MULTITHREADED $ENV{BOOST_USE_MULTITHREADED})
+ set(Boost_VERBOSE TRUE)
+-find_dependency(Boost 1.70 REQUIRED COMPONENTS timer filesystem)
++find_dependency(Boost 1.70 REQUIRED COMPONENTS timer)
+ 
+ if(@ufcx_FOUND@)
+   find_dependency(ufcx)
+diff --git a/python/dolfinx/wrappers/assemble.cpp 
b/python/dolfinx/wrappers/assemble.cpp
+index fb4460b49aa..7dc07803e07 100644
+--- a/python/dolfinx/wrappers/assemble.cpp
 b/python/dolfinx/wrappers/assemble.cpp
+@@ -362,12 +362,13 @@ void declare_assembly_functions(nb::module_& m)
+ std::span cols,
+ std::span data)
+ {
+-  return 

Bug#1026898: [External] Re: Bug#1026898: deprecate QUOTAUSER post-bookworm

[Marc Haber]

Hi,

On Wed, May 29, 2024 at 04:41:04PM +, Merlin Hansen wrote:
> Unfortunately I have no experience in creating test cases for a package 
> build. However, point me in a direction where I can learn and I'm willing to 
> look into the feasibility of contributing.

The current test cases are available as example in the source package.
Do apt source adduser and look in debian/tests/f.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1072205: prevent re-using package versions for NMUs

[Johannes Schauer Marin Rodrigues]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
User: reproducible-bui...@lists.alioth.debian.org
Usertags: infrastructure
User: ftp.debian@packages.debian.org
Usertags: dak

Hi,

the binary package bash 5.2.15-2+b3 was uploaded to the archive twice. Once to
bookworm and once to sid but with differing content. Here is a diff of their
d/changelog:

@@ -1,6 +1,6 @@
-bash (5.2.15-2+b3) bookworm; urgency=low, binary-only=yes
+bash (5.2.15-2+b3) sid; urgency=low, binary-only=yes
 
   * Binary-only non-maintainer upload for arm64; no source changes.
   * Rebuild for outdated Built-Using (glibc/2.36-9)
 
- -- arm Build Daemon (arm-ubc-03)   
Fri, 29 Mar 2024 13:22:36 +
+ -- arm Build Daemon (arm-ubc-02)   
Thu, 13 Jul 2023 09:12:53 +

This is not only confusing for apt (it will not be able to figure out which of
the two is installed because dpkg does not keep track of package hashes) but it
is also problematic for reproducible builds because the buildinfo file records
packages by their name/architecture/version tuple and relies on those to be
unique throughout the history of Debian.

This example with bash is especially problematic since bash is Essential:yes so
there will now be a large portion of buildinfo files where it is not possible
to figure out with which of the two differing bash packages the sources were
compiled.

snapshot.d.o also shows the issue and could probably be used to get an idea how
many packages are affected:

http://snapshot.debian.org/package/bash/5.2.15-2/#bash_5.2.15-2:2b:b3

Maybe this issue is blocked by #620356?

Thanks!

cheers, josch

Bug#1071378: [REGRESSION] commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 (Linux 6.7+) crashes during boot

[Linux regression tracking (Thorsten Leemhuis)]

On 30.05.24 10:45, Jörn Heusipp wrote:
> 
> On 30/05/2024 09:27, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 30.05.24 08:55, Jörn Heusipp wrote:
>>> commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 ("x86/sev-es: Set
>>> x86_virt_bits to the correct value straight away, instead of a two-phase
>>> approach") crashes during boot for me on this 32bit x86 system.
>>
>> FWIW, not my area of expertise, but there is a patch from Dave with a
>> Fixes: tag for your culprit up for review:
>> https://lore.kernel.org/all/20240517200534.8ec5f...@davehans-spike.ostc.intel.com/
> 
> That did not apply cleanly to 6.10-rc1,

Maybe something changed since then.

> but I figured it out manually. I
> can confirm that it fixes the issue.

Cool. Guess Dave in that case might be happy about a "Tested-by" tag
from you:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

#regzbot dup:
https://lore.kernel.org/all/20240516173928.3960193-1-andriy.shevche...@linux.intel.com/
#regzbot fix: x86/cpu: Provide default cache line size if not enumerated
#regzbot related:
https://lore.kernel.org/all/20240517200534.8ec5f...@davehans-spike.ostc.intel.com/

Bug#1071378: [REGRESSION] commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 (Linux 6.7+) crashes during boot

[Jörn Heusipp]

Hello!

On 30/05/2024 09:27, Linux regression tracking (Thorsten Leemhuis) wrote:

On 30.05.24 08:55, Jörn Heusipp wrote:



commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 ("x86/sev-es: Set
x86_virt_bits to the correct value straight away, instead of a two-phase
approach") crashes during boot for me on this 32bit x86 system.


FWIW, not my area of expertise, but there is a patch from Dave with a
Fixes: tag for your culprit up for review:
https://lore.kernel.org/all/20240517200534.8ec5f...@davehans-spike.ostc.intel.com/


That did not apply cleanly to 6.10-rc1, but I figured it out manually. I
can confirm that it fixes the issue.

Best regards,
Jörn

Bug#1072201: rtags: autopkgtest failure due to missing depends on emacs

[Xiyue Deng]

Control: tags -1 patch pending

Xiyue Deng  writes:

> Package: rtags
> Version: 2.38-10
> Severity: serious
>
> Dear Maintainer,
>
> rtags is now failing autopkgtest due to missing dependency on emacs.
> See the autopkgtest regression test from flycheck[1].  It used to work
> because it pulls in emacs through the dependency of flycheck.  The
> recent upload of flycheck 34.1-1 has downgraded this dependency to
> recommends (by me, actually) which triggered this failure.  As this is
> causing build failure on rebuild, I'm using the serious severity.
>
> I'll prepare a fix patch/MR soon.
>
> [1] https://ci.debian.net/packages/r/rtags/testing/amd64/47083927/
>
> -- System Information:
> Debian Release: 12.5
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
> 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.1.0-21-amd64 (SMP w/16 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

As I have team repo access, I have pushed the fix[1] and it has passed
autopkgtest on Salsa CI[2].

[1] 
https://salsa.debian.org/emacsen-team/rtags/-/commit/af72d9a977846760ce7b21de36955e4083a34a68
[2] https://salsa.debian.org/emacsen-team/rtags/-/jobs/5789916

-- 
Xiyue Deng

Bug#966621: Make /tmp/ a tmpfs and cleanup /var/tmp/ on a timer by default [was: Re: systemd: tmpfiles.d not cleaning /var/tmp by default]

[Peter Pentchev]

On Thu, May 30, 2024 at 08:35:47AM +0200, Johannes Schauer Marin Rodrigues 
wrote:
> Hi,
> 
> Quoting Luca Boccassi (2024-05-28 01:54:08)
> > Thanks for the useful input, the following has been done:
> > 
> > - existing installations pre-trixie will get an orphaned tmpfiles.d in
> > /etc/ that keeps the existing behaviour unchanged (no cleanup of
> > /var/tmp)
> > - openssh and tmux have been fixed to provide a tmpfiles.d exception
> > to retain their respective files
> > - the /tmp/ description in debian-installer has been updated to note
> > it is a tmpfs by default (via a commit in partman-basicfilesystems,
> > will upload if nobody gets around to it before Trixie's freeze)
> > - two paragraphs have been provided for the release notes ticket
> > - the changes are also noted in NEWS, with instructions on how to
> > override locally
> > - as mentioned, the latest upload to unstable makes /tmp/ a tmpfs by
> > default and for new installations 10+ days old files in /tmp/ and 30+ days
> > old files in /var/tmp/ are cleaned up daily
> 
> thank you for having discussed this change on d-devel and for adding
> documentation to NEWS and release notes to announce this change. I also think
> it is sensible to roll this only out on new installations and to keep the
> behaviour on existing setups. Thank you for implementing that as well.
> 
> That being said, maybe some Perl wizard knows how to do a flock on a directory
> in Perl?

I wouldn't call myself a Perl wizard by a long stretch, but I can give it a try 
:)

>  I tried this:
> 
> use Fcntl qw(LOCK_EX);
> opendir(my $handle, ".") or die "opendir: $!";
[snip]

Here lies your problem. The flock(2) syscall works on file descriptors,
the things returned by open(2), not on the dirent structures returned by
opendir(3). So you need something like this:

use v5.10;  # I really should switch to at least 5.16 if not 5.24
use strict;
use warnings;

use Fcntl qw(O_RDONLY O_DIRECTORY LOCK_EX);

my $dirname = "/tmp/to-be-locked";
sysopen(my $handle, "/tmp/to-be-locked", O_RDONLY | O_DIRECTORY) or
die "Could not open $dirname: $!\n";
flock($handle, LOCK_EX) or
die "Could not lock $dirname: $!\n";

say "locked, it seems";
sleep(3600);'

I only put the sleep() part so I could check using lsof that
the directory was indeed locked. And yeah, the v5.10 part is a leftover
from the days (...until a month or two ago...) when I still had to
support stock CentOS 7 systems; I really should train my fingers to
put 5.24 there.

Hope that helps!

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org pe...@morpheusly.com
PGP key:https://www.ringlet.net/roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#1070322: still an issue in trixie

[Andreas B. Mundt]

Control: reopen -1
Control: notfixed -1 kio/5.115.0-6


Hi again,

some more tests with trixie.  I mounted a samba share and in
comparision a ksmbd share.  Long story short: ark still fails for the
samba share.  The ksmbd share seems to work as expected:

-- samba mount (note the 'Links: X', file disappears)

ansible@trixie:~$ ls -l $FILE
ls: cannot access '/media/samba/test.tar.gz': No such file or directory

ansible@trixie:~$ ark --add-to $FILE 
/usr/share/images/desktop-base/desktop-grub.png && stat $FILE
  File: /media/samba/test.tar.gz
  Size: 147 Blocks: 1  IO Block: 1048576 regular file
Device: 0,52Inode: 924164  Links: 1
Access: (0755/-rwxr-xr-x)  Uid: ( 1000/ ansible)   Gid: ( 1000/ ansible)
Access: 2024-05-30 09:42:30.891533000 +0200
Modify: 2024-05-30 09:42:30.906949700 +0200
Change: 2024-05-30 09:42:30.906949700 +0200
 Birth: 2024-05-30 09:42:30.891533000 +0200

ansible@trixie:~$ ls -l $FILE
-rwxr-xr-x 1 ansible ansible 147 May 30 09:42 /media/samba/test.tar.gz

ansible@trixie:~$ ark --add-to $FILE 
/usr/share/images/desktop-base/desktop-grub.png && stat $FILE
  File: /media/samba/test.tar.gz
  Size: 147 Blocks: 8  IO Block: 1048576 regular file
Device: 0,52Inode: 924164  Links: 0
Access: (0755/-rwxr-xr-x)  Uid: ( 1000/ ansible)   Gid: ( 1000/ ansible)
Access: 2024-05-30 09:42:39.643743300 +0200
Modify: 2024-05-30 09:42:30.906949700 +0200
Change: 2024-05-30 09:42:30.906949700 +0200
 Birth: 2024-05-30 09:42:30.891533000 +0200

ansible@trixie:~$ ls -l $FILE
ls: cannot access '/media/samba/test.tar.gz': No such file or directory

- ksmbd mount (looks fine)

ansible@trixie:~$ FILE=/media/ksmbd/test.tar.gz
ansible@trixie:~$ ark --add-to $FILE 
/usr/share/images/desktop-base/desktop-grub.png && stat $FILE
  File: /media/ksmbd/test.tar.gz
  Size: 5694Blocks: 16 IO Block: 1048576 regular file
Device: 0,53Inode: 391733  Links: 1
Access: (0755/-rwxr-xr-x)  Uid: ( 1000/ ansible)   Gid: ( 1000/ ansible)
Access: 2024-05-30 09:43:10.516972400 +0200
Modify: 2024-05-30 09:43:10.520972500 +0200
Change: 2024-05-30 09:43:10.520972500 +0200
 Birth: 2024-05-30 09:43:10.516972400 +0200

ansible@trixie:~$ ark --add-to $FILE 
/usr/share/images/desktop-base/desktop-grub.png && stat $FILE
  File: /media/ksmbd/test.tar.gz
  Size: 5694Blocks: 16 IO Block: 1048576 regular file
Device: 0,53Inode: 391734  Links: 1
Access: (0755/-rwxr-xr-x)  Uid: ( 1000/ ansible)   Gid: ( 1000/ ansible)
Access: 2024-05-30 09:43:13.885037800 +0200
Modify: 2024-05-30 09:43:13.885037800 +0200
Change: 2024-05-30 09:43:13.885037800 +0200
 Birth: 2024-05-30 09:43:13.885037800 +0200

ansible@trixie:~$ ls -l $FILE
-rwxr-xr-x 1 ansible ansible 5694 May 30 09:43 /media/ksmbd/test.tar.gz

Any ideas?  Again, find below some more information about the setup.

Best regards,

  Andi

--

ansible@trixie:~$ apt list kio
kio/testing,now 5.115.0-6 amd64 [installed,automatic]

mount:
//192.168.122.184/homes on /media/samba type cifs 
(rw,nosuid,nodev,relatime,vers=3.1.1,cache=strict,username=andi,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.122.184,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,nobrl,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1,user=ansible,user=andi)
//192.168.122.157/homedirs on /media/ksmbd type cifs 
(rw,nosuid,nodev,relatime,vers=3.1.1,cache=strict,username=smbuser,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.122.157,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,nobrl,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1,user=ansible,user=smbuser)

Bug#1072200: libllvm19: libLLVM.so.19.0 => not found

[Wentao Zhang]

On 2024-05-30 02:10, Sylvestre Ledru wrote:


Le 30/05/2024 à 07:16, Wentao Zhang a écrit :

Package: libllvm19
Version: 1:19~++20240529104944+a3f9066e99f3-1~exp1~20240529225109.743
Severity: normal

Hi,

Some library symlinks have changed and as a result:

$ ldd `which clang-19`
linux-vdso.so.1 (0x89cf)
libclang-cpp.so.19.0 => not found
libLLVM.so.19.0 => not found
libstdc++.so.6 => /lib/aarch64-linux-gnu/libstdc++.so.6 
(0x89a0)

libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x8996)
libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 
(0x89c4)

libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x897b)
/lib/ld-linux-aarch64.so.1 (0x89cb3000)

I guess for libLLVM we should port part of this commit [1] from branch 
"18" to
branch "snapshot". I'm still figuring out the needed changes for 
libclang-cpp.


Also, line #1 and line #3 in this file [2] seem conflicting? (only 
affecting

branch "18" though)

[1] 
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/f6c22777bc0687fc548343d3fa565656a1318a18
[2] 
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/blob/d5a73bd2c9551571084ccecf4307ef94e0b75d96/debian/libllvmX.Y.links.in

Thanks,
Wentao


Thanks

clang still works right ?


Yes. In my use cases I haven't encountered other problems.

Thanks,
Wentao



$ clang-19 --version
Debian clang version 19.0.0 (++20240529093513+2cfea14a57ad-1~exp1)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm-19/bin

Thanks

S

Bug#1071378: [REGRESSION] commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 (Linux 6.7+) crashes during boot

[Linux regression tracking (Thorsten Leemhuis)]

On 30.05.24 08:55, Jörn Heusipp wrote:
> 
> Hello x86 maintainers!
> 
> commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 ("x86/sev-es: Set
> x86_virt_bits to the correct value straight away, instead of a two-phase
> approach") crashes during boot for me on this 32bit x86 system.

FWIW, not my area of expertise, but there is a patch from Dave with a
Fixes: tag for your culprit up for review:
https://lore.kernel.org/all/20240517200534.8ec5f...@davehans-spike.ostc.intel.com/

Ciao, Thorsten

> Updating a Debian testing system resulted in a hang during boot before
> printing anything, with any 6.7 or later kernel. With 'earlyprintk=vga',
> I managed to capture the crash on video and stitched it together as an
> image [1].
> Trimmed transcription (might contain typos) of the crash from Debian
> kernel 6.7.12-1:
> ===
> BUG: kernel NULL pointer dereference, address: 0010
> #PF: supervisor write access in kernel mode
> #PF: error_code(0x0002) - not-present page
> Oops: 0002 [#1] PREEMPT SMP NOPTI
> [...]
> EIP: __ring_buffer_alloc+0x32/0x194
> [...]
> show_regs
> __die
> page_fault_oops
> kernelmode_fixup_or_oops.constprop
> __bad_area_nosemaphore.constprop
> bad_area_nosemaphore
> do_user_addr_fault
> prb_read_valid
> exc_page_fault
> pvclock_clocksource_read_nowd
> handle_exception
> pvclock_clocksource_read_nowd
> __ring_buffer_alloc
> pvclock_clocksource_read_nowd
> __ring_buffer_alloc
> early_trace_init
> start_kernel
> i386_start_kernel
> startup_32_smp
> [...]
> ===
> I could transcribe all of it or capture it again from latest git and
> decode the symbols, if truely really needed, but I figured the type of
> crash and the trace itself could maybe be sufficient. It looks identical
> to me for all later crashing kernel versions.
> 
> I bisected this down to commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6.
> 
> The kernel config [2] I used is 'make olddefconfig' based on Debian's
> config-6.8.11-686-pae [3].
> 
> I also tested 6.9.2 and 6.10-rc1, both also still crash in the same way.
> 
> cpuinfo:
> ===
> manx@caesar:~$ cat /proc/cpuinfo
> processor   : 0
> vendor_id   : AuthenticAMD
> cpu family  : 6
> model   : 8
> model name  : AMD Duron(tm)
> stepping    : 1
> cpu MHz : 1798.331
> cache size  : 64 KB
> physical id : 0
> siblings    : 1
> core id : 0
> cpu cores   : 1
> apicid  : 0
> initial apicid  : 0
> fdiv_bug    : no
> f00f_bug    : no
> coma_bug    : no
> fpu : yes
> fpu_exception   : yes
> cpuid level : 1
> wp  : yes
> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow cpuid
> 3dnowprefetch vmmcall
> bugs    : fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2
> spec_store_bypass
> bogomips    : 3596.66
> clflush size    : 32
> cache_alignment : 32
> address sizes   : 34 bits physical, 32 bits virtual
> power management: ts
> ===
> 
> dmesg from a successful boot (Debian kernel 6.6.15-2) is here [4].
> 
> This particular system has been running all Debian testing kernels since
> at least the 2.6.32 days and is currently running 6.6.15-2 completely
> fine, thus this is an obvious regression.
> 
> The original Debian bug is #1071378 [5].
> 
> 
> #regzbot introduced: fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6
> 
> [1] https://manx.datengang.de/temp/linux-6.7-crash/6.7.12-1-crash.png
> [2] https://manx.datengang.de/temp/linux-6.7-crash/config
> [3] https://manx.datengang.de/temp/linux-6.7-crash/config-6.8.11-686-pae
> [4] https://manx.datengang.de/temp/linux-6.7-crash/dmesg-6.6.15-2.txt
> [5] https://bugs.debian.org/1071378
> 
> 
> Best regards,
> Jörn
> 
> 

Bug#1072200: libllvm19: libLLVM.so.19.0 => not found

[Sylvestre Ledru]

Le 30/05/2024 à 07:16, Wentao Zhang a écrit :

Package: libllvm19
Version: 1:19~++20240529104944+a3f9066e99f3-1~exp1~20240529225109.743
Severity: normal

Hi,

Some library symlinks have changed and as a result:

$ ldd `which clang-19`
linux-vdso.so.1 (0x89cf)
libclang-cpp.so.19.0 => not found
libLLVM.so.19.0 => not found
libstdc++.so.6 => /lib/aarch64-linux-gnu/libstdc++.so.6 
(0x89a0)
libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x8996)
libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 
(0x89c4)
libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x897b)
/lib/ld-linux-aarch64.so.1 (0x89cb3000)

I guess for libLLVM we should port part of this commit [1] from branch "18" to
branch "snapshot". I'm still figuring out the needed changes for libclang-cpp.

Also, line #1 and line #3 in this file [2] seem conflicting? (only affecting
branch "18" though)

[1] 
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/f6c22777bc0687fc548343d3fa565656a1318a18
[2] 
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/blob/d5a73bd2c9551571084ccecf4307ef94e0b75d96/debian/libllvmX.Y.links.in

Thanks,
Wentao


Thanks

clang still works right ?

$ clang-19 --version
Debian clang version 19.0.0 (++20240529093513+2cfea14a57ad-1~exp1)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm-19/bin

Thanks

S

Bug#1058649: (no subject)

[wuruilong]

Dear Maintainer:

Upstream has merged patch to support loongarch at the following link: 
https://git.savannah.gnu.org/gitweb/?p=libffcall.git;a=commit;h= 
600d713cd18f09a698f937ff6c2cead41036e3da.


Please upgrade the version or merge the patches in the link.

Thanks

wuruilong

Bug#1071140: gcc-14: internal compiler error: in find_or_generate_expression, at tree-ssa-pre.cc:2780 on riscv64

[Bo YU]

Hi,

On Thu, May 30, 2024 at 2:45 PM Jiawei  wrote:
>
> We had fixed this on gcc upstream ——
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c9842f99042454bef99fe82506c6dd50f34e283e
>

\o/.

Thanks for so quickly fix!

> Thanks for your report.

Okay, I will close this once I can verify this on Debian side.

Thanks again!

BR,
Bo
>
>
> BR,
>
> Jiawei
>

Bug#1072204: setupcon: race condition with systemd-tmpfiles

[Marc Leeman]

Package: console-setup
Version: 1.226
Severity: normal
Tags: patch

Dear Maintainer,

On occasion I have a situation where console-setup.service fails to
start up due to a race condition. After investigating this, it was
already reported in Ubuntu back in 2019 and I have verified that the
patch they have implemented resolves the issue for me:

admin@boxpc001-a8f7693fbff14940ade0e3247b1cea8e:~$ for s in $(systemctl 
list-units --type service --full --failed --plain --no-legend | cut -f 1 -d ' 
'); do journalctl --boot --no-pager --unit "${s}"; done
May 28 13:15:05 boxpc001 systemd[1]: Starting console-setup.service - Set 
console font and keymap...
May 28 13:15:05 boxpc001 console-setup.sh[588]: /usr/bin/setupcon: 999: cannot 
open /tmp/tmpkbd.hoHrPK: No such file
May 28 13:15:05 boxpc001 systemd[1]: console-setup.service: Main process 
exited, code=exited, status=1/FAILURE
May 28 13:15:05 boxpc001 systemd[1]: console-setup.service: Failed with result 
'exit-code'.
May 28 13:15:05 boxpc001 systemd[1]: Failed to start console-setup.service - 
Set console font and keymap.

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

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

Versions of packages console-setup depends on:
ii  console-setup-linux 1.226
ii  debconf [debconf-2.0]   1.5.86
ii  keyboard-configuration  1.226
ii  xkb-data2.41-2

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales2.38-11
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.09-1

Versions of packages keyboard-configuration depends on:
ii  debconf [debconf-2.0]   1.5.86
ii  liblocale-gettext-perl  1.07-7
ii  xkb-data2.41-2

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.66
ii  kbd 2.6.4-2
ii  keyboard-configuration  1.226

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
ii  gnome-control-center  1:46.0.1-1
ii  kbd   2.6.4-2
ii  systemd   255.5-1

-- debconf information:
* keyboard-configuration/optionscode:
  console-setup/use_system_font:
  console-setup/store_defaults_in_debconf_db: true
  debian-installer/console-setup-udeb/title:
  keyboard-configuration/unsupported_config_layout: true
* keyboard-configuration/model: Generic 105-key PC
* keyboard-configuration/store_defaults_in_debconf_db: true
* keyboard-configuration/switch: No temporary switch
* keyboard-configuration/layout:
  keyboard-configuration/unsupported_layout: true
  console-setup/fontsize: 8x16
  console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  console-setup/guess_font:
* keyboard-configuration/layoutcode: us
* keyboard-configuration/altgr: The default for the keyboard layout
  console-setup/fontsize-fb47: 8x16
* keyboard-configuration/xkb-keymap: us
* keyboard-configuration/variantcode:
* keyboard-configuration/toggle: No toggling
* keyboard-configuration/modelcode: pc105
* keyboard-configuration/compose: No compose key
  console-setup/fontface47: Fixed
  console-setup/framebuffer_only:
* keyboard-configuration/other:
  console-setup/fontsize-text47: 8x16
  console-setup/codesetcode: Lat15
* keyboard-configuration/variant: English (US)
  keyboard-configuration/unsupported_options: true
  console-setup/charmap47: UTF-8
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_config_options: true
diff -Nru console-setup-1.108ubuntu15.4/debian/changelog 
console-setup-1.108ubuntu15.5/debian/changelog
--- console-setup-1.108ubuntu15.4/debian/changelog  2017-10-05 
19:36:07.0 +
+++ console-setup-1.108ubuntu15.5/debian/changelog  2019-04-10 
20:16:29.0 +
@@ -1,3 +1,13 @@
+console-setup (1.108ubuntu15.5) xenial; urgency=medium
+
+  * setupcon: use /run for tempfiles (and dump the various unnecessary
+fallback paths), since /run is always mountable rw at least as early as
+/tmp is and is guaranteed to be safe from tmpcleaners at boot.  Only keep
+/tmp as a fallback in case we have access to write to /tmp and to a
+console, but not to /run.  LP: #1824227.
+
+ -- Steve Langasek   Wed, 10 Apr 2019 13:16:29 -0700
+
 console-setup (1.108ubuntu15.4) xenial; urgency=medium
 
* Drop dependency from console-setup to initramfs-tools |
diff -Nru console-setup-1.108ubuntu15.4/setupcon 
console-setup-1.108ubuntu15.5/setupcon
--- 

Bug#1063770: transition: mupdf

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 25/05/2024 16:52, Bastian Germann wrote:

On Sun, 5 May 2024 18:29:52 +0200 Sebastian Ramacher  
wrote:

> ippsample - doesn't seem to use mupdf at all
> pymupdf - requires some changes. Likely also needs to update to new upstream 
version.

> sioyek - requires some changes to drop extra linker flags.

Have bugs been filed for these issues?


The packages are prepared in experimental.


I'm not sure there's anything for us to do here, as this is not really a library 
transition as you say. But in any case, go ahead and let us know if there's 
anything for us to do.


Cheers,
Emilio

Bug#1071378: [REGRESSION] commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 (Linux 6.7+) crashes during boot

[Jörn Heusipp]

Hello x86 maintainers!


commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 ("x86/sev-es: Set
x86_virt_bits to the correct value straight away, instead of a two-phase
approach") crashes during boot for me on this 32bit x86 system.

Updating a Debian testing system resulted in a hang during boot before
printing anything, with any 6.7 or later kernel. With 'earlyprintk=vga',
I managed to capture the crash on video and stitched it together as an
image [1].
Trimmed transcription (might contain typos) of the crash from Debian
kernel 6.7.12-1:
===
BUG: kernel NULL pointer dereference, address: 0010
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
Oops: 0002 [#1] PREEMPT SMP NOPTI
[...]
EIP: __ring_buffer_alloc+0x32/0x194
[...]
show_regs
__die
page_fault_oops
kernelmode_fixup_or_oops.constprop
__bad_area_nosemaphore.constprop
bad_area_nosemaphore
do_user_addr_fault
prb_read_valid
exc_page_fault
pvclock_clocksource_read_nowd
handle_exception
pvclock_clocksource_read_nowd
__ring_buffer_alloc
pvclock_clocksource_read_nowd
__ring_buffer_alloc
early_trace_init
start_kernel
i386_start_kernel
startup_32_smp
[...]
===
I could transcribe all of it or capture it again from latest git and
decode the symbols, if truely really needed, but I figured the type of
crash and the trace itself could maybe be sufficient. It looks identical
to me for all later crashing kernel versions.

I bisected this down to commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6.

The kernel config [2] I used is 'make olddefconfig' based on Debian's
config-6.8.11-686-pae [3].

I also tested 6.9.2 and 6.10-rc1, both also still crash in the same way.

cpuinfo:
===
manx@caesar:~$ cat /proc/cpuinfo
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 8
model name  : AMD Duron(tm)
stepping: 1
cpu MHz : 1798.331
cache size  : 64 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow cpuid
3dnowprefetch vmmcall
bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2
spec_store_bypass
bogomips: 3596.66
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts
===

dmesg from a successful boot (Debian kernel 6.6.15-2) is here [4].

This particular system has been running all Debian testing kernels since
at least the 2.6.32 days and is currently running 6.6.15-2 completely
fine, thus this is an obvious regression.

The original Debian bug is #1071378 [5].


#regzbot introduced: fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6

[1] https://manx.datengang.de/temp/linux-6.7-crash/6.7.12-1-crash.png
[2] https://manx.datengang.de/temp/linux-6.7-crash/config
[3] https://manx.datengang.de/temp/linux-6.7-crash/config-6.8.11-686-pae
[4] https://manx.datengang.de/temp/linux-6.7-crash/dmesg-6.6.15-2.txt
[5] https://bugs.debian.org/1071378


Best regards,
Jörn

Bug#1061902: consolekit2: NMU diff for 64-bit time_t transition

[Mark Hindley]

Control: severity -1 normal

On Fri, May 17, 2024 at 08:58:34AM +0100, Mark Hindley wrote:
> On Wed, May 08, 2024 at 01:09:59PM +0100, Mark Hindley wrote:
> > Michael and Steve,
> > 
> > I would appreciate some help here.
> 
> Bump to reset autoremove timer.

Still no response. Downgrading severity to avoid the autoremove dance again.

Mark

Bug#1071140: gcc-14: internal compiler error: in find_or_generate_expression, at tree-ssa-pre.cc:2780 on riscv64

[Jiawei]

We had fixed this on gcc upstream —— 
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c9842f99042454bef99fe82506c6dd50f34e283e


Thanks for your report.


BR,

Jiawei

Bug#966621: Make /tmp/ a tmpfs and cleanup /var/tmp/ on a timer by default [was: Re: systemd: tmpfiles.d not cleaning /var/tmp by default]

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Luca Boccassi (2024-05-28 01:54:08)
> Thanks for the useful input, the following has been done:
> 
> - existing installations pre-trixie will get an orphaned tmpfiles.d in
> /etc/ that keeps the existing behaviour unchanged (no cleanup of
> /var/tmp)
> - openssh and tmux have been fixed to provide a tmpfiles.d exception
> to retain their respective files
> - the /tmp/ description in debian-installer has been updated to note
> it is a tmpfs by default (via a commit in partman-basicfilesystems,
> will upload if nobody gets around to it before Trixie's freeze)
> - two paragraphs have been provided for the release notes ticket
> - the changes are also noted in NEWS, with instructions on how to
> override locally
> - as mentioned, the latest upload to unstable makes /tmp/ a tmpfs by
> default and for new installations 10+ days old files in /tmp/ and 30+ days
> old files in /var/tmp/ are cleaned up daily

thank you for having discussed this change on d-devel and for adding
documentation to NEWS and release notes to announce this change. I also think
it is sensible to roll this only out on new installations and to keep the
behaviour on existing setups. Thank you for implementing that as well.

That being said, maybe some Perl wizard knows how to do a flock on a directory
in Perl? I tried this:

use Fcntl qw(LOCK_EX);
opendir(my $handle, ".") or die "opendir: $!";
flock($handle, LOCK_EX) or die "flock: $!";

And got this:

flock() on unopened filehandle $handle at test.pl line 8.
(Are you trying to call flock() on dirhandle $handle?)
flock: Bad file descriptor at test.pl line 8.

Wrapping $handle in fileno() doesn't make a difference either. Perl sources
seem to indicate that directory handles are "evil_fh"?

https://sources.debian.org/src/perl/5.38.2-4/util.c/?hl=3783#L3783

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1072073: python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py

[Yogeswaran Umasankar]

Hi Laszlo,

I am reaching out to you regarding a file conflict between the nanopb
package and the python3-proto-plus package. The conflict involves the
file /usr/lib/python3/dist-packages/proto/__init__.py, which is present
in both packages.

Module name "proto" is part of python3-proto-plus. Renaming proto in
python3-proto-plus will significantly impact the future depended
packages too.

It appears that the nanopb package’s usage of the module name "proto"
does not identify a Python module in the conventional sense. It might be
plausible to make this module private within the nanopb package, which
could resolve the conflict. Would you consider making the module
private? Alternatively, if you have any other suggestions to resolve
this conflict, I am glad to hear them.

Cheers!

Bug#1072203: O: filezilla -- Full-featured graphical FTP/FTPS/SFTP client

[Phil Wyett]

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

I intend to orphan the filezilla package.

Description: Full-featured graphical FTP/FTPS/SFTP client
 FileZilla is a full-featured FTP client with an easy-to-use GUI.
 .
 It is written in C++ and uses the wxWidgets library.
 .
 FileZilla includes the following features:
   * Supports FTP, FTP over SSL/TLS (FTPS) and SSH File Transfer Protocol (SFTP)
   * IPv6 support
   * Available in more than 40 languages
   * Supports resume and transfer of large files >4GB
   * Easy to use Site Manager and transfer queue
   * Bookmarks
   * Drag & drop support (in application)
   * Speed limits
   * Filename filters
   * Directory comparison
   * Network configuration wizard
   * Remote file editing
   * Keep-alive
   * HTTP/1.1, SOCKS5 and FTP Proxy support
   * Logging to file
   * Synchronized directory browsing
   * Remote file search
   * Tabbed interface to connect to multiple servers

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1072202: O: libfilezilla -- build high-performing platform-independent programs

[Phil Wyett]

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

I intend to orphan the libfilezilla package.

Description: build high-performing platform-independent programs (development)
 Free, open source C++ library, offering some basic functionality to build
 high-performing, platform-independent programs. Some of the highlights include:
 .
  - A typesafe, multi-threaded event system that's very simple to use yet
extremely efficient
  - Timers for periodic events
  - A datetime class that not only tracks timestamp but also their accuracy,
which simplifies dealing with timestamps originating from different sources
  - Simple process handling for spawning child processes with redirected I/O

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1072200: libllvm19: libLLVM.so.19.0 => not found

[Wentao Zhang]

Package: libllvm19
Version: 1:19~++20240529104944+a3f9066e99f3-1~exp1~20240529225109.743
Severity: normal

Hi,

Some library symlinks have changed and as a result:

$ ldd `which clang-19`
linux-vdso.so.1 (0x89cf)
libclang-cpp.so.19.0 => not found
libLLVM.so.19.0 => not found
libstdc++.so.6 => /lib/aarch64-linux-gnu/libstdc++.so.6 
(0x89a0)
libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x8996)
libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 
(0x89c4)
libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x897b)
/lib/ld-linux-aarch64.so.1 (0x89cb3000)

I guess for libLLVM we should port part of this commit [1] from branch "18" to
branch "snapshot". I'm still figuring out the needed changes for libclang-cpp.

Also, line #1 and line #3 in this file [2] seem conflicting? (only affecting
branch "18" though)

[1] 
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/f6c22777bc0687fc548343d3fa565656a1318a18
[2] 
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/blob/d5a73bd2c9551571084ccecf4307ef94e0b75d96/debian/libllvmX.Y.links.in

Thanks,
Wentao


-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 6.7.12-orbstack-00201-g2ddb8f197a46 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libllvm19 depends on:
ii  libc6   2.36-9+deb12u7
ii  libedit23.1-20221030-2
ii  libffi8 3.4.4-1
ii  libgcc-s1   12.2.0-14
ii  libstdc++6  12.2.0-14
ii  libtinfo6   6.4-4
ii  libxml2 2.9.14+dfsg-1.3~deb12u1
ii  libz3-4 4.8.12-3.1
ii  libzstd11.5.4+dfsg2-5
ii  zlib1g  1:1.2.13.dfsg-1

libllvm19 recommends no packages.

libllvm19 suggests no packages.

-- no debconf information

Bug#1072201: rtags: autopkgtest failure due to missing depends on emacs

[Xiyue Deng]

Package: rtags
Version: 2.38-10
Severity: serious

Dear Maintainer,

rtags is now failing autopkgtest due to missing dependency on emacs.
See the autopkgtest regression test from flycheck[1].  It used to work
because it pulls in emacs through the dependency of flycheck.  The
recent upload of flycheck 34.1-1 has downgraded this dependency to
recommends (by me, actually) which triggered this failure.  As this is
causing build failure on rebuild, I'm using the serious severity.

I'll prepare a fix patch/MR soon.

[1] https://ci.debian.net/packages/r/rtags/testing/amd64/47083927/

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

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

Bug#1072199: O: compton-- compositor for X11, based on xcompmgr

[Phil Wyett]

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

I intend to orphan the compton package.

Description: compositor for X11, based on xcompmgr
 compton is a compositor for
X11, based on xcompmgr. In addition to shadows,
 fading and translucency, compton
implements window frame opacity control,
 inactive window transparency, and
shadows on argb windows.

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1064196: tracker-extract: Repeatedly coredumps

[oliver]

This time a trace of tracker-extract from coredumpctl.

   PID: 8695 (tracker-extract)
   UID: 1000 (oliver)
   GID: 1000 (oliver)
Signal: 31 (SYS)
 Timestamp: Thu 2024-05-30 00:46:52 EDT (57min ago)
  Command Line: /usr/libexec/tracker-extract-3
Executable: /usr/libexec/tracker-extract-3
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/background.slice/tracker-extract-3.service

  Unit: user@1000.service
 User Unit: tracker-extract-3.service
 Slice: user-1000.slice
 Owner UID: 1000 (oliver)
   Boot ID: b155d2eaa24748068bc5ffb2a30031b3
Machine ID: 4113bca0c7624baa833583af51ac9106
  Hostname: localhost
   Storage: 
/var/lib/systemd/coredump/core.tracker-extract.1000.b155d2eaa24748068bc5ffb2a30031b3.8695.171704441200.zst 
(present)

  Size on Disk: 451.9K
   Message: Process 8695 (tracker-extract) of user 1000 dumped core.

Module libudev.so.1 from deb systemd-256~rc3-2.amd64
Module libmount.so.1 from deb util-linux-2.40.1-2.amd64
Module libblkid.so.1 from deb util-linux-2.40.1-2.amd64
Stack trace of thread 8697:
#0  0x7f602bc5fe06 epoll_wait (libc.so.6 + 0x10be06)
#1  0x7f602b1c7cba n/a (libmount.so.1 + 0x3bcba)
#2  0x7f602b1c924f mnt_monitor_get_fd 
(libmount.so.1 + 0x3d24f)

#3  0x7f602bfad118 n/a (libgio-2.0.so.0 + 0xd5118)
#4  0x7f602bf2d3c4 n/a (libgio-2.0.so.0 + 0x553c4)
#5  0x7f602c122e3f n/a (libglib-2.0.so.0 + 0x59e3f)
#6  0x7f602c124ec7 n/a (libglib-2.0.so.0 + 0x5bec7)
#7  0x7f602c1254e0 g_main_context_iteration 
(libglib-2.0.so.0 + 0x5c4e0)

#8  0x7f602c125531 n/a (libglib-2.0.so.0 + 0x5c531)
#9  0x7f602c152bb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#10 0x7f602bbdddbb n/a (libc.so.6 + 0x89dbb)
#11 0x7f602bc5f9f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 8699:
#0  0x7f602bbec267 n/a (libc.so.6 + 0x98267)
#1  0x7f602bbed7b9 malloc (libc.so.6 + 0x997b9)
#2  0x7f602c12bdd2 g_malloc (libglib-2.0.so.0 + 
0x62dd2)
#3  0x7f602c147af9 g_strconcat (libglib-2.0.so.0 + 
0x7eaf9)

#4  0x7f602bf49c5e n/a (libgio-2.0.so.0 + 0x71c5e)
#5  0x7f602bf49d70 n/a (libgio-2.0.so.0 + 0x71d70)
#6  0x7f602bf4a440 n/a (libgio-2.0.so.0 + 0x72440)
#7  0x7f602bf4c195 n/a (libgio-2.0.so.0 + 0x74195)
#8  0x7f602bf4e6e8 g_file_attribute_matcher_new 
(libgio-2.0.so.0 + 0x766e8)

#9  0x7f602c0151ea n/a (libgio-2.0.so.0 + 0x13d1ea)
#10 0x7f602bf3d287 n/a (libgio-2.0.so.0 + 0x65287)
#11 0x7f602bf8f4c1 n/a (libgio-2.0.so.0 + 0xb74c1)
#12 0x7f602c153712 n/a (libglib-2.0.so.0 + 0x8a712)
#13 0x7f602c152bb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#14 0x7f602bbdddbb n/a (libc.so.6 + 0x89dbb)
#15 0x7f602bc5f9f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 8695:
#0  0x7f602bc5d9f9 syscall (libc.so.6 + 0x1099f9)
#1  0x7f602c181114 g_cond_wait (libglib-2.0.so.0 + 
0xb8114)

#2  0x7f602bf2d363 n/a (libgio-2.0.so.0 + 0x55363)
#3  0x7f602bf2d468 n/a (libgio-2.0.so.0 + 0x55468)
#4  0x7f602c265e93 n/a (libtracker-miner-3.0.so + 
0x24e93)
#5  0x7f602c266c3d 
tracker_content_identifier_cache_init (libtracker-miner-3.0.so + 0x25c3d)

#6  0x55d528caba49 main (tracker-extract-3 + 0xaa49)
#7  0x7f602bb7bc8a n/a (libc.so.6 + 0x27c8a)
#8  0x7f602bb7bd45 __libc_start_main (libc.so.6 + 
0x27d45)

#9  0x55d528cabeb1 _start (tracker-extract-3 + 0xaeb1)

Stack trace of thread 8698:
#0  0x7f602bc5247f __poll (libc.so.6 + 0xfe47f)
#1  0x7f602c124e15 n/a (libglib-2.0.so.0 + 0x5be15)
#2  0x7f602c1257cf g_main_loop_run 
(libglib-2.0.so.0 + 0x5c7cf)

#3  0x7f602bffca6a n/a (libgio-2.0.so.0 + 0x124a6a)
#4  0x7f602c152bb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#5  0x7f602bbdddbb n/a (libc.so.6 + 0x89dbb)
#6  0x7f602bc5f9f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 8696:
#0  0x7f602bc5d9f9 syscall (libc.so.6 + 0x1099f9)
#1  0x7f602c181114 g_cond_wait (libglib-2.0.so.0 + 
0xb8114)

#2  0x7f602c0ed35b n/a (libglib-2.0.so.0 + 0x2435b)
#3  0x7f602c1533ea n/a (libglib-2.0.so.0 + 

Bug#1072198: xfce4-pulseaudio-plugin: [pipewire] Plugin terminates with signal SIGABRT during Xfce-user logout

[Dirk Lehmann]

Package: xfce4-pulseaudio-plugin
Version: 0.4.8-1+b2
Severity: normal

Dear Maintainer,

I am using the xfce4-pulseaudio-plugin in conjunction with Pipewire.
Since some days, if I'm logging out from Xfce desktop (or shutting
down the computer) the xfce4-pulseaudio-plugin terminates irregular
with signal SIGABRT.  I have GDB attached during that issue, here
follows the output:

**
*** shell ***
/home/user$> ps aux | grep 'wrapper-2.0.*PulseAudio'
user3609  0.0  0.2 453236 38784 ?Sl   07:07   0:00 
/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libpulseaudio-plugin.so 6 
16777239 pulseaudio PulseAudio Plugin Adjust the audio volume of the PulseAudio 
sound system
user4259  0.0  0.0   6852  2240 pts/0S+   07:10   0:00 grep 
wrapper-2.0.*PulseAudio
/home/user$> gdb -p 3609
GNU gdb (Debian 13.2-1+b1) 13.2 
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 3609
[New LWP 3617]
[New LWP 3618]
[New LWP 3619]
[New LWP 3641]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f135837a47f in __GI___poll (fds=0x559d0b19def0, nfds=4, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
29  ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
(gdb) backtrace
#0  0x7f135837a47f in __GI___poll (fds=0x559d0b19def0, nfds=4, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f13584bce15 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f13584bd7cf in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f13589fd65d in gtk_main () from /lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x559d0a7178d3 in main ()
(gdb) continue
Continuing.

Thread 1 "panel-6-pulseau" received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=, signo=signo@entry=6, 
no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: No such file or directory.
(gdb) backtrace
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1  0x7f1358307b7f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2  0x7f13582b94e2 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#3  0x7f13582a24ed in __GI_abort () at ./stdlib/abort.c:79
#4  0x7f13584800a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f13584e8ffe in g_assertion_message_expr () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f13585eab06 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x7f13585c92c3 in g_object_unref () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x559d0a717924 in main ()
(gdb) continue
Continuing.
[Thread 0x7f1354c006c0 (LWP 3641) exited]
[Thread 0x7f13560006c0 (LWP 3618) exited]
[Thread 0x7f1356a006c0 (LWP 3617) exited]
[Thread 0x7f135737da80 (LWP 3609) exited]
[Thread 0x7f13556006c0 (LWP 3619) exited]
[New process 3609]

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb) q
***
**

After the first `(gdb) continue` a logged off.  Then a `core` file was
written to my home directory in `/home/user`.  I backtraced it with
GDB, here is the output:

**
*** shell ***
/home/user$> gdb -c core 
GNU gdb (Debian 13.2-1+b1) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".

warning: Can't open file /memfd:pulseaudio (deleted) during file-backed mapping 
note 

Bug#1072197: O: bglibs-- This package contains a collection of libraries

[Phil Wyett]

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

I intend to orphan the bglibs package.

Description: This package contains a collection of libraries (development)
 written by Bruce Guenter and put in use in various packages.

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1072196: ppa-dev-tools: please remove dependency on old mock

[Alexandre Detiste]

Source: ppa-dev-tools
Version: 0.5.0-1
Severity: normal
X-Debbugs-Cc: Benjamin Drung 

Hi,

I pushed a "no-mock" branch on Salsa with a patch that
replaces the old & deprecated "mock" with
the newer one from the standard library.

I have no idea how Launchpad works so
I please ask you to forward it to the right persons.

Greetings

> https://github.com/testing-cabal/mock
>
> mock is now part of the Python standard library, available as unittest.mock 
> in Python 3.3 onwards.

Bug#1072073: python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py

[Yogeswaran Umasankar]

Hi,

I will reachout to the nanopb maintainer.

Thank you!

Bug#1072195: valgrind: add support for loong64

[Andrius Merkys]

Package: valgrind
Version: 1:3.20.0-2.1
Severity: wishlist
Control: block 1072148 by -1
X-Debbugs-CC: wuruil...@loongson.cn

Hello,

In #1072148 a patch to support loong64 has been proposed in epics-base. 
The proposed patch modifies valgrind header (valgrind/valgrind.h) 
embedded in epics-base source. I would like to un-embed this header in 
the upcoming upload. Therefore to be able to add support for loong64 in 
epics-base, valgrind should support it first.


Andrius

Bug#1072073: python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py

[Helmut Grohne]

Control: reassign -1 python3-proto-plus,nanopb
Control: affects -1 =

On Wed, May 29, 2024 at 08:40:03PM -0400, Yogeswaran Umasankar wrote:
> For now, I am planning to declare nanopb in Conflicts for
> 'python3-proto-plus' binary. Let me know if it might not be advisable.

Doing so violates Debian policy 10.1:

Two different packages must not install programs with different
functionality but with the same filenames.

Arguably, this extends to Python modules. Generally speaking, packages
should be coinstallable unless they fundamentally cannot and in this
case renaming either is a reasonable solution.

I recommend talking to the nanopb maintainer, because what their
package does is unusual. The affected module name "proto" is part of the
python3-proto package, but the nanopb package isn't even identifying a
Python module. It would be plausible to make their module private and
hence resolve the conflict. I very much expect a solution of this bug to
require changes in nanopb of some form.

So this bug likely involves more coordination than originally
anticipated. Keep in mind that every mail to this bug resets the
testing autoremover and the freeze is not exactly close.

Helmut

Bug#1072148: epics-base: please add support for loong64

[Andrius Merkys]

On 2024-05-30 05:17, wuruilong wrote:

I checked valgrind debian package is not supported loongarch architecture.


Thanks for checking. I would like to remove the embedded 
valgrind/valgrind.h and use the header from valgrind package. Thus I 
would suggest implementing loongarch support in valgrind before epics-base.


Andrius

Bug#1072194: O: librepfunc-- set of C++ classes and utilities for building multimedia tools

[Phil Wyett]

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

I intend to orphan the librepfunc package.

Description: set of C++ classes and utilities for building multimedia tools
 This
is a collection of utilities and functions used for example in w-scan-cpp
 .
 stri
ng related:
  * LowerCase and UpperCase
  * LeftTrim and RightTrim and Trim
  *
FrontFill and BackFill
  * ReplaceAll
 .
 vector of string related:
  * SplitStr
 .
 n
umber conversion to string or vice versa
  * IntToStr
  * FloatToStr
  * ExpToStr
 
* StrToInt
  * StrToFloat
 .
 print time
  * TimeStr
 .
 other conversions
  *
BCDtoDecimal
 .
 sleep threads
  * Sleep, mSleep, uSleep
 .
 print hex data
  *
HexDump
 .
 files and directories
  * FileExists
  * cFileList
  * ReadFileToStream
 
* ReadFile
  * WriteStreamToFile
  * WriteFile
 .
 start/stop threads from main
thread
  * ThreadBase

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1072193: O: w-scan-cpp -- DVB channel scanner (successor of w_scan)

[Phil Wyett]

Package: wnpp
Severity: normal
X-Debbugs-Cc: w-scan-...@packages.debian.org
Control: affects -1 + src:w-scan-cpp

I intend to orphan the w-scan-cpp package.

Description: DVB channel scanner (successor of w_scan)
 This is w_scan_cpp - a
dtv channel scanner based on VDR (www.tvdr.de)
 and its Plugins.
 .
 w_scan_cpp
supports
 .
DVB-T(2), DVB-C, DVB-S(2), ATSC(VSB && QAM)
SAT>IP
SCR
("Unicable") EN-50494 & EN-50607 (aka. "JESS")
DiSEqC switches
DiSEqC
rotors (Standard & USALS)
various output formats
VDR channels.conf

VLC channels.xspf
dtv scan tables for dvbv5-scan
channels.dat
for the SAT>IP "DVB Viewer Lite for Windows"
(..)
 .
 Some features are
more recent than those of w_scan, other outdated features
 were not ported.

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1072192: O: vdr-plugin-wirbelscan -- Wirbelscan plugin for VDR

[Phil Wyett]

Package: wnpp
Severity: normal
X-Debbugs-Cc: vdr-plugin-wirbels...@packages.debian.org
Control: affects -1 + src:vdr-plugin-wirbelscan

I intend to orphan the vdr-plugin-wirbelscan package.

Description: Wirbelscan plugin for VDR
 A plugin for the Video Disk Recorder (VDR) that scans for available Digital
 Television (DTV) on the following channels.
 .
   * Digital Video Broadcasting (DVB).
   * Vestigial Sideband (VSB).
   * Quadrature Amplitude Modulation (QAM).
   * SAT>IP, technology (SATIP).

-- 

Website: https://kathenas.org

Instagram: https://instagram.com/kathenasorg/

Buy Me A Coffee: https://buymeacoffee.com/kathenasorg


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

Bug#1059414: open-ath9k-htc-firmware: diff for NMU version 1.4.0-108-gd856466+dfsg1-1.5

[Oleksij Rempel]

Hi Chris,

I'm developer, not the package maintainer. On the source code side
didn't happened anything for some years, so there are no conflicts are
expected. From my perspective there is no need to wait.

Regards,

Oleksij

Bug#1064196: tracker-extract: Repeatedly coredumps

[oliver]

Recently I have been encountering this on trixie/sid.

Here are the error messages:

May 30 00:04:15 localhost systemd[1308]: Failed to start 
tracker-extract-3.service - Tracker metadata extractor.
May 30 00:04:15 localhost systemd[1308]: tracker-extract-3.service: 
Failed with result 'core-dump'.
May 30 00:04:15 localhost systemd[1308]: tracker-extract-3.service: 
Start request repeated too quickly.
May 30 00:04:15 localhost systemd[1308]: tracker-extract-3.service: 
Scheduled restart job, restart counter is at 5.
May 30 00:04:15 localhost systemd[1308]: Failed to start 
tracker-extract-3.service - Tracker metadata extractor.
May 30 00:04:15 localhost systemd[1308]: tracker-extract-3.service: 
Failed with result 'core-dump'.
May 30 00:04:15 localhost systemd[1308]: tracker-extract-3.service: Main 
process exited, code=dumped, status=31/SYS


Here is the stack trace:

Process 4391 (tracker-extract) of user 1000 dumped core.

Module libudev.so.1 from deb systemd-256~rc3-2.amd64
Module libmount.so.1 from deb util-linux-2.40.1-2.amd64
Module libblkid.so.1 from deb util-linux-2.40.1-2.amd64
Stack trace of thread 4394:
#0  0x7eff31b28e06 epoll_wait (libc.so.6 + 0x10be06)
#1  0x7eff315adcba n/a (libmount.so.1 + 0x3bcba)
#2  0x7eff315af24f mnt_monitor_get_fd (libmount.so.1 + 0x3d24f)
#3  0x7eff31e76118 n/a (libgio-2.0.so.0 + 0xd5118)
#4  0x7eff31df63c4 n/a (libgio-2.0.so.0 + 0x553c4)
#5  0x7eff31febe3f n/a (libglib-2.0.so.0 + 0x59e3f)
#6  0x7eff31fedec7 n/a (libglib-2.0.so.0 + 0x5bec7)
#7  0x7eff31fee4e0 g_main_context_iteration (libglib-2.0.so.0 + 0x5c4e0)
#8  0x7eff31fee531 n/a (libglib-2.0.so.0 + 0x5c531)
#9  0x7eff3201bbb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#10 0x7eff31aa6dbb n/a (libc.so.6 + 0x89dbb)
#11 0x7eff31b289f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 4396:
#0  0x7eff31fb62e0 n/a (libglib-2.0.so.0 + 0x242e0)
#1  0x7eff3201c76a n/a (libglib-2.0.so.0 + 0x8a76a)
#2  0x7eff3201bbb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#3  0x7eff31aa6dbb n/a (libc.so.6 + 0x89dbb)
#4  0x7eff31b289f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 4391:
#0  0x7eff31b269f9 syscall (libc.so.6 + 0x1099f9)
#1  0x7eff3204a114 g_cond_wait (libglib-2.0.so.0 + 0xb8114)
#2  0x7eff31df6363 n/a (libgio-2.0.so.0 + 0x55363)
#3  0x7eff31df6468 n/a (libgio-2.0.so.0 + 0x55468)
#4  0x7eff3212ee93 n/a (libtracker-miner-3.0.so + 0x24e93)
#5  0x7eff3212fc3d tracker_content_identifier_cache_init 
(libtracker-miner-3.0.so + 0x25c3d)

#6  0x55e5acdf1a49 main (tracker-extract-3 + 0xaa49)
#7  0x7eff31a44c8a n/a (libc.so.6 + 0x27c8a)
#8  0x7eff31a44d45 __libc_start_main (libc.so.6 + 0x27d45)
#9  0x55e5acdf1eb1 _start (tracker-extract-3 + 0xaeb1)

Stack trace of thread 4395:
#0  0x7eff31b1b47f __poll (libc.so.6 + 0xfe47f)
#1  0x7eff31fede15 n/a (libglib-2.0.so.0 + 0x5be15)
#2  0x7eff31fee7cf g_main_loop_run (libglib-2.0.so.0 + 0x5c7cf)
#3  0x7eff31ec5a6a n/a (libgio-2.0.so.0 + 0x124a6a)
#4  0x7eff3201bbb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#5  0x7eff31aa6dbb n/a (libc.so.6 + 0x89dbb)
#6  0x7eff31b289f8 n/a (libc.so.6 + 0x10b9f8)

Stack trace of thread 4393:
#0  0x7eff31b269f9 syscall (libc.so.6 + 0x1099f9)
#1  0x7eff3204a114 g_cond_wait (libglib-2.0.so.0 + 0xb8114)
#2  0x7eff31fb635b n/a (libglib-2.0.so.0 + 0x2435b)
#3  0x7eff3201c3ea n/a (libglib-2.0.so.0 + 0x8a3ea)
#4  0x7eff3201bbb1 n/a (libglib-2.0.so.0 + 0x89bb1)
#5  0x7eff31aa6dbb n/a (libc.so.6 + 0x89dbb)
#6  0x7eff31b289f8 n/a (libc.so.6 + 0x10b9f8)
ELF object binary architecture: AMD x86-64


OpenPGP_0x96B430AAF6F4B86F.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1060772: [Python-modules-team] Bug#1060772: python3-jupyterlab: Using node-corepack downloads yarnpkg from Internet

[Yadd]

Hi,

depending on the use of "jupyterlab build":
 - when used manually, may prefer to launch yarnpkg
 - when used under Debian build/test, may prefer to use
   pkgjs-install-minimal

So proposition:
 - drop the patch 0003-Use-system-provided-yarn.js.patch
 - build a custom yarn.js that calls yarnpks or pkg-install-minimal
   depending on an environment variable

Bug#1060011:

[Jaikumar Sharma]

I've also stumbled upon due to this bug , is there any workaround available?

Thanks.

Bug#1072148: epics-base: please add support for loong64

[wuruilong]

在 2024/5/29 下午9:30, Andrius Merkys 写道:

On 2024-05-29 11:32, wuruilong wrote:
Modify the valgrind header file because valgrind's code has gone too 
long without loongarch support.


Does the valgrind Debian package support loong64? If so, the embedded 
valgrind/valgrind.h can be replaced with the header from Debian package.


Andrius


I checked valgrind debian package is not supported loongarch architecture.

wuruilong

Bug#1059283: mate-settings-daemon: diff for NMU version 1.26.1-1.1

[Chris Hofstaedtler]

Control: tags 1059283 + pending


Dear maintainer,

I've prepared an NMU for mate-settings-daemon (versioned as 1.26.1-1.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru mate-settings-daemon-1.26.1/debian/changelog mate-settings-daemon-1.26.1/debian/changelog
--- mate-settings-daemon-1.26.1/debian/changelog	2024-01-06 08:00:22.0 +0100
+++ mate-settings-daemon-1.26.1/debian/changelog	2024-05-30 03:21:29.0 +0200
@@ -1,3 +1,10 @@
+mate-settings-daemon (1.26.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use udev.pc to place udev files. (Closes: #1059283)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 03:21:29 +0200
+
 mate-settings-daemon (1.26.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru mate-settings-daemon-1.26.1/debian/control mate-settings-daemon-1.26.1/debian/control
--- mate-settings-daemon-1.26.1/debian/control	2024-01-06 08:00:14.0 +0100
+++ mate-settings-daemon-1.26.1/debian/control	2024-05-30 03:21:26.0 +0200
@@ -33,6 +33,8 @@
libxrandr-dev,
libxt-dev,
mate-common (>= 1.18),
+   pkgconf,
+   systemd-dev,
x11proto-kb-dev,
 Standards-Version: 4.6.2
 Rules-Requires-Root: no
diff -Nru mate-settings-daemon-1.26.1/debian/mate-settings-daemon-common.install mate-settings-daemon-1.26.1/debian/mate-settings-daemon-common.install
--- mate-settings-daemon-1.26.1/debian/mate-settings-daemon-common.install	2019-08-11 13:32:02.0 +0200
+++ mate-settings-daemon-1.26.1/debian/mate-settings-daemon-common.install	2024-05-30 03:21:26.0 +0200
@@ -1,6 +1,6 @@
 #! /usr/bin/dh-exec
 
-[linux-any] usr/lib/udev/rules.d/ lib/udev
+[linux-any] usr/lib/udev/rules.d/ ${deb_udevdir}
 usr/share/glib-2.0/
 usr/share/icons/
 usr/share/locale/
diff -Nru mate-settings-daemon-1.26.1/debian/rules mate-settings-daemon-1.26.1/debian/rules
--- mate-settings-daemon-1.26.1/debian/rules	2024-01-06 08:00:22.0 +0100
+++ mate-settings-daemon-1.26.1/debian/rules	2024-05-30 03:21:26.0 +0200
@@ -9,8 +9,10 @@
 DEB_HOST_ARCH_OS?=$(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
 ifeq (,$(filter linux, $(DEB_HOST_ARCH_OS)))
 WITHOUT_RFKILL = "--disable-rfkill"
+export deb_udevdir =
 else
 WITHOUT_RFKILL = ""
+export deb_udevdir = $(shell pkg-config --variable=udevdir udev | sed s,^/,,)
 endif
 
 

Bug#1054013: dnssec-trigger: diff for NMU version 0.17+repack-5.2

[Chris Hofstaedtler]

Control: tags 1054013 + pending


Dear maintainer,

I've prepared an NMU for dnssec-trigger (versioned as 0.17+repack-5.2) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru dnssec-trigger-0.17+repack/debian/changelog dnssec-trigger-0.17+repack/debian/changelog
--- dnssec-trigger-0.17+repack/debian/changelog	2023-05-11 19:40:04.0 +0200
+++ dnssec-trigger-0.17+repack/debian/changelog	2024-05-30 03:23:48.0 +0200
@@ -1,3 +1,12 @@
+dnssec-trigger (0.17+repack-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Defer placement of systemd units to systemd.pc. (Closes: #1054013)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 03:23:48 +0200
+
 dnssec-trigger (0.17+repack-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru dnssec-trigger-0.17+repack/debian/control dnssec-trigger-0.17+repack/debian/control
--- dnssec-trigger-0.17+repack/debian/control	2023-05-11 19:39:30.0 +0200
+++ dnssec-trigger-0.17+repack/debian/control	2024-05-30 03:23:45.0 +0200
@@ -11,8 +11,10 @@
 	   libgtk2.0-dev,
 	   libldns-dev (>= 1.6.14-1~),
 	   lsb-base,
+	   pkgconf,
 	   python3,
-   sensible-utils
+	   sensible-utils,
+	   systemd-dev,
 Standards-Version: 4.3.0
 Homepage: https://www.nlnetlabs.nl/projects/dnssec-trigger/
 Vcs-Git: https://salsa.debian.org/dns-team/dnssec-trigger.git
diff -Nru dnssec-trigger-0.17+repack/debian/rules dnssec-trigger-0.17+repack/debian/rules
--- dnssec-trigger-0.17+repack/debian/rules	2020-08-24 20:24:56.0 +0200
+++ dnssec-trigger-0.17+repack/debian/rules	2024-05-30 03:23:45.0 +0200
@@ -21,7 +21,7 @@
 		--with-python=/usr/bin/python3 \
 		--with-hooks=networkmanager \
 		--with-gui=gtk \
-		--with-unitdir=/lib/systemd/system \
+		--with-unitdir=$(shell pkgconf --variable=systemdsystemunitdir systemd) \
 		--with-rundir=/run \
 		--with-keydir=/etc/dnssec-trigger \
 		--with-pidfile=/run/dnssec-triggerd.pid \

Bug#1063693: xdm: diff for NMU version 1:1.1.11-3.1

[Chris Hofstaedtler]

Control: tags 1063693 + pending


Dear maintainer,

I've prepared an NMU for xdm (versioned as 1:1.1.11-3.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -u xdm-1.1.11/debian/changelog xdm-1.1.11/debian/changelog
--- xdm-1.1.11/debian/changelog
+++ xdm-1.1.11/debian/changelog
@@ -1,3 +1,12 @@
+xdm (1:1.1.11-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Let systemd.pc determine the location of systemd units. (Closes: #1063693)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 03:12:21 +0200
+
 xdm (1:1.1.11-3) unstable; urgency=medium
 
   * Team upload.
diff -u xdm-1.1.11/debian/control xdm-1.1.11/debian/control
--- xdm-1.1.11/debian/control
+++ xdm-1.1.11/debian/control
@@ -5,8 +5,9 @@
 Uploaders: Cyril Brulebois 
 Build-Depends:
  debhelper (>= 9),
+ dh-exec,
  dpkg-dev (>= 1.16.1),
- pkg-config,
+ pkgconf,
  libxmu-dev (>= 1:1.0.1),
  libx11-dev (>= 2:1.0.0),
  libxau-dev (>= 1:1.0.0),
@@ -18,6 +19,7 @@
  quilt,
  automake,
  libtool,
+ systemd-dev,
  xutils-dev,
 Standards-Version: 3.9.6
 Vcs-Git: git://anonscm.debian.org/pkg-xorg/app/xdm
diff -u xdm-1.1.11/debian/rules xdm-1.1.11/debian/rules
--- xdm-1.1.11/debian/rules
+++ xdm-1.1.11/debian/rules
@@ -13,6 +13,8 @@
 
 include debian/xsfbs/xsfbs.mk
 
+export deb_systemdsystemunitdir := $(shell pkgconf --variable=systemdsystemunitdir systemd | sed s,^/,,)
+
 confflags += \
 	--prefix=/usr \
 	--mandir=\$${prefix}/share/man \
@@ -24,7 +26,7 @@
 	--with-pixmapdir=/usr/share/X11/xdm/pixmaps \
 	--with-color-pixmap=debian.xpm \
 	--with-bw-pixmap=debianbw.xpm \
-	--with-systemdsystemunitdir=/lib/systemd/system \
+	--with-systemdsystemunitdir \
 	--disable-xdm-auth \
 	--with-xft \
 	--disable-silent-rules \
@@ -126,6 +128,7 @@
 	dh_testroot
 
 	dh_installdocs
+	chmod +x debian/xdm.install
 	dh_install --sourcedir=debian/tmp --list-missing
 	dh_installchangelogs ChangeLog
 	dh_installinit --noscripts
diff -u xdm-1.1.11/debian/xdm.install xdm-1.1.11/debian/xdm.install
--- xdm-1.1.11/debian/xdm.install
+++ xdm-1.1.11/debian/xdm.install
@@ -1,3 +1,4 @@
+#!/usr/bin/dh-exec
 etc/X11/app-defaults/Chooser
 etc/X11/xdm/Xaccess
 etc/X11/xdm/Xreset
@@ -10,7 +11,7 @@
 etc/X11/xdm/xdm-config
 etc/X11/xdm/xdm.options
 etc/insserv.conf.d/xdm
-lib/systemd/system/xdm.service
+${deb_systemdsystemunitdir}/xdm.service
 usr/bin/xdm
 usr/lib/X11/xdm/chooser
 usr/lib/X11/xdm/libXdmGreet.so

Bug#1072190: ITS: psensor

[xiao sheng wen]

Package: psensor
Version: 1.1.5-1.4
Severity: important
X-Debbugs-Cc: mo...@debian.org, sudipm.mukher...@gmail.com, b...@debian.org, 
locutusofb...@debian.org, m...@qa.debian.org, atzli...@sina.com

Hi,

psensor is in clear need of some love and care.

It has many NMU and many bugs not fix.

The current maintainers also agree to somebody adopt it in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953896#27

Regards,

-- System Information:
Release:12.5.2
Codename:   bookworm
Architecture: x86_64

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

Versions of packages psensor depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  libatasmart4 0.19-5
ii  libayatana-appindicator3-1   0.5.92-1
ii  libc62.36-9+deb12u7
ii  libcairo21.16.0-7
ii  libcurl3-gnutls  7.88.1-10+deb12u5
ii  libglib2.0-0 2.74.6-2+deb12u2
ii  libgtk-3-0   3.24.38-2~deb12u1
ii  libgtop-2.0-11   2.40.0-2
ii  libjson-c5   0.16-2
ii  libnotify4   0.8.1-1
ii  libsensors5  1:3.6.0-7.1
ii  libudisks2-0 2.9.4-4
ii  libx11-6 2:1.8.4-2+deb12u2
ii  libxnvctrl0  525.85.05-3~deb12u1
ii  psensor-common   1.1.5-1.4

psensor recommends no packages.

psensor suggests no packages.

-- no debconf information

Bug#1063572: jfsutils: diff for NMU version 1.1.15-5.1

[Chris Hofstaedtler]

Control: tags 1063572 + pending


Dear maintainer,

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

Regards.

diff -Nru jfsutils-1.1.15/debian/changelog jfsutils-1.1.15/debian/changelog
--- jfsutils-1.1.15/debian/changelog	2020-06-23 22:31:15.0 +0200
+++ jfsutils-1.1.15/debian/changelog	2024-05-30 03:10:37.0 +0200
@@ -1,3 +1,12 @@
+jfsutils (1.1.15-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Move files to /usr for DEP17 (closes: #1063572).
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 03:10:37 +0200
+
 jfsutils (1.1.15-5) unstable; urgency=medium
 
   * Update Standards-Version to 4.5.0 .
diff -Nru jfsutils-1.1.15/debian/jfsutils.install jfsutils-1.1.15/debian/jfsutils.install
--- jfsutils-1.1.15/debian/jfsutils.install	2016-11-07 18:39:06.0 +0100
+++ jfsutils-1.1.15/debian/jfsutils.install	2024-05-30 03:10:36.0 +0200
@@ -1 +1 @@
-debian/tmp/sbin
+debian/tmp/usr/sbin
diff -Nru jfsutils-1.1.15/debian/jfsutils-udeb.install jfsutils-1.1.15/debian/jfsutils-udeb.install
--- jfsutils-1.1.15/debian/jfsutils-udeb.install	2016-11-07 18:39:06.0 +0100
+++ jfsutils-1.1.15/debian/jfsutils-udeb.install	2024-05-30 03:10:36.0 +0200
@@ -1 +1 @@
-debian/tmp/sbin
\ No newline at end of file
+debian/tmp/usr/sbin
diff -Nru jfsutils-1.1.15/debian/rules jfsutils-1.1.15/debian/rules
--- jfsutils-1.1.15/debian/rules	2016-11-07 18:39:29.0 +0100
+++ jfsutils-1.1.15/debian/rules	2024-05-30 03:10:36.0 +0200
@@ -25,5 +25,4 @@
 	LDFLAGS += -Wl,--no-relax
 endif
 
-DEB_CONFIGURE_USER_FLAGS := --sbindir=/sbin
 DEB_MAKE_INSTALL_TARGET := install DESTDIR=$(CURDIR)/debian/tmp

Bug#1054088: sanoid: let dh_installsystemd choose the location of units

[Chris Hofstaedtler]

Hi,

On Tue, Oct 17, 2023 at 11:08:24AM -0400, Michael Jeanson wrote:
> On 2023-10-16 15:38, Helmut Grohne wrote:
> > Source: sanoid
> > Version: 2.2.0-1
> > Tags: patch
> > User: helm...@debian.org
> > Usertags: dep17m2
> > 
> > We want to move all aliased files from / to /usr to finalize the
> > /usr-merge transition via DEP17
[..]
> 
> Thanks for the patch, it will be included in the next upload.

Please make sure this lands in trixie before the transition freeze.
Now would be a great time.

Chris

Bug#1071911: debiman: diff for NMU version 0.0~git20220907.a582536-1.1

[Chris Hofstaedtler]

Control: tags 1071911 + patch
Control: tags 1071911 + pending


Dear maintainer,

I've prepared an NMU for debiman (versioned as 0.0~git20220907.a582536-1.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru debiman-0.0~git20220907.a582536/debian/changelog debiman-0.0~git20220907.a582536/debian/changelog
--- debiman-0.0~git20220907.a582536/debian/changelog	2022-10-22 10:38:42.0 +0200
+++ debiman-0.0~git20220907.a582536/debian/changelog	2024-05-30 03:07:49.0 +0200
@@ -1,3 +1,10 @@
+debiman (0.0~git20220907.a582536-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd unit into /usr/lib. (Closes: #1071911)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 03:07:49 +0200
+
 debiman (0.0~git20220907.a582536-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru debiman-0.0~git20220907.a582536/debian/install debiman-0.0~git20220907.a582536/debian/install
--- debiman-0.0~git20220907.a582536/debian/install	2022-10-22 09:34:00.0 +0200
+++ debiman-0.0~git20220907.a582536/debian/install	2024-05-30 03:07:48.0 +0200
@@ -1 +1 @@
-debiman-auxserver.service lib/systemd/system
+debiman-auxserver.service usr/lib/systemd/system

Bug#1054086: lsm: let dh_installsystemd choose the location of units

[Chris Hofstaedtler]

On Wed, May 29, 2024 at 12:57:21PM -0300, Lucas Castro wrote:
> I would like the NMU be canceled.

> cancel lsm_1.0.4-2.1_source.changes
Files removed from 3-day: lsm_1.0.4-2.1_source.changes lsm_1.0.4-2.1.dsc 
lsm_1.0.4-2.1.debian.tar.xz lsm_1.0.4-2.1_arm64.buildinfo

I'm looking forward to your fix landing before the trixie transition
freeze.

Chris

Bug#1051460: crowdsec-custom-bouncer: move systemd units to /usr

[Chris Hofstaedtler]

On Tue, Dec 19, 2023 at 04:36:16AM +0100, Cyril Brulebois wrote:
> Chris Hofstaedtler  (2023-12-19):
> > If you can reasonably expect that the package in question will not
> > change name, or split out or move the systemd unit files in any
> > other way, than strictly from /lib to /usr/lib, then this is safe to
> > do now.
> 
> That's very safe to assume, yes. If that's enough to guarantee that I
> won't actually be generating another problem down the line, I'm happy to
> implement this change.

Yes, having migrated enough packages I (we) believe this is safe.

Please land this in trixie before the transition freeze.

Thanks,
Chris

Bug#1054093: monit: diff for NMU version 1:5.33.0-2.1

[Chris Hofstaedtler]

Control: tags 1054093 + pending


Dear maintainer,

I've prepared an NMU for monit (versioned as 1:5.33.0-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru monit-5.33.0/debian/changelog monit-5.33.0/debian/changelog
--- monit-5.33.0/debian/changelog	2023-08-20 22:27:26.0 +0200
+++ monit-5.33.0/debian/changelog	2024-05-30 02:57:21.0 +0200
@@ -1,3 +1,12 @@
+monit (1:5.33.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Let dh_installsystemd choose the location of units (Closes: #1054093)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:57:21 +0200
+
 monit (1:5.33.0-2) unstable; urgency=medium
 
   * debian/conf-available/:
diff -Nru monit-5.33.0/debian/monit.install monit-5.33.0/debian/monit.install
--- monit-5.33.0/debian/monit.install	2023-08-20 22:26:59.0 +0200
+++ monit-5.33.0/debian/monit.install	2024-05-30 02:57:07.0 +0200
@@ -2,4 +2,3 @@
 debian/conf-available/* etc/monit/conf-available/
 debian/templates/* etc/monit/templates/
 system/bash/monit usr/share/bash-completion/completions/
-system/startup/monit.service lib/systemd/system/
diff -Nru monit-5.33.0/debian/monit.service monit-5.33.0/debian/monit.service
--- monit-5.33.0/debian/monit.service	1970-01-01 01:00:00.0 +0100
+++ monit-5.33.0/debian/monit.service	2023-02-11 11:29:19.0 +0100
@@ -0,0 +1,33 @@
+# This file is systemd template for monit service. To
+# register monit with systemd, place the monit.service file
+# to the /lib/systemd/system/ directory and then start it
+# using systemctl (see bellow).
+#
+# Enable monit to start on boot:
+# systemctl enable monit.service
+#
+# Start monit immediately:
+# systemctl start monit.service
+#
+# Stop monit:
+# systemctl stop monit.service
+#
+# Status:
+# systemctl status monit.service
+
+[Unit]
+Description=Pro-active monitoring utility for unix systems
+After=network-online.target
+Documentation=man:monit(1) https://mmonit.com/wiki/Monit/HowTo
+
+[Service]
+Type=simple
+KillMode=process
+ExecStart=/usr/local/bin/monit -I
+ExecStop=/usr/local/bin/monit quit
+ExecReload=/usr/local/bin/monit reload
+Restart=on-abnormal
+StandardOutput=null
+
+[Install]
+WantedBy=multi-user.target

Bug#1054089: php-defaults: diff for NMU version 93+nmu1

[Chris Hofstaedtler]

Control: tags 1054089 + pending


Dear maintainer,

I've prepared an NMU for php-defaults (versioned as 93+nmu1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru php-defaults-93/debian/changelog php-defaults-93+nmu1/debian/changelog
--- php-defaults-93/debian/changelog	2022-07-13 10:19:37.0 +0200
+++ php-defaults-93+nmu1/debian/changelog	2024-05-30 02:53:37.0 +0200
@@ -1,3 +1,12 @@
+php-defaults (93+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Install systemd units using dh helpers. (Closes: #1054089)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:53:37 +0200
+
 php-defaults (93) unstable; urgency=medium
 
   * Bump the default and supported version to PHP 8.2
diff -Nru php-defaults-93/debian/php-common.install php-defaults-93+nmu1/debian/php-common.install
--- php-defaults-93/debian/php-common.install	2022-07-13 10:19:37.0 +0200
+++ php-defaults-93+nmu1/debian/php-common.install	2024-05-30 02:53:37.0 +0200
@@ -3,6 +3,4 @@
 php-maintscript-helper /usr/lib/php/
 phpenmod /usr/sbin/
 phpquery /usr/sbin/
-phpsessionclean.service /lib/systemd/system/
-phpsessionclean.timer /lib/systemd/system/
 sessionclean /usr/lib/php/
diff -Nru php-defaults-93/debian/php-common.phpsessionclean.service php-defaults-93+nmu1/debian/php-common.phpsessionclean.service
--- php-defaults-93/debian/php-common.phpsessionclean.service	1970-01-01 01:00:00.0 +0100
+++ php-defaults-93+nmu1/debian/php-common.phpsessionclean.service	2022-07-13 10:19:37.0 +0200
@@ -0,0 +1,9 @@
+[Unit]
+Description=Clean php session files
+
+[Service]
+Type=oneshot
+ExecStart=/usr/lib/php/sessionclean
+ProtectHome=true
+ProtectSystem=true
+PrivateTmp=true
diff -Nru php-defaults-93/debian/php-common.phpsessionclean.timer php-defaults-93+nmu1/debian/php-common.phpsessionclean.timer
--- php-defaults-93/debian/php-common.phpsessionclean.timer	1970-01-01 01:00:00.0 +0100
+++ php-defaults-93+nmu1/debian/php-common.phpsessionclean.timer	2022-07-13 10:19:37.0 +0200
@@ -0,0 +1,9 @@
+[Unit]
+Description=Clean PHP session files every 30 mins
+
+[Timer]
+OnCalendar=*-*-* *:09,39:00
+Persistent=true
+
+[Install]
+WantedBy=timers.target
diff -Nru php-defaults-93/debian/rules php-defaults-93+nmu1/debian/rules
--- php-defaults-93/debian/rules	2022-07-13 10:19:37.0 +0200
+++ php-defaults-93+nmu1/debian/rules	2024-05-30 02:53:37.0 +0200
@@ -86,7 +86,8 @@
 	dh_gencontrol --remaining-packages -- -v$(PHP_DEB_VERSION)
 
 override_dh_systemd_enable:
-	dh_systemd_enable --package=php-common phpsessionclean.timer
+	dh_systemd_enable --package=php-common --name phpsessionclean phpsessionclean.timer
+	dh_systemd_enable --package=php-common --name phpsessionclean --no-enable phpsessionclean.service
 
 override_dh_systemd_start:
 	dh_systemd_start --package=php-common phpsessionclean.timer

Bug#1054191: memlockd: diff for NMU version 1.3.1-1.1

[Chris Hofstaedtler]

Control: tags 1054191 + pending


Dear maintainer,

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

Regards.

diff -Nru memlockd-1.3.1/changes.txt memlockd-1.3.1/changes.txt
--- memlockd-1.3.1/changes.txt	2023-09-30 03:49:17.0 +0200
+++ memlockd-1.3.1/changes.txt	2024-05-30 02:50:10.0 +0200
@@ -1,3 +1,12 @@
+memlockd (1.3.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Do not install a possibly empty /lib/systemd/system. (Closes: #1054191)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:50:10 +0200
+
 memlockd (1.3.1-1) unstable; urgency=medium
 
   * Convert to source format 3.0, closes: #1043214
diff -Nru memlockd-1.3.1/debian/changelog memlockd-1.3.1/debian/changelog
--- memlockd-1.3.1/debian/changelog	2023-09-30 03:49:17.0 +0200
+++ memlockd-1.3.1/debian/changelog	2024-05-30 02:50:10.0 +0200
@@ -1,3 +1,12 @@
+memlockd (1.3.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Do not install a possibly empty /lib/systemd/system. (Closes: #1054191)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:50:10 +0200
+
 memlockd (1.3.1-1) unstable; urgency=medium
 
   * Convert to source format 3.0, closes: #1043214
diff -Nru memlockd-1.3.1/debian/dirs memlockd-1.3.1/debian/dirs
--- memlockd-1.3.1/debian/dirs	2012-06-16 07:33:33.0 +0200
+++ memlockd-1.3.1/debian/dirs	2024-05-30 02:49:57.0 +0200
@@ -2,4 +2,3 @@
 etc/default
 etc/memlockd.d
 usr/share/man/man8
-lib/systemd/system

Bug#1054090: zram-tools: diff for NMU version 0.3.3.1-1.2

[Chris Hofstaedtler]

Control: tags 1054090 + pending


Dear maintainer,

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

Regards.

diff -Nru zram-tools-0.3.3.1/debian/changelog zram-tools-0.3.3.1/debian/changelog
--- zram-tools-0.3.3.1/debian/changelog	2022-10-15 12:59:52.0 +0200
+++ zram-tools-0.3.3.1/debian/changelog	2024-05-30 02:51:05.0 +0200
@@ -1,3 +1,12 @@
+zram-tools (0.3.3.1-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Let dh_installsystemd choose the location of the unit (Closes: #1054090)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:51:05 +0200
+
 zram-tools (0.3.3.1-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru zram-tools-0.3.3.1/debian/install zram-tools-0.3.3.1/debian/install
--- zram-tools-0.3.3.1/debian/install	2018-10-11 12:44:12.0 +0200
+++ zram-tools-0.3.3.1/debian/install	2024-05-30 02:51:01.0 +0200
@@ -1,3 +1,2 @@
 zramswap usr/sbin
 conf/zramswap etc/default
-zramswap.service lib/systemd/system
diff -Nru zram-tools-0.3.3.1/debian/rules zram-tools-0.3.3.1/debian/rules
--- zram-tools-0.3.3.1/debian/rules	2018-09-12 11:49:53.0 +0200
+++ zram-tools-0.3.3.1/debian/rules	2024-05-30 02:51:01.0 +0200
@@ -2,3 +2,6 @@
 
 %:
 	dh $@
+
+override_dh_installsystemd:
+	dh_installsystemd --name=zramswap
diff -Nru zram-tools-0.3.3.1/debian/zram-tools.zramswap.service zram-tools-0.3.3.1/debian/zram-tools.zramswap.service
--- zram-tools-0.3.3.1/debian/zram-tools.zramswap.service	1970-01-01 01:00:00.0 +0100
+++ zram-tools-0.3.3.1/debian/zram-tools.zramswap.service	2020-11-02 15:19:01.0 +0100
@@ -0,0 +1,14 @@
+[Unit]
+Description=Linux zramswap setup
+Documentation=man:zramswap(8)
+
+[Service]
+EnvironmentFile=-/etc/default/zramswap
+ExecStart=/usr/sbin/zramswap start
+ExecStop=/usr/sbin/zramswap stop
+ExecReload=/usr/sbin/zramswap restart
+Type=oneshot
+RemainAfterExit=true
+
+[Install]
+WantedBy=multi-user.target

Bug#1063458: open-infrastructure-storage-tools: diff for NMU version 20190301-lts1-5.1

[Chris Hofstaedtler]

Control: tags 1063458 + pending


Dear maintainer,

I've prepared an NMU for open-infrastructure-storage-tools (versioned as 
20190301-lts1-5.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru open-infrastructure-storage-tools-20190301-lts1/debian/changelog open-infrastructure-storage-tools-20190301-lts1/debian/changelog
--- open-infrastructure-storage-tools-20190301-lts1/debian/changelog	2023-02-07 15:31:53.0 +0100
+++ open-infrastructure-storage-tools-20190301-lts1/debian/changelog	2024-05-30 02:44:06.0 +0200
@@ -1,3 +1,12 @@
+open-infrastructure-storage-tools (20190301-lts1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Move files to /usr for DEP17. (Closes: #1063458)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:44:06 +0200
+
 open-infrastructure-storage-tools (20190301-lts1-5) sid; urgency=high
 
   * Uploading to sid, with bumped urgency due to upcoming freeze deadline.
diff -Nru open-infrastructure-storage-tools-20190301-lts1/debian/patches/dep17.patch open-infrastructure-storage-tools-20190301-lts1/debian/patches/dep17.patch
--- open-infrastructure-storage-tools-20190301-lts1/debian/patches/dep17.patch	1970-01-01 01:00:00.0 +0100
+++ open-infrastructure-storage-tools-20190301-lts1/debian/patches/dep17.patch	2024-05-30 02:43:52.0 +0200
@@ -0,0 +1,13 @@
+--- open-infrastructure-storage-tools-20190301-lts1.orig/Makefile
 open-infrastructure-storage-tools-20190301-lts1/Makefile
+@@ -72,8 +72,8 @@
+ 	mkdir -p $(DESTDIR)/etc/logrotate.d
+ 	cp -r share/logrotate/* $(DESTDIR)/etc/logrotate.d
+ 
+-	mkdir -p $(DESTDIR)/lib/systemd/system
+-	cp -r share/systemd/* $(DESTDIR)/lib/systemd/system
++	mkdir -p $(DESTDIR)/usr/lib/systemd/system
++	cp -r share/systemd/* $(DESTDIR)/usr/lib/systemd/system
+ 
+ 	mkdir -p $(DESTDIR)/usr/share/$(PROJECT)/$(PROGRAM)
+ 	cp -r share/ceph-info $(DESTDIR)/usr/share/$(PROJECT)
diff -Nru open-infrastructure-storage-tools-20190301-lts1/debian/patches/series open-infrastructure-storage-tools-20190301-lts1/debian/patches/series
--- open-infrastructure-storage-tools-20190301-lts1/debian/patches/series	2023-02-07 15:31:22.0 +0100
+++ open-infrastructure-storage-tools-20190301-lts1/debian/patches/series	2024-05-30 02:44:02.0 +0200
@@ -1 +1,2 @@
 upstream/0001-ftbfs-asciidoc.patch
+dep17.patch

Bug#1063455: open-infrastructure-compute-tools: diff for NMU version 20221223-3.1

[Chris Hofstaedtler]

Control: tags 1063455 + pending


Dear maintainer,

I've prepared an NMU for open-infrastructure-compute-tools (versioned as 
20221223-3.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru open-infrastructure-compute-tools-20221223/debian/changelog open-infrastructure-compute-tools-20221223/debian/changelog
--- open-infrastructure-compute-tools-20221223/debian/changelog	2023-02-05 16:42:42.0 +0100
+++ open-infrastructure-compute-tools-20221223/debian/changelog	2024-05-30 02:45:16.0 +0200
@@ -1,3 +1,12 @@
+open-infrastructure-compute-tools (20221223-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Move files to /usr for DEP17. (Closes: #1063455)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:45:16 +0200
+
 open-infrastructure-compute-tools (20221223-3) sid; urgency=medium
 
   * Uploading to sid.
diff -Nru open-infrastructure-compute-tools-20221223/debian/patches/dep17.patch open-infrastructure-compute-tools-20221223/debian/patches/dep17.patch
--- open-infrastructure-compute-tools-20221223/debian/patches/dep17.patch	1970-01-01 01:00:00.0 +0100
+++ open-infrastructure-compute-tools-20221223/debian/patches/dep17.patch	2024-05-30 02:45:04.0 +0200
@@ -0,0 +1,13 @@
+--- open-infrastructure-compute-tools-20221223.orig/Makefile
 open-infrastructure-compute-tools-20221223/Makefile
+@@ -142,8 +142,8 @@
+ 	ln -sf stop $(DESTDIR)/usr/libexec/$(PROGRAM)/t
+ 	ln -sf update $(DESTDIR)/usr/libexec/$(PROGRAM)/u
+ 
+-	mkdir -p $(DESTDIR)/lib/systemd/system
+-	cp -r share/systemd/* $(DESTDIR)/lib/systemd/system
++	mkdir -p $(DESTDIR)/usr/lib/systemd/system
++	cp -r share/systemd/* $(DESTDIR)/usr/lib/systemd/system
+ 
+ 	mkdir -p $(DESTDIR)/var/log/$(SOFTWARE)
+ 
diff -Nru open-infrastructure-compute-tools-20221223/debian/patches/series open-infrastructure-compute-tools-20221223/debian/patches/series
--- open-infrastructure-compute-tools-20221223/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ open-infrastructure-compute-tools-20221223/debian/patches/series	2024-05-30 02:45:07.0 +0200
@@ -0,0 +1 @@
+dep17.patch

Bug#1072073: python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py

[Yogeswaran Umasankar]

Hi,

Thank you for noticing. Looks like proto module in nanopb is very
specific to nanopb.

For now, I am planning to declare nanopb in Conflicts for
'python3-proto-plus' binary. Let me know if it might not be advisable.

Cheers!

Bug#1068229: login: remove lastlog, remove pam_lastlog.so from PAM config [patch]

[Chris Hofstaedtler]

Control: tags 1068229 + patch

Hi,

here's a patch to achieve the requested changes.

When this is uploaded, we can have lastlog2 take over.

Please let me know about your plan on uploading.

Chris

diff -Nru shadow-4.13+dfsg1/debian/changelog shadow-4.13+dfsg1/debian/changelog
--- shadow-4.13+dfsg1/debian/changelog	2024-02-04 21:28:27.0 +0100
+++ shadow-4.13+dfsg1/debian/changelog	2024-05-30 02:23:58.0 +0200
@@ -1,3 +1,11 @@
+shadow (1:4.13+dfsg1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop pam_lastlog.so from config. (Closes: #1068229)
+  * Stop installing lastlog binary.
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:23:58 +0200
+
 shadow (1:4.13+dfsg1-4) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru shadow-4.13+dfsg1/debian/login.install shadow-4.13+dfsg1/debian/login.install
--- shadow-4.13+dfsg1/debian/login.install	2024-02-04 21:28:27.0 +0100
+++ shadow-4.13+dfsg1/debian/login.install	2024-05-30 02:23:58.0 +0200
@@ -2,6 +2,5 @@
 usr/share/locale/*/LC_MESSAGES/shadow.mo
 sbin/nologin usr/sbin
 usr/bin/faillog
-usr/bin/lastlog
 usr/bin/newgrp
 bin/login usr/bin
diff -Nru shadow-4.13+dfsg1/debian/login.manpages shadow-4.13+dfsg1/debian/login.manpages
--- shadow-4.13+dfsg1/debian/login.manpages	2024-02-04 21:28:27.0 +0100
+++ shadow-4.13+dfsg1/debian/login.manpages	2024-05-30 02:23:58.0 +0200
@@ -4,7 +4,6 @@
 usr/share/man/*/man5/faillog.5
 usr/share/man/*/man5/login.defs.5
 usr/share/man/*/man8/faillog.8
-usr/share/man/*/man8/lastlog.8
 usr/share/man/*/man8/nologin.8
 usr/share/man/man1/login.1
 usr/share/man/man1/newgrp.1
@@ -12,5 +11,4 @@
 usr/share/man/man5/faillog.5
 usr/share/man/man5/login.defs.5
 usr/share/man/man8/faillog.8
-usr/share/man/man8/lastlog.8
 usr/share/man/man8/nologin.8
diff -Nru shadow-4.13+dfsg1/debian/login.pam shadow-4.13+dfsg1/debian/login.pam
--- shadow-4.13+dfsg1/debian/login.pam	2024-02-04 21:28:27.0 +0100
+++ shadow-4.13+dfsg1/debian/login.pam	2024-05-30 02:23:58.0 +0200
@@ -77,10 +77,6 @@
 # (Replaces the use of /etc/limits in old login)
 sessionrequired   pam_limits.so
 
-# Prints the last login info upon successful login
-# (Replaces the `LASTLOG_ENAB' option from login.defs)
-sessionoptional   pam_lastlog.so
-
 # Prints the status of the user's mailbox upon successful login
 # (Replaces the `MAIL_CHECK_ENAB' option from login.defs). 
 #
diff -Nru shadow-4.13+dfsg1/debian/not-installed shadow-4.13+dfsg1/debian/not-installed
--- shadow-4.13+dfsg1/debian/not-installed	2024-02-04 21:28:27.0 +0100
+++ shadow-4.13+dfsg1/debian/not-installed	2024-05-30 02:23:58.0 +0200
@@ -15,6 +15,7 @@
 etc/pam.d/useradd
 etc/pam.d/userdel
 etc/pam.d/usermod
+usr/bin/lastlog
 usr/bin/sg
 usr/lib/*/libsubid.la
 usr/sbin/logoutd
@@ -25,6 +26,7 @@
 usr/share/man/*/man3/getspnam.3
 usr/share/man/*/man3/shadow.3
 usr/share/man/*/man5/suauth.5
+usr/share/man/*/man8/lastlog.8
 usr/share/man/*/man8/logoutd.8
 usr/share/man/man1/groups.1
 usr/share/man/man1/logoutd.1
@@ -32,5 +34,6 @@
 usr/share/man/man3/getspnam.3
 usr/share/man/man3/shadow.3
 usr/share/man/man5/suauth.5
+usr/share/man/man8/lastlog.8
 usr/share/man/man8/logoutd.8
 

Bug#1064238: fuse-umfuse-ext2: diff for NMU version 0.4-1.5

[Chris Hofstaedtler]

Control: tags 1064238 + pending


Dear maintainer,

I've prepared an NMU for fuse-umfuse-ext2 (versioned as 0.4-1.5) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru fuse-umfuse-ext2-0.4/debian/changelog fuse-umfuse-ext2-0.4/debian/changelog
--- fuse-umfuse-ext2-0.4/debian/changelog	2023-09-29 01:48:00.0 +0200
+++ fuse-umfuse-ext2-0.4/debian/changelog	2024-05-30 02:19:03.0 +0200
@@ -1,3 +1,12 @@
+fuse-umfuse-ext2 (0.4-1.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * DEP17: Move files to /usr. (Closes: #1064238)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:19:03 +0200
+
 fuse-umfuse-ext2 (0.4-1.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fuse-umfuse-ext2-0.4/debian/patches/series fuse-umfuse-ext2-0.4/debian/patches/series
--- fuse-umfuse-ext2-0.4/debian/patches/series	2023-09-29 01:48:00.0 +0200
+++ fuse-umfuse-ext2-0.4/debian/patches/series	2024-05-30 02:18:57.0 +0200
@@ -1 +1,2 @@
 fuse-ext2.h.patch
+usrmove.patch
diff -Nru fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch
--- fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch	1970-01-01 01:00:00.0 +0100
+++ fuse-umfuse-ext2-0.4/debian/patches/usrmove.patch	2024-05-30 02:18:57.0 +0200
@@ -0,0 +1,22 @@
+--- fuse-umfuse-ext2-0.4.orig/fuse-ext2/Makefile.am
 fuse-umfuse-ext2-0.4/fuse-ext2/Makefile.am
+@@ -283,7 +283,7 @@
+ if LINUX
+ install-exec-local:
+ 	$(INSTALL) -d "$(DESTDIR)/usr/sbin"
+-	$(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" "$(DESTDIR)/sbin/mount.fuse-ext2"
++	$(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" "$(DESTDIR)/$(sbindir)/mount.fuse-ext2"
+ endif
+ 
+ dist_man1_MANS = fuse-ext2.1
+--- fuse-umfuse-ext2-0.4.orig/fuse-ext2/Makefile.in
 fuse-umfuse-ext2-0.4/fuse-ext2/Makefile.in
+@@ -1884,7 +1884,7 @@
+ #endif
+ @LINUX_TRUE@install-exec-local:
+ @LINUX_TRUE@	$(INSTALL) -d "$(DESTDIR)/usr/sbin"
+-@LINUX_TRUE@	$(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" "$(DESTDIR)/sbin/mount.fuse-ext2"
++@LINUX_TRUE@	$(LN_S) -f "$(DESTDIR)/$(bindir)/fuse-ext2" "$(DESTDIR)/$(sbindir)/mount.fuse-ext2"
+ 
+ # Tell versions [3.59,3.63) of GNU make to not export all variables.
+ # Otherwise a system limit (for SysV at least) may be exceeded.
diff -Nru fuse-umfuse-ext2-0.4/debian/rules fuse-umfuse-ext2-0.4/debian/rules
--- fuse-umfuse-ext2-0.4/debian/rules	2023-09-29 01:47:05.0 +0200
+++ fuse-umfuse-ext2-0.4/debian/rules	2024-05-30 02:18:57.0 +0200
@@ -3,15 +3,17 @@
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/autotools.mk
 
+DEB_CONFIGURE_EXTRA_FLAGS=--exec-prefix='$${prefix}'
+
 common-install-prehook-arch common-install-prehook-indep::
-	mkdir -p debian/tmp/sbin
+	mkdir -p debian/tmp/usr/sbin
 
 install/fuseext2::
 	dh_link -pfuseext2 /usr/share/man/man1/fuse-ext2.1 /usr/share/man/man8/mount.fuse-ext2.8
-	dh_link -pfuseext2 /usr/bin/fuse-ext2 /sbin/mount.fuse-ext2
+	dh_link -pfuseext2 /usr/bin/fuse-ext2 /usr/sbin/mount.fuse-ext2
 	# Compatibility symlinks for versions up to 0.3.
 	dh_link -pfuseext2 /usr/bin/fuse-ext2 /usr/bin/fuseext2
-	dh_link -pfuseext2 /sbin/mount.fuse-ext2 /sbin/mount.fuseext2
+	dh_link -pfuseext2 /usr/sbin/mount.fuse-ext2 /usr/sbin/mount.fuseext2
 	dh_link -pfuseext2 /usr/share/man/man1/fuse-ext2.1 /usr/share/man/man1/fuseext2.1
 	dh_link -pfuseext2 /usr/share/man/man8/mount.fuse-ext2.8 /usr/share/man/man8/mount.fuseext2.8
 	dh_compress -pfuseext2

Bug#1068229: Bug#1066060: libpam-modules: pam_lastlog.so missing

[Chris Hofstaedtler]

Control: retitle -1 login: remove lastlog, remove pam_lastlog.so from PAM config
Control: severity -1 important

Dear shadow maintainers,

as originally requested, please drop pam_lastlog.so from the PAM
config.

Please also drop the lastlog binary, which isn't very useful when
the data it is reading is not updated anymore.

Chris

Bug#1066060: libpam-modules: pam_lastlog.so missing

[Chris Hofstaedtler]

Control: retitle -1 libpam-modules: pam_lastlog.so missing

Apologies, this was the wrong half of the bug.

I think in src:pam not much is to be done, except the NEWS.Debian
entry?

Chris

Bug#1061489: libpam-ccreds: diff for NMU version 10-8.1

[Chris Hofstaedtler]

Control: tags 1061489 + pending


Dear maintainer,

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

Regards.

diff -Nru libpam-ccreds-10/debian/changelog libpam-ccreds-10/debian/changelog
--- libpam-ccreds-10/debian/changelog	2019-10-26 00:28:29.0 +0200
+++ libpam-ccreds-10/debian/changelog	2024-05-30 02:15:58.0 +0200
@@ -1,3 +1,12 @@
+libpam-ccreds (10-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Michael Biebl ]
+  * Install PAM modules and binaries into /usr (Closes: #1061489)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:15:58 +0200
+
 libpam-ccreds (10-8) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru libpam-ccreds-10/debian/dirs libpam-ccreds-10/debian/dirs
--- libpam-ccreds-10/debian/dirs	2009-08-01 19:57:03.0 +0200
+++ libpam-ccreds-10/debian/dirs	1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-usr/sbin
-lib/security
diff -Nru libpam-ccreds-10/debian/libpam-ccreds.lintian-overrides libpam-ccreds-10/debian/libpam-ccreds.lintian-overrides
--- libpam-ccreds-10/debian/libpam-ccreds.lintian-overrides	2009-08-01 19:57:03.0 +0200
+++ libpam-ccreds-10/debian/libpam-ccreds.lintian-overrides	2024-05-30 02:15:54.0 +0200
@@ -1,2 +1,2 @@
 # yes, we know it's suid, that's the whole point...
-libpam-ccreds: setuid-binary sbin/ccreds_chkpwd 4755 root/root
+libpam-ccreds: setuid-binary usr/sbin/ccreds_chkpwd 4755 root/root
diff -Nru libpam-ccreds-10/debian/rules libpam-ccreds-10/debian/rules
--- libpam-ccreds-10/debian/rules	2019-10-26 00:27:03.0 +0200
+++ libpam-ccreds-10/debian/rules	2024-05-30 02:15:54.0 +0200
@@ -4,8 +4,6 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 DEB_CONFIGURE_EXTRA_ARGS := \
-	--libdir=/lib/$(DEB_HOST_GNU_TYPE) \
-	--sbindir=/sbin \
 	--enable-gcrypt \
 	$(NULL)
 
@@ -17,16 +15,15 @@
 
 override_dh_auto_install:
 	dh_auto_install
-	chown root:root debian/libpam-ccreds/sbin/ccreds_chkpwd
-	chmod 4755 debian/libpam-ccreds/sbin/ccreds_chkpwd
+	chown root:root debian/libpam-ccreds/usr/sbin/ccreds_chkpwd
+	chmod 4755 debian/libpam-ccreds/usr/sbin/ccreds_chkpwd
 
 	mkdir -p debian/libpam-ccreds/usr/share/pam-configs
 	install -m 0644 debian/libpam-ccreds.pam-auth-update.ccreds-save \
 		debian/libpam-ccreds/usr/share/pam-configs/ccreds-save
 	install -m 0644 debian/libpam-ccreds.pam-auth-update.ccreds-check \
 		debian/libpam-ccreds/usr/share/pam-configs/ccreds-check
-	rmdir debian/libpam-ccreds/lib/security
 
 override_dh_fixperms:
-	dh_fixperms -X/sbin/ccreds_chkpwd
+	dh_fixperms -X/usr/sbin/ccreds_chkpwd
 

Bug#1058859: teensy-loader-cli: diff for NMU version 2.2-1.1

[Chris Hofstaedtler]

Control: tags 1058859 + pending


Dear maintainer,

I've prepared an NMU for teensy-loader-cli (versioned as 2.2-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru teensy-loader-cli-2.2/debian/49-teensy.rules teensy-loader-cli-2.2/debian/49-teensy.rules
--- teensy-loader-cli-2.2/debian/49-teensy.rules	2022-01-11 14:30:43.0 +0100
+++ teensy-loader-cli-2.2/debian/49-teensy.rules	1970-01-01 01:00:00.0 +0100
@@ -1,38 +0,0 @@
-# UDEV Rules for Teensy boards, http://www.pjrc.com/teensy/
-#
-# The latest version of this file may be found at:
-#   http://www.pjrc.com/teensy/49-teensy.rules
-#
-# This file must be placed at:
-#
-# /etc/udev/rules.d/49-teensy.rules(preferred location)
-#   or
-# /lib/udev/rules.d/49-teensy.rules(req'd on some broken systems)
-#
-# To install, type this command in a terminal:
-#   sudo cp 49-teensy.rules /etc/udev/rules.d/49-teensy.rules
-#
-# Or use the alternate way (from this forum message) to download and install:
-#   https://forum.pjrc.com/threads/45595?p=150445=1#post150445
-#
-# After this file is installed, physically unplug and reconnect Teensy.
-#
-ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", ENV{ID_MM_DEVICE_IGNORE}="1"
-ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789A]?", ENV{MTP_NO_PROBE}="1"
-SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789ABCD]?", TAG+="uaccess", TAG+="udev-acl"
-KERNEL=="ttyACM*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", TAG+="uaccess", TAG+="udev-acl"
-#
-# If you share your linux system with other users, or just don't like the
-# idea of write permission for everybody, you can replace MODE:="0666" with
-# OWNER:="yourusername" to create the device owned by you, or with
-# GROUP:="somegroupname" and mange access using standard unix groups.
-#
-#
-# If using USB Serial you get a new device each time (Ubuntu 9.10)
-# eg: /dev/ttyACM0, ttyACM1, ttyACM2, ttyACM3, ttyACM4, etc
-#apt-get remove --purge modemmanager (reboot may be necessary)
-#
-# Older modem proding (eg, Ubuntu 9.04) caused very slow serial device detection.
-# To fix, add this near top of /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules
-#   SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789]?", GOTO="nm_modem_probe_end" 
-#
diff -Nru teensy-loader-cli-2.2/debian/changelog teensy-loader-cli-2.2/debian/changelog
--- teensy-loader-cli-2.2/debian/changelog	2022-01-15 21:59:54.0 +0100
+++ teensy-loader-cli-2.2/debian/changelog	2024-05-30 02:13:46.0 +0200
@@ -1,3 +1,10 @@
+teensy-loader-cli (2.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Let dh_installudev install udev rules. (Closes: #1058859)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:13:46 +0200
+
 teensy-loader-cli (2.2-1) unstable; urgency=medium
 
   * New upstream release, contained all debian patches
diff -Nru teensy-loader-cli-2.2/debian/install teensy-loader-cli-2.2/debian/install
--- teensy-loader-cli-2.2/debian/install	2022-01-11 14:30:43.0 +0100
+++ teensy-loader-cli-2.2/debian/install	2024-05-30 02:13:43.0 +0200
@@ -1,2 +1 @@
 teensy_loader_cli /usr/bin/
-debian/49-teensy.rules /lib/udev/rules.d/
diff -Nru teensy-loader-cli-2.2/debian/rules teensy-loader-cli-2.2/debian/rules
--- teensy-loader-cli-2.2/debian/rules	2022-01-11 14:30:43.0 +0100
+++ teensy-loader-cli-2.2/debian/rules	2024-05-30 02:13:43.0 +0200
@@ -12,3 +12,6 @@
 
 %:
 	dh $@
+
+override_dh_installudev:
+	dh_installudev --priority=49 --name=teensy
diff -Nru teensy-loader-cli-2.2/debian/teensy-loader-cli.teensy.udev teensy-loader-cli-2.2/debian/teensy-loader-cli.teensy.udev
--- teensy-loader-cli-2.2/debian/teensy-loader-cli.teensy.udev	1970-01-01 01:00:00.0 +0100
+++ teensy-loader-cli-2.2/debian/teensy-loader-cli.teensy.udev	2024-05-30 02:13:43.0 +0200
@@ -0,0 +1,38 @@
+# UDEV Rules for Teensy boards, http://www.pjrc.com/teensy/
+#
+# The latest version of this file may be found at:
+#   http://www.pjrc.com/teensy/49-teensy.rules
+#
+# This file must be placed at:
+#
+# /etc/udev/rules.d/49-teensy.rules(preferred location)
+#   or
+# /lib/udev/rules.d/49-teensy.rules(req'd on some broken systems)
+#
+# To install, type this command in a terminal:
+#   sudo cp 49-teensy.rules /etc/udev/rules.d/49-teensy.rules
+#
+# Or use the alternate way (from this forum message) to download and install:
+#   https://forum.pjrc.com/threads/45595?p=150445=1#post150445
+#
+# After this file is installed, physically unplug and reconnect Teensy.
+#
+ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", ENV{ID_MM_DEVICE_IGNORE}="1"
+ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789A]?", ENV{MTP_NO_PROBE}="1"
+SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789ABCD]?", TAG+="uaccess", TAG+="udev-acl"
+KERNEL=="ttyACM*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", TAG+="uaccess", 

Bug#1059379: f2fs-tools: diff for NMU version 1.16.0-1.1

[Chris Hofstaedtler]

Control: tags 1059379 + pending


Dear maintainer,

I've prepared an NMU for f2fs-tools (versioned as 1.16.0-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru f2fs-tools-1.16.0/debian/changelog f2fs-tools-1.16.0/debian/changelog
--- f2fs-tools-1.16.0/debian/changelog	2023-07-17 06:03:45.0 +0200
+++ f2fs-tools-1.16.0/debian/changelog	2024-05-30 02:10:23.0 +0200
@@ -1,3 +1,10 @@
+f2fs-tools (1.16.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install files into /usr instead of /. (Closes: #1059379)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 02:10:23 +0200
+
 f2fs-tools (1.16.0-1) unstable; urgency=medium
 
   [ Vincent Cheng ]
diff -Nru f2fs-tools-1.16.0/debian/f2fs-tools.install f2fs-tools-1.16.0/debian/f2fs-tools.install
--- f2fs-tools-1.16.0/debian/f2fs-tools.install	2023-07-17 06:02:17.0 +0200
+++ f2fs-tools-1.16.0/debian/f2fs-tools.install	2024-05-30 02:10:20.0 +0200
@@ -1,4 +1,4 @@
 # All but sbin/sg_write_buffer
-sbin/*f2fs*
+usr/sbin/*f2fs*
 
 usr/share/man/man8/*.8
diff -Nru f2fs-tools-1.16.0/debian/f2fs-tools-udeb.install f2fs-tools-1.16.0/debian/f2fs-tools-udeb.install
--- f2fs-tools-1.16.0/debian/f2fs-tools-udeb.install	2023-07-17 06:02:17.0 +0200
+++ f2fs-tools-1.16.0/debian/f2fs-tools-udeb.install	2024-05-30 02:10:20.0 +0200
@@ -1,2 +1,2 @@
 # All but sbin/sg_write_buffer
-sbin/*f2fs*
+usr/sbin/*f2fs*
diff -Nru f2fs-tools-1.16.0/debian/rules f2fs-tools-1.16.0/debian/rules
--- f2fs-tools-1.16.0/debian/rules	2023-07-17 06:02:17.0 +0200
+++ f2fs-tools-1.16.0/debian/rules	2024-05-30 02:10:20.0 +0200
@@ -10,8 +10,8 @@
 	dh $@
 
 override_dh_auto_configure:
-	dh_auto_configure -- --sbindir=/sbin --disable-shared \
-		--with-root-libdir=/lib/$(DEB_HOST_MULTIARCH)
+	dh_auto_configure -- --sbindir=/usr/sbin --disable-shared \
+		--with-root-libdir=/usr/lib/$(DEB_HOST_MULTIARCH)
 
 # dh_dwz when run on f2fs-tools-udeb ends up installing the
 # /usr/lib/debug/.dwz files into the udeb.  I think that's a bug,

Bug#1072189: Acknowledgement (apt: typo in apt.conf(5))

[Noah Meyerhans]

Control: tags -1 + patch

Fix is at https://salsa.debian.org/apt-team/apt/-/merge_requests/353

Bug#1058857: alsa-tools: diff for NMU version 1.2.11-1.1

[Chris Hofstaedtler]

Control: tags 1058857 + pending


Dear maintainer,

I've prepared an NMU for alsa-tools (versioned as 1.2.11-1.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru alsa-tools-1.2.11/debian/alsa-firmware-loaders.dirs alsa-tools-1.2.11/debian/alsa-firmware-loaders.dirs
--- alsa-tools-1.2.11/debian/alsa-firmware-loaders.dirs	2019-11-07 00:42:01.0 +0100
+++ alsa-tools-1.2.11/debian/alsa-firmware-loaders.dirs	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-/lib/udev/rules.d
diff -Nru alsa-tools-1.2.11/debian/alsa-firmware-loaders.udev alsa-tools-1.2.11/debian/alsa-firmware-loaders.udev
--- alsa-tools-1.2.11/debian/alsa-firmware-loaders.udev	2021-09-09 02:44:36.0 +0200
+++ alsa-tools-1.2.11/debian/alsa-firmware-loaders.udev	2024-05-30 01:51:59.0 +0200
@@ -1,18 +1,18 @@
 ###
 # Description:   udev rule to load TASCAM US-122 usb sound card.
 # Created:   Wed, 12 Sep 2007 17:05:25 +0200
-# Last modified: Thu, 21 Jan 2010 21:21:12 +0100
+# Last modified: Sun, 17 Dec 2023 01:35:53 +0100
 # File:  /etc/udev/alsa-firmware-loaders.rules
 ###
 
 # TASCAM US-428 usb sound card.
-SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8000", RUN+="/lib/udev/tascam_fw"
+SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8000", RUN+="tascam_fw"
 # TASCAM US-224 usb sound card.
-SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8004", RUN+="/lib/udev/tascam_fw"
+SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8004", RUN+="tascam_fw"
 # TASCAM US-112 usb sound card.
-SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8006", RUN+="/lib/udev/tascam_fw"
+SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="1604", ATTR{idProduct}=="8006", RUN+="tascam_fw"
 
-SUBSYSTEM=="usb", ACTION=="add", ATTR{id}=="USX2Y", RUN+="/lib/udev/tascam_fpga"
+SUBSYSTEM=="usb", ACTION=="add", ATTR{id}=="USX2Y", RUN+="tascam_fpga"
 
 # vim:tw=160:syntax=udevrules
 
diff -Nru alsa-tools-1.2.11/debian/changelog alsa-tools-1.2.11/debian/changelog
--- alsa-tools-1.2.11/debian/changelog	2024-03-04 23:13:35.0 +0100
+++ alsa-tools-1.2.11/debian/changelog	2024-05-30 01:58:32.0 +0200
@@ -1,3 +1,13 @@
+alsa-tools (1.2.11-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use udev.pc to place udev files. (Closes: #1058857)
+  * Avoid hard-coding path to udev helpers in udev rules, as it will
+change.
+  * Update firmware path to /usr/lib/firmware.
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:58:32 +0200
+
 alsa-tools (1.2.11-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru alsa-tools-1.2.11/debian/control alsa-tools-1.2.11/debian/control
--- alsa-tools-1.2.11/debian/control	2023-05-05 00:30:53.0 +0200
+++ alsa-tools-1.2.11/debian/control	2024-05-30 01:51:59.0 +0200
@@ -10,7 +10,9 @@
libasound2-dev (>= 1.0.24.1),
libfltk1.3-dev,
libgtk-3-dev,
-   libgtk2.0-dev
+   libgtk2.0-dev,
+   pkgconf,
+   systemd-dev,
 Standards-Version: 4.6.0
 Homepage: https://www.alsa-project.org/
 Vcs-Git: https://salsa.debian.org/alsa-team/alsa-tools.git
diff -Nru alsa-tools-1.2.11/debian/patches/firmware_locations.patch alsa-tools-1.2.11/debian/patches/firmware_locations.patch
--- alsa-tools-1.2.11/debian/patches/firmware_locations.patch	2021-09-09 02:44:36.0 +0200
+++ alsa-tools-1.2.11/debian/patches/firmware_locations.patch	2024-05-30 01:51:59.0 +0200
@@ -1,5 +1,5 @@
 Author: Elimar Riesebieter 
-Description: Set firmware location to /lib/firmware, as expected in Debian.
+Description: Set firmware location to /usr/lib/firmware, as expected in Debian.
 Forwarded: no
 
 Index: alsa-tools/hdsploader/Makefile.in
@@ -11,7 +11,7 @@
  # # Process this file with automake to produce Makefile.in.
  MYNAME = hdsploader
 -AM_CFLAGS = -DDATAPATH=\"$(datadir)/alsa/firmware/$(MYNAME)\"
-+AM_CFLAGS = -DDATAPATH=\"/lib/firmware/$(MYNAME)\"
++AM_CFLAGS = -DDATAPATH=\"/usr/lib/firmware/$(MYNAME)\"
  hdsploader_SOURCES = hdsploader.c
  EXTRA_DIST = gitcompile depcomp
  all: all-am
@@ -24,7 +24,7 @@
  AUTOMAKE_OPTIONS = 1.3 foreign
  MYNAME = mixartloader
 -AM_CFLAGS = -DDATAPATH=\"$(datadir)/alsa/firmware/$(MYNAME)\"
-+AM_CFLAGS = -DDATAPATH=\"/lib/firmware/$(MYNAME)\"
++AM_CFLAGS = -DDATAPATH=\"/usr/lib/firmware/$(MYNAME)\"
  mixartloader_SOURCES = mixartloader.c
  EXTRA_DIST = gitcompile depcomp
  all: all-am
@@ -37,7 +37,7 @@
  AUTOMAKE_OPTIONS = 1.3 foreign
  MYNAME = pcxhrloader
 -AM_CFLAGS = -DDATAPATH=\"$(datadir)/alsa/firmware/$(MYNAME)\"
-+AM_CFLAGS = -DDATAPATH=\"/lib/firmware/$(MYNAME)\"
++AM_CFLAGS = 

Bug#1072189: apt: typo in apt.conf(5)

[Noah Meyerhans]

Package: apt
Version: 2.9.4
Severity: minor

The Snapshots::URI scope documentation in apt.conf(5) has a minor typo in which
the @SNAPSHOTID@ placeholder is missing the trailing '@'.

Bug#1057804: libguestfs: diff for NMU version 1:1.52.0-6.1

[Chris Hofstaedtler]

Control: tags 1057804 + patch
Control: tags 1057804 + pending


Dear maintainer,

I've prepared an NMU for libguestfs (versioned as 1:1.52.0-6.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru libguestfs-1.52.0/debian/changelog libguestfs-1.52.0/debian/changelog
--- libguestfs-1.52.0/debian/changelog	2024-05-18 22:26:51.0 +0200
+++ libguestfs-1.52.0/debian/changelog	2024-05-30 01:35:29.0 +0200
@@ -1,3 +1,11 @@
+libguestfs (1:1.52.0-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install 99-guestfs-serial.rules into /usr/lib/udev/rules.d (Closes:
+#1057804)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:35:29 +0200
+
 libguestfs (1:1.52.0-6) unstable; urgency=medium
 
   * Add util-linux-extra to appliance list (Closes: #1071313)
diff -Nru libguestfs-1.52.0/debian/guestfsd.install libguestfs-1.52.0/debian/guestfsd.install
--- libguestfs-1.52.0/debian/guestfsd.install	2023-07-23 13:30:56.0 +0200
+++ libguestfs-1.52.0/debian/guestfsd.install	2024-05-30 01:34:40.0 +0200
@@ -1,3 +1,3 @@
 usr/sbin/guestfsd
 usr/share/man/man8/guestfsd.8*
-lib/udev/rules.d/99-guestfs-serial.rules
+usr/lib/udev/rules.d/99-guestfs-serial.rules
diff -Nru libguestfs-1.52.0/debian/patches/series libguestfs-1.52.0/debian/patches/series
--- libguestfs-1.52.0/debian/patches/series	2024-05-18 22:26:51.0 +0200
+++ libguestfs-1.52.0/debian/patches/series	2024-05-30 01:35:09.0 +0200
@@ -20,3 +20,4 @@
 Only-set-rtc-driftfix-slew-on-x86-architectures.patch
 Add-dhcpcd-to-Debian-package-list.patch
 Add-util-linux-extra-to-appliance-list.patch
+udev-rules-path.patch
diff -Nru libguestfs-1.52.0/debian/patches/udev-rules-path.patch libguestfs-1.52.0/debian/patches/udev-rules-path.patch
--- libguestfs-1.52.0/debian/patches/udev-rules-path.patch	1970-01-01 01:00:00.0 +0100
+++ libguestfs-1.52.0/debian/patches/udev-rules-path.patch	2024-05-30 01:35:22.0 +0200
@@ -0,0 +1,13 @@
+Index: libguestfs-1.52.0/appliance/Makefile.am
+===
+--- libguestfs-1.52.0.orig/appliance/Makefile.am
 libguestfs-1.52.0/appliance/Makefile.am
+@@ -157,7 +157,7 @@ supermin.d/udev-rules.tar.gz: 99-guestfs
+ # If installing the daemon, install the udev rules too.
+ 
+ if INSTALL_DAEMON
+-udevrulesdir = /lib/udev/rules.d
++udevrulesdir = /usr/lib/udev/rules.d
+ udevrules_DATA = 99-guestfs-serial.rules
+ endif
+ 

Bug#1072188: Package error

[Peter Carter]

Package: installation-reports

Boot method: 
Image version: 
Date: 

Machine: Dell 7020
Processor:Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
Memory: 16G
Partitions:
filesystem Type 1K-blocks Used Available Use% Mounted on 
udev   devtmpfs   8108416    0   8108416   0% /dev tmpfs 
 tmpfs  1628976 1552   1627424   1% /run /dev/sda3 
 btrfs    468253696 32781716 430568940   8% / tmpfs  tmpfs 
 8144876    0   8144876   0% /dev/shm tmpfs  tmpfs 
5120   16  5104   1% /run/lock efivarfs   efivarfs 
  128   96    28  78% /sys/firmware/efi/efivars /dev/sdb1 
 btrfs    976761560 5920 974597824   1% /data /dev/sda1 
 vfat    497684 4480    493204   1% /boot/efi overlay 
   overlay  468253696 32781716 430568940   8% 
/var/lib/docker/overlay2/afa24d7e3210883370c5732 
914467d97f210df47b7a7635495e899928a72/merged tmpfs  tmpfs 
 1628972  232   1628740   1% /run/user/1000


Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor 
DRAM Controller [8086:0c00] (rev 06)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: hsw_uncore 00:02.0 VGA 
compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller [8086:0412] (rev 06) 
   DeviceName:  Onboard IGD    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: i915    Kernel modules: 
i915 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor HD Audio Controller [808 6:0c0c] (rev 06) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
snd_hda_intel    Kernel modules: snd_hda_intel 00:14.0 USB 
controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI [8086:8c31] (rev 04)    Subsystem: Dell Device [1028:05a5] 
   Kernel driver in use: xhci_hcd    Kernel modules: xhci_pci 
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 
Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
mei_me    Kernel modules: mei_me 00:19.0 Ethernet controller [0200]: 
Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 04) 
   DeviceName:  Onboard LAN    Subsystem: Dell Device 
[1028:05a4]    Kernel driver in use: e1000e    Kernel modules: 
e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 
Series Chipset Family USB EHCI #2 [8086:8c2d] ( rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
ehci-pci    Kernel modules: ehci_pci 00:1b.0 Audio device [0403]: 
Intel Corporation 8 Series/C220 Series Chipset High Definition Audio 
Controller [ 8086:8c20] (rev 04)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: snd_hda_intel    Kernel 
modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 8 
Series/C220 Series Chipset Family PCI Express Root Port #1 [808 6:8c10] 
(rev d4)    Subsystem: Dell Device [1028:05a5]    Kernel driver 
in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 8 
Series/C220 Series Chipset Family PCI Express Root Port #5 [808 6:8c18] 
(rev d4)    Subsystem: Dell Device [1028:05a5]    Kernel driver 
in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 8 
Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] ( rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
ehci-pci    Kernel modules: ehci_pci 00:1f.0 ISA bridge [0601]: 
Intel Corporation Q87 Express LPC Controller [8086:8c4e] (rev 04) 
   Subsystem: Dell Device [1028:05a5]    Kernel driver in use: 
lpc_ich    Kernel modules: lpc_ich 00:1f.2 SATA controller [0106]: 
Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA 
Controller 1 [AHCI mode] [8086:8c02] (rev 04)    DeviceName: 
 Onboard SATA controller #1    Subsystem: Dell Device [1028:05a5] 
   Kernel driver in use: ahci    Kernel modules: ahci 00:1f.3 
SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family 
SMBus Controller [8086:8c22] (rev 04)    Subsystem: Dell Device 
[1028:05a5]    Kernel driver in use: i801_smbus    Kernel 
modules: i2c_i801 02:00.0 Network controller [0280]: Intel Corporation 
Wireless 7265 [8086:095a] (rev 59)    Subsystem: Intel Corporation 
Dual Band Wireless-AC 7265 [Stone Peak 2 AC] [8086:5010]    Kernel 
driver in use: iwlwifi    Kernel modules: iwlwifi


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

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   

Bug#1061342: gridengine: diff for NMU version 8.1.9+dfsg-11.1

[Chris Hofstaedtler]

Control: tags 1061342 + pending


Dear maintainer,

I've prepared an NMU for gridengine (versioned as 8.1.9+dfsg-11.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru gridengine-8.1.9+dfsg/debian/changelog gridengine-8.1.9+dfsg/debian/changelog
--- gridengine-8.1.9+dfsg/debian/changelog	2023-08-13 17:56:03.0 +0200
+++ gridengine-8.1.9+dfsg/debian/changelog	2024-05-30 01:41:12.0 +0200
@@ -1,3 +1,12 @@
+gridengine (8.1.9+dfsg-11.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Michael Biebl ]
+  * Install PAM modules into /usr (DEP 17 M2). (Closes: #1061342)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:41:12 +0200
+
 gridengine (8.1.9+dfsg-11) unstable; urgency=medium
 
   * Team upload.
diff -Nru gridengine-8.1.9+dfsg/debian/gridengine-exec.install gridengine-8.1.9+dfsg/debian/gridengine-exec.install
--- gridengine-8.1.9+dfsg/debian/gridengine-exec.install	2023-08-13 17:40:33.0 +0200
+++ gridengine-8.1.9+dfsg/debian/gridengine-exec.install	2024-05-30 01:41:11.0 +0200
@@ -1,3 +1,3 @@
 debian/tmp/usr/bin/*/sge_execd		usr/lib/gridengine
 debian/tmp/usr/bin/*/sge_*shepherd	usr/lib/gridengine
-/lib/*/security/*.so
+usr/lib/*/security/*.so
diff -Nru gridengine-8.1.9+dfsg/debian/rules gridengine-8.1.9+dfsg/debian/rules
--- gridengine-8.1.9+dfsg/debian/rules	2023-08-13 17:40:33.0 +0200
+++ gridengine-8.1.9+dfsg/debian/rules	2024-05-30 01:41:11.0 +0200
@@ -66,7 +66,7 @@
 override_dh_auto_install:
 	install -d debian/tmp/usr
 	install -d debian/tmp/usr/share
-	install -d debian/tmp/lib/$(DEB_HOST_GNU_TYPE)/security
+	install -d debian/tmp/usr/lib/$(DEB_HOST_GNU_TYPE)/security
 	cd source && /usr/bin/yes | ${PRECMD} scripts/distinst \
 	-basedir ${CURDIR}/debian \
 	-vdir tmp/usr \
@@ -102,7 +102,7 @@
 	mandb -u -c debian/tmp/usr/share/man
 	chmod 755 debian/scripts/init_cluster debian/gridengine-wrapper
 	cp source/clients/qmon/qmon.desktop debian
-	mv debian/tmp/usr/lib/*/pam_sge* debian/tmp/lib/$(DEB_HOST_GNU_TYPE)/security
+	mv debian/tmp/usr/lib/*/pam_sge* debian/tmp/usr/lib/$(DEB_HOST_GNU_TYPE)/security
 
 override_dh_installinit:
 	dh_installinit -p gridengine-master

Bug#1061359: not fixed in unstable

[Chris Hofstaedtler]

Hi,

are you working on this?
Please make sure fixed packages are in trixie before the transition
freeze.

Chris

On Sat, Mar 02, 2024 at 09:58:35PM +0100, Chris Hofstaedtler wrote:
> Control: reopen -1
> Control: found -1 zfs-linux/2.2.3-1
> 
> Hi,
> 
> 2.2.3-1 in unstable still installs a lot of files outside of /usr.
> 
> /srv/debian-mirror/mirror/pool/contrib/z/zfs-linux/libnvpair3linux_2.2.3-1_amd64.deb
> drwxr-xr-x root/root 0 2024-02-23 14:28 ./lib/
> drwxr-xr-x root/root 0 2024-02-23 14:28 ./lib/x86_64-linux-gnu/
> -rw-r--r-- root/root104400 2024-02-23 14:28 
> ./lib/x86_64-linux-gnu/libnvpair.so.3.0.0
> lrwxrwxrwx root/root 0 2024-02-23 14:28 
> ./lib/x86_64-linux-gnu/libnvpair.so.3 -> libnvpair.so.3.0.0
[..]

Bug#1065307: r4d: diff for NMU version 1.7-4.1

[Chris Hofstaedtler]

Control: tags 1065307 + patch
Control: tags 1065307 + pending


Dear maintainer,

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

Regards.

diff -Nru r4d-1.7/debian/changelog r4d-1.7/debian/changelog
--- r4d-1.7/debian/changelog	2023-05-17 17:21:39.0 +0200
+++ r4d-1.7/debian/changelog	2024-05-30 01:29:57.0 +0200
@@ -1,3 +1,10 @@
+r4d (1.7-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd unit into /usr/lib. (Closes: #1065307)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:29:57 +0200
+
 r4d (1.7-4) unstable; urgency=medium
 
   * Change bage's email address
diff -Nru r4d-1.7/debian/patches/series r4d-1.7/debian/patches/series
--- r4d-1.7/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ r4d-1.7/debian/patches/series	2024-05-30 01:29:51.0 +0200
@@ -0,0 +1 @@
+systemd-unit-usrmerge.patch
diff -Nru r4d-1.7/debian/patches/systemd-unit-usrmerge.patch r4d-1.7/debian/patches/systemd-unit-usrmerge.patch
--- r4d-1.7/debian/patches/systemd-unit-usrmerge.patch	1970-01-01 01:00:00.0 +0100
+++ r4d-1.7/debian/patches/systemd-unit-usrmerge.patch	2024-05-30 01:29:39.0 +0200
@@ -0,0 +1,13 @@
+Index: r4d-1.7/setup.py
+===
+--- r4d-1.7.orig/setup.py
 r4d-1.7/setup.py
+@@ -25,7 +25,7 @@ setup(name='r4d',
+   scripts=['r4dd', 'r4dcfg'],
+   data_files= [
+   ('/etc/',glob("r4d.cfg")),
+-  ('/lib/systemd/system',  glob("r4dd.service"))],
++  ('/usr/lib/systemd/system',  glob("r4dd.service"))],
+   classifiers=[
+   'License :: OSI Approved :: GNU General Public License v3 or later (GPLv3+)',
+   ],

Bug#1060799: libunwind: diff for NMU version 1.6.2-3.1

[Chris Hofstaedtler]

Control: tags 1060799 + patch
Control: tags 1060799 + pending


Dear maintainer,

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

Regards.

diff -Nru libunwind-1.6.2/debian/changelog libunwind-1.6.2/debian/changelog
--- libunwind-1.6.2/debian/changelog	2022-12-16 22:50:28.0 +0100
+++ libunwind-1.6.2/debian/changelog	2024-05-30 01:17:49.0 +0200
@@ -1,3 +1,10 @@
+libunwind (1.6.2-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Stop installing empty /lib directory. (Closes: #1060799)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:17:49 +0200
+
 libunwind (1.6.2-3) unstable; urgency=low
 
   * Add upstream change to determine the page size dynamically,
diff -Nru libunwind-1.6.2/debian/libunwind8.dirs libunwind-1.6.2/debian/libunwind8.dirs
--- libunwind-1.6.2/debian/libunwind8.dirs	2015-07-04 07:02:00.0 +0200
+++ libunwind-1.6.2/debian/libunwind8.dirs	2024-05-30 01:17:43.0 +0200
@@ -1,2 +1 @@
-lib
 usr/lib

Bug#1059757: firmware-sof: diff for NMU version 2023.12.1-1.1

[Chris Hofstaedtler]

Control: tags 1059757 + patch
Control: tags 1059757 + pending


Dear maintainer,

I've prepared an NMU for firmware-sof (versioned as 2023.12.1-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru firmware-sof-2023.12.1/debian/changelog firmware-sof-2023.12.1/debian/changelog
--- firmware-sof-2023.12.1/debian/changelog	2024-03-05 15:52:23.0 +0100
+++ firmware-sof-2023.12.1/debian/changelog	2024-05-30 01:19:39.0 +0200
@@ -1,3 +1,10 @@
+firmware-sof (2023.12.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install into /usr/lib instead of /lib. (Closes: #1059757)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:19:39 +0200
+
 firmware-sof (2023.12.1-1) unstable; urgency=medium
 
   * Update to upstream version 2023-12.1
diff -Nru firmware-sof-2023.12.1/debian/rules firmware-sof-2023.12.1/debian/rules
--- firmware-sof-2023.12.1/debian/rules	2024-03-05 15:52:23.0 +0100
+++ firmware-sof-2023.12.1/debian/rules	2024-05-30 01:19:39.0 +0200
@@ -4,7 +4,7 @@
 
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
-export SOF_INSTALL_DIR=debian/firmware-sof-signed/lib/firmware/intel
+export SOF_INSTALL_DIR=debian/firmware-sof-signed/usr/lib/firmware/intel
 %:
 	dh $@
 

Bug#1057290: bpftool: please build from https://github.com/libbpf/bpftool

[Sudip Mukherjee]

On Wed, 29 May 2024 at 23:27, Luca Boccassi  wrote:
>
> On Wed, 29 May 2024 19:00:59 +0100 Ben Hutchings 
> wrote:
> > On Sat, 2023-12-02 at 20:04 +, Sudip Mukherjee wrote:
> > > And so, it will be great if kernel team will like to package and
> > > maintain it, if not, then I will be happy to do it. Please
> > > reject this bug report if you think bpftool should not be done
> > > separately and should live inside kernel source package.
> >
> > Since you are already maintaining libbpf I would be happy to hand
> over
> > bpftool to you.  I will try to discuss this at this evening's team
> > meeting.
>
> What about moving libbpf and bpftool to the kernel team area under
> Salsa? That way more people can help, and it can use salsa-ci too

bpftool is already with the kernel team and being built from kernel
source. And I anticipated that bpftool will move to github like
upstream libbpf did and also mentioned that at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948041#83. So, its
upto the kernel team what they want to do with bpftool -
1. continue to build from kernel source and we can just close this bug
2. Split bpftool from kernel source and package it from github. The
kernel team can maintain if they want to maintain an userspace
package. If the kernel team does not want to maintain it, I can do
that.

About libbpf, I am confused with your message. What kind of help? Are
you seeing that libbpf is not maintained properly?


-- 
Regards
Sudip

Bug#1059414: open-ath9k-htc-firmware: diff for NMU version 1.4.0-108-gd856466+dfsg1-1.5

[Chris Hofstaedtler]

Control: tags 1059414 + pending


Dear maintainer,

I've prepared an NMU for open-ath9k-htc-firmware (versioned as 
1.4.0-108-gd856466+dfsg1-1.5) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog
--- open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog	2023-07-26 21:09:48.0 +0200
+++ open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/changelog	2024-05-30 01:01:56.0 +0200
@@ -1,3 +1,10 @@
+open-ath9k-htc-firmware (1.4.0-108-gd856466+dfsg1-1.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install all files below /usr. (Closes: #1059414)
+
+ -- Chris Hofstaedtler   Thu, 30 May 2024 01:01:56 +0200
+
 open-ath9k-htc-firmware (1.4.0-108-gd856466+dfsg1-1.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/firmware-ath9k-htc.install open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/firmware-ath9k-htc.install
--- open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/firmware-ath9k-htc.install	2023-07-26 21:09:18.0 +0200
+++ open-ath9k-htc-firmware-1.4.0-108-gd856466+dfsg1/debian/firmware-ath9k-htc.install	2024-05-30 01:01:52.0 +0200
@@ -1,2 +1,2 @@
-target_firmware/htc_*.fw lib/firmware/ath9k_htc/
+target_firmware/htc_*.fw usr/lib/firmware/ath9k_htc/
 debian/firmware-ath9k-htc.metainfo.xml usr/share/metainfo