Processed: severity of 1070217 is serious

2024-05-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1070217 serious Bug #1070217 [snappy] chromium: Symbol lookup error with libsnappy1v5>=1.2.0 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1070217:

Bug#1070188: python3-spyder: uninstallable in unstable due to pylint

2024-05-01 Thread Julian Gilbey
On Wed, May 01, 2024 at 03:04:56PM +0200, Roland Mas wrote: > Package: python3-spyder > Version: 5.5.1+ds-1 > Severity: important > > Dear Maintainer, > > python3-spyder is no longer installable in sid; it depends (and > build-depends) on pylint (< 3.1~) but pylint is currently 3.1.0-1 in >

Bug#1058419: marked as done (pyannotate: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Thu, 02 May 2024 04:00:31 + with message-id and subject line Bug#1065045: Removed package(s) from unstable has caused the Debian Bug report #1058419, regarding pyannotate: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned

Bug#1058237: marked as done (python-boto: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-05-01 Thread Debian Bug Tracking System
Your message dated Thu, 02 May 2024 04:00:02 + with message-id and subject line Bug#1058652: Removed package(s) from unstable has caused the Debian Bug report #1058237, regarding python-boto: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you claim

Bug#1060963: paramiko: FTBFS: dh_auto_test: error: pybuild

2024-05-01 Thread Alexandre Detiste
> E ModuleNotFoundError: No module named 'six' This happens because we unknot the python3-mock -> python3-pbr -> python3-six dependency chain. I did this _on purpose_ to discover missing python3-six (build-)dependencies and/or upstream that needs a cleanup. Here it's of course better to do

Bug#1069191: glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix^J out-of-bound writes when writing escape sequence

2024-05-01 Thread Miguel Jacq
On Mon, 22 Apr 2024 09:31:39 +0200 Charlemagne Lasse wrote: > Hi, > > Can this be backported to older Debian versions via the security repo? > This bug can be used to execute code when using the PHP engine: > > * https://www.offensivecon.org/speakers/2024/charles-fol.html > *

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

2024-05-01 Thread Shmerl
On Mon, 26 Feb 2024 19:53:49 +0100 Fabio Pedretti wrote: > Ubuntu fixed it with this patch: > https://launchpadlibrarian.net/715235929/meson_1.3.2-1_1.3.2-1ubuntu1.diff.gz > Can this fix be added to Debian? Meson has been stuck without moving to testing for a very long time and now it seems to

Processed: openttd: cmake licensing concern for openttd 14.0 source package

2024-05-01 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/OpenTTD/OpenTTD/pull/12603 Bug #1070208 [src:openttd] openttd: cmake licensing concern for openttd 14.0 source package Set Bug forwarded-to-address to 'https://github.com/OpenTTD/OpenTTD/pull/12603'. -- 1070208:

Bug#1070208: openttd: cmake licensing concern for openttd 14.0 source package

2024-05-01 Thread James Addison
Source: openttd Version: 14.0-1 Severity: serious Tags: upstream Justification: Policy 12.5 Control: forwarded -1 https://github.com/OpenTTD/OpenTTD/pull/12603 Dear Maintainer, The build scripts for the initial version 14.0 release of OpenTTD include a CMake file that determines whether and how

Bug#1070015: marked as done (haskel-pandoc: FTBFS on armel: Couldn't match expected type: WriterState -> m a)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 21:20:13 + with message-id and subject line Bug#1070015: fixed in haskell-pandoc 3.1.3-2 has caused the Debian Bug report #1070015, regarding haskel-pandoc: FTBFS on armel: Couldn't match expected type: WriterState -> m a to be marked as done. This means

Processed: found 1069357 in 0.14.3+ds-1

2024-05-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1069357 0.14.3+ds-1 Bug #1069357 [src:cpp-httplib] cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3

Processed: found 1069552 in 1.0.21-13.1

2024-05-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1069552 1.0.21-13.1 Bug #1069552 [src:freecontact] freecontact: FTBFS on armel: make[1]: *** [Makefile:469: all-recursive] Error 1 Ignoring request to alter found versions of bug #1069552 to the same values previously set > thanks

Bug#1070015: haskel-pandoc: FTBFS on armel: Couldn't match expected type: WriterState -> m a

2024-05-01 Thread Ilias Tsitsimpis
On Sun, Apr 28, 2024 at 05:14PM, Sebastian Ramacher wrote: > https://buildd.debian.org/status/fetch.php?pkg=haskell-pandoc=armel=3.1.3-1%2Bb1=1713911741=0 I have been trying to understand what is wrong, but haven't found anything. My best guess right now is that this is a GHC bug that manifests

Bug#1070201: scikit-learn: autopkgtest regression on i386 with NumPy 1.26

2024-05-01 Thread Graham Inggs
Source: scikit-learn Version: 1.4.1.post1+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer scikit-learn's autopkgtest regresses on i386 when tested with numpy 1.26 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham

Bug#1070062: marked as done (waylandpp: Missing build-depends libwayland-egl1-mesa)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 17:56:11 + with message-id and subject line Bug#1070062: fixed in waylandpp 1.0.0-6 has caused the Debian Bug report #1070062, regarding waylandpp: Missing build-depends libwayland-egl1-mesa to be marked as done. This means that you claim that the problem

Bug#1069557: libkdumpfile: FTBFS on armel: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2

2024-05-01 Thread Michel Lind
Hi Lucas, On 4/20/24 8:23 AM, Lucas Nussbaum wrote: Source: libkdumpfile Version: 0.5.4-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel Hi, During a rebuild of all packages in sid, your package failed

Bug#1067315: marked as done (matplotlib: FTBFS: unsatisfiable build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 8.1.1-2 is to be installed)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 15:19:24 + with message-id and subject line Bug#1067311: fixed in ipywidgets 8.1.2-1 has caused the Debian Bug report #1067311, regarding matplotlib: FTBFS: unsatisfiable build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 8.1.1-2 is

Bug#1067311: marked as done (ipywidgets: FTBFS: unsatisfiable build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 8.1.1-2 is to be installed)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 15:19:24 + with message-id and subject line Bug#1067311: fixed in ipywidgets 8.1.2-1 has caused the Debian Bug report #1067311, regarding ipywidgets: FTBFS: unsatisfiable build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 8.1.1-2 is

Bug#1066551: marked as done (ramond: FTBFS: src/main.c:164:17: error: implicit declaration of function ‘LOG’ [-Werror=implicit-function-declaration])

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 14:58:50 + with message-id and subject line Bug#1066551: fixed in ramond 0.5-5 has caused the Debian Bug report #1066551, regarding ramond: FTBFS: src/main.c:164:17: error: implicit declaration of function ‘LOG’ [-Werror=implicit-function-declaration] to

Bug#1069413: marked as done (rust-coreutils: FTBFS on arm64: make[2]: *** [GNUmakefile:289: test] Error 101)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 13:37:36 + with message-id and subject line Bug#1069413: fixed in rust-coreutils 0.0.26-1 has caused the Debian Bug report #1069413, regarding rust-coreutils: FTBFS on arm64: make[2]: *** [GNUmakefile:289: test] Error 101 to be marked as done. This means

Bug#1067897: marked as done (rust-coreutils - FTBFS with new rust-uutils-term-grid.)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 13:37:36 + with message-id and subject line Bug#1067897: fixed in rust-coreutils 0.0.26-1 has caused the Debian Bug report #1067897, regarding rust-coreutils - FTBFS with new rust-uutils-term-grid. to be marked as done. This means that you claim that the

Processed: Re: [Pkg-rust-maintainers] Bug#1019042: rust-qwertone: FTBFS - dep issue

2024-05-01 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1019042 [src:qwertone] rust-qwertone: FTBFS - dep issue Severity set to 'serious' from 'important' -- 1019042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: severity of 1070188 is serious

2024-05-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1070188 serious Bug #1070188 [python3-spyder] python3-spyder: uninstallable in unstable due to pylint Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1070188:

Bug#1070186: python3-datalad: Don't recommend python3-boto

2024-05-01 Thread Jeremy Bícha
Package: python3-datalad Version: 0.19.6-2 Severity: serious Debian Policy § 2.2 says that packages in main (like python3-datalad) are not allowed to have Recommends on packages that are not in main (unless it is only a non-default alternative for a package in main). python3-datalad Recommends:

Bug#1070184: gnome-maps: Unable to start gnome-maps

2024-05-01 Thread Enrique Garcia
Package: gnome-maps Version: 46.0-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: cqu...@arcor.de I have recently upgraded my Debian testing and it comes with gnome-46.0-1. I am using XFCE 4 desktop and when I try to start gnome-maps nothing happens. From the command line

Bug#947039: marked as done (libapache2-mod-auth-pgsql: AuthType Basic configured without corresponding module)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 12:17:44 + with message-id and subject line Bug#1070165: Removed package(s) from unstable has caused the Debian Bug report #947039, regarding libapache2-mod-auth-pgsql: AuthType Basic configured without corresponding module to be marked as done. This

Bug#1061694: marked as done (gnome-video-arcade: Please stop using libsoup2.4)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 12:17:15 + with message-id and subject line Bug#1070156: Removed package(s) from unstable has caused the Debian Bug report #1061694, regarding gnome-video-arcade: Please stop using libsoup2.4 to be marked as done. This means that you claim that the problem

Bug#1061696: marked as done (gnome-video-arcade: Remove unmaintained package?)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 12:17:15 + with message-id and subject line Bug#1070156: Removed package(s) from unstable has caused the Debian Bug report #1061696, regarding gnome-video-arcade: Remove unmaintained package? to be marked as done. This means that you claim that the problem

Bug#1064375: marked as done (rust-gtk: Unmaintained library should not be included in Trixie)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 12:13:02 + with message-id and subject line Bug#1070092: Removed package(s) from unstable has caused the Debian Bug report #1064375, regarding rust-gtk: Unmaintained library should not be included in Trixie to be marked as done. This means that you claim

Bug#1066616: marked as done (moonshot-ui: FTBFS: src/moonshot-futils.c:41:34: error: implicit declaration of function ‘getuid’; did you mean ‘getpwuid’? [-Werror=implicit-function-declaration])

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 12:09:52 + with message-id and subject line Bug#1070072: Removed package(s) from unstable has caused the Debian Bug report #1066616, regarding moonshot-ui: FTBFS: src/moonshot-futils.c:41:34: error: implicit declaration of function ‘getuid’; did you mean

Bug#1068923: marked as done (heat-cfntools: Remove from Debian?)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 12:07:31 + with message-id and subject line Bug#1070045: Removed package(s) from unstable has caused the Debian Bug report #1068923, regarding heat-cfntools: Remove from Debian? to be marked as done. This means that you claim that the problem has been

Bug#1069614: marked as done (erfs: no longer functional, should be removed)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 12:07:03 + with message-id and subject line Bug#1070030: Removed package(s) from unstable has caused the Debian Bug report #1069614, regarding erfs: no longer functional, should be removed to be marked as done. This means that you claim that the problem

Bug#1022392: marked as done (python-ospurge: FTBFS: AttributeError: Mock object has no attribute 'detach_policy_from_cluster')

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 12:08:27 + with message-id and subject line Bug#1070061: Removed package(s) from unstable has caused the Debian Bug report #1022392, regarding python-ospurge: FTBFS: AttributeError: Mock object has no attribute 'detach_policy_from_cluster' to be marked as

Bug#1058242: marked as done (heat-cfntools: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 12:07:31 + with message-id and subject line Bug#1070045: Removed package(s) from unstable has caused the Debian Bug report #1058242, regarding heat-cfntools: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you claim

Bug#1021924: marked as done (networking-mlnx: FTBFS test failures: sqlalchemy.exc.InvalidRequestError: A transaction is already begun on this Session.)

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 12:08:00 + with message-id and subject line Bug#1070060: Removed package(s) from unstable has caused the Debian Bug report #1021924, regarding networking-mlnx: FTBFS test failures: sqlalchemy.exc.InvalidRequestError: A transaction is already begun on this

Processed: forward 1069843

2024-05-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1069843 https://github.com/zarr-developers/zarr-python/issues/1819 Bug #1069843 [src:zarr] zarr: FTBFS: failing tests Set Bug forwarded-to-address to 'https://github.com/zarr-developers/zarr-python/issues/1819'. > thanks Stopping

Bug#1070172: Exception when invoked without options

2024-05-01 Thread Guido Günther
Package: gcovr Version: 7.2-1 Severity: grave Hi, invoking gcovr 7.2 in an empty directory fails like $ gcovr -- GCC Code Coverage Report Traceback (most recent call last): File

Bug#1066703: marked as done (rxtx: FTBFS: SerialImp.c:5453:23: error: implicit declaration of function ‘major’ [-Werror=implicit-function-declaration])

2024-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2024 10:20:30 + with message-id and subject line Bug#1066703: fixed in rxtx 2.2.0+dfsg-3 has caused the Debian Bug report #1066703, regarding rxtx: FTBFS: SerialImp.c:5453:23: error: implicit declaration of function ‘major’

Processed: Bug#1066703 marked as pending in rxtx

2024-05-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1066703 [src:rxtx] rxtx: FTBFS: SerialImp.c:5453:23: error: implicit declaration of function ‘major’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066703 Debian Bug

Bug#1066703: marked as pending in rxtx

2024-05-01 Thread Emmanuel Bourg
Control: tag -1 pending Hello, Bug #1066703 in rxtx 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:

Processed: reassign 1070102 to src:llvm-toolchain-14, reassign 1055324 to src:libdmapsharing ...

2024-05-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1070102 src:llvm-toolchain-14 1:14.0.6-12 Bug #1070102 [src:llm-toolchain-14] Requesting patch for llvm-toolchain-14 Warning: Unknown package 'src:llm-toolchain-14' Bug reassigned from package 'src:llm-toolchain-14' to

Bug#1069945: Acknowledgement (rapiddisk-dkms: module fails to build for Linux 6.7.12, 6.1.85: rapiddisk-cache.c:198:16: error: too few arguments to function 'dm_io')

2024-05-01 Thread Andreas Beckmann
On 29/04/2024 09.59, Andreas Beckmann wrote: A possible solution (which also handles all kernels that got the patch Merged in dm-writeboost as https://github.com/akiradeveloper/dm-writeboost/commit/1967beb97d63044043383721759c8928bc6353c6 Andreas