Bug#1031489: OpenSUSE Leap 15.4 + 340.108 + Qt 6.2.2 = ALL QT WORKING GOOD

[Alexander Procenko]

OpenSUSE Leap 15.4 + 340.108 + Qt 6.2.2 = ALL QT WORKING GOOD
https://i.imgur.com/u5WOQD0.png
So its Debian issue?

Bug#1000209: Bug #1000209

[Couret Charles-Antoine]

Hello,

I'd a look into this bug this evening and it looks like the problem was 
related to


update-rc.d (provided by #DEBHELPER#) which is called after "invoke-rc.d 
timidity stop" which stops the service.



It means systemd was not able to find the relevant service to stop at 
this moment in time. Making this update just before does the trick.


The patch is in attachment.


Regards,

Charles-Antoine Couret
diff --git a/debian/timidity-daemon.postinst b/debian/timidity-daemon.postinst
index a3610f9..573bc09 100644
--- a/debian/timidity-daemon.postinst
+++ b/debian/timidity-daemon.postinst
@@ -55,10 +55,13 @@
 
 # make sure we really stop, because packaging system doesn't
 # understand what we're trying to do with migration to timidity-daemon
-[ -f "/etc/init.d/timidity" ] && if which invoke-rc.d >/dev/null 2>&1; then
-  invoke-rc.d timidity stop
-else
-  /etc/init.d/timidity stop
+if [ -f "/etc/init.d/timidity" ]; then
+  if [ which invoke-rc.d >/dev/null 2>&1 ] ; then
+update-rc.d timidity defaults
+invoke-rc.d timidity stop
+  else
+/etc/init.d/timidity stop
+  fi
 fi
 
 #DEBHELPER#

Bug#1013594: insubstantial: FTBFS: Caused by: : java.lang.VerifyError: Expecting a stackmap frame at branch target 33

[Ben Hutchings]

The laf-widget library that's part of this package generates some Java
bytecode directly:
.
Since Java 11, additional metadata (the "stackmap frame") appears to be
required for Java bytecode, and is not generated by laf-widget.

However, this code generation is apparently only used to "augment" the
rendering of other widget classes and does not seem to be essential for
the function of the library.  In fact, it was completely removed in a
later version of laf-widget:
https://github.com/kirill-grouchnikov/laf-widget/commit/8b0871e84ca6b6c0c479a6033998eb39e0fc767d

I patched the Gradle build files to disable this code generation and
the build succeeded.  I tested triplea with the old and new binaries
built from insubstantial: start the program, install the "Tutorial"
map, and start a local game with that map.  I didn't see any
regressions.  As I expected, the GUI rendering is different but only
slightly; see the attached "old" and "new" screenshots.

scilab is already broken (#1030205) so I couldn't test it.

I will NMU with the attached changes shortly.

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.
diff -Nru insubstantial-7.3+dfsg3/debian/changelog insubstantial-7.3+dfsg3/debian/changelog
--- insubstantial-7.3+dfsg3/debian/changelog	2019-08-26 13:49:59.0 +0200
+++ insubstantial-7.3+dfsg3/debian/changelog	2023-03-03 23:42:05.0 +0100
@@ -1,3 +1,10 @@
+insubstantial (7.3+dfsg3-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Java 11: disable augmentation (fixes FTBFS) (Closes: #1013594)
+
+ -- Ben Hutchings   Fri, 03 Mar 2023 23:42:05 +0100
+
 insubstantial (7.3+dfsg3-5) unstable; urgency=medium
 
   [ Andrius Merkys ]
diff -Nru insubstantial-7.3+dfsg3/debian/patches/java-11-disable-augmentation.patch insubstantial-7.3+dfsg3/debian/patches/java-11-disable-augmentation.patch
--- insubstantial-7.3+dfsg3/debian/patches/java-11-disable-augmentation.patch	1970-01-01 01:00:00.0 +0100
+++ insubstantial-7.3+dfsg3/debian/patches/java-11-disable-augmentation.patch	2023-03-03 23:11:22.0 +0100
@@ -0,0 +1,51 @@
+From: Ben Hutchings 
+Subject: Java 11: disable augmentation
+Date: Fri, 03 Mar 2023 23:11:14 +0100
+Bug-Debian: https://bugs.debian.org/1013594
+
+Since Java 11, Java bytecode is required to include some additional
+metadata.  The bytecode generated by laf-widget for "augmentation" of
+other widget libraries does not follow this requirement, resulting in
+a build failure.
+
+A later version of laf-widget has removed this augmentation rather
+than fixing it:
+https://github.com/kirill-grouchnikov/laf-widget/commit/8b0871e84ca6b6c0c479a6033998eb39e0fc767d
+
+This augmentation does not seem to be essential, so disable it until
+it is fixed or properly removed.
+
+---
+--- a/substance-flamingo/build.gradle
 b/substance-flamingo/build.gradle
+@@ -24,6 +24,8 @@ dependencies {
+ 
+ task augmentation(dependsOn: classes) {
+   description = "Performs code augmentaiton for the laf-plugin and laf-widget libraries on the substance jar classes"
++  // Broken under Java 11 - see Debian bug #1013594
++  enabled = false
+ 
+   doLast {
+ def augmentClassPath = configurations.toolsCompile.asPath + File.pathSeparator + configurations.compile.asPath
+--- a/substance-swingx/build.gradle
 b/substance-swingx/build.gradle
+@@ -25,6 +25,8 @@ dependencies {
+ 
+ task augmentation(dependsOn: classes) {
+   description = "Performs code augmentaiton for the laf-plugin and laf-widget libraries on the substance jar classes"
++  // Broken under Java 11 - see Debian bug #1013594
++  enabled = false
+ 
+   doLast {
+ def augmentClassPath = configurations.toolsCompile.asPath + File.pathSeparator + configurations.compile.asPath
+--- a/substance/build.gradle
 b/substance/build.gradle
+@@ -28,6 +28,8 @@ dependencies {
+ 
+ task augmentation(dependsOn: classes) {
+   description = "Performs code augmentaiton for the laf-plugin and laf-widget libraries on the substance jar classes"
++  // Broken under Java 11 - see Debian bug #1013594
++  enabled = false
+ 
+   doLast {
+ def augmentClassPath = configurations.toolsCompile.asPath
diff -Nru insubstantial-7.3+dfsg3/debian/patches/series insubstantial-7.3+dfsg3/debian/patches/series
--- insubstantial-7.3+dfsg3/debian/patches/series	2019-08-26 13:49:59.0 +0200
+++ insubstantial-7.3+dfsg3/debian/patches/series	2023-03-03 22:31:44.0 +0100
@@ -4,3 +4,4 @@
 asm5.patch
 java9-compatibility.patch
 fix-56.patch
+java-11-disable-augmentation.patch


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

Bug#1013594: marked as done (insubstantial: FTBFS: Caused by: : java.lang.VerifyError: Expecting a stackmap frame at branch target 33)

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 23:19:17 +
with message-id 
and subject line Bug#1013594: fixed in insubstantial 7.3+dfsg3-5.1
has caused the Debian Bug report #1013594,
regarding insubstantial: FTBFS: Caused by: : java.lang.VerifyError: Expecting a 
stackmap frame at branch target 33
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.)


-- 
1013594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: insubstantial
Version: 7.3+dfsg3-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- -x test check assemble -x :substance:compileToolsJava
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=insubstantial -Dfile.encoding=UTF-8 
> --parallel --max-workers=8 -x test check assemble -x 
> :substance:compileToolsJava
> Initialized native services in: /<>/.gradle/native
> To honour the JVM settings for this build a new JVM will be forked. Please 
> consider using the daemon: 
> https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html.
> Starting process 'Gradle build daemon'. Working directory: 
> /<>/.gradle/daemon/4.4.1 Command: 
> /usr/lib/jvm/java-11-openjdk-amd64/bin/java 
> -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar
>  --add-opens java.base/java.lang=ALL-UNNAMED -Dfile.encoding=UTF-8 
> -Duser.country -Duser.language=en -Duser.variant -cp 
> /usr/share/gradle/lib/gradle-launcher-4.4.1.jar 
> org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1
> Successfully started process 'Gradle build daemon'
> An attempt to start the daemon took 0.834 secs.
> The client will now receive all logging from the daemon (pid: 4095812). The 
> daemon log file: /<>/.gradle/daemon/4.4.1/daemon-4095812.out.log
> Daemon will be stopped at the end of the build stopping after processing
> Closing daemon's stdin at end of input.
> The daemon will no longer process any standard input.
> Using 8 worker leases.
> Creating new cache for fileHashes, path 
> /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@624a2ef
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
> access org.gradle.cache.internal.DefaultCacheAccess@624a2ef
> Creating new cache for fileHashes, path 
> /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@146f4ba3
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Creating new cache for metadata-1.1/results, path 
> /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@478049c5
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> SubsetScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> BuildScriptTransformer.
> Settings evaluated using settings file '/<>/settings.gradle'.
>   Settings file found (/<>/settings.gradle), but 
> rootProject.name isn't defined
>   Root project name not defined in settings.gradle, defaulting to 
> 'insubstantial' instead of the name of the root directory 
> 'insubstantial-7.3+dfsg3'
> Projects loaded. Root project using build file 
> '/<>/build.gradle'.
> Included projects: [root project 'insubstantial', project ':flamingo', 
> project ':laf-plugin', project ':laf-widget', project ':substance', project 
> ':substance-flamingo', project ':substance-swingx', project ':trident']
>   Keep-alive timer started
>   Adding Debian repository to project 'insubstantial'
>   Adding Debian repository to project 'flamingo'
>   Adding Debian repository to project 'laf-plugin'
>   Adding Debian repository to project 'laf-widget'
>   Adding Debian repository to project 'substance'
>   Adding Debian repository to project 'substance-flamingo'
>   Adding Debian repository to project 'substance-swingx'
>   Adding Debian repository to project 'trident'
> 

Processed: severity of 1030205 is grave

[Debian Bug Tracking System]

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

> severity 1030205 grave
Bug #1030205 [scilab] scilab: Could not find Java package 
'/usr/share/java/batik-all-1.14.jar'
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Processed: Bug#1031794 marked as pending in socklog

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1031794 [src:socklog] socklog: fails to extract source package: 
dpkg-source: error: pathname 
'socklog-2.1.0+repack/debian/service/socklog-unix/log/supervise' points outside 
source root (to '/run/runit/supervise/socklog-unix.log')
Added tag(s) pending.

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

Bug#1031794: marked as pending in socklog

[Mathieu Mirmont]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/socklog/-/commit/6600381e0afd6158e0088b6604753e717a191f1e


service/socklog-unix: remove supervise symlink (Closes: #1031794)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1031794

Bug#1023284: marked as done (libevent: FTBFS with glibc 2.36)

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 21:49:23 +
with message-id 
and subject line Bug#1023284: fixed in libevent 2.1.12-stable-8
has caused the Debian Bug report #1023284,
regarding libevent: FTBFS with glibc 2.36
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.)


-- 
1023284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libevent
Version: 2.0.21-stable-2+deb8u1
Severity: serious
Justification: FTBFS

Hello,

Since the upload of glibc 2.36 in unstable (2.36-3), libevent fails to
build from source:

dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libevent-core-2.1-7/DEBIAN/symbols doesn't 
match completely debian/libevent-core-2.1-7.symbols
--- debian/libevent-core-2.1-7.symbols 
(libevent-core-2.1-7_2.1.12-stable-5_amd64)
+++ dpkg-gensymbolse6mOZa   2022-11-01 18:35:41.660556092 +0100
@@ -394,7 +394,7 @@
  evutil_parse_sockaddr_port@Base 2.1.8-stable
  evutil_read_file_@Base 2.1.8-stable
  evutil_rtrim_lws_@Base 2.1.8-stable
- evutil_secure_rng_add_bytes@Base 2.1.8-stable
+#MISSING: 2.1.12-stable-5# evutil_secure_rng_add_bytes@Base 2.1.8-stable
  evutil_secure_rng_get_bytes@Base 2.1.8-stable
  evutil_secure_rng_global_setup_locks_@Base 2.1.8-stable
  evutil_secure_rng_init@Base 2.1.8-stable

That's probably due the addition of arc4random in glibc, which makes

#if !defined(EVENT__HAVE_ARC4RANDOM) || 
defined(EVENT__HAVE_ARC4RANDOM_ADDRANDOM)
void
evutil_secure_rng_add_bytes(const char *buf, size_t n)
{
arc4random_addrandom((unsigned char*)buf,
n>(size_t)INT_MAX ? INT_MAX : (int)n);
}
#endif

not define evutil_secure_rng_add_bytes any more.

Samuel

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), 
(500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- End Message ---
--- Begin Message ---
Source: libevent
Source-Version: 2.1.12-stable-8
Done: Nicolas Mora 

We believe that the bug you reported is fixed in the latest version of
libevent, 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 1023...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Mora  (supplier of updated libevent 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: SHA512

Format: 1.8
Date: Wed, 04 Jan 2023 15:28:26 -0500
Source: libevent
Architecture: source
Version: 2.1.12-stable-8
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Mora 
Changed-By: Nicolas Mora 
Closes: 1023284
Changes:
 libevent (2.1.12-stable-8) unstable; urgency=medium
 .
   * Upload to unstable
   * Restore last unstable version
   * d/patches: Add patch evutil_secure_rng_add_bytes_noop.patch
 to make evutil_secure_rng_add_bytes noop with glibc's
 implemtation of arc4random, thanks z...@debian.org!
 (Closes: #1023284)
   * d/control: upgrade Standards-Version to 4.6.2
   * d/copyright: update year to 2023
Checksums-Sha1:
 c9d26c6ab0f5bcbabedbcd7c740ea3179c011a9a 2356 libevent_2.1.12-stable-8.dsc
 cd55656a9b5bed630b08f05495230affb7996b21 1100847 
libevent_2.1.12-stable.orig.tar.gz
 bb30312e6c69451caf0b7832af37b823b0f86392 17632 
libevent_2.1.12-stable-8.debian.tar.xz
 

Processed: Re: grub: grub-probe doesn't detect that file is on cryptfs on new installation

[Debian Bug Tracking System]

Processing control commands:

> tag -1 upstream fixed-upstream patch
Bug #1028301 [grub-common] grub: grub-probe doesn't detect that file is on 
cryptfs on new installation
Added tag(s) patch, fixed-upstream, and upstream.

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

Bug#1028301: grub: grub-probe doesn't detect that file is on cryptfs on new installation

[Ben Hutchings]

Control: tag -1 upstream fixed-upstream patch

On Mon, 09 Jan 2023 12:12:19 +0100 Laurent Bigonville
 wrote:
> Package: grub-common
> Version: 2.06-7
> Severity: serious
> File: /usr/sbin/grub-probe
> 
> Hello,
> 
> On a newly installed laptop, it seems that grub-probe is not able to
> detect that files are on an encrypted FS.
> 
> New laptop:
> 
> $ sudo grub-probe -t abstraction 
> /usr/share/images/desktop-base/desktop-grub.png
> lvm
> 
> $ sudo lsblk
> NAME  MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
> nvme0n1   259:0    0 476,9G  0 disk
> ├─nvme0n1p1   259:1    0   512M  0 part  /boot/efi
> ├─nvme0n1p2   259:2    0   488M  0 part  /boot
> └─nvme0n1p3   259:3    0   476G  0 part
>   └─nvme0n1p3_crypt   254:0    0 475,9G  0 crypt
> ├─new_laptop--vg-root    254:1    0  27,9G  0 lvm   /
> ├─new_laptop--vg-swap_1  254:2    0   976M  0 lvm   [SWAP]
> ├─new_laptop--vg-home    254:3    0    40G  0 lvm   /home
> └─new_laptop--vg-libvirt 254:4    0    60G  0 lvm   /var/lib/libvirt
[...]

I can reproduce this. What changed is that we now use LUKS2 instead of
LUKS1. Although GRUB has some LUKS2 support, it doesn't probe LUKS2
volumes automatically.

I found the 3 upstream commits that are enough to make the "grub-probe
..." line work and am attaching a debdiff with those.  I don't know
whether this is enough to completely fix the problem.

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.

diff -Nru grub2-2.06/debian/changelog grub2-2.06/debian/changelog
--- grub2-2.06/debian/changelog	2023-02-25 21:16:55.0 +0100
+++ grub2-2.06/debian/changelog	2023-03-03 19:21:28.0 +0100
@@ -1,3 +1,15 @@
+grub2 (2.06-8.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix probing of LUKS2 devices (Closes: #1028301):
+- disk/cryptodisk: When cheatmounting, use the sector info of the cheat
+  device
+- osdep/devmapper/getroot: Have devmapper recognize LUKS2
+- osdep/devmapper/getroot: Set up cheated LUKS2 cryptodisk mount from DM
+  parameters
+
+ -- Ben Hutchings   Fri, 03 Mar 2023 19:21:28 +0100
+
 grub2 (2.06-8.1) experimental; urgency=medium
 
   * Non-maintainer upload.
diff -Nru grub2-2.06/debian/patches/disk-cryptodisk-when-cheatmounting-use-the-sector-info-of-the-cheat-device.patch grub2-2.06/debian/patches/disk-cryptodisk-when-cheatmounting-use-the-sector-info-of-the-cheat-device.patch
--- grub2-2.06/debian/patches/disk-cryptodisk-when-cheatmounting-use-the-sector-info-of-the-cheat-device.patch	1970-01-01 01:00:00.0 +0100
+++ grub2-2.06/debian/patches/disk-cryptodisk-when-cheatmounting-use-the-sector-info-of-the-cheat-device.patch	2023-03-03 19:21:28.0 +0100
@@ -0,0 +1,72 @@
+From: Fabian Vogt 
+Date: Thu, 12 Jan 2023 17:05:07 -0600
+Subject: disk/cryptodisk: When cheatmounting, use the sector info of the cheat
+ device
+Origin: https://git.savannah.gnu.org/cgit/grub.git/commit/?id=efc9c363b2aab222586b420508eb46fc13242739
+Bug-Debian: https://bugs.debian.org/1028301
+
+When using grub-probe with cryptodisk, the mapped block device from the host
+is used directly instead of decrypting the source device in GRUB code.
+In that case, the sector size and count of the host device needs to be used.
+This is especially important when using LUKS2, which does not assign
+total_sectors and log_sector_size when scanning, but only later when the
+segments in the JSON area are evaluated. With an unset log_sector_size,
+grub_device_open() complains.
+
+This fixes grub-probe failing with
+"error: sector sizes of 1 bytes aren't supported yet.".
+
+Signed-off-by: Fabian Vogt 
+Reviewed-by: Patrick Steinhardt 
+Tested-by: Glenn Washburn 
+Reviewed-by: Glenn Washburn 
+Reviewed-by: Patrick Steinhardt 
+Reviewed-by: Daniel Kiper 
+---
+ grub-core/disk/cryptodisk.c | 20 ++--
+ 1 file changed, 18 insertions(+), 2 deletions(-)
+
+--- a/grub-core/disk/cryptodisk.c
 b/grub-core/disk/cryptodisk.c
+@@ -694,16 +694,31 @@ grub_cryptodisk_open (const char *name,
+   if (!dev)
+ return grub_error (GRUB_ERR_UNKNOWN_DEVICE, "No such device");
+ 
+-  disk->log_sector_size = dev->log_sector_size;
+-
+ #ifdef GRUB_UTIL
+   if (dev->cheat)
+ {
++  grub_uint64_t cheat_dev_size;
++  unsigned int cheat_log_sector_size;
++
+   if (!GRUB_UTIL_FD_IS_VALID (dev->cheat_fd))
+ 	dev->cheat_fd = grub_util_fd_open (dev->cheat, GRUB_UTIL_FD_O_RDONLY);
+   if (!GRUB_UTIL_FD_IS_VALID (dev->cheat_fd))
+ 	return grub_error (GRUB_ERR_IO, N_("cannot open `%s': %s"),
+ 			   dev->cheat, grub_util_fd_strerror ());
++
++  /* Use the sector size and count of the cheat device. */
++  cheat_dev_size = grub_util_get_fd_size (dev->cheat_fd, dev->cheat, _log_sector_size);
++  if (cheat_dev_size == -1)
++{
++  const char *errmsg = grub_util_fd_strerror ();
++  grub_util_fd_close (dev->cheat_fd);
++  dev->cheat_fd 

Processed: Re: Bug#1032259: conky: High CPU usage

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1032259 [src:conky] High CPU and memory usage
Severity set to 'important' from 'serious'

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

Bug#1032259: conky: High CPU usage

[Vincent Cheng]

Control: severity -1 important

On Fri, Mar 3, 2023 at 5:48 AM Antoine Le Gonidec
 wrote:
>
> I think I can confirm that the high Xorg memory usage is due to this update, 
> I am now sitting at 3.30GB after a dozen hours.
>
> To make really sure of the cause, I am going to revert to the 1.17 build of 
> Conky and let it run for a dozen hours too.
>
> In the meantime I am bumping the bug severity again to prevent this memory 
> leak to reach Bookworm, once again feel free to revert that if you think that 
> is not such a big deal (I guess not everyone have X sessions running for 
> several days).

I'm downgrading severity because I can't repro it on my end, and I
don't think it qualifies as a RC bug unless it's more widespread. I'd
be happy to cherrypick a patch for this for bookworm once upstream
fixes the issue.

Regards,
Vincent

Bug#1030284: [Pkg-javascript-devel] Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

[Emanuele Rocca]

Hi,

On Wed, Mar 01, 2023 at 02:41:05PM +0100, Jérémy Lal wrote:
> For now I'm unlucky with the porterbox, because /var/run/schroot
> disappeared yesterday.

I can confirm that the issue isn't reproducible with V8_DEFAULT_STACK_SIZE_KB
set to 984. Built and tested on a Macbook M1.

  (sid-arm64)ema@sarzana:~/debian/dygraphs-2.2.1
  $ babeljs --config-file $PWD/babel.config.json --compact false --source-maps 
inline -d tests5 auto_tests
  Successfully compiled 59 files with Babel (994ms).

Bug#1026204: tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64

[Kurt Roeckx]

Hi,

Is the issue that with older glibc versions, it was silently casted
to a 32 bit value, but now that glibc supports 64 bit, it knows
it can't represent it, and gives an error?

Maybe for bookworm, we should just ignore the test error?


Kurt

Bug#1003044: python3-dateutil: python_dateutil get_zonefile_instance functionality is broken (no zoneinfo found)

[Sandro Tosi]

> This bug is about the warning, not about the fact that the bundled zoninfo
> database is missing.

not exactly

even if these APIs are deprecated upstream, i think breaking them on
purpose (by removing the bundled timezone file) is uncalled for.

Either we reintroduce the timezone file (that may not be a good idea)
or translate these deprecated APIs into the recommended one, or we do
something else entirely, it's up for debate.

simply silencing the warning message is providing 0 value to a proper solution.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#1026508: ca-certificates: FTBFS: TypeError: argument 'data': 'bytearray' object cannot be converted to 'PyBytes'

[Kurt Roeckx]

Hi,

Are you waiting for something before uploading this fix?


Kurt

Bug#1023284: libevent: FTBFS with glibc 2.36

[Nicolas Mora]

Hello,

The patch was submitted upstream for their feedback [1], and was finally 
agreed. So I will upload a new package very soon then.


/Nicolas

[1] https://github.com/libevent/libevent/issues/1393#issuecomment-1453924054

Processed: tagging 1003044

[Debian Bug Tracking System]

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

> tags 1003044 + patch
Bug #1003044 [python3-dateutil] internal 'getzoneinfofile_stream' method emits 
a warning message
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1003044: python3-dateutil: python_dateutil get_zonefile_instance functionality is broken (no zoneinfo found)

[Arnout Vandecappelle]

 [I picked up this bug as part of a Debian bugsquashing sprint together with my 
colleagues.]

 Since there's been some back-and-forth in this thread, let me first summarize 
the status.

- The following will print an ugly warning:

In [1]: from dateutil import zoneinfo

In [2]: zoneinfo.get_zonefile_instance()
/usr/lib/python3/dist-packages/dateutil/zoneinfo/__init__.py:26:
UserWarning: I/O error(2): No such file or directory
 warnings.warn("I/O error({0}): {1}".format(e.errno, e.strerror))
Out[2]: 


- It's just a warning, but it may confuse tools that consume stderr, or build
  scripts may fail if anything is emitted on stderr.

- The warning can also be triggered by requesting a timezone that doesn't exist:

In [1]: from dateutil import tz In [2]: tz.gettz('foo') 
/usr/lib/python3/dist-packages/dateutil/zoneinfo/__init__.py:26: UserWarning: 
I/O error(2): No such file or directory  warnings.warn("I/O error({0}): 
{1}".format(e.errno, e.strerror)) - In this case, the warning is in fact 
useless: if a timezone doesn't exist in the system database, it doesn't exist. - 
Thus, the only case where the warning is relevant is when the bundled database 
is used explicitly (by calling zoneinfo.get_zonefile_instance()).

  However, this is not really a valid use case.


 I conclude from this that all that really has to be done is to remove the
warning. Since the debian package doesn't have the bundled zoneinfo database,
it is not useful to issue a warning when there is no bundled zoneinfo database.
This bug is about the warning, not about the fact that the bundled zoninfo
database is missing.

 Therefore, the attached patch removes the warning. This is done as part of
Remove_Zoneinfo_Tarball.patch because removing the database should really go 
hand in hand with removing the warning. [Note that this is my first time 
contribution to Debian packaging. I'm actually using Fedora myself :-). The 
patch was tested by building it with pbuilder and running it in a bookworm 
container. Please let me know if there is anything else I should do, or if there 
is anything I should have done differently.] Regards, Arnout
diff -Nru python-dateutil-2.8.2/debian/changelog python-dateutil-2.8.2/debian/changelog
--- python-dateutil-2.8.2/debian/changelog	2022-10-14 13:10:49.0 +0200
+++ python-dateutil-2.8.2/debian/changelog	2023-03-03 18:58:30.0 +0100
@@ -1,3 +1,10 @@
+python-dateutil (2.8.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove warning about missing bundled zoneinfo database (closes: #1003044) 
+
+ -- Arnout Vandecappelle   Fri, 03 Mar 2023 18:58:30 +0100
+
 python-dateutil (2.8.2-1) unstable; urgency=medium
 
   * Team upload
diff -Nru python-dateutil-2.8.2/debian/patches/Remove_Zoneinfo_Tarball.patch python-dateutil-2.8.2/debian/patches/Remove_Zoneinfo_Tarball.patch
--- python-dateutil-2.8.2/debian/patches/Remove_Zoneinfo_Tarball.patch	2022-10-14 13:10:49.0 +0200
+++ python-dateutil-2.8.2/debian/patches/Remove_Zoneinfo_Tarball.patch	2023-03-03 18:58:30.0 +0100
@@ -5,9 +5,10 @@
 ---
  MANIFEST.in  | 1 +
  dateutil/test/test_tz.py | 2 ++
+ dateutil/zoneinfo/__init__.py| 1 -
  python_dateutil.egg-info/SOURCES.txt | 3 +--
  setup.cfg| 3 ---
- 4 files changed, 4 insertions(+), 5 deletions(-)
+ 5 files changed, 4 insertions(+), 6 deletions(-)
 
 diff --git a/MANIFEST.in b/MANIFEST.in
 index d4d9f32..3e8b3fb 100644
@@ -38,6 +39,18 @@
  def testPickleZoneFileGettz(self):
  zoneinfo_file = zoneinfo.get_zonefile_instance()
  tzi = zoneinfo_file.get('America/New_York')
+diff --git a/dateutil/zoneinfo/__init__.py b/dateutil/zoneinfo/__init__.py
+index 34f11ad..18021dc 100644
+--- a/dateutil/zoneinfo/__init__.py
 b/dateutil/zoneinfo/__init__.py
+@@ -23,7 +23,6 @@ def getzoneinfofile_stream():
+ try:
+ return BytesIO(get_data(__name__, ZONEFILENAME))
+ except IOError as e:  # TODO  switch to FileNotFoundError?
+-warnings.warn("I/O error({0}): {1}".format(e.errno, e.strerror))
+ return None
+ 
+ 
 diff --git a/python_dateutil.egg-info/SOURCES.txt b/python_dateutil.egg-info/SOURCES.txt
 index c0d2a0f..ae4d43f 100644
 --- a/python_dateutil.egg-info/SOURCES.txt

Bug#1014329: marked as done (anbox: Not working after removing ashmem module)

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 19:22:28 +
with message-id 
and subject line Bug#1032304: Removed package(s) from unstable
has caused the Debian Bug report #1014329,
regarding anbox: Not working after removing ashmem module
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.)


-- 
1014329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: anbox
Version: 0.0~git20211020-3
Severity: grave
Justification: renders package unusable
Forwarded: https://github.com/anbox/anbox/issues/2042
X-Debbugs-Cc: z...@debian.org

ashmem_linux module has been removed from kernel 5.18.

https://github.com/torvalds/linux/commit/721412ed3d819e767cac2b06646bf03aa158aaec
https://salsa.debian.org/kernel-team/linux/-/commit/7d080ca22b66848115547ebc7da839d18db956f4
--- End Message ---
--- Begin Message ---
Version: 0.0~git20211020-3+rm

Dear submitter,

as the package anbox has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1032304

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1023284: libevent: FTBFS with glibc 2.36

[Kurt Roeckx]

Hi,

It seems a fix for this is sitting git, but hasn't been uploaded. Is
there a reason it's not been uploaded yet?


Kurt

Processed: severity of 987355 is grave

[Debian Bug Tracking System]

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

> severity 987355 grave
Bug #987355 [phpldapadmin] CVE-2020-35132
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#1031812: marked as done (crystal missing several dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 18:34:08 +
with message-id 
and subject line Bug#1031812: fixed in crystal 1.6.0+dfsg-3
has caused the Debian Bug report #1031812,
regarding crystal missing several dependencies
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.)


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

Package: crystal
Version: 1.6.0+dfsg-2
Severity: serious

Hi!

On a fresh unstable install, installing crystal and trying to compile a 
program with it fails due to dependency issues:


$ crystal hello.cr --: 1: cc: not found
Error: execution of command failed with code: 127: `cc "${@}" -o 
/root/.cache/crystal/crystal-run-hello.tmp  -rdynamic 
-L/usr/bin/../lib/crystal -lm -lgc -lpthread -levent -lrt -lpthread -ldl`


After installing the 'gcc' package, the error turns to
$ crystal hello.cr
/usr/bin/ld: cannot find -levent (this usually means you need to install 
the development package for libevent): No such file or directory

collect2: error: ld returned 1 exit status
Error: execution of command failed with code: 1: `cc "${@}" -o 
/root/.cache/crystal/crystal-run-hello.tmp  -rdynamic 
-L/usr/bin/../lib/crystal -lm -lgc -lpthread -levent -lrt -lpthread -ldl`


Only after also installing the 'libevent-dev' package it starts to work:
$ crystal hello.cr Hello World!

I am setting this as 'serious' as a violation of policy §3.5.

thanks,
Taavi

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

Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

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

Versions of packages crystal depends on:
ii  libc6 2.36-8
ii  libevent-2.1-72.1.12-stable-5+b1
ii  libgc-dev 1:8.2.2-3
ii  libgc11:8.2.2-3
ii  libgcc-s1 12.2.0-14
ii  libllvm14 1:14.0.6-10+b1
ii  libpcre3  2:8.39-15
ii  libstdc++612.2.0-14
ii  pkg-config1.8.1-1
ii  pkgconf [pkg-config]  1.8.1-1

crystal recommends no packages.

Versions of packages crystal suggests:
pn  crystal-doc  
pn  crystal-samples  

-- no debconf information


OpenPGP_0xEF242F709F912FBE.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: crystal
Source-Version: 1.6.0+dfsg-3
Done: David Suárez 

We believe that the bug you reported is fixed in the latest version of
crystal, 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 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Suárez  (supplier of updated crystal 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: Fri, 03 Mar 2023 19:03:34 +0100
Source: crystal
Architecture: source
Version: 1.6.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: David Suárez 
Changed-By: David Suárez 
Closes: 1031812
Changes:
 crystal (1.6.0+dfsg-3) unstable; urgency=medium
 .
   * Update runtime depends (Closes: #1031812).
Checksums-Sha1:
 38fdc54477529264f3b850ebd4401bf8487d6911 2185 crystal_1.6.0+dfsg-3.dsc
 3974fc9ef136e2cf1e3a22202e7170fbcc0e311c 6416 
crystal_1.6.0+dfsg-3.debian.tar.xz
 2ea001e5a28fae320a722c5636d5e7c6c22e7c7f 8505 
crystal_1.6.0+dfsg-3_source.buildinfo
Checksums-Sha256:
 f38763c0bd48153bf7399713fbcbc03869e664366241b383c1b046d94db7d3cd 2185 
crystal_1.6.0+dfsg-3.dsc
 be2f5da91653304b4b31c4c83c46b5c8a5d582d9a7ad44db4f033a08c3422893 6416 
crystal_1.6.0+dfsg-3.debian.tar.xz
 a81a495771660e1e4c952b7848862e83c711eb1ce4c9401561bbce1edcee2244 8505 
crystal_1.6.0+dfsg-3_source.buildinfo
Files:
 56edc47714cbe8450de7e2558e79eab4 2185 devel optional crystal_1.6.0+dfsg-3.dsc
 a22f4176340f941a6a6e6019443137b3 6416 devel optional 
crystal_1.6.0+dfsg-3.debian.tar.xz
 9a60e235101a0587b4cba6ac74372913 8505 devel optional 

Processed: bug 1023284 is forwarded to https://github.com/libevent/libevent/issues/1393

[Debian Bug Tracking System]

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

> forwarded 1023284 https://github.com/libevent/libevent/issues/1393
Bug #1023284 [src:libevent] libevent: FTBFS with glibc 2.36
Set Bug forwarded-to-address to 
'https://github.com/libevent/libevent/issues/1393'.
> thanks
Stopping processing here.

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

Bug#1029010: llvm-toolchain-15: autopkgtest regression

[Simon McVittie]

On Fri, 03 Mar 2023 at 17:41:22 +0100, Sylvestre Ledru wrote:
> Le 16/01/2023 à 16:44, Adrian Bunk a écrit :
> > /usr/include/wasm32-wasi/c++/v1/__type_traits/is_array.h:40:22: error: 
> > reference to unresolved using declaration
> > template  struct _LIBCPP_TEMPLATE_VIS 
> > is_array<_Tp[_Np]>
> >   ^
> > /usr/include/wasm32-wasi/c++/v1/cstddef:52:1: note: using declaration 
> > annotated with 'using_if_exists' here
> > using ::size_t _LIBCPP_USING_IF_EXISTS;

I've cut down what I think is the root cause of this compile failure to
a more minimal bug report: see #1032317.

I don't think this is *really* a regression, because in the version in
bookworm, the autopkgtest didn't exercise compilation of C++ into
WebAssembly at all.

If I understand correctly, when compared with bookworm, the version in
sid adds a new feature (the necessary -dev packages for compiling C++ into
WebAssembly) and also adds a smoke-test for that feature, but the feature
doesn't yet work as intended. Is that accurate?

Did the new autopkgtest coverage pass on the maintainers' systems? I don't
seen any sign of it having passed on ci.debian.net since 1:15.0.6-5~exp1
(see https://ci.debian.net/packages/l/llvm-toolchain-15/unstable/amd64/
which includes test results with all packages from unstable, and also test
results with llvm-toolchain-15 taken from experimental and everything else
from unstable).

If you don't consider full C++ wasm support to be release-critical for
bookworm, one option would be to remove the packages that enable it,
together with their test coverage; that should get the autopkgtest passing
again. However, I haven't looked at the diff between 15.0.6 and 15.0.7,
so I don't know whether the release team would be likely to accept an
unblock request or not.

When enabling new features in experimental, please check the CI results
before re-uploading to unstable. This can be done conveniently via
,
which asks the question: if the packages in unstable were all in
testing, and the packages in experimental were all in unstable, would
llvm-toolchain-15 be able to migrate?

Thanks,
smcv

Bug#1022742: marked as done (multipath-tools: CVE-2022-41973 CVE-2022-41974)

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 17:02:40 +
with message-id 
and subject line Bug#1022742: fixed in multipath-tools 0.8.5-2+deb11u1
has caused the Debian Bug report #1022742,
regarding multipath-tools: CVE-2022-41973 CVE-2022-41974
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.)


-- 
1022742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: multipath-tools
Version: 0.9.0-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 0.7.9-3

Hi,

The following vulnerabilities were published for multipath-tools.

CVE-2022-41973[0]:
| Symlink attack

CVE-2022-41974[1]:
| Authorization bypass

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-41973
https://www.cve.org/CVERecord?id=CVE-2022-41973
[1] https://security-tracker.debian.org/tracker/CVE-2022-41974
https://www.cve.org/CVERecord?id=CVE-2022-41974
[2] https://www.openwall.com/lists/oss-security/2022/10/24/2

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: multipath-tools
Source-Version: 0.8.5-2+deb11u1
Done: Tobias Frost 

We believe that the bug you reported is fixed in the latest version of
multipath-tools, 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 1022...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated multipath-tools 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: Tue, 28 Feb 2023 14:59:15 +0100
Source: multipath-tools
Architecture: source
Version: 0.8.5-2+deb11u1
Distribution: bullseye-security
Urgency: high
Maintainer: Debian DM Multipath Team 
Changed-By: Tobias Frost 
Closes: 1022742
Changes:
 multipath-tools (0.8.5-2+deb11u1) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Backport patch for CVE-2022-41974 and CVE-2022-41973. (Closes: #1022742)
 - multipath.rules is now rebuilt from multipath.rules.in, superceding
   0010-multipath.rules-do-not-assume-usrmerged-paths.patch.
 - to rebuild multipath.rules reliably:
   - Reorder d/rules so it is built the file is copied
   - Remove the generated multipath.rules in d/clean
   - Remove also the patch that would have patched the output file
Checksums-Sha1:
 55fa8aeccf7cb740e4ea8d174c63fec0cbc25684 2619 
multipath-tools_0.8.5-2+deb11u1.dsc
 58886428511e57390cc7b2d71aac3920e2dd0461 494654 
multipath-tools_0.8.5.orig.tar.gz
 64ec5631d4147090a50b06fe1c0ae5b812679f5d 43920 
multipath-tools_0.8.5-2+deb11u1.debian.tar.xz
 f59a5c719231119b4848b937071f108ad8d16cef 9169 
multipath-tools_0.8.5-2+deb11u1_amd64.buildinfo
Checksums-Sha256:
 5d35c55e64514eddc0bd76781101b191e450adf6c29af164ed3c6eda3d74f4bf 2619 
multipath-tools_0.8.5-2+deb11u1.dsc
 0549ebe39fd3950ec49c16304da408c2bfe1b18d386d8e6647b5bcb60363c8aa 494654 
multipath-tools_0.8.5.orig.tar.gz
 0a6895e1e24e86f9a0e4865c3d70589a16ac654e68fa65d0c86447a47e2293e1 43920 
multipath-tools_0.8.5-2+deb11u1.debian.tar.xz
 719fd4dd19a265e1acfa0dd57731682b2c823c7fb22686950e727ba9fb39a8a6 9169 
multipath-tools_0.8.5-2+deb11u1_amd64.buildinfo
Files:
 14567d27fd7e348e7194ca23f2e5e289 2619 admin optional 
multipath-tools_0.8.5-2+deb11u1.dsc
 353e8ff3211d368c17c9b465a468c7ed 494654 admin optional 
multipath-tools_0.8.5.orig.tar.gz
 6cea518f56a77fdab875fe102061f3a8 43920 admin optional 
multipath-tools_0.8.5-2+deb11u1.debian.tar.xz
 d94cf13796963aa4658b3840b096bccf 9169 admin optional 
multipath-tools_0.8.5-2+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmP+bDQACgkQkWT6HRe9
XTaCAw/9HncYSdC7smsRwGJrwPUAJfYsqtU4qRxvo3LtuyI2obtSrel4AuVjm8v8
EWNi20CukCnd4qBWtsX9hVMD4u9dAPaAeqbZKO0m78PgGC8OsejSUFC2GbrvzkY2
o3XMGtHBonWlEpcXylFi+ofCGJd7s/23rlky49I8RQDkT0vk9G86JR0mmJCjKg2L
uU5+k3WIIb3xL8HR/L00fyFzpFqAQ+IMbLSpmnrPutLUJwGFBs9FzkwNJSMIt4aT

Bug#1029010: llvm-toolchain-15: autopkgtest regression

[Sylvestre Ledru]

Hello

Sorry, I missed this issue.

Faidon, does it ring a bell ?

Thanks

Sylvestre


Le 16/01/2023 à 16:44, Adrian Bunk a écrit :

Source: llvm-toolchain-15
Version: 1:15.0.7-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-15/30436521/log.gz

...
In file included from cout.cpp:1:
In file included from /usr/include/wasm32-wasi/c++/v1/iostream:41:
In file included from /usr/include/wasm32-wasi/c++/v1/ios:221:
In file included from /usr/include/wasm32-wasi/c++/v1/__locale:18:
In file included from /usr/include/wasm32-wasi/c++/v1/memory:841:
In file included from /usr/include/wasm32-wasi/c++/v1/__algorithm/copy.h:12:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__algorithm/unwrap_iter.h:13:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__iterator/iterator_traits.h:14:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__iterator/incrementable_traits.h:15:
In file included from /usr/include/wasm32-wasi/c++/v1/concepts:133:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__concepts/arithmetic.h:15:
In file included from /usr/include/wasm32-wasi/c++/v1/type_traits:421:
In file included from /usr/include/wasm32-wasi/c++/v1/__functional/invoke.h:17:
In file included from /usr/include/wasm32-wasi/c++/v1/__type_traits/decay.h:16:
/usr/include/wasm32-wasi/c++/v1/__type_traits/is_array.h:40:22: error: 
reference to unresolved using declaration
template  struct _LIBCPP_TEMPLATE_VIS is_array<_Tp[_Np]>
  ^
/usr/include/wasm32-wasi/c++/v1/cstddef:52:1: note: using declaration annotated 
with 'using_if_exists' here
using ::size_t _LIBCPP_USING_IF_EXISTS;
^
In file included from cout.cpp:1:
In file included from /usr/include/wasm32-wasi/c++/v1/iostream:41:
In file included from /usr/include/wasm32-wasi/c++/v1/ios:221:
In file included from /usr/include/wasm32-wasi/c++/v1/__locale:18:
In file included from /usr/include/wasm32-wasi/c++/v1/memory:841:
In file included from /usr/include/wasm32-wasi/c++/v1/__algorithm/copy.h:12:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__algorithm/unwrap_iter.h:13:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__iterator/iterator_traits.h:14:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__iterator/incrementable_traits.h:15:
In file included from /usr/include/wasm32-wasi/c++/v1/concepts:133:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__concepts/arithmetic.h:15:
In file included from /usr/include/wasm32-wasi/c++/v1/type_traits:421:
In file included from /usr/include/wasm32-wasi/c++/v1/__functional/invoke.h:17:
In file included from /usr/include/wasm32-wasi/c++/v1/__type_traits/decay.h:20:
/usr/include/wasm32-wasi/c++/v1/__type_traits/remove_extent.h:25:22: error: 
reference to unresolved using declaration
template  struct _LIBCPP_TEMPLATE_VIS 
remove_extent<_Tp[_Np]>
  ^
/usr/include/wasm32-wasi/c++/v1/cstddef:52:1: note: using declaration annotated 
with 'using_if_exists' here
using ::size_t _LIBCPP_USING_IF_EXISTS;
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
autopkgtest [04:43:27]: test command1: ---]
autopkgtest [04:43:27]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 1
...
autopkgtest [04:47:28]:  summary
command1 FAIL non-zero exit status 1
integration-test-suite-test PASS
cmake-test   PASS
command2 PASS
command3 PASS

___
Pkg-llvm-team mailing list
pkg-llvm-t...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-llvm-team

Bug#1032316: llvm-toolchain-15: is this version intended for Debian 12 'bookworm'?

[Simon McVittie]

Source: llvm-toolchain-15
Version: 1:15.0.7-1
Severity: serious
Justification: blocking RC bug fixes in Mesa from migrating
X-Debbugs-Cc: debian-rele...@lists.debian.org

llvm-toolchain-15/1:15.0.7-1 was uploaded several weeks ago, shortly
after the transition freeze, but has not migrated to testing due to an
autopkgtest regression (#1029010).

Mesa uses LLVM 15, so the new upstream release is preventing Mesa bug fixes
from migrating, some of them important or even release-critical.

Is this version intended to enter testing in time for Debian 12 'bookworm'?
It seems quite late in the release process for the restructuring that
happened in 1:15.0.6-5~exp1 to be uploaded to unstable, for example.

If this version is meant to enter testing, then please fix the autopkgtest
(I'll follow up to #1029010 with more about that) and coordinate with
the release team to get it into unstable.

Or, if this version is not meant to enter testing, please upload a
version to unstable that is intended for testing (which might involve
reverting some of the changes and/or using a "+really" version), and
then re-upload the newer version to experimental.

For more details of the freeze timeline, please refer to
,
 and
.

Thanks,
smcv

Processed (with 1 error): Re: Bug#1031364: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Debian Bug Tracking System]

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

> tags 1031364 + upstream,forwarded,patch
Unknown tag/s: forwarded.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky 
forky-ignore.

Bug #1031364 [vmdb2] e2fsprogs: generates filesystems that grub-install doesn't 
recognize
Added tag(s) upstream and patch.
> thanks
Stopping processing here.

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

Bug#1031364: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Gunnar Wolf]

tags 1031364 + upstream,forwarded,patch
thanks

I have reported this bug to the upstream author as issue #69:

https://gitlab.com/larswirzenius/vmdb2/-/issues/69

And proposed a simplistic patch as merge request #106:

https://gitlab.com/larswirzenius/vmdb2/-/merge_requests/106

Just for completeness sake, I'm including the patch in this report as
well:

diff --git a/vmdb/plugins/mkfs_plugin.py b/vmdb/plugins/mkfs_plugin.py
index 7bb32b6..f0bef3b 100644
--- a/vmdb/plugins/mkfs_plugin.py
+++ b/vmdb/plugins/mkfs_plugin.py
@@ -51,6 +51,17 @@ class MkfsStepRunner(vmdb.StepRunnerInterface):
 cmd.append("-L")
 cmd.append(label)
 
+# Ext4 filesystem features large_dir and metadata_csum_seed
+# are known to make versions of GRUB older than 2.06-8 unable
+# to boot. Keep this around at least until it is no longer
+# likely enough(?) users will try to build older target
+# systems.
+if fstype == "ext4":
+cmd.append("-O")
+cmd.append("^large_dir")
+cmd.append("-O")
+cmd.append("^metadata_csum_seed")
+
 options = values["options"] or None
 if options:
 for opt in options.split(" "):

Bug#1032198: marked as done (wapiti fails to start with Python 3.11)

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 15:06:56 +
with message-id 
and subject line Bug#1032198: fixed in wapiti 3.0.4+dfsg-2
has caused the Debian Bug report #1032198,
regarding wapiti fails to start with Python 3.11
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.)


-- 
1032198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wapiti
Version: 3.0.4+dfsg-1
Severity: grave
Justification: renders package unusable
User: de...@kali.org
Usertags: origin-kali
X-Debbugs-Cc: sop...@offensive-security.com

Hello

Wapiti fails to start with

Traceback (most recent call last):
  File "/usr/bin/wapiti", line 33, in 
sys.exit(load_entry_point('wapiti3==3.0.4', 'console_scripts', 'wapiti')())
 ^^^
  File "/usr/bin/wapiti", line 25, in importlib_load_entry_point
return next(matches).load()
   
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load
module = import_module(match.group('module'))
 
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1206, in _gcd_import
  File "", line 1178, in _find_and_load
  File "", line 1149, in _find_and_load_unlocked
  File "", line 690, in _load_unlocked
  File "", line 940, in exec_module
  File "", line 241, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/wapitiCore/main/wapiti.py", line 41, in 

from wapitiCore.language.language import _
  File "/usr/lib/python3/dist-packages/wapitiCore/language/language.py", line 
62, in 
lan = gettext.translation(
  
TypeError: translation() got an unexpected keyword argument 'codeset'

It is caused by a change in Python 3.11

The latest upstream release no longer contains this code. But we
can't update the package now because of the freeze.

The code can be patched easily to get rid of this issue, but I don't know if
there are any other issues with Python 3.11

This issue has first been reported here:
https://bugs.kali.org/view.php?id=8197

Regards,

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

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

Versions of packages wapiti depends on:
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
ii  python3 3.11.2-1
ii  python3-bs4 4.11.2-1
ii  python3-importlib-metadata  4.12.0-1
ii  python3-mako1.2.4+ds-1
ii  python3-markupsafe  2.1.2-1+b1
ii  python3-requests2.28.1+dfsg-1
ii  python3-six 1.16.0-4
ii  python3-socks   1.7.1+dfsg-1
ii  python3-tld 0.11.11-4
ii  python3-yaswfp  0.9.3-2

wapiti recommends no packages.

wapiti suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file 
/usr/lib/python3/dist-packages/wapitiCore/language/language.py (from wapiti 
package)
--- End Message ---
--- Begin Message ---
Source: wapiti
Source-Version: 3.0.4+dfsg-2
Done: Sophie Brun 

We believe that the bug you reported is fixed in the latest version of
wapiti, 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 1032...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sophie Brun  (supplier of updated wapiti 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: SHA512

Format: 1.8
Date: Fri, 03 Mar 2023 15:29:34 +0100
Source: wapiti
Architecture: source
Version: 3.0.4+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian 

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[James Addison]

Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
X-Debbugs-Cc: gunna...@debian.org

On Fri, 3 Mar 2023 15:10:30 +0100, Gunnar wrote:
> On 2023-03-03 13:21, James Addison wrote:
> > I also noticed that some of gnome-desktop's default locale-to-input-source
> > mappings provide multiple entries, delimited by the '+' character:
> > 
> > https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/43.2/libgnome-desktop/default-input-sources.h#L31

> That's a misconception. The '+' character is there to specify a layout 
> variant. So "ch+fr" means the "French (Switzerland)" keyboard layout.

Ok, that's good to have clarified - thank you Gunnar for the correction.

Unrelated to that: I think I'll pause from providing any further comments on
this bug thread for at least a few days.

Bug#1030298: marked as done (pyopencl: FTBFS on i386: = 1 failed, 304 passed, 7 skipped, 1 deselected, 2 xfailed, 31 warnings in 736.25s (0:12:16) =)

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 14:49:57 +
with message-id 
and subject line Bug#1030298: fixed in pyopencl 2022.3.1-2.1
has caused the Debian Bug report #1030298,
regarding pyopencl: FTBFS on i386: = 1 failed, 304 passed, 7 skipped, 1 
deselected, 2 xfailed, 31 warnings in 736.25s (0:12:16) =
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.)


-- 
1030298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyopencl
Version: 2022.3.1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=pyopencl=i386=2022.3.1-2%2Bb1=1675322850=0

=== short test summary info 
FAILED test_clmath.py::test_fmod[>]
= 1 failed, 304 passed, 7 skipped, 1 deselected, 2 xfailed, 31 warnings in 
736.25s (0:12:16) =
E: pybuild pybuild:388: test: plugin custom failed with: exit code=1: 
PYTHONPATH=/<>/.pybuild/cpython3_3.11/build cp -r 
/<>/test /<>/.pybuild/cpython3_3.11/build && cd 
/<>/.pybuild/cpython3_3.11/build/test && python3.11 -m pytest 
--verbosity=2 -k 'not test_event_set_callback' && rm -rf 
/<>/.pybuild/cpython3_3.11/build/test
Traceback (most recent call last):
  File "/usr/bin/pybuild", line 386, in main
run(func, i, version, c)
  File "/usr/bin/pybuild", line 324, in run
result = func(context, args)
 ^^^
  File "/usr/share/dh-python/dhpython/build/base.py", line 290, in wrapped_func
raise Exception(msg)
Exception: exit code=1: 
PYTHONPATH=/<>/.pybuild/cpython3_3.11/build cp -r 
/<>/test /<>/.pybuild/cpython3_3.11/build && cd 
/<>/.pybuild/cpython3_3.11/build/test && python3.11 -m pytest 
--verbosity=2 -k 'not test_event_set_callback' && rm -rf 
/<>/.pybuild/cpython3_3.11/build/test
rm -fr -- /tmp/dh-xdg-rundir-Y5upF5ES
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 -s 
custom "--test-args=PYTHONPATH={build_dir} cp -r {dir}/test {build_dir} && cd 
{build_dir}/test && {interpreter} -m pytest --verbosity=2 -k 'not 
test_event_set_callback' && rm -rf {build_dir}/test" returned exit code 13
make[1]: *** [debian/rules:49: override_dh_auto_test] Error 25

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: pyopencl
Source-Version: 2022.3.1-2.1
Done: Roland Mas 

We believe that the bug you reported is fixed in the latest version of
pyopencl, 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 1030...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roland Mas  (supplier of updated pyopencl 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: SHA512

Format: 1.8
Date: Tue, 21 Feb 2023 14:45:02 +0100
Source: pyopencl
Architecture: source
Version: 2022.3.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers 
Changed-By: Roland Mas 
Closes: 1030298
Changes:
 pyopencl (2022.3.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Backport upstream fix for "FTBFS on i386: = 1 failed, 304 passed, 7
 skipped, 1 deselected, 2 xfailed, 31 warnings in 736.25s (0:12:16) =",
 thanks to Sebastian Ramacher (Closes: #1030298).
Checksums-Sha1:
 daff409e5de61a18fa0e6ac61c445a18c9679a68 2758 pyopencl_2022.3.1-2.1.dsc
 0941904a8a029e85959719b96d287c04f2e47f16 26620 
pyopencl_2022.3.1-2.1.debian.tar.xz
 d67e7c122a74b730f8786107806b0241c25c06c9 11236 
pyopencl_2022.3.1-2.1_amd64.buildinfo
Checksums-Sha256:
 dd9968c64753700d3a9dd6a52e87721354aa3576535397f470ad7da5f60b0a28 2758 
pyopencl_2022.3.1-2.1.dsc
 dd8c0dfa413706910ef0d05ed8a8ca7fceb9682bd71c1dbcb95e9f8f62b1392a 26620 
pyopencl_2022.3.1-2.1.debian.tar.xz
 c5cf529f3c3a30c0a7c584e08442e3dbf36348ab200b04b679b8a9f88aba932a 11236 
pyopencl_2022.3.1-2.1_amd64.buildinfo
Files:
 5041b5fd87697682adf984f390e4229c 2758 python optional pyopencl_2022.3.1-2.1.dsc
 9bebb08fa653a14f5b939d2fa0b9462b 26620 python optional 
pyopencl_2022.3.1-2.1.debian.tar.xz
 05cdcd63aee452d42c126bb8f6d2f6dc 11236 python optional 

Bug#1032166: timeline data not shown in browser (from local install)

[Laura Arjona Reina]

Hello, I have done some tests and I think that the issue is related to 
CORS policy of the browsers.


If I install debian-timeline and I do:
 chromium  --allow-file-access-from-files 
file:///usr/share/debian-timeline/index.html &


I cannot see the events, but if I press F12 I can see them. So I think 
it's because 62-63  lines in media/debian-timeline.js:


	Timeline.loadXML("xml/events.xml?" + random, function(xml, url) { 
events.loadXML(xml, url); });
	Timeline.loadXML("xml/releases.xml?" + random, function(xml, url) { 
releases.loadXML(xml, url); });
	Timeline.loadXML("xml/release_eras.xml?" + random, function(xml, url) { 
release_eras.loadXML(xml, url); });


result in trying to load the data with the file:/// scheme, and thus, 
blocked by the browser. I think this does not happen in 
https://timeline.debian.net because there is a web server serving the 
files, so no file:/// is used.


I'll try to see if there is other way to load the data so a browser is 
happy with a local install; I'll also investigate if this issue is also 
related to the problems declaring the DOCTYPE as html5 (bug #1032293: 
when we set DOCTYPE html, the data is not rendered either and the 
timeline appears as empty).


Kind regards
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#1031794: socklog: fails to extract source package: dpkg-source: error: pathname 'socklog-2.1.0+repack/debian/service/socklog-unix/log/supervise' points outside source root (to '/run/runit/supervis

[Mathieu Mirmont]

On Wed, Feb 22, 2023 at 10:17:23PM +0100, Sven Joachim wrote:
> On 2023-02-22 21:45 +0100, Lucas Nussbaum wrote:
> 
> > Source: socklog
> > Version: 2.1.0+repack-4
> > Severity: serious
> >
> > dpkg-source: info: extracting socklog in socklog-2.1.0+repack
> > dpkg-source: info: unpacking socklog_2.1.0+repack.orig.tar.gz
> > dpkg-source: info: unpacking socklog_2.1.0+repack-4.debian.tar.xz
> > dpkg-source: info: using patch list from debian/patches/series
> > dpkg-source: info: applying 0001-socklog-conf-update-service.patch
> > dpkg-source: info: applying 0002-tryto-c.patch
> > dpkg-source: info: applying 0003-patches-fix-build-warnings.patch
> > dpkg-source: error: pathname 
> > 'socklog-2.1.0+repack/debian/service/socklog-unix/log/supervise' points 
> > outside source root (to '/run/runit/supervise/socklog-unix.log')
> >
> > That's on a system with a mix of testing and unstable. I'm not sure of
> > which package introduced that additional check. Let me know if you
> > cannot reproduce.
> 
> I can reproduce this, but only if the target directory
> (/run/runit/supervise) actually exists.  Otherwise dpkg-source does not
> complain.
> 
> Lintian reports the absolute symlink as a warning, but maybe turning it
> into an error would be more appropriate.

Thanks for checking, I'll be having a look soon. I haven't touched
this package in years and a bit of refreshing wouldn't hurt.

-- 
Mathieu Mirmont 


signature.asc
Description: Digital signature

Bug#982794: firefox-esr: illegal instruction in libxul.so on armhf

[Emanuele Rocca]

Hi,

On Sun, Feb 14, 2021 at 02:12:17PM +, Vincent Arkesteijn wrote:
> Firefox is killed with SIGILL shortly after startup:
> $ firefox-esr -safe-mode
> Illegal instruction
> $ 

This is due to the fact that some armhf CPUs do not have support for NEON
instructions.

skia used to detect such support at runtime, but that behavior was removed in
https://github.com/google/skia/commit/809ccf37ec836d0df64afd0b13023fd968d505a4

Firefox seems to erroneously enable NEON in places where it shouldn't. Trying
to figure out exactly where and what's the best way to address this.

Meanwhile, to reproduce and debug this issue on a amd64 machine:

  apt install debootstrap qemu-user-static binfmt-support schroot

Trying to run a armhf binary on the x86 host will invoke qemu-arm-static, see:

  /usr/sbin/update-binfmts --display qemu-arm
  ls -l /usr/libexec/qemu-binfmt/arm-binfmt-P

Create a armhf chroot:

  debootstrap --arch=armhf sid /srv/sid-armhf
  printf '[armhf]\ntype=directory\ndirectory=/srv/sid-armhf\n' >> 
/etc/schroot/schroot.conf

Install and run firefox-esr in the chroot:

  schroot -c armhf
  (armhf)root@ariel:/home/ema# apt install --no-install-recommends firefox-esr

Firefox seems to be working:

  (armhf)root@ariel:/home/ema# firefox --help | head -1
  Usage: firefox-esr [ options ... ] [URL]

The reason why firefox does not crash here is that the default armhf CPU
emulated by qemu-arm-static has NEON support. We can override that by setting
QEMU_CPU to cortex-r5f (which cannot execute NEON instructions) and reproduce
the issue:

  (armhf)root@ariel:/home/ema# QEMU_CPU=cortex-r5f firefox
  qemu: uncaught target signal 4 (Illegal instruction) - core dumped
  Illegal instruction

To get a backtrace, install Firefox's debugging symbols in the chroot:

  (armhf)root@ariel:/home/ema# echo 'deb http://deb.debian.org/debian-debug 
sid-debug main' > /etc/apt/sources.list.d/debug.list
  (armhf)root@ariel:/home/ema# apt update && apt install firefox-esr-dbgsym

And do the following on the x86 host:

  dpkg --add-architecture armhf
  apt install libc6:armhf libc6-dbg:armhf gdb-multiarch

  LD_LIBRARY_PATH=/srv/sid-armhf/usr/lib/arm-linux-gnueabihf qemu-arm-static -g 
1234 -cpu cortex-r5f /srv/sid-armhf/usr/bin/firefox-esr --private-window

In another terminal, again on the host, this should give you a backtrace:

  gdb-multiarch -q /srv/sid-armhf/usr/bin/firefox-esr -ex 'set architecture 
arm' -ex 'target remote :1234' -ex 'set debug-file-directory 
/srv/sid-armhf/usr/lib/debug' -ex 'set pagination off' -ex 'continue' -ex 'bt' 
-ex 'continue' -ex 'exit'

Something like:

  Program received signal SIGILL, Illegal instruction.
  0x37071dc6 in _GLOBAL__sub_I_SkOpts.cpp () from 
/srv/sid-armhf/usr/lib/firefox-esr/libxul.so
  #0  0x37071dc6 in _GLOBAL__sub_I_SkOpts.cpp () from 
/srv/sid-armhf/usr/lib/firefox-esr/libxul.so
  #1  0x3f7d144c in call_init (env=0x3f208340, argv=0x3c94, argc=1, 
l=) at dl-init.c:70
  #2  call_init (l=, argc=1, argv=0x3c94, env=0x3f208340) at 
dl-init.c:26
  #3  0x3f7d14f2 in _dl_init (main_map=0x3f245f00, argc=1, argv=0x3c94, 
env=0x3f208340) at dl-init.c:117
  #4  0x3f56664a in _dl_catch_exception () from 
/srv/sid-armhf/usr/lib/arm-linux-gnueabihf/libc.so.6
  #5  0x3f7d5b60 in dl_open_worker (a=0x3fffd7b0) at dl-open.c:808
  #6  0x3f566614 in _dl_catch_exception () from 
/srv/sid-armhf/usr/lib/arm-linux-gnueabihf/libc.so.6
  #7  0x3f7d5da2 in _dl_open (file=0x3fffda64 
"/srv/sid-armhf/usr/lib/firefox-esr/libxul.so", mode=-2147483391, 
  caller_dlopen=0x4000af81 <_start+4560>, nsid=-2, argc=1, argv=0x3c94, 
env=0x3f208340) at dl-open.c:884
  #8  0x3f4d9da0 in ?? () from 
/srv/sid-armhf/usr/lib/arm-linux-gnueabihf/libc.so.6

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[Gunnar Hjalmarsson]

On 2023-03-03 13:21, James Addison wrote:

I also noticed that some of gnome-desktop's default locale-to-input-source
mappings provide multiple entries, delimited by the '+' character:

https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/43.2/libgnome-desktop/default-input-sources.h#L31


That's a misconception. The '+' character is there to specify a layout 
variant. So "ch+fr" means the "French (Switzerland)" keyboard layout.


--
Gunnar

Bug#1031763: marked as done (python3-motor asyncio broken with python3.11)

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 13:48:59 +
with message-id 
and subject line Bug#1031763: fixed in python-motor 2.3.0-3
has caused the Debian Bug report #1031763,
regarding python3-motor asyncio broken with python3.11
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.)


-- 
1031763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-motor
Version: 2.3.0-2
Severity: important
X-Debbugs-Cc: thomas.celler...@appgate.com

Dear Maintainer,

Since bookworm was switched to python3.11 from python3.10 the
python3-motor package breaks when trying to use asyncio.

This is very easy to reproduce:

$ python3
Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import motor.motor_asyncio
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/motor/motor_asyncio.py", line 18, in 

from .frameworks import asyncio as asyncio_framework
  File 
"/usr/lib/python3/dist-packages/motor/frameworks/asyncio/__init__.py", line 28, 
in 
from asyncio import coroutine  # For framework interface.
^
ImportError: cannot import name 'coroutine' from 'asyncio' 
(/usr/lib/python3.11/asyncio/__init__.py)

This makes the package unusable when using asyncio on bookworm.

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

Kernel: Linux 5.19.0-32-generic (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages python3-motor depends on:
ii  python3  3.11.1-3
ii  python3-gridfs   3.11.0-1
ii  python3-pymongo  3.11.0-1+b5

python3-motor recommends no packages.

Versions of packages python3-motor suggests:
pn  python3-aiohttp  
pn  python3-tornado  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-motor
Source-Version: 2.3.0-3
Done: Étienne Mollier 

We believe that the bug you reported is fixed in the latest version of
python-motor, 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 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated python-motor 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: SHA512

Format: 1.8
Date: Fri, 03 Mar 2023 14:29:00 +0100
Source: python-motor
Architecture: source
Version: 2.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Étienne Mollier 
Closes: 1031763
Changes:
 python-motor (2.3.0-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Update standards version to 4.6.2, no changes needed.
 .
   [ Étienne Mollier ]
   * python-3.11.patch: add patch from upstream.
 This fixes an import error of motor.motor_asyncio.
 Thanks to Andrey Rakhmatullin for the hint!  (Closes: #1031763)
Checksums-Sha1:
 a4805031e56e3ffeefa9b565d1559e3bba1d895d 2302 python-motor_2.3.0-3.dsc
 3e4e2cbb012f3e304de4df9d5340871c8be861c9 14872 
python-motor_2.3.0-3.debian.tar.xz
Checksums-Sha256:
 e1911c9b3e4dfbc422caa8c089c79371f12c8c4f2777581bdb3eb6fcc65308a1 2302 
python-motor_2.3.0-3.dsc
 ef25c202fa2bd496134669b6f20f5759f0f5447232fd252c8aac67d8742932ab 14872 
python-motor_2.3.0-3.debian.tar.xz
Files:
 fab3436d228df7c1a8991d0531201f4e 2302 python optional python-motor_2.3.0-3.dsc
 bc9136b65dacd6ace69288e2e1140521 14872 python optional 
python-motor_2.3.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmQB9uwUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdpRHBAAgYC6OuRcdld3TiHS2F6PHkJ9d8t8
IfkENeKLHcVp8Jzc3J75eVfsBCEHpmOdR5J3Y8cElQ4ROTOscWPJ4hOkrss3aaj+
89qLjysryWoYLLn45IuyAY4Z+ZRyeiQfGg2yaZcCxEq1dGAaABcOcCaZNYkP534w
XbdSz+DVGcokPM9x7pKSWelfF5CTtiEYkG2lFVvvIgHtnUG2Q/hezzoeheQoe76C
EPrD6H39OO4oac504uVX1GtrJC6gdKy1YjLZpcKnWP5u0IM9ZOnYCMd1r852N8eE

Processed: your mail

[Debian Bug Tracking System]

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

> severity 1032259 serious
Bug #1032259 [src:conky] High CPU and memory usage
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1032041: marked as done (FTBFS: error: ‘size_t’ does not name a type)

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 13:34:07 +
with message-id 
and subject line Bug#1032041: fixed in arm-compute-library 20.08+dfsg-6
has caused the Debian Bug report #1032041,
regarding FTBFS: error: ‘size_t’ does not name a type
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.)


-- 
1032041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: arm-compute-library
Version: 20.08+dfsg-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid your package fails to build, with:

In file included from src/core/ITensorPack.cpp:24:
./arm_compute/core/ITensorPack.h:89:5: error: ‘size_t’ does not name a type
   89 | size_t size() const;
  | ^~
./arm_compute/core/ITensorPack.h:29:1: note: ‘size_t’ is defined in header 
‘’; did you forget to ‘#include ’?
   28 | #include 
  +++ |+#include 
   29 | 

Full log attached.


Meow!
-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (490, 'testing'), (250, 'unstable'), (201, 'experimental')
merged-usr: no
Architecture: arm64 (aarch64)

Kernel: Linux 6.1.0-3-arm64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
sbuild (Debian sbuild) 0.85.0 (04 January 2023) on rhun

+==+
| arm-compute-library (arm64)  Sat, 25 Feb 2023 23:54:14 + |
+==+

Package: arm-compute-library
Distribution: unstable
Machine Architecture: arm64
Host Architecture: arm64
Build Architecture: arm64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-arm64-sbuild-edf3fc6f-42f6-4973-91ef-878c3886c3bc'
 with '<>'
I: NOTICE: Log filtering will replace 
'build/arm-compute-library-q3qKDi/resolver-psabH1' with '<>'

+--+
| Update chroot|
+--+

Hit:1 http://apt-rosy.angband.pl:3142/debian unstable InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Check APT
-

Checking available source versions...

Download source files with APT
--

Reading package lists...
NOTICE: 'arm-compute-library' packaging is maintained in the 'Git' version 
control system at:
https://salsa.debian.org/wookey/arm-compute-library
Please use:
git clone https://salsa.debian.org/wookey/arm-compute-library
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 1941 kB of source archives.
Get:1 http://apt-rosy.angband.pl:3142/debian unstable/main arm-compute-library 
20.08+dfsg-5 (dsc) [2339 B]
Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main arm-compute-library 
20.08+dfsg-5 (tar) [1924 kB]
Get:3 http://apt-rosy.angband.pl:3142/debian unstable/main arm-compute-library 
20.08+dfsg-5 (diff) [14.7 kB]
Fetched 1941 kB in 0s (27.9 MB/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 
'build/arm-compute-library-q3qKDi/arm-compute-library-20.08+dfsg' with 
'<>'
I: NOTICE: Log filtering will replace 'build/arm-compute-library-q3qKDi' with 
'<>'

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: debhelper-compat (= 12), dh-exec (>= 0.3), scons (>= 
2.4), doxygen, graphviz, build-essential, fakeroot
Filtered Build-Depends: debhelper-compat (= 12), dh-exec (>= 0.3), scons (>= 
2.4), doxygen, graphviz, build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
'/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 

Processed: Bug#1031763 marked as pending in python-motor

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1031763 [python3-motor] python3-motor asyncio broken with python3.11
Added tag(s) pending.

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

Bug#1031763: marked as pending in python-motor

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1031763 in python-motor 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/python-team/packages/python-motor/-/commit/7e4fb051ea9111e5205c09914cfddc50a44a681b


python-3.11.patch: add patch.

This fixes the import error of motor.motor_asyncio.

Closes: #1031763
Thanks: Andrey Rakhmatullin for the hint


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1031763

Bug#1032310: marked as done (zcfan should "Conflicts: thinkfan")

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 13:26:41 +
with message-id 
and subject line Bug#1032310: fixed in thinkfan 1.3.1-4
has caused the Debian Bug report #1032310,
regarding zcfan should "Conflicts: thinkfan"
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.)


-- 
1032310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zcfan
Severity: normal
X-Debbugs-Cc: deb...@rocketjump.eu

Hi Michel,

thank you for packaging zcfan! I think it should have "Conflicts: thinkfan" set
in the package meta-data, as both installed on the same machine likely will
produce unpredictable behaviour.

By the way, it looks like you're using git-buildpackage. Can you push the
pristine-tar and upstream branches? That would make it easier for me to build
and verify the package, and provide a patch.

Greetings,
Lee

-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages zcfan depends on:
ii  libc6  2.31-13+deb11u3

zcfan recommends no packages.

zcfan suggests no packages.
--- End Message ---
--- Begin Message ---
Source: thinkfan
Source-Version: 1.3.1-4
Done: Lee Garrett 

We believe that the bug you reported is fixed in the latest version of
thinkfan, 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 1032...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lee Garrett  (supplier of updated thinkfan 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: SHA512

Format: 1.8
Date: Fri, 03 Mar 2023 13:41:08 +0100
Source: thinkfan
Architecture: source
Version: 1.3.1-4
Distribution: unstable
Urgency: medium
Maintainer: Lee Garrett 
Changed-By: Lee Garrett 
Closes: 1032310
Changes:
 thinkfan (1.3.1-4) unstable; urgency=medium
 .
   * Prevent thinkfan and zcfan being installed at the same time,
 as this will cause unpredictable behaviour and possibly hardware damage
 (Closes: #1032310)
   * Fix dep3 headers in two patches
   * Bump Standards-Version (no changes needed)
Checksums-Sha1:
 60b823880defb4c20d98e384087f42d4a8bf790f 2579 thinkfan_1.3.1-4.dsc
 897051c62a1aec82f45da11a948241efe98a5a15 9236 thinkfan_1.3.1-4.debian.tar.xz
 be5b32ae0d6f9883e1dd816789bdce50be0708f8 8388 thinkfan_1.3.1-4_amd64.buildinfo
Checksums-Sha256:
 89b74aa52ba2e07cf7c64d0451ef07fcc419dca98c9c2bd408a639bd435268fe 2579 
thinkfan_1.3.1-4.dsc
 c1d733f4d73677f80ff025ded2dbf2dd57a3436deae52428a9caf8355a1b899b 9236 
thinkfan_1.3.1-4.debian.tar.xz
 4537f637057e7a8fb0da910124b6251cd879fdce77d362e29f6d6cd2a13048ee 8388 
thinkfan_1.3.1-4_amd64.buildinfo
Files:
 9ce2dc1d016d453389b9f89bca2a505a 2579 misc optional thinkfan_1.3.1-4.dsc
 e90d109e2c11437a88278cc571d67ef6 9236 misc optional 
thinkfan_1.3.1-4.debian.tar.xz
 8b8123f122edc54e51bc99d1d05542f9 8388 misc optional 
thinkfan_1.3.1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEE2EfGJRCpwv8kLOAs1gShxII+4PgFAmQB8JQACgkQ1gShxII+
4PhxIx/7Byw8kUWTdM3xZvyTAF/Zdw+tFU8nljm1rjxWzRbvHXva/Y8q0wgRh+Qh
IJmFle5Qenz6ntz5zM5pG2lpRcq5wmHBN2X4xWxvwRgEG5M3EQWHwO0ODEl45Y1G
W4iYFgYXx/LQbAJKYGC0pEPBtGbX7pwYyLCns7VPMjg72uTIHKnCTNL3p8mCNjmD
NR2/vgbaxqzLxmo/Psyr/2WszLss0CWVEXgYx1Y6A00lcc0H36fr5Z2kXptG79fP
4WKpJjONgXiDJKxkpIBPVPByLyKbN0OqVtIXu5ynZYORHimHXzPQ+fbUHu8B8id8
IoihNgMMjDPrhodi5fuHshD4+7an3UZzPcotIfdLsyH33jYbGZ5Cy6Nr98074KIG
RiHzEjciWyB0hrx5EF7u98PkCQkObHFknIY4ZEumeHlzLlSaKhffT0jOMZbj0XV9
yZai7Mp1N2LO5vKQ+hL0u/iaIr5vjI8veNm0dHz0zOXDpVdQbeiZE0ub5+bCbYKI
77wdGrEWEe2sYUq0p3RYeK81bnjXkWafOLJ4voUhPgBk7MDUPeS+W578WtYTdaJP
gFWf7cWX0UUxk0HWv4BLIGRZzfcic+KX0AgU+i6i8+V++n9XN1n5kUU3wJzgQ8qd
twMR+rUTIcK8xMrU+3V+2yeRVl1H7H43M9JfourWasbJayD5t1If30aHCMe8Soji

Bug#1032255: pulseaudio: sound keeps dying (on Tiger Lake)

[James Addison]

Package: pulseaudio
Followup-For: Bug #1032255
Control: retitle -1 pulseaudio: application restart required to restore sound
Control: severity -1 normal
Control: tags -1 moreinfo

Hi Dave,

Are there any clues (error messages, service start/stops, or things like that)
in the affected system's journal logs?

The following command might be helpful along those lines:

  $ journalctl --user --merge --unit pulseaudio.service

Also, the following page provides some information (and some problem-solving
techniques) for PulseAudio on Debian - have you had any luck with any of these?

https://wiki.debian.org/PulseAudio

Cheers,
James

Processed: Re: pulseaudio: sound keeps dying (on Tiger Lake)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 pulseaudio: application restart required to restore sound
Bug #1032255 [pulseaudio] pulseaudio: sound keeps dying (on Tiger Lake)
Changed Bug title to 'pulseaudio: application restart required to restore 
sound' from 'pulseaudio: sound keeps dying (on Tiger Lake)'.
> severity -1 normal
Bug #1032255 [pulseaudio] pulseaudio: application restart required to restore 
sound
Severity set to 'normal' from 'serious'
> tags -1 moreinfo
Bug #1032255 [pulseaudio] pulseaudio: application restart required to restore 
sound
Added tag(s) moreinfo.

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

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[Gunnar Hjalmarsson]

X-Debbugs-CC: s...@debian.org, z...@debian.org, ken...@xdump.org, 
yy.y.ja...@gmail.com, iwama...@debian.org, debian-i...@lists.debian.org, 
debian-japan...@lists.debian.org, m...@packages.debian.org, 
ibus-an...@packages.debian.org


On 2023-03-03 12:52, James Addison wrote:

If it's true that the cause is that 'tasksel' and 'gnome-initial-setup'
are mismatched, then we could apply a fix in either one.

Given that we have an existing patch available for 'gnome-initial-desktop',
I've opened a corresponding 'tasksel' changeset with the mirrored side of
the fix at:

https://salsa.debian.org/installer-team/tasksel/-/merge_requests/25


While either one would address the inconsistency, most Japanese users 
seem to prefer mozc over anthy. So the two routes are not equally good.


Please do not ignore the user preferences.

--
Gunnar Hjalmarsson

Processed: reassign 1032310 to thinkfan

[Debian Bug Tracking System]

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

> reassign 1032310 thinkfan
Bug #1032310 [zcfan] zcfan should "Conflicts: thinkfan"
Bug reassigned from package 'zcfan' to 'thinkfan'.
Ignoring request to alter found versions of bug #1032310 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1032310 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[James Addison]

Package: libgnome-desktop-4-2
Followup-For: Bug #1029821

I also noticed that some of gnome-desktop's default locale-to-input-source
mappings provide multiple entries, delimited by the '+' character:

https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/43.2/libgnome-desktop/default-input-sources.h#L31

It's probably a question to ask them, but I am wondering whether it'd be
possible (and/or sensible) to provide *both* anthy and mozc in the default
input sources (which would correspond to adding ibus-anthy and ibus-mozc both
as 'Recommends', instead of a choice between them).

Processed: cloning 1017980

[Debian Bug Tracking System]

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

> clone 1017980 -1
Bug #1017980 [zcfan] zcfan should "Conflicts: thinkfan"
Bug 1017980 cloned as bug 1032310
> thanks
Stopping processing here.

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

Processed: severity of 1017980 is grave

[Debian Bug Tracking System]

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

> severity 1017980 grave
Bug #1017980 [zcfan] zcfan should "Conflicts: thinkfan"
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[James Addison]

Package: libgnome-desktop-4-2
Followup-For: Bug #1029821

(comment to bug-thread only)

If it's true that the cause is that 'tasksel' and 'gnome-initial-setup'
are mismatched, then we could apply a fix in either one.

Given that we have an existing patch available for 'gnome-initial-desktop',
I've opened a corresponding 'tasksel' changeset with the mirrored side of the
fix at:

https://salsa.debian.org/installer-team/tasksel/-/merge_requests/25

Processed: bug 1032177 is forwarded to https://github.com/wolfcw/libfaketime/issues/418

[Debian Bug Tracking System]

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

> forwarded 1032177 https://github.com/wolfcw/libfaketime/issues/418
Bug #1032177 [faketime] faketime doesn't fake time (on i386)
Set Bug forwarded-to-address to 
'https://github.com/wolfcw/libfaketime/issues/418'.
> thanks
Stopping processing here.

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

Bug#1018023: Update on this bug?

[Matthew Vernon]

Hi,

On 14/02/2023 18:36, Jose Antonio Jimenez Madrid wrote:


I will test this patch and let you to know whether the bug is fixed.


Any joy? We're approaching the time that eterm is going to be 
autoremoved from bookworm...


Thanks,

Matthew

Bug#1032300: odoo-14: Not functional with pypdf2 2.x

[Sebastien Delafond]

Package: odoo-14
Version: 14.0.0+dfsg.4-1
Severity: grave

odoo 14.x is not compatible with pypdf2 2.x, and the server cannot be
started:

  ModuleNotFoundError: No module named 'PyPDF2.utils'

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

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

Versions of packages odoo-14 depends on:
ii  adduser 3.131
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-4.1
ii  fonts-glyphicons-halflings  1.009~3.4.1+dfsg-3
pn  fonts-inconsolata   
ii  fonts-roboto-unhinted   2:0~20170802-3
ii  init-system-helpers 1.65.2
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-ui 1.13.2+dfsg-1
ii  libjs-underscore1.13.4~dfsg+~1.11.4-3
ii  lsb-base11.6
pn  postgresql-client   
ii  python3 3.11.2-1
ii  python3-babel   2.10.3-1
ii  python3-chardet 5.1.0+dfsg-2
ii  python3-dateutil2.8.2-1
ii  python3-decorator   5.1.1-3
ii  python3-docutils0.19+dfsg-6
ii  python3-feedparser  6.0.10-1
pn  python3-freezegun   
pn  python3-gevent  
ii  python3-html2text   2020.1.16-2
ii  python3-idna3.3-1
ii  python3-jinja2  3.0.3-2
pn  python3-libsass 
ii  python3-lxml4.9.2-1+b1
pn  python3-mako
ii  python3-mock4.0.3-4
pn  python3-num2words   
ii  python3-ofxparse0.21-2
ii  python3-passlib 1.7.4-3
ii  python3-pil 9.4.0-1.1+b1
pn  python3-polib   
ii  python3-psutil  5.9.4-1+b1
ii  python3-psycopg22.9.5-1+b1
pn  python3-pydot   
ii  python3-pyparsing   3.0.9-1
ii  python3-pypdf2  2.12.1-3
pn  python3-qrcode  
ii  python3-renderpm3.6.12-1+b1
ii  python3-reportlab   3.6.12-1
ii  python3-requests2.28.1+dfsg-1
pn  python3-serial  
pn  python3-stdnum  
pn  python3-suds
ii  python3-tz  2022.7.1-1
pn  python3-usb 
ii  python3-vobject 0.9.6.1-2
ii  python3-werkzeug2.2.2-2
pn  python3-xlrd
pn  python3-xlsxwriter  
pn  python3-xlwt
pn  python3-zeep
ii  sysvinit-utils [lsb-base]   3.06-2
ii  wkhtmltopdf 0.12.6-2+b1

Versions of packages odoo-14 recommends:
pn  postgresql
pn  python3-ldap  

odoo-14 suggests no packages.

Bug#1032048: marked as done (d3-dsv-tools: Dangling symlinks in /usr/bin/)

[Debian Bug Tracking System]

Your message dated Fri, 03 Mar 2023 08:23:24 +
with message-id 
and subject line Bug#1032048: fixed in node-d3-dsv 1.1.1-9
has caused the Debian Bug report #1032048,
regarding d3-dsv-tools: Dangling symlinks in /usr/bin/
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.)


-- 
1032048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: d3-dsv-tools
Version: 1.1.1-8
Severity: grave
Justification: renders package unusable

$ symlinks -tv /usr/bin* | fgrep dangling
dangling: /usr/bin/csv2json -> ../share/nodejs/d3-dsv/bin/dsv2json.js
dangling: /usr/bin/csv2tsv -> ../share/nodejs/d3-dsv/bin/dsv2dsv.js
dangling: /usr/bin/dsv2dsv -> ../share/nodejs/d3-dsv/bin/dsv2dsv.js
dangling: /usr/bin/json2csv -> ../share/nodejs/d3-dsv/bin/json2dsv.js
dangling: /usr/bin/json2dsv -> ../share/nodejs/d3-dsv/bin/json2dsv.js
dangling: /usr/bin/tsv2csv -> ../share/nodejs/d3-dsv/bin/dsv2dsv.js
dangling: /usr/bin/json2tsv -> ../share/nodejs/d3-dsv/bin/json2dsv.js
dangling: /usr/bin/dsv2json -> ../share/nodejs/d3-dsv/bin/dsv2json.js
dangling: /usr/bin/tsv2json -> ../share/nodejs/d3-dsv/bin/dsv2json.js

Looking at where those files actually might be, I figured that the
symlinks probably should point to the same target without the .js
suffix — or that those files need to be renamed:

/usr/share/nodejs/d3-dsv/bin/dsv2dsv
/usr/share/nodejs/d3-dsv/bin/dsv2json
/usr/share/nodejs/d3-dsv/bin/json2dsv

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

Kernel: Linux 6.1.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages d3-dsv-tools depends on:
ii  node-d3-dsv  1.1.1-8
ii  nodejs   18.13.0+dfsg1-1

d3-dsv-tools recommends no packages.

d3-dsv-tools suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: node-d3-dsv
Source-Version: 1.1.1-9
Done: Yadd 

We believe that the bug you reported is fixed in the latest version of
node-d3-dsv, 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 1032...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-d3-dsv 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: SHA512

Format: 1.8
Date: Fri, 03 Mar 2023 11:39:08 +0400
Source: node-d3-dsv
Architecture: source
Version: 1.1.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1032048
Changes:
 node-d3-dsv (1.1.1-9) unstable; urgency=medium
 .
   * Team upload
   * Fix links (Closes: #1032048)
   * Update standards version to 4.6.2, no changes needed.
Checksums-Sha1: 
 59171b7f6a319656906fd1689d3688fd4cd5e167 2143 node-d3-dsv_1.1.1-9.dsc
 a833932fa060e440ecfcbe53f895c588dda8be7c 4540 node-d3-dsv_1.1.1-9.debian.tar.xz
Checksums-Sha256: 
 351a84d7079694f5d46a14ba07029c0946a33133ec47f91d4332b8c0c061 2143 
node-d3-dsv_1.1.1-9.dsc
 e84b145c2b93b87263daaf65db68c94e0173906ee807c9e0ce6916b61ea99980 4540 
node-d3-dsv_1.1.1-9.debian.tar.xz
Files: 
 68fd954d8e66c47f7b166c5e12c93fd3 2143 javascript optional 
node-d3-dsv_1.1.1-9.dsc
 a5ae9af98ab130b22f8360f68896a24c 4540 javascript optional 
node-d3-dsv_1.1.1-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmQBpJoACgkQ9tdMp8mZ
7ulnLxAAmdlcVFmHBlC+Jb35DfwRLBdnx8w9wUuGkamExVzrEHoFNJUM2cpOg3pk
pV9feV6OwaDgMCwSXBO+JQp+m0/ISJ2ddHGctzJ9cw7TLf4VrhUGISRO/1QB/VvO
MXWuvK42lsonIL0lAlR53ShgCgBJLRqqUZAu7o6iY3CwczV87K03Xs3yFkd9FMLb
a/lgFYba2QRGPmhgL+wRXfqKNYVhV/Lz8dEn9QY1ViEWlXUC5dT9ibDNF24mhhp7
qMvUY0MwftRgjiV9tzt+PGq6ClVwGGRAPEkAhVFTzM6DWv7fZ9i/qmZwSahsiB12
AiWI3pvJlS8IV6amQUjR4BfcslG6u3JfFC6dbCT11CkoHlqqJhDVopKYWbjnrLXQ
vQzwfIAjQGQsm/2V9NqjiBvIZY0ZBGW1roPIKNA+nGgKGux7DyNH0BDnYTvEX00A
truCq7dkA65xhnEYpobQCZwDEC4xgAsMCiHnvB2LXkbeORfnGdcSjh7HpkY1dz1j
i/xrFJvUPBMgawtFqx6r1TTF8yB3cBjuzRM4mr7VdK3MkAQ9b34EcyZUqf+UCTfc

Bug#1027215: Bug#1026539: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

[Rebecca N. Palmer]

On 03/03/2023 06:00, Andreas Tille wrote:

Ahh, so aesara is not really a "fork" but a "rename"?


The original is abandoned (no new development since 2017, and now mostly 
unmaintained, which is probably why it has this kind of bug).  Aesara is 
a continuation by a new upstream (possibly one that mostly wanted it for 
their own use), that chose to break compatibility.