Bug#1049872: FTBFS on multiple release architectures

Hi Emanuele, On 2023-09-05 16:58, Emanuele Rocca wrote: On 2023-08-28 07:42, Andrius Merkys wrote: On Wed, 16 Aug 2023 14:29:10 +0200 Emanuele Rocca wrote: asmjit does not build correctly on the following architectures: armel, armhf, mips64el, mipsel, s390x. Does this constitute an RC bug?

Processed: set forward URL for 1049872

Processing commands for cont...@bugs.debian.org: > forwarded 1049872 https://github.com/asmjit/asmjit/issues/74 Bug #1049872 [src:asmjit] asmjit: FTBFS on armel and armhf Set Bug forwarded-to-address to 'https://github.com/asmjit/asmjit/issues/74'. > thanks Stopping processing here. Please

Processed: Re: Bug#1051510: searx: SearX upstream is no longer maintained

Processing control commands: > severity -1 serious Bug #1051510 [src:searx] searx: SearX upstream is no longer maintained Severity set to 'serious' from 'normal' -- 1051510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051510 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1035366: marked as done (pytorch-ignite: FTBFS: py3versions: empty set of versions)

Your message dated Sat, 09 Sep 2023 01:49:45 + with message-id and subject line Bug#1035366: fixed in pytorch-ignite 0.4.12-1 has caused the Debian Bug report #1035366, regarding pytorch-ignite: FTBFS: py3versions: empty set of versions to be marked as done. This means that you claim that

Bug#1051496: mailgraph: does not support the new syslog format

Control: tags -1 patch upstream On 2023-09-08 19:30:29 +0200, Vincent Lefevre wrote: > mailgraph no longer works after the upgrade to bookworm, and > this is probably due to the fact that it does not support the > new syslog format: /usr/sbin/mailgraph contains [...] > and this format is no

Processed: Re: mailgraph: does not support the new syslog format

Processing control commands: > tags -1 patch upstream Bug #1051496 [mailgraph] mailgraph: does not support the new syslog format Added tag(s) upstream and patch. -- 1051496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051496 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1051521: rust-palette: autopkgtest failures

Source: rust-palette Version: 0.7.3+dfsg-1 Severity: serious rust-palette is unable to migrate to Testing because its autopkgtests are failing. https://qa.debian.org/excuses.php?package=rust-palette Thank you, Jeremy Bícha

Bug#1051519: rust-async-task: autopkgtest failures

Source: rust-async-task Version: 4.4.0-2 Severity: serious rust-async-task is unable to migrate to Testing because its autopkgtests are failing. https://qa.debian.org/excuses.php?package=rust-async-task Thank you, Jeremy Bícha

Bug#1050299: [Pkg-rust-maintainers] Bug#1050299: rust-webpki: RUSTSEC-2023-0052

I think this indicates that it can indeed be safely removed from Debian? I'm CC'ing developers that have made uploads to this packages in the past for additiponal opinions as I suspect the issue is more subtle than that. dak rm does not take account of virtual packages. So for rust packages it

Bug#1051031: marked as done (libvmime: build-depends on old libgsasl7-dev)

Your message dated Fri, 08 Sep 2023 22:35:12 + with message-id and subject line Bug#1051031: fixed in libvmime 0.9.2-8.1 has caused the Debian Bug report #1051031, regarding libvmime: build-depends on old libgsasl7-dev to be marked as done. This means that you claim that the problem has been

Bug#1051392: marked as done (Crash on unaligned reads on 32-bit arm architectures)

Your message dated Fri, 08 Sep 2023 22:21:18 + with message-id and subject line Bug#1051392: fixed in victoriametrics 1.79.14+ds1-1 has caused the Debian Bug report #1051392, regarding Crash on unaligned reads on 32-bit arm architectures to be marked as done. This means that you claim that

Bug#1050299: rust-webpki: RUSTSEC-2023-0052

Hi Salvatore, thanks for filing this bug. > Please see https://rustsec.org/advisories/RUSTSEC-2023-0052.html . This page is giving a very general description of the problem: >> When this crate is given a pathological certificate chain to validate, it >> will spend CPU time exponential with

Bug#1050592: marked as done (perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl)

Your message dated Fri, 08 Sep 2023 20:50:10 + with message-id and subject line Bug#1050592: fixed in glibc 2.37-8 has caused the Debian Bug report #1050592, regarding perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl to be marked as done. This means that you

Bug#1051287: marked as done (pike8.0-core: undeclared file conflict with former pike8.0-pcre)

Your message dated Fri, 08 Sep 2023 20:42:42 + with message-id and subject line Bug#1051287: fixed in pike8.0 8.0.1738-1.2 has caused the Debian Bug report #1051287, regarding pike8.0-core: undeclared file conflict with former pike8.0-pcre to be marked as done. This means that you claim that

Bug#1050592: marked as pending in glibc

Control: tag -1 pending Hello, Bug #1050592 in glibc 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: Bug#1050592 marked as pending in glibc

Processing control commands: > tag -1 pending Bug #1050592 [libc6-dev] perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl Added tag(s) pending. -- 1050592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050592 Debian Bug Tracking System Contact

Bug#1051355: Processed: your mail

Hi, On Fri, Sep 8, 2023 at 4:39 PM Andres Salomon wrote: > > > > On Fri, Sep 8 2023 at 03:31:37 PM -03:00:00, Leandro Cunha > wrote: > > Hi, On Fri, Sep 8, 2023 at 10:03 AM Debian Bug Tracking System > wrote: > > Processing commands for cont...@bugs.debian.org: > affects 1051355 phpsysinfo

Bug#1051287: NMU 8.0.1738-1.2

I am uploading a NMU to fix this.diff -Nru pike8.0-8.0.1738/debian/changelog pike8.0-8.0.1738/debian/changelog --- pike8.0-8.0.1738/debian/changelog 2023-08-22 11:50:42.0 + +++ pike8.0-8.0.1738/debian/changelog 2023-09-06 22:00:09.0 + @@ -1,3 +1,10 @@ +pike8.0

Bug#1051355: Processed: your mail

On Fri, Sep 8 2023 at 03:31:37 PM -03:00:00, Leandro Cunha wrote: Hi, On Fri, Sep 8, 2023 at 10:03 AM Debian Bug Tracking System mailto:ow...@bugs.debian.org>> wrote: Processing commands for cont...@bugs.debian.org : > affects 1051355 phpsysinfo

Bug#1051504: salt: CVE-2023-20897 CVE-2023-20898

Source: salt Version: 3004.1+dfsg-2.2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for salt. CVE-2023-20897[0]: | Salt masters prior to 3005.2 or 3006.2 contain a

Bug#1051355: Processed: your mail

Hi, On Fri, Sep 8, 2023 at 10:03 AM Debian Bug Tracking System wrote: > > Processing commands for cont...@bugs.debian.org: > > > affects 1051355 phpsysinfo phpldapadmin jquery-timepicker > Bug #1051355 [chromium] chromium: Segmentation fault > Added indication that 1051355 affects phpsysinfo,

Processed: severity of 1033316 is serious

Processing commands for cont...@bugs.debian.org: > severity 1033316 serious Bug #1033316 [src:ruby-moneta] Autopkgtest is flaky Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1033316:

Bug#1042911: marked as done (Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc)

Your message dated Fri, 08 Sep 2023 17:49:00 + with message-id and subject line Bug#1042911: fixed in muse-el 3.20+dfsg-8 has caused the Debian Bug report #1042911, regarding Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc to be

Bug#1051496: mailgraph: does not support the new syslog format

Package: mailgraph Version: 1.14-20 Severity: grave Justification: renders package unusable mailgraph no longer works after the upgrade to bookworm, and this is probably due to the fact that it does not support the new syslog format: /usr/sbin/mailgraph contains sub _next_syslog($) { [...]

Processed: Re: Error while importing Python "lensfun" module

Processing control commands: > tags -1 moreinfo unreproducible Bug #1050998 [python3-lensfun] Error while importing Python "lensfun" module Added tag(s) moreinfo and unreproducible. > severity -1 important Bug #1050998 [python3-lensfun] Error while importing Python "lensfun" module Severity set

Bug#1050998: Error while importing Python "lensfun" module

Control: tags -1 moreinfo unreproducible Control: severity -1 important On Fri, 1 Sep 2023 10:40:47 +0200 Thierry Florac wrote: I just installed the package "python3-lensfun" on Debian testing. When trying to import the module, an error occurs: *> python3* Python 3.9.15 (main, Nov 21 2022,

Processed: Re: Bug#1036737: libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from bullseye

Processing commands for cont...@bugs.debian.org: > severity 1036737 normal Bug #1036737 [libsoapysdr0.8] libsoapysdr0.8 is not co-installable with libsoapysdr0.7 Severity set to 'normal' from 'serious' > tags 1036737 - patch Bug #1036737 [libsoapysdr0.8] libsoapysdr0.8 is not co-installable with

Bug#1036737: libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from bullseye

severity 1036737 normal tags 1036737 - patch thanks [resend just to the bug because it was still archived before] On Thu, May 25, 2023 at 03:08:22AM +0200, Andreas Beckmann wrote: > The soapysdr library stacks from bullseye and bookworm are not > co-installable, but the transitive conflict

Bug#1051493: ghc: FTBFS with a GHC newer than 9.0.2

Source: ghc Version: 9.4.6-1 Severity: serious Tags: ftbfs Justification: FTBFS The current version of GHC in unstable (9.4.6-1) FTBFS when the bootstrap compiler is newer than 9.0.2. The error message is the following: ghc.mk:141: *** The make build system requires a boot compiler older

Bug#1051484: marked as done (dose3 FTBFS with ocamlgraph 2.0.0)

Your message dated Fri, 08 Sep 2023 16:19:12 + with message-id and subject line Bug#1051484: fixed in dose3 7.0.0-4 has caused the Debian Bug report #1051484, regarding dose3 FTBFS with ocamlgraph 2.0.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1050433: marked as done (src:sqlgrey: fails to migrate to testing for too long)

Your message dated Fri, 08 Sep 2023 16:06:31 + with message-id and subject line Bug#1050433: fixed in sqlgrey 1:1.8.0-5.1 has caused the Debian Bug report #1050433, regarding src:sqlgrey: fails to migrate to testing for too long to be marked as done. This means that you claim that the

Bug#1050299: marked as done (rust-webpki: RUSTSEC-2023-0052)

Your message dated Fri, 08 Sep 2023 16:06:25 + with message-id and subject line Bug#1050299: fixed in rust-webpki 0.22.1-1 has caused the Debian Bug report #1050299, regarding rust-webpki: RUSTSEC-2023-0052 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Bug#1051484 marked as pending in dose3

Processing control commands: > tag -1 pending Bug #1051484 [src:dose3] dose3 FTBFS with ocamlgraph 2.0.0 Added tag(s) pending. -- 1051484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1051484: marked as pending in dose3

Control: tag -1 pending Hello, Bug #1051484 in dose3 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:

Bug#1051475: marked as done (ledit: can't be built with arch:all+any)

Your message dated Fri, 08 Sep 2023 15:35:15 + with message-id and subject line Bug#1051475: fixed in ledit 2.04-7 has caused the Debian Bug report #1051475, regarding ledit: can't be built with arch:all+any to be marked as done. This means that you claim that the problem has been dealt

Processed (with 1 error): Re: Bug#1036737: libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from bullseye

Processing commands for cont...@bugs.debian.org: > unarchive 1036737 Bug #1036737 {Done: Andreas Beckmann } [libsoapysdr0.8] libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from bullseye Unarchived Bug 1036737 > reopen 1036737 Bug #1036737 {Done: Andreas Beckmann }

Processed: Bug#1051475 marked as pending in ledit

Processing control commands: > tag -1 pending Bug #1051475 [src:ledit] ledit: can't be built with arch:all+any Added tag(s) pending. -- 1051475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1051475: marked as pending in ledit

Control: tag -1 pending Hello, Bug #1051475 in ledit 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:

Bug#1051485: frama-c FTBFS with why3 1.6.0

Source: frama-c Version: 20220511-manganese-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=frama-c=amd64=20220511-manganese-4%2Bb5=1694181938=0 ... File "src/plugins/wp/ProverWhy3.ml", line 1129, characters 12-36: 1129 | let drv = Why3.Whyconf.load_driver

Bug#1051484: dose3 FTBFS with ocamlgraph 2.0.0

Source: dose3 Version: 7.0.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=dose3=amd64=7.0.0-3%2Bb1=1694182045=0 ... == FAIL: runTest (__main__.DoseTests.runTest) Test : ceve_cone_dot Group :

Bug#1051475: ledit: can't be built with arch:all+any

Le 08/09/2023 à 15:53, Gianfranco Costamagna a écrit : Hello, for some reasons, building ledit with arch:all + arch:any produces a ledit binary with an additional dependency on libstdlib-ocaml-lqmb5 This makes the arch:all package not binNMU safe, and then RC buggy. I think, for an arch:all

Bug#1050688: marked as done (poetry: needs internet access during build?)

Your message dated Fri, 08 Sep 2023 14:41:39 + with message-id and subject line Bug#1050688: fixed in poetry 1.6.1+dfsg-1 has caused the Debian Bug report #1050688, regarding poetry: needs internet access during build? to be marked as done. This means that you claim that the problem has been

Bug#1050687: marked as done (poetry: needs internet access during build?)

Your message dated Fri, 08 Sep 2023 14:41:39 + with message-id and subject line Bug#1050688: fixed in poetry 1.6.1+dfsg-1 has caused the Debian Bug report #1050688, regarding poetry: needs internet access during build? to be marked as done. This means that you claim that the problem has been

Processed: Bug#1050688 marked as pending in poetry

Processing control commands: > tag -1 pending Bug #1050688 [src:poetry] poetry: needs internet access during build? Bug #1050687 [src:poetry] poetry: needs internet access during build? Added tag(s) pending. Added tag(s) pending. -- 1050687:

Bug#1050688: marked as pending in poetry

Control: tag -1 pending Hello, Bug #1050688 in poetry 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:

Bug#1051475: ledit: can't be built with arch:all+any

Source: ledit Version: 2.04-6 Severity: serious Hello, for some reasons, building ledit with arch:all + arch:any produces a ledit binary with an additional dependency on libstdlib-ocaml-lqmb5 This makes the arch:all package not binNMU safe, and then RC buggy. I think, for an arch:all package

Bug#1051474: libreoffice: Please add embeded code copies to embeded-code-copies on security tracker debian.tar.xz/tarballs

Source: libreoffice Severity: serious Tags: security Justification: Document embdeded code copy + copyright X-Debbugs-Cc: Debian Security Team Dear Maintainer, Could you document that you embded a few tar ball under the security tracker ? For oldstable/stable/unstable Version should be

Processed: your mail

Processing commands for cont...@bugs.debian.org: > affects 1051355 phpsysinfo phpldapadmin jquery-timepicker Bug #1051355 [chromium] chromium: Segmentation fault Added indication that 1051355 affects phpsysinfo, phpldapadmin, and jquery-timepicker > stop Stopping processing here. Please contact

Processed: bug 1051454 is forwarded to https://code.videolan.org/rist/librist/-/issues/169

Processing commands for cont...@bugs.debian.org: > # many thanks to Simon McVittie for collecting this report > forwarded 1051454 https://code.videolan.org/rist/librist/-/issues/169 Bug #1051454 [src:librist] librist: FTBFS on 32-bit architectures: "Simple profile unicast packet loss" test

Bug#1025576: marked as done (libgsecuredelete: recommends transitional policykit-1 package)

Your message dated Fri, 08 Sep 2023 10:19:23 + with message-id and subject line Bug#1025576: fixed in libgsecuredelete 0.3-3.1 has caused the Debian Bug report #1025576, regarding libgsecuredelete: recommends transitional policykit-1 package to be marked as done. This means that you claim

Bug#1025576: libgsecuredelete: recommends transitional policykit-1 package

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru libgsecuredelete-0.3/debian/changelog libgsecuredelete-0.3/debian/changelog --- libgsecuredelete-0.3/debian/changelog 2021-01-12 15:17:08.0 +0100 +++ libgsecuredelete-0.3/debian/changelog 2023-09-08

Bug#1042199: marked as done (python-colour: FTBFS: ImportError: cannot import name '_get_unpatched' from 'setuptools.dist' (/usr/lib/python3/dist-packages/setuptools/dist.py))

Your message dated Fri, 08 Sep 2023 10:04:47 + with message-id and subject line Bug#1042199: fixed in python-colour 0.1.5-4 has caused the Debian Bug report #1042199, regarding python-colour: FTBFS: ImportError: cannot import name '_get_unpatched' from 'setuptools.dist'

Bug#1051454: librist: FTBFS on 32-bit architectures: "Simple profile unicast packet loss" test segfaults

Source: librist Version: 0.2.8+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The new version of librist in unstable is failing its build-time tests on all 32-bit architectures (armel, armhf, i386 and several ports

Processed: severity of 1051368 is normal

Processing commands for cont...@bugs.debian.org: > severity 1051368 normal Bug #1051368 [python3-selenium] python3-selenium: Selenium Python still can't find chromedriver Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: notfound 1030328 in 0.4.0-16

Processing commands for cont...@bugs.debian.org: > notfound 1030328 0.4.0-16 Bug #1030328 {Done: Bastian Germann } [src:quelcom] quelcom: FTBFS with TeXInfo 7.0.x No longer marked as found in versions quelcom/0.4.0-16. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#1051096: marked as done (nfoview: recommends a non-existent package)

Your message dated Fri, 8 Sep 2023 09:16:33 +0200 with message-id <20230908091633.3bca9...@debian.org> and subject line Re: Bug#1051096: nfoview: recommends a non-existent package has caused the Debian Bug report #1051096, regarding nfoview: recommends a non-existent package to be marked as done.

Bug#1051368: python3-selenium: Selenium Python still can't find chromedriver

Control: tags -1 severity normal Hello Jonathan, Am Wed, Sep 06, 2023 at 04:37:28PM -0400 schrieb Jonathan Kamens: > Opening a new ticket since bug 1050378 is resolved and I don't know > how to reopen a resolved ticket (nor do I know if it is even possible > for me to reopen a resolved