Bug#1063621: bookworm-pu: package clamav/clamav_1.0.5+dfsg-1~deb12u1

[Adam D. Barratt]

On Fri, 2024-02-09 at 23:12 +0100, Sebastian Andrzej Siewior wrote:
> This is an update to the latest clamav release in the 1.0.x series. 

One small thing you may want to fix for any follow-up updates:

+clamav (1.0.5+dfsg-1~deb12u1) bookworm; urgency=medium
+
+  * Import 1.0.4 (Closes: #1063479).

Regards,

Adam

Bug#1065651: powerdevil: changes for libddcutil 2.1.4

[Sanford Rockowitz]

Package: powerdevil
Version: 4:5.27.8-0ubuntu1
Severity: normal
X-Debbugs-Cc: rockow...@minsoft.com

Dear Maintainer,

The version of ddcutil in Debian is being updated to release 2.1.4. Shared
library package libddcutil5 replaces libddcutil4.

The code in powerdevil should work unchanged.

In debian/control, consider adding:

Build-Depends: libddcutil-dev

Recommends: libddcutil4 (>= 1.4.1) | libddcutil5 (>= 2.1.4)
or
Suggests: libddcutil4 (>= 1.4.1) | libddcutil5 (>= 2.1.4)



-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-21-generic (SMP w/20 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=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages powerdevil depends on:
ii  kio  5.110.0-0ubuntu1
ii  libc62.38-1ubuntu6.1
ii  libcap2-bin  1:2.66-4ubuntu1
ii  libkf5activities55.110.0-0ubuntu1
ii  libkf5authcore5  5.110.0-0ubuntu1
ii  libkf5bluezqt6   5.110.0-0ubuntu1
ii  libkf5completion55.110.0-0ubuntu1
ii  libkf5configcore55.110.0-0ubuntu1
ii  libkf5configgui5 5.110.0-0ubuntu1
ii  libkf5configwidgets5 5.110.0-0ubuntu1
ii  libkf5coreaddons55.110.0-0ubuntu1
ii  libkf5crash5 5.110.0-0ubuntu1
ii  libkf5dbusaddons55.110.0-0ubuntu1
ii  libkf5globalaccel-bin5.110.0-0ubuntu1
ii  libkf5globalaccel5   5.110.0-0ubuntu1
ii  libkf5i18n5  5.110.0-0ubuntu1
ii  libkf5idletime5  5.110.0-0ubuntu1
ii  libkf5kiowidgets55.110.0-0ubuntu1
ii  libkf5kirigami2-55.110.0-0ubuntu1
ii  libkf5networkmanagerqt6  5.110.0-0ubuntu1
ii  libkf5notifyconfig5  5.110.0-0ubuntu1
ii  libkf5screen-bin 4:5.27.8-0ubuntu1
ii  libkf5screen84:5.27.8-0ubuntu1
ii  libkf5screendpms84:5.27.8-0ubuntu1
ii  libkf5solid5 5.110.0-0ubuntu1
ii  libkf5widgetsaddons5 5.110.0-0ubuntu1
ii  libkf5xmlgui55.110.0-0ubuntu1
ii  libkworkspace5-5 4:5.27.8-0ubuntu1
ii  libpowerdevilcore2   4:5.27.8-0ubuntu1
ii  libpowerdevilui5 4:5.27.8-0ubuntu1
ii  libqt5core5a 5.15.10+dfsg-3
ii  libqt5dbus5  5.15.10+dfsg-3
ii  libqt5gui5   5.15.10+dfsg-3
ii  libqt5widgets5   5.15.10+dfsg-3
ii  libqt5x11extras5 5.15.10-2
ii  libstdc++6   13.2.0-4ubuntu3
ii  libudev1 253.5-1ubuntu6.1
ii  powerdevil-data  4:5.27.8-0ubuntu1

Versions of packages powerdevil recommends:
ii  power-profiles-daemon  0.13-2
ii  systemsettings 4:5.27.8-0ubuntu1

powerdevil suggests no packages.

-- no debconf information

Bug#1065650: ukui-control-center: changes for libddcutil 2.1.4

[Sanford Rockowitz]

Package: ukui-control-center
Severity: normal
Tags: upstream
X-Debbugs-Cc: rockow...@minsoft.com

The version of ddcutil in Debian is being updated to release 2.1.4. Shared
library package libddcutil5 replaces libddcutil4.

Source packages ukui-control-center and ukui-settings-daemon have been
identified as using libddcutil.

References in files debian/control should be updated to specify:

Build-Depends:  libddcutil-dev (>= 1.4.1)
Depends:   libddcutil4 (>= 1.4.1) | libddcutil5 (>= 2.1.4)

Function name ddca_create_display_ref() is deprecated and will be removed in a
future release.  It should be replaced in source code with the alternative name
ddca_get_display_ref(), which more accurately describes what the function does.


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-21-generic (SMP w/20 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=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ukui-control-center depends on:
ii  dconf-cli0.40.0-4
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
pn  ddcutil  
ii  libc62.38-1ubuntu6.1
ii  libcanberra0 0.30-10ubuntu4
ii  libcrypt11:4.4.36-2
ii  libdconf10.40.0-4
pn  libddcutil4  
ii  libgcc-s113.2.0-4ubuntu3
ii  libglib2.0-0 2.78.0-2
ii  libglib2.0-bin   2.78.0-2
ii  libgsettings-qt1 0.2-5
ii  libgtk-3-0   3.24.38-5ubuntu1
ii  libkf5bluezqt6   5.110.0-0ubuntu1
ii  libkf5configcore55.110.0-0ubuntu1
ii  libkf5configgui5 5.110.0-0ubuntu1
ii  libkf5coreaddons55.110.0-0ubuntu1
ii  libkf5globalaccel-bin5.110.0-0ubuntu1
ii  libkf5globalaccel5   5.110.0-0ubuntu1
ii  libkf5i18n5  5.110.0-0ubuntu1
ii  libkf5screen-bin 4:5.27.8-0ubuntu1
ii  libkf5screen84:5.27.8-0ubuntu1
ii  libkf5windowsystem5  5.110.0-0ubuntu1
ii  libmatekbd4  1.26.1-1
ii  libmatemixer01.26.1-1
ii  libopencv-core4064.6.0+dfsg-13build1
ii  libopencv-imgcodecs406   4.6.0+dfsg-13build1
ii  libopencv-imgproc406 4.6.0+dfsg-13build1
ii  libpam0g 1.5.2-6ubuntu1.1
ii  libpolkit-qt5-1-10.114.0-2
ii  libpulse-mainloop-glib0  1:16.1+dfsg1-2ubuntu4
ii  libpulse01:16.1+dfsg1-2ubuntu4
ii  libqt5concurrent55.15.10+dfsg-3
ii  libqt5core5a 5.15.10+dfsg-3
ii  libqt5dbus5  5.15.10+dfsg-3
ii  libqt5gui5   5.15.10+dfsg-3
ii  libqt5network5   5.15.10+dfsg-3
ii  libqt5printsupport5  5.15.10+dfsg-3
ii  libqt5qml5   5.15.10+dfsg-2
ii  libqt5quick5 5.15.10+dfsg-2
ii  libqt5quickwidgets5  5.15.10+dfsg-2
ii  libqt5svg5   5.15.10-2
ii  libqt5widgets5   5.15.10+dfsg-3
ii  libqt5x11extras5 5.15.10-2
ii  libqt5xml5   5.15.10+dfsg-3
ii  libstdc++6   13.2.0-4ubuntu3
ii  libudev1 253.5-1ubuntu6.1
ii  libx11-6 2:1.8.6-1ubuntu1
ii  libxcursor1  1:1.2.1-1
ii  libxi6   2:1.8-1build1
ii  libxkbfile1  1:1.1.0-1build3
ii  libxklavier165.4-4build2
ii  libxml2  2.9.14+dfsg-1.3ubuntu0.1
ii  qml-module-qtgraphicaleffects5.15.10-2
ii  qml-module-qtquick-controls  5.15.10-2
ii  qt5-image-formats-plugins5.15.10-2

ukui-control-center recommends no packages.

Versions of packages ukui-control-center suggests:
ii  gsettings-desktop-schemas  45.0-1ubuntu1
ii  

Bug#1065649: e17: changes for libddcutil 2.1.4

[Sanford Rockowitz]

Source: e17
Version: 0.25.4-2
Severity: normal
Tags: upstream
X-Debbugs-Cc: rockow...@minsoft.com

The version of ddcutil in Debian is being updated to release 2.1.4. Shared
library package libddcutil5 replaces libddcutil4.

Source package e17 has been identified as using libddcutil.

File e_system_ddc.c should be modified to try opening libddcutil.so.5 before
libddcutil.so.4.

In debian/control, consider adding:

Recommends: libddcutil4 (>= 1.4.1) | libddcutil5 (>= 2.1.4)
or
Suggests: libddcutil4 (>= 1.4.1) | libddcutil5 (>= 2.1.4)


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-21-generic (SMP w/20 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=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1065646: Additional information

[Vladimir Petko]

Dear Maintainers,

  Would it be possible to consider a merge request[1] that addresses this issue?

Best Regards,
 Vladimir.

 [1] https://salsa.debian.org/med-team/igv/-/merge_requests/1

Bug#1065648: dpkg: FTBFS when gpg is installed

[Tianyu Chen]

Source: dpkg
Version: 1.22.5
Severity: normal
Tags: ftbfs
X-Debbugs-Cc: sweetyf...@deepin.org

Hi,

When building dpkg in some environment with gpg installed or lintian
installed (lintian depends on gpg), dh_auto_test failed in Dpkg_OpenPGP.t.
But when gnupg is installed, dpkg builds successfully.

In those circumstances, Dpkg_OpenPGP.t should skip subtests instead of fail.

Best regards,
Tianyu Chen @ deepin

-- System Information:
Distributor ID: Deepin
Description:Deepin 23
Release:23
Codename:   beige
Architecture: x86_64

Kernel: Linux 6.6.7-amd64-desktop-hwe (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
../../scripts/t/Dpkg_Path.t  ok
../../scripts/t/Dpkg_Control_Tests.t ... ok
../../scripts/t/Dpkg_Source_Functions.t  ok

#   Failed test '(auto:auto) dearmoring OpenPGP ASCII Armored certificate'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 67.

#   Failed test '(auto:auto) armoring OpenPGP binary certificate'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 69.
diff: t.tmp/Dpkg_OpenPGP/dpkg-test-pub.asc: No such file or directory

#   Failed test '(auto:auto) OpenPGP certificate dearmor/armor round-trip 
correctly (../../scripts/t/Dpkg_OpenPGP/dpkg-test-pub.asc vs 
t.tmp/Dpkg_OpenPGP/dpkg-test-pub.asc)'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 54.

#   Failed test '(auto:auto) armoring OpenPGP binary signature succeeded'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 74.

#   Failed test '(auto:auto) armoring OpenPGP armored signature succeeded'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 78.
diff: t.tmp/Dpkg_OpenPGP/sign-file-rearmor.asc: No such file or directory

#   Failed test '(auto:auto) rearmoring OpenPGP ASCII Armor changed the file 
(../../scripts/t/Dpkg_OpenPGP/sign-file.asc vs 
t.tmp/Dpkg_OpenPGP/sign-file-rearmor.asc)'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 54.

#   Failed test '(auto:auto) dearmoring OpenPGP armored signature succeeded'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 83.
diff: t.tmp/Dpkg_OpenPGP/sign-file.sig: No such file or directory
../../scripts/t/Dpkg_Deps.t  ok
../../scripts/t/Dpkg_Control.t . ok

#   Failed test '(auto:auto) dearmored OpenPGP ASCII Armor signature matches 
(../../scripts/t/Dpkg_OpenPGP/sign-file.sig vs 
t.tmp/Dpkg_OpenPGP/sign-file.sig)'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 54.

#   Failed test '(auto:auto) verify OpenPGP ASCII Armor inline signature'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 90.

#   Failed test '(auto:auto) verify OpenPGP binary inline signature'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 92.

#   Failed test '(auto:auto) verify OpenPGP ASCII Armor detached signature'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 95.

#   Failed test '(auto:auto) verify OpenPGP binary detached signature'
#   at ../../scripts/t/Dpkg_OpenPGP.t line 97.
../../scripts/t/Dpkg_Substvars.t ... ok
../../scripts/t/Dpkg_Source_Format.t ... ok
../../scripts/t/Dpkg_Changelog.t ... ok
../../scripts/t/Dpkg_Source_Patch.t  ok
../../scripts/t/Dpkg_Changelog_Ubuntu.t  ok
# Looks like you failed 12 tests of 32.
../../scripts/t/Dpkg_OpenPGP.t . 
not ok 3 - (auto:auto) dearmoring OpenPGP ASCII Armored certificate
not ok 4 - (auto:auto) armoring OpenPGP binary certificate
not ok 5 - (auto:auto) OpenPGP certificate dearmor/armor round-trip correctly 
(../../scripts/t/Dpkg_OpenPGP/dpkg-test-pub.asc vs 
t.tmp/Dpkg_OpenPGP/dpkg-test-pub.asc)
not ok 6 - (auto:auto) armoring OpenPGP binary signature succeeded
not ok 8 - (auto:auto) armoring OpenPGP armored signature succeeded
not ok 9 - (auto:auto) rearmoring OpenPGP ASCII Armor changed the file 
(../../scripts/t/Dpkg_OpenPGP/sign-file.asc vs 
t.tmp/Dpkg_OpenPGP/sign-file-rearmor.asc)
not ok 10 - (auto:auto) dearmoring OpenPGP armored signature succeeded
not ok 11 - (auto:auto) dearmored OpenPGP ASCII Armor signature matches 
(../../scripts/t/Dpkg_OpenPGP/sign-file.sig vs t.tmp/Dpkg_OpenPGP/sign-file.sig)
not ok 12 - (auto:auto) verify OpenPGP ASCII Armor inline signature
not ok 13 - (auto:auto) verify OpenPGP binary inline signature
not ok 14 - (auto:auto) verify OpenPGP ASCII Armor detached signature
not ok 15 - (auto:auto) verify OpenPGP binary detached signature
Dubious, test returned 12 (wstat 3072, 0xc00)
Failed 12/32 subtests 
(less 4 skipped subtests: 16 okay)
../../scripts/t/Dpkg_Compression.t . ok
../../scripts/t/Dpkg_Source_Quilt.t  ok
../../scripts/t/Dpkg_Dist_Files.t .. ok
../../scripts/t/Dpkg_Source_Archive.t .. ok
../../scripts/t/Dpkg_Source_Package.t .. ok
../../scripts/t/Dpkg_Control_Fields.t .. ok
../../scripts/t/dpkg_mergechangelogs.t . ok
../../scripts/t/Dpkg_Arch.t  ok
../../scripts/t/Dpkg_IPC.t . ok
../../scripts/t/dpkg_source.t .. ok

Bug#1042042: android-platform-build: FTBFS: Vector.h:259:28: error: cannot convert ‘const android::Vector*’ to ‘android::VectorImpl*’

[Vladimir Petko]

Package: android-platform-build
Followup-For: Bug #1042042
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

The attached patch resolves the above ftbfs by adding patches for BouncyCastle
and libziparchive-dev API changes.

In Ubuntu, the attached patch was applied to achieve the following:

  * Resolve ftbfs due to the API changes (LP: #2056084):
- d/p/bouncycastle177-compat.patch: replace DerOutputStream with
  ASN1OutputStream.
- d/p/zip-archive-reader-signature: update ReadAtOffset method
  signature.


Thanks for considering the patch.


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-21-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru 
android-platform-build-10.0.0+r36/debian/patches/bouncycastle177-compat.patch 
android-platform-build-10.0.0+r36/debian/patches/bouncycastle177-compat.patch
--- 
android-platform-build-10.0.0+r36/debian/patches/bouncycastle177-compat.patch   
1970-01-01 12:00:00.0 +1200
+++ 
android-platform-build-10.0.0+r36/debian/patches/bouncycastle177-compat.patch   
2024-03-06 14:35:07.0 +1300
@@ -0,0 +1,30 @@
+Description: remove usage of DerOutputStream
+ BouncyCastle removed DerOutputStream and replaced it
+ with ASN1OutputStream.
+Author: Vladimir Petko 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042042
+Bug-Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/android-platform-build/+bug/2056084
+Forwarded: not-needed
+Last-Update: 2024-03-06
+
+--- a/tools/signapk/src/com/android/signapk/SignApk.java
 b/tools/signapk/src/com/android/signapk/SignApk.java
+@@ -18,7 +18,8 @@
+
+ import org.bouncycastle.asn1.ASN1InputStream;
+ import org.bouncycastle.asn1.ASN1ObjectIdentifier;
+-import org.bouncycastle.asn1.DEROutputStream;
++import org.bouncycastle.asn1.ASN1OutputStream;
++import org.bouncycastle.asn1.ASN1Encoding;
+ import org.bouncycastle.asn1.cms.CMSObjectIdentifiers;
+ import org.bouncycastle.asn1.pkcs.PrivateKeyInfo;
+ import org.bouncycastle.cert.jcajce.JcaCertStore;
+@@ -334,7 +335,7 @@
+ CMSSignedData sigData = gen.generate(data, false);
+
+ try (ASN1InputStream asn1 = new 
ASN1InputStream(sigData.getEncoded())) {
+-DEROutputStream dos = new DEROutputStream(out);
++ASN1OutputStream dos = ASN1OutputStream.create(out, 
ASN1Encoding.DER);
+ dos.writeObject(asn1.readObject());
+ }
+ }
diff -Nru android-platform-build-10.0.0+r36/debian/patches/series 
android-platform-build-10.0.0+r36/debian/patches/series
--- android-platform-build-10.0.0+r36/debian/patches/series 2021-01-03 
10:32:31.0 +1300
+++ android-platform-build-10.0.0+r36/debian/patches/series 2024-03-06 
14:35:07.0 +1300
@@ -3,3 +3,5 @@
 fix_zipalign_typo.diff
 python-2to3.patch
 Implement-range-based-pin-list.patch
+zip-archive-reader-signature.patch
+bouncycastle177-compat.patch
diff -Nru 
android-platform-build-10.0.0+r36/debian/patches/zip-archive-reader-signature.patch
 
android-platform-build-10.0.0+r36/debian/patches/zip-archive-reader-signature.patch
--- 
android-platform-build-10.0.0+r36/debian/patches/zip-archive-reader-signature.patch
 1970-01-01 12:00:00.0 +1200
+++ 
android-platform-build-10.0.0+r36/debian/patches/zip-archive-reader-signature.patch
 2024-03-06 14:35:07.0 +1300
@@ -0,0 +1,21 @@
+Description: update FileReader::ReadAtOffset signature
+ FileReader:ReadAtOffset() signature was changed in
+ android-libziparchive-dev. Update the method signature
+ to match.
+Author: Vladimir Petko 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042042
+Bug-Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/android-platform-build/+bug/2056084
+Forwarded: not-needed
+Last-Update: 2024-03-06
+
+--- a/tools/zipalign/ZipFile.cpp
 b/tools/zipalign/ZipFile.cpp
+@@ -1223,7 +1223,7 @@
+ FileReader(FILE* fp) : Reader(), fp_(fp), current_offset_(0) {
+ }
+
+-bool ReadAtOffset(uint8_t* buf, size_t len, uint32_t offset) const {
++bool ReadAtOffset(uint8_t* buf, size_t len, off64_t offset) const {
+ // Data is usually requested sequentially, so this helps avoid 
pointless
+ // fseeks every time we perform a read. There's an impedence mismatch
+ // here because the original API was designed around pread and pwrite.

Bug#1065522: android-platform-external-nist-sip: FTBFS with default Java 21

[Vladimir Petko]

Package: android-platform-external-nist-sip
Followup-For: Bug #1065522
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

The package fails to build with default Java 21 due to java.util.List API
changes.

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/java21-update-list-api.patch: add patch to workaround Java 21
java.util.List API changes (LP: #2056086).


Thanks for considering the patch.


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-21-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru 
android-platform-external-nist-sip-9.0.0+r35/debian/patches/java21-update-list-api.patch
 
android-platform-external-nist-sip-9.0.0+r35/debian/patches/java21-update-list-api.patch
--- 
android-platform-external-nist-sip-9.0.0+r35/debian/patches/java21-update-list-api.patch
1970-01-01 12:00:00.0 +1200
+++ 
android-platform-external-nist-sip-9.0.0+r35/debian/patches/java21-update-list-api.patch
2024-03-06 14:00:01.0 +1300
@@ -0,0 +1,55 @@
+Description: workaround java.util.List changes in Java 21
+ Java 21 adds removeFirst()/removeLast() and getFirst()/getLast() methods
+ that are also defined in the class SIPHeader. Update method signatures
+ to match Java 21 API.
+Author: Vladimir Petko 
+Bug-Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/android-platform-external-nist-sip/+bug/2056086
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065522
+Frwarded: not-needed
+Last-Update: 2024-03-06
+
+--- a/java/gov/nist/javax/sip/header/SIPHeaderList.java
 b/java/gov/nist/javax/sip/header/SIPHeaderList.java
+@@ -208,7 +208,7 @@
+  *
+  * @return SIPHeader first element of the list.
+  */
+-public Header getFirst() {
++public HDR getFirst() {
+ if (hlist == null || hlist.isEmpty())
+ return null;
+ else
+@@ -220,7 +220,7 @@
+  *
+  * @return SIPHeader last element of the list.
+  */
+-public Header getLast() {
++public HDR getLast() {
+ if (hlist == null || hlist.isEmpty())
+ return null;
+ return  hlist.get(hlist.size() - 1);
+@@ -277,18 +277,19 @@
+ /**
+  * Remove the first element of this list.
+  */
+-public void removeFirst() {
++public HDR removeFirst() {
+ if (hlist.size() != 0)
+-hlist.remove(0);
+-
++return hlist.remove(0);
++return null;
+ }
+
+ /**
+  * Remove the last element of this list.
+  */
+-public void removeLast() {
++public HDR removeLast() {
+ if (hlist.size() != 0)
+-hlist.remove(hlist.size() - 1);
++return hlist.remove(hlist.size() - 1);
++return null;
+ }
+
+ /**
diff -Nru android-platform-external-nist-sip-9.0.0+r35/debian/patches/series 
android-platform-external-nist-sip-9.0.0+r35/debian/patches/series
--- android-platform-external-nist-sip-9.0.0+r35/debian/patches/series  
1970-01-01 12:00:00.0 +1200
+++ android-platform-external-nist-sip-9.0.0+r35/debian/patches/series  
2024-03-06 14:00:01.0 +1300
@@ -0,0 +1 @@
+java21-update-list-api.patch

Bug#1065301: Please stop hijacking mailto: by default

[Rob Browning]

Eduard Bloch  writes:

> I have recently experienced a little discomfort, when my regular click
> on some mailto: link in a browser started opening Emacs (which I have
> not configured for this purpose and never wanted to use it for Mail).
> Instead of my regular mutt-in-terminal.

I spoke to someone who was more knowledgeable about the current state of
affairs, and they said that applications can't control the priorities
with desktop files the way they could with mailcap.  So emacs can only
say that it provides mailto support (which it does via notmuch, gnus,
rmail, etc.), but it can't set itself at a "lower" priority.

However, you can specify your own priorities either via your browser's
mechanism (settings > general > applications in firefox), or possibly
(it sounds like) via overrides provided by a desktop like gnome (if you
use it).  i.e. while I haven't used gnome in a while, it sounds like
they have a "default applications" option under settings.

Hope this helps.
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#1065647: lists.debian.org: Refresh list of category in https://lists.debian.org/

[Kentaro HAYASHI]

Package: lists.debian.org
Severity: normal
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

* What led up to the situation?

  Currently, list of category in https://lists.debian.org are like this:

  * Debconf
  * Users
  * Developers
  * Internationalization and Translations
  * Ports
  * Bug tracking system
  * Miscellaneous Debian
  * Linux Standard Base
  * Software in the Public Interest
  * Other 

  It seems that some of above category may be too comprehensive,
  so I think that updating list of category may be better.

* What exactly did you do (or not do) that was effective (or
  ineffective)?

  Checked existing category and list of what mailing-list belong to each
  category.

* What was the outcome of this action?

  It seems that some of existing category should be split into new one.

  I suggest the following two cases.

  * Case 1) Users category is too comprehensive, let's split it.
  * Case 2) Developers category is too comprehensive, let's split it.


  Case 1) Users category is too comprehensive, let's split it.

  Split Users into "Users" and "Local Community and Users".
  Merit of this one is making it easy to distinct regional community.

  Before:

   * Users (English)
* debian-announce
* debian-backports
...
* debian-user
...
* debian-chinese
* debian-chinese-big5
* debian-chinese-gb
* debian-esperanto
...


  After:

   * Users (English)
* debian-announce
* debian-backports
...
* debian-user
...

   * Local Community and Users

* debian-chinese
* debian-chinese-big5
* debian-chinese-gb
* debian-esperanto
* debian-french
* debian-italian
* debian-japanese
* debian-user-catalan
* debian-user-danish
...


  Case 2) Developers category is too comprehensive, let's split it.

Extract some mailing-list into new "Maintenance of Programming
Languages" from Developpers category.

  Before:

   * Developpers

* debian-academy
...

  After:

   * Developpers

* debian-academy
...

   * Maintenance of Programming Languages

* debian-ada
* debian-clojure
* debian-common-lisp
* debian-go
* debian-haskell
* debian-js
* debian-ocaml-maint
* debian-perl
* debian-python
* debian-r
* debian-ruby
* debian-rust
* debian-scheme

* What outcome did you expect instead?

Miscellaneous Debian may be better to re-consider, but it is out of
scope.

BTW, where is the source code of lists.debian.org/?

Regards,

Bug#1065646: igv fails to build from source due to tests trying to access the internet

[Vladimir Petko]

Source: igv
Version: 2.17.1+dfsg-1
Severity: normal

Dear Maintainer,

Tests fail when building the package with the following exceptions[1]:

org.broad.igv.sam.mods.BaseModificationCountsTest > incrementCounts2 FAILED
java.net.UnknownHostException: dl.dropboxusercontent.com

org.broad.igv.util.blat.BlatClientTest > classMethod FAILED
java.net.UnknownHostException: s3.amazonaws.com

org.broad.igv.tdf.TDFReaderTest > testReader FAILED
org.broad.igv.exceptions.DataLoadException: An error occurred while
accessing:
http://data.broadinstitute.org/igvdata/tutorials/hg18/wgEncodeBroadChipSeqSignalK562H3k4me3.wig.gz.tdfError
loading file:

[1] https://launchpad.net/ubuntu/+source/igv/2.17.1+dfsg-1/+build/27788297


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#961389: fonts-dejavu-core: unannounced change of default config breaks user configuration

[Boyuan Yang]

reassign 961389 src:fontconfig
fixed 961389 fontconfig/2.14.1-4
tags 961389 sid trixie bookworm
close 961389
thanks

Given that the required changes in fontconfig is present after v2.13.93,
marking this bug as fixed in Debian Bookworm, Trixie and Sid.

Thanks,
Boyuan Yang


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

Bug#1065633: [SPAM] Re: Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function 'kadm5_s_init_with_password_ctx'

[John David Anglin]

On 2024-03-07 7:21 p.m., Ryan Tandy wrote:

On Thu, Mar 07, 2024 at 01:29:54PM -0800, Ryan Tandy wrote:
The binNMUs succeeded on several release arches already. I'm not sure why hppa would be different. I see 
-Werror=implicit-function-declaration in its compiler commands, but I don't know where it's coming from.


I remembered later maybe seeing something about this around time64 build flags, 
and sure enough, in dpkg 1.22.5:

https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=ef90821fe45b99fa8c8c4279b9a74c30f59f491d

So actually it looks like hppa was only the first to encounter it, and armel/armhf are likely to fail the same way (right now they are still 
BD-Uninstallable), in which case this bug will be RC.

Yes, see:
https://wiki.debian.org/BrainDumpT64

We have been doing a lot of manual builds, so it's possible we may have messed 
up.

--
John David Anglin  dave.ang...@bell.net

Bug#1055438: kea: init-scripts not working

[Stefan Klein]

Hello Paride,

thank you for looking at the patch again and rating it as good enough. I 
fully understand your point about the problems with init-script QA...


The merge request you prepared contains all the changes I made. So this 
mail is my final green light, that MR contains the code that worked for me!


Sorry for doing that via mail only. I am currently on vacation and don't 
have access to my Salsa account :(


Stefan

Bug#1054514: [PATCH 1/1] drm/qxl: fixes qxl_fence_wait

[Alex Constantino]

Fix OOM scenario by doing multiple notifications to the OOM handler through
a busy wait logic.
Changes from commit 5a838e5d5825 ("drm/qxl: simplify qxl_fence_wait") would
result in a '[TTM] Buffer eviction failed' exception whenever it reached a
timeout.

Fixes: 5a838e5d5825 ("drm/qxl: simplify qxl_fence_wait")
Link: 
https://lore.kernel.org/regressions/fb0fda6a-3750-4e1b-893f-97a3e402b...@leemhuis.info
Reported-by: Timo Lindfors 
Closes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054514
Signed-off-by: Alex Constantino 
---
 drivers/gpu/drm/qxl/qxl_release.c | 20 ++--
 1 file changed, 14 insertions(+), 6 deletions(-)

diff --git a/drivers/gpu/drm/qxl/qxl_release.c 
b/drivers/gpu/drm/qxl/qxl_release.c
index 368d26da0d6a..51c22e7f9647 100644
--- a/drivers/gpu/drm/qxl/qxl_release.c
+++ b/drivers/gpu/drm/qxl/qxl_release.c
@@ -20,8 +20,6 @@
  * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
  */
 
-#include 
-
 #include 
 
 #include "qxl_drv.h"
@@ -59,14 +57,24 @@ static long qxl_fence_wait(struct dma_fence *fence, bool 
intr,
 {
struct qxl_device *qdev;
unsigned long cur, end = jiffies + timeout;
+   signed long iterations = 1;
+   signed long timeout_fraction = timeout;
 
qdev = container_of(fence->lock, struct qxl_device, release_lock);
 
-   if (!wait_event_timeout(qdev->release_event,
+   // using HZ as a factor since it is used in ttm_bo_wait_ctx too
+   if (timeout_fraction > HZ) {
+   iterations = timeout_fraction / HZ;
+   timeout_fraction = HZ;
+   }
+   for (int i = 0; i < iterations; i++) {
+   if (wait_event_timeout(
+   qdev->release_event,
(dma_fence_is_signaled(fence) ||
-(qxl_io_notify_oom(qdev), 0)),
-   timeout))
-   return 0;
+   (qxl_io_notify_oom(qdev), 0)),
+   timeout_fraction))
+   break;
+   }
 
cur = jiffies;
if (time_after(cur, end))
-- 
2.39.2

Bug#1054514: [PATCH 0/1] drm/qxl: fixes qxl_fence_wait

[Alex Constantino]

Hi,
As initially reported by Timo in the QXL driver will crash given enough
workload:
https://lore.kernel.org/regressions/fb0fda6a-3750-4e1b-893f-97a3e402b...@leemhuis.info/
I initially came across this problem when migrating Debian VMs from Bullseye
to Bookworm. This bug will somewhat randomly but consistently happen, even
just by using neovim with plugins or playing a video. This exception would
then cascade and make Xorg crash too.

The error log from dmesg would have `[TTM] Buffer eviction failed` followed
by either a `failed to allocate VRAM BO` or `failed to allocate GEM object`.
And the error log from Xorg would have `qxl(0): error doing QXL_ALLOC`
followed by a backtrace and segmentation fault.

I can confirm the problem still exists in latest kernel versions:
https://gitlab.freedesktop.org/drm/kernel @ c6d6a82d8a9f
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git @ 
1870cdc0e8de

When I was investigating this issue I ended up creating a script which
triggers the issue in just a couple of minutes when executed under uxterm.
YMMV according to your system, for example when using urxvt crashes were
not as consistent, likely due to it being more efficient and having less
video memory allocations.
For me this is the fastest way to trigger the bug. Here follows:
```
#!/bin/bash
print_gradient_with_awk() {
local arg="$1"
if [[ -n $arg ]]; then
arg=" ($arg)"
fi
awk -v arg="$arg" 'BEGIN{
s="/\\/\\/\\/\\/\\"; s=s s s s s s s s;
for (colnum = 0; colnum<77; colnum++) {
r = 255-(colnum*255/76);
g = (colnum*510/76);
b = (colnum*255/76);
if (g>255) g = 510-g;
printf "\033[48;2;%d;%d;%dm", r,g,b;
printf "\033[38;2;%d;%d;%dm", 255-r,255-g,255-b;
printf "%s\033[0m", substr(s,colnum+1,1);
}
printf "%s\n", arg;
}'
}
for i in {1..1}; do
print_gradient_with_awk $i
done
```

Timo initially reported:
commit 5f6c871fe919 ("drm/qxl: properly free qxl releases") as working fine
commit 5a838e5d5825 ("drm/qxl: simplify qxl_fence_wait") introducing the bug

The bug occurs whenever a timeout is reached in wait_event_timeout.
To fix this issue I updated the code to include a busy wait logic, which
was how the last working version operated. That fixes this bug while still
keeping the code simple (which I suspect was the motivation for the
5a838e5d5825 commit in the first place), as opposed to just reverting to
the last working version at 5f6c871fe919
The choice for the use of HZ as a scaling factor for the loop was that it
is also used by ttm_bo_wait_ctx which is one of the indirect callers of
qxl_fence_wait, with the other being ttm_bo_delayed_delete

To confirm the problem no longer manifests I have:
- executed my own test case pasted above
- executed Timo's test case pasted below
- played a video stream in mplayer for 3h (no audio stream because
  apparently pulseaudio and/or alsa have memory leaks that make the
  system run out of memory)

For quick reference here is Timo's script:
```
#!/bin/bash
chvt 3
for j in $(seq 80); do
echo "$(date) starting round $j"
if [ "$(journalctl --boot | grep "failed to allocate VRAM BO")" != "" ]; 
then
echo "bug was reproduced after $j tries"
exit 1
fi
for i in $(seq 100); do
dmesg > /dev/tty3
done
done
echo "bug could not be reproduced"
exit 0
```

>From what I could find online it seems that users that have been affected
by this problem just tend to move from QXL to VirtIO, that is why this bug
has been hidding for over 3 years now.
This issue was initially reported by Timo 4 months ago but the discussion
seems to have stalled.
It would be great if this could be addressed and avoid it falling through
the cracks.

Thank you for your time.


---

Alex Constantino (1):
  drm/qxl: fixes qxl_fence_wait

 drivers/gpu/drm/qxl/qxl_release.c | 20 ++--
 1 file changed, 14 insertions(+), 6 deletions(-)


base-commit: 1870cdc0e8dee32e3c221704a2977898ba4c10e8
-- 
2.39.2

Bug#1065645: O: qtdbusextended -- Extended DBus interface for Qt

[Boyuan Yang]

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

I intend to orphan the qtdbusextended package. It is no longer used by other
software.

The package description is:
 Qtdbusextended library provides several additional features to the original
 QDbusAbstractInterface class, includes:
  - Handling of PropertiesChanged signal in DBus Properties Interface
  - the GetAll method in DBus Properties Interface
  - asynchronous alternative to original synchronous QtDBus properties mechanism
  - an alternative cache mechanism for Qt DBus traffic
 .
 This package provides shared library files.

Thanks,
Boyuan Yang


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

Bug#1064252: closed by Salvatore Bonaccorso (Re: Bug#1064252: linux-image-6.1.0-17-amd64: CONFIG_SYSTEM_TRUSTED_KEYS="y" is in the default config "y")

[TomK]

Since .config lists the response to this as "y" WITH THE DOUBLE QUOTES, IT is 
not possible to change it in menuconfig, and the quotes break the compile. So, 
the stock linux-image-6.5-amd64 config file in /boot, if copied to .config into 
the source directory, it's booby trapped with a config value: "y", that 
prevents it from being changed in the make config, and it breaks the 
kernel compile no matter what.

Nowhere does Debian kernel development document all the changes that must be 
made to the stock configs from the linux-image packages when they are copied as 
.config from /boot to the source directory. Every single stock /boot/config-xyz 
will break the compile of the source package if used as a template for .config 
(which could be a super time-saver)--which is bad enough--but Debian has let 
this problem go on for probably 6 years. 

I think a patch to fix this problem would be in order. Just have a config 
option: "patch stock config for successful compile", would be really helpful. 
Or, better yet, an interactive Makefile option--make compilableconfig, that 
branches to a script that calls external programs and promts the source package 
user to create and put in place the necessary files to use the problematic 
options for their intended purpose, and correct .config options that need to be 
changed. 

That would require, at most, 15 minutes per linux-image package. I appreciate 
all the Debian project gives to the world, and to me personally. I don't mean 
to just vent on you. 

Another plan could be to mark stock config files, and if one is detected, to 
execute the repair script, and print a config-patch.log. Also, perhaps shasums 
could be calculated for stock config files and .config in the sources 
directory, and compared to determine whether or not .config is a copy of 
/boot/config-xyz. 

I've been using Debian since woody, when I was in elementary school. But I 
became more of an admin, security, forensics, triage and hacker. Alhough I have 
some noteworthy programming accomplishments.I devised algorithms to convert 
between numeric bases, and to do arithematic using numbers of different bases. 

I was a self-employed consultant while in college. My first job I made $6,000 
in 20 hours. I'd like to contribute more to Debian. But most of the English 
language documentation is well done. Maintaining packages is time-consuming. 
But, I don't want to go on and on. I hope I've communicated more clearly.   

Tom


 Original Message 
From: Debian Bug Tracking System 
Sent: March 7, 2024 9:03:05 PM UTC
To: tomas k 
Subject: Bug#1064252 closed by Salvatore Bonaccorso  (Re: 
Bug#1064252: linux-image-6.1.0-17-amd64: CONFIG_SYSTEM_TRUSTED_KEYS="y" is in 
the default config "y")

This is an automatic notification regarding your Bug report
which was filed against the src:linux package:

#1064252: linux-image-6.1.0-17-amd64: CONFIG_SYSTEM_TRUSTED_KEYS="y" is in the 
default config "y"

It has been closed by Salvatore Bonaccorso .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Salvatore Bonaccorso 
 by
replying to this email.


-- 
1064252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function 'kadm5_s_init_with_password_ctx'

[Ryan Tandy]

On Thu, Mar 07, 2024 at 01:29:54PM -0800, Ryan Tandy wrote:
The binNMUs succeeded on several release arches already. I'm not sure 
why hppa would be different. I see 
-Werror=implicit-function-declaration in its compiler commands, but I 
don't know where it's coming from.


I remembered later maybe seeing something about this around time64 build 
flags, and sure enough, in dpkg 1.22.5:


https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=ef90821fe45b99fa8c8c4279b9a74c30f59f491d

So actually it looks like hppa was only the first to encounter it, and 
armel/armhf are likely to fail the same way (right now they are still 
BD-Uninstallable), in which case this bug will be RC.

Bug#1065644: O: qstardict -- International dictionary written using Qt

[Boyuan Yang]

Subject: O: qstardict -- International dictionary written using Qt
Package: wnpp
Control: affects -1 + src:qstardict
X-Debbugs-Cc: qstard...@packages.debian.org
Severity: normal

I intend to orphan the qstardict package since I no longer use it.

The package description is:
 QStarDict is a modern international dictionary written using Qt.
 .
 Main features include:
  * Full support of StarDict dictionaries
  * Fuzzy search
  * Support for hyper links in translations
  * Working from the system tray
  * Scanning mouse selection and showing pop-up windows with translation of
selected words
  * Translations reformatting
  * Pronouncing of the translated words
  * Plugins support

Regards,
Boyuan Yang


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

Bug#1064967: fontforge: diff for NMU version 1:20230101~dfsg-1.1

[Adrian Bunk]

Control: tags 1064967 + patch
Control: tags 1064967 + pending

Dear maintainer,

I've prepared an NMU for fontforge (versioned as 1:20230101~dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it.

@Security team:
If wanted, I could afterwards also prepare (pu or DSA) updates for 
bookworm and bullseye.

cu
Adrian
diff -Nru fontforge-20230101~dfsg/debian/changelog fontforge-20230101~dfsg/debian/changelog
--- fontforge-20230101~dfsg/debian/changelog	2023-01-18 20:05:41.0 +0200
+++ fontforge-20230101~dfsg/debian/changelog	2024-03-08 01:15:58.0 +0200
@@ -1,3 +1,13 @@
+fontforge (1:20230101~dfsg-1.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * CVE-2024-25081: Spline Font command injection via crafted filenames
+  * CVE-2024-25082: Spline Font command injection via crafted archives
+or compressed files
+  * Closes: #1064967
+
+ -- Adrian Bunk   Fri, 08 Mar 2024 01:15:58 +0200
+
 fontforge (1:20230101~dfsg-1) unstable; urgency=medium
 
   * New upstream version 20230101~dfsg
diff -Nru fontforge-20230101~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch fontforge-20230101~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch
--- fontforge-20230101~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch	1970-01-01 02:00:00.0 +0200
+++ fontforge-20230101~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch	2024-03-07 23:25:36.0 +0200
@@ -0,0 +1,181 @@
+From 216eb14b558df344b206bf82e2bdaf03a1f2f429 Mon Sep 17 00:00:00 2001
+From: Peter Kydas 
+Date: Tue, 6 Feb 2024 20:03:04 +1100
+Subject: fix splinefont shell command injection (#5367)
+
+---
+ fontforge/splinefont.c | 125 +
+ 1 file changed, 90 insertions(+), 35 deletions(-)
+
+diff --git a/fontforge/splinefont.c b/fontforge/splinefont.c
+index 239fdc035..647daee10 100644
+--- a/fontforge/splinefont.c
 b/fontforge/splinefont.c
+@@ -788,11 +788,14 @@ return( name );
+ 
+ char *Unarchive(char *name, char **_archivedir) {
+ char *dir = getenv("TMPDIR");
+-char *pt, *archivedir, *listfile, *listcommand, *unarchivecmd, *desiredfile;
++char *pt, *archivedir, *listfile, *desiredfile;
+ char *finalfile;
+ int i;
+ int doall=false;
+ static int cnt=0;
++gchar *command[5];
++gchar *stdoutresponse = NULL;
++gchar *stderrresponse = NULL;
+ 
+ *_archivedir = NULL;
+ 
+@@ -827,18 +830,30 @@ return( NULL );
+ listfile = malloc(strlen(archivedir)+strlen("/" TOC_NAME)+1);
+ sprintf( listfile, "%s/" TOC_NAME, archivedir );
+ 
+-listcommand = malloc( strlen(archivers[i].unarchive) + 1 +
+-			strlen( archivers[i].listargs) + 1 +
+-			strlen( name ) + 3 +
+-			strlen( listfile ) +4 );
+-sprintf( listcommand, "%s %s %s > %s", archivers[i].unarchive,
+-	archivers[i].listargs, name, listfile );
+-if ( system(listcommand)!=0 ) {
+-	free(listcommand); free(listfile);
+-	ArchiveCleanup(archivedir);
+-return( NULL );
+-}
+-free(listcommand);
++command[0] = archivers[i].unarchive;
++command[1] = archivers[i].listargs;
++command[2] = name;
++command[3] = NULL; // command args need to be NULL-terminated
++
++if ( g_spawn_sync(
++  NULL,
++  command,
++  NULL,
++  G_SPAWN_SEARCH_PATH, 
++  NULL, 
++  NULL, 
++  , 
++  , 
++  NULL, 
++  NULL
++  ) == FALSE) { // did not successfully execute
++  ArchiveCleanup(archivedir);
++  return( NULL );
++}
++// Write out the listfile to be read in later
++FILE *fp = fopen(listfile, "wb");
++fwrite(stdoutresponse, strlen(stdoutresponse), 1, fp);
++fclose(fp);
+ 
+ desiredfile = ArchiveParseTOC(listfile, archivers[i].ars, );
+ free(listfile);
+@@ -847,22 +862,28 @@ return( NULL );
+ return( NULL );
+ }
+ 
+-/* I tried sending everything to stdout, but that doesn't work if the */
+-/*  output is a directory file (ufo, sfdir) */
+-unarchivecmd = malloc( strlen(archivers[i].unarchive) + 1 +
+-			strlen( archivers[i].listargs) + 1 +
+-			strlen( name ) + 1 +
+-			strlen( desiredfile ) + 3 +
+-			strlen( archivedir ) + 30 );
+-sprintf( unarchivecmd, "( cd %s ; %s %s %s %s ) > /dev/null", archivedir,
+-	archivers[i].unarchive,
+-	archivers[i].extractargs, name, doall ? "" : desiredfile );
+-if ( system(unarchivecmd)!=0 ) {
+-	free(unarchivecmd); free(desiredfile);
+-	ArchiveCleanup(archivedir);
+-return( NULL );
++command[0] = archivers[i].unarchive;
++command[1] = archivers[i].extractargs;
++command[2] = name;
++command[3] = doall ? "" : desiredfile;
++command[4] = NULL;
++
++if ( g_spawn_sync(
++  (gchar*)archivedir,
++ 

Bug#967258: artha: depends on deprecated GTK 2

[Yavor Doganov]

Control: tags -1 + patch
Control: block -1 with 955873

Please find attached a patch -- I tested it a lot but chances are that
I've missed something.

As there is no GtkStatusIcon (aka "trayicon") anymore, the
notifications are sent when the window is closed (and of course, when
they are enabled which was and still is the default).

The "Notify" toolbar item is now permanent (unlike in the original
code) because if a user disables notifications there is no way to
enable them again apart from editing the configuration file (since
there is no systray icon with a popup menu having a "Notify"
GtkCheckMenuItem).

Also please note that this patch formally depends on the patch I sent
to #955873 (hence the block) as that patch is its parent.  It cannot
be applied cleanly to current git master because of that but otherwise
this bug does not depend on it; they're completely orthogonal.
>From 5c15a90a1b6e4f912d1fd326d055c4bca2093ea6 Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Fri, 8 Mar 2024 00:26:46 +0200
Subject: [PATCH] Port to GTK 3 (#967258)

---
 debian/changelog  |4 +-
 debian/control|3 +-
 debian/patches/gtk3.patch | 2406 +
 debian/patches/series |1 +
 4 files changed, 2411 insertions(+), 3 deletions(-)
 create mode 100644 debian/patches/gtk3.patch

diff --git a/debian/changelog b/debian/changelog
index abf4b48..5086ebd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,8 +3,10 @@ artha (1.0.5-4) UNRELEASED; urgency=medium
   * Team upload.
   * debian/patches/no-dbus-glib.patch: New; stop using dbus-glib in favor
 of dbus-gmain as recommended (Closes: #955873).
+  * debian/patches/gtk3.patch: New; port to GTK 3 (Closes: #967258).
   * debian/control (Build-Depends): Replace libdbus-glib-1-dev with
-libdbus-1-dev.
+libdbus-1-dev and libgtk2.0-dev with libgtk-3-dev.
+(Recommends): Drop libnotify4, the program uses GNotification now.
 
  -- Yavor Doganov   Mon, 04 Mar 2024 16:53:11 +0200
 
diff --git a/debian/control b/debian/control
index 83103fa..d2cc751 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Section: utils
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
wordnet-dev,
-   libgtk2.0-dev,
+   libgtk-3-dev,
libdbus-1-dev
 Standards-Version: 4.6.0
 Vcs-Browser: https://salsa.debian.org/science-team/artha
@@ -20,7 +20,6 @@ Depends: ${misc:Depends},
  ${shlibs:Depends},
  wordnet
 Recommends: wordnet-sense-index,
-libnotify4,
 libenchant-2-2
 Suggests: aspell-en
 Description: Handy off-line thesaurus based on WordNet
diff --git a/debian/patches/gtk3.patch b/debian/patches/gtk3.patch
new file mode 100644
index 000..2fa388a
--- /dev/null
+++ b/debian/patches/gtk3.patch
@@ -0,0 +1,2406 @@
+Description: Port to GTK 3.
+Bug-Debian: https://bugs.debian.org/967258
+Author: Yavor Doganov 
+Forwarded: no
+Last-Update: 2024-03-08
+---
+
+--- artha.orig/configure.ac
 artha/configure.ac
+@@ -55,12 +55,10 @@
+ AC_SUBST([WORDNET_LIB])
+ 
+ 
+-# GtkComboBox with entry only since 2.24 only, hence check for GTK+-2.0 >= 
2.24
+-# check for GTK+ and GLib
+-PKG_CHECK_MODULES([GTK], [gtk+-2.0 >= 2.24 glib-2.0 >= 2.40], , [
++PKG_CHECK_MODULES([GTK], [gtk+-3.0 >= 3.21.4 glib-2.0 >= 2.40], , [
+ AC_MSG_RESULT(no)
+ AC_MSG_ERROR([
+-You must have GTK+ 2.0 (version 2.24 or above) and GLib 2.0 (version 2.40
++You must have GTK+ 3.0 (version 3.21.4 or above) and GLib 2.0 (version 2.40
+ or above) development headers installed to build.
+ 
+ If you have these installed already you may need to install pkg-config so 
+--- artha.orig/src/gui.c
 artha/src/gui.c
+@@ -54,7 +54,7 @@
+ static gboolean   was_double_click = FALSE, 
last_search_successful = FALSE, advanced_mode = FALSE, auto_contract = FALSE;
+ static gboolean   hotkey_set = FALSE, mod_suggest = FALSE;
+ // options which default to true
+-static gboolean   notifier_enabled = TRUE, show_polysemy = TRUE, 
launch_minimized = TRUE, show_trayicon = TRUE;
++static gboolean   notifier_enabled = TRUE, show_polysemy = TRUE, 
launch_minimized = TRUE;
+ static gboolean   last_lookup_a_notification = FALSE;
+ static gchar  last_search[MAX_LEMMA_LEN] = "";
+ #ifdef X11_AVAILABLE
+@@ -63,13 +63,11 @@
+ guint32   last_hotkey_time = 0;
+ static guint  num_lock_mask = 0, caps_lock_mask = 0, 
scroll_lock_mask = 0;
+ #endif
+-static guint  hotkey_trials[] = {GDK_w, GDK_a, GDK_t, GDK_q};
++static guint  hotkey_trials[] = {GDK_KEY_w, GDK_KEY_a, 
GDK_KEY_t, GDK_KEY_q};
+ GtkAccelKey   app_hotkey = {0};
+ static gint   notify_toolbar_index = -1;
+ static guint  status_msg_context_id = 0;
+ static GString*wordnet_terms = NULL;
+-NotifyNotification*mod_notifier = 

Bug#1065441: dh-python: pybuild's pyproject plugin puts data files in different directory than the distutils plugin

[Brett Holman]

>From a conversation in Libera's #debian-python channel today, it sounds like
making pybuild's pyproject plugin backwards compatible for writing data_files
to the root filesystem is unlikely to happen. I've filed a bug[1]
against the upstream
cloud-init project to make the required upstream changes to support PEP517 on
debian-based distros. More context can be found there.

[1] https://github.com/canonical/cloud-init/issues/5027

Bug#955873: artha: Depends on deprecated dbus-glib

[Yavor Doganov]

Control: tags -1 + patch

Please find attached a patch.
>From 6c94fcfbf0dc45114602312c8bc6f1bededbf840 Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Mon, 4 Mar 2024 16:56:28 +0200
Subject: [PATCH] Drop dbus-glib dependency (#955873)

---
 debian/changelog  |  10 +
 debian/control|   2 +-
 debian/patches/no-dbus-glib.patch | 810 ++
 debian/patches/series |   1 +
 4 files changed, 822 insertions(+), 1 deletion(-)
 create mode 100644 debian/patches/no-dbus-glib.patch

diff --git a/debian/changelog b/debian/changelog
index 9ae7a98..abf4b48 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+artha (1.0.5-4) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * debian/patches/no-dbus-glib.patch: New; stop using dbus-glib in favor
+of dbus-gmain as recommended (Closes: #955873).
+  * debian/control (Build-Depends): Replace libdbus-glib-1-dev with
+libdbus-1-dev.
+
+ -- Yavor Doganov   Mon, 04 Mar 2024 16:53:11 +0200
+
 artha (1.0.5-3) unstable; urgency=medium
 
   * DEP5 copyright
diff --git a/debian/control b/debian/control
index 780d311..83103fa 100644
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,7 @@ Priority: optional
 Build-Depends: debhelper-compat (= 13),
wordnet-dev,
libgtk2.0-dev,
-   libdbus-glib-1-dev
+   libdbus-1-dev
 Standards-Version: 4.6.0
 Vcs-Browser: https://salsa.debian.org/science-team/artha
 Vcs-Git: https://salsa.debian.org/science-team/artha.git
diff --git a/debian/patches/no-dbus-glib.patch 
b/debian/patches/no-dbus-glib.patch
new file mode 100644
index 000..11e36d9
--- /dev/null
+++ b/debian/patches/no-dbus-glib.patch
@@ -0,0 +1,810 @@
+Description: Stop using dbus-glib.
+Bug-Debian: https://bugs.debian.org/955873
+Author: Yavor Doganov 
+Forwarded: no
+Last-Update: 2024-03-08
+---
+
+--- artha.orig/configure.ac
 artha/configure.ac
+@@ -57,10 +57,10 @@
+ 
+ # GtkComboBox with entry only since 2.24 only, hence check for GTK+-2.0 >= 
2.24
+ # check for GTK+ and GLib
+-PKG_CHECK_MODULES([GTK], [gtk+-2.0 >= 2.24 glib-2.0 >= 2.22], , [
++PKG_CHECK_MODULES([GTK], [gtk+-2.0 >= 2.24 glib-2.0 >= 2.40], , [
+ AC_MSG_RESULT(no)
+ AC_MSG_ERROR([
+-You must have GTK+ 2.0 (version 2.24 or above) and GLib 2.0 (version 2.22 
++You must have GTK+ 2.0 (version 2.24 or above) and GLib 2.0 (version 2.40
+ or above) development headers installed to build.
+ 
+ If you have these installed already you may need to install pkg-config so 
+@@ -97,12 +97,12 @@
+ # begin of POSIX specific config
+ if test "$build_mach" = "posix"; then
+ 
+-# check if dbus-1 alone is enough or dbus-glib-1 alone is enough
+-PKG_CHECK_MODULES([libdbus], [dbus-1 >= 0.60 dbus-glib-1 >= 0.60], 
++# check if dbus-1 alone is enough
++PKG_CHECK_MODULES([libdbus], [dbus-1 >= 1.8],
+ [AC_DEFINE([DBUS_AVAILABLE], [], [Dbus dev. headers are present])], [
+ AC_MSG_RESULT(no)
+ AC_MSG_ERROR([
+-You must have the dbus and dbus-glib-1 (version 0.60 or above) 
++You must have the dbus (version 1.8 or above)
+ development headers installed!
+ 
+ If it is installed already, you may need to install pkg-config so 
+--- artha.orig/src/Makefile.am
 artha/src/Makefile.am
+@@ -9,7 +9,7 @@
+ libwni_a_SOURCES = wni.c wni.h
+ 
+ artha_DEPENDENCIES = libwni.a
+-artha_SOURCES = mod_notify.c mod_notify.h \
++artha_SOURCES = dbus-gmain.c dbus-gmain.h mod_notify.c mod_notify.h \
+   suggestions.c suggestions.h \
+   hotkey_editor.c hotkey_editor.h \
+   gui.c gui.h addons.h
+@@ -38,7 +38,7 @@
+ 
+ if POSIX
+ AM_CFLAGS += @libdbus_CFLAGS@
+-artha_LDADD += -lX11 -ldbus-1 -ldbus-glib-1 -lgtk-x11-2.0 -lgdk-x11-2.0 \
++artha_LDADD += -lX11 -ldbus-1 -lgtk-x11-2.0 -lgdk-x11-2.0 \
+-lgio-2.0 -lgmodule-2.0 -lgobject-2.0 -lglib-2.0
+ else
+ artha_LDADD += @GTK_LIBS@
+--- /dev/null
 artha/src/dbus-gmain.c
+@@ -0,0 +1,666 @@
++/* -*- mode: C; c-file-style: "gnu" -*- */
++/* dbus-gmain.c GLib main loop integration
++ *
++ * Copyright © 2002-2003 CodeFactory AB
++ * Copyright © 2002-2010 Red Hat, Inc.
++ * Copyright © 2003 James Willcox
++ * Copyright © 2006 Marc-Andre Lureau
++ * Copyright © 2006-2018 Collabora Ltd.
++ * Copyright © 2010-2012 Mike Gorse
++ *
++ * SPDX-License-Identifier: AFL-2.1 OR GPL-2.0-or-later
++ *
++ * Licensed under the Academic Free License version 2.1
++ *
++ * This program is free software; you can redistribute it and/or modify
++ * it under the terms of the GNU General Public License as published by
++ * the Free Software Foundation; either version 2 of the License, or
++ * (at your option) any later version.
++ *
++ * This program is distributed in the hope that it will be useful,
++ * but WITHOUT ANY WARRANTY; without even the implied warranty of
++ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
++ * GNU General Public License for more details.
++ *
++ * You should have received a copy of the GNU 

Bug#1061731: fwupd: Failed to load daemon: failed to load engine: Failed to load config: Key file does not have group “redfish”

[Richard B]

Hello.

I can confirm that upgrading fwupd and libfwupd2 on Trixie to 1.9.14-1 
and installing the package maintainer's version of /etc/fwupd/fwupd.conf 
allowed the fwupd status to start:


   sudo apt upgrade
   Reading package lists... Done
   Building dependency tree... Done
   Reading state information... Done
   Calculating upgrade... Done
   The following packages will be upgraded:
  fwupd libfwupd2
   2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
   Need to get 0 B/3,833 kB of archives.
   After this operation, 54.3 kB of additional disk space will be used.
   Do you want to continue? [Y/n] y
   Retrieving bug reports... Done
   Parsing Found/Fixed information... Done
   serious bugs of fwupd (1.9.11-1 → 1.9.14-1) 
 b1 - #1061731 - fwupd: Failed to load daemon: failed to load
   engine: Failed to load config: Key file does not have group “redfish”
   Summary:
 fwupd(1 bug)
   Are you sure you want to install/upgrade the above packages?
   [Y/n/?/...] y
   Reading changelogs... Done
   ...
   Configuration file '/etc/fwupd/fwupd.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
   *** fwupd.conf (Y/I/N/O/D/Z) [default=N] ? y
   Installing new version of config file /etc/fwupd/fwupd.conf ...
   fwupd-offline-update.service is a disabled or a static unit not
   running, not starting it.
   fwupd-refresh.service is a disabled or a static unit not running,
   not starting it.
   fwupd.service is a disabled or a static unit not running, not
   starting it.
   Processing triggers for libc-bin (2.37-15) ...
   Processing triggers for man-db (2.12.0-3) ...
   Processing triggers for dbus (1.14.10-4) ...
   Processing triggers for hicolor-icon-theme (0.17-2) ...

   systemctl status fwupd
   ○ fwupd.service - Firmware update daemon
 Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static)
 Active: inactive (dead)
   Docs: https://fwupd.org/

   sudo systemctl start fwupd

   systemctl status fwupd
   ● fwupd.service - Firmware update daemon
 Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static)
 Active: active (running) since Thu 2024-03-07 16:37:27 CST; 3s ago
   Docs: https://fwupd.org/
   Main PID: 22184 (fwupd)
  Tasks: 7 (limit: 18110)
 Memory: 23.7M (peak: 108.7M)
    CPU: 988ms
 CGroup: /system.slice/fwupd.service
 └─22184 /usr/libexec/fwupd/fwupd

I kept fwupd at 1.9.11-1 since this bug was reported, but the new 
version seems to be in the clear.


Best.

Richard

Bug#1064676: additional information

[Vladimir Petko]

Dear Maintainers,

  Would it be possible to consider a merge request[1] that addresses this issue?

Best Regards,
 Vladimir.

 [1] 
https://salsa.debian.org/android-tools-team/android-platform-tools-apksig/-/merge_requests/6

Bug#1065643: debian-policy: Refer to «dpkg-buildtree clean» for dpkg generated files

[Guillem Jover]

Package: debian-policy
Version: 4.6.2.1
Severity: wishlist

Hi!

Currently the Debian policy lists several files that are generated by
dpkg tools, but because there was no matching dpkg tool to clean them
up, it delegates that responsibility to packagers. With dpkg 1.22.3 a
new dpkg-buildtree tool was introduced that supports a «clean» action
precisely to take care of removing all these files. In the future I'd
like to change the location of some of these files, but that requires
for packages that do not use a helper to be updated to match the dpkg
behavior. While I expect this to be controlled via dpkg-build-api, it
would be best if such packages switched to use dpkg-buildtree to have
automatic handling when that time comes.

I've worded the changes as an example, because I don't want to impose
that packages should be using this if they are using a helper or that
helpers necessarily have to call it. If you'd prefer me to spell that
out more explicitly I'm happy to try to come up with some wording. It
intends to be more informational than a requirement, as I am going to
be filing wishlist bugs with patches as time permits, anyway.

I'm attaching a patch to add references to that new tool.

Thanks,
Guillem
From afac52fa956087eb737c123682f634fc739c7e20 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Tue, 27 Feb 2024 23:37:06 +0100
Subject: [PATCH] =?UTF-8?q?Add=20references=20to=20=C2=ABdpkg-buildtree=20?=
 =?UTF-8?q?clean=C2=BB=20for=20debian/{substvars,files}?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

These files are generated by dpkg tools (and in some cases by helpers),
but the maintainer was responsible for cleaning them up. There is now
a new command that will take care of cleaning these (and any other
future) files that the dpkg suite might end up generating, making their
introduction easier as the responsibility to remove them shifts back
where it belongs.
---
 policy/ch-source.rst | 7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/policy/ch-source.rst b/policy/ch-source.rst
index 4307e89..2fb05cd 100644
--- a/policy/ch-source.rst
+++ b/policy/ch-source.rst
@@ -685,7 +685,7 @@ variables are also available.
 
 The ``debian/substvars`` file is usually generated and modified
 dynamically by ``debian/rules`` targets, in which case it must be
-removed by the ``clean`` target.
+removed by the ``clean`` target (for example with ``dpkg-buildtree clean``).
 
 See :manpage:`deb-substvars(5)` for full details about source variable
 substitutions, including the format of ``debian/substvars``.
@@ -725,8 +725,9 @@ building packages to record which files are being generated.
 
 It should not exist in a shipped source package, and so it (and any
 backup files or temporary files such as ``files.new``)  [#]_ should be
-removed by the ``clean`` target. It may also be wise to ensure a fresh
-start by emptying or removing it at the start of the ``binary`` target.
+removed by the ``clean`` target (for example with ``dpkg-buildtree clean``).
+It may also be wise to ensure a fresh start by emptying or removing it at the
+start of the ``binary`` target.
 
 When ``dpkg-gencontrol`` is run for a binary package, it adds an entry
 to ``debian/files`` for the ``.deb`` file that will be created when
-- 
2.43.0

Bug#1065642: nvidia-driver: Fails to build module due to outdated *nvidia-settings*

[Paul Menzel]

Package: nvidia-driver
Version: 535.104.12-2
Severity: normal


Dear Debian folks,


Upgrading from 525.147.05-1 to 535.104.12-2 with

apt install -t experimental nvidia-driver`

the DKMS build failed because nvidia-settings was still at 525.147.05-1, 
and a newer version is required. I wonder, why it could be installed in 
the first place, as *nvidia-settings* is listed as a recommends with the 
correct version requirement [1].



rec: nvidia-settings (>= 535)


Any idea, how this could happen?

I guess I could remove *nvidia-settings* for the time being, so 
installation of the actual Nvidia driver modules succeeds.



Kind regards,

Paul


[1]: https://packages.debian.org/experimental/nvidia-driver

Bug#1064763: possible fix

[Daniel Kondor]

Hi,

I've looked into this, and I believe that the attached two patches 
should fix this. However, I cannot test this on Debian -- I'm on Ubuntu 
22.04 where cairo-dock-plug-ins builds and installs well with or without 
the patches.


It would be great to know if these really fix the problem, so we can 
include these fixes in the next release.


Best,

Daniel


From 1aaf4b9d5c10167c1c14394ad940684c7aef65ec Mon Sep 17 00:00:00 2001
From: Daniel Kondor 
Date: Thu, 7 Mar 2024 22:39:19 +0100
Subject: [PATCH 1/2] Dbus: do not use deprecated distutils Python module

---
 Dbus/interfaces/bash/setup.py   | 2 +-
 Dbus/interfaces/python/setup.py | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Dbus/interfaces/bash/setup.py b/Dbus/interfaces/bash/setup.py
index 80aa9d418..756bf3474 100644
--- a/Dbus/interfaces/bash/setup.py
+++ b/Dbus/interfaces/bash/setup.py
@@ -13,7 +13,7 @@
 # GNU General Public License for more details.
 # http://www.gnu.org/licenses/licenses.html#GPL
 
-from distutils.core import setup
+from setuptools import setup
 setup(name='CDBashApplet',
 		version='1.0',
 		license='GPL-3',
diff --git a/Dbus/interfaces/python/setup.py b/Dbus/interfaces/python/setup.py
index af33b73bd..04525688f 100644
--- a/Dbus/interfaces/python/setup.py
+++ b/Dbus/interfaces/python/setup.py
@@ -13,7 +13,7 @@
 # GNU General Public License for more details.
 # http://www.gnu.org/licenses/licenses.html#GPL
 
-from distutils.core import setup
+from setuptools import setup
 setup(name='CDApplet',
 		version='1.0',
 		license='GPL-3',
-- 
2.34.1

From 5d747b30271961daf3dc92b2c77fd8b10fb3acd0 Mon Sep 17 00:00:00 2001
From: Daniel Kondor 
Date: Thu, 7 Mar 2024 22:40:23 +0100
Subject: [PATCH 2/2] Dbus: do not use a deprecated CMake function

---
 Dbus/interfaces/bash/BashInstall.cmake.in | 46 ---
 Dbus/interfaces/bash/CMakeLists.txt   |  6 +--
 Dbus/interfaces/python/CMakeLists.txt |  6 +--
 Dbus/interfaces/python/PythonInstall.cmake.in | 46 ---
 4 files changed, 66 insertions(+), 38 deletions(-)

diff --git a/Dbus/interfaces/bash/BashInstall.cmake.in b/Dbus/interfaces/bash/BashInstall.cmake.in
index dd0f7924f..d46a02e9f 100644
--- a/Dbus/interfaces/bash/BashInstall.cmake.in
+++ b/Dbus/interfaces/bash/BashInstall.cmake.in
@@ -2,38 +2,52 @@
 
 IF ("@PYTHON2_FOUND@" STREQUAL "TRUE")
 	IF("@ROOT_PREFIX@" STREQUAL "")
-		EXEC_PROGRAM("@PYTHON2_EXECUTABLE@" "${CMAKE_CURRENT_BINARY_DIR}" ARGS
+		set (ROOT1 "$ENV{DESTDIR}")
+		IF ("${ROOT1}" STREQUAL "")
+			set (ROOT1 "/")
+		ENDIF()
+		execute_process(COMMAND "@PYTHON2_EXECUTABLE@"
 		"setup.py" "install"
-		"--prefix=${CMAKE_INSTALL_PREFIX}"
-		"--root=`test -z \"\$DESTDIR\" && echo / || echo \$DESTDIR`"
-		"@DEBIAN_INSTALL_LAYOUT@")
+		"--prefix=@CMAKE_INSTALL_PREFIX@"
+		"--root=${ROOT1}"
+		@DEBIAN_INSTALL_LAYOUT@
+		WORKING_DIRECTORY "@CMAKE_CURRENT_BINARY_DIR@")
 	ELSEIF("@python_no_deb_layout@" STREQUAL "")
-		EXEC_PROGRAM("@PYTHON2_EXECUTABLE@" "${CMAKE_CURRENT_BINARY_DIR}" ARGS
+		execute_process(COMMAND "@PYTHON2_EXECUTABLE@"
 		"setup.py" "install"
 		"--root=@ROOT_PREFIX@"
-		"@DEBIAN_INSTALL_LAYOUT@")
+		@DEBIAN_INSTALL_LAYOUT@
+		WORKING_DIRECTORY "@CMAKE_CURRENT_BINARY_DIR@")
 	ELSE()
-		EXEC_PROGRAM("@PYTHON2_EXECUTABLE@" "${CMAKE_CURRENT_BINARY_DIR}" ARGS
+		execute_process(COMMAND "@PYTHON2_EXECUTABLE@"
 		"setup.py" "install"
-		"--root=@ROOT_PREFIX@")
+		"--root=@ROOT_PREFIX@"
+		WORKING_DIRECTORY "@CMAKE_CURRENT_BINARY_DIR@")
 	ENDIF()
 ENDIF()
 
 IF ("@PYTHON3_FOUND@" STREQUAL "TRUE")
 	IF("@ROOT_PREFIX@" STREQUAL "")
-		EXEC_PROGRAM("@PYTHON3_EXECUTABLE@" "${CMAKE_CURRENT_BINARY_DIR}" ARGS
+		set (ROOT1 "$ENV{DESTDIR}")
+		IF ("${ROOT1}" STREQUAL "")
+			set (ROOT1 "/")
+		ENDIF()
+		execute_process(COMMAND "@PYTHON3_EXECUTABLE@"
 		"setup.py" "install"
-		"--prefix=${CMAKE_INSTALL_PREFIX}"
-		"--root=`test -z \"\$DESTDIR\" && echo / || echo \$DESTDIR`"
-		"@DEBIAN_INSTALL_LAYOUT@")
+		"--prefix=@CMAKE_INSTALL_PREFIX@"
+		"--root=${ROOT1}"
+		@DEBIAN_INSTALL_LAYOUT@
+		WORKING_DIRECTORY "@CMAKE_CURRENT_BINARY_DIR@")
 	ELSEIF("@python_no_deb_layout@" STREQUAL "")
-		EXEC_PROGRAM("@PYTHON3_EXECUTABLE@" "${CMAKE_CURRENT_BINARY_DIR}" ARGS
+		execute_process(COMMAND "@PYTHON3_EXECUTABLE@"
 		"setup.py" "install"
 		"--root=@ROOT_PREFIX@"
-		"@DEBIAN_INSTALL_LAYOUT@")
+		@DEBIAN_INSTALL_LAYOUT@
+		WORKING_DIRECTORY "@CMAKE_CURRENT_BINARY_DIR@")
 	ELSE()
-		EXEC_PROGRAM("@PYTHON3_EXECUTABLE@" "${CMAKE_CURRENT_BINARY_DIR}" ARGS
+		execute_process(COMMAND "@PYTHON3_EXECUTABLE@"
 		"setup.py" "install"
-		"--root=@ROOT_PREFIX@")
+		"--root=@ROOT_PREFIX@"
+		WORKING_DIRECTORY "@CMAKE_CURRENT_BINARY_DIR@")
 	ENDIF()
 ENDIF()
diff --git a/Dbus/interfaces/bash/CMakeLists.txt b/Dbus/interfaces/bash/CMakeLists.txt
index 024296919..e1fd86763 100644
--- 

Bug#1065638: systemd-journald: systemd-journald restart misses SyslogFacility

[Michael Biebl]

Control: tags -1 + upstream

Am 07.03.24 um 20:25 schrieb Kai Palomaki:

Package: systemd
Version: 247.3-7+deb11u4
Severity: normal
X-Debbugs-Cc: armando.va...@gmail.com

Dear Maintainer,

* What led up to the situation?
A systemd service unit "test" has SyslogFacility=local0 set. Service is 
running and logging lines.
Log lines have SYSLOG_FACILITY=16 when observed with journalctl -o verbose.
Restart journald. After restart of journald, log lines have no more 
SYSLOG_FACILITY=16.
To restore SYSLOG_FACILITY=16 in journal logs, one has to restart service unit 
"test".

* What exactly did you do (or not do) that was effective (or
  ineffective)?
systemctl restart systemd-journald.service

* What was the outcome of this action?
journald did not record the SyslogFacility set in the service unit file.

* What outcome did you expect instead?
journald should continue recording SyslogFacility set in the service unit 
file without needing to restart the service having the SyslogFacility set.



The Debian package doesn't ship any patches in that regard, thus this 
issue should be raised upstream.


For that, please try to reproduce the issue first with a recent version 
of systemd (say v254 or v255) and if it's reproducible, report it at

https://github.com/systemd/systemd/issues
and then report back with the issue number.

Thanks,
Michael



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065641: gnome-control-center: "Sharing" hangs/crashes when gnome-remote-desktop is installed

[Social]

Package: gnome-control-center

Version: 1:43.6-2~deb12u1

Severity: important

 

 

How to reproduce:

*   gnome-remote-desktop is installed
*   create a new user
*   login as the new user
*   start Settings and switch to Sharing

 

Note that also grdctl rdp set-credentials   hangs forever

Running gnome-control-center -vvv results in following messages:

 

22:24:00.0401 cc-window:DEBUG: Time to open panel
'Sharing': 0.283450s

22:24:00.0401 cc-window:DEBUG: Added 'network' to the
previous panels

(gnome-control-center:325748): dconf-DEBUG: 22:24:00.535: watch_fast:
"/org/gnome/desktop/file-sharing/" (establishing: 0, active: 0)

(gnome-control-center:325748): dconf-DEBUG: 22:24:00.537: watch_established:
"/org/gnome/desktop/file-sharing/" (establishing: 1)

(gnome-control-center:325748): dconf-DEBUG: 22:24:00.549: watch_fast:
"/org/gnome/desktop/remote-desktop/rdp/" (establishing: 0, active: 0)

(gnome-control-center:325748): dconf-DEBUG: 22:24:00.552: watch_established:
"/org/gnome/desktop/remote-desktop/rdp/" (establishing: 1)

22:24:00.0641  sharing-cc-panel:DEBUG: No RDP credentials
available

22:24:00.0669  sharing-cc-panel:DEBUG: No RDP credentials
available

(gnome-control-center:325748): dconf-DEBUG: 22:24:00.693: watch_fast:
"/org/gnome/desktop/remote-desktop/rdp/" (establishing: 0, active: 1)

(gnome-control-center:325748): dconf-DEBUG: 22:24:00.693: unwatch_fast:
"/org/gnome/desktop/remote-desktop/rdp/" (active: 2, establishing: 0)

22:24:00.0693  sharing-cc-panel:DEBUG: Error getting remote
login state: GDBus.Error:org.freedesktop.DBus.Error.FileNotFound: No such
file or directory

 

What helps:

*   Logout from the new user, and login as the new user
*   Now the Sharing settings work

 

What does not help:

Enabling the testing repository makes it worse, sharing settings for rdp are
completely gone.

 

 



 

 

Thank You!

 

 

 

-- 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-18-amd64 (SMP w/4 CPU threads; PREEMPT)

Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en

Shell: /bin/sh linked to /usr/bin/dash

Init: systemd (via /run/systemd/system)

LSM: AppArmor: enabled

 

Versions of packages gnome-control-center depends on:

ii  accountsservice   22.08.8-6

ii  apg   2.2.3.dfsg.1-5+b2

ii  colord1.4.6-2.2

ii  desktop-base  12.0.6+nmu1~deb12u1

ii  desktop-file-utils0.26-1

ii  gnome-control-center-data 1:43.6-2~deb12u1

ii  gnome-desktop3-data   43.2-2

ii  gnome-settings-daemon 43.0-4

ii  gsettings-desktop-schemas 43.0-1

ii  libaccountsservice0   22.08.8-6

ii  libadwaita-1-01.2.2-1

ii  libc6 2.36-9+deb12u4

ii  libcairo2 1.16.0-7

ii  libcolord-gtk4-1  0.3.0-3.1

ii  libcolord21.4.6-2.2

ii  libcups2  2.4.2-3+deb12u5

ii  libepoxy0 1.5.10-1

ii  libfontconfig12.14.1-4

ii  libgcr-base-3-1   3.41.1-1+b1

ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1+b1

ii  libglib2.0-0  2.74.6-2

ii  libgnome-bg-4-2   43.2-2

ii  libgnome-bluetooth-ui-3.0-13  42.5-3

ii  libgnome-desktop-4-2  43.2-2

ii  libgnome-rr-4-2   43.2-2

ii  libgnutls30   3.7.9-2+deb12u2

ii  libgoa-1.0-0b 3.46.0-1

ii  libgoa-backend-1.0-1  3.46.0-1

ii  libgsound01.0.3-2

ii  libgtk-3-03.24.38-2~deb12u1

ii  libgtk-4-14.8.3+ds-2+deb12u1

ii  libgtop-2.0-112.40.0-2

ii  libgudev-1.0-0237-2

ii  libibus-1.0-5 1.5.27-5

ii  libkrb5-3 1.20.1-2+deb12u1

ii  libmalcontent-0-0 0.11.0-4

ii  libmm-glib0   1.20.4-1

ii  libnm01.42.4-1

ii  libnma-gtk4-0 1.10.6-1

ii  libpango-1.0-01.50.12+ds-1

ii  libpangocairo-1.0-0   1.50.12+ds-1

ii  libpolkit-gobject-1-0 122-3

ii  libpulse-mainloop-glib0   16.1+dfsg1-2+b1

ii  libpulse0 16.1+dfsg1-2+b1

ii  libpwquality1 1.4.5-1+b1

ii  libsecret-1-0 0.20.5-3

ii  libsmbclient  2:4.17.12+dfsg-0+deb12u1

ii  libsnapd-glib-2-1 1.63-5

ii  libudisks2-0  2.9.4-4

ii  libupower-glib3   0.99.20-2

ii  libwacom9 2.6.0-1

ii  libx11-6  2:1.8.4-2+deb12u2

ii  libxi62:1.8-1+b1

ii  libxml2   2.9.14+dfsg-1.3~deb12u1

ii  

Bug#1037327: MariaDB upgrade fails if page compressed tables exist already due to plugin dependency

[debian . 627of]

I also have this issue but it is with the audit plugin, and it impacts MariaDB 
upgrades over apt, rather than an install of MariaDB from scratch.

I receive this message in the syslog from mariadb-server-10.3.postinst

Installation of system tables failed! ...

In /var/log/mysql/error.log, I see this:

[ERROR] mysqld: Can't open shared library '/usr/server_audit.so' (errno: 22, 
cannot open shared object file: No such file or directory)
[ERROR] Couldn't load plugins from 'server_audit.so'.
[ERROR] /usr/sbin/mysqld: unknown variable 
'server_audit=FORCE_PLUS_PERMANENT'[ERROR] Aborting

The database server continues to function correctly after the service starts. 
The audit plugin is functional outside of the postinst script. This issue has 
happened for about a year or two and I never noticed any issues otherwise. I 
was concerned about a new patch adding newly required system tables failing, 
such as with an upgrade from Buster to Bullseye, etc.

I am unsure if this is the exact same issue as this big. If not, let me know 
and I can open a new bug report.

On a mostly normal Buster:
dpkg -l | grep maria

ii libmariadb3:amd64 1:10.4.14+maria~buster amd64 MariaDB database client 
library
ii mariadb-client-10.3 1:10.3.39-0+deb10u2 amd64 MariaDB database client 
binaries
ii mariadb-client-core-10.3 1:10.3.39-0+deb10u2 amd64 MariaDB database core 
client binaries
ii mariadb-common 1:10.4.14+maria~buster all MariaDB database common files 
(e.g. /etc/mysql/conf.d/mariadb.cnf)
ii mariadb-server 1:10.3.39-0+deb10u2 all MariaDB database server (metapackage 
depending on the latest version)
ii mariadb-server-10.3 1:10.3.39-0+deb10u2 amd64 MariaDB database server 
binaries
ii mariadb-server-core-10.3 1:10.3.39-0+deb10u2 amd64 MariaDB database core 
server files
ii mysql-common 1:10.4.14+maria~buster all MariaDB database common files (e.g. 
/etc/mysql/my.cnf)

Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function 'kadm5_s_init_with_password_ctx'

[Ryan Tandy]

The implicit declaration occurs on all arches, but it's a warning, not 
an error. For example on amd64:


smbk5pwd.c:917:23: warning: implicit declaration of function 
‘kadm5_s_init_with_password_ctx’; did you mean ‘kadm5_init_with_password_ctx’? 
[-Wimplicit-function-declaration]
  917 | ret = kadm5_s_init_with_password_ctx( context,
  |   ^~
  |   kadm5_init_with_password_ctx


The binNMUs succeeded on several release arches already. I'm not sure 
why hppa would be different. I see -Werror=implicit-function-declaration 
in its compiler commands, but I don't know where it's coming from.


As for the implicit declaration, I don't remember why I didn't already 
submit a patch for it... At a quick glance it looks like the prototype 
is now in the private header . I don't know if 
there's a reason we can't/shouldn't include that one... The symbol may 
be private, but we're already using it regardless :)

Bug#1065320: linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop during boot & requires power cycle

[Salvatore Bonaccorso]

Control: severity -1 serious
Control: tags -1 + upstream fixed-upstream
Control: forwarded -1 
https://lore.kernel.org/regressions/zd2bsv8vsfjml...@archie.me/ 
https://bugzilla.kernel.org/show_bug.cgi?id=218531
Control: found -1 6.6.15-1
Control: found -1 6.7.4-1~exp1

Hi Lee,

On Sat, Mar 02, 2024 at 05:33:55PM +, Lee Elliott wrote:
> Package: src:linux
> Version: 6.1.76-1
> Severity: critical
> Justification: breaks the whole system
> X-Debbugs-Cc: leeejobsacco...@mail.co.uk
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
>Trying to boot the system with the 6.1.0-18 kernel
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
>I tried adding 'boot_delay=1000' boot option to slow the console
>scroll rate, to enable better recording of the error messages.
> 
>I tried rebooting the previous 6.1.0-17 kernel.
> 
>* What was the outcome of this action?
> 
>After adding the 'boot_delay=1000' option the boot process
>progressed no further than "Loading initial ramdisk ..."
>(left for several minutes - required power cycle).
> 
>The system boots sucessfully on the previous 6.1.0-17 kernel
> 
>* What outcome did you expect instead?
> 
>I expected the system to successfully boot.
> 
>* Additional observations
> 
>This system also normally includes 'hpet=disable' and
>'acpi_enforce_resources=lax' boot options but removing these
>made no difference.
> 
>Although I was not able to boot the system with the
>'boot_delay=1000' option and obtain clear photographs of the
>console output - the ones I've attached suffer from
>'overprinting' - it does seem clear that ACPI errors are
>being reported.
> 
>There appear to be two distinct phases to this problem.
>Initially, ACPI seems to be reporting errors for "GPE", as
>shown in the first attached photograph, but after ~10 seconds
>or so, ACPI then switches to continuously reporting an error
>for PM_TIMER, as shown in the second attached photograph. At
>this point a power cycle is required.
> 
>Purging and reinstalling the package made no difference. Atm,
>only three kernels are installed on this system but I have
>had more in the past as I normally compile my own kernels
>from the corresponding Debian source package. My own 6.1.76-1
>kernel also suffers from the same problem, whereas my own
>6.1.69-1 kernel boots and runs Ok.
> 
>Comparing the kernel configs for 6.1.0-17 and 6.1.0-18
>showed just one functional change - an additional
>Compile-time checks and compiler option, which did not seem
>relevant to this problem.

The images were missing but from the description I assume it's the
same regression as reported in

https://lore.kernel.org/regressions/zd2bsv8vsfjml...@archie.me/
https://bugzilla.kernel.org/show_bug.cgi?id=218531

It looks a fix has landed in mainline:

https://git.kernel.org/linus/aec7d25b497ce4a8d044e9496de0aa433f7f8f06

Regards,
Salvatore

Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function 'kadm5_s_init_with_password_ctx'

[Quanah Gibson-Mount]

--On Thursday, March 7, 2024 5:41 PM + John David Anglin 
 wrote:



Source: openldap
Version: 2.5.13+dfsg-5+b4
Severity: normal
Tags: ftbfs

Dear Maintainer,

See:
https://buildd.debian.org/status/fetch.php?pkg=openldap=hppa=2.5
.13%2Bdfsg-5%2Bb4=1709830559=0

smbk5pwd.c: In function 'smbk5pwd_modules_init':
smbk5pwd.c:917:23: error: implicit declaration of function
'kadm5_s_init_with_password_ctx'; did you mean
'kadm5_init_with_password_ctx'?
[-Werror=implicit-function-declaration]   917 | ret =
kadm5_s_init_with_password_ctx( context,   |
^~


Maybe you're missing a header?  This is a standard Heimdal function:



Or, Debian failed to properly package the Heimdal includes.  But this 
doesn't seem to be the right place to report the issue.


--Quanah

Bug#1065640: Errata

[Rod Webster]

Search the build log for raspberry-firmware.

should be

Search the build log for raspi-firmware.


Rod Webster
*1300 896 832*
+61 435 765 611
VMN®
www.vmn.com.au


*Sole Queensland Distributor*

Bug#1065640: Debian-Live still installs raspi-firmware on X86

[Rod Webster]

Package: Debian-Live
Version: Bookworm 12.5

The current version of the debian-live installer in the Debian Bookworm
repositories installs raspberry-firmware which was a feature of Debian
12.0. This was subsequently resolved with the release of Debian 12.1.

Debian-Live has never been updated in the Debian Repositories from the 12.0
release. Building an image after installing debian-live from Debian's
Bookworm Repository still includes raspi-firmware even on Debian 12.5

Building debian-live from source resolves this issue.

To demonstrate:
Install debian-live from the repositories as described in 3.2.1 of the
debian live manual.
https://live-team.pages.debian.net/live-manual/html/live-manual/installation.en.html#127
clone the linuxcnc live installer from their repositories  (use the default
Bookworm branch)
https://github.com/LinuxCNC/linuxcnc-live-build and build
Search the build log for raspberry-firmware. It will be found.
Remove the debian-live package, build the deb from source and install it as
per 3.2.2 of the Debian Live Manual.
https://live-team.pages.debian.net/live-manual/html/live-manual/installation.en.html#130


Searching build.log for raspi-firmware will not find it.

Resolution:
Please update the Debnian repositories so it is consistent with the source.

I am the linuxcnc user who built our debian live installer mentioned above.
We distribute our ISO via https://linuxcnc.org/downloads/ and this has been
a very frustrating issue for many of our users relying on our ISO.

Rod Webster
*1300 896 832*
+61 435 765 611
VMN®
www.vmn.com.au


*Sole Queensland Distributor*

Bug#1058331: android-platform-tools-base: additional information

[Vladimir Petko]

Package: android-platform-tools-base
Followup-For: Bug #1058331
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

I apologise for submitting it as a debdiff, salsa repository appears to be out
of date.

The attached patch resolves ftbfs due to the internal sun.security and
BouncyCastle API changes.

In Ubuntu, the attached patch was applied to achieve the following:

  * Resolve the failure to build from source (LP: #2056088):
- d/p/{der-output-stream.patch, add-exports.patch}: sun.security
  PKCS7 class now only supports encoding to DerOutputStream.
  Explicitly instantiate it.
- d/p/bouncycastle177-compat.patch: use ASN1OutputStream instead
  of remove DerOutputStream.


Thanks for considering the patch.


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-21-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru android-platform-tools-base-2.2.2/debian/patches/add-exports.patch 
android-platform-tools-base-2.2.2/debian/patches/add-exports.patch
--- android-platform-tools-base-2.2.2/debian/patches/add-exports.patch  
2023-02-03 03:01:58.0 +1300
+++ android-platform-tools-base-2.2.2/debian/patches/add-exports.patch  
2024-03-06 13:16:37.0 +1300
@@ -5,7 +5,7 @@
  }
  
 +compileJava {
-+options.compilerArgs << '--add-exports' << 
'java.base/sun.security.pkcs=ALL-UNNAMED' << '--add-exports' << 
'java.base/sun.security.x509=ALL-UNNAMED'
++options.compilerArgs << '--add-exports' << 
'java.base/sun.security.pkcs=ALL-UNNAMED' << '--add-exports' << 
'java.base/sun.security.x509=ALL-UNNAMED' << '--add-exports' << 
'java.base/sun.security.util=ALL-UNNAMED'
 +}
 +
  task initSdkForTests(type: JavaExec) {
diff -Nru 
android-platform-tools-base-2.2.2/debian/patches/bouncycastle177-compat.patch 
android-platform-tools-base-2.2.2/debian/patches/bouncycastle177-compat.patch
--- 
android-platform-tools-base-2.2.2/debian/patches/bouncycastle177-compat.patch   
1970-01-01 12:00:00.0 +1200
+++ 
android-platform-tools-base-2.2.2/debian/patches/bouncycastle177-compat.patch   
2024-03-06 13:16:37.0 +1300
@@ -0,0 +1,57 @@
+Description: bouncycastle 1.77 compatibility patch
+ Remove usages of DerOutputStream that is no longer public.
+Author: Vladimir Petko 
+Bug-Ubuntu: 
https://bugs.launchpad.net/debian/+source/android-platform-tools-base/+bug/2056088
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058331
+Forwarded: not-needed
+Last-Update: 2024-03-06
+
+--- 
a/build-system/builder/src/main/java/com/android/builder/internal/packaging/sign/SignatureExtension.java
 
b/build-system/builder/src/main/java/com/android/builder/internal/packaging/sign/SignatureExtension.java
+@@ -29,7 +29,8 @@
+ 
+ import org.apache.commons.codec.binary.Base64;
+ import org.bouncycastle.asn1.ASN1InputStream;
+-import org.bouncycastle.asn1.DEROutputStream;
++import org.bouncycastle.asn1.ASN1OutputStream;
++import org.bouncycastle.asn1.ASN1Encoding;
+ import org.bouncycastle.cert.jcajce.JcaCertStore;
+ import org.bouncycastle.cms.CMSException;
+ import org.bouncycastle.cms.CMSProcessableByteArray;
+@@ -610,12 +611,12 @@
+ /*
+  * DEROutputStream is not closeable! OMG!
+  */
+-DEROutputStream dos = null;
++ASN1OutputStream dos = null;
+ try (ASN1InputStream asn1 = new 
ASN1InputStream(sigData.getEncoded())) {
+-dos = new DEROutputStream(outputBytes);
++dos = ASN1OutputStream.create(outputBytes, ASN1Encoding.DER);
+ dos.writeObject(asn1.readObject());
+ 
+-DEROutputStream toClose = dos;
++ASN1OutputStream toClose = dos;
+ dos = null;
+ toClose.close();
+ } catch (IOException e) {
+--- 
a/build-system/builder/src/main/java/com/android/builder/signing/SignedJarApkCreator.java
 
b/build-system/builder/src/main/java/com/android/builder/signing/SignedJarApkCreator.java
+@@ -33,7 +33,8 @@
+ import com.google.common.io.Files;
+ 
+ import org.bouncycastle.asn1.ASN1InputStream;
+-import org.bouncycastle.asn1.DEROutputStream;
++import org.bouncycastle.asn1.ASN1OutputStream;
++import org.bouncycastle.asn1.ASN1Encoding;
+ import org.bouncycastle.cert.jcajce.JcaCertStore;
+ import org.bouncycastle.cms.CMSException;
+ import org.bouncycastle.cms.CMSProcessableByteArray;
+@@ -400,7 +401,7 @@
+ CMSSignedData sigData = gen.generate(data, false);
+ 
+ try (ASN1InputStream asn1 = new 

Bug#1065639: RFS: rapid-photo-downloader/0.9.36-1 -- Photo downloader (importer) from cameras, memory cards, other devices

[Tino Mettler]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "rapid-photo-downloader":

 * Package name : rapid-photo-downloader
   Version  : 0.9.36-1
   Upstream contact : Damon Lynch 
 * URL  : https://damonlynch.net/rapid
 * License  : GPL-3+
 * Vcs  : https://salsa.debian.org/debian/rapid-photo-downloader
   Section  : graphics

The source builds the following binary packages:

  rapid-photo-downloader - Photo downloader (importer) from cameras, memory 
cards, other devices

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/rapid-photo-downloader/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/r/rapid-photo-downloader/rapid-photo-downloader_0.9.36-1.dsc

Changes since the last upload:

 rapid-photo-downloader (0.9.36-1) unstable; urgency=medium
 .
   * New upstream version 0.9.36
   * Update patch 0001-Disable-version-checks-on-startup.patch
   * Remove 0002-Import-setuptools-before-distutils.patch, adopted upstream
   * Adjust Debian copyright
   * Fix python warnings during installation
   * Fix 2 further python warnings

Regards,
-- 
  Tino Mettler

Bug#1061754: python-json-log-formatter ftbfs with Python 3.12 as default

[Colin Watson]

On Tue, Mar 05, 2024 at 06:15:32PM +, Colin Watson wrote:
> While it looks like this was fixed upstream in
> https://github.com/marselester/json-log-formatter/commit/74f04ee4f6aa8e461fcb2d688459888b7279fc73
> and I guess we could cherry-pick that, I also can't reproduce this
> failure in current unstable with Python 3.12.  Can you still reproduce
> this?

I guess it doesn't hurt to apply this anyway, so I'm just going ahead.

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

Bug#1061618: src:haskell-misfortune: unsatisfied build dependency in testing: libghc-regex-pcre-doc

[Peter Green]

On 07/03/2024 19:43, Peter Green wrote:

In raspbian, I removed the reference from misfortune.cabel, removed the
build-dependencies on libghc-regex-pcre* and also (for unrelated reasons)
removed the build-dependency on ghc-doc. After doing so I was able to
successfully build the package.

Scratch that, I thought the build had finished, but it hadn't. It did
in fact fail. The reference in the code to PCRE was in all caps which
is why my grep did not find it.

Bug#1061618: src:haskell-misfortune: unsatisfied build dependency in testing: libghc-regex-pcre-doc

[Peter Green]

Can you please investigate the situation and figure out how to resolve
it? 


I'm no haskell expert, but to me the dependency looks vestigal. Grepping
the source tree for "pcre" finds a mention in the misfortune.cabal
file but no mentions in the actual code, and there are no corresponding
binary dependencies.

In raspbian, I removed the reference from misfortune.cabel, removed the
build-dependencies on libghc-regex-pcre* and also (for unrelated reasons)
removed the build-dependency on ghc-doc. After doing so I was able to
successfully build the package.

Bug#1065638: systemd-journald: systemd-journald restart misses SyslogFacility

[Kai Palomaki]

Package: systemd
Version: 247.3-7+deb11u4
Severity: normal
X-Debbugs-Cc: armando.va...@gmail.com

Dear Maintainer,

   * What led up to the situation?
   A systemd service unit "test" has SyslogFacility=local0 set. Service is 
running and logging lines.
   Log lines have SYSLOG_FACILITY=16 when observed with journalctl -o verbose.
   Restart journald. After restart of journald, log lines have no more 
SYSLOG_FACILITY=16.
   To restore SYSLOG_FACILITY=16 in journal logs, one has to restart service 
unit "test".

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   systemctl restart systemd-journald.service

   * What was the outcome of this action?
   journald did not record the SyslogFacility set in the service unit file.

   * What outcome did you expect instead?
   journald should continue recording SyslogFacility set in the service unit 
file without needing to restart the service having the SyslogFacility set.


-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.118+deb11u1
ii  libacl1  2.2.53-10
ii  libapparmor1 2.13.6-10
ii  libaudit11:3.0-2
ii  libblkid12.36.1-8+deb11u1
ii  libc62.31-13+deb11u7
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.18-4
ii  libcryptsetup12  2:2.3.7-1+deb11u1
ii  libgcrypt20  1.8.7-6
ii  libgnutls30  3.7.1-5+deb11u3
ii  libgpg-error01.38-2
ii  libip4tc21.8.7-1
ii  libkmod2 28-1
ii  liblz4-1 1.9.3-2
ii  liblzma5 5.2.5-2.1~deb11u1
ii  libmount12.36.1-8+deb11u1
ii  libpam0g 1.4.0-9+deb11u1
ii  libseccomp2  2.5.1-1+deb11u1
ii  libselinux1  3.1-3
ii  libsystemd0  247.3-7+deb11u4
ii  libzstd1 1.4.8+dfsg-2.1
ii  mount2.36.1-8+deb11u1
ii  util-linux   2.36.1-8+deb11u1

Versions of packages systemd recommends:
ii  dbus   1.12.28-0+deb11u1
ii  ntp [time-daemon]  1:4.2.8p15+dfsg-1

Versions of packages systemd suggests:
ii  policykit-10.105-31+deb11u1
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.140
ii  libnss-systemd   247.3-7+deb11u4
ii  libpam-systemd   247.3-7+deb11u4
ii  udev 247.3-7+deb11u4

-- no debconf information

Bug#1064617: Passwords should not be changed frequently

[Holger Wansing]

Hi,

Am 7. März 2024 08:50:25 MEZ schrieb Justin B Rye :
>Philip Hands wrote:
>>> Maybe instead of saying "use the system's initial user account to
>>> become root" it should say "allow the system's initial user account
>>> to gain administrative privileges"?  I'm not sure.  Oh, and we might
>>> even want to mention the word "superuser", or then again we might not.
>> 
>> I think Diederik's suggestion of using 'root' for the account and
>> 'super-user' for the privileges might be the way to go.
>
>Looking at what I end up with after another couple of rounds of
>fiddling with it I'm not sure if it's doing quite what you asked for,
>but you still might want it so here it is:
>
>-   Some account needs to have system administrative privileges. The
>-   password/passphrase for that account should be something that
>-   cannot be guessed.
>+   Some account needs to be available with administrative super-user
>+   privileges. The password/passphrase for that account should be
>+   something that cannot be guessed.
>.
>To allow direct password-based access via the 'root' account, you
>can set the password/passphrase for that account here.
>.
>-   Alternatively, you can lock root's password
>+   Alternatively, you can lock the root account's password
>by leaving this setting empty, and
>instead use the system's initial user account
>(which will be set up in the next step)
>-   to become root. This will be enabled for you
>-   by adding that user to the 'sudo' group.
>+   to gain administrative privileges. This will be enabled for you by
>+   adding that initial user to the 'sudo' group.
>.
>Note: what you type here will be hidden (unless you select to show it).

All the above looks like an improvement to me.


Holger


-- 
Sent from /e/ OS on Fairphone3

Bug#1064077: RFS: qt5ct/1.8-1 -- Qt5 Configuration Utility

[Mateusz Łukasik]

W dniu 6.03.2024 o 18:32, Soren Stoutner pisze:

Mateusz,

Did you have any questions about what I was asking here?

Soren

On Tuesday, February 20, 2024 2:40:04 PM MST Soren Stoutner wrote:

Mateusz,

When compiling locally on my system, the current version of lintian

(2.117.0)

found the following problems.  These are not displayed on

mentors.debian.net,

leading me to believe they were recently added checks.

W: qt5ct: link-to-shared-library-in-wrong-package usr/lib/x86_64-linux-gnu/
libqt5ct-common.so.1.8 [usr/lib/x86_64-linux-gnu/libqt5ct-common.so]
N:
N:   Although this package is not a "-dev" package, it installs a
N:   "libsomething.so" symbolic link referencing the corresponding shared
N:   library. When the link doesn't include the version number, it is used

by

N:   the linker when other programs are built against this shared library.
N:
N:   Shared libraries are supposed to place such symbolic links in their
N:   respective "-dev" packages, so it is a bug to include it with the main
N:   library package.
N:
N:   However, if this is a small package which includes the runtime and the
N:   development libraries, this is not a bug. In the latter case, please
N:   override this warning.
N:
N:   Please refer to Development files (Section 8.4) in the Debian Policy
N:   Manual for details.
N:
N:   Visibility: warning
N:   Show-Always: no
N:   Check: libraries/shared/links
N:   Renamed from: non-dev-pkg-with-shlib-symlink
N:
N:
W: qt5ct: package-name-doesnt-match-sonames libqt5ct-common1.8
N:
N:   The package name of a library package should usually reflect the soname
of N:   the included library. The package name can determined from the
library N:   file name with the following code snippet:
N:
N:$ objdump -p /path/to/libfoo-bar.so.1.2.3 | sed -n -e's/
^[[:space:]]*SONAME[[:space:]]*//p' | \
N:sed -r -e's/([0-9])\.so\./\1-/; s/\.so(\.|$)//; y/_/-/; s/(.*)/

\L&/'

N:
N:   Visibility: warning
N:   Show-Always: no
N:   Check: libraries/shared/soname
N:
N:
I: qt5ct: no-symbols-control-file usr/lib/x86_64-linux-gnu/libqt5ct-

common.so.

1.8
N:
N:   Although the package includes a shared library, the package does not

have

N:   a symbols control file.
N:
N:   dpkg can use symbols files in order to generate more accurate library
N:   dependencies for applications, based on the symbols from the library

that

N:   are actually used by the application.
N:
N:   Please refer to the dpkg-gensymbols(1) manual page and
N:https://wiki.debian.org/UsingSymbolsFiles for details.
N:
N:   Visibility: info
N:   Show-Always: no
N:   Check: debian/shlibs

As noted in the text of the checks, there are scenarios where these do not
apply (like small packages that include the runtime and the development
files), which appears to be the case with qt5ct.  Can you please help me to
understand why qt5ct is including this shared library, if there are any

other

packages in Debian that are building against this library, and if you feel
that any of the lintian checks above apply?  If you feel they don’t apply I
would recommend you add lintian overrides and I will be happy to upload your
package.

Soren




Hi Soren,

Sorry for delay. I converted the sources into separate libraries in new 
mentors upload. The soname will change every new version.


Now in lintian only left:

P: qt5ct source: maintainer-manual-page [debian/qt5ct.1]
N:
N:   The maintainer keeps a manual page in ./debian. Please forward the 
manual
N:   page upstream and ask them to include in their version control 
system, and

N:   in their next release.
N:
N:   If the manual page was already forwarded or rejected, or the 
upstream is

N:   gone, please override the tag and annotate it with a suitable comment.
N:
N:   Please refer to social contract item 2, Coordination with upstream
N:   developers (Section 3.1.4) in the Debian Developer's Reference, and
N:   Changes to the upstream sources (Section 4.3) in the Debian Policy 
Manual

N:   for details.
N:
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/manual-pages
N:   Renamed from: maintainer-manpage
N:
N:
X: qt5ct source: debian-watch-does-not-check-openpgp-signature 
[debian/watch]

N:
N:   This watch file does not specify a means to verify the upstream tarball
N:   using a cryptographic signature.
N:
N:   If upstream distributions provides such signatures, please use the
N:   pgpsigurlmangle options in this watch file's opts= to generate the 
URL of
N:   an upstream OpenPGP signature. This signature is automatically 
downloaded
N:   and verified against a keyring stored in 
debian/upstream/signing-key.asc

N:
N:   Of course, not all upstreams provide such signatures but you could 
request
N:   them as a way of verifying that no third party has modified the 
code after

N:   its release (projects such as phpmyadmin, unrealircd, and proftpd have
N:   suffered from this kind of attack).
N:
N:   Please refer to the uscan(1) manual page for details.
N:
N:   Visibility: pedantic
N:   

Bug#1065501: qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb

[Sebastiaan Couwenberg]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/qgis/QGIS/issues/56756

From the build log:

 Operation needs translation in 
QgsCoordinateReferenceSystemUtils::translateProjection: mod_krovak


This is actually caused by PROJ 9.4.0 which introduced support for the 
Modified Krovak projection.


Kind Regards,

Bas

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

Bug#1065634: wv: /usr/share/doc wv is a dangling symlink

[Sven Joachim]

Control: tags -1 + patch

On 2024-03-07 18:49 +0100, Sven Joachim wrote:

> Package: wv
> Version: 1.2.9-6.1
> Severity: serious
> X-Debbugs-Cc: Sven Joachim , Steve Langasek 
> 
>
> After renaming the libwv-1.2-4 library package to libwv-1.2-4t64, the
> /usr/share/doc/wv symlink has become dangling.
>
> ,
> | $ file /usr/share/doc/wv
> | /usr/share/doc/wv: broken symbolic link to libwv-1.2-4
> `
>
> It should point to libwv-1.2-4t64 instead, obviously.

There is a similar broken symlink in the libwv-dev package (which
I do not have installed).  The attached patch takes care of them.

Steve, would you like to upload that?  Note that the package is
orphaned, therefore I have created a debian/changelog entry for a QA
upload rather than for another NMU.

Cheers,
   Sven

diff -Nru wv-1.2.9/debian/changelog wv-1.2.9/debian/changelog
--- wv-1.2.9/debian/changelog	2024-02-29 06:47:50.0 +0100
+++ wv-1.2.9/debian/changelog	2024-03-07 19:42:29.0 +0100
@@ -1,3 +1,10 @@
+wv (1.2.9-7) unstable; urgency=medium
+
+  * QA upload.
+  * Fix dangling /usr/share/doc symlinks (Closes: #1065634).
+
+ -- Sven Joachim   Thu, 07 Mar 2024 19:42:29 +0100
+
 wv (1.2.9-6.1) unstable; urgency=medium

   * Non-maintainer upload.
diff -Nru wv-1.2.9/debian/libwv-dev.links wv-1.2.9/debian/libwv-dev.links
--- wv-1.2.9/debian/libwv-dev.links	2023-09-17 23:45:41.0 +0200
+++ wv-1.2.9/debian/libwv-dev.links	2024-03-07 19:41:38.0 +0100
@@ -1 +1 @@
-usr/share/doc/libwv-1.2-4 usr/share/doc/libwv-dev
+usr/share/doc/libwv-1.2-4t64 usr/share/doc/libwv-dev
diff -Nru wv-1.2.9/debian/wv.links wv-1.2.9/debian/wv.links
--- wv-1.2.9/debian/wv.links	2023-09-17 23:45:41.0 +0200
+++ wv-1.2.9/debian/wv.links	2024-03-07 19:01:19.0 +0100
@@ -1 +1 @@
-usr/share/doc/libwv-1.2-4 usr/share/doc/wv
+usr/share/doc/libwv-1.2-4t64 usr/share/doc/wv

Bug#1065637: pmbootstrap: postmarketOS project broke compatibility with v2.1.0

[erebion]

Package: pmbootstrap
Version: 2.1.0-1
Severity: important
X-Debbugs-Cc: ereb...@erebion.eu

Dear maintainers,

recent changes in pmaports broke compatibility with pmbootstrap.

$ pmbootstrap
[19:24:32] NOTE: you are using pmbootstrap version 2.1.0, but version 
2.2.0 is required.
[19:24:32] ERROR: Please update your pmbootstrap version (with your 
distribution's package manager, or with pip, depending on how you have 
installed it). (...)


The solution would be simply to package the new version.

The issue will arise even on currently working setups as soon as users 
execute "pmbootstrap pull" per the recommendation of pmbootstrap itself.


Cheers,

erebion

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

Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 pmbootstrap depends on:
ii python3 3.11.6-1

pmbootstrap recommends no packages.

pmbootstrap suggests no packages.

-- no debconf information

--
erebion

Matrix: @erebion:erebion.eu

My languages: German, English, Swedish, Norwegian, Danish
Yes, I'm a language nerd. Feel free to write to me in any of the aforementioned 
languages.



OpenPGP_0x8EAF40326E02AE7D.asc
Description: OpenPGP public key
BEGIN:VCARD
VERSION:4.0
N:;erebion;;;
FN:erebion
EMAIL;PREF=1:ereb...@erebion.eu
IMPP:matrix:u/erebion:erebion.eu
URL:https://erebion.eu
TZ:Europe/Berlin
END:VCARD


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065167: google-perftools: FTBFS on armhf/armel: static_assert(sizeof(int32_t) == sizeof(off_t), "")

[Aliaksey Kandratsenka]

Hi again. So last time I failed to check _TIME_BITS=64. I only tested
_FILE_OFFSET_BITS. And 32-bit arm bits continue failing.
https://buildd.debian.org/status/fetch.php?pkg=google-perftools=armel=2.15-2=1709539473=log

Please also cherry-pick
https://github.com/gperftools/gperftools/commit/02adc8ceab39bbeac1f65e10bde577e1753094fa
.

On Fri, Mar 1, 2024 at 4:32 PM Aliaksey Kandratsenka <
alkondrate...@gmail.com> wrote:

> Hi. Upstream maintainer here. Please cherry-pick:
> https://github.com/gperftools/gperftools/commit/198b3dd2d0b4d83c873b2ce480837edacc0f35ab
>
>
> On Fri, Mar 1, 2024 at 6:15 AM Emanuele Rocca  wrote:
>
>> Source: google-perftools
>> Version: 2.15-1.1
>> Severity: serious
>> Tags: ftbfs
>> User: debian-...@lists.debian.org
>> Usertag: time64
>>
>> Dear Maintainer,
>>
>> google-perftools fails to build from source when building with
>> -D_TIME_BITS=64
>> on armhf and armel with the following error:
>>
>> src/mmap_hook.cc:309:31: error: static assertion failed
>>   309 | static_assert(sizeof(int32_t) == sizeof(off_t), "");
>>   |   ^~~~
>> src/mmap_hook.cc:309:31: note: the comparison reduces to ‘(4 == 8)’
>> make[1]: *** [Makefile:5124: src/libtcmalloc_internal_la-mmap_hook.lo]
>> Error 1
>>
>> The package builds correctly disabling the time64 flags with:
>>
>>   DEB_BUILD_MAINT_OPTIONS=abi=-time64 dpkg-buildpackage
>>
>>

Bug#1065636: kwartz-client: Please review debconf template

[Helge Kreutzmann]

Source: kwartz-client
Version: 2.1-2
Severity: normal

While translating your debconf messages we noticed quite a few issues
within the debconf template, ranging from spelling error over punctuation
problems up to difficult to understand sentences. 

Please ask on debian-l10n-english for a review to fix all issues, as
we are not native speakers.

We found the following issues:

Issue: The wording "is safe" is ambigous, maybe just state (as other tools do 
as well): "If unsure, keep the default list."

#. Type: string
#. Description
#: ../kwartz-client.templates:2001
"Please enter the port number of the proxy service. The default value is "
"usually safe."



Issue 1: Missing final full stop
Issue 2: The previous strings do not use "you" in the 2nd sentence, use 
coherent wording, avoding "you"

#. Type: boolean
#. Description
#: ../kwartz-client.templates:6001
"When the recommended package unattended-upgrades is installed, APT will run "
"in the background to attempt some automatic upgrades. If unsure, you can "
"safely keep the \"false\" option"




Issue 1: What is "run some automatic update"? Do you mean "When APT updates the 
package database"?
Issue 2: Sometimes, "apt" is used, sometimes "APT"?
Issue 3: unpriviledged → unprivileged

#. Type: string
#. Description
#: ../kwartz-client.templates:7001
"When APT will run some automatic update for the package database, a user "
"name is needed to use the proxy service. This user must be unpriviledged. If "
"apt does not need to make automatic upgrades, you can keep the default empty "
"value."



Issue: The previous prompt uses an article, this is inconsistent

#. Type: password
#. Description
#: ../kwartz-client.templates:8001
"Password to access the web:"


Issue: some strong password → a strong password

#. Type: password
#. Description
#: ../kwartz-client.templates:8001
"The unpriviledged user which will be used by APT to access the web needs a "
"password. It must be some strong password. If apt does not need to make "
"automatic upgrades, you can keep the default empty value."

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


signature.asc
Description: PGP signature

Bug#1065635: kwartz-client: [INTL:de] updated German debconf translation

[Helge Kreutzmann]

Package: kwartz-client
Version: 3.0-5
Severity: wishlist
Tags: patch l10n

Please find the updated German debconf translation for kwartz-client
attached.

Please place this file in debian/po/ as de.po for your next upload.

If you update your template, please use 
'msgfmt --statistics '
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# German message catalogue for Configuring the kwartz package on Debian systems
# Copyright (C) 2019 Georges Khaznadar
# This file is distributed under the same license as the kwartz-client package.
# Markus Hiereth , 2019, 2020.
# Helge Kreutzmann , 2024.
msgid ""
msgstr ""
"Project-Id-Version: kwartz-client 3.0-5\n"
"Report-Msgid-Bugs-To: kwartz-cli...@packages.debian.org\n"
"POT-Creation-Date: 2024-02-23 13:07+0100\n"
"PO-Revision-Date: 2024-03-07 18:19+0100\n"
"Last-Translator: Helge Kreutzmann \n"
"Language-Team: debian-l10n-german \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Virtaal 0.7.1\n"

#. Type: string
#. Description
#: ../kwartz-client.templates:1001
msgid "IP address of the proxy service:"
msgstr "IP-Adresse des Proxy-Dienstes:"

#. Type: string
#. Description
#: ../kwartz-client.templates:1001
msgid ""
"Please enter the address of the proxy service. It is ususally the same as "
"the address of the Kwartz server. If unsure, keep the default value."
msgstr ""
"Bitte geben Sie die IP-Adresse des Proxy-Dienstes ein. Diese ist "
"normalerweise identisch zu der Adresse des Kwartz-Servers. Falls Sie sich "
"nicht sicher sind, behalten Sie den Vorgabewert bei."

#. Type: string
#. Description
#: ../kwartz-client.templates:2001
msgid "Port number of the proxy service:"
msgstr "Port-Nummer des Proxy-Dienstes:"

# FIXME The wording "is safe" is ambigous, maybe just state (as other tools do 
as well): "If unsure, keep the default list."
#. Type: string
#. Description
#: ../kwartz-client.templates:2001
msgid ""
"Please enter the port number of the proxy service. The default value is "
"usually safe."
msgstr ""
"Bitte geben Sie die Port-Nummer des Proxy-Dienstes ein. Der Vorgabewert ist "
"normalerweise sicher."

#. Type: string
#. Description
#: ../kwartz-client.templates:3001
msgid "List of IP addresses not concerned by the proxy service:"
msgstr "Liste der IP-Adressen, die vom Proxy-Dienst nicht betroffen sind:"

#. Type: string
#. Description
#: ../kwartz-client.templates:3001
msgid ""
"Please enter the IP addresses and ranges which must be fetched without the "
"help of the proxy. If unsure, keep the default list."
msgstr ""
"Bitte geben Sie die IP-Adressen und -Bereiche an, die ohne Hilfe des Proxy-"
"Dienstes abgerufen werden müssen. Falls Sie sich nicht sicher sind, behalten "
"Sie die Vorgabeliste bei."

#. Type: string
#. Description
#: ../kwartz-client.templates:4001
msgid "Landing page URL for the browser:"
msgstr "URL der Startseite für den Browser:"

#. Type: string
#. Description
#: ../kwartz-client.templates:4001
msgid ""
"Please choose the URL of a landing page for the browser. This web page will "
"appear each time the browser is launched. If unsure, keep the default URL."
msgstr ""
"Bitte wählen Sie die URL der Startseite für den Browser aus. Diese Webseite "
"wird jedes mal beim Start des Browsers erscheinen. Falls Sie sich nicht "
"sicher sind, behalten Sie die Vorgabe-URL bei."

#. Type: string
#. Description
#: ../kwartz-client.templates:5001
msgid "Halt the client computer every night:"
msgstr "Den Client-Computer jede Nacht anhalten:"

#. Type: string
#. Description
#: ../kwartz-client.templates:5001
msgid "- 0: no, the computer will not be halted automatically"
msgstr "- 0: nein, der Computer wird nicht automatisch angehalten"

#. Type: string
#. Description
#: ../kwartz-client.templates:5001
msgid "- 1: yes, the computer will be halted at 19:00"
msgstr "- 1: ja, der Computer wird um 19:00 Uhr angehalten"

#. Type: string
#. Description
#: ../kwartz-client.templates:5001
msgid "- 2: yes, the computer will be halted at 20:00"
msgstr "- 2: ja, der Computer wird um 20:00 Uhr angehalten"

#. Type: string
#. Description
#: ../kwartz-client.templates:5001
msgid "- 3: yes, the computer will be halted at 22:00"
msgstr "- 3: ja, der Computer wird um 22:00 Uhr angehalten"

#. Type: boolean
#. Description
#: ../kwartz-client.templates:6001
msgid "Define whether apt should make automatic upgrades"
msgstr "Definieren Sie, ob Apt automatische Upgrades durchführen soll"

# FIXME Missing final full stop
# FIXME The previous strings do not use "you" in the 2nd sentence
#. Type: boolean
#. Description
#: ../kwartz-client.templates:6001
msgid ""
"When the recommended package unattended-upgrades is installed, APT will run "
"in the background to attempt some automatic upgrades. If unsure, you can "
"safely 

Bug#1065397: RFS: libunistring/1.2-1 -- Unicode string library for C

[Boyuan Yang]

Hi,

在 2024-03-07星期四的 16:02 +0100，Jörg Frings-Fürst写道：
> Hello, 
> 
> Am Donnerstag, dem 07.03.2024 um 09:29 -0500 schrieb Boyuan Yang:
> > Hi,
> > 
> > 在 2024-03-07星期四的 10:11 +0100，Jörg Frings-Fürst写道：
> > > Control: tags -1 -moreinfo
> > 
> [...]
> > For Debian-specific maintenance: please remove #MISSING# placeholders for
> > disappeared private symbols from the debian/*.symbols file,
> > as they are not needed anyway.

I believe the same issue need to be solved for the
debian/libunistring5.symbols.hurd-i386 file.

Thanks,
Boyuan Yang



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

Bug#1065634: wv: /usr/share/doc wv is a dangling symlink

[Sven Joachim]

Package: wv
Version: 1.2.9-6.1
Severity: serious
X-Debbugs-Cc: Sven Joachim , Steve Langasek 

After renaming the libwv-1.2-4 library package to libwv-1.2-4t64, the
/usr/share/doc/wv symlink has become dangling.

,
| $ file /usr/share/doc/wv
| /usr/share/doc/wv: broken symbolic link to libwv-1.2-4
`

It should point to libwv-1.2-4t64 instead, obviously.


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

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

Versions of packages wv depends on:
ii  libc62.37-15.1
ii  libglib2.0-0t64  2.78.4-3
ii  libgsf-1-114 1.14.51-2
ii  libwv-1.2-4t64   1.2.9-6.1

wv recommends no packages.

Versions of packages wv suggests:
ii  elinks   0.16.1.1-4.1+b2
ii  ghostscript [postscript-viewer]  10.02.1~dfsg-3
ii  imagemagick  8:6.9.12.98+dfsg1-5.1+b1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.12.98+dfsg1-5.1+b1
ii  lynx 2.9.0rel.0-2
ii  okular [postscript-viewer]   4:23.08.1-2
ii  texlive  2023.20240207-1

-- no debconf information

Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

[Vincent Lefevre]

On 2024-03-07 17:15:05 +, Simon McVittie wrote:
> I can confirm that version 2.24.33-4 of libgtk2.0-common, libgtk2.0-0t64
> and libgtk2.0-bin are, in fact, installable (I have them installed
> right now). I can't see any dependency relationships between them that
> look suspicious.
> 
> If dpkg is removing libgtk2.0-common, then something must surely be
> asking dpkg to remove it?

But if it were aptitude, I would assume that it would have
a REMOVE line with this package in its logs.

> I notice that you have reported at least three bugs that are "the same
> shape" with three unrelated libraries, which suggests that this might
> be more of an aptitude problem than a GTK problem.

Some aptitude developer told me that installation issues were
in general due to declarations by packages.

> Other logs, in particular /var/log/apt/term.log, might provide more
> information about what actually happened.

I've attached the corresponding part of this file.
Note that libgtk2.0-common is mentioned only at the end
(what I had already given).

> Alternatively, if there is some heuristic about "try to keep packages
> from the same source at the same version" being applied, perhaps waiting
> for libgtk2.0-common_2.24.33-4 to become available from the
> Architecture: all buildd would help?

It was already available. And I installed it just after the error.
aptitude should obviously have proposed it for upgrade. I don't
know whether this is a bug in aptitude or something wrong in the
dependencies.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Log started: 2024-03-07  16:01:43
(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% (Reading database ... 20% (Reading database ... 25% 
(Reading database ... 30% (Reading database ... 35% (Reading database ... 40% 
(Reading database ... 45% (Reading database ... 50% (Reading database ... 55% 
(Reading database ... 60% (Reading database ... 65% (Reading database ... 70% 
(Reading database ... 75% (Reading database ... 80% (Reading database ... 85% 
(Reading database ... 90% (Reading database ... 95% (Reading database ... 100% 
(Reading database ... 655929 files and directories currently installed.)
Preparing to unpack .../libgtk2.0-bin_2.24.33-4_amd64.deb ...
Unpacking libgtk2.0-bin (2.24.33-4) over (2.24.33-3) ...
Preparing to unpack .../libgail-common_2.24.33-4_amd64.deb ...
Unpacking libgail-common:amd64 (2.24.33-4) over (2.24.33-3) ...
dpkg: libgail18:amd64: dependency problems, but removing anyway as you 
requested:
 libgnomecanvas2-0:amd64 depends on libgail18 (>= 1.18.0).

(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% (Reading database ... 20% (Reading database ... 25% 
(Reading database ... 30% (Reading database ... 35% (Reading database ... 40% 
(Reading database ... 45% (Reading database ... 50% (Reading database ... 55% 
(Reading database ... 60% (Reading database ... 65% (Reading database ... 70% 
(Reading database ... 75% (Reading database ... 80% (Reading database ... 85% 
(Reading database ... 90% (Reading database ... 95% (Reading database ... 100% 
(Reading database ... 655928 files and directories currently installed.)
Removing libgail18:amd64 (2.24.33-3) ...
Selecting previously unselected package libgail18t64:amd64.
(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% (Reading database ... 20% (Reading database ... 25% 
(Reading database ... 30% (Reading database ... 35% (Reading database ... 40% 
(Reading database ... 45% (Reading database ... 50% (Reading database ... 55% 
(Reading database ... 60% (Reading database ... 65% (Reading database ... 70% 
(Reading database ... 75% (Reading database ... 80% (Reading database ... 85% 
(Reading database ... 90% (Reading database ... 95% (Reading database ... 100% 
(Reading database ... 655923 files and directories currently installed.)
Preparing to unpack .../libgail18t64_2.24.33-4_amd64.deb ...
Unpacking libgail18t64:amd64 (2.24.33-4) ...
dpkg: libgtk2.0-0:amd64: dependency problems, but removing anyway as you 
requested:
 xournal depends on libgtk2.0-0 (>= 2.14.0).
 pinentry-gtk2 depends on libgtk2.0-0 (>= 2.18.0).
 pavumeter depends on libgtk2.0-0 (>= 2.8.0).
 libgtkmm-2.4-1v5:amd64 depends on libgtk2.0-0 (>= 2.24.0).
 libgnomecanvas2-0:amd64 depends on libgtk2.0-0 (>= 2.8.17).
 libgimp2.0:amd64 depends on libgtk2.0-0 (>= 2.24.10).
 ibus-gtk:amd64 depends on libgtk2.0-0 (>= 2.24.0).
 gromit depends on libgtk2.0-0 (>= 2.24.0).
 gkrellweather depends on libgtk2.0-0 (>= 2.8.0).
 gkrellm-volume depends on libgtk2.0-0 (>= 2.8.0).
 gkrellm depends on libgtk2.0-0 (>= 2.24.0).
 gimp depends on libgtk2.0-0 (>= 2.24.10).

(Reading database ...  (Reading database ... 5% (Reading database ... 10% 
(Reading database ... 15% 

Bug#1065633: openldap: FTBFS on hppa - implicit declaration of function ‘kadm5_s_init_with_password_ctx’

[John David Anglin]

Source: openldap
Version: 2.5.13+dfsg-5+b4
Severity: normal
Tags: ftbfs

Dear Maintainer,

See:
https://buildd.debian.org/status/fetch.php?pkg=openldap=hppa=2.5.13%2Bdfsg-5%2Bb4=1709830559=0

smbk5pwd.c: In function ‘smbk5pwd_modules_init’:
smbk5pwd.c:917:23: error: implicit declaration of function 
‘kadm5_s_init_with_password_ctx’; did you mean ‘kadm5_init_with_password_ctx’? 
[-Werror=implicit-function-declaration]
  917 | ret = kadm5_s_init_with_password_ctx( context,
  |   ^~
  |   kadm5_init_with_password_ctx
smbk5pwd.c:924:25: warning: ‘krb5_get_error_string’ is deprecated 
[-Wdeprecated-declarations]
  924 | err_str = krb5_get_error_string( context );
  | ^~~
In file included from /usr/include/heimdal/krb5.h:967,
 from smbk5pwd.c:45:
/usr/include/heimdal/krb5-protos.h:4188:1: note: declared here
 4188 | krb5_get_error_string (krb5_context /*context*/)
  | ^
smbk5pwd.c:926:33: warning: ‘krb5_get_err_text’ is deprecated 
[-Wdeprecated-declarations]
  926 | err_msg = (char *)krb5_get_err_text( 
context, ret );
  | ^~~
/usr/include/heimdal/krb5-protos.h:4152:1: note: declared here
 4152 | krb5_get_err_text (
  | ^
smbk5pwd.c:931:33: warning: ‘krb5_free_error_string’ is deprecated 
[-Wdeprecated-declarations]
  931 | krb5_free_error_string( context, 
err_str );
  | ^~
/usr/include/heimdal/krb5-protos.h:3721:1: note: declared here
 3721 | krb5_free_error_string (
  | ^~
cc1: some warnings being treated as errors
make[2]: *** [Makefile:54: smbk5pwd.lo] Error 1

Regards,
Dave Anglin

-- System Information:
Debian Release: trixie/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 6.1.80+ (SMP w/4 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

[Simon McVittie]

Control: reassign -1 aptitude,libgtk2.0-0t64
Control: tags -1 + moreinfo

On Thu, 07 Mar 2024 at 16:10:17 +0100, Vincent Lefevre wrote:
> During an upgrade with aptitude:
> 
> dpkg: dependency problems prevent removal of libgtk2.0-common:
>  libgtk2.0-bin depends on libgtk2.0-common.
>  libgtk2.0-0t64:amd64 depends on libgtk2.0-common.
> 
> dpkg: error processing package libgtk2.0-common (--purge):
>  dependency problems - not removing
> Errors were encountered while processing:
>  libgtk2.0-common
> 
> Note that "apt install -f" has nothing to fix; this upgrade just
> triggered a dpkg error (similar to bugs 1065603 and 1065625).
> 
> Moreover, like in these bugs, aptitude did not propose the removal
> of libgtk2.0-common:
> 
> Aptitude 0.8.13: log report
> Thu, Mar  7 2024 16:01:36 +0100
> 
>   IMPORTANT: this log only lists intended actions; actions which fail
>   due to dpkg problems may not be completed.
> 
> Will install 5 packages, and remove 2 packages.
> 2048 B of disk space will be used
> 
> [...]
> [HOLD, DEPENDENCIES] libgtk2.0-common:amd64 2.24.33-3
> [...]
> [INSTALL, DEPENDENCIES] libgail18t64:amd64 2.24.33-4
> [INSTALL, DEPENDENCIES] libgtk2.0-0t64:amd64 2.24.33-4
> [REMOVE, DEPENDENCIES] libgail18:amd64 2.24.33-3
> [REMOVE, DEPENDENCIES] libgtk2.0-0:amd64 2.24.33-3
> [...]
> [UPGRADE] gtk2-engines-pixbuf:amd64 2.24.33-3 -> 2.24.33-4
> [UPGRADE] libgail-common:amd64 2.24.33-3 -> 2.24.33-4
> [UPGRADE] libgtk2.0-bin:amd64 2.24.33-3 -> 2.24.33-4
> 

I can confirm that version 2.24.33-4 of libgtk2.0-common, libgtk2.0-0t64
and libgtk2.0-bin are, in fact, installable (I have them installed
right now). I can't see any dependency relationships between them that
look suspicious.

If dpkg is removing libgtk2.0-common, then something must surely be
asking dpkg to remove it?

I notice that you have reported at least three bugs that are "the same
shape" with three unrelated libraries, which suggests that this might
be more of an aptitude problem than a GTK problem.

>   IMPORTANT: this log only lists intended actions

Other logs, in particular /var/log/apt/term.log, might provide more
information about what actually happened.

Alternatively, if there is some heuristic about "try to keep packages
from the same source at the same version" being applied, perhaps waiting
for libgtk2.0-common_2.24.33-4 to become available from the
Architecture: all buildd would help?

smcv

Bug#1065632: debian-edu-config: no online sources after offline install from BD ISO

[Serhii Horichenko]

Package: src:debian-edu-config
Version: 2.12.44~deb12u1

source.list after the offline installation from BD ISO-image has only
"cdrom" source:

tester@tjener:~$ cat /etc/apt/sources.list
deb cdrom:[Debian GNU/Linux 12.5.0 _Bookworm_ - Official amd64 BD
Binary-1 with firmware 20240210-11:28]/ bookworm contrib main
non-free-firmware

Diskless Workstation has the same issue, when I boot it from this tjener.



Sincerely,
Serhii Horichenko

Bug#1032623: marked as done (vcswatch: should not raise error on repos > 1GiB in size)

[Guillem Jover]

Hi!

On Thu, 2024-03-07 at 14:34:39 +0100, Christoph Berg wrote:
> > It looks like this broke for remotes that do not support filtering
> > (yet?). The attached completely untested patch might make this work
> > again. Affecting at least git.hadrons.org and git.dpkg.org, but there
> > might be others too.
> 
> Thanks for spotting that, the patch seems to work.

Great! :)

> Re-running the scan on the dpkg repo still takes around 3 minutes -
> not sure what the client or the server are doing during that time, it
> doesn't re-fetch the repo.

I've now done a «git gc --aggressive» on the repo on the server,
hoping that might help with that.

> On acl and attr the scan is done in 2 or 3s.

These only contain the debian/ directory, so I'd expect them to be
fast no matter what.

Thanks,
Guillem

Bug#557171: /bin/chvt: accessability issue

[Joshua]

Package: kbd
Version: 2.5.1-1+b1
Followup-For: Bug #557171

request tag accessability security important

I am restriced to one hand and forced to enable stickykeys everywhere

It's too difficult to switch consoles with three finget hotkey and sometimes 
impossible.

as emergency action I set suid root on chvt which setting suid on a binary not 
designed for it is a bad idea

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

Kernel: Linux 6.4.12 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
LSM: AppArmor: enabled

Versions of packages kbd depends on:
ii  libc6  2.36-9+deb12u4

Versions of packages kbd recommends:
ii  console-data   2:1.12-9
ii  console-setup  1.221

kbd suggests no packages.

-- no debconf information

Bug#1065625: libmtp9t64 / libmtp-runtime dependency problem makes dpkg fail with attempt of removal of libmtp-common

[Vincent Lefevre]

On 2024-03-07 16:00:35 +0100, Vincent Lefevre wrote:
> Will install 11 packages, and remove 3 packages.
> 8192 B of disk space will be used
> 
> [...]
> [HOLD, DEPENDENCIES] libmtp-common:amd64 1.1.21-3
> [...]
> [INSTALL, DEPENDENCIES] libgphoto2-6t64:amd64 2.5.31-2.1
> [INSTALL, DEPENDENCIES] libgphoto2-port12t64:amd64 2.5.31-2.1
> [INSTALL, DEPENDENCIES] libmtp9t64:amd64 1.1.21-3.1
> [REMOVE, DEPENDENCIES] libgphoto2-6:amd64 2.5.31-2
> [REMOVE, DEPENDENCIES] libgphoto2-port12:amd64 2.5.31-2
> [REMOVE, DEPENDENCIES] libmtp9:amd64 1.1.21-3
> [...]
> [UPGRADE] gvfs:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-backends:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-common:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-daemons:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-fuse:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] gvfs-libs:amd64 1.53.90-2 -> 1.53.90-3
> [UPGRADE] libgphoto2-l10n:amd64 2.5.31-2 -> 2.5.31-2.1
> [UPGRADE] libmtp-runtime:amd64 1.1.21-3 -> 1.1.21-3.1
> 

Note that libmtp-common:amd64 1.1.21-3.1 was available, but for
some unknown reason, aptitude did not propose its upgrade.

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

Bug#1065624: resolved not working after installation, race with dbus and user creation

[Michael Biebl]

Am 07.03.24 um 16:22 schrieb Michael Biebl:

The chain of events afaics is this:

1/ postinst creates systemd-resolve
2/ systemd-resolved.service is started in postinst
3/ dbus trigger is activated after postinst and the dbus config is reloaded

Because the dbus daemon reload happens after the systemd-resolved user 
has been created, systemd-resolved could not successfully claim the 
org.freedesktop.resolve1 D-Bus name.


What we would need to be able to do is to trigger a dbus daemon-reload 
after the system user has been created and before the service is started.


Both is autogenerated code (via dh_installsysusers and 
dh_installsystemd), and there is no way to inject maintscript code 
manually unfortunately.


One way to maybe address this is to make dh_installsysusers generate 
maintscript code to reload dbus.
This could either be done unconditionally, via a dh_installsysusers 
option, or automatically when it finds a D-Bus config file shipped by 
the package (and referencing that user).


dh_installsysusers is part of debhelper, so would need to be addressed 
there.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065624: resolved not working after installation, race with dbus and user creation

[Michael Biebl]

Am 07.03.24 um 15:12 schrieb Timo Weingärtner:

Package: systemd-resolved
Version: 252.22-1~deb12u1
Severity: important
X-Debbugs-Cc: timo.weingaert...@quantumsimulations.de

After installing systemd-resolved name resolution does not work anymore:
8<8<
# apt-get --no-install-recommends install systemd-resolved
[…]
# host debian.org
Host debian.org not found: 2(SERVFAIL)
# resolvectl
Failed to get global data: Connection timed out
# systemctl restart systemd-resolved.service
# host debian.org
debian.org has address […]
[…]
8<8<

The relevant error message from dbus-daemon appears before postinst creates
the user and starts the service.

Maybe creating the user in preinst already, before it is referenced in
dbus config, would be better.

This is the log, including my workaround:


The chain of events afaics is this:

1/ postinst creates systemd-resolve
2/ systemd-resolved.service is started in postinst
3/ dbus trigger is activated after postinst and the dbus config is reloaded

Because the dbus daemon reload happens after the systemd-resolved user 
has been created, systemd-resolved could not successfully claim the 
org.freedesktop.resolve1 D-Bus name.


What we would need to be able to do is to trigger a dbus daemon-reload 
after the system user has been created and before the service is started.


Both is autogenerated code (via dh_installsysusers and 
dh_installsystemd), and there is no way to inject maintscript code 
manually unfortunately.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065631: [INTL:es] Spanish translation of kwartz-client debconf template

[Camaleón]

Package: kwartz-client
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.

Kindly place this file in debian/po/ as es.po for your next upload.

Cheers,
-- 
Camaleón# kwartz-client po-debconf translation to Spanish.
# Copyright (C) 2021
# This file is distributed under the same license as the kwartz-client package.
# Camaleón , 2021.
#
msgid ""
msgstr ""
"Project-Id-Version: kwartz-client\n"
"Report-Msgid-Bugs-To: kwartz-cli...@packages.debian.org\n"
"POT-Creation-Date: 2024-02-23 13:07+0100\n"
"PO-Revision-Date: 2024-03-07 16:11+0100\n"
"Last-Translator: Camaleón \n"
"Language-Team: Debian Spanish \n"
"Language: es\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"

#. Type: string
#. Description
#: ../kwartz-client.templates:1001
msgid "IP address of the proxy service:"
msgstr "Dirección IP del proxy:"

#. Type: string
#. Description
#: ../kwartz-client.templates:1001
msgid ""
"Please enter the address of the proxy service. It is ususally the "
"same as the address of the Kwartz server. If unsure, keep the default "
"value."
msgstr ""
"Introduzca la dirección IP del proxy. Suele ser la misma dirección "
"del servidor Kwartz. Si tiene alguna duda, mantenga el valor "
"predeterminado."

#. Type: string
#. Description
#: ../kwartz-client.templates:2001
msgid "Port number of the proxy service:"
msgstr "Número del puerto del proxy:"

#. Type: string
#. Description
#: ../kwartz-client.templates:2001
msgid ""
"Please enter the port number of the proxy service. The default value "
"is usually safe."
msgstr ""
"Introduzca el número del puerto del proxy. El valor predeterminado "
"suele ser seguro."

#. Type: string
#. Description
#: ../kwartz-client.templates:3001
msgid "List of IP addresses not concerned by the proxy service:"
msgstr "Lista de direcciones IP no afectadas por el proxy:"

#. Type: string
#. Description
#: ../kwartz-client.templates:3001
msgid ""
"Please enter the IP addresses and ranges which must be fetched "
"without the help of the proxy. If unsure, keep the default list."
msgstr ""
"Introduzca las direcciones IP y los rangos de red a las que no "
"afectará el proxy. Si tiene alguna duda, mantenga la lista "
"predeterminada."

#. Type: string
#. Description
#: ../kwartz-client.templates:4001
msgid "Landing page URL for the browser:"
msgstr "Dirección URL de la página de inicio del navegador:"

#. Type: string
#. Description
#: ../kwartz-client.templates:4001
msgid ""
"Please choose the URL of a landing page for the browser. This web "
"page will appear each time the browser is launched. If unsure, keep "
"the default URL."
msgstr ""
"Indique la URL de la página de inicio del navegador. Esta página se "
"cargará cada vez que se inicie el navegador. Si tiene alguna duda, "
"mantenga la URL predeterminada."

#. Type: string
#. Description
#: ../kwartz-client.templates:5001
msgid "Halt the client computer every night:"
msgstr "Detener el equipo cliente cada noche:"

#. Type: string
#. Description
#: ../kwartz-client.templates:5001
msgid "- 0: no, the computer will not be halted automatically"
msgstr "- 0: no, el equipo no se detendrá automáticamente"

#. Type: string
#. Description
#: ../kwartz-client.templates:5001
msgid "- 1: yes, the computer will be halted at 19:00"
msgstr "- 1: sí, el equipo se detendrá a las 19:00"

#. Type: string
#. Description
#: ../kwartz-client.templates:5001
msgid "- 2: yes, the computer will be halted at 20:00"
msgstr "- 2: sí, el equipo se detendrá a las 20:00"

#. Type: string
#. Description
#: ../kwartz-client.templates:5001
msgid "- 3: yes, the computer will be halted at 22:00"
msgstr "- 3: sí, el equipo se detendrá a las 22:00"

#. Type: boolean
#. Description
#: ../kwartz-client.templates:6001
msgid "Define whether apt should make automatic upgrades"
msgstr "Indique si APT debe realizar actualizaciones automáticas"

#. Type: boolean
#. Description
#: ../kwartz-client.templates:6001
msgid ""
"When the recommended package unattended-upgrades is installed, APT "
"will run in the background to attempt some automatic upgrades. If "
"unsure, you can safely keep the \"false\" option"
msgstr ""
"Si el paquete recomendado unattended-upgrades está instalado, APT se "
"ejecutará en segundo plano para realizar actualizaciones automáticas. "
"Si tiene alguna duda, puede mantener la opción «false»"

#. Type: string
#. Description
#: ../kwartz-client.templates:7001
msgid "An unpriviledged user to access the web:"
msgstr "Usuario sin privilegios para acceder a la web:"

#. Type: string
#. Description
#: ../kwartz-client.templates:7001
msgid ""
"When APT will run some automatic update for the package database, a "
"user name is needed to use the proxy service. This user must be "
"unpriviledged. If apt does not need to make automatic upgrades, you "
"can keep the default empty value."
msgstr ""
"Cuando 

Bug#1063380: ITP: libuio -- Linux Kernel UserspaceIO helper library

[Peter Pentchev]

On Thu, Mar 07, 2024 at 03:25:01PM +0100, Manuel Traut wrote:
> Hi Dima,
> 
> > On 7 Feb 2024, at 18:27, Dima Kogan  wrote:
> > 
> > Hi. Thanks for your contribution. I looked at the upstream code a tiny
> > bit, and it looks like it might have portability bug, at least on
> > big-endian architectures. For instance:
> > 
> >  
> > https://github.com/missinglinkelectronics/libuio/blob/6ef3d8d096a641686bfdd112035aa04aa16fe81a/irq.c#L78
> > 
> > This assumes that sizeof(long)==4. Maybe this is benign, but it would be
> > nice to fix. Are you upstream or do you know upstream? Can yall fix
> > these?
> 
> The kernel expects a 4 byte write here, since unsigned long is defined as at 
> least 32 bit this shall work on all architectures.
> 
> If your concern is about endianess this is not in the current scope of libuio 
> and needs to be addressed by a higher layer.
> 
> I am very familiar with library and in close contact with upstream.

In the case of uio_disable_irq() the bug is nicely hidden by the fact
that tmp is guaranteed to be all-zeroes. However, consider the previous
function in the file, uio_enable_irq(). If sizeof(unsigned long) == 8,
then the "tmp" variable's value of 1 will be encoded in memory as
8 bytes containing the values 0, 0, 0, 0, 0, 0, 0, and 1 respectively.
When uio_enable_irq() calls write(..., , 4), it will only send
the first four bytes to the kernel - and they are 0, 0, 0, and... 0.
So it turns out that uio_disable_irq() and uio_enable_irq() do
exactly the same - send a 32-bit zero value to the kernel.

Is this the expected behavior indeed?

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#1065628: [INTL:es] Spanish translation of icingaweb2-module-incubator debconf template

[Camaleón]

Package: icingaweb2-module-incubator
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.

Kindly place this file in debian/po/ as es.po for your next upload.

Cheers,
-- 
Camaleón# Translation of icingaweb2-module-incubater debconf templates to Spanish.
# Copyright (C) 2023 Camaleón 
# This file is distributed under the same license as the 
icingaweb2-module-incubater package.
# Camaleón , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: icingaweb2-module-incubater\n"
"Report-Msgid-Bugs-To: icingaweb2-module-incubator@packages.debian."
"org\n"
"POT-Creation-Date: 2023-06-14 16:33+0200\n"
"PO-Revision-Date: 2024-03-07 15:56+0100\n"
"Last-Translator: Camaleón \n"
"Language-Team: Debian Spanish \n"
"Language: es\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: title
#. Description
#: ../icingaweb2-module-incubator.templates:1001
msgid "icingaweb2-module-incubator: Setup"
msgstr "icingaweb2-module-incubator: Configuración"

#. Type: boolean
#. Description
#: ../icingaweb2-module-incubator.templates:2001
msgid "Should this module be enabled?"
msgstr "¿Quiere activar este módulo?"

#. Type: boolean
#. Description
#: ../icingaweb2-module-incubator.templates:2001
msgid "This module is possible to be enabled or disabled."
msgstr "Puede activar o desactivar este módulo."

Bug#1065630: [INTL:es] Spanish translation of icingaweb2-module-reporting debconf template

[Camaleón]

Package: icingaweb2-module-reporting
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.

Kindly place this file in debian/po/ as es.po for your next upload.

Cheers,
-- 
Camaleón# Translation of icingaweb2-module-reporing debconf templates to Spanish.
# Copyright (C) 2023 Camaleón 
# This file is distributed under the same license as the 
icingaweb2-module-reporing package.
# Camaleón , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: icingaweb2-module-reporing\n"
"Report-Msgid-Bugs-To: icingaweb2-module-reporting@packages.debian."
"org\n"
"POT-Creation-Date: 2023-06-14 16:42+0200\n"
"PO-Revision-Date: 2024-03-07 16:00+0100\n"
"Last-Translator: Camaleón \n"
"Language-Team: Debian Spanish \n"
"Language: es\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: title
#. Description
#: ../icingaweb2-module-reporting.templates:1001
msgid "icingaweb2-module-reporting: Setup"
msgstr "icingaweb2-module-reporting: Configuración"

#. Type: boolean
#. Description
#: ../icingaweb2-module-reporting.templates:2001
msgid "Should this module be enabled?"
msgstr "¿Quiere activar este módulo?"

#. Type: boolean
#. Description
#: ../icingaweb2-module-reporting.templates:2001
msgid "This module is possible to be enabled or disabled."
msgstr "Puede activar o desactivar este módulo."

Bug#1065629: [INTL:es] Spanish translation of icingaweb2-module-nagvis debconf template

[Camaleón]

Package: icingaweb2-module-nagvis
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.

Kindly place this file in debian/po/ as es.po for your next upload.

Cheers,
-- 
Camaleón# Translation of icingaweb2-module-nagvis debconf templates to Spanish.
# Copyright (C) 2023 Camaleón 
# This file is distributed under the same license as the 
icingaweb2-module-nagvis package.
# Camaleón , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: icingaweb2-module-nagvis\n"
"Report-Msgid-Bugs-To: icingaweb2-module-nag...@packages.debian.org\n"
"POT-Creation-Date: 2023-06-14 16:35+0200\n"
"PO-Revision-Date: 2024-03-07 15:58+0100\n"
"Last-Translator: Camaleón \n"
"Language-Team: Debian Spanish \n"
"Language: es\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: title
#. Description
#: ../icingaweb2-module-nagvis.templates:1001
msgid "icingaweb2-module-nagivs: Setup"
msgstr "icingaweb2-module-nagvis: Configuración"

#. Type: boolean
#. Description
#: ../icingaweb2-module-nagvis.templates:2001
msgid "Should this module be enabled?"
msgstr "¿Quiere activar este módulo?"

#. Type: boolean
#. Description
#: ../icingaweb2-module-nagvis.templates:2001
msgid "This module is possible to be enabled or disabled."
msgstr "Puede activar o desactivar este módulo."

Bug#1065627: [INTL:es] Spanish translation of nncp debconf template

[Camaleón]

Package: nncp
Severity: wishlist
Tags: patch l10n

Hello,

You can find enclosed the Spanish translation template to be uploaded with the 
latest package build.

Kindly place this file in debian/po/ as es.po for your next upload.

Cheers,
-- 
Camaleón# Translation of nncp debconf templates to Spanish
# Copyright (C) Camaleon , 2023
# This file is distributed under the same license as the nncp package.
# Camaleon , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: nncp\n"
"Report-Msgid-Bugs-To: n...@packages.debian.org\n"
"POT-Creation-Date: 2023-11-08 05:56-0600\n"
"PO-Revision-Date: 2024-03-07 15:52+0100\n"
"Last-Translator: Camaleón \n"
"Language-Team: Debian Spanish \n"
"Language: es\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: boolean
#. Description
#: ../nncp.templates:1001
msgid "Upgrade NNCP?"
msgstr "¿Quiere actualizar NNCP?"

#. Type: boolean
#. Description
#: ../nncp.templates:1001
msgid ""
"Your currently-installed NNCP is from a version older than 8.10.0."
msgstr ""
"La versión de NNCP que se encuentra instalada actualmente es anterior "
"a la 8.10.0."

#. Type: boolean
#. Description
#: ../nncp.templates:1001
msgid ""
"Those versions embedded a Yggdrasil 0.4 node.  If you aren't using "
"the Yggdrasil node (it is uncommon), you can ignore this message and "
"proceed with the upgrade."
msgstr ""
"Esas versiones integraban un nodo Yggdrasil 0.4. Si no está "
"utilizando el nodo de Yggdrasil (es poco común), puede ignorar este "
"mensaje y continuar con la instalación."

#. Type: boolean
#. Description
#: ../nncp.templates:1001
msgid ""
"If you are using the embedded Yggdrasil node, NNCP 8.10.0 upgraded it "
"to Yggdrasil 0.5. Yggdrasil 0.5 changed the on-the-wire network "
"protocol, and it cannot communicate with Yggdrasil versions older "
"than 0.5.  If you continue, your NNCP installation will be unable to "
"communicate with older Yggdrasil nodes."
msgstr ""
"Si está utilizando el nodo integrado de Yggdrasil, NNCP 8.10.0 lo ha "
"actualizado a la versión de Yggdrasil 0.5. A partir de la versión "
"0.5, Yggdrasil ha cambiado el protocolo de red cableada y no puede "
"comunicarse con versiones de Yggdrasil anteriores a la 0.5. Si decide "
"continuar, su instalación de NNCP no podrá comunicarse con nodos más "
"antiguos de Yggdrasil."

Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

[Vincent Lefevre]

Package: libgtk2.0-0t64
Version: 2.24.33-4
Severity: serious

During an upgrade with aptitude:

dpkg: dependency problems prevent removal of libgtk2.0-common:
 libgtk2.0-bin depends on libgtk2.0-common.
 libgtk2.0-0t64:amd64 depends on libgtk2.0-common.

dpkg: error processing package libgtk2.0-common (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libgtk2.0-common

Note that "apt install -f" has nothing to fix; this upgrade just
triggered a dpkg error (similar to bugs 1065603 and 1065625).

Moreover, like in these bugs, aptitude did not propose the removal
of libgtk2.0-common:

Aptitude 0.8.13: log report
Thu, Mar  7 2024 16:01:36 +0100

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 5 packages, and remove 2 packages.
2048 B of disk space will be used

[...]
[HOLD, DEPENDENCIES] libgtk2.0-common:amd64 2.24.33-3
[...]
[INSTALL, DEPENDENCIES] libgail18t64:amd64 2.24.33-4
[INSTALL, DEPENDENCIES] libgtk2.0-0t64:amd64 2.24.33-4
[REMOVE, DEPENDENCIES] libgail18:amd64 2.24.33-3
[REMOVE, DEPENDENCIES] libgtk2.0-0:amd64 2.24.33-3
[...]
[UPGRADE] gtk2-engines-pixbuf:amd64 2.24.33-3 -> 2.24.33-4
[UPGRADE] libgail-common:amd64 2.24.33-3 -> 2.24.33-4
[UPGRADE] libgtk2.0-bin:amd64 2.24.33-3 -> 2.24.33-4


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

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 libgtk2.0-0t64 depends on:
ii  adwaita-icon-theme   46~rc-1
ii  gnome-icon-theme 3.12.0-5
ii  hicolor-icon-theme   0.17-2
ii  libatk1.0-0t64   2.51.90-2
ii  libc62.37-15.1
ii  libcairo21.18.0-1+b1
ii  libcups2t64  2.4.7-1.2+b1
ii  libfontconfig1   2.15.0-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b1
ii  libglib2.0-0t64  2.78.4-3
pn  libgtk2.0-common 
ii  libpango-1.0-0   1.51.0+ds-4
ii  libpangocairo-1.0-0  1.51.0+ds-4
ii  libpangoft2-1.0-01.51.0+ds-4
ii  libx11-6 2:1.8.7-1
ii  libxcomposite1   1:0.4.5-1
ii  libxcursor1  1:1.2.1-1
ii  libxdamage1  1:1.1.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxi6   2:1.8.1-1
ii  libxinerama1 2:1.1.4-3
ii  libxrandr2   2:1.5.2-2+b1
ii  libxrender1  1:0.9.10-1.1
ii  shared-mime-info 2.4-1

Versions of packages libgtk2.0-0t64 recommends:
ii  libgail-common   2.24.33-4
ii  libgtk2.0-bin2.24.33-4
ii  librsvg2-common  2.54.7+dfsg-2

Versions of packages libgtk2.0-0t64 suggests:
ii  gvfs  1.53.90-3

-- no debconf information

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

Bug#1063380: ITP: libuio -- Linux Kernel UserspaceIO helper library

[Peter Pentchev]

On Thu, Mar 07, 2024 at 05:02:29PM +0200, Peter Pentchev wrote:
> On Thu, Mar 07, 2024 at 03:25:01PM +0100, Manuel Traut wrote:
> > Hi Dima,
> > 
> > > On 7 Feb 2024, at 18:27, Dima Kogan  wrote:
> > > 
> > > Hi. Thanks for your contribution. I looked at the upstream code a tiny
> > > bit, and it looks like it might have portability bug, at least on
> > > big-endian architectures. For instance:
> > > 
> > >  
> > > https://github.com/missinglinkelectronics/libuio/blob/6ef3d8d096a641686bfdd112035aa04aa16fe81a/irq.c#L78
> > > 
> > > This assumes that sizeof(long)==4. Maybe this is benign, but it would be
> > > nice to fix. Are you upstream or do you know upstream? Can yall fix
> > > these?
> > 
> > The kernel expects a 4 byte write here, since unsigned long is defined as 
> > at least 32 bit this shall work on all architectures.
> > 
> > If your concern is about endianess this is not in the current scope of 
> > libuio and needs to be addressed by a higher layer.
> > 
> > I am very familiar with library and in close contact with upstream.
> 
> In the case of uio_disable_irq() the bug is nicely hidden by the fact
> that tmp is guaranteed to be all-zeroes. However, consider the previous
> function in the file, uio_enable_irq(). If sizeof(unsigned long) == 8,
> then the "tmp" variable's value of 1 will be encoded in memory as
> 8 bytes containing the values 0, 0, 0, 0, 0, 0, 0, and 1 respectively.
> When uio_enable_irq() calls write(..., , 4), it will only send
> the first four bytes to the kernel - and they are 0, 0, 0, and... 0.
> So it turns out that uio_disable_irq() and uio_enable_irq() do
> exactly the same - send a 32-bit zero value to the kernel.

...of course, this will only happen on a big-endian system, as
Dima Kogan was concerned about. On a little-endian system, this
will work by chance.

> Is this the expected behavior indeed?

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#1065397: RFS: libunistring/1.2-1 -- Unicode string library for C

[Jörg Frings-Fürst]

Hello, 

Am Donnerstag, dem 07.03.2024 um 09:29 -0500 schrieb Boyuan Yang:
> Hi,
> 
> 在 2024-03-07星期四的 10:11 +0100，Jörg Frings-Fürst写道：
> > Control: tags -1 -moreinfo
> 
[...]
> For Debian-specific maintenance: please remove #MISSING# placeholders for
> disappeared private symbols from the debian/*.symbols file,
> as they are not needed anyway.
> 
Done. Uploaded to mentors and into git.

> For upstream development (optional): it might be better if private symbols'
> visibility could be made into hidden so that unnecessary symbols are not
> exposed.
> 
[...]


> 
> Thanks,
> Boyuan

CU
Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56


Jörg Frings-Fürst
D-54470 Lieser


git:  https://git.jff.email/cgit/

Skype:jff-skype@jff.email
Jami: joergfringsfuerst
Telegram: @joergfringsfuerst
Matrix:   @joergff:matrix.snct-gmbh.de

My wish list: 
 - Please send me a picture from the nature at your home.






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

Bug#1065625: libmtp9t64 / libmtp-runtime dependency problem makes dpkg fail with attempt of removal of libmtp-common

[Vincent Lefevre]

Package: libmtp9t64
Version: 1.1.21-3.1
Severity: serious

During an upgrade with aptitude:

dpkg: dependency problems prevent removal of libmtp-common:
 libmtp9t64:amd64 depends on libmtp-common.
 libmtp-runtime depends on libmtp-common.

dpkg: error processing package libmtp-common (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libmtp-common

Note that "apt install -f" has nothing to fix; this upgrade just
triggered a dpkg error (similar to bug 1065603).

Moreover, like in bug 1065603, aptitude did not propose the removal
of libmtp-common:

Aptitude 0.8.13: log report
Thu, Mar  7 2024 15:49:03 +0100

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 11 packages, and remove 3 packages.
8192 B of disk space will be used

[...]
[HOLD, DEPENDENCIES] libmtp-common:amd64 1.1.21-3
[...]
[INSTALL, DEPENDENCIES] libgphoto2-6t64:amd64 2.5.31-2.1
[INSTALL, DEPENDENCIES] libgphoto2-port12t64:amd64 2.5.31-2.1
[INSTALL, DEPENDENCIES] libmtp9t64:amd64 1.1.21-3.1
[REMOVE, DEPENDENCIES] libgphoto2-6:amd64 2.5.31-2
[REMOVE, DEPENDENCIES] libgphoto2-port12:amd64 2.5.31-2
[REMOVE, DEPENDENCIES] libmtp9:amd64 1.1.21-3
[...]
[UPGRADE] gvfs:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-backends:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-common:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-daemons:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-fuse:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] gvfs-libs:amd64 1.53.90-2 -> 1.53.90-3
[UPGRADE] libgphoto2-l10n:amd64 2.5.31-2 -> 2.5.31-2.1
[UPGRADE] libmtp-runtime:amd64 1.1.21-3 -> 1.1.21-3.1


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

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 libmtp9t64 depends on:
ii  libc6  2.37-15.1
ii  libgcrypt201.10.3-2
pn  libmtp-common  
ii  libusb-1.0-0   2:1.0.27-1

Versions of packages libmtp9t64 recommends:
ii  libmtp-runtime  1.1.21-3.1
ii  udev255.3-2

libmtp9t64 suggests no packages.

-- no debconf information

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

Bug#1031236: Bug pending since more than one year

[rolf.zimmerli]

Dear Maintainer,


this important bug in /etc/network/if-up.d/resolved is pendent since more than 
one year.

In Ubuntu this was already fixed in November 2023:

https://launchpad.net/ubuntu/+source/ifupdown/0.8.36+nmu1ubuntu3.1



When will this be fixed in Debian 12 ?



My customers are thinking about a change from Debian to Ubuntu ☹



Kind regards

Rolf Zimmerli




Freundliche Grüsse

Rolf Zimmerli
Systemspezialist UNIX

PostFinance AG
CD & Infrastructure Services, PF85-62 DT Linux
Engehaldenstrasse 37
CH-3030 Bern

Telefon: +41 79 500 87 53
rolf.zimme...@postfinance.ch
www.postfinance.ch


Sicherheitshinweis:
Dieses E-Mail von PostFinance ist signiert. Weitere Informationen finden Sie 
unter: 
https://www.postfinance.ch/e-signature.
Geben Sie Ihre Sicherheitselemente niemals Dritten bekannt.

smime.p7s
Description: S/MIME Cryptographic Signature

Bug#1065587: rust-polling: Please try to rebuild rust-polling for loong64

[Peter Green]

I have built the rust-polling successfully in my local loong64 
environment, without modifications required.


Make sure you are not using DEB_BUILD_OPTIONS=nocheck

since rust crates don't have stable ABIs and cargo doesn't support
pre-built rust crates, librust* packages contain source code rather
than binaries of any sort.

The package build process does a test build to check that the code
is actually buildable before packaging but this is skipped if
DEB_BUILD_OPTIONS=nocheck is set.



Please try to rebuild rust-polling for loong64 in the Debian Package 
Auto-Building environment.


It failed again.

I've taken a quick look at the code, but I'm not seeing anything
obvious. The definitions in linux-raw-sys seem to exist, at least
accoding to the error messages. I notice that the reexports of those
definitions are gaurded behind a target_pointer_bits guard, it may
be worth checking if rustc is setting that correctly on your
architecture (though if it isn't, I'd expect that to cause a lot
of problems)

Bug#1065467: marisa: FTBFS on loongarch64 as the test case fails

[Boyuan Yang]

Hi,

在 2024-03-05星期二的 12:10 +0800，zhangdandan写道：
> Source: marisa
> Version: 0.2.6-15
> Severity: wishlist
> Tags: ftbfs
> User: debian-loonga...@lists.debian.org
> Usertags: loong64
> 
> Dear maintainers,
> 
> Compiling the marisa failed for loong64 in the Debian Package 
> Auto-Building environment.
> The error messages is as follows,
> ```
> 
>     marisa 0.2.6: tests/test-suite.log
> 
> 
> # TOTAL: 5
> # PASS:  4
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: base-test
> ===
> ```
> 
> The full build log can be found at 
> https://buildd.debian.org/status/logs.php?pkg=marisa=0.2.6-15=loong64.
> 
> After analyzing the test case failures, I have fixed wordsize detection 
> for loongarch64 architecture.
> Please consider the patch (my local patch) I have attached.
> If you have any questions, you can contact me at any time.


I can take this patch, but the patch should be forwarded upstream first.
Please forward it to GitHub upstream project so that I can use the forwarded
link as a reference. After that, I can make the patched upload in Debian.

Thanks,
Boyuan Yang


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

Bug#1065397: RFS: libunistring/1.2-1 -- Unicode string library for C

[Boyuan Yang]

Hi,

在 2024-03-07星期四的 10:11 +0100，Jörg Frings-Fürst写道：
> Control: tags -1 -moreinfo
> 
> 
> Hello Boyuan,
> 
> 
> thanks for your review.
> 
> 
> Am Mittwoch, dem 06.03.2024 um 23:22 -0500 schrieb Boyuan Yang:
> > Control: tags -1 +moreinfo
> > X-Debbugs-CC: debian@jff.email
> > 
> > Hi,
> > 
> [...]
> > 
> > Having #MISSING# in .symbols file is a red flag. It is a strong indication
> > that
> > the library is breaking API explicitly.
> > 
> > Please check again and work with upstream to persue bumping SONAME together
> > with API/ABI breakage. This is especially important given large number
> > of reverse dependencies.
> > 
> 
> Here are the answer from upstream:
> 
> [quote]
> > This is a strong indication that the library explicitly breaks the API.
> 
> These symbols have the prefix 'libunistring_', which effectively makes
> them private symbols. They are *not* part of the API or ABI, as you can see
> by searching the header files for these symbols.

For Debian-specific maintenance: please remove #MISSING# placeholders for
disappeared private symbols from the debian/*.symbols file,
as they are not needed anyway.

For upstream development (optional): it might be better if private symbols'
visibility could be made into hidden so that unnecessary symbols are not 
exposed.


> > Please can you check whether the SONAME needs to be changed.
> 
> The library's major version number does *not* need to be bumped.
> I considered this question when making this commit:
> https://git.savannah.gnu.org/gitweb/?p=libunistring.git;a=commitdiff;h=2a6b2a826c408eaeca3038156d1f512a64b560bd
> 
> Bruno
> [/quote]

Thanks,
Boyuan


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

Bug#1063380: ITP: libuio -- Linux Kernel UserspaceIO helper library

[Manuel Traut]

Hi Dima,

> On 7 Feb 2024, at 18:27, Dima Kogan  wrote:
> 
> Hi. Thanks for your contribution. I looked at the upstream code a tiny
> bit, and it looks like it might have portability bug, at least on
> big-endian architectures. For instance:
> 
>  
> https://github.com/missinglinkelectronics/libuio/blob/6ef3d8d096a641686bfdd112035aa04aa16fe81a/irq.c#L78
> 
> This assumes that sizeof(long)==4. Maybe this is benign, but it would be
> nice to fix. Are you upstream or do you know upstream? Can yall fix
> these?

The kernel expects a 4 byte write here, since unsigned long is defined as at 
least 32 bit this shall work on all architectures.

If your concern is about endianess this is not in the current scope of libuio 
and needs to be addressed by a higher layer.

I am very familiar with library and in close contact with upstream.

Best regards 
Manuel

Bug#731140: ghostscript: on PDF files with embedded fonts, ps2pdf changes the way fonts are rendered

[Vincent Lefevre]

On 2024-02-28 23:04:41 -0600, Steven Robbins wrote:
> On Mon, 2 Dec 2013 13:54:19 +0100 Vincent Lefevre  wrote:
> > font1.pdf is the original file (generated by pdflatex).
> > font2.pdf is the file obtained with "ps2pdf font1.pdf font2.pdf".
> > font.png shows the text of font1.pdf (left) and font2.pdf (right),
> > as obtained with xpdf.
> 
> I have repeated the test with ghostscript 10.02.1 and I cannot see any 
> difference (using xpdf, or using evince) between font1 and the output of 
> ps2pdf.

Well, with the font*.pdf files I had attached in my bug report, I can
no longer see any difference between font1.pdf and font2.pdf with xpdf
(or zathura). So I assume that this was actually a bug in xpdf (or
poppler), which did something wrong concerning font2.pdf.

I've also compared the rendering of these attached files on a Debian 11
machine with xpdf, and I cannot see any difference either.

So I suppose that this bug can be closed.

Regards,

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

Bug#1065624: resolved not working after installation, race with dbus and user creation

[Timo Weingärtner]

Package: systemd-resolved
Version: 252.22-1~deb12u1
Severity: important
X-Debbugs-Cc: timo.weingaert...@quantumsimulations.de

After installing systemd-resolved name resolution does not work anymore:
8<8<
# apt-get --no-install-recommends install systemd-resolved
[…]
# host debian.org
Host debian.org not found: 2(SERVFAIL)
# resolvectl
Failed to get global data: Connection timed out
# systemctl restart systemd-resolved.service 
# host debian.org
debian.org has address […]
[…]
8<8<

The relevant error message from dbus-daemon appears before postinst creates
the user and starts the service.

Maybe creating the user in preinst already, before it is referenced in
dbus config, would be better.

This is the log, including my workaround:
8<8<
Mar 07 14:10:50 HOST python3(mitogen:[…])[45763]: ansible-apt Invoked with 
pkg=['systemd-resolved'] install_recommends=False package=['systemd-resolved'] 
state=present […]
Mar 07 14:10:51 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:51 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:51 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:51 HOST dbus-daemon[15599]: Unknown username "systemd-resolve" in 
message bus configuration file
Mar 07 14:10:51 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:51 HOST systemd[1]: Reloading.
Mar 07 14:10:52 HOST systemd[1]: Starting systemd-resolved.service - Network 
Name Resolution...
Mar 07 14:10:52 HOST systemd-resolved[46459]: Positive Trust Anchors:
Mar 07 14:10:52 HOST systemd-resolved[46459]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Mar 07 14:10:52 HOST systemd-resolved[46459]: Negative trust anchors: home.arpa 
10.in-addr.arpa […]
Mar 07 14:10:52 HOST systemd-resolved[46459]: Using system hostname 'HOST'.
Mar 07 14:10:52 HOST systemd[1]: Started systemd-resolved.service - Network 
Name Resolution.
Mar 07 14:10:52 HOST systemd[1]: Reached target nss-lookup.target - Host and 
Network Name Lookups.
Mar 07 14:10:52 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:53 HOST python3(mitogen:[…])[45763]: ansible-systemd_service 
Invoked with unit=dbus.service state=reloaded name=dbus.service 
daemon_reload=False daemon_reexec=False scope=system no_block=False 
enabled=None force=None masked=None
Mar 07 14:10:53 HOST systemd[1]: Reloading dbus.service - D-Bus System Message 
Bus...
Mar 07 14:10:53 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:53 HOST dbus-send[46517]: method return time=1709817053.651177 
sender=org.freedesktop.DBus -> destination=:1.143 serial=3 reply_serial=2
Mar 07 14:10:53 HOST systemd[1]: Reloaded dbus.service - D-Bus System Message 
Bus.
Mar 07 14:10:53 HOST python3(mitogen:[…])[45763]: ansible-systemd_service 
Invoked with unit=systemd-resolved.service state=restarted 
name=systemd-resolved.service daemon_reload=False daemon_reexec=False 
scope=system no_block=False enabled=None force=None masked=None
Mar 07 14:10:53 HOST systemd[1]: Stopping systemd-resolved.service - Network 
Name Resolution...
Mar 07 14:10:53 HOST systemd[1]: systemd-resolved.service: Deactivated 
successfully.
Mar 07 14:10:53 HOST systemd[1]: Stopped systemd-resolved.service - Network 
Name Resolution.
Mar 07 14:10:53 HOST systemd[1]: Starting systemd-resolved.service - Network 
Name Resolution...
Mar 07 14:10:53 HOST systemd-resolved[46522]: Positive Trust Anchors:
Mar 07 14:10:53 HOST systemd-resolved[46522]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Mar 07 14:10:53 HOST systemd-resolved[46522]: Negative trust anchors: home.arpa 
10.in-addr.arpa […]
Mar 07 14:10:53 HOST systemd-resolved[46522]: Using system hostname 'HOST'.
Mar 07 14:10:53 HOST systemd[1]: Started systemd-resolved.service - Network 
Name Resolution.
Mar 07 14:10:53 HOST systemd-resolved[46522]: wlp[…]: Bus client set default 
route setting: yes
Mar 07 14:10:53 HOST systemd-resolved[46522]: wlp[…]: Bus client set DNS server 
list to: […]
Mar 07 14:10:53 HOST systemd-resolved[46522]: enx[…]: Bus client set search 
domain list to: […]
Mar 07 14:10:53 HOST systemd-resolved[46522]: enx[…]: Bus client set default 
route setting: yes
Mar 07 14:10:53 HOST systemd-resolved[46522]: enx[…]: Bus client set DNS server 
list to: […]
8<8<


-- 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-18-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd-resolved depends on:
ii  dbus [default-dbus-system-bus]  1.14.10-1~deb12u1
ii  libc6   2.36-9+deb12u4
ii  libssl3  

Bug#1065319: notfound 1065319 in 0.5.2-1

[Jakob Haufe]

notfound 1065319 0.5.2-1
thanks

I just re-checked and could not reproduce this in bookworm.

Cheers,
sur5r

-- 
ceterum censeo microsoftem esse delendam.


pgpvkzKeZXUdO.pgp
Description: OpenPGP digital signature

Bug#1065623: RM: libomxil-bellagio -- ROM; Dead upstream

[Ying-Chun Liu (PaulLiu)]

Package: ftp.debian.org
Control: affects -1 + src:libomxil-bellagio
X-Debbugs-Cc: libomxil-bella...@packages.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: paul...@debian.org
Severity: normal

Hi,

OpenMAX standard is inactive for many years by The Khronos Group.
And gst-omx is removed by the upstream (gstreamer1.0).

Let's remove all OpenMAX related packages in Debian.

Yours,
Paul



OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065622: RM: libomxxvideo -- ROM; Dead upstream

[Ying-Chun Liu (PaulLiu)]

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

Hi,

OpenMAX standard is inactive for many years by The Khronos Group.
And gst-omx is removed by the upstream (gstreamer1.0).

Let's remove all OpenMAX related packages in Debian.

Yours,
Paul



OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065621: RM: libomxvorbis -- ROM; Dead upstream

[Ying-Chun Liu (PaulLiu)]

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

Hi,

OpenMAX standard is inactive for many years by The Khronos Group.
And gst-omx is removed by the upstream (gstreamer1.0).

Let's remove all OpenMAX related packages in Debian.

Yours,
Paul



OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065620: RM: libomxvideosrc -- ROM; Dead upstream

[Ying-Chun Liu (PaulLiu)]

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

Hi,

OpenMAX standard is inactive for many years by The Khronos Group.
And gst-omx is removed by the upstream (gstreamer1.0).

Let's remove all OpenMAX related packages in Debian.

Yours,
Paul



OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065619: RM: libomxmad -- ROM; Dead upstream

[Ying-Chun Liu (PaulLiu)]

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

Hi,

OpenMAX standard is inactive for many years by The Khronos Group.
And gst-omx is removed by the upstream (gstreamer1.0).

Let's remove all OpenMAX related packages in Debian.

Yours,
Paul



OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065597: racket: Inclusion of mzdyn.o in the binary package

[David Bremner]

Rafael Laboissière  writes:

>
> However, it does not work because the file mzdyn.o is needed and 
> cannot be found anywhere. Indeed, this file is mentioned in the Racket 
> documentation.[*]
>

My knowledge here is incomplete, and I'd be happy to be corrected, but:

I think that documentation relates to the old "bc" backend of racket.
For most architectures we are using the new "cs" backend (and will
possibly migrate the remaining architectures).  So it may not be
possible to do the same kind of linking as was done with the old
backend.

Bug#1065618: RM: libomxfbdevsink -- ROM; Dead upstream

[Ying-Chun Liu (PaulLiu)]

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

Hi,

OpenMAX standard is inactive for many years by The Khronos Group.
And gst-omx is removed by the upstream (gstreamer1.0).

Let's remove all OpenMAX related packages in Debian.

Yours,
Paul



OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065617: RM: libomxcamera -- ROM; Dead upstream

[Ying-Chun Liu (PaulLiu)]

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

Hi,

OpenMAX standard is inactive for many years by The Khronos Group.
And gst-omx is removed by the upstream (gstreamer1.0).

Let's remove all OpenMAX related packages in Debian.

Yours,
Paul



OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065616: RM: libomxalsa -- ROM; Dead upstream

[Ying-Chun Liu (PaulLiu)]

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

Hi,

OpenMAX standard is inactive for many years by The Khronos Group.
And gst-omx is removed by the upstream (gstreamer1.0).

Let's remove all OpenMAX related packages in Debian.

Yours,
Paul



OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065615: New version 1.7.6 available

[Marcus Frings]

Package: dovecot-fts-xapian
Version: 1.6.0-1
Severity: wishlist

Dear maintainer,

Please package the latest version 1.7.6 for Debian because it seems to
fix the bug reported at: https://github.com/grosjo/fts-xapian/issues/147

Best regards
Marcus

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

Kernel: Linux 6.6.15-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=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dovecot-fts-xapian depends on:
ii  dovecot-core [dovecot-abi-2.3.abiv21]  1:2.3.21+dfsg1-2
ii  libc6  2.37-15.1
ii  libgcc-s1  14-20240303-1
ii  libicu72   72.1-4+b1
ii  libsqlite3-0   3.45.1-1
ii  libstdc++6 14-20240303-1
ii  libxapian301.4.22-1+b1

dovecot-fts-xapian recommends no packages.

dovecot-fts-xapian suggests no packages.

-- no debconf information

Bug#1065114: cinnamon-control-center: Drop Online Accounts feature or port it away from GOA

[Jeremy Bícha]

Control: tags -1 +ftbfs sid experimental

I prepared a merge request at
https://salsa.debian.org/cinnamon-team/cinnamon-control-center/-/merge_requests/5

Thank you,
Jeremy Bícha

Bug#1065614: RM: gst-omx -- ROM; Dead upstream

[Ying-Chun Liu (PaulLiu)]

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

Hi,

OpenMAX standard is inactive for many years by The Khronos Group.
And gst-omx is removed by the upstream (gstreamer1.0).

Let's remove all OpenMAX related packages in Debian.

Yours,
Paul



OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1032623: marked as done (vcswatch: should not raise error on repos > 1GiB in size)

[Christoph Berg]

> It looks like this broke for remotes that do not support filtering
> (yet?). The attached completely untested patch might make this work
> again. Affecting at least git.hadrons.org and git.dpkg.org, but there
> might be others too.

Thanks for spotting that, the patch seems to work.

Re-running the scan on the dpkg repo still takes around 3 minutes -
not sure what the client or the server are doing during that time, it
doesn't re-fetch the repo.

On acl and attr the scan is done in 2 or 3s.

Christoph

Bug#1065613: gjs: Fails to build on ppc64el

[Jeremy Bícha]

Source: gjs
Version: 1.79.90-1
Severity: serious
Tags: ftbfs sid
Forwarded: https://gitlab.gnome.org/GNOME/gjs/-/issues/605

The new version of gjs is failing to build on ppc64 and ppc64el. I
have reported this issue upstream.

Thank you,
Jeremy Bícha

Bug#1065611: Additional support for SolidRun HoneyComb

[Diederik de Haas]

Hi Josua,

On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote:
> LX2160 SoC early silicon revisions have a pci-e generation 4 controller.
> It requires a different driver from newer gen-3 silicon.
> 
> This affects the SolidRun Honeycomb Workstation which
> is otherwise fully supported in Debian.

I cloned bug report #1061116 into #1065611 to discuss some additional support 
for the SolidRun HoneyComb.

I analyzed the HoneyComb dts file and the following included .dtsi files:
- arch/arm64/boot/dts/freescale/fsl-lx2160a-clearfog-itx.dtsi
- arch/arm64/boot/dts/freescale/fsl-lx2160a-cex7.dtsi
- arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi

If I exclude the kernel modules from 1061116 and 1061117, then I still have 
the following list of additional modules to enable:
- drivers/edac: Enable EDAC_MPC85XX
- drivers/hwmon/pmbus: Enable PMBUS, SENSORS_PMBUS and
  SENSORS_LTC2978 as modules
- drivers/nvmem: Enable NVMEM_LAYERSCAPE_SFP as module
- drivers/rtc: Enable RTC_DRV_FSL_FTM_ALARM as module
- drivers/soc/fsl: Enable FSL_RCPM

If you agree that this is a good list I can make a MR to get them enabled.
A MR for 1061116 and 1061117 has just been merged in our 'master' branch.

But I ran into an issue when looking at the ``EDAC_MPC85XX`` stanza 
in``drivers/edac/Kconfig``:
``depends on FSL_SOC && EDAC=y``

But ``FSL_SOC`` is (only) defined in ``arch/powerpc/Kconfig``, which means 
``EDAC_MPC85XX`` can not be enabled on ``arm64``. 
That module was found based on ``compatible = "fsl,qoriq-memory-controller"``, 
which sounds like something you would want to have.

Upstream commit ea2eb9a8b6207ee4 has the following commit message:
```
EDAC, fsl-ddr: Separate FSL DDR driver from MPC85xx

The mpc85xx-compatible DDR controllers are used on ARM-based SoCs too.
Carve out the DDR part from the mpc85xx EDAC driver in preparation to
support both architectures.
```
Which I interpret as all (?) the preparations for supporting both powerpc and 
ARM were made, but they forgot to update the strict dependency of 
``EDAC_MPC85XX`` to powerpc to actually support both architectures?

Can you shed some light on this?

Cheers,
  Diederik

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

Bug#1032623: marked as done (vcswatch: should not raise error on repos > 1GiB in size)

[Guillem Jover]

Hi!

On Wed, 2024-03-06 at 14:15:03 +, Debian Bug Tracking System wrote:
> 
> vcswatch: Use --filter blob:none
> 
> Required blobs (changelog, control, upstream metadata) are fetched by
> git on demand. Thanks to Gábor Németh for the suggestion!
> 
> Closes: #1032623
> 

It looks like this broke for remotes that do not support filtering
(yet?). The attached completely untested patch might make this work
again. Affecting at least git.hadrons.org and git.dpkg.org, but there
might be others too.

Thanks,
Guillem
From d78a41fad53de64eb50f72692bf057c82d41fc85 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Thu, 7 Mar 2024 13:30:41 +0100
Subject: [PATCH] vcswatch: Ignore warning when the server does not know about
 filtering

The command succeeded, but emitted a warning. Instead of failing the
fetching, ignore the warning.
---
 data/vcswatch/vcswatch | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/data/vcswatch/vcswatch b/data/vcswatch/vcswatch
index be72cc35..611d5372 100755
--- a/data/vcswatch/vcswatch
+++ b/data/vcswatch/vcswatch
@@ -243,6 +243,8 @@ sub process_package ($) {
 	# try a full clone instead
 	runcmd ('git', 'clone', '--quiet', '--bare', '--mirror', '--template', '', $url, $pkgdir);
 	$dbh->do("UPDATE vcs SET dumb_http = true WHERE package = ?", undef, $pkg->{package});
+} elsif ($err =~ /warning: filtering not recognized by server, ignoring/) {
+	# ignore the warning
 } else {
 	error ($err);
 }
-- 
2.43.0

Bug#1065612: O: google-android-m2repository-installer -- Google Android support m2 repository

[Hans-Christoph Steiner]

Package: wnpp
Severity: normal
X-Debbugs-Cc: google-android-m2repository-instal...@packages.debian.org
Control: affects -1 + src:google-android-m2repository-installer

I intend to orphan the google-android-m2repository-installer package.
None of the current maintainers have an interest in it, and it is
non-free.

The package description is:
 This package will download the Google Android Support Library repository and
 create a Debian package. This is structured as a maven m2 repository of all the
 versions of the library.
 .
 The Android Support Library offers a number of features that are not built into
 the framework. These libraries offer backward-compatible versions of new
 features, provide useful UI elements that are not included in the framework,
 and provide a range of utilities that apps can draw on.
 .
 WARNING: Installing this Debian package causes android_m2repository_r35.zip to
 be downloaded from dl.google.com and/or from other suggested mirrors. The End
 User License Agreement of this binary package is available at
 developer.android.com.

Bug#1061116: linux-image-6.1.0-17-arm64: please enable support for lx2160a pcie gen4 controller on early silicon

[Diederik de Haas]

Control: clone -1 -2
Control: retitle -2 Additional support for SolidRun HoneyComb

On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote:
> LX2160 SoC early silicon revisions have a pci-e generation 4 controller.
> It requires a different driver from newer gen-3 silicon.
> 
> This affects the SolidRun Honeycomb Workstation which
> is otherwise fully supported in Debian.

Cloning this bug into a new one to discuss some additional support for the 
SolidRun HoneyComb.

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

Bug#921239:

[c . buhtz]

I support this wish because of the low quality German translation of the 
current man page.


Translating it is waste of ressources.
It is also not clear where the translation comes from Upstream do not 
provide translations.
It is obvious that the German man page was translated by a machine or a 
none native speaker.


Kind

Bug#1065610: libguestfs0t64: All appliance dependencies lost during time_t transition

[James Cowgill]

Package: libguestfs0t64
Version: 1.52.0-2.1
Severity: serious

Hi,

During the time_t transition all the appliance dependencies of
libguestfs0 were lost:

$ debdiff libguestfs0_1%3a1.52.0-2+b1_amd64.deb 
libguestfs0t64_1%3a1.52.0-2.1_amd64.deb
...
Control files: lines which differ (wdiff format)

{+Breaks: libguestfs0 (<< 1:1.52.0-2.1)+}
Depends: libacl1 (>= 2.2.23), libaugeas0 (>= 1.8.0), libc6 (>= 2.35), libcap2 
(>= 1:2.10), libfuse2 (>= 2.8), libhivex0 (>= 1.3.14), libjansson4 (>= 2.14), 
libpcre2-8-0 (>= 10.22), librpm9 (>= 4.14.0+dfsg1), libselinux1 (>= 3.1~), 
libsystemd0, libtirpc3 (>= 1.0.2), libtsk19 (>= 4.12.1+dfsg), libvirt0 (>= 
1.2.7~rc2), libxml2 (>= 2.8.0), libyara10 (>= 4.0.0~), supermin (>= 5), 
qemu-system-x86, qemu-utils, db-util, icoutils, netpbm,
[-osinfo-db, acl, attr, binutils, bsdextrautils, btrfs-progs, bzip2, cpio, 
cryptsetup-bin, dash, diffutils, dosfstools, e2fsprogs, exfatprogs, extlinux, 
f2fs-tools, fdisk | util-linux (<< 2.29.2), file, gawk, gdisk, grub2-common, 
iproute2 | iproute, dhcpcd-base | isc-dhcp-client, kmod | module-init-tools, 
ldmtool, less, lsscsi, lvm2, lzop, mdadm, mount, mtools, ntfs-3g, 
openssh-client, parted, pciutils, procps, psmisc, scrub, sleuthkit, 
squashfs-tools, syslinux, systemd-sysv | sysvinit-core, udev, uuid-runtime, 
xz-utils, zerofree, zstd-]
{+osinfo-db+}
Installed-Size: [-5038-] {+5039+}
Package: [-libguestfs0-] {+libguestfs0t64+}

The build log contains this:

debian/gen-appliance-depends.sh
...
cat: 'debian/libguestfs0/usr/lib/*-*/guestfs/supermin.d/packages': No such file 
or directory

So I think updating debian/gen-appliance-depends.sh with the new library
name should fix this.



I did try this change but it the package test doesn't pass right now. I
think that supermin fails to understand virtual dependencies when
resolving packages and so fails to install various things. Maybe
once the time_t transition has completed and the affected packages are
binNMUed this should resolve itself?

James