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.

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1042042 [src:android-platform-build] android-platform-build: FTBFS: 
Vector.h:259:28: error: cannot convert ‘const android::Vector*’ to 
‘android::VectorImpl*’
Added tag(s) patch.

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

Processed: found 1064967 in 1:20170731~dfsg-1, found 1064967 in 1:20230101~dfsg-1 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1064967 1:20170731~dfsg-1
Bug #1064967 [src:fontforge] fontforge: CVE-2024-25081 CVE-2024-25082
Marked as found in versions fontforge/1:20170731~dfsg-1.
> found 1064967 1:20230101~dfsg-1
Bug #1064967 [src:fontforge] fontforge: CVE-2024-25081 CVE-2024-25082
Marked as found in versions fontforge/1:20230101~dfsg-1.
> fixed 1064967 1:20170731~dfsg-1+deb10u1
Bug #1064967 [src:fontforge] fontforge: CVE-2024-25081 CVE-2024-25082
The source 'fontforge' and version '1:20170731~dfsg-1+deb10u1' do not appear to 
match any binary packages
Marked as fixed in versions fontforge/1:20170731~dfsg-1+deb10u1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1064967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: libcypher-parser: diff for NMU version 0.6.2-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1012975 + patch
Bug #1012975 [src:libcypher-parser] libcypher-parser: ftbfs with GCC-12
Added tag(s) patch.
> tags 1012975 + pending
Bug #1012975 [src:libcypher-parser] libcypher-parser: ftbfs with GCC-12
Added tag(s) pending.

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

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

Processed: fontforge: diff for NMU version 1:20230101~dfsg-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1064967 + patch
Bug #1064967 [src:fontforge] fontforge: CVE-2024-25081 CVE-2024-25082
Added tag(s) patch.
> tags 1064967 + pending
Bug #1064967 [src:fontforge] fontforge: CVE-2024-25081 CVE-2024-25082
Added tag(s) pending.

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

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#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#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
--- 

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

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1065320 [src:linux] linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters 
ACPI Error loop during boot & requires power cycle
Severity set to 'serious' from 'critical'
> tags -1 + upstream fixed-upstream
Bug #1065320 [src:linux] linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters 
ACPI Error loop during boot & requires power cycle
Added tag(s) upstream and fixed-upstream.
> forwarded -1 https://lore.kernel.org/regressions/zd2bsv8vsfjml...@archie.me/ 
> https://bugzilla.kernel.org/show_bug.cgi?id=218531
Bug #1065320 [src:linux] linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters 
ACPI Error loop during boot & requires power cycle
Set Bug forwarded-to-address to 
'https://lore.kernel.org/regressions/zd2bsv8vsfjml...@archie.me/ 
https://bugzilla.kernel.org/show_bug.cgi?id=218531'.
> found -1 6.6.15-1
Bug #1065320 [src:linux] linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters 
ACPI Error loop during boot & requires power cycle
Marked as found in versions linux/6.6.15-1.
> found -1 6.7.4-1~exp1
Bug #1065320 [src:linux] linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters 
ACPI Error loop during boot & requires power cycle
Marked as found in versions linux/6.7.4-1~exp1.

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

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#1064252: marked as done (linux-image-6.1.0-17-amd64: CONFIG_SYSTEM_TRUSTED_KEYS="y" is in the default config "y")

[Debian Bug Tracking System]

Your message dated Thu, 7 Mar 2024 22:02:05 +0100
with message-id 
and subject line Re: Bug#1064252: linux-image-6.1.0-17-amd64: 
CONFIG_SYSTEM_TRUSTED_KEYS="y" is in the default config "y"
has caused the Debian Bug report #1064252,
regarding linux-image-6.1.0-17-amd64: CONFIG_SYSTEM_TRUSTED_KEYS="y" is in the 
default config "y"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.1.69-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: foren...@wi.rr.com

In the default config-6.1.0-17-amd64, there is a line: 
CONFIG_SYSTEM_TRUSTED_KEYS="y"

It is impossible to change it from y in menuconfig. Then, it creates 'error no 
rule to make y.  

-- Package-specific info:
** Version:
Linux version 6.1.0-17-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30)

** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-17-amd64 
root=UUID=b8970480-c02f-4e13-83ea-99242beaa8c1 ro quiet

** Not tainted

** Kernel log:
[850617.148769]  sda: unable to read partition table
[850617.148860] sd 6:0:0:0: [sda] Attached SCSI disk
[850617.204217] sd 6:0:0:0: [sda] Synchronizing SCSI cache
[850617.444223] sd 6:0:0:0: [sda] Synchronize Cache(10) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[850617.716182] usb 2-7.4: new high-speed USB device number 11 using xhci_hcd
[850617.888733] usb 2-7.4: New USB device found, idVendor=152d, idProduct=0562, 
bcdDevice= 2.09
[850617.888746] usb 2-7.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[850617.888748] usb 2-7.4: Product: SSK Storage
[850617.888750] usb 2-7.4: Manufacturer: SSK
[850617.888752] usb 2-7.4: SerialNumber: DD564198838B8
[850617.892008] scsi host6: uas
[850617.892602] scsi 6:0:0:0: Direct-Access SSK   0209 
PQ: 0 ANSI: 6
[850617.894762] sd 6:0:0:0: Attached scsi generic sg1 type 0
[850617.894982] sd 6:0:0:0: [sda] Spinning up disk...
[850618.428107] usb 2-7.4: USB disconnect, device number 11
[850618.924215] .ready
[850618.924291] sd 6:0:0:0: [sda] Read Capacity(16) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[850618.924296] sd 6:0:0:0: [sda] Sense not available.
[850618.924302] sd 6:0:0:0: [sda] Read Capacity(10) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[850618.924304] sd 6:0:0:0: [sda] Sense not available.
[850618.924314] sd 6:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[850618.924316] sd 6:0:0:0: [sda] 0-byte physical blocks
[850618.924321] sd 6:0:0:0: [sda] Write Protect is off
[850618.924324] sd 6:0:0:0: [sda] Mode Sense: 00 00 00 00
[850618.924328] sd 6:0:0:0: [sda] Asking for cache data failed
[850618.924333] sd 6:0:0:0: [sda] Assuming drive cache: write through
[850618.924342] sd 6:0:0:0: [sda] Preferred minimum I/O size 4096 bytes not a 
multiple of physical block size (0 bytes)
[850618.924345] sd 6:0:0:0: [sda] Optimal transfer size 33553920 bytes not a 
multiple of physical block size (0 bytes)
[850618.924995] sd 6:0:0:0: [sda] Attached SCSI disk
[854882.880440] usb 2-7.3: USB disconnect, device number 5
[854884.327593] usb 2-7.3: new low-speed USB device number 12 using xhci_hcd
[854884.457279] usb 2-7.3: New USB device found, idVendor=047d, idProduct=1020, 
bcdDevice= 1.08
[854884.457289] usb 2-7.3: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
[854884.457292] usb 2-7.3: Product: Kensington Expert Mouse
[854884.463747] input: Kensington Expert Mouse as 
/devices/pci:00/:00:14.0/usb2/2-7/2-7.3/2-7.3:1.0/0003:047D:1020.0004/input/input21
[854884.464101] hid-generic 0003:047D:1020.0004: input,hidraw2: USB HID v1.11 
Mouse [Kensington Expert Mouse] on usb-:00:14.0-7.3/input0
[860266.405755] audit: type=1400 audit(1707886801.612:37): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=178977 comm="cupsd" 
capability=12  capname="net_admin"
[880247.840603] wlp4s0: Connection to AP 00:90:7f:4a:10:b1 lost
[880459.847171] wlp4s0: authenticate with 00:90:7f:4a:10:b1
[880459.850240] wlp4s0: send auth to 00:90:7f:4a:10:b1 (try 1/3)
[880459.879928] wlp4s0: authenticated
[880459.881486] wlp4s0: associate with 00:90:7f:4a:10:b1 (try 1/3)
[880459.888498] wlp4s0: RX AssocResp from 00:90:7f:4a:10:b1 (capab=0x511 
status=0 aid=1)
[880459.893044] wlp4s0: associated
[880459.970372] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link 

Bug#1061754: marked as done (python-json-log-formatter ftbfs with Python 3.12 as default)

[Debian Bug Tracking System]

Your message dated Thu, 07 Mar 2024 20:52:51 +
with message-id 
and subject line Bug#1061754: fixed in python-json-log-formatter 0.5.2-3
has caused the Debian Bug report #1061754,
regarding python-json-log-formatter ftbfs with Python 3.12 as default
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: src:python-json-log-formatter
Version: 0.5.2-2
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

With python3-defaults from experimental, the package fails to build:

[...]
= test session starts 
==

platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.4.0
cachedir: .tox/py312/.pytest_cache
rootdir: /<>
collected 29 items

tests.py ...FF

=== FAILURES 
===
_ 
JSONFormatterTest.test_message_and_time_and_extra_are_in_json_record_when_extra_is_provided 
_


self = testMethod=test_message_and_time_and_extra_are_in_json_record_when_extra_is_provided>


def 
test_message_and_time_and_extra_are_in_json_record_when_extra_is_provided(self):

logger.info('Sign up', extra={'fizz': 'bazz'})
json_record = json.loads(log_buffer.getvalue())
expected_fields = set([
'message',
'time',
'fizz',
])
>   self.assertEqual(set(json_record), expected_fields)
E   AssertionError: Items in the first set but not the second:
E   'taskName'

tests.py:72: AssertionError
-- Captured log call 
---

INFO test:tests.py:65 Sign up
_ 
JSONFormatterTest.test_message_and_time_are_in_json_record_when_extra_is_blank 
_


self = testMethod=test_message_and_time_are_in_json_record_when_extra_is_blank>


def test_message_and_time_are_in_json_record_when_extra_is_blank(self):
logger.info('Sign up')
json_record = json.loads(log_buffer.getvalue())
expected_fields = set([
'message',
'time',
])
>   self.assertEqual(set(json_record), expected_fields)
E   AssertionError: Items in the first set but not the second:
E   'taskName'

tests.py:62: AssertionError
-- Captured log call 
---

INFO test:tests.py:56 Sign up
=== warnings summary 
===

tests.py: 28 warnings
  /<>/json_log_formatter/__init__.py:123: 
DeprecationWarning: datetime.datetime.utcnow() is deprecated and 
scheduled for removal in a future version. Use timezone-aware objects to 
represent datetimes in UTC: datetime.datetime.now(datetime.UTC).

extra['time'] = datetime.utcnow()

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=== short test summary info 

FAILED 
tests.py::JSONFormatterTest::test_message_and_time_and_extra_are_in_json_record_when_extra_is_provided
FAILED 
tests.py::JSONFormatterTest::test_message_and_time_are_in_json_record_when_extra_is_blank
== 2 failed, 27 passed, 28 warnings in 0.17s 
===

py312: exit 1 (0.36 seconds) /<>> pytest -s tests.py pid=5939
--- End Message ---
--- Begin Message ---
Source: python-json-log-formatter
Source-Version: 0.5.2-3
Done: Colin Watson 

We believe that the bug you reported is fixed in the latest version of
python-json-log-formatter, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated 
python-json-log-formatter package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Mar 2024 19:47:05 +
Source: python-json-log-formatter
Architecture: source
Version: 0.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Colin Watson 
Closes: 1061754
Changes:
 

Processed: android-platform-tools-base: additional information

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1058331 [src:android-platform-tools-base] android-platform-tools-base: 
FTBFS: SignatureExtension.java:32: error: DEROutputStream is not public in 
org.bouncycastle.asn1; cannot be accessed from outside package
Added tag(s) patch.

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

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#999908: marked as done (python3-celery-haystack-ng: missing Breaks+Replaces: python3-django-celery-haystack (<< 0.20))

[Debian Bug Tracking System]

Your message dated Thu, 07 Mar 2024 20:40:38 +
with message-id 
and subject line Bug#08: fixed in celery-haystack-ng 0.20.post2-2
has caused the Debian Bug report #08,
regarding python3-celery-haystack-ng: missing Breaks+Replaces: 
python3-django-celery-haystack (<< 0.20)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
08: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=08
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-celery-haystack-ng
Version: 0.20.post2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package python3-celery-haystack-ng.
  Preparing to unpack .../16-python3-celery-haystack-ng_0.20.post2-1_all.deb ...
  Unpacking python3-celery-haystack-ng (0.20.post2-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-09EOH1/16-python3-celery-haystack-ng_0.20.post2-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/python3/dist-packages/celery_haystack/__init__.py', which is also in 
package python3-django-celery-haystack 0.10-4
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-09EOH1/16-python3-celery-haystack-ng_0.20.post2-1_all.deb


I assume python3-celery-haystack-ng is intended as successor to
python3-django-celery-haystack which was last released with buster
and is RC buggy in sid.

cheers,

Andreas


python3-django-celery-haystack=0.10-4_python3-celery-haystack-ng=0.20.post2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: celery-haystack-ng
Source-Version: 0.20.post2-2
Done: Colin Watson 

We believe that the bug you reported is fixed in the latest version of
celery-haystack-ng, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated celery-haystack-ng 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Mar 2024 20:01:48 +
Source: celery-haystack-ng
Architecture: source
Version: 0.20.post2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Colin Watson 
Closes: 08
Changes:
 celery-haystack-ng (0.20.post2-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure URI in debian/watch.
   * Set debhelper-compat version in Build-Depends.
   * Update standards version to 4.6.2, no changes needed.
 .
   [ Colin Watson ]
   * Breaks/Replaces: python3-django-celery-haystack (closes: #08).
   * Fix typos in package description.
   * Remove d2to1, which no longer works with modern setuptools.
Checksums-Sha1:
 8d6923062bf7209d95873990f42a42ae50716d61 2346 
celery-haystack-ng_0.20.post2-2.dsc
 fee343b68ccd4ddd70467d96aec7d0dd68daea3b 3684 
celery-haystack-ng_0.20.post2-2.debian.tar.xz
Checksums-Sha256:
 bbee0f3218587336613a782c1485f04e41da41e4b6cc0a642ab3e267f964 2346 
celery-haystack-ng_0.20.post2-2.dsc
 3b8eba97a5d0363793b0d6263b2af0ce4e564fd036b64645a6bb29f19fae1bd6 3684 
celery-haystack-ng_0.20.post2-2.debian.tar.xz
Files:
 adb6ffbae5ed2994d61040f6e751cf07 2346 python optional 
celery-haystack-ng_0.20.post2-2.dsc
 2e21eaa300d2d067a22a1c3fac1b4592 3684 python optional 
celery-haystack-ng_0.20.post2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmXqHYkACgkQOTWH2X2G
UAsDCQ/8C0zyfAi9FX16Cau42sEAPpDdNpzpxcp1cId0We4xyL2gf3fFDSvUtFwW
ZHXUpfMH0Ax2oK0sffYKFZCGQp1zRBUmRgL6vBdDDFp/tQ9PMrlJyZtVU7PFXJpJ
u/yy1GdVv0YkhlT1Nz2T3VEL4JP/Y1yFwBwcyd18/Snke9lmNzTw5XyqKzQuaR2I
KBXQcvBJno5OUWORrxWsqV8G5K8VzkSm2NAqnK1rK0/hfnXfXZesJZFE8uJHmq7v
nHFMC8DSPokoIP5Ukpe2FpfiLsrukWz7oer8VGVPGu9kCxx+h+FkCAuHj/aKY51J
ySNB9RTkfwHPy6w0Yyi2T9X9ZVNtSeJXAzzpP8eRbQpXFazhRFpxXraycvR55v+R

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#1064420: marked as done (src:ruby-omniauth-alicloud: fails to migrate to testing for too long: uploader built arch:all binary)

[Debian Bug Tracking System]

Your message dated Thu, 07 Mar 2024 19:08:46 +
with message-id 
and subject line Bug#1064420: fixed in ruby-omniauth-alicloud 3.0.0-2.1
has caused the Debian Bug report #1064420,
regarding src:ruby-omniauth-alicloud: fails to migrate to testing for too long: 
uploader built arch:all binary
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Source: ruby-omniauth-alicloud
Version: 2.0.1-2
Severity: serious
Control: close -1 3.0.0-2
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ruby-omniauth-alicloud has been trying to 
migrate for 32 days [2]. Hence, I am filing this bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=ruby-omniauth-alicloud



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-omniauth-alicloud
Source-Version: 3.0.0-2.1
Done: Paul Gevers 

We believe that the bug you reported is fixed in the latest version of
ruby-omniauth-alicloud, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated ruby-omniauth-alicloud 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Feb 2024 22:06:40 +0100
Source: ruby-omniauth-alicloud
Architecture: source
Version: 3.0.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Paul Gevers 
Closes: 1064420
Changes:
 ruby-omniauth-alicloud (3.0.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1064420)
Checksums-Sha1:
 c2164e61f1e4d5f518ca17814ac466f0e83e156f 1823 
ruby-omniauth-alicloud_3.0.0-2.1.dsc
 441a1a0d7e1e713663ae52fd13181bc88f0470f3 3008 
ruby-omniauth-alicloud_3.0.0-2.1.debian.tar.xz
Checksums-Sha256:
 9b1e6455eead6119dd25bb083c47f28cd447b9b15b24ac1a7936dd6eddf239bd 1823 
ruby-omniauth-alicloud_3.0.0-2.1.dsc
 b0c9a65bfe7cc4779e2068ae2a62b1774b41c6dd067698272bb3fbe7184c295e 3008 
ruby-omniauth-alicloud_3.0.0-2.1.debian.tar.xz
Files:
 6083f22ca0ff0e08bb2841e8266bd1b5 1823 ruby optional 
ruby-omniauth-alicloud_3.0.0-2.1.dsc
 515e2deb46439ab6e708ab4eeabdc36e 3008 ruby optional 
ruby-omniauth-alicloud_3.0.0-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmXaMDIACgkQnFyZ6wW9
dQrgkAf9FBk5fBmkAgYFqFPSaBb3I1xVHW8cJmx/DaxR1dYjPHAYylpU2hFVW0VF
O/EfJejzp7D4mbPc4ax10OzjgON1Bigq2OSObRs0oGuHf85Fav8DAJh0+a0Bd+nr

Processed: closing 1051967

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # php-psr-log-test was removed via #1052296
> close 1051967
Bug #1051967 [php-fig-log-test] php-fig-log-test: ships 
/usr/share/php/Psr/Log/Test/*.php, already in php-psr-log-test
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1051967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1065501 [src:qgis] qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb
Added tag(s) upstream.
> forwarded -1 https://github.com/qgis/QGIS/issues/56756
Bug #1065501 [src:qgis] qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb
Set Bug forwarded-to-address to 'https://github.com/qgis/QGIS/issues/56756'.

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

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

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1065634 [wv] wv: /usr/share/doc wv is a dangling symlink
Added tag(s) patch.

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

Bug#1064422: marked as done (src:ohai: fails to migrate to testing for too long: uploader built arch:all binary)

[Debian Bug Tracking System]

Your message dated Thu, 07 Mar 2024 18:52:52 +
with message-id 
and subject line Bug#1064422: fixed in ohai 18.1.3-2.1
has caused the Debian Bug report #1064422,
regarding src:ohai: fails to migrate to testing for too long: uploader built 
arch:all binary
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Source: ohai
Version: 17.9.0-2
Severity: serious
Control: close -1 18.1.3-2
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ohai has been trying to migrate for 32 
days [2]. Hence, I am filing this bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=ohai



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ohai
Source-Version: 18.1.3-2.1
Done: Paul Gevers 

We believe that the bug you reported is fixed in the latest version of
ohai, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated ohai package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Feb 2024 22:10:05 +0100
Source: ohai
Architecture: source
Version: 18.1.3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Paul Gevers 
Closes: 1064422
Changes:
 ohai (18.1.3-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1064422)
Checksums-Sha1:
 29ece30a03a95f70a0830575c101f7dc7ba7345f 1833 ohai_18.1.3-2.1.dsc
 29a96feac4d93d5e51d2201b0212721a9fed07f9 6868 ohai_18.1.3-2.1.debian.tar.xz
Checksums-Sha256:
 2b94453b3f85a5a0ad78b6caf121117567751a13e78736369567259ead60b71b 1833 
ohai_18.1.3-2.1.dsc
 fd5ec8b51b167b4ba577e4a48c2000f9833517da7c85e52d2060aabd1cd93f51 6868 
ohai_18.1.3-2.1.debian.tar.xz
Files:
 b2f71e4237493df3e6e37c3f368d4d24 1833 admin optional ohai_18.1.3-2.1.dsc
 25cd4e731a4df9a44d2c369bd9fde313 6868 admin optional 
ohai_18.1.3-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmXaLyYACgkQnFyZ6wW9
dQrodwf/eBVmiC/EYNc/v/XiSd3bDk5bnQUxs+W2LPfMKqTiSo5aZrrCQvpIG9Xq
4NMROsvCkXerSD2SutsOy55zRaWWp+5y9v5YLrPIlrlgWqFyl3a9U9+uL4+xeJNa
apNcjsp2p+4knnr+o6NHdIuf+ReC1A+UNKEpieDvGnzPKzq3pxD1tOkoyEA1ELa3
K9C1b9MomZaNnnXLoy7goyDzxwTEXFO1YKCsbjUTZ+tiurfAVj8mRJ9gUHUohLBz
sw53R9TQQoGz2l85bqh4TQkbZY0ZaFonoyWeTjuU5J+nh0ewuVF7kagYxKlIBrQV
CHhkJi2CDjYhPks4QBn4hpRM5N+XgQ==
=8h3e
-END PGP SIGNATURE-



pgprafXmZHYSj.pgp

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
>>
>>

Processed: Re: Bug#1065548: marked as pending in octave-statistics

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1065548 [src:octave-statistics] octave-statistics: binary-any FTBFS
Bug 1065548 is not marked as done; doing nothing.

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

Processed: Re: Bug#1065548: marked as pending in octave-statistics

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1065548 {Done: Rafael Laboissière } 
[src:octave-statistics] octave-statistics: binary-any FTBFS
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions octave-statistics/1.6.4-2.

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

Bug#1065548: marked as pending in octave-statistics

[Sébastien Villemot]

Control: reopen -1

Le mercredi 06 mars 2024 à 17:25 +, Rafael Laboissière a écrit :
> Control: tag -1 pending
> 
> Hello,
> 
> Bug #1065548 in octave-statistics reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
> 
> https://salsa.debian.org/pkg-octave-team/octave-statistics/-/commit/5d7e5e9addd6ad613ee6dae349a8551a2a369888
> 
> 
> d/rules: Do not FTBFS if empty doc/ directory does not exist
> 
> Closes: #1065548
> 

The build still fails for arch:any.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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#1053169: marked as done (Please remove librbd-dev build-depends on all 32 bits arch)

[Debian Bug Tracking System]

Your message dated Thu, 07 Mar 2024 17:30:37 +
with message-id 
and subject line Bug#1053169: fixed in tcmu 1.5.4-6
has caused the Debian Bug report #1053169,
regarding Please remove librbd-dev build-depends on all 32 bits arch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1053169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tcmu
Version: 1.5.4-4.1
Severity: important

Hi,

I'd like to remove 32 bits support from Ceph, because upstream makes some
64 bits assumptions a bit everywhere, because it's not tested in upstream
CI, and because it is increasingly difficult to build Ceph on a smaller
addressing footprint (we used to have many tricks to reduce the build footprint
that isn't sustainable in the long run).

So please remove librbd-dev in build-depends of your package for all 32
bits arch, and remove Ceph support in all 32 bits binaries. I'll upload
Ceph with Build-Depends: architecture-is-64-bit as soon as this is done
for the 4 affected packages:
- fio
- libvirt
- tcmu
- qemu

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Source: tcmu
Source-Version: 1.5.4-6
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
tcmu, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1053...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated tcmu package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Mar 2024 17:46:11 +0100
Source: tcmu
Architecture: source
Version: 1.5.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1046607 1053169
Changes:
 tcmu (1.5.4-6) unstable; urgency=medium
 .
   * QA upload.
   * Restrict librbd-dev build-dependency to 64-bit architectures.
 (Closes: #1053169)
   * Clean more generated files.  (Closes: #1046607)
Checksums-Sha1:
 5f910bbdef89d98ab9cfaaaccd71a2cfabefdc90 2055 tcmu_1.5.4-6.dsc
 672887b22bc094c50fc4a219606a73f2d564e17b 7032 tcmu_1.5.4-6.debian.tar.xz
 3ba9361d32dec4b5f6b1d4e68a47ec890a85d37a 8367 tcmu_1.5.4-6_source.buildinfo
Checksums-Sha256:
 a2a9ad0801ccc4d36c3ee445326e3b84076c642bc401f42f301b401ae2e030dc 2055 
tcmu_1.5.4-6.dsc
 68f00ab5994c0296254a180e7166bbbfa7906264eae6a89c3ad57de7141040ff 7032 
tcmu_1.5.4-6.debian.tar.xz
 ad80c370754ee4eb8f97f8e91608b8847caa7e4754121a8d80ab9252dd76095c 8367 
tcmu_1.5.4-6_source.buildinfo
Files:
 58c49cd8c4ece1329443b50c8b8bcbb1 2055 admin optional tcmu_1.5.4-6.dsc
 c013bfe5e853d2ed1aefedcea785e814 7032 admin optional tcmu_1.5.4-6.debian.tar.xz
 4db50bc72d4a8f77180687b4617248b6 8367 admin optional 
tcmu_1.5.4-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmXp8BEQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCG+ND/0WbWflFoAtL0wzPo2gm2Hjt6TKp1CzF/yQ
RuwXEaz05nlC1Ris9G5ZJY3S7nVUuUxH9/tByR/U6eYlhxtQV/GPRV4aMqeWVgrK
Xyi7h1fguYB6T+MOjXoFtuZFH/R6tewnB9ceC6aXC2Wnc1Ki6VwVfPDHPrV6AjTR
mPc6CvPhdlmUCBSlaEFxUDtuITnHVdt7XmGLe+hfRjbuNTjSxhLH/aotp2z8L9lJ
II+eZNdhKLchrUxF6p1aeklfYDe+6XHUZYUc8YUhTrm3J9YotQx60LAUU/yb3yGc
b8SgnN/I2V6kCpEn0Syn/5Q63YV3qRwYQFqrcoSoEiuate4+6uyu2/Zh8uCUBbec
48GaLwNktqWLDcpFYK/OZkYMvNnKNEWOsN5LHfqz54E502CMtHHm1yBfxDQ2393E
2jC+NILOUgw/SCFPvcu2yqpQDJ+3eJJAv77tmLrVBgspLgzK0qNLqGv1Vgd7kbZW
ijew8F0rP/vYtasqHJaKtUOwDSM0WaMlDjeTh7e1DXlgNznJhjkwTARjU7Xuy0mW
otHo18+Fy1eOMwvTspkjOaiMQ2uyISHsByxf4JHrv9cm6W3CYNWghvpzuaA4onzA
nRDSxhJDsB6ZxMlrwCCj8LKXpwLQdZ3ogVgYE+fH86+XT+gAEEmb/XQaO3b6iKcT
XrfuQ+R1AA==
=OLoE
-END PGP SIGNATURE-



pgpGLOv8um71d.pgp
Description: PGP signature
--- End Message ---

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

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 aptitude,libgtk2.0-0t64
Bug #1065626 [libgtk2.0-0t64] libgtk2.0-0t64 / libgtk2.0-bin dependency problem 
makes dpkg fail with attempt of removal of libgtk2.0-common
Bug reassigned from package 'libgtk2.0-0t64' to 'aptitude,libgtk2.0-0t64'.
No longer marked as found in versions gtk+2.0/2.24.33-4.
Ignoring request to alter fixed versions of bug #1065626 to the same values 
previously set
> tags -1 + moreinfo
Bug #1065626 [aptitude,libgtk2.0-0t64] libgtk2.0-0t64 / libgtk2.0-bin 
dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common
Added tag(s) moreinfo.

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

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

Processed: tagging 1064722

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1064722 + confirmed
Bug #1064722 [src:erlang-p1-xml] erlang-p1-xml: FTBFS: dh_auto_test: error: 
make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile test 
returned exit code 2
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1064722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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#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#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#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

Processed: found 1065585 in 6.6.3-1~exp1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1065585 6.6.3-1~exp1
Bug #1065585 [src:linux] linux-headers-6.7.7-amd64: Depends: 
linux-compiler-gcc-13-x86 -> linux-image-6.7.7-amd64, gcc-13 => uninstallable 
on x32
Marked as found in versions linux/6.6.3-1~exp1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1065585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fix 1065610 tags

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1065610 1:1.52.0-2.1
Bug #1065610 [libguestfs0t64] libguestfs0t64: All appliance dependencies lost 
during time_t transition
Marked as found in versions libguestfs/1:1.52.0-2.1.
> notfound 1065610 1.52.0-2.1
Bug #1065610 [libguestfs0t64] libguestfs0t64: All appliance dependencies lost 
during time_t transition
There is no source info for the package 'libguestfs0t64' at version 
'1.52.0-2.1' with architecture ''
Unable to make a source version for version '1.52.0-2.1'
No longer marked as found in versions 1.52.0-2.1.
> user debian-...@lists.debian.org
Setting user to debian-...@lists.debian.org (was jcowg...@debian.org).
> usertags 1065610 time-t
There were no usertags set.
Usertags are now: time-t.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1065610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

Processed: Re: libdebuginfod1t64 dependency problem breaks the upgrade

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libdebuginfod1t64 dependency problem makes dpkg fail with attempt 
> of removal of libdebuginfod-common
Bug #1065603 [libdebuginfod1t64] libdebuginfod1t64 dependency problem breaks 
the upgrade
Changed Bug title to 'libdebuginfod1t64 dependency problem makes dpkg fail with 
attempt of removal of libdebuginfod-common' from 'libdebuginfod1t64 dependency 
problem breaks the upgrade'.

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

Bug#1065603: libdebuginfod1t64 dependency problem breaks the upgrade

[Vincent Lefevre]

Control: retitle -1 libdebuginfod1t64 dependency problem makes dpkg fail with 
attempt of removal of libdebuginfod-common

On 2024-03-07 11:28:21 +0100, Vincent Lefevre wrote:
> When I wanted to upgrade, this ended up with
> 
> dpkg: dependency problems prevent removal of libdebuginfod-common:
>  libdebuginfod1t64:amd64 depends on libdebuginfod-common (>= 0.190-1.1).
> 
> dpkg: error processing package libdebuginfod-common (--purge):
>  dependency problems - not removing
> (Reading database ... 655945 files and directories currently installed.)
> Errors were encountered while processing:
>  libdebuginfod-common

Well, the issue just seems to be a dpkg failure. "apt install -f"
shows nothing to fix.

So I'm wondering why dpkg wanted to remove libdebuginfod-common.

FYI, I did the upgrade via aptitude, and this package wasn't proposed
for removal. In /var/log/aptitude, after discarding the HOLD lines
(which correspond to no changes for these packages):

Aptitude 0.8.13: log report
Thu, Mar  7 2024 11:24:24 +0100

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

Will install 15 packages, and remove 6 packages.
5096 kB of disk space will be freed

[...]
[INSTALL, DEPENDENCIES] libasm1t64:amd64 0.190-1.1
[INSTALL, DEPENDENCIES] libdebuginfod1t64:amd64 0.190-1.1
[INSTALL, DEPENDENCIES] libdw1t64:amd64 0.190-1.1
[INSTALL, DEPENDENCIES] libelf1t64:amd64 0.190-1.1
[INSTALL, DEPENDENCIES] libglib2.0-0t64:amd64 2.78.4-3
[REMOVE, DEPENDENCIES] libasm1:amd64 0.190-1+b1
[REMOVE, DEPENDENCIES] libdebuginfod1:amd64 0.190-1+b1
[REMOVE, DEPENDENCIES] libdw1:amd64 0.190-1+b1
[REMOVE, DEPENDENCIES] libelf1:amd64 0.190-1+b1
[REMOVE, DEPENDENCIES] libglib2.0-0:amd64 2.78.4-1
[REMOVE, DEPENDENCIES] libglib2.0-0-dbgsym:amd64 2.78.4-1
[...]
[UPGRADE] elfutils:amd64 0.190-1+b1 -> 0.190-1.1
[UPGRADE] gir1.2-freedesktop:amd64 1.78.1-15 -> 1.78.1-16
[UPGRADE] gir1.2-freedesktop-dev:amd64 1.78.1-15 -> 1.78.1-16
[UPGRADE] gir1.2-girepository-2.0:amd64 1.78.1-15 -> 1.78.1-16
[UPGRADE] gir1.2-glib-2.0:amd64 1.78.1-15 -> 1.78.1-16
[UPGRADE] gir1.2-glib-2.0-dev:amd64 1.78.1-15 -> 1.78.1-16
[UPGRADE] libelf-dev:amd64 0.190-1+b1 -> 0.190-1.1
[UPGRADE] libglib2.0-bin:amd64 2.78.4-1 -> 2.78.4-3
[UPGRADE] libglib2.0-dev:amd64 2.78.4-1 -> 2.78.4-3
[UPGRADE] libglib2.0-dev-bin:amd64 2.78.4-1 -> 2.78.4-3


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

Bug#1064886: sqlite-utils: Fails with "ModuleNotFoundError"

[Edward Betts]

Hi Sebastian,

The click_default_group module is in the python3-click-default-group package,
sqlite-utils depends on python3-click-default-group.

Do you have python3-click-default-group installed?

The module will be installed
as /usr/lib/python3/dist-packages/click_default_group.py

Do you have this file on your system?

Cheers,
-- 
Edward

Bug#1065603: libdebuginfod1t64 dependency problem breaks the upgrade

[Vincent Lefevre]

Package: libdebuginfod1t64
Version: 0.190-1.1
Severity: serious

When I wanted to upgrade, this ended up with

dpkg: dependency problems prevent removal of libdebuginfod-common:
 libdebuginfod1t64:amd64 depends on libdebuginfod-common (>= 0.190-1.1).

dpkg: error processing package libdebuginfod-common (--purge):
 dependency problems - not removing
(Reading database ... 655945 files and directories currently installed.)
Errors were encountered while processing:
 libdebuginfod-common

-- 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 libdebuginfod1t64 depends on:
ii  libc6 2.37-15.1
ii  libcurl3t64-gnutls [libcurl3-gnutls]  8.6.0-3.2
pn  libdebuginfod-common  
ii  libdw1t64 0.190-1.1
ii  libelf1t640.190-1.1

libdebuginfod1t64 recommends no packages.

libdebuginfod1t64 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#1065599: gcc-14-offload-nvptx: openmp offload compile fails due to missing libgomp.spec

[Giacomo Mulas]

Package: gcc-14-offload-nvptx
Version: 14-20240303-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

due to a different organisation in file installation with respect to 
gcc-12-offload-nvptx, compiling code to offload openmp to nvptx fails with the 
following:
x86_64-linux-gnu-accel-nvptx-none-gcc-14: fatal error: cannot read spec file 
'libgomp.spec': No such file or directory
compilation terminated.
nvptx mkoffload: fatal error: x86_64-linux-gnu-accel-nvptx-none-gcc-14 returned 
1 exit status
compilation terminated.
lto-wrapper: fatal error: 
/usr/libexec/gcc/x86_64-linux-gnu/14//accel/nvptx-none/mkoffload returned 1 
exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed

While gcc-12-offload-nvptx installed executables, includes, and libs under 
/usr/lib/gcc/x86_64-linux-gnu/12/accel/nvptx-none, and found them, 
gcc-14-offload-nvptx does not appear to install them anywhere, nor
to depend on any other separate package that does. This effectively renders the 
package unusable. 

Thanks in advance, best regards
Giacomo Mulas


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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

Kernel: Linux 6.7.7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 gcc-14-offload-nvptx depends on:
ii  gcc-14 14-20240303-1
ii  gcc-14-base14-20240303-1
ii  libc6  2.37-15.1
ii  libc6-dev  2.37-15.1
ii  libgmp10   2:6.3.0+dfsg-2+b1
ii  libgomp-plugin-nvptx1  14-20240303-1
ii  libmpc31.3.1-1+b2
ii  libmpfr6   4.2.1-1+b1
ii  libzstd1   1.5.5+dfsg2-2
ii  nvptx-tools0.20230904-1
ii  zlib1g 1:1.3.dfsg-3.1

gcc-14-offload-nvptx recommends no packages.

gcc-14-offload-nvptx suggests no packages.

-- no debconf information

Bug#1065598: gcc-13-offload-nvptx: openmp offload compile fails due to missing libgomp.spec

[Giacomo Mulas]

Package: gcc-13-offload-nvptx
Version: 13.2.0-18
Severity: grave
Justification: renders package unusable

Dear Maintainer,

due to a different organisation in file installation with respect to 
gcc-12-offload-nvptx, compiling code to offload openmp to nvptx fails with the 
following:
x86_64-linux-gnu-accel-nvptx-none-gcc-13: fatal error: cannot read spec file 
'libgomp.spec': No such file or directory
compilation terminated.
nvptx mkoffload: fatal error: x86_64-linux-gnu-accel-nvptx-none-gcc-13 returned 
1 exit status
compilation terminated.
lto-wrapper: fatal error: 
/usr/libexec/gcc/x86_64-linux-gnu/13//accel/nvptx-none/mkoffload returned 1 
exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed

While gcc-12-offload-nvptx installed executables, includes, and libs under 
/usr/lib/gcc/x86_64-linux-gnu/12/accel/nvptx-none, and found them, 
gcc-13-offload-nvptx does not appear to install them anywhere, nor to depend on 
any other separate package that does. This effectively renders the package 
unusable. While the gcc-12 offload still works, gcc-13 is now the default 
compiler on sid, meaning that trying to compile openmp to offload to nvptx with 
the default compiler fails.

Thanks in advance, best regards
Giacomo Mulas


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

Kernel: Linux 6.7.7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 gcc-13-offload-nvptx depends on:
ii  gcc-13 13.2.0-18
ii  gcc-13-base13.2.0-18
ii  libc6  2.37-15.1
ii  libc6-dev  2.37-15.1
ii  libgmp10   2:6.3.0+dfsg-2+b1
ii  libgomp-plugin-nvptx1  14-20240303-1
ii  libmpc31.3.1-1+b2
ii  libmpfr6   4.2.1-1+b1
ii  libzstd1   1.5.5+dfsg2-2
ii  nvptx-tools0.20230904-1
ii  zlib1g 1:1.3.dfsg-3.1

gcc-13-offload-nvptx recommends no packages.

gcc-13-offload-nvptx suggests no packages.

-- no debconf information

Bug#1063484: libuv1: CVE-2024-24806

[Dominique Dumont]

On Wednesday, 6 March 2024 21:07:56 CET Salvatore Bonaccorso wrote:
> Thank you very much. Looks good to me, feel free to upload as well to
> security-master (and build as well with -sa).

Done.

All the best