Bug#1071628: marked as done (python-pymysql: CVE-2024-36039)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 May 2024 06:49:24 + with message-id and subject line Bug#1071628: fixed in python-pymysql 1.1.1-1 has caused the Debian Bug report #1071628, regarding python-pymysql: CVE-2024-36039 to be marked as done. This means that you claim that the problem has been dealt with

Processed: Re: rdkit: FTBFS convert: Unable to read font (/usr/share/fonts/type1/gsfonts/n019003l.pfb).

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1069873 [src:rdkit] rdkit: FTBFS convert: Unable to read font (/usr/share/fonts/type1/gsfonts/n019003l.pfb). Severity set to 'important' from 'serious' -- 1069873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069873 Debian Bug Trac

Bug#1069873: rdkit: FTBFS convert: Unable to read font (/usr/share/fonts/type1/gsfonts/n019003l.pfb).

2024-05-27 Thread Andrius Merkys
Control: severity -1 important On Fri, 26 Apr 2024 09:25:06 +0300 Andrius Merkys wrote: Since I need to upload rdkit to experimental to deal with time_t64 transition, I am going to disable latexpdf documentation building for the time being and deal with this issue later. I have disabled late

Bug#1072074: 7zip has an undeclared file conflict

2024-05-27 Thread Helmut Grohne
Package: 7zip Version: 24.06+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + p7zip p7zip-full 7zip has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/bin/7z * /usr/bin/7za are contained in the pa

Processed: 7zip has an undeclared file conflict

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + p7zip p7zip-full Bug #1072074 [7zip] 7zip has an undeclared file conflict Added indication that 1072074 affects p7zip and p7zip-full -- 1072074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072074 Debian Bug Tracking System Contact ow...@bugs.deb

Processed: python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + nanopb Bug #1072073 [python3-proto-plus] python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py Added indication that 1072073 affects nanopb -- 1072073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Bug#1072073: python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py

2024-05-27 Thread Helmut Grohne
Package: python3-proto-plus Version: 1.23.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + nanopb python3-proto-plus has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/python3/dist-packages/proto/__in

Bug#1071843: marked as done (src:r-cran-pracma: fails to migrate to testing for too long: uploader built arch:all binary)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 May 2024 05:19:12 + with message-id and subject line Bug#1071843: fixed in r-cran-pracma 2.4.4-3 has caused the Debian Bug report #1071843, regarding src:r-cran-pracma: fails to migrate to testing for too long: uploader built arch:all binary to be marked as done. T

Bug#1064311: marked as done (rdkit: NMU diff for 64-bit time_t transition)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 May 2024 05:19:53 + with message-id and subject line Bug#1064311: fixed in rdkit 202309.3-4 has caused the Debian Bug report #1064311, regarding rdkit: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been de

Processed: tagging 1071360

2024-05-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1071360 + pending Bug #1071360 [src:rkward] rkward: FTBFS: rkward/rbackend/rkrbackend.cpp:948:47: error: format not a string literal and no format arguments Added tag(s) pending. > thanks Stopping processing here. Please contact me if you n

Bug#1072068: golang-github-elazarl-goproxy accesses network resources during the build

2024-05-27 Thread Jochen Sprickerhof
Source: golang-github-elazarl-goproxy Version: 1.1+git20231117.7cc037d+dfsg-1 Severity: serious Tags: sid trixie ftbfs Justification: Policy 4.9 X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, golang-github-elazarl-goproxy accesses network resour

Processed: golang-github-elazarl-goproxy accesses network resources during the build

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > affects -1 buildd.debian.org Bug #1072068 [src:golang-github-elazarl-goproxy] golang-github-elazarl-goproxy accesses network resources during the build Added indication that 1072068 affects buildd.debian.org -- 1072068: https://bugs.debian.org/cgi-bin/bugreport.cg

Bug#1068142: marked as done (Build-Depends on missing librust-quick-xml-0.31+default-dev)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 May 2024 01:42:28 +0100 with message-id <0533fb89-643b-451e-e23e-753797452...@debian.org> and subject line re: Build-Depends on missing librust-quick-xml-0.31+default-dev has caused the Debian Bug report #1068142, regarding Build-Depends on missing librust-quick-xml-0.31+

Bug#1069423: marked as done (fcoe-utils: FTBFS on armhf: lib/sa_log.c:185:45: error: format ‘%ld’ expects argument of type ‘long int’, but argument 3 has type ‘__time64_t’ {aka ‘long long int’} [-Werr

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 22:50:41 + with message-id and subject line Bug#1069423: fixed in fcoe-utils 1.0.34-6 has caused the Debian Bug report #1069423, regarding fcoe-utils: FTBFS on armhf: lib/sa_log.c:185:45: error: format ‘%ld’ expects argument of type ‘long int’, but argument

Bug#1071031: marked as done (ezurio-qcacld-2.0-dkms: several module build failures)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 22:08:13 + with message-id and subject line Bug#1071031: fixed in ezurio-qcacld-2.0-dkms 0.0~git20230623.2cd31b6-2 has caused the Debian Bug report #1071031, regarding ezurio-qcacld-2.0-dkms: several module build failures to be marked as done. This means t

Bug#1070839: marked as done (r-cran-data.table: autopkgtest regression on i386)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 22:08:32 + with message-id and subject line Bug#1070839: fixed in r-cran-data.table 1.15.4+dfsg-2 has caused the Debian Bug report #1070839, regarding r-cran-data.table: autopkgtest regression on i386 to be marked as done. This means that you claim that the

Bug#1071031: ezurio-qcacld-2.0-dkms: several module build failures

2024-05-27 Thread Johannes Schauer Marin Rodrigues
Hi, Quoting Andreas Beckmann (2024-05-27 18:52:58) > On 27/05/2024 18.32, Johannes Schauer Marin Rodrigues wrote: > > I'm inclined to just restrict the kernel to amd64, arm64 and riscv64 as the > > relevant hardware is unlikely (or rather impossible) to be found on other > > architectures. Or do y

Processed: affects 1072057

2024-05-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1072057 + src:jeepney src:pymodbus src:python-channels-redis > src:python-redis src:python-truststore src:streamlink src:vdirsyncer Bug #1072057 [python3-pytest-asyncio] python3-pytest-asyncio: AttributeError: 'FixtureDef' object has no

Processed: reassign 1072057 to python3-pytest-asyncio

2024-05-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1072057 python3-pytest-asyncio 0.20.3-1.2 Bug #1072057 [python3-pytest-ayncio] python3-pytest-asyncio: AttributeError: 'FixtureDef' object has no attribute 'unittest' Warning: Unknown package 'python3-pytest-ayncio' Bug reassigned from p

Bug#1072057: python3-pytest-asyncio: AttributeError: 'FixtureDef' object has no attribute 'unittest'

2024-05-27 Thread Timo Röhling
Package: python3-pytest-ayncio Version: 0.20.3-1.2 Severity: serious Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, pytest-asyncio has a regression with pytest 8.2. For your convenience, find attached a backported patch that will resolve the issue. Alternatively, y

Bug#1072056: texlive-bin: Migration blocker

2024-05-27 Thread Hilmar Preusse
Source: texlive-bin Version: 2024.20240313.70630+ds-2 Severity: grave Justification: renders package unusable Should not migrate to testing for now. H. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,

Bug#1071312: marked as done (guake-indicator: FTBFS: guake-indicator-ayatana.c:36:15: error: implicit declaration of function ‘IS_APP_INDICATOR’)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 21:04:02 + with message-id and subject line Bug#1071312: fixed in guake-indicator 1.4.5-3 has caused the Debian Bug report #1071312, regarding guake-indicator: FTBFS: guake-indicator-ayatana.c:36:15: error: implicit declaration of function ‘IS_APP_INDICATOR

Bug#1072055: texlive-base: Migration blocker

2024-05-27 Thread Hilmar Preusse
Source: texlive-base Version: 2024.20240401-2 Severity: grave Justification: renders package unusable Should not migrate to testing for now. H. -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problem

Bug#1072054: biber: Migration blocker

2024-05-27 Thread Hilmar Preusse
Source: biber Version: 2.20-2 Severity: grave biber should not migrate to testing for now. H. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Foreign Architectur

Bug#1072052: djangorestframework: regression with pytest 8.2 due to invalid config key

2024-05-27 Thread Timo Röhling
Source: djangorestframework Version: 3.15.1-1 Severity: serious Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, djangorestframework has an error in its setup.cfg, using the invalid key testspath instead of testpaths. Starting with pytest 8.2, this is no longer igno

Bug#1062645: marked as done (libsysstat: NMU diff for 64-bit time_t transition)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 13:44:55 -0700 with message-id and subject line Re: libsysstat: NMU diff for 64-bit time_t transition has caused the Debian Bug report #1062645, regarding libsysstat: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the

Bug#1059133: marked as done (libboost1.83-dev: Please add upstream fix needed for dogecoin)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 20:37:17 + with message-id and subject line Bug#1059133: fixed in boost1.83 1.83.0-3 has caused the Debian Bug report #1059133, regarding libboost1.83-dev: Please add upstream fix needed for dogecoin to be marked as done. This means that you claim that the

Processed: Re: Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1072012 {Done: gregor herrmann } [src:libxml-libxml-perl] libxml-libxml-perl: FTBFS with libxml2 >= 2.11 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug

Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11

2024-05-27 Thread gregor herrmann
Control: reopen -1 On Mon, 27 May 2024 19:03:56 +0200, gregor herrmann wrote: > As a quick bandaid to fix the FTBFS bug and unblock libxml2, I've > prepared an upload with only the one upstream commit added as an > additional quilt patch (which makes the test suite pass on sid and > trixie, i.e.

Processed: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 = Bug #1071007 {Done: Samuel Henrique } [sherlock] sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py Bug reopened Ignoring request to alter fixed versions of bug #1071007 to the same values previously set -- 1071007: https://bugs.debian

Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py

2024-05-27 Thread Samuel Henrique
Control: reopen -1 = > I have read the other replies to the bug, which I missed previously. > It's not upstream's intention to ship the modules in dist-packages. Nevermind this, I misread upstream's response. Upstream contacted me to ask about it and it's clear to me now. Nilson: > As Sherlock i

Bug#1071975: marked as done (dh-make: Don't include 'Multi-Arch: foreign' in debian/control)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 19:34:17 + with message-id and subject line Bug#1071975: fixed in dh-make 2.202402 has caused the Debian Bug report #1071975, regarding dh-make: Don't include 'Multi-Arch: foreign' in debian/control to be marked as done. This means that you claim that the p

Bug#1071272: marked as done (linux: building the bookworm-backports armhf kernel causes OOM on buildds)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 21:30:15 +0200 with message-id and subject line Re: Bug#1071272: linux: building the bookworm-backports armhf kernel causes OOM on buildds has caused the Debian Bug report #1071272, regarding linux: building the bookworm-backports armhf kernel causes OOM on bu

Bug#1071378: linux-image-6.7.12-686-pae: Crash during early boot

2024-05-27 Thread Salvatore Bonaccorso
Control: tags -1 - moreinfo unreproducible Control: found -1 6.8.11-1 Hi, On Mon, May 27, 2024 at 03:11:21PM +0200, Jörn Heusipp wrote: > > Hello! > > > I cannot reproduce this problem. > > So it might be probably somewhat system-specific. I have not tried other > i386 systems myself. > > > I

Processed: Re: Bug#1071378: linux-image-6.7.12-686-pae: Crash during early boot

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > tags -1 - moreinfo unreproducible Bug #1071378 [src:linux] linux-image-6.7.12-686-pae: Crash during early boot Removed tag(s) unreproducible and moreinfo. > found -1 6.8.11-1 Bug #1071378 [src:linux] linux-image-6.7.12-686-pae: Crash during early boot Marked as found

Processed: Bug#1071975 marked as pending in dh-make

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1071975 [src:dh-make] dh-make: Don't include 'Multi-Arch: foreign' in debian/control Added tag(s) pending. -- 1071975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071975 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Bug#1071975: marked as pending in dh-make

2024-05-27 Thread Baptiste Beauplat
Control: tag -1 pending Hello, Bug #1071975 in dh-make reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/dh-make/-/commit/cdf6d627b45ed8a6c655c4071cb30266f

Bug#1069909: dcraw: FTBFS due to conflicting memmem prototype

2024-05-27 Thread Filip Hroch
Dear Steve, thank you for your support. The build fail is appearing in Debian  now, as the compiler update consequence. Best regards, FH On Fri, 26 Apr 2024 15:01:22 -0700 Steve Langasek wrote: > Package: dcraw > Version: 9.28-5 > Severity: normal > Tags: patch > User: ubuntu-de...@lists.ubunt

Bug#1069909: dcraw: diff for NMU version 9.28-5.1

2024-05-27 Thread Filip Hroch
Dear Eriberto, thank you for preparing of the upload. I think it is completelly ready to be published thanks to you. Best regards, FH -- PS. Sorry I am late, the end semester is hectic. On Sat, 25 May 2024 12:37:33 -0300 Joao Eriberto Mota Filho wrote: > Control: tags 1069909 + pending > >

Bug#1072012: marked as done (libxml-libxml-perl: FTBFS with libxml2 >= 2.11)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 17:50:20 + with message-id and subject line Bug#1072012: fixed in libxml-libxml-perl 2.0207+dfsg+really+2.0134-2 has caused the Debian Bug report #1072012, regarding libxml-libxml-perl: FTBFS with libxml2 >= 2.11 to be marked as done. This means that you c

Bug#1061743: Gramps in Debian

2024-05-27 Thread Dr. Tobias Quathamer
Am 27.05.24 um 15:38 schrieb IOhannes m zmölnig (Debian GNU|Linux): On 5/26/24 23:56, Dr. Tobias Quathamer wrote: The package builds on my machine, although I had to disable a single test for now. You'll find it in the newly created patch. Maybe you have an idea what's causing the failure, so

Processed: severity of 1072004 is important

2024-05-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1072004 important Bug #1072004 [src:linux] linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci) Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you n

Processed: Bug#1072012 marked as pending in libxml-libxml-perl

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1072012 [src:libxml-libxml-perl] libxml-libxml-perl: FTBFS with libxml2 >= 2.11 Added tag(s) pending. -- 1072012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1072012: marked as pending in libxml-libxml-perl

2024-05-27 Thread gregor herrmann
Control: tag -1 pending Hello, Bug #1072012 in libxml-libxml-perl 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/perl-team/modules/packages/libxml-libxml-perl/

Processed: Re: Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #1072012 [src:libxml-libxml-perl] libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11 Bug 1072012 cloned as bug 1072037 > retitle -1 libxml-libxml-perl: FTBFS with libxml2 >= 2.11 Bug #1072012 [src:libxml-li

Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11

2024-05-27 Thread gregor herrmann
Control: clone -1 -2 Control: retitle -1 libxml-libxml-perl: FTBFS with libxml2 >= 2.11 Control: retitle -2 libxml-libxml-perl: update to current upstream release Control: severity -2 normal Control: tags -2 = trixie sid On Mon, 27 May 2024 22:12:06 +0800, Aron Xu wrote: > libxml2 has been update

Bug#1071031: ezurio-qcacld-2.0-dkms: several module build failures

2024-05-27 Thread Andreas Beckmann
On 27/05/2024 18.32, Johannes Schauer Marin Rodrigues wrote: I'm inclined to just restrict the kernel to amd64, arm64 and riscv64 as the relevant hardware is unlikely (or rather impossible) to be found on other architectures. Or do you think that this would be a bed "solution"? No objections.

Processed: severity of 1072012 is serious, tagging 1072012

2024-05-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1072012 serious Bug #1072012 [src:libxml-libxml-perl] libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11 Severity set to 'serious' from 'normal' > tags 1072012 + sid trixie fixed-upstream ftbfs

Processed: Re: Bug#1071552: Bug#1071552: gnupg: Please upgrade GnuPG >= 2.4.4, current GnuPG break Emacs's EasyPG

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1071552 [gnupg] GnuPG 2.2.42+ breaks emacs' EasyPG Severity set to 'serious' from 'important' -- 1071552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1071031: ezurio-qcacld-2.0-dkms: several module build failures

2024-05-27 Thread Johannes Schauer Marin Rodrigues
Hi Andreas, On Mon, 13 May 2024 10:32:23 +0200 Andreas Beckmann wrote: > The module fails to build for several architectures and kernel versions: > > Linux 6.6.*: > https://ci.debian.net/packages/e/ezurio-qcacld-2.0-dkms/testing/amd64/45828215/#L3674 > 243s > /var/lib/dkms/ezurio-qcacld-2.0/0.0

Processed: sslh: FTBFS randomly (sbuild hangs)

2024-05-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 851877 2.1.1-1 Bug #851877 [src:sslh] sslh: FTBFS randomly (sbuild hangs) Marked as found in versions sslh/2.1.1-1. > severity 851877 serious Bug #851877 [src:sslh] sslh: FTBFS randomly (sbuild hangs) Severity set to 'serious' from 'importan

Bug#1071575: dahdi-dkms: module fails to build for Linux 6.8.9: error: implicit declaration of function 'strlcpy'

2024-05-27 Thread Tzafrir Cohen
Hi, On Mon, May 27, 2024 at 10:26:45AM +0200, Diederik de Haas via Pkg-voip-maintainers wrote: > Control: tag -1 upstream fixed-upstream patch Thanks for that. Just one note regarding the word "upstream". The current upstream of the package is the osmo fork. At the time when uploading previous v

Bug#1071575: dahdi-dkms: module fails to build for Linux 6.8.9: error: implicit declaration of function 'strlcpy'

2024-05-27 Thread Diederik de Haas
On Monday, 27 May 2024 17:25:02 CEST Tzafrir Cohen wrote: > Thanks for that. Just one note regarding the word "upstream". The > current upstream of the package is the osmo fork. At the time when > uploading previous version, that fork was looking more reliable than the > main branch. Yeah, it was/

Bug#1067663: marked as done (org-mode: CVE-2024-30202 CVE-2024-30205)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 14:32:34 + with message-id and subject line Bug#1067663: fixed in org-mode 9.4.0+dfsg-1+deb11u2 has caused the Debian Bug report #1067663, regarding org-mode: CVE-2024-30202 CVE-2024-30205 to be marked as done. This means that you claim that the problem has

Bug#1061743: Gramps in Debian

2024-05-27 Thread Debian GNU|Linux
On 5/26/24 23:56, Dr. Tobias Quathamer wrote: The package builds on my machine, although I had to disable a single test for now. You'll find it in the newly created patch. Maybe you have an idea what's causing the failure, so it can be fixed properly. https://gramps-project.org/bugs/view.php

Bug#1067717: marked as done (emacs-common: Security issues with emacs; remote code execution in Gnus)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 13:32:31 + with message-id and subject line Bug#1067630: fixed in emacs 1:27.1+1-3.1+deb11u3 has caused the Debian Bug report #1067630, regarding emacs-common: Security issues with emacs; remote code execution in Gnus to be marked as done. This means that

Bug#1067630: marked as done (emacs: CVE-2024-30202 CVE-2024-30203 CVE-2024-30204 CVE-2024-30205)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 13:32:31 + with message-id and subject line Bug#1067630: fixed in emacs 1:27.1+1-3.1+deb11u3 has caused the Debian Bug report #1067630, regarding emacs: CVE-2024-30202 CVE-2024-30203 CVE-2024-30204 CVE-2024-30205 to be marked as done. This means that you cl

Bug#1067717: marked as done (emacs-common: Security issues with emacs; remote code execution in Gnus)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 13:32:31 + with message-id and subject line Bug#1067630: fixed in emacs 1:27.1+1-3.1+deb11u4 has caused the Debian Bug report #1067630, regarding emacs-common: Security issues with emacs; remote code execution in Gnus to be marked as done. This means that

Bug#1067630: marked as done (emacs: CVE-2024-30202 CVE-2024-30203 CVE-2024-30204 CVE-2024-30205)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 13:32:31 + with message-id and subject line Bug#1067630: fixed in emacs 1:27.1+1-3.1+deb11u4 has caused the Debian Bug report #1067630, regarding emacs: CVE-2024-30202 CVE-2024-30203 CVE-2024-30204 CVE-2024-30205 to be marked as done. This means that you cl

Bug#1031888: marked as done (bullseye-pu: package emacs/27.1+1-3.1+deb11u4)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 13:32:31 + with message-id and subject line Bug#1031888: fixed in emacs 1:27.1+1-3.1+deb11u4 has caused the Debian Bug report #1031888, regarding bullseye-pu: package emacs/27.1+1-3.1+deb11u4 to be marked as done. This means that you claim that the problem

Bug#1071378: linux-image-6.7.12-686-pae: Crash during early boot

2024-05-27 Thread Jörn Heusipp
Hello! I cannot reproduce this problem. So it might be probably somewhat system-specific. I have not tried other i386 systems myself. If you still can with the recent 6.8.11-1 landed in unstable, 6.8.11-1 also crashes. you might try to bisect the changes in upstream kernel to determi

Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)

2024-05-27 Thread Thorsten Leemhuis
On 27.05.24 14:22, Luca Boccassi wrote: >> https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461 > > This has been reported upstream 3 weeks ago, but so far it seems no > action has been taken: > > https://lore.kernel.org/all/Zj0ErxVBE3DYT2Ea@gpd/ Hmmm, that thread is strange, why a

Bug#1066510: marked as done (hashrat: FTBFS: files.c:651:1: error: implicit declaration of function ‘MapClear’; did you mean ‘MapCreate’? [-Werror=implicit-function-declaration])

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 19:57:19 +0700 with message-id and subject line has caused the Debian Bug report #1066510, regarding hashrat: FTBFS: files.c:651:1: error: implicit declaration of function ‘MapClear’; did you mean ‘MapCreate’? [-Werror=implicit-function-declaration] to be mar

Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)

2024-05-27 Thread Luca Boccassi
On Mon, 27 May 2024 13:02:12 +0100 Luca Boccassi wrote: > Source: linux > Version: 6.8.9-1 > Severity: grave > Justification: breaks autopkgtest jobs running in qemu, breaking amd64 debci > X-Debbugs-CC: elb...@debian.org, m...@tls.msk.ru > > Hi, > > Kernel 6.8 includes this change: > > https:/

Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)

2024-05-27 Thread Luca Boccassi
Source: linux Version: 6.8.9-1 Severity: grave Justification: breaks autopkgtest jobs running in qemu, breaking amd64 debci X-Debbugs-CC: elb...@debian.org, m...@tls.msk.ru Hi, Kernel 6.8 includes this change: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80105ed2

Bug#1057544: barrier: FTBFS: failing test

2024-05-27 Thread Kentaro HAYASHI
I've just tried it with debian:sid container, it seems that there is no test failure about 4 reported failures. [ OK ] XWindowsKeyStateTests.setActiveGroup_poll_groupIsNotSet (21 ms) [ RUN ] XWindowsKeyStateTests.setActiveGroup_customGroup_groupWasSet [2024-05-27T11:26:31] DEBUG: openi

Bug#1071987: marked as done (python3-sqlalchemy: Missing version constraint in python3-typing-extensions dependency)

2024-05-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 May 2024 10:38:29 + with message-id and subject line Bug#1071987: fixed in sqlalchemy 2.0.30+ds1-2 has caused the Debian Bug report #1071987, regarding python3-sqlalchemy: Missing version constraint in python3-typing-extensions dependency to be marked as done. This

Bug#1068119: Solution for 1068119 - compile error for s390-tools 2.16.0-2

2024-05-27 Thread Steffen Eiden
Hi, this issue is already fixed upstream since v2.22.0. Do one of: - apply the upstream fix [1,2] - update your package to at least v2.22.0 The upstream fix disables the warning similar to the kernel[3] (see commit description) as there is no better solution for this as of now. I can ensure

Bug#1071319: libapache2-mod-auth-openidc: FTBFS: test/test fails

2024-05-27 Thread Moritz Schlarb
Thanks for the report, I suppose this is due to an algorithm support change in cjose - upstream fixed it in Git: https://github.com/OpenIDC/mod_auth_openidc/commit/1f2697468a505c66439117b769dbe6779d26968c On 17.05.24 22:38, Santiago Vila wrote: Package: src:libapache2-mod-auth-openidc Versio

Processed: reassign 1071319 to src:cjose, affects 1071319

2024-05-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1071319 src:cjose Bug #1071319 [src:libapache2-mod-auth-openidc] libapache2-mod-auth-openidc: FTBFS: test/test fails Bug reassigned from package 'src:libapache2-mod-auth-openidc' to 'src:cjose'. No longer marked as found in versions liba

Bug#1071296: blobwars: FTBFS: src/headers.h:60:20: error: ambiguating new declaration of ‘void strlcat(char*, const char*, size_t)’

2024-05-27 Thread Bo YU
Hi, On Fri, May 17, 2024 at 10:36:12PM +0200, Santiago Vila wrote: Package: src:blobwars Version: 2.00-4 Severity: serious Tags: ftbfs /usr/include/x86_64-linux-gnu/bits/string_fortified.h:167:1: note: old declaration ‘size_t strlcat(char*, const char*, size_t)’ 167 | __NTH (strlcat (char *__re

Bug#1071575: dahdi-dkms: module fails to build for Linux 6.8.9: error: implicit declaration of function 'strlcpy'

2024-05-27 Thread Diederik de Haas
On 27 May 2024 10:26:45 +0200 Diederik de Haas wrote: > Control: tag -1 upstream fixed-upstream patch > > On Tue, 21 May 2024 14:57:47 +0200 Andreas Beckmann wrote: > > Package: dahdi-dkms > > Version: 1:3.1.0+git20230717~dfsg-5 > > Severity: serious > > Attached is the upstream patch for compa

Bug#1067317: scons: FTBFS: Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so: libharfbuzz.so.0: cannot open shared object file: No su

2024-05-27 Thread Benjamin Drung
On Wed, 20 Mar 2024 22:04:03 +0100 Lucas Nussbaum wrote: > Source: scons > Version: 4.5.2+dfsg-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240319 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package

Processed: Re: dahdi-dkms: module fails to build for Linux 6.8.9: error: implicit declaration of function 'strlcpy'

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > tag -1 upstream fixed-upstream patch Bug #1071575 [dahdi-dkms] dahdi-dkms: module fails to build for Linux 6.8.9: error: implicit declaration of function 'strlcpy' Added tag(s) patch, upstream, and fixed-upstream. -- 1071575: https://bugs.debian.org/cgi-bin/bugrep

Bug#1071575: dahdi-dkms: module fails to build for Linux 6.8.9: error: implicit declaration of function 'strlcpy'

2024-05-27 Thread Diederik de Haas
Control: tag -1 upstream fixed-upstream patch On Tue, 21 May 2024 14:57:47 +0200 Andreas Beckmann wrote: > Package: dahdi-dkms > Version: 1:3.1.0+git20230717~dfsg-5 > Severity: serious > > DKMS make.log for dahdi-3.1.0+git20230717 for kernel 6.8.9-amd64 (x86_64) > Sun May 19 19:55:53 UTC 2024 >

Processed: severity of 1065973 is important

2024-05-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # tests disabled on 32 bit architectures > severity 1065973 important Bug #1065973 [src:kmod] kmod: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" Severity set to

Bug#1067545: klatexformula: diff for NMU version 4.1.0-1.1

2024-05-27 Thread pino
Control: tags 1067545 + patch Control: tags 1067545 + pending Dear maintainer, I've prepared an NMU for klatexformula (versioned as 4.1.0-1.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should delay it longer. Regards. diff -Nru klatexformula-4.1.0/debian/changelog klatex

Processed: klatexformula: diff for NMU version 4.1.0-1.1

2024-05-27 Thread Debian Bug Tracking System
Processing control commands: > tags 1067545 + patch Bug #1067545 [src:klatexformula] FTBFS on 32-bit time64 arches: cannot convert ‘long int*’ to ‘time_t*’ {aka ‘long long int*’} Added tag(s) patch. > tags 1067545 + pending Bug #1067545 [src:klatexformula] FTBFS on 32-bit time64 arches: cannot co