Bug#1076418: FTBFS: undeclared type `TestClient`

Source: rust-axum Version: 0.6.20-21 Severity: serious Tags: ftbfs Justification: FTBFS Seem the buildds are having trouble building this package: error[E0433]: failed to resolve: use of undeclared type `TestClient` --> axum/src/routing/tests/mod.rs:1039:18 | 1039 | let client = Test

Processed: wfuzz: FTBFS with Python 3.12 as default

Processing control commands: > tag -1 + pending Bug #1067598 [src:wfuzz] wfuzz: FTBFS with Python 3.12 as default Added tag(s) pending. -- 1067598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1067598: wfuzz: FTBFS with Python 3.12 as default

Control: tag -1 + pending Hi, I've just applied your patch to fix also [0], I made a NMU in DELAYED/2-days. [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066009 -- cheers, Emmanuel Arias ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ eam...@debian.org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5

Processed: wfuzz: Please drop dependencies on python3-distutils

Processing control commands: > tag -1 + pending Bug #1066009 [src:wfuzz] wfuzz: Please drop dependencies on python3-distutils Added tag(s) pending. > tag -1 + patch Bug #1066009 [src:wfuzz] wfuzz: Please drop dependencies on python3-distutils Added tag(s) patch. -- 1066009: https://bugs.debian.o

Bug#1066009: wfuzz: Please drop dependencies on python3-distutils

Control: tag -1 + pending Control: tag -1 + patch Dear maintainer, I've prepared an NMU for tulip (versioned as 3.1.0-4.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. I attach the patch that I applied. This is the same as proposed in [0]. I made some te

Processed: Bug#1075849 marked as pending in websockify

Processing control commands: > tag -1 pending Bug #1075849 [src:websockify] websockify: FTBFS with systemd (>= 256~rc3-3) due to fileno limit bump Added tag(s) pending. -- 1075849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075849 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1075849: marked as pending in websockify

Control: tag -1 pending Hello, Bug #1075849 in websockify 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/openstack-team/python/websockify/-/commit/c87fbffa637a

Bug#1065989: tulip: Please drop dependencies on python3-distutils

Control: tags 1065989 + patch Control: tags 1065989 + pending Dear maintainer, I've prepared an NMU for tulip (versioned as 5.4.0+dfsg-3.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- cheers, Emmanuel Arias ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ea

Processed: tulip: Please drop dependencies on python3-distutils

Processing control commands: > tags 1065989 + patch Bug #1065989 [src:tulip] tulip: Please drop dependencies on python3-distutils Added tag(s) patch. > tags 1065989 + pending Bug #1065989 [src:tulip] tulip: Please drop dependencies on python3-distutils Added tag(s) pending. -- 1065989: https://b

Bug#1076319: marked as done (python-pyproject-hooks autopkg tests fail with setuptools 70)

Your message dated Mon, 15 Jul 2024 23:36:55 + with message-id and subject line Bug#1076319: fixed in python-pyproject-hooks 1.1.0-2 has caused the Debian Bug report #1076319, regarding python-pyproject-hooks autopkg tests fail with setuptools 70 to be marked as done. This means that you clai

Processed: Re: kpatch: please switch to B-D: dh-sequence-dkms (or dh-dkms)

Processing control commands: > tag -1 + pending Bug #1027889 [src:kpatch] kpatch FTBFS: please switch to B-D: dh-sequence-dkms (or dh-dkms) Added tag(s) pending. -- 1027889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027889 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#1027889: kpatch: please switch to B-D: dh-sequence-dkms (or dh-dkms)

Control: tag -1 + pending On Wed, 04 Jan 2023 11:52:18 +0100 Andreas Beckmann wrote: > Source: kpatch > Version: 0.6.0-0.2 > Severity: serious > Tags: sid bookworm experimental > > Hi, > > please switch the Build-Depends of your package from `dkms` to `dh-dkms` > or (preferrably) `dh-sequence-d

Processed: Re: kpatch-dkms: fails to build module for Linux 4.19.0-17 or newer: find_symbol is no longer exported by the kernel

Processing control commands: > severity -1 important Bug #991003 [kpatch-dkms] kpatch-dkms: fails to build module for Linux 4.19.0-17 or newer: find_symbol is no longer exported by the kernel Severity set to 'important' from 'serious' -- 991003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Bug#991003: kpatch-dkms: fails to build module for Linux 4.19.0-17 or newer: find_symbol is no longer exported by the kernel

Control: severity -1 important On Mon, 12 Jul 2021 19:24:56 +0200 Andreas Beckmann wrote: > Package: kpatch-dkms > Version: 0.6.0-0.2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > kpatch-dkms fails to build a module for the latest kernel in stable. > > For more

Bug#1076381: marked as done (librav1e0.7: trying to overwrite librav1e.so.0.7.1', which is also in package librav1e0:amd64 0.7.1-2)

Your message dated Mon, 15 Jul 2024 22:27:51 + with message-id and subject line Bug#1076381: fixed in rust-rav1e 0.7.1-4 has caused the Debian Bug report #1076381, regarding librav1e0.7: trying to overwrite librav1e.so.0.7.1', which is also in package librav1e0:amd64 0.7.1-2 to be marked as d

Bug#1076408: rust-fs4: Failing autopkgtests

Source: rust-fs4 Version: 0.8.4-3 Severity: serious X-Debbugs-CC: werdah...@riseup.net rust-fs4's autopkgtests are failing. This is preventing migration to Testing. https://qa.debian.org/excuses.php?package=rust-fs4 test excerpt = error[E0433]: failed to resolve: use of undeclared crate

Bug#1076407: rust-oo7: autopkgtest regression

Source: rust-oo7 Version: 0.3.3-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-oo7/48952368/log.gz ... 147s error: You can't enable both async-std & tokio features at once 147s --> src/lib.rs:5:1 147s | 147s 5 | compile_error!("You can't enable both async-std &

Processed: mark as fixed

Processing commands for cont...@bugs.debian.org: > fixed 1072132 sphinx-bootstrap-theme/0.8.1-5 Bug #1072132 {Done: Sergio Durigan Junior } [sphinx-bootstrap-theme] behave: FTBFS: dh_sphinxdoc: error: debian/python-behave-doc/usr/share/doc/python-behave-doc/html/_static/js/jquery-1.12.4.min.js

Processed: reassign

Processing commands for cont...@bugs.debian.org: > reassign 1072132 sphinx-bootstrap-theme Bug #1072132 {Done: Sergio Durigan Junior } [src:behave] behave: FTBFS: dh_sphinxdoc: error: debian/python-behave-doc/usr/share/doc/python-behave-doc/html/_static/js/jquery-1.12.4.min.js is missing Bug re

Bug#1072133: metakernel: FTBFS: dh_sphinxdoc: error: debian/python-metakernel-doc/usr/share/doc/python3-metakernel/html/_static/js/jquery-1.12.4.min.js is missing

On Sunday, July 14 2024, Santiago Vila wrote: >> Therefore, I am closing this bug and marking it as fixed in version >> 0.8.5-1. > > Ok, one more thing: > > Between 202405 and 202406 I reported a few similar bugs. Could you please > check the following packages? (and reassign + affects + merge + e

Bug#1072132: marked as done (behave: FTBFS: dh_sphinxdoc: error: debian/python-behave-doc/usr/share/doc/python-behave-doc/html/_static/js/jquery-1.12.4.min.js is missing)

Your message dated Mon, 15 Jul 2024 15:14:15 -0400 with message-id <875xt6cvso@debian.org> and subject line Close bugs related to sphinx-bootstrap-theme issue has caused the Debian Bug report #1072132, regarding behave: FTBFS: dh_sphinxdoc: error: debian/python-behave-doc/usr/share/doc/python-

Bug#1072138: marked as done (python-peachpy: FTBFS: dh_sphinxdoc: error: debian/python-peachpy-doc/usr/share/doc/python3-peachpy/html/_static/bootstrap-3.4.1/js/bootstrap.min.js is missing)

Your message dated Mon, 15 Jul 2024 15:14:15 -0400 with message-id <875xt6cvso@debian.org> and subject line Close bugs related to sphinx-bootstrap-theme issue has caused the Debian Bug report #1072138, regarding python-peachpy: FTBFS: dh_sphinxdoc: error: debian/python-peachpy-doc/usr/share/do

Processed (with 3 errors): Close bugs related to sphinx-bootstrap-theme issue

Processing commands for cont...@bugs.debian.org: > reassign 1072132 sphinx-bootstrap-theme/0.8.1-4 Unknown command or malformed arguments to command. > reassign 1072136 sphinx-bootstrap-theme/0.8.1-4 Unknown command or malformed arguments to command. > reassign 1072138 sphinx-bootstrap-theme/0.8.1

Bug#1071888: marked as done (rust-gvdb-macros: FTBFS: unsatisfiable build-dependencies)

Your message dated Mon, 15 Jul 2024 19:36:56 +0200 with message-id <8d2121b6-5868-44a7-ba34-7f5b0a77b...@riseup.net> and subject line has caused the Debian Bug report #1071888, regarding rust-gvdb-macros: FTBFS: unsatisfiable build-dependencies to be marked as done. This means that you claim that

Bug#1076374: libplayeronecamera2t64: ineffective replaces for /usr/lib/udev/rules.d/99-player_one_astronomy.rules causes file loss

Thorsten, Helmut, On Mon, Jul 15, 2024 at 01:09:09PM +0200, Helmut Grohne wrote: > Package: libplayeronecamera2t64 > Version: 3.1.0+20221218103507-2 > Severity: serious [..] > thank you for applying our /usr-move patches. Unfortunately, this one > went wrong and it went to unstable rather than exp

Processed: Re: Bug#1075849: websockify: FTBFS on riscv64 (test timeout)

Processing control commands: > retitle -1 websockify: FTBFS with systemd (>= 256~rc3-3) due to fileno limit > bump Bug #1075849 [src:websockify] websockify: FTBFS on riscv64 (test timeout) Changed Bug title to 'websockify: FTBFS with systemd (>= 256~rc3-3) due to fileno limit bump' from 'websock

Bug#1075849: websockify: FTBFS on riscv64 (test timeout)

control: retitle -1 websockify: FTBFS with systemd (>= 256~rc3-3) due to fileno limit bump Hi, On 2024-07-06 11:54, Graham Inggs wrote: > Source: websockify > Version: 0.10.0+dfsg1-6 > Severity: serious > Tags: ftbfs > X-Debbugs-Cc: debian-ri...@lists.debian.org > > Hi Maintainer > > Since th

Bug#1076381: librav1e0.7: trying to overwrite librav1e.so.0.7.1', which is also in package librav1e0:amd64 0.7.1-2

On Mon, Jul 15, 2024 at 02:18:46PM +0200, Christian Marillat wrote: > | dpkg: error processing archive > /var/cache/apt/archives/librav1e0.7_0.7.1-3+b1_amd64.deb (--unpack): > | trying to overwrite '/usr/lib/x86_64-linux-gnu/librav1e.so.0.7.1', which > is also in package librav1e0:amd64 0.7.1-2

Bug#1076235: marked as done (grub-efi-arm64-unsigned: trying to overwrite '/usr/lib/grub/arm64-efi/monolithic/gcdaa64.efi', which is also in package grub-efi-arm64-bin 2.12-2)

Your message dated Mon, 15 Jul 2024 16:07:39 + with message-id and subject line Bug#1076235: fixed in grub2 2.12-5 has caused the Debian Bug report #1076235, regarding grub-efi-arm64-unsigned: trying to overwrite '/usr/lib/grub/arm64-efi/monolithic/gcdaa64.efi', which is also in package grub

Processed: closing 1022881

Processing commands for cont...@bugs.debian.org: > close 1022881 Bug #1022881 [src:swt4-gtk] swt4-gtk FTBFS due to default encoding Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1022881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102288

Bug#1076378: [Pkg-javascript-devel] Bug#1076378: node-xterm: Unable to build package node-xterm from sources in Debian Bookworm because of error TS2769

Control: fixed -1 5.3.0-1 On 7/15/24 15:57, Sergei Semin wrote: Source: node-xterm Version: 3.8.1+~cs0.9.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: syominser...@gmail.com Dear Maintainer, I tried to build node-xterm from sources in Debian Bookworm

Processed: Re: [Pkg-javascript-devel] Bug#1076378: node-xterm: Unable to build package node-xterm from sources in Debian Bookworm because of error TS2769

Processing control commands: > fixed -1 5.3.0-1 Bug #1076378 [src:node-xterm] node-xterm: Unable to build package node-xterm from sources in Debian Bookworm because of error TS2769 Marked as fixed in versions node-xterm/5.3.0-1. -- 1076378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076

Bug#1076388: node-xterm: Unable to build package node-xterm in Debian Trixie i386 due to LinkError in WebAssembly.Instance()

Source: node-xterm Version: 5.3.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: syominser...@gmail.com Dear Maintainer, I have tried to build package node-xterm in Debian Trixie i386 but there was a failure in tests. I was not able to reproduce this prob

Bug#1069728: marked as done (freerdp2: CVE-2024-32039 CVE-2024-32040 CVE-2024-32041 CVE-2024-32458 CVE-2024-32459 CVE-2024-32460)

Your message dated Mon, 15 Jul 2024 15:10:04 + with message-id and subject line Bug#1069728: fixed in freerdp2 2.11.7+dfsg1-1 has caused the Debian Bug report #1069728, regarding freerdp2: CVE-2024-32039 CVE-2024-32040 CVE-2024-32041 CVE-2024-32458 CVE-2024-32459 CVE-2024-32460 to be marked a

Bug#1076378: marked as pending in node-xterm

Control: tag -1 pending Hello, Bug #1076378 in node-xterm 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/js-team/node-xterm/-/commit/763f19349390aabc3d4557cead

Processed: Bug#1076378 marked as pending in node-xterm

Processing control commands: > tag -1 pending Bug #1076378 [src:node-xterm] node-xterm: Unable to build package node-xterm from sources in Debian Bookworm because of error TS2769 Added tag(s) pending. -- 1076378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076378 Debian Bug Tracking Syst

Processed: Bug#1076120 marked as pending in onboard

Processing control commands: > tag -1 pending Bug #1076120 [onboard] onboard: Segmentation Fault on Mouse Hover After Update to Version 1.4.1-7 Added tag(s) pending. -- 1076120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076120 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Bug#1076120: marked as pending in onboard

Control: tag -1 pending Hello, Bug #1076120 in onboard 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-mate-team/onboard/-/commit/db9b303ae74fbe4b55f0d8e

Bug#1076387: Cannot use agda-stdlib modules at all

Package: agda-stdlib Version: 1.7.3-1 Severity: serious When using the agda command to verify .agda, which uses the agda-stdlib package, it tries to write to the library directory, resulting in a `permission denied` error. Here is information on related packages: ``` % dpkg --no-pager -l emacs

Bug#1063190: [Pkg-owncloud-maintainers] Bug#1063190: Bug#1063190: closing 1063190 [owncloud-client+t64 RC]

Hey Agustin, Agustin Martin wrote on 11/07/2024 at 19:49:35+0200: > El mar, 9 jul 2024 a las 18:37, Agustin Martin () > escribió: >> >> El mar, 9 jul 2024 a las 14:26, Pierre-Elliott Bécue >> () escribió: >> > >> > Feel free to upload it even not as a NMU. (you can add a Team Upload >> > entry

Bug#1052088: marked as done (gnome-shell-extension-arc-menu: needs update for GNOME Shell 46)

Your message dated Mon, 15 Jul 2024 12:49:47 + with message-id and subject line Bug#1052088: fixed in gnome-shell-extension-arc-menu 57-1 has caused the Debian Bug report #1052088, regarding gnome-shell-extension-arc-menu: needs update for GNOME Shell 46 to be marked as done. This means that

Bug#1052107: marked as done (gnome-shell-extension-shortcuts: needs update for GNOME Shell 46)

Your message dated Mon, 15 Jul 2024 12:34:46 + with message-id and subject line Bug#1052107: fixed in gnome-shell-extension-shortcuts 1.5.1-1 has caused the Debian Bug report #1052107, regarding gnome-shell-extension-shortcuts: needs update for GNOME Shell 46 to be marked as done. This means

Bug#1052104: marked as done (gnome-shell-extension-impatience: needs update for GNOME Shell 45)

Your message dated Mon, 15 Jul 2024 12:19:12 + with message-id and subject line Bug#1052104: fixed in gnome-shell-extension-impatience 0.5.1-1 has caused the Debian Bug report #1052104, regarding gnome-shell-extension-impatience: needs update for GNOME Shell 45 to be marked as done. This mean

Bug#1069113: marked as done (gnome-shell-extension-dash-to-panel: Please update to ver. 62 , because ver. 60 doesn't work with gnome-shell ver 46)

Your message dated Mon, 15 Jul 2024 12:19:05 + with message-id and subject line Bug#1069113: fixed in gnome-shell-extension-dash-to-panel 62-1 has caused the Debian Bug report #1069113, regarding gnome-shell-extension-dash-to-panel: Please update to ver. 62 , because ver. 60 doesn't work with

Bug#1076381: librav1e0.7: trying to overwrite librav1e.so.0.7.1', which is also in package librav1e0:amd64 0.7.1-2

Package: librav1e0.7 Version: 0.7.1-3+b1 Severity: serious Dear Maintainer, I see this error : , | Unpacking librav1e0.7:amd64 (0.7.1-3+b1) ... | dpkg: error processing archive /var/cache/apt/archives/librav1e0.7_0.7.1-3+b1_amd64.deb (--unpack): | trying to overwrite '/usr/lib/x86_64-linux

Bug#1052103: marked as done (gnome-shell-extension-hide-activities: needs update for GNOME Shell 46)

Your message dated Mon, 15 Jul 2024 12:05:45 + with message-id and subject line Bug#1052103: fixed in gnome-shell-extension-hide-activities 46-1 has caused the Debian Bug report #1052103, regarding gnome-shell-extension-hide-activities: needs update for GNOME Shell 46 to be marked as done. T

Bug#1075792: [Debian-med-packaging] Bug#1075792: sight FTBFS with DCMTK 3.6.8

I'm on it, that's quite an easy fix. I'll take the opportunity to upgrade the package. *Dr. Flavien BRIDAULT* Director of Software Development IRCAD France & IRCAD Africa flavien.brida...@ircad.fr Tél. : +33 (0)3 88 119 201 IRCAD Franc

Processed: r-cran-mertools: autopkgtest regression on i386 with rmatrix 1.7-0

Processing control commands: > reopen -1 Bug #1071171 {Done: "Michael R. Crusoe" } [src:r-cran-mertools] r-cran-mertools: autopkgtest regression on i386 with rmatrix 1.7-0 Bug reopened Ignoring request to alter fixed versions of bug #1071171 to the same values previously set -- 1071171: https

Bug#1071171: r-cran-mertools: autopkgtest regression on i386 with rmatrix 1.7-0

Control: reopen -1 > The autopkgtest no longer fails on i386 r-cran-mertools' autopkgtests still run for almost 3 hours and time out when tested with lme4 1.1-35.5-1 (now in testing).

Bug#1076378: node-xterm: Unable to build package node-xterm from sources in Debian Bookworm because of error TS2769

Source: node-xterm Version: 3.8.1+~cs0.9.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: syominser...@gmail.com Dear Maintainer, I tried to build node-xterm from sources in Debian Bookworm. I created new VM from official Debian vagrant image: https://app.

Processed: azure-cli: Please drop dependencies on python3-distutils

Processing control commands: > severity -1 serious Bug #1065832 [src:azure-cli] azure-cli: Please drop dependencies on python3-distutils Bug #1076127 [src:azure-cli] (build-)dependency on removed python3-distutils Severity set to 'serious' from 'important' Severity set to 'serious' from 'importan

Bug#1076350: [Pkg-javascript-devel] Bug#1076350: nodejs: segfault in node when running browserify script on i386 when building node-chai

> If it's for building a debian package, then I recommend using rollup or > webpack, whatever is easier. Yes, I want to build some packages for i386 arch for some reasons. Because of my target arch for simplicity I'm building all packages in i386 env, even packages with all architecture. And with

Processed: libplayeronecamera2t64: ineffective replaces for /usr/lib/udev/rules.d/99-player_one_astronomy.rules causes file loss

Processing control commands: > clone -1 -2 Bug #1076374 [libplayeronecamera2t64] libplayeronecamera2t64: ineffective replaces for /usr/lib/udev/rules.d/99-player_one_astronomy.rules causes file loss Bug 1076374 cloned as bug 1076375 > retitle -2 libplayeronecamera2t64: soname-independent file in

Bug#1075814: plotpy: Fails to build on arm64

Hello Jeremy and Roland, On 2024-07-05 01:27, Jeremy Bícha wrote: > plotpy fails to build on arm64. Because it built once on arm64, its > build needs to be fixed or you could file a RM bug to remove it only > on arm64. I've forwarded the issue upstream [1], and they were quick to come up with a f

Bug#1076374: libplayeronecamera2t64: ineffective replaces for /usr/lib/udev/rules.d/99-player_one_astronomy.rules causes file loss

Package: libplayeronecamera2t64 Version: 3.1.0+20221218103507-2 Severity: serious User: helm...@debian.org Usertags: dep17p1 Control: clone -1 -2 Control: retitle -2 libplayeronecamera2t64: soname-independent file in shared libarary package Control: affects -1 libplayeronecamera2 X-Debbugs-Cc: z..

Bug#1076373: docker-cli and podman-docker have an undeclared file conflict on /usr/bin/docker

Package: docker-cli,podman-docker Severity: serious User: debian...@lists.debian.org Usertags: fileconflict The file /usr/bin/docker is contained in the packages * docker-cli/26.1.4+dfsg1-7 as present in experimental * podman-docker/5.0.3+ds1-2 as present in experimental These packages can be u

Bug#1065871: marked as done (grokevt: Please drop dependencies on python3-distutils)

Your message dated Mon, 15 Jul 2024 11:06:44 + with message-id and subject line Bug#1065871: fixed in grokevt 0.5.0-6.1 has caused the Debian Bug report #1065871, regarding grokevt: Please drop dependencies on python3-distutils to be marked as done. This means that you claim that the problem

Bug#1076370: fortunes: Symbol Lookup Error for rpl_malloc

reassign 1076370 librecode0 affects 1076370 fortunes found 1076370 3.6-27 fixed 1076370 3.6-29 thanks El 15/7/24 a las 10:55, Max Görner escribió: Package: fortunes Version: 1:1.99.1-7.3 Severity: grave Justification: renders package unusable Dear Maintainer, today I ran a full upgrade of my D

Processed: Re: Bug#1076370: fortunes: Symbol Lookup Error for rpl_malloc

Processing commands for cont...@bugs.debian.org: > reassign 1076370 librecode0 Bug #1076370 [fortunes] fortunes: Symbol Lookup Error for rpl_malloc Bug reassigned from package 'fortunes' to 'librecode0'. No longer marked as found in versions fortune-mod/1:1.99.1-7.3. Ignoring request to alter fixe

Bug#1076131: marked as done (libllvm18: declares itself as MA: same but is not co-installable)

Your message dated Mon, 15 Jul 2024 10:53:38 + with message-id and subject line Bug#1076131: fixed in llvm-toolchain-18 1:18.1.8-3 has caused the Debian Bug report #1076131, regarding libllvm18: declares itself as MA: same but is not co-installable to be marked as done. This means that you cl

Bug#1076350: [Pkg-javascript-devel] Bug#1076350: nodejs: segfault in node when running browserify script on i386 when building node-chai

Le lun. 15 juil. 2024 à 11:27, Сергей Сёмин a écrit : > I tried to give maximum resources to my VM with Debian Bookworm i386 > (recently upgraded to Debian Sid). > I gave 8 GB RAM in VM settings but because of i386 limitations only > 4GB actually available in VM. > The problem remains: > > root@d

Bug#1076350: [Pkg-javascript-devel] Bug#1076350: nodejs: segfault in node when running browserify script on i386 when building node-chai

I tried to give maximum resources to my VM with Debian Bookworm i386 (recently upgraded to Debian Sid). I gave 8 GB RAM in VM settings but because of i386 limitations only 4GB actually available in VM. The problem remains: root@debian-bookworm-i386:~/node-chai-4.3.7~ds1+~cs9.7.21# free -h

Bug#1076350: [Pkg-javascript-devel] Bug#1076350: nodejs: segfault in node when running browserify script on i386 when building node-chai

Thanks. It may be that browserify hits a bug by exhausting resources (heap). Using another bundler might be a good idea (rollup, webpack, esbuild...). Upstream doesn't support 32-bits builds on linux, however it does provide 32-bits build for windows. If that bug can be reproduced there, it would

Bug#1076370: fortunes: Symbol Lookup Error for rpl_malloc

Package: fortunes Version: 1:1.99.1-7.3 Severity: grave Justification: renders package unusable Dear Maintainer, today I ran a full upgrade of my Debian Testing as part of my daily routine. Since then, I cannot run `fortune` anymore. The error message I get is fortune: symbol lookup error:

Bug#1076355: marked as done (librecode0: removal of symbol rpl_malloc breaks ABI)

Your message dated Mon, 15 Jul 2024 08:49:17 + with message-id and subject line Bug#1076355: fixed in recode 3.6-29 has caused the Debian Bug report #1076355, regarding librecode0: removal of symbol rpl_malloc breaks ABI to be marked as done. This means that you claim that the problem has bee

Bug#1076355: fortune-mod: missing dependency

Long story short: I tried fixing the build failure with gcc-14 by updating the configure script and adding a few includes. But there are interactions between autoconf and libtool and it does not work. And updating libtool stuff in a 23-year old program would be a nightmare. So I've reverted thos

Bug#1076350: [Pkg-javascript-devel] Bug#1076350: nodejs: segfault in node when running browserify script on i386 when building node-chai

Hi! Just now I upgraded my existing Debian Bookworm i386 installation to Debian Sid using this repositories: deb http://deb.debian.org/debian unstable contrib main non-free-firmware deb-src http://deb.debian.org/debian unstable contrib main non-free-firmware Now I have these versions of packages o

Bug#1076350: [Pkg-javascript-devel] Bug#1076350: nodejs: segfault in node when running browserify script on i386 when building node-chai

Le dim. 14 juil. 2024 à 23:48, Sergei Semin a écrit : > Package: nodejs > Version: 18.19.0+dfsg-6~deb12u2 > I was trying to build from source package node-chai in Debian Bookworm > i386. And there was a failure. Now I will describe how to reproduce. > Thank you for the detailed report. First th

Bug#1076065: marked as done (rust-hyper-timeout: panick at CI testing: Expected timeout error)

Your message dated Mon, 15 Jul 2024 07:04:19 + with message-id and subject line Bug#1076065: fixed in rust-hyper-timeout 0.4.1-2 has caused the Debian Bug report #1076065, regarding rust-hyper-timeout: panick at CI testing: Expected timeout error to be marked as done. This means that you clai

Bug#1075860: marked as done (FTBFS: rustc 1.78)

Your message dated Mon, 15 Jul 2024 08:52:47 +0200 with message-id <449cfd8415c7f35fa00455edcbeed...@tauware.de> and subject line Fwd: rust-parsec-interface_0.29.1-2_source.changes ACCEPTED into unstable has caused the Debian Bug report #1075860, regarding FTBFS: rustc 1.78 to be marked as done.