Processed: limit source to linux, tagging 1092969

Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 1092969 + pending Bug #1092969 [src:linux] linux: building dkms modules fails with x86_64-linux-gnu-ld: rea

Bug#1092969: linux: building dkms modules fails with x86_64-linux-gnu-ld: read in flex scanner failed

Hi Andreas, On Tue, Jan 14, 2025 at 01:25:27AM +0100, Andreas Beckmann wrote: > Source: linux > Version: 6.13~rc6-1~exp1 > Severity: serious > > building dkms modules for 6.13 in experimental fails with: > > ... > # LD [M] dm-writeboost.ko > x86_64-linux-gnu-ld -r -m elf_x86_64 -z noexecstack

Bug#1088558: dkms: please do source-only upload to allow migration

Hi, The new version of dkms has fixed #1088558, yet not migratable: Migration status for dkms (3.0.13-1 to 3.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: ∙ ∙ Not built on buildd: arch all binaries uploaded by pere, a new source-only up

Bug#1090190: marked as done (amgcl: FTBFS: The following tests FAILED: 13 - test_pyamgcl (Failed))

Your message dated Tue, 14 Jan 2025 06:49:16 + with message-id and subject line Bug#1090190: fixed in amgcl 1.4.4-1 has caused the Debian Bug report #1090190, regarding amgcl: FTBFS: The following tests FAILED: 13 - test_pyamgcl (Failed) to be marked as done. This means that you claim that th

Bug#1092983: libosmo-sccp fails autopkg tests, blocking python3-defaults

Package: src:libosmo-sccp Version: 1.9.0+dfsg1-3 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.13 [...] 68s autopkgtest [22:50:12]: test can-link: ---] 68s can-link FAIL stderr: /tmp/autopkgtest-lxc.kzg7dxze/downtmp/bu

Bug#1090819: marked as done (src:votca: unsatisfied build dependency in testing: librdkit-dev)

Your message dated Mon, 13 Jan 2025 21:40:42 -0800 with message-id <20250114054041.ga18...@ofb.net> and subject line Re: [Debichem-devel] Bug#1090819: src:votca: unsatisfied build dependency in testing: librdkit-dev has caused the Debian Bug report #1090819, regarding src:votca: unsatisfied build

Bug#1092982: FTBFS: sphinx-build segfaults

Source: pymatgen Version: 2024.10.29+dfsg1-4 Severity: serious Tags: ftbfs When building in a local sbuild chroot: reading sources... [ 10%] pymatgen.analysis Matplotlib created a temporary cache directory at /tmp/matplotlib-1a_c8sx6 because the default path (/sbuild-nonexistent/.config/matplotli

Bug#1092981: Autopkgtests fail with Python 3.13: KeyError: 'l'

Source: pymatgen Version: 2024.10.29+dfsg1-4 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.13 https://ci.debian.net/packages/p/pymatgen/testing/amd64/56411098/ -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-

Bug#1092371: marked as done (valkey: CVE-2024-46981 CVE-2024-51741)

Your message dated Tue, 14 Jan 2025 04:21:34 + with message-id and subject line Bug#1092371: fixed in valkey 8.0.2+dfsg1-1 has caused the Debian Bug report #1092371, regarding valkey: CVE-2024-46981 CVE-2024-51741 to be marked as done. This means that you claim that the problem has been dealt

Bug#1082555: marked as done (sslh blocks when reading data in some systems)

Your message dated Mon, 13 Jan 2025 19:34:08 -0800 with message-id and subject line Select blocking on some archs Fixed in 2.1.4-1 has caused the Debian Bug report #1082555, regarding sslh blocks when reading data in some systems to be marked as done. This means that you claim that the problem h

Bug#1092851: marked as done (tiny-initramfs-core: Fails to be installed after migrating to /usr/libexec/tiny-initramfs)

Your message dated Tue, 14 Jan 2025 02:42:33 + with message-id and subject line Bug#1092851: fixed in tiny-initramfs 0.1-6.1 has caused the Debian Bug report #1092851, regarding tiny-initramfs-core: Fails to be installed after migrating to /usr/libexec/tiny-initramfs to be marked as done. Th

Bug#1092851: tiny-initramfs-core: Fails to be installed after migrating to /usr/libexec/tiny-initramfs

Hi, Cyril Brulebois (2025-01-14): > Yes, I've just hit this too, trying to install a newer linux-image > package in my sid chroot, and I concur with your analysis: this looks > like an incomplete move and I don't understand how this could possibly > work without an accompanying change in the shel

Bug#1092865: marked as done (kodi: FTBFS with taglib 2.0 on 32 bit architectures)

Your message dated Tue, 14 Jan 2025 01:20:38 + with message-id and subject line Bug#1092865: fixed in kodi 2:21.1+dfsg-8 has caused the Debian Bug report #1092865, regarding kodi: FTBFS with taglib 2.0 on 32 bit architectures to be marked as done. This means that you claim that the problem ha

Processed: Re: Bug#1092414: neovim: FTBFS: make[1]: *** [debian/rules:129: override_dh_auto_test-arch] Error 1

Processing control commands: > severity -1 important Bug #1092414 [src:neovim] neovim: FTBFS: make[1]: *** [debian/rules:129: override_dh_auto_test-arch] Error 1 Severity set to 'important' from 'serious' -- 1092414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092414 Debian Bug Tracking

Bug#1091945: org-roam: FTBFS: error: (void-function emacsql-sqlite)

Hi Sean, Sean Whitton writes: > Hello, > > On Fri 10 Jan 2025 at 02:34pm -08, Xiyue Deng wrote: > >> Thanks for bringing up this. I checked the uscan manual and it said >> that the default for "gitmode" is "shallow", so AIUI it shouldn't be >> that costly, right? > > That didn't exist before, s

Bug#1091749: marked as done (src:tellico: unsatisfied build dependency in testing: libkf5cddb-dev)

Your message dated Mon, 13 Jan 2025 20:06:41 -0500 with message-id and subject line Re: src:tellico: unsatisfied build dependency in testing: libkf5cddb-dev has caused the Debian Bug report #1091749, regarding src:tellico: unsatisfied build dependency in testing: libkf5cddb-dev to be marked as do

Bug#1074854: brasero: FTBFS with gcc-14

On Sun, Jan 12, 2025 at 5:20 PM Simon McVittie wrote: > On Sun, 12 Jan 2025 at 12:28:10 +, Simon McVittie wrote: > > I have a USB optical drive and some media, so I can at least do a > > smoke-test on it to get this RC bug fixed, assuming my blank media > > haven't completely delaminated by no

Bug#1092851: tiny-initramfs-core: Fails to be installed after migrating to /usr/libexec/tiny-initramfs

Control: tag -1 patch pending Hi Michael, Michael Krylov (2025-01-12): > Package: tiny-initramfs-core > Version: 0.1-6 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I tried installing the version 0.1-6 of this package along with > tiny-initramfs package (

Processed: Re: Bug#1092851: tiny-initramfs-core: Fails to be installed after migrating to /usr/libexec/tiny-initramfs

Processing control commands: > tag -1 patch pending Bug #1092851 [tiny-initramfs-core] tiny-initramfs-core: Fails to be installed after migrating to /usr/libexec/tiny-initramfs Added tag(s) pending and patch. -- 1092851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092851 Debian Bug Track

Bug#1092969: linux: building dkms modules fails with x86_64-linux-gnu-ld: read in flex scanner failed

Source: linux Version: 6.13~rc6-1~exp1 Severity: serious building dkms modules for 6.13 in experimental fails with: ... # LD [M] dm-writeboost.ko x86_64-linux-gnu-ld -r -m elf_x86_64 -z noexecstack --no-warn-rwx-segments --build-id=sha1 -T /usr/src/linux-headers-6.13-rc6-amd64/ -o dm-writebo

Processed: severity of 885563 is important

Processing commands for cont...@bugs.debian.org: > severity 885563 important Bug #885563 [src:vte] vte: Do not release with forky Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 885563: https://bugs.debian.org/cgi-bin/bug

Processed: Fixed in ddate upstream

Processing commands for cont...@bugs.debian.org: > tags 1091251 patch fixed-upstream Bug #1091251 [src:ddate] ddate: FTBFS on armhf: ddate.c:234:24: error: passing argument 1 of ‘localtime’ from incompatible pointer type [-Wincompatible-pointer-types] Added tag(s) patch and fixed-upstream. > tha

Bug#1091251: Fixed in ddate upstream

tags 1091251 patch fixed-upstream thanks This was fixed upstream in 2015 (patch attached): https://github.com/bo0ts/ddate/commit/ac96f247c7a735daed1a8e1b4fa18560ab52 /Gwen -- Sitting in muddy water isn't such as a bad life if it ends after the first time >From ac96f247c7a735daed1a8e1b4f

Bug#1092963: korganizer: Each action in Korganizer are extremely slow since last debian testing update of kdepim6

Control: severity -1 important Hej, Am Montag, 13. Januar 2025, 23:50:06 MEZ schrieb Alexandre Bonneau: > Package: korganizer > Version: 4:24.12.0-3 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: alexandre.bonn...@linuxfr.eu > > Dear Maintainer, > >* What led up

Processed: Re: Bug#1092963: korganizer: Each action in Korganizer are extremely slow since last debian testing update of kdepim6

Processing control commands: > severity -1 important Bug #1092963 [korganizer] korganizer: Each action in Korganizer are extremely slow since last debian testing update of kdepim6 Severity set to 'important' from 'grave' -- 1092963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092963 Debi

Bug#1091045: marked as done (r-bioc-cummerbund: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 23:41:35 +0100 with message-id <9cc525e9-fd08-4e86-a9e4-891835640...@debian.org> and subject line Re: r-bioc-cummerbund: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091045, regarding r-bioc-cummerbund: FTBFS: build

Bug#1092963: korganizer: Each action in Korganizer are extremely slow since last debian testing update of kdepim6

Package: korganizer Version: 4:24.12.0-3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: alexandre.bonn...@linuxfr.eu Dear Maintainer, * What led up to the situation? Last week (approx 2025-01-06) I updated Debian testing with all the new akonadi, korganizer and kdepim6 p

Bug#1091048: marked as done (r-bioc-biovizbase: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 23:47:27 +0100 with message-id and subject line Re: r-bioc-biovizbase: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091048, regarding r-bioc-biovizbase: FTBFS: build-dependency not installable: r-api-bioc-3.20 to

Bug#1091066: marked as done (r-bioc-genomicfiles: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 23:46:50 +0100 with message-id <347a4e55-b866-4e11-aef2-5db146716...@debian.org> and subject line Re: r-bioc-genomicfiles: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091066, regarding r-bioc-genomicfiles: FTBFS: b

Bug#1091065: marked as done (r-bioc-gviz: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 23:43:17 +0100 with message-id <2453d1a0-13cc-451e-95a8-a838740b8...@debian.org> and subject line Re: r-bioc-gviz: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091065, regarding r-bioc-gviz: FTBFS: build-dependency

Bug#1091060: marked as done (r-bioc-purecn: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 23:42:44 +0100 with message-id and subject line Re: r-bioc-purecn: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091060, regarding r-bioc-purecn: FTBFS: build-dependency not installable: r-api-bioc-3.20 to be marke

Bug#1091066: r-bioc-genomicfiles: FTBFS: build-dependency not installable: r-api-bioc-3.20

Version: 1.42.0+dfsg-1 OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1091048: r-bioc-biovizbase: FTBFS: build-dependency not installable: r-api-bioc-3.20

Version: 1.54.0-1 OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1091044: marked as done (r-bioc-mutationalpatterns: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 23:39:16 +0100 with message-id and subject line Re: r-bioc-mutationalpatterns: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091044, regarding r-bioc-mutationalpatterns: FTBFS: build-dependency not installable: r-a

Bug#1087954: marked as done (ruby3.3: Fix FTBFS against openssl 3.4)

Your message dated Mon, 13 Jan 2025 22:39:56 + with message-id and subject line Bug#1087954: fixed in ruby3.3 3.3.6-1.1 has caused the Debian Bug report #1087954, regarding ruby3.3: Fix FTBFS against openssl 3.4 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1091043: marked as done (r-bioc-titancna: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 23:38:44 +0100 with message-id and subject line Re: r-bioc-titancna: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091043, regarding r-bioc-titancna: FTBFS: build-dependency not installable: r-api-bioc-3.20 to be m

Bug#1091505: marked as done (ruby3.3: Tries to access Internet during build)

Your message dated Mon, 13 Jan 2025 22:39:56 + with message-id and subject line Bug#1091505: fixed in ruby3.3 3.3.6-1.1 has caused the Debian Bug report #1091505, regarding ruby3.3: Tries to access Internet during build to be marked as done. This means that you claim that the problem has been

Bug#1091051: marked as done (r-bioc-ensembldb: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 23:35:11 +0100 with message-id <711ecf1e-48ae-439a-8b61-29d7f9426...@debian.org> and subject line Re: r-bioc-ensembldb: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091051, regarding r-bioc-ensembldb: FTBFS: build-d

Bug#1091080: marked as done (r-bioc-variantannotation: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 23:35:51 +0100 with message-id <3d72d5b3-cacd-4d50-85c6-f7fcc9b2e...@debian.org> and subject line Re: r-bioc-variantannotation: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091080, regarding r-bioc-variantannotation

Bug#1091041: marked as done (r-bioc-edaseq: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 23:34:38 +0100 with message-id <230c141d-8e42-4fc6-8d8d-deade4b4e...@debian.org> and subject line Re: r-bioc-edaseq: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091041, regarding r-bioc-edaseq: FTBFS: build-depende

Bug#1091026: marked as done (r-bioc-structuralvariantannotation: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 23:37:49 +0100 with message-id and subject line Re: r-bioc-structuralvariantannotation: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091026, regarding r-bioc-structuralvariantannotation: FTBFS: build-dependency not

Bug#1092533: jupyter-client: FTBFS: make[2]: *** [Makefile:55: html] Error 2

On Mon, Jan 13, 2025 at 06:36:40PM +1100, Stuart Prescott wrote: > Control: tags -1 + patch > > On 13/01/2025 12:59, Stuart Prescott wrote: > > The error «(SEVERE/4) Unexpected section title.» is about the Parameters > > and Returns headings that are inserted into the API docs (running sphinx > >

Bug#1092533: marked as done (jupyter-client: FTBFS: make[2]: *** [Makefile:55: html] Error 2)

Your message dated Mon, 13 Jan 2025 21:34:46 + with message-id and subject line Bug#1092533: fixed in jupyter-client 8.6.3-2 has caused the Debian Bug report #1092533, regarding jupyter-client: FTBFS: make[2]: *** [Makefile:55: html] Error 2 to be marked as done. This means that you claim tha

Bug#1092204: marked as done (odb still b-d's on GCC 12, which should not be part of the trixie release)

Your message dated Mon, 13 Jan 2025 21:35:06 + with message-id and subject line Bug#1092204: fixed in odb 2.4.0-17 has caused the Debian Bug report #1092204, regarding odb still b-d's on GCC 12, which should not be part of the trixie release to be marked as done. This means that you claim th

Bug#1087970: pep8: old version of pycodestyle

Hi, I agree with you & fixed actdiag & seqdiag right now. But, as long as pep8 is a key package (from cloud-init); and there's no autoremoval kicking in this message here will stay unread. Please consider sending an MBF. Greetings, Alexandre Debian Cloud Team cloud-init Debian FreeIP

Bug#1091054: marked as done (r-bioc-ioniser: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 22:15:02 +0100 with message-id <2f301a31-3c99-4cfc-905e-f7aa9b671...@debian.org> and subject line Re: r-bioc-ioniser: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091054, regarding r-bioc-ioniser: FTBFS: build-depen

Bug#1091053: marked as done (r-bioc-genomicfeatures: FTBFS: build-dependency not installable: r-api-bioc-3.20)

Your message dated Mon, 13 Jan 2025 22:08:22 +0100 with message-id <86b90f13-b464-403a-9074-3f85c9605...@debian.org> and subject line Re: r-bioc-genomicfeatures: FTBFS: build-dependency not installable: r-api-bioc-3.20 has caused the Debian Bug report #1091053, regarding r-bioc-genomicfeatures: FT

Bug#1092533: marked as pending in jupyter-client

Control: tag -1 pending Hello, Bug #1092533 in jupyter-client 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/python-team/packages/jupyter-client/-/commit/ed70b

Processed: Bug#1092533 marked as pending in jupyter-client

Processing control commands: > tag -1 pending Bug #1092533 [src:jupyter-client] jupyter-client: FTBFS: make[2]: *** [Makefile:55: html] Error 2 Added tag(s) pending. -- 1092533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092533 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Bug#1090290: marked as pending in qtnetworkauth-opensource-src

Control: tag -1 pending Hello, Bug #1090290 in qtnetworkauth-opensource-src 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/qt-kde-team/qt/qtnetworkauth/-/comm

Processed: Bug#1090290 marked as pending in qtnetworkauth-opensource-src

Processing control commands: > tag -1 pending Bug #1090290 [src:qtnetworkauth-everywhere-src] qtnetworkauth-everywhere-src: FTBFS: failing tests Added tag(s) pending. -- 1090290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090290 Debian Bug Tracking System Contact ow...@bugs.debian.org w

Bug#1092354: python3-vtk9: segfault on Python 3.13

On 2025-01-13 21:12, Drew Parsons wrote: Both these patches landed in vtk 9.4, so the simplest fix is to upgrade to the latest upstream release. Well, maybe not the "simplest" fix since it will need new binary package libvtk9.4. But that needs to be done sooner or later.

Processed: Re: Bug#1090290: qtnetworkauth-everywhere-src: FTBFS: failing tests

Processing control commands: > tags -1 - unreproducible Bug #1090290 [src:qtnetworkauth-everywhere-src] qtnetworkauth-everywhere-src: FTBFS: failing tests Removed tag(s) unreproducible. > severity -1 serious Bug #1090290 [src:qtnetworkauth-everywhere-src] qtnetworkauth-everywhere-src: FTBFS: fai

Bug#1092956: progress-linux-container: incorrect --rename flags in duplicated diversions (DEP17)

Source: progress-linux-metapackages Version: 20221002-20 Severity: serious Tags: patch User: helm...@debian.org Usertags: dep17 Hi, I'm sorry to tell you that I still got the duplicated diversions wrong. The full story is at https://lists.debian.org/debian-devel/2025/01/msg00125.html. In any case

Bug#1092354: python3-vtk9: segfault on Python 3.13

Package: vtk9 Followup-For: Bug #1092354 Control: forwarded 1092354 https://gitlab.kitware.com/vtk/vtk/-/issues/19466 Reported and fixed upstream, https://gitlab.kitware.com/vtk/vtk/-/merge_requests/11486 Found also in paraview, which shamefully ships its own vtk and needs the same patch. There

Processed: Re: python3-vtk9: segfault on Python 3.13

Processing control commands: > forwarded 1092354 https://gitlab.kitware.com/vtk/vtk/-/issues/19466 Bug #1092354 [python3-vtk9] python3-vtk9: segfault on Python 3.13 Set Bug forwarded-to-address to 'https://gitlab.kitware.com/vtk/vtk/-/issues/19466'. -- 1092354: https://bugs.debian.org/cgi-bin/b

Bug#1092955: bfh-metapackages: incorrect --rename flags in duplicated diversions (DEP17)

Package: bfh-container Version: 20211009-31 Severity: serious Tags: patch User: helm...@debian.org Usertags: dep17 Hi, I'm sorry to tell you that I still got the duplicated diversions wrong. The full story is at https://lists.debian.org/debian-devel/2025/01/msg00125.html. In any case, I managed t

Processed: forw

Processing commands for cont...@bugs.debian.org: > forwarded 1092791 https://github.com/opencobra/cobrapy/pull/1412 Bug #1092791 [src:python-cobra] FTBFS: TypeError: GPR.__init__() takes from 1 to 2 positional arguments but 3 were given Set Bug forwarded-to-address to 'https://github.com/opencob

Bug#1092688: ocaml-taglib: FTBFS with taglib 2.0

Control: forwarded -1 https://github.com/savonet/ocaml-taglib/issues/12 Hi, On Fri, 10 Jan 2025 12:44:42 -0500 Boyuan Yang wrote: > Source: ocaml-taglib > Version: 0.3.10-3 > Severity: important > User: debian-multime...@lists.debian.org > Usertags: taglib2.0 > > The package fails to build with

Processed: Re: ocaml-taglib: FTBFS with taglib 2.0

Processing control commands: > forwarded -1 https://github.com/savonet/ocaml-taglib/issues/12 Bug #1092688 [src:ocaml-taglib] ocaml-taglib: FTBFS with taglib 2.0 Set Bug forwarded-to-address to 'https://github.com/savonet/ocaml-taglib/issues/12'. -- 1092688: https://bugs.debian.org/cgi-bin/bugr

Bug#1092514: marked as done (libelogind tests fail with sbuild unshare backend)

Your message dated Mon, 13 Jan 2025 19:20:01 + with message-id and subject line Bug#1092514: fixed in elogind 255.5-1debian5 has caused the Debian Bug report #1092514, regarding libelogind tests fail with sbuild unshare backend to be marked as done. This means that you claim that the problem

Bug#1092075: [Debian-med-packaging] Bug#1092075: NMU: libsbml ftbfs with Python 3.13 as the default

Hi Bastian, Bastian Germann, on 2025-01-09: > I am uloading a NMU to fix this and the other open bugs. > The debdiff is attached. Thank you for your contribution, I have recorded your changes in the Salsa repository. Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6

Bug#1091873: octave-statistics: flaky autopkgtest: seems to hang and times out

Hi, On 13-01-2025 14:20, Sébastien Villemot wrote: I’ve asked upstream for help because I fail to understand the problem at this stage. Is there anything particular to be aware of regarding the debCI amd64 runners? Our amd64 machine is extremely powerful: 256 GB RAM, 64 cores. It wouldn't be

Bug#1090219: marked as done (fasttrack-archive-keyring: FTBFS: make[1]: apt-key: No such file or directory)

Your message dated Mon, 13 Jan 2025 18:34:01 + with message-id and subject line Bug#1090219: fixed in fasttrack-archive-keyring 2025.01.13 has caused the Debian Bug report #1090219, regarding fasttrack-archive-keyring: FTBFS: make[1]: apt-key: No such file or directory to be marked as done.

Bug#1091453: marked as done (tuigreet - rust package updates.)

Your message dated Mon, 13 Jan 2025 18:35:40 + with message-id and subject line Bug#1091453: fixed in tuigreet 0.9.1-5 has caused the Debian Bug report #1091453, regarding tuigreet - rust package updates. to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1091560: marked as done (tuigreet: FTBFS on i386: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

Your message dated Mon, 13 Jan 2025 18:35:40 + with message-id and subject line Bug#1091560: fixed in tuigreet 0.9.1-5 has caused the Debian Bug report #1091560, regarding tuigreet: FTBFS on i386: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 to be marked as don

Bug#1092587: marked as done (debusine: autopkgtests are flaky on s390x)

Your message dated Mon, 13 Jan 2025 17:49:12 + with message-id and subject line Bug#1092587: fixed in debusine 0.8.1 has caused the Debian Bug report #1092587, regarding debusine: autopkgtests are flaky on s390x to be marked as done. This means that you claim that the problem has been dealt w

Bug#1091735: marked as done (radare2: FTBFS on armel: undefined reference to `__atomic_compare_exchange_8')

Your message dated Mon, 13 Jan 2025 17:36:21 + with message-id and subject line Bug#1091735: fixed in radare2 5.9.8+dfsg-2 has caused the Debian Bug report #1091735, regarding radare2: FTBFS on armel: undefined reference to `__atomic_compare_exchange_8' to be marked as done. This means that

Processed: [bts-link] source package llvm-toolchain-19

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package llvm-toolchain-19 > # 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.debian.o

Processed: [bts-link] source package src:debusine

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:debusine > # 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.debian.org Se

Processed: Re: Bug#1092532: terminator: FTBFS: SystemError: returned a result with an exception set

Processing control commands: > reassign -1 libvte-2.91-0 0.78.2-1 Bug #1092532 [src:terminator] terminator: FTBFS: SystemError: returned a result with an exception set Bug reassigned from package 'src:terminator' to 'libvte-2.91-0'. No longer marked as found in versions terminator/2.1.4-3. Ignori

Bug#1069969: marked as done (ruby3.1: CVE-2024-27282)

Your message dated Mon, 13 Jan 2025 17:22:14 + with message-id and subject line Bug#1069969: fixed in ruby3.1 3.1.2-8.5 has caused the Debian Bug report #1069969, regarding ruby3.1: CVE-2024-27282 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1087960: marked as done (ruby3.1: Fix FTBFS against openssl 3.4)

Your message dated Mon, 13 Jan 2025 17:22:14 + with message-id and subject line Bug#1087960: fixed in ruby3.1 3.1.2-8.5 has caused the Debian Bug report #1087960, regarding ruby3.1: Fix FTBFS against openssl 3.4 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1092532: terminator: FTBFS: SystemError: returned a result with an exception set

Control: reassign -1 libvte-2.91-0 0.78.2-1 Control: affects -1 src:terminator Control: tag -1 patch On Wed, Jan 08, 2025 at 08:41:46PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[1]: E

Bug#1092936: wrong package name in symbols file

If I apply this patch will it also fix #1092915 ? I want to know if I should close that bug in the changelog or will some other mechanism close that bug. -- john

Bug#1091276: marked as done (kile: FTBFS on armhf: configure fails to find Okular5)

Your message dated Mon, 13 Jan 2025 16:22:29 + with message-id and subject line Bug#1091276: fixed in kile 4:2.9.94-0.1 has caused the Debian Bug report #1091276, regarding kile: FTBFS on armhf: configure fails to find Okular5 to be marked as done. This means that you claim that the problem h

Bug#1091487: marked as done (kile: Kile does not start)

Your message dated Mon, 13 Jan 2025 16:22:29 + with message-id and subject line Bug#1091483: fixed in kile 4:2.9.94-0.1 has caused the Debian Bug report #1091483, regarding kile: Kile does not start to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1091483: marked as done (kile: Kile does not start)

Your message dated Mon, 13 Jan 2025 16:22:29 + with message-id and subject line Bug#1091483: fixed in kile 4:2.9.94-0.1 has caused the Debian Bug report #1091483, regarding kile: Kile does not start to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1082254: marked as done (python-pydub FTBFS with Python 3.13)

Your message dated Mon, 13 Jan 2025 15:46:28 + with message-id and subject line Bug#1092664: Removed package(s) from unstable has caused the Debian Bug report #1082254, regarding python-pydub FTBFS with Python 3.13 to be marked as done. This means that you claim that the problem has been deal

Processed: tagging 1064855

Processing commands for cont...@bugs.debian.org: > tags 1064855 + trixie sid Bug #1064855 [xfce4-power-manager] xfce4-power-manager: Display is shutdown despite activity Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064855: https:/

Bug#1092745: opensysusers: DEP17 diversions may delete systemd's systemd-sysuser

On 1/13/25 00:16, Chris Hofstaedtler wrote: Not having multiple implementors of the same functionality just for NIH-reasons, too. Ah, there we go... toxicity starts again. Aren't you guys tired of it? It's been a long time I am. FYI, that's what made me stop working on opensysusers, but I sti

Bug#1083120: marked as done (Viagee permanently disabled)

Your message dated Mon, 13 Jan 2025 15:47:02 + with message-id and subject line Bug#1092825: Removed package(s) from unstable has caused the Debian Bug report #1083120, regarding Viagee permanently disabled to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1092890: also affects lomiri-thumbnailer

Control: affects -1 lomiri-thumbnailer Similarly affects lomiri-thumbnailer... Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http

Processed: also affects lomiri-thumbnailer

Processing control commands: > affects -1 lomiri-thumbnailer Bug #1092890 [libglx-mesa0] mesa: regression in 24.3: software rendering crashes on ppc64el with segmentation fault Added indication that 1092890 affects lomiri-thumbnailer -- 1092890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Processed: affects lomiri-system-settings, lomiri-settings-components and like other Lomiri unit tests

Processing control commands: > affects -1 lomiri-system-settings Bug #1092890 [libglx-mesa0] mesa: regression in 24.3: software rendering crashes on ppc64el with segmentation fault Added indication that 1092890 affects lomiri-system-settings > affects -1 lomiri-settings-components Bug #1092890 [l

Bug#1092890: affects lomiri-system-settings, lomiri-settings-components and like other Lomiri unit tests

Control: affects -1 lomiri-system-settings Control: affects -1 lomiri-settings-components This issue also appears while running unit tests (qmltestrunner) of lomiri-system-settings and lomiri-settings-components on ppc64el and mips64el: (gdb) run -input /home/sunweaver/lomiri-settings-co

Bug#1092915: Not installable on t64 arches: Depends: libagg2 (>= 2.6.0) but it is not installable

On Mon, Jan 13, 2025 at 03:51:58PM +0100, Sven Eckelmann wrote: > Control: reassign -1 agg 1:2.7.0.r145+dfsg-1 > Control: retitle -1 Linked packages depends on libagg2 (>= 2.6.0) but it is > not installable > Control: affects -1 exactimage > > On Monday, 13 January 2025 12:45:06 CET Andrey Rakh

Bug#1092936: wrong package name in symbols file

Package: src:agg Version: 1:2.7.0.r145+dfsg-1 Severity: serious Tags: sid trixie patch agg has a wrong package name in the symbols file, generating invalid dependencies on armel and armhf. After this fix, all depending packages should be binNMUd. patch at http://launchpadlibrarian.net/7702996

Processed: affects 1092890

Processing commands for cont...@bugs.debian.org: > affects 1092890 src:pyside2 src:pyside6 Bug #1092890 [libglx-mesa0] mesa: regression in 24.3: software rendering crashes on ppc64el with segmentation fault Added indication that 1092890 affects src:pyside2 and src:pyside6 > thanks Stopping proces

Processed: Re: Bug#1092915: Not installable on t64 arches: Depends: libagg2 (>= 2.6.0) but it is not installable

Processing control commands: > reassign -1 agg 1:2.7.0.r145+dfsg-1 Bug #1092915 [exactimage] Not installable on t64 arches: Depends: libagg2 (>= 2.6.0) but it is not installable Bug reassigned from package 'exactimage' to 'agg'. No longer marked as found in versions exactimage/1.0.2-12. Ignoring

Bug#1092915: Not installable on t64 arches: Depends: libagg2 (>= 2.6.0) but it is not installable

Control: reassign -1 agg 1:2.7.0.r145+dfsg-1 Control: retitle -1 Linked packages depends on libagg2 (>= 2.6.0) but it is not installable Control: affects -1 exactimage On Monday, 13 January 2025 12:45:06 CET Andrey Rakhmatullin wrote: > Both exactimage and python3-exactimage depend on libagg2 w

Bug#1087306: marked as done (fonts-sahel: FTBFS: fontmake: Error: In 'Sahel.designspace': Compatibility check failed)

Your message dated Mon, 13 Jan 2025 17:48:31 +0330 with message-id and subject line has caused the Debian Bug report #1087306, regarding fonts-sahel: FTBFS: fontmake: Error: In 'Sahel.designspace': Compatibility check failed to be marked as done. This means that you claim that the problem has b

Processed: Re: Bug#1090290: qtnetworkauth-everywhere-src: FTBFS: failing tests

Processing control commands: > tags -1 + unreproducible Bug #1090290 [src:qtnetworkauth-everywhere-src] qtnetworkauth-everywhere-src: FTBFS: failing tests Added tag(s) unreproducible. > severity -1 important Bug #1090290 [src:qtnetworkauth-everywhere-src] qtnetworkauth-everywhere-src: FTBFS: fai

Bug#1090290: qtnetworkauth-everywhere-src: FTBFS: failing tests

Control: tags -1 + unreproducible Control: severity -1 important Hi Santiago! On Mon, Dec 16, 2024 at 05:52:32PM +, Santiago Vila wrote: > Package: src:qtnetworkauth-everywhere-src > Version: 5.15.15-2 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > During a rebuild of all packag

Bug#1089964: nvidia-tesla-470-kernel-dkms: Build error with kernel 6.12

Thank you Андрей Спицын, I got it working with the help of apt-src. $ uname --kernel-release 6.12.6-amd64 $ lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1)

Processed: closing 1091068

Processing commands for cont...@bugs.debian.org: > close 1091068 Bug #1091068 [src:tellico] tellico: FTBFS: The following packages have unmet dependencies: libksanecore6-1 : Breaks: libksanecore1 but 23.08.1-2+b1 is to be installed Marked Bug as done > thanks Stopping processing here. Please co

Processed: Re: Bug#1092384: krb5: FTBFS: make[1]: *** [debian/rules:111: override_dh_install-arch] Error 1

Processing commands for cont...@bugs.debian.org: > # use the right tag this time > tags 1092384 pending Bug #1092384 [src:krb5] krb5: FTBFS: make[1]: *** [debian/rules:111: override_dh_install-arch] Error 1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need as

Bug#1092384: krb5: FTBFS: make[1]: *** [debian/rules:111: override_dh_install-arch] Error 1

Control: tags -1 patch Niels Thykier: [...] Hi, For starters, tagging this one pending, since git now has a fix in the form of `Rules-Requires-Root: binary-targets`: https://salsa.debian.org/debian/krb5/-/blob/master/debian/control?ref_type=heads#L30 [...] The patch from Guillem looks p

Processed: Re: Bug#1092384: krb5: FTBFS: make[1]: *** [debian/rules:111: override_dh_install-arch] Error 1

Processing control commands: > tags -1 patch Bug #1092384 [src:krb5] krb5: FTBFS: make[1]: *** [debian/rules:111: override_dh_install-arch] Error 1 Ignoring request to alter tags of bug #1092384 to the same tags previously set -- 1092384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109238

Processed: severity of 1092562 is grave

Processing commands for cont...@bugs.debian.org: > severity 1092562 grave Bug #1092562 [unicode] unicode: fails after Python 3.13 upgrade Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1092562: https://bugs.debian.org/cgi-

  1   2   >