Bug#1076774: CVE-2024-40767

Source: nova Version: 2:26.1.0-4 Severity: grave This CVE-2024-40767 is embargoed, to be disclosed later today, so I'm not publishing any more details just yet. Barely opening this bug to reference it in the package. Cheers, Thomas Goirand (zigo)

Bug#1076775: gpscorrelate: autopkgtest failures

Source: gpscorrelate Version: 2.1-2 Severity: serious Hi Shriram, the test upstream-suite autopkgtest still fails on practically all the architectures, even after disabling the valgrind support (#1071656): - https://ci.debian.net/packages/g/gpscorrelate/testing/amd64/48755050/ - https://ci.debian

Processed: Re: swift-im: FTBFS: boost1.83 transition

Processing control commands: > reassign -1 src:boost1.83 Bug #1056100 [src:swift-im] swift-im: FTBFS: boost1.83 transition Bug reassigned from package 'src:swift-im' to 'src:boost1.83'. No longer marked as found in versions swift-im/5.0~alpha2.145.g12d031cf8+dfsg-3. Ignoring request to alter fixed

Bug#1056100: swift-im: FTBFS: boost1.83 transition

Control: reassign -1 src:boost1.83 Control: affects -1 swift-im Control: tags -1 fixed-upstream patch Control: retitle -1 boost1.83: Boost.Signals2 causes FTBFS Hi, This seems to be a boost bug: https://github.com/boostorg/signals2/issues/70 -- tobi On Thu, 16 Nov 2023 22:08:39 +0100 gl...@d

Bug#1076757: Please package version 3.10.4

Source: apscheduler Version: 3.9.1-2 Severity: serious Hi, The package is currently broken in Unstable, leading to the bug report I sent upstream for Watcher here: https://bugs.launchpad.net/watcher/+bug/2073821 which in fact shows an issue in apscheduler, that apparrently, is using keywords no

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

Your message dated Tue, 23 Jul 2024 01:48:56 + with message-id and subject line Bug#1072753: fixed in neutron-taas 12.0.0+git.2024.10.07.749ac4557c-1 has caused the Debian Bug report #1072753, regarding neutron-taas: FTBFS: Session.begin() got an unexpected keyword argument 'subtransactions'

Bug#1074763: marked as done (CVE-2024-32498: Arbitrary file access through custom QCOW2 external data)

Your message dated Tue, 23 Jul 2024 03:00:45 +0200 with message-id and subject line fixed has caused the Debian Bug report #1074763, regarding CVE-2024-32498: Arbitrary file access through custom QCOW2 external data to be marked as done. This means that you claim that the problem has been dealt

Bug#1074729: golang-github-safchain-ethtool: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/safchain/ethtool github.com/safchain/ethtool/example returned ex

I wrote: the noshare backend. Sorry, just to avoid confusion: the correct name is the unshare backend. Thanks.

Processed: Re: golang-github-safchain-ethtool: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/safchain/ethtool github.com/safchain/ethtool/example returned

Processing commands for cont...@bugs.debian.org: > reopen 1074729 Bug #1074729 {Done: Sascha Steinbiss } [src:golang-github-safchain-ethtool] golang-github-safchain-ethtool: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/safchain/ethtool github.com/sa

Bug#1074729: golang-github-safchain-ethtool: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/safchain/ethtool github.com/safchain/ethtool/example returned ex

reopen 1074729 thanks Sascha Steinbiss wrote: This should have been taken care of with the latest upload (0.4.1-1). There are still failing tests. See this for example: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-safchain-ethtool.html Quote: === RUN Te

Bug#1076737: marked as done (ModuleNotFoundError: No module named 'dateutil')

Your message dated Tue, 23 Jul 2024 00:52:01 +0100 with message-id and subject line Re: Bug#1076737: Sorry, not a bug... has caused the Debian Bug report #1076737, regarding ModuleNotFoundError: No module named 'dateutil' to be marked as done. This means that you claim that the problem has been d

Processed: bug 1076751 is forwarded to https://ikiwiki-hosting.branchable.com/bugs/git-daemon_will_not_export_source.git_with_git_2.45/

Processing commands for cont...@bugs.debian.org: > forwarded 1076751 > https://ikiwiki-hosting.branchable.com/bugs/git-daemon_will_not_export_source.git_with_git_2.45/ Bug #1076751 [src:ikiwiki-hosting] ikiwiki-hosting: autopkgtest regression with git 2.45.2: dubious ownership in repository at

Bug#1076751: ikiwiki-hosting: autopkgtest regression with git 2.45.2: dubious ownership in repository at '/var/lib/ikiwiki-hosting-web/git/foo.example.com.git'

Source: ikiwiki-hosting Version: 0.20220716-2 Severity: serious Tags: upstream trixie sid Justification: https://release.debian.org/testing/rc_policy.txt §6a X-Debbugs-Cc: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update As reported (eventually) in

Processed: git-daemon: No longer allows exporting git repos owned by a different user

Processing control commands: > block 1074064 by -1 Bug #1074064 {Done: Paul Gevers } [src:git] src:git: fails to migrate to testing for too long: triggers autopkgtest issues 1074064 was not blocked by any bugs. 1074064 was not blocking any bugs. Added blocking bug(s) of 1074064: 1076750 -- 1074

Bug#1076737: Sorry, not a bug...

Oops, false alarm -- it was just me being stupid and mixing up system and venv packages... I suggest to just close this issue. Sorry for any inconvenience -- tcrass OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1076747: AttributeError: partially initialized module 'threading' has no attribute 'RLock'

Package: mercurial Version: 6.8-1 Severity: grave Dear Maintainer, Running mercurial (simply running `hg`) on trixie fails with: ``` Traceback (most recent call last): File "/usr/bin/hg", line 57, in from mercurial import dispatch File "", line 1360, in _find_and_load File "", line 13

Bug#1076742: sphinxsearch: FTBFS with abseil 20230802: -std=c++11 unsupported

Source: sphinxsearch Version: 2.8.2-1 Severity: serious sphinxsearch/experimental cannot be built with abseil 20230802 (sphinxsearch/sid is not affected): /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported." but sphinxsearch builds with -s

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

On Fri, 19 Jul 2024 18:11:18 +0200 Diederik de Haas wrote: Control: affects -1 firmware-nvidia-graphics On Friday, 19 July 2024 17:56:30 CEST Chris Hofstaedtler wrote: > Control: retitle -1 initramfs-tools: duplicates nvidia firmware files > > On Fri, Jul 19, 2024 at 04:43:47PM +0200, Diederik

Bug#1076737: ModuleNotFoundError: No module named 'dateutil'

Package: python3-dateutil Version: 2.9.0-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: m...@tcrass.de Dear Maintainer, * What led up to the situation? apt update && apt upgrade * What exactly did you do (or not do) that was effective (or ineffective

Bug#1074384: marked as done (slurm-wlm-basic-plugins, depends on 64-bit only library)

Your message dated Mon, 22 Jul 2024 20:10:50 + with message-id and subject line Bug#1074384: fixed in slurm-wlm 24.05.1-1 has caused the Debian Bug report #1074384, regarding slurm-wlm-basic-plugins, depends on 64-bit only library to be marked as done. This means that you claim that the probl

Processed: Bug#1052101 marked as pending in gnome-shell-extension-hamster

Processing control commands: > tag -1 pending Bug #1052101 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: needs update for GNOME Shell 46 Ignoring request to alter tags of bug #1052101 to the same tags previously set -- 1052101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Bug#1052101: marked as pending in gnome-shell-extension-hamster

Control: tag -1 pending Hello, Bug #1052101 in gnome-shell-extension-hamster 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/projecthamster-team/gnome-shell-ex

Bug#1052101: marked as pending in gnome-shell-extension-hamster

Control: tag -1 pending Hello, Bug #1052101 in gnome-shell-extension-hamster 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/projecthamster-team/gnome-shell-ex

Processed: Bug#1052101 marked as pending in gnome-shell-extension-hamster

Processing control commands: > tag -1 pending Bug #1052101 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: needs update for GNOME Shell 46 Ignoring request to alter tags of bug #1052101 to the same tags previously set -- 1052101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Processed: Bug#1052101 marked as pending in gnome-shell-extension-hamster

Processing control commands: > tag -1 pending Bug #1052101 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: needs update for GNOME Shell 46 Ignoring request to alter tags of bug #1052101 to the same tags previously set -- 1052101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Bug#1052101: marked as pending in gnome-shell-extension-hamster

Control: tag -1 pending Hello, Bug #1052101 in gnome-shell-extension-hamster 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/projecthamster-team/gnome-shell-ex

Processed: src:neutron: fails to migrate to testing for too long: uploader built arch:all binaries

Processing control commands: > close -1 2:24.0.0-3 Bug #1076734 [src:neutron] src:neutron: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions neutron/2:24.0.0-3. Bug #1076734 [src:neutron] src:neutron: fails to migrate to testing for too long:

Bug#1076734: src:neutron: fails to migrate to testing for too long: uploader built arch:all binaries

Source: neutron Version: 2:24.0.0-2 Severity: serious Control: close -1 2:24.0.0-3 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than

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

Source: safeeyes Version: 2.1.5-0.1 Severity: serious Control: close -1 2.1.9-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30

Processed: src:safeeyes: fails to migrate to testing for too long: uploader built arch:all binary

Processing control commands: > close -1 2.1.9-1 Bug #1076733 [src:safeeyes] src:safeeyes: fails to migrate to testing for too long: uploader built arch:all binary Marked as fixed in versions safeeyes/2.1.9-1. Bug #1076733 [src:safeeyes] src:safeeyes: fails to migrate to testing for too long: upl

Processed: src:ispc: fails to migrate to testing for too long: installability issue on armhf

Processing control commands: > close -1 1.24.0-1 Bug #1076732 [src:ispc] src:ispc: fails to migrate to testing for too long: installability issue on armhf Marked as fixed in versions ispc/1.24.0-1. Bug #1076732 [src:ispc] src:ispc: fails to migrate to testing for too long: installability issue o

Bug#1076732: src:ispc: fails to migrate to testing for too long: installability issue on armhf

Source: ispc Version: 1.23.0-1 Severity: serious Control: close -1 1.24.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as havi

Bug#1076730: dart: autopkgtest regression with CMake 3.30+

Source: dart Version: 6.12.1+dfsg4-13.1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package has a autopkgtest regression with CMake 3.30, due to a new policy regarding the deprecation of the built-in find_package Boost module in favor of upstream's B

Processed: src:gffread: fails to migrate to testing for too long: autopkgtest regression on s390x

Processing control commands: > close -1 0.12.7-6 Bug #1076731 [src:gffread] src:gffread: fails to migrate to testing for too long: autopkgtest regression on s390x Marked as fixed in versions gffread/0.12.7-6. Bug #1076731 [src:gffread] src:gffread: fails to migrate to testing for too long: autop

Bug#1076731: src:gffread: fails to migrate to testing for too long: autopkgtest regression on s390x

Source: gffread Version: 0.12.7-4 Severity: serious Control: close -1 0.12.7-6 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as h

Bug#1073205: docker-compose: new python3-requests dependency brokes docker-compose

On Mon Jul 22 2024 10:59:51 GMT-0700 (Pacific Daylight Time), Philip Chung wrote: Attached is a patch for compatibility with version 7 of the python-docker/docker-py library. It removes the SSL version handling and --skip-hostname-check option, which are no longer supported in docker-py since 7

Processed: Re: docker-compose: new python3-requests dependency brokes docker-compose

Processing control commands: > tags -1 + patch Bug #1073205 [docker-compose] docker-compose: new python3-requests dependency brokes docker-compose Added tag(s) patch. -- 1073205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073205 Debian Bug Tracking System Contact ow...@bugs.debian.org w

Bug#1073205: docker-compose: new python3-requests dependency brokes docker-compose

Control: tags -1 + patch On Wed, 3 Jul 2024 10:16:00 -0300 Ernesto Domato wrote: Yesterday, an update to version 7.1.0-1 of the same library broke again the package that now when you try to run any command, it throws this error: Traceback (most recent call last): File "/usr/bin/docker-compo

Bug#1069425: uid-wrapper: FTBFS on armhf: 15: [ LINE ] --- ./tests/test_syscall.c:53: error: Failure!

On Sun, 21 Jul 2024 23:00:48 +0200 Drew Parsons wrote: Just to be clear, I'm not supporting dropping armv7 support. It's only one test that's failing. Skipping the one test (on 32-bit arm) is all that's needed. It's passing the other tests. Yes, that's what I mean. But a failing test indic

Bug#1074112: marked as done ([arm64] boot stops at 'Starting kernel ...' without any further output when kernel built with recent binutils)

Your message dated Mon, 22 Jul 2024 18:16:04 +0200 with message-id <3762619.0MlLrn18Ui@bagend> and subject line Re: Bug#1074111: [arm64] boot stops at 'Starting kernel ...' without any further output when kernel built with recent binutils has caused the Debian Bug report #1074112, regarding [arm64

Bug#1076699: jpeg-xl: 0.10.3 failing autopkgtests

I have successfully rebuilt all the reverse dependencies for the jpeg-xl 0.10 transition on Ubuntu 24.10 on amd64 and am confident they would successfully build in Debian Unstable too. https://launchpad.net/~jbicha/+archive/ubuntu/arch/+packages?field.series_filter=oracular Thank you, Jeremy Bích

Bug#1066313: torsocks upstream fix

On 2024-07-18 14:29:54, Clément Hermann wrote: > Hi Micah, > > > > > > Le 11 juillet 2024 13:06:48 UTC, micah anderson a écrit : >> >>Hello, >> >>In April you had said that you were going to try and upload a new >>version of torsocks, which fixes the FTBFS, but you were trying to fix a >>few linti

Bug#1074680: marked as done (osc: FTBFS: ModuleNotFoundError: No module named 'imp')

Your message dated Mon, 22 Jul 2024 15:21:43 + with message-id and subject line Bug#1074680: fixed in osc 1.7.0-4 has caused the Debian Bug report #1074680, regarding osc: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you claim that the problem has be

Processed: correct 1076493 metadata, merge bugs 1076449 and 1076493

Processing commands for cont...@bugs.debian.org: > severity 1076493 grave Bug #1076493 [python3.12] python3.12: latest update breaks mercurial. Severity set to 'grave' from 'normal' > notfound 1076493 3.12.4-1 Bug #1076493 [python3.12] python3.12: latest update breaks mercurial. No longer marked a

Bug#1076449: mercurial: does not start anymore with python 3.12.4-3, hgdemandimport problem

On Tue, Jul 16, 2024 at 11:12:12 -0400, Daniel Serpell wrote: > Package: mercurial > Version: 6.8-1 > Severity: grave > Justification: renders package unusable > > Dear maintainer, > > In current sid, with python 3.12.4-3, mercurial fails at load with: > > ~$ hg > Traceback (most recent call

Processed: Re: Bug#1076449: python3.12 threading breakage?

Processing control commands: > reassign -1 python3.12 3.12.4-3 Bug #1076449 [mercurial] mercurial: does not start anymore with python 3.12.4-3, hgdemandimport problem Bug reassigned from package 'mercurial' to 'python3.12'. No longer marked as found in versions mercurial/6.8-1. Ignoring request t

Bug#1076449: python3.12 threading breakage?

Control: reassign -1 python3.12 3.12.4-3 On Mon, Jul 22, 2024 at 13:32:28 +0200, Vincent Lefevre wrote: > On 2024-07-22 17:58:01 +0700, Sam wrote: > > So, I have now two machines where this bug happens, but on a third one > > (my notebook) there seems to be no problem, despite all of them showing

Bug#1076449: Might be a different cause

On 2024-07-22 17:58:01 +0700, Sam wrote: > So, I have now two machines where this bug happens, but on a third one > (my notebook) there seems to be no problem, despite all of them showing > 6.8-1 as the installed version (via `dpkg --list | grep mercurial`). > > Any recommendations how to make a d

Bug#1076449: Workaround, for now

Follow up: As a work-around, the following seems to get things to work again (not tested in-depth though): Change line /usr/lib/python3/dist-packages/hgdemandimport/demandimportpy3.py:32 from _deactivated = True to _deactivated = False This allows at least to hg command to be calle

Bug#1076449: Might be a different cause

So, I have now two machines where this bug happens, but on a third one (my notebook) there seems to be no problem, despite all of them showing 6.8-1 as the installed version (via `dpkg --list | grep mercurial`). Any recommendations how to make a differential-diagnosis between two systems? I think

Bug#1071053: marked as done (python3-pynpoint: uninstallable in sid: Depends: python3-h5py (< 3.10) but 3.10.0-1 is to be installed)

Your message dated Mon, 22 Jul 2024 10:35:09 + with message-id and subject line Bug#1071053: fixed in pynpoint 0.11.0-3 has caused the Debian Bug report #1071053, regarding python3-pynpoint: uninstallable in sid: Depends: python3-h5py (< 3.10) but 3.10.0-1 is to be installed to be marked as d

Processed: Re: Bug#1074727: ikiwiki: FTBFS: t/po.t: msgfmt: input file doesn't contain a header entry with a charset specification

Processing control commands: > tag -1 + patch Bug #1074727 [src:ikiwiki] ikiwiki: FTBFS: t/po.t: msgfmt: input file doesn't contain a header entry with a charset specification Added tag(s) patch. -- 1074727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074727 Debian Bug Tracking System Co

Bug#1074727: ikiwiki: FTBFS: t/po.t: msgfmt: input file doesn't contain a header entry with a charset specification

Control: tag -1 + patch Hi, Jonathan Dowland (2024-07-21): > I believe the issue is a po file generated and written out by t/po.t > (missing a content-type header). It looks like it indeed! The attached Git patch (against current upstream master branch) fixes the test failure when I run the tes

Bug#1076449: mercurial: does not start anymore with python 3.12.4-3, hgdemandimport problem

On 2024-07-16 11:12:12 -0400, Daniel Serpell wrote: > In current sid, with python 3.12.4-3, mercurial fails at load with: > > ~$ hg > Traceback (most recent call last): >File "/usr/bin/hg", line 57, in > from mercurial import dispatch >File "", line 1360, in _find_and_load >Fi

Bug#1076203: marked as done (coot: Please drop dependencies on python3-distutils)

Your message dated Mon, 22 Jul 2024 08:36:51 + with message-id and subject line Bug#1076203: fixed in coot 1.1.09+dfsg-2 has caused the Debian Bug report #1076203, regarding coot: Please drop dependencies on python3-distutils to be marked as done. This means that you claim that the problem ha

Bug#1075798: marked as done (tifffile: Failing autopkgtest on s390x)

Your message dated Mon, 22 Jul 2024 08:37:48 + with message-id and subject line Bug#1075798: fixed in tifffile 20240721-1 has caused the Debian Bug report #1075798, regarding tifffile: Failing autopkgtest on s390x to be marked as done. This means that you claim that the problem has been dealt