Processed: src:orange-spectroscopy: fails to migrate to testing for too long

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.7.2-2 Bug #1086743 [src:orange-spectroscopy] src:orange-spectroscopy: fails to migrate to testing for too long The source 'orange-spectroscopy' and version '0.7.2-2' do not appear to match any binary packages Marked as fixed in versions orange-spectrosco

Bug#1066247: uhub: diff for NMU version 0.4.1-3.3

2024-11-04 Thread Gianfranco Costamagna
Package: uhub Version: 0.4.1-3.2 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for uhub (versioned as 0.4.1-3.3) and uploaded it. Regards. diff -Nru uhub-0.4.1/debian/changelog uhub-0.4.1/debian/changelog --- uhub-0.4.1/debian/changelog 2022-09-12 11:14:29.0

Processed: src:ejabberd-contrib: fails to migrate to testing for too long

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.2024.07.18~dfsg0-1 Bug #1086745 [src:ejabberd-contrib] src:ejabberd-contrib: fails to migrate to testing for too long Marked as fixed in versions ejabberd-contrib/0.2024.07.18~dfsg0-1. Bug #1086745 [src:ejabberd-contrib] src:ejabberd-contrib: fails to mig

Bug#1086701: autopkgtest: Same package version considered downgrade

2024-11-04 Thread Paul Gevers
Control: notfound -1 5.42 Hi, On 04-11-2024 13:15, Laurent Bigonville wrote: Package: autopkgtest Version: 5.42 I've removed the version, as this doesn't look like a regression. (The version in combination with the bug severity is blocking the migration to testing). Severity: serious A

Bug#1086744: src:erlang-p1-eimp: fails to migrate to testing for too long

2024-11-04 Thread Paul Gevers
Source: erlang-p1-eimp Version: 1.0.22-3 Severity: serious Control: close -1 1.0.23-2 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 da

Processed: src:ejabberd: fails to migrate to testing for too long

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > close -1 24.07-2 Bug #1086746 [src:ejabberd] src:ejabberd: fails to migrate to testing for too long Marked as fixed in versions ejabberd/24.07-2. Bug #1086746 [src:ejabberd] src:ejabberd: fails to migrate to testing for too long Marked Bug as done -- 1086746: htt

Processed: src:ruby-excon: fails to migrate to testing for too long

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.112.0-2 Bug #1086742 [src:ruby-excon] src:ruby-excon: fails to migrate to testing for too long The source 'ruby-excon' and version '0.112.0-2' do not appear to match any binary packages Marked as fixed in versions ruby-excon/0.112.0-2. Bug #1086742 [src:

Bug#1086745: src:ejabberd-contrib: fails to migrate to testing for too long

2024-11-04 Thread Paul Gevers
Source: ejabberd-contrib Version: 0.2023.10.04~dfsg0-1 Severity: serious Control: close -1 0.2024.07.18~dfsg0-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 un

Bug#1086746: src:ejabberd: fails to migrate to testing for too long

2024-11-04 Thread Paul Gevers
Source: ejabberd Version: 23.10-1 Severity: serious Control: close -1 24.07-2 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 ha

Processed: src:erlang-p1-eimp: fails to migrate to testing for too long

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.0.23-2 Bug #1086744 [src:erlang-p1-eimp] src:erlang-p1-eimp: fails to migrate to testing for too long Marked as fixed in versions erlang-p1-eimp/1.0.23-2. Bug #1086744 [src:erlang-p1-eimp] src:erlang-p1-eimp: fails to migrate to testing for too long Mark

Bug#1086742: src:ruby-excon: fails to migrate to testing for too long

2024-11-04 Thread Paul Gevers
Source: ruby-excon Version: 0.88.0-1 Severity: serious Control: close -1 0.112.0-2 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

Bug#1086743: src:orange-spectroscopy: fails to migrate to testing for too long

2024-11-04 Thread Paul Gevers
Source: orange-spectroscopy Version: 0.6.10-4 Severity: serious Control: close -1 0.7.2-2 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 3

Bug#1081027: src:sssd: flaky autopkgtest: spawn id exp3 not open

2024-11-04 Thread Michael Prokop
Hi, * Paul Gevers [Sat Sep 07, 2024 at 07:13:21AM +0200]: > I looked at the results of the autopkgtest of your package. I noticed that > it regularly fails. > > Because the unstable-to-testing migration software now blocks on > regressions in testing, flaky tests, i.e. tests that flip between >

Processed: Re: Bug#1086701: autopkgtest: Same package version considered downgrade

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > notfound -1 5.42 Bug #1086701 [autopkgtest] autopkgtest: Same package version considered downgrade No longer marked as found in versions autopkgtest/5.42. -- 1086701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086701 Debian Bug Tracking System Contact ow..

Bug#1066247: marked as done (uhub: FTBFS: adcclient.c:178:33: error: implicit declaration of function ‘ADC_client_connect_internal’; did you mean ‘ADC_client_connect’? [-Werror=implicit-function-decla

2024-11-04 Thread Debian Bug Tracking System
Your message dated Tue, 05 Nov 2024 06:50:45 + with message-id and subject line Bug#1066247: fixed in uhub 0.4.1-3.3 has caused the Debian Bug report #1066247, regarding uhub: FTBFS: adcclient.c:178:33: error: implicit declaration of function ‘ADC_client_connect_internal’; did you mean ‘ADC_c

Processed: tagging 1086676

2024-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1086676 + fixed-upstream patch Bug #1086676 [python3-flake8] Not installable with python3-pycodestyle/sid Added tag(s) fixed-upstream and patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1086676: https:

Bug#1085594: reposurgeon: Missing build dependency on tzdata-legacy

2024-11-04 Thread Aurelien Jarno
On 2024-11-05 00:33, Santiago Vila wrote: > > please find the debdiff attached > > Hi. Can you post the debdiff? (or just say what you did) Oops sorry about that. Please find it attached. > NMUs are messy for my taste. I could fix the FTBFS problem and let Anthony > (the usual uploader) to decid

Bug#1075694: xxkb: ftbfs with GCC-14

2024-11-04 Thread Bo YU
Hi, On Tue, Nov 05, 2024 at 10:56:09AM +0800, Bo YU wrote: Hi, ... I have uploaded it to mentor also. Please review it. Could you upload it if there are no other issues? TIA. ``` The source builds the following binary packages: xxkb - Keyboard state indicator and switcher for xkb To acce

Bug#1075694: xxkb: ftbfs with GCC-14

2024-11-04 Thread Bo YU
Hi, On Wed, Jul 03, 2024 at 12:49:38PM +, Matthias Klose wrote: resource.c: In function ‘GetConfig’: resource.c:625:22: error: assignment to ‘int’ from ‘void *’ makes integer from pointer without a cast [-Wint-conversion] 625 | stat = NULL; | ^ make

Processed: tagging with patch

2024-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1075684 patch Bug #1075684 [src:xshisen] xshisen: ftbfs with GCC-14 Ignoring request to alter tags of bug #1075684 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1075684: http

Processed: tagging with patch

2024-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1075694 patch Bug #1075694 [src:xxkb] xxkb: ftbfs with GCC-14 Ignoring request to alter tags of bug #1075694 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1075694: https://bu

Processed: tagging the patch

2024-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1075684 patch Bug #1075684 [src:xshisen] xshisen: ftbfs with GCC-14 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1075684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075684 Debia

Bug#1075684: xshisen: ftbfs with GCC-14

2024-11-04 Thread YunQiang Su
On Tue, 5 Nov 2024 10:43:19 +0800 Bo YU wrote: > Hi, > > >configure:673:1: error: return type defaults to 'int' [-Wimplicit-int] > > 673 | main(){return(0);} > > | ^~~~ > >configure: failed program was: > > > >#line 671 "configure" > >#include "confdefs.h" > > > > I proposed one patch to fix

Processed: tagging with patch

2024-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1075694 patch Bug #1075694 [src:xxkb] xxkb: ftbfs with GCC-14 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1075694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075694 Debian Bug

Bug#1075684: xshisen: ftbfs with GCC-14

2024-11-04 Thread Bo YU
Hi, configure:673:1: error: return type defaults to 'int' [-Wimplicit-int] 673 | main(){return(0);} | ^~~~ configure: failed program was: #line 671 "configure" #include "confdefs.h" I proposed one patch to fix the issue, please review it. And I did some minor changes with QA upload als

Bug#1085594: reposurgeon: Missing build dependency on tzdata-legacy

2024-11-04 Thread Santiago Vila
please find the debdiff attached Hi. Can you post the debdiff? (or just say what you did) NMUs are messy for my taste. I could fix the FTBFS problem and let Anthony (the usual uploader) to decide (for a later upload) if he wants to use a depends, a recommends, or a suggest for the binary depend

Bug#1085594: reposurgeon: Missing build dependency on tzdata-legacy

2024-11-04 Thread Aurelien Jarno
Dear maintainer, On 2024-10-21 01:59, Adrian Bunk wrote: > Source: reposurgeon > Version: 4.38-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=reposurgeon&ver=4.38-1%2Bb3 > > ... > === RUN TestReadAuthorMap > reposurgeon: in readAuthorMap, while parsing li

Bug#1086735: libx11-6: buggy shlibs, libx11-xcb1 vs. libx11-6-udeb

2024-11-04 Thread Cyril Brulebois
Package: libx11-6 Version: 2:1.8.10-1 Severity: serious Tags: d-i Justification: broken shlibs, breaks udebs, etc. X-Debbugs-Cc: debian-b...@lists.debian.org Hi, [ Now turning the initial mail ping into a proper bug report. ] Spotted via dose's reporting lots of uninstallable udebs on arm64: the

Bug#1054814: marked as done (criu: FTBFS: bad install directory or PYTHONPATH)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 21:50:01 + with message-id and subject line Bug#1054814: fixed in criu 3.19-1 has caused the Debian Bug report #1054814, regarding criu: FTBFS: bad install directory or PYTHONPATH to be marked as done. This means that you claim that the problem has been dea

Bug#1081079: marked as done (python3-nipype: unsatisfiable dependency)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 21:53:02 + with message-id and subject line Bug#1081079: fixed in nipype 1.9.0-1 has caused the Debian Bug report #1081079, regarding python3-nipype: unsatisfiable dependency to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1086676: Not installable with python3-pycodestyle/sid

2024-11-04 Thread Salvatore Bonaccorso
Hi, On Sun, Nov 03, 2024 at 10:47:58PM +0500, Andrey Rakhmatullin wrote: > Package: python3-flake8 > Version: 7.1.1-1 > Severity: serious > > pycodestyle 2.12.1-1 was just uploaded, making python3-flake8 not installable. And since upstream commit https://github.com/PyCQA/flake8/commit/defd315175

Bug#1081856: marked as done (agg: FTBFS: agg_font_freetype.cpp:182:35: error: invalid conversion from 'unsigned char*' to 'char*' [-fpermissive])

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 21:19:25 + with message-id and subject line Bug#1081856: fixed in agg 1:2.7.0.r145+dfsg-1 has caused the Debian Bug report #1081856, regarding agg: FTBFS: agg_font_freetype.cpp:182:35: error: invalid conversion from 'unsigned char*' to 'char*' [-fpermissive

Bug#1086701: autopkgtest: Same package version considered downgrade

2024-11-04 Thread Paride Legovini
On 2024-11-04 18:29, Paride Legovini wrote: > *However*, if you check the policy table at this point, it will > identical to the previous one. APT has no way to determine the real > source of an installed package: it only knows about _versions_ of > installed packages. [Note how /var/lib/dpkg/statu

Bug#1086725: marked as done (z3 FTBFS on mips64el)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 20:56:47 + with message-id and subject line Bug#1086725: fixed in z3 4.8.12-3.2 has caused the Debian Bug report #1086725, regarding z3 FTBFS on mips64el to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Processed: Re: Bug#1016062: haskell-cborg FTBFS on 32bit: error: Couldn't match expected type ‘Int64#’ with actual type ‘Int#’

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1016062 [src:haskell-cborg] haskell-cborg FTBFS on 32bit: error: Couldn't match expected type ‘Int64#’ with actual type ‘Int#’ Severity set to 'important' from 'serious' -- 1016062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=10160

Bug#1016062: haskell-cborg FTBFS on 32bit: error: Couldn't match expected type ‘Int64#’ with actual type ‘Int#’

2024-11-04 Thread Ilias Tsitsimpis
Control: severity -1 important I have removed haskell-cborg from 32bit architectures (see #1086352). -- Ilias

Bug#1086725: z3 FTBFS on mips64el

2024-11-04 Thread Adrian Bunk
Source: z3 Version: 4.8.12-3.1 Severity: serious Tags: ftbfs trixie sid patch https://buildd.debian.org/status/fetch.php?pkg=z3&arch=mips64el&ver=4.8.12-3.1%2Bb3&stamp=1730452483&raw=0 ... /usr/bin/ld: not enough GOT space for local GOT entries /usr/bin/ld: BFD (GNU Binutils for Debian) 2.43.1 in

Bug#1086562: marked as done (gnustep-gui: Please build-depend on imagemagick 7)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 19:49:24 + with message-id and subject line Bug#1086562: fixed in gnustep-gui 0.31.1-6 has caused the Debian Bug report #1086562, regarding gnustep-gui: Please build-depend on imagemagick 7 to be marked as done. This means that you claim that the problem ha

Bug#1014187: marked as done (fruit: Binary file without a source code)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:19:00 + with message-id and subject line Bug#1079960: Removed package(s) from unstable has caused the Debian Bug report #1014187, regarding fruit: Binary file without a source code to be marked as done. This means that you claim that the problem has been

Bug#1022630: marked as done (node-mermaid: Unable to build with rollup 3)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:24:29 + with message-id and subject line Bug#1080267: Removed package(s) from unstable has caused the Debian Bug report #1022630, regarding node-mermaid: Unable to build with rollup 3 to be marked as done. This means that you claim that the problem has b

Bug#1066987: marked as done (clickhouse: FTBFS: flaky tests)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:41:09 + with message-id and subject line Bug#1086505: Removed package(s) from unstable has caused the Debian Bug report #1066987, regarding clickhouse: FTBFS: flaky tests to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1016319: marked as done (apertium-crh-tur: FTBFS: make[2]: *** [Makefile:890: crh-tur.t1x.bin] Error 1)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:26:58 + with message-id and subject line Bug#1080410: Removed package(s) from unstable has caused the Debian Bug report #1016319, regarding apertium-crh-tur: FTBFS: make[2]: *** [Makefile:890: crh-tur.t1x.bin] Error 1 to be marked as done. This means th

Bug#1008982: marked as done (adacontrol: depends on unavailable asis)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:31:57 + with message-id and subject line Bug#1080507: Removed package(s) from unstable has caused the Debian Bug report #1008982, regarding adacontrol: depends on unavailable asis to be marked as done. This means that you claim that the problem has been

Bug#1059261: marked as done (clickhouse: CVE-2023-48298 CVE-2023-47118 CVE-2022-44011 CVE-2022-44010)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:41:09 + with message-id and subject line Bug#1086505: Removed package(s) from unstable has caused the Debian Bug report #1059261, regarding clickhouse: CVE-2023-48298 CVE-2023-47118 CVE-2022-44011 CVE-2022-44010 to be marked as done. This means that you

Bug#1075992: marked as done (laminard: move lib/systemd/system/laminar.service to /usr for DEP17)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:23:36 + with message-id and subject line Bug#1080075: Removed package(s) from unstable has caused the Debian Bug report #1075992, regarding laminard: move lib/systemd/system/laminar.service to /usr for DEP17 to be marked as done. This means that you clai

Bug#1036688: marked as done (node-mermaid: node-stylis is now packaged separately)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:24:29 + with message-id and subject line Bug#1080267: Removed package(s) from unstable has caused the Debian Bug report #1036688, regarding node-mermaid: node-stylis is now packaged separately to be marked as done. This means that you claim that the prob

Bug#1032109: marked as done (Don't release with bookworm)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:35:41 + with message-id and subject line Bug#1081322: Removed package(s) from unstable has caused the Debian Bug report #1032109, regarding Don't release with bookworm to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1019455: marked as done (laminard: WebUI of laminar fails because newer incompatible version of Chart.js is included)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:23:36 + with message-id and subject line Bug#1080075: Removed package(s) from unstable has caused the Debian Bug report #1019455, regarding laminard: WebUI of laminar fails because newer incompatible version of Chart.js is included to be marked as done.

Bug#1071455: marked as done (python-html-sanitizer: python3-lxml-html-clean is now a separate package)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:22:04 + with message-id and subject line Bug#1080054: Removed package(s) from unstable has caused the Debian Bug report #1071455, regarding python-html-sanitizer: python3-lxml-html-clean is now a separate package to be marked as done. This means that yo

Bug#1008366: marked as done (python-html-sanitizer: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:22:04 + with message-id and subject line Bug#1080054: Removed package(s) from unstable has caused the Debian Bug report #1008366, regarding python-html-sanitizer: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13

Bug#1070710: marked as done (python-html-sanitizer: CVE-2024-34078: Arbitrary HTML present after sanitization because of unicode normalization)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:22:04 + with message-id and subject line Bug#1080054: Removed package(s) from unstable has caused the Debian Bug report #1070710, regarding python-html-sanitizer: CVE-2024-34078: Arbitrary HTML present after sanitization because of unicode normalization

Bug#958692: marked as done (node-matrix-js-sdk: Remove dependency to node-request)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:21:25 + with message-id and subject line Bug#1080047: Removed package(s) from unstable has caused the Debian Bug report #958692, regarding node-matrix-js-sdk: Remove dependency to node-request to be marked as done. This means that you claim that the prob

Bug#1077820: marked as done (clickhouse: CVE-2024-6873)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:41:09 + with message-id and subject line Bug#1086505: Removed package(s) from unstable has caused the Debian Bug report #1077820, regarding clickhouse: CVE-2024-6873 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1070658: marked as done (FTBFS: error: expected ‘)’ before ‘maxLength’)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:41:09 + with message-id and subject line Bug#1086505: Removed package(s) from unstable has caused the Debian Bug report #1070658, regarding FTBFS: error: expected ‘)’ before ‘maxLength’ to be marked as done. This means that you claim that the problem has

Bug#1030453: marked as done (devpi-common: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:33:08 + with message-id and subject line Bug#1080509: Removed package(s) from unstable has caused the Debian Bug report #1030453, regarding devpi-common: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit co

Bug#1018970: marked as done (node-matrix-js-sdk: CVE-2022-36059)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:21:25 + with message-id and subject line Bug#1080047: Removed package(s) from unstable has caused the Debian Bug report #1018970, regarding node-matrix-js-sdk: CVE-2022-36059 to be marked as done. This means that you claim that the problem has been dealt

Bug#1033621: marked as done (node-matrix-js-sdk: CVE-2023-28427)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:21:25 + with message-id and subject line Bug#1080047: Removed package(s) from unstable has caused the Debian Bug report #1033621, regarding node-matrix-js-sdk: CVE-2023-28427 to be marked as done. This means that you claim that the problem has been dealt

Bug#994213: marked as done (node-matrix-js-sdk: CVE-2021-40823: E2EE vulnerability)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:21:25 + with message-id and subject line Bug#1080047: Removed package(s) from unstable has caused the Debian Bug report #994213, regarding node-matrix-js-sdk: CVE-2021-40823: E2EE vulnerability to be marked as done. This means that you claim that the pro

Bug#1021136: marked as done (node-matrix-js-sdk: CVE-2022-39236 CVE-2022-39249 CVE-2022-39251)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:21:25 + with message-id and subject line Bug#1080047: Removed package(s) from unstable has caused the Debian Bug report #1021136, regarding node-matrix-js-sdk: CVE-2022-39236 CVE-2022-39249 CVE-2022-39251 to be marked as done. This means that you claim t

Processed: limit source to criu, tagging 1054814

2024-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source criu Limiting to bugs with field 'source' containing at least one of 'criu' Limit currently set to 'source':'criu' > tags 1054814 + pending Bug #1054814 [src:criu] criu: FTBFS: bad install directory or PYTHONPATH Added tag(s) pending

Bug#997156: marked as done (crazydiskinfo: FTBFS: main.cpp:217:18: error: format not a string literal and no format arguments [-Werror=format-security])

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:30:12 + with message-id and subject line Bug#1080504: Removed package(s) from unstable has caused the Debian Bug report #997156, regarding crazydiskinfo: FTBFS: main.cpp:217:18: error: format not a string literal and no format arguments [-Werror=format-s

Bug#1027037: marked as done (backdoor-factory: Backdoor-factory isn't working after python3 transition)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:29:34 + with message-id and subject line Bug#1080503: Removed package(s) from unstable has caused the Debian Bug report #1027037, regarding backdoor-factory: Backdoor-factory isn't working after python3 transition to be marked as done. This means that y

Bug#988156: marked as done (breezy breaks breezy-loom autopkgtest: FAILED (failures=4))

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:28:56 + with message-id and subject line Bug#1080502: Removed package(s) from unstable has caused the Debian Bug report #988156, regarding breezy breaks breezy-loom autopkgtest: FAILED (failures=4) to be marked as done. This means that you claim that the

Bug#414092: marked as done (airport-utils: Tools start and quit immediately without working)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:28:00 + with message-id and subject line Bug#1080501: Removed package(s) from unstable has caused the Debian Bug report #414092, regarding airport-utils: Tools start and quit immediately without working to be marked as done. This means that you claim tha

Bug#1008348: marked as done (apertium-sme-nob: FTBFS: semanticroles.cg3: Error: Expected set on line 4400 near `;␊␊TEMPLATE uniqueLO`!)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:27:31 + with message-id and subject line Bug#1080411: Removed package(s) from unstable has caused the Debian Bug report #1008348, regarding apertium-sme-nob: FTBFS: semanticroles.cg3: Error: Expected set on line 4400 near `;␊␊TEMPLATE uniqueLO`! to be ma

Bug#1016336: marked as done (apertium-mlt-ara: FTBFS: make[1]: *** [Makefile:790: ara-mlt.t1x.bin] Error 1)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:25:17 + with message-id and subject line Bug#1080405: Removed package(s) from unstable has caused the Debian Bug report #1016336, regarding apertium-mlt-ara: FTBFS: make[1]: *** [Makefile:790: ara-mlt.t1x.bin] Error 1 to be marked as done. This means th

Bug#1016320: marked as done (apertium-cy-en: FTBFS: make[2]: *** [Makefile:816: en-cy.t2x.bin] Error 1)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:25:47 + with message-id and subject line Bug#1080407: Removed package(s) from unstable has caused the Debian Bug report #1016320, regarding apertium-cy-en: FTBFS: make[2]: *** [Makefile:816: en-cy.t2x.bin] Error 1 to be marked as done. This means that y

Bug#1005670: marked as done (apertium-kaz-tat: FTBFS: ERROR: Transducer contains epsilon transition to a final state. Aborting.)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:26:18 + with message-id and subject line Bug#1080408: Removed package(s) from unstable has caused the Debian Bug report #1005670, regarding apertium-kaz-tat: FTBFS: ERROR: Transducer contains epsilon transition to a final state. Aborting. to be marked as

Processed: [bts-link] source package src:blueprint-compiler

2024-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:blueprint-compiler > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.deb

Bug#997203: marked as done (gigedit: FTBFS: ../compat.h:194:21: error: ‘const Pango::Alignment Pango::ALIGN_LEFT’ redeclared as different kind of entity)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:20:51 + with message-id and subject line Bug#1079966: Removed package(s) from unstable has caused the Debian Bug report #997203, regarding gigedit: FTBFS: ../compat.h:194:21: error: ‘const Pango::Alignment Pango::ALIGN_LEFT’ redeclared as different kind

Bug#964195: marked as done (CVE-2020-9497 CVE-2020-9498)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:20:19 + with message-id and subject line Bug#1079964: Removed package(s) from unstable has caused the Debian Bug report #964195, regarding CVE-2020-9497 CVE-2020-9498 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#995966: marked as done (epigrass: epirunner and epidash fail to run due to missing dash modules)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:18:27 + with message-id and subject line Bug#1079958: Removed package(s) from unstable has caused the Debian Bug report #995966, regarding epigrass: epirunner and epidash fail to run due to missing dash modules to be marked as done. This means that you

Bug#998265: marked as done (epigrass: autopkgtest regression: The 'panel' distribution was not found)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:18:27 + with message-id and subject line Bug#1079958: Removed package(s) from unstable has caused the Debian Bug report #998265, regarding epigrass: autopkgtest regression: The 'panel' distribution was not found to be marked as done. This means that you

Bug#1081523: marked as done (guacomole-server: Switch from freerdp2 to freerdp3)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:20:19 + with message-id and subject line Bug#1079964: Removed package(s) from unstable has caused the Debian Bug report #1081523, regarding guacomole-server: Switch from freerdp2 to freerdp3 to be marked as done. This means that you claim that the proble

Bug#880220: marked as done (should not install a globally valid trust anchor)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:19:43 + with message-id and subject line Bug#1079961: Removed package(s) from unstable has caused the Debian Bug report #880220, regarding should not install a globally valid trust anchor to be marked as done. This means that you claim that the problem h

Bug#1005154: marked as done (guacamole-server: frequent test failure on i386)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 18:20:19 + with message-id and subject line Bug#1079964: Removed package(s) from unstable has caused the Debian Bug report #1005154, regarding guacamole-server: frequent test failure on i386 to be marked as done. This means that you claim that the problem h

Bug#1086501: close #1086501

2024-11-04 Thread Jérôme Kieffer
Since I was not able to reproduce the bug on another computer ... I investigate and found the issue: ldd /lib/x86_64-linux-gnu/libwebkit2gtk-4.1.so.0.16.3 linux-vdso.so.1 (0x7ffd0affa000) [...] libgbm.so.1 => /lib/x86_64-linux-gnu/libgbm.so.1 (0x7fb11a12) libd

Bug#1086720: libsdl3: not ready to include in a stable release

2024-11-04 Thread Simon McVittie
Source: libsdl3 Version: 3.1.3+ds-1 Severity: serious Tags: upstream Forwarded: https://github.com/libsdl-org/SDL/milestone/10 With the 3.1.3 preview release having frozen the API and ABI, I think libsdl3 is ready to go to unstable, but it should probably not be included in trixie until we reach t

Bug#1000303: liboqs: not yet ready for testing or stable

2024-11-04 Thread Andreas Metzler
On 2023-06-28 Andrius Merkys wrote: > On Wed, 28 Jun 2023, 10:09 Mikael Frykholm, wrote: >>> The upstream wishes to keep the package out of stable distributions for >>> now, until the NIST Post-Quantum Cryptography standardization project >>> reaches its conclusion >> Is this still true? Can th

Bug#1086685: cryptsetup-initramfs: Fails to include all LUKS LVM PVs required to activate VG

2024-11-04 Thread Tj
Package: lvm2 Version: 2.03.16-2 Followup-For: Bug #1086685 X-Debbugs-Cc: tj.iam...@proton.me This really is not an lvm problem; lvm never should try to activate an incomplete volume group especially if some of the logical volumes span the physical volume that is missing - and that is the case her

Bug#1086701: autopkgtest: Same package version considered downgrade

2024-11-04 Thread Paride Legovini
On 2024-11-04 13:15, Laurent Bigonville wrote: > With the unshare backend(?) it seems that rebuilding a package without > changing the version is causing test to fail becuase it consider the > same version as a downgrade. > > For example: > > apt-get source libselinux > cd libselinux-3.7 > autopk

Processed: htsjdk: FTBFS: 35741 tests completed, 9 failed, 10 skipped

2024-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # this is happening in bookworm > # will probably do an upload for proposed-updates > unarchive 1055447 Bug #1055447 {Done: Pierre Gruet } [src:htsjdk] htsjdk: FTBFS: 35741 tests completed, 9 failed, 10 skipped Unarchived Bug 1055447 > found 1055

Bug#1016936: Debian: quassel build fails with DWZ errors when using LLVM-19 and DWARF-5

2024-11-04 Thread Sedat Dilek
On Mon, Nov 4, 2024 at 3:39 PM Sedat Dilek wrote: > > On Fri, Nov 1, 2024 at 11:34 AM Sedat Dilek wrote: > > > > OK. > > > > Using dh_strip instead of dh_strip_nondeterminism (default) ... > > > > Hi, > > In my latest build I created an OVERRIDE in debian/rules for dh_dwz as > this seems to have

Processed: reopening 1083019, found 1083019 in 47.0-2, severity of 1083019 is important ...

2024-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 1083019 Bug #1083019 {Done: Jeremy Bícha } [src:gtk4] nautilus: Crashes on load after upgrade to version 47.0-1 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need t

Bug#1083019: nautilus: Crashes on load after upgrade to version 47.0-1

2024-11-04 Thread John M.
Hi. I'm not sure if anyone's checking this bug anymore ---since it was erroneously marked as Done. With nautilus 47.0-2, and libgtk-4-1 v4.16.3+ds-2, the issue still persists: $ nautilus ** Message: 09:01:23.931: Connecting to org.freedesktop.Tracker3.Miner.Files MESA-INTEL: warning: ../src/inte

Processed: util-linux ftbfs on kernel > 6.5

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/util-linux/util-linux/issues/3266 Bug #1086706 [src:util-linux] util-linux ftbfs on kernel > 6.5 Set Bug forwarded-to-address to 'https://github.com/util-linux/util-linux/issues/3266'. -- 1086706: https://bugs.debian.org/cgi-bin/bug

Processed: forcibly merging 1078810 1080523

2024-11-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1078810 1080523 Bug #1078810 {Done: Laurent Bigonville } [src:audit] audit: FTBFS: Test suite does not allow the package to be built Bug #1080523 [src:audit] audit: auparse/test/auparse_test.ref and auparse_test.cur are different afte

Bug#1086706: util-linux ftbfs on kernel > 6.5

2024-11-04 Thread Chris Hofstaedtler
Source: util-linux Version: 2.40.2-9 Tags: ftbfs Severity: serious Control: forwarded -1 https://github.com/util-linux/util-linux/issues/3266 fincore/count test fails.

Bug#1054814: Proposed fix

2024-11-04 Thread Reinhard Tartler
Control: tag -1 patch I believe the change in https://salsa.debian.org/debian/criu/-/merge_requests/4 should address this issue. Best, -rt

Processed: Proposed fix

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #1054814 [src:criu] criu: FTBFS: bad install directory or PYTHONPATH Added tag(s) patch. -- 1054814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1086701: autopkgtest: Same package version considered downgrade

2024-11-04 Thread Laurent Bigonville
Package: autopkgtest Version: 5.42 Severity: serious Hello, With the unshare backend(?) it seems that rebuilding a package without changing the version is causing test to fail becuase it consider the same version as a downgrade. For example: apt-get source libselinux cd libselinux-3.7 autopkgte

Bug#1042588: marked as done (fmtlib: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:18: override_dh_auto_build-indep] Error 2)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 10:04:04 + with message-id and subject line Bug#1042588: fixed in fmtlib 10.1.1+ds1-3 has caused the Debian Bug report #1042588, regarding fmtlib: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:18: override_dh_auto_build-indep] Error 2 to

Bug#1084301: marked as done (moment-timezone.js: FTBFS: make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error 1)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 10:50:45 + with message-id and subject line Bug#1084301: fixed in moment-timezone.js 0.5.46+dfsg-1 has caused the Debian Bug report #1084301, regarding moment-timezone.js: FTBFS: make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error 1 to be

Bug#1068750: marked as done (moment-timezone.js: FTBFS everywhere)

2024-11-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Nov 2024 10:50:45 + with message-id and subject line Bug#1068750: fixed in moment-timezone.js 0.5.46+dfsg-1 has caused the Debian Bug report #1068750, regarding moment-timezone.js: FTBFS everywhere to be marked as done. This means that you claim that the problem has

Processed: fmtlib 10 transition is started

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1056389 [src:termpaint] FTBFS with fmtlib 10 Severity set to 'serious' from 'important' -- 1056389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: fmtlib 10 transition is started

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1086567 [src:xmrig] xmrig: FTBFS with fmtlib 10 Severity set to 'serious' from 'important' -- 1086567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: fmtlib 10 transition is started

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1086565 [src:genomicsdb] genomicsdb: FTBFS with fmtlib 10 Severity set to 'serious' from 'important' -- 1086565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problem

Processed: fmtlib 10 transition is started

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1086564 [src:ceph] ceph: FTBFS with fmtlib 10 Severity set to 'serious' from 'important' -- 1086564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: fmtlib 10 transition is started

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1086566 [src:open3d] open3d: FTBFS with fmtlib 10 Severity set to 'serious' from 'important' -- 1086566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: fmtlib 10 transition is started

2024-11-04 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1086563 [src:0ad] 0ad: FTBFS with fmtlib 10 Severity set to 'serious' from 'important' -- 1086563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

  1   2   >