Bug#1021894: marked as done (openjfx: FTBFS on arm64 and armhf)

Your message dated Sun, 16 Jul 2023 05:51:46 + with message-id and subject line Bug#1021894: fixed in openjfx 11.0.11+1-3.1 has caused the Debian Bug report #1021894, regarding openjfx: FTBFS on arm64 and armhf to be marked as done. This means that you claim that the problem has been dealt

Bug#1021894: openjfx: FTBFS on arm64 and armhf

On Sat, Jul 15, 2023 at 01:46:02PM -0700, tony mancill wrote: > I intend to build and upload in the next few days, but you are welcome > to NMU if you would prefer. Uploaded as 11.0.11+1-3.1. (The version number was a slight mistake on my part; I meant to remove the NMU suffix in the changelog

Processed: Bug#1021894 marked as pending in openjfx

Processing control commands: > tag -1 pending Bug #1021894 [src:openjfx] openjfx: FTBFS on arm64 and armhf Added tag(s) pending. -- 1021894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1021894: marked as pending in openjfx

Control: tag -1 pending Hello, Bug #1021894 in openjfx 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#1037685: guitarix: ftbfs with GCC-13

Hi This bug is already fixed in upstream, here is the related patch: https://github.com/brummer10/guitarix/commit/b52736180b6966f24398f8a5ad179a58173473ec regards hermann

Processed: Bug#1038486 marked as pending in devscripts

Processing control commands: > tag -1 pending Bug #1038486 {Done: Paul Gevers } [src:devscripts] devscripts: FTBFS + autopkgtest failure with libgitlab-api-v4-perl 0.27-1 Bug #1041220 {Done: Paul Gevers } [src:devscripts] src:libgitlab-api-v4-perl: fails to migrate to testing for too long:

Processed: reassign 1041220 to src:devscripts, forcibly merging 1041220 1038486

Processing commands for cont...@bugs.debian.org: > reassign 1041220 src:devscripts Bug #1041220 {Done: Paul Gevers } [devscripts] src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts Bug reassigned from package 'devscripts' to

Bug#1038486: marked as pending in devscripts

Control: tag -1 pending Hello, Bug #1038486 in devscripts 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 (with 1 error): reassign 1041220 to devscripts, forcibly merging 1041220 1038486

Processing commands for cont...@bugs.debian.org: > reassign 1041220 devscripts Bug #1041220 {Done: Paul Gevers } [src:libgitlab-api-v4-perl] src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts Bug reassigned from package

Bug#1041220: src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts

On 7/15/23 22:46, Paul Gevers wrote: Source: libgitlab-api-v4-perl Version: 0.26-3 Severity: serious Control: close -1 0.27-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1038486 Dear maintainer(s), The Release Team considers packages

Bug#1041230: onetbb 2021.9.0-1 FTBFS on multiple release architectures

Source: onetbb Version: 2021.9.0-1 Severity: serious I'm aware of this issue. I'm slightly faster than buildd for toolchain upgrades. The issue will automatically disappear once our amd64 buildd migrates to gcc-13. The gcc-12 will lead to the FTBFS you see now. Local sbuild with gcc-13 has no

Bug#965826: marked as done (stalonetray: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Sat, 15 Jul 2023 23:21:48 + with message-id and subject line Bug#965826: fixed in stalonetray 0.8.3-1 has caused the Debian Bug report #965826, regarding stalonetray: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim

Bug#1041162: bogus test triggers with unused compilers

On 15/07/2023 12.11, Matthias Klose wrote: Package: src:dkms Version: 3.0.11-3 seen with https://ci.debian.net/data/autopkgtest/testing/amd64/d/dkms/35776414/log.gz That's an autopkgtest pinning problem: autopkgtest uses this command to build the list of binary packages to pin for these

Bug#1039583: libltdl-dev: missing Breaks+Replaces: libltdl3-dev

Hi, On 2023-06-27 14:50:30 +0200, Andreas Beckmann wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'lenny' to 'squeeze' to 'wheezy' to 'jessie' to 'stretch' to 'buster'. > It installed fine in 'lenny', and upgraded to 'squeeze', 'wheezy', > 'jessie', 'stretch',

Bug#1041207: debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE

Hi Adam, On Sat, 15 Jul 2023 18:27:24 +0200 Adam Borowski wrote: Packages built in an usrmerged chroot place such files under /usr while built without usrmerge into whatever place they were installed to -- which is a direct breach of the ruling. Packages stage their files in debian/tmp or

Bug#1041229: dependency problems prevent configuration of libltdl-dev

And "apt install -f" cannot fix the error. I could downgrade the packages to testing (2.4.7-5), though. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP,

Bug#1037819: marked as done (pistache: ftbfs with GCC-13)

Your message dated Sat, 15 Jul 2023 22:26:12 + with message-id and subject line Bug#1037819: fixed in pistache 0.0.5+ds-5 has caused the Debian Bug report #1037819, regarding pistache: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1041207: marked as done (debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE)

Your message dated Sat, 15 Jul 2023 22:22:00 + with message-id and subject line Bug#1041207: fixed in debootstrap 1.0.128+nmu4 has caused the Debian Bug report #1041207, regarding debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE to be marked as done. This means that you

Bug#1041229: dependency problems prevent configuration of libltdl-dev

Package: libltdl-dev Version: 2.4.7-6 Severity: grave Justification: renders package unusable When upgrading, I got: E: Sub-process /usr/bin/dpkg returned an error code (1) dpkg: dependency problems prevent configuration of libltdl-dev:amd64: libltdl-dev:i386 (2.4.7-6) breaks libltdl3-dev and

Processed: transition: suitesparse

Processing control commands: > affects -1 + src:suitesparse Bug #1041227 [release.debian.org] transition: suitesparse Added indication that 1041227 affects src:suitesparse > forwarded -1 https://release.debian.org/transitions/html/auto-suitesparse.html Bug #1041227 [release.debian.org]

Bug#1037896: marked as done (widelands: ftbfs with GCC-13)

Your message dated Sat, 15 Jul 2023 21:10:05 + with message-id and subject line Bug#1037896: fixed in widelands 2:1.1-4 has caused the Debian Bug report #1037896, regarding widelands: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1037754: marked as done (limesuite: ftbfs with GCC-13)

Your message dated Sat, 15 Jul 2023 21:02:12 + with message-id and subject line Bug#1037754: fixed in limesuite 22.09.1+dfsg-2 has caused the Debian Bug report #1037754, regarding limesuite: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt

Bug#1037598: marked as done (capnproto: ftbfs with GCC-13)

Your message dated Sat, 15 Jul 2023 20:58:32 + with message-id and subject line Bug#1037598: fixed in capnproto 0.9.2-3 has caused the Debian Bug report #1037598, regarding capnproto: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1021894: openjfx: FTBFS on arm64 and armhf

Hi Wookey, Thank you for the investigation and the patch! I intend to build and upload in the next few days, but you are welcome to NMU if you would prefer. Cheers, tony On Fri, Jul 14, 2023 at 02:28:14PM +0100, Wookey wrote: > Source: openjfx > Followup-For: Bug #1021894 > > I was surprised

Bug#1040694: Proposing a way to solve #1040694

Hello Julien, I am writing to you in addition to the sole bug report as you are the uploader of coinor-cbc. Because we saw an ABI breakage between versions 2.10.8 and 2.10.10 which affects rdeps, I propose to: - Revert the version in unstable to 2.10.8, with upstream version number being

Bug#1037754: marked as pending in limesuite

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

Processing control commands: > tag -1 pending Bug #1037754 [src:limesuite] limesuite: ftbfs with GCC-13 Added tag(s) pending. -- 1037754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1041161: dkms autopkg test fails on arm64

On 15/07/2023 12.00, Matthias Klose wrote: 179s The following packages have unmet dependencies: 179s  libhwasan0 : Depends: gcc-13-base (= 13.1.0-8) but 13.1.0-6 is to be installed 179s E: Unable to correct problems, you have held broken packages. 179s E: Linux headers failed to install.

Processed: Xournal++ GCC 13 FTBFS fixed upstream

Processing control commands: > forwarded -1 > https://github.com/xournalpp/xournalpp/commit/9172ee831f4dfbb88dfeb13b66862e80e64a0d3f Bug #1037904 [src:xournalpp] xournalpp: ftbfs with GCC-13 Set Bug forwarded-to-address to

Bug#1037904: Xournal++ GCC 13 FTBFS fixed upstream

Control: forwarded -1 https://github.com/xournalpp/xournalpp/commit/9172ee831f4dfbb88dfeb13b66862e80e64a0d3f Control: tags -1 fixed-upstream It looks like this has been fixed upstream, so I'm setting the bug metadata as such. signature.asc Description: This is a digitally signed message part

Processed: notfixed 1037598 in 15.02.00-1

Processing commands for cont...@bugs.debian.org: > notfixed 1037598 15.02.00-1 Bug #1037598 [src:capnproto] capnproto: ftbfs with GCC-13 The source 'capnproto' and version '15.02.00-1' do not appear to match any binary packages Ignoring request to alter fixed versions of bug #1037598 to the same

Bug#1037857: closing 1037857

close 1037857 15.02.00-1 thanks Upstream 15.02.00 addressed the FTBFS with GCC-13.

Processed: closing 1037857

Processing commands for cont...@bugs.debian.org: > close 1037857 15.02.00-1 Bug #1037857 [src:simrisc] simrisc: ftbfs with GCC-13 Marked as fixed in versions simrisc/15.02.00-1. Bug #1037857 [src:simrisc] simrisc: ftbfs with GCC-13 Marked Bug as done > thanks Stopping processing here. Please

Processed: reopening 1037598

Processing commands for cont...@bugs.debian.org: > reopen 1037598 Bug #1037598 {Done: tony mancill } [src:capnproto] capnproto: ftbfs with GCC-13 '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#981869: marked as done (librust-tcmalloc-dev: Depends: librust-tcmalloc-sys-0.3+default-dev but it is not installable)

Your message dated Sat, 15 Jul 2023 19:09:04 + with message-id and subject line Bug#981869: fixed in rust-tcmalloc-sys 0.3.0-1 has caused the Debian Bug report #981869, regarding librust-tcmalloc-dev: Depends: librust-tcmalloc-sys-0.3+default-dev but it is not installable to be marked as

Bug#1037598: closing 1037598

close 1037598 15.02.00-1 thanks Upstream release 15.02.00 addressed the FTBFS with GCC-13.

Processed: closing 1037598

Processing commands for cont...@bugs.debian.org: > close 1037598 15.02.00-1 Bug #1037598 [src:capnproto] capnproto: ftbfs with GCC-13 The source 'capnproto' and version '15.02.00-1' do not appear to match any binary packages Marked as fixed in versions capnproto/15.02.00-1. Bug #1037598

Bug#1040855: marked as done (setuptools-scm autopkg test fail with setuptools 68)

Your message dated Sat, 15 Jul 2023 19:03:21 + with message-id and subject line Bug#1040855: fixed in setuptools-scm 7.1.0-4 has caused the Debian Bug report #1040855, regarding setuptools-scm autopkg test fail with setuptools 68 to be marked as done. This means that you claim that the

Bug#1041223: src:icingaweb2-module-graphite: fails to migrate to testing for too long: unresolved issues

Source: icingaweb2-module-graphite Version: 1.2.2-1 Severity: serious Control: close -1 1.2.2-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1038929 Dear maintainer(s), The Release Team considers packages that are out-of-sync between

Processed: src:icingaweb2-module-graphite: fails to migrate to testing for too long: unresolved issues

Processing control commands: > close -1 1.2.2-2 Bug #1041223 [src:icingaweb2-module-graphite] src:icingaweb2-module-graphite: fails to migrate to testing for too long: unresolved issues Marked as fixed in versions icingaweb2-module-graphite/1.2.2-2. Bug #1041223 [src:icingaweb2-module-graphite]

Processed: src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts

Processing control commands: > close -1 0.27-1 Bug #1041220 [src:libgitlab-api-v4-perl] src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts Marked as fixed in versions libgitlab-api-v4-perl/0.27-1. Bug #1041220

Bug#1041220: src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts

Source: libgitlab-api-v4-perl Version: 0.26-3 Severity: serious Control: close -1 0.27-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1038486 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing

Bug#1041219: src:basilisk2: fails to migrate to testing for too long: FTBFS on arm*

Source: basilisk2 Version: 0.9.20220710-1 Severity: serious Control: close -1 0.9.20230516-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 unstable for more

Processed: src:basilisk2: fails to migrate to testing for too long: FTBFS on arm*

Processing control commands: > close -1 0.9.20230516-1 Bug #1041219 [src:basilisk2] src:basilisk2: fails to migrate to testing for too long: FTBFS on arm* Marked as fixed in versions basilisk2/0.9.20230516-1. Bug #1041219 [src:basilisk2] src:basilisk2: fails to migrate to testing for too long:

Bug#1041218: src:ardour: fails to migrate to testing for too long: FTBFS on mips*el

Source: ardour Version: 1:7.3.0+ds0-1 Severity: serious Control: close -1 1:7.4.0+ds-1 Tags: sid trixie ftbfs 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

Processed: src:ardour: fails to migrate to testing for too long: FTBFS on mips*el

Processing control commands: > close -1 1:7.4.0+ds-1 Bug #1041218 [src:ardour] src:ardour: fails to migrate to testing for too long: FTBFS on mips*el Marked as fixed in versions ardour/1:7.4.0+ds-1. Bug #1041218 [src:ardour] src:ardour: fails to migrate to testing for too long: FTBFS on mips*el

Processed: Re: pylint: Regression with tomlkit 0.11.8, Fixed in 2.17.4

Processing control commands: > severity -1 serious Bug #1038258 [src:pylint] pylint: Regression with tomlkit 0.11.8, Fixed in 2.17.4 Severity set to 'serious' from 'important' -- 1038258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038258 Debian Bug Tracking System Contact

Processed: Bug#1040855 marked as pending in setuptools-scm

Processing control commands: > tag -1 pending Bug #1040855 [src:setuptools-scm] setuptools-scm autopkg test fail with setuptools 68 Added tag(s) pending. -- 1040855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1040855: marked as pending in setuptools-scm

Control: tag -1 pending Hello, Bug #1040855 in setuptools-scm 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: src:node-chart.js: fails to migrate to testing for too long: autopkgtest failure

Processing control commands: > close -1 3.9.1+~cs3.1.2-2 Bug #1041217 [src:node-chart.js] src:node-chart.js: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions node-chart.js/3.9.1+~cs3.1.2-2. Bug #1041217 [src:node-chart.js] src:node-chart.js: fails to

Bug#1041217: src:node-chart.js: fails to migrate to testing for too long: autopkgtest failure

Source: node-chart.js Version: 3.9.1+~0.2.1-2 Severity: serious Control: close -1 3.9.1+~cs3.1.2-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1039918 Dear maintainer(s), The Release Team considers packages that are out-of-sync

Processed (with 1 error): src:ruby-sidekiq: fails to migrate to testing for too long: autopkgtest failure

Processing control commands: > close -1 6.5.7+dfsg3-2 Bug #1041216 [src:ruby-sidekiq] src:ruby-sidekiq: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions ruby-sidekiq/6.5.7+dfsg3-2. Bug #1041216 [src:ruby-sidekiq] src:ruby-sidekiq: fails to migrate to

Bug#1041216: src:ruby-sidekiq: fails to migrate to testing for too long: autopkgtest failure

Source: ruby-sidekiq Version: 6.4.1+dfsg-1 Severity: serious Control: close -1 6.5.7+dfsg3-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: tags -1 by 1039921 Dear maintainer(s), The Release Team considers packages that are out-of-sync between

Processed: src:squeekboard: fails to migrate to testing for too long: FTBFS on mipsel

Processing control commands: > close -1 1.22.0-3 Bug #1041215 [src:squeekboard] src:squeekboard: fails to migrate to testing for too long: FTBFS on mipsel Marked as fixed in versions squeekboard/1.22.0-3. Bug #1041215 [src:squeekboard] src:squeekboard: fails to migrate to testing for too long:

Bug#1041215: src:squeekboard: fails to migrate to testing for too long: FTBFS on mipsel

Source: squeekboard Version: 1.21.0-1 Severity: serious Control: close -1 1.22.0-3 Tags: sid trixie ftbfs 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

Processed: src:mesa: fails to migrate to testing for too long: causes autopkgtest regression

Processing control commands: > close -1 23.1.3-1 Bug #1041214 [src:mesa] src:mesa: fails to migrate to testing for too long: causes autopkgtest regression Marked as fixed in versions mesa/23.1.3-1. Bug #1041214 [src:mesa] src:mesa: fails to migrate to testing for too long: causes autopkgtest

Bug#1041214: src:mesa: fails to migrate to testing for too long: causes autopkgtest regression

Source: mesa Version: 22.3.6-1+deb12u1 Severity: serious Control: close -1 23.1.3-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1039922 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and

Bug#1031306: marked as done (rust-criterion: autopkgtest regression)

Your message dated Sat, 15 Jul 2023 18:21:50 + with message-id and subject line Bug#1031306: fixed in rust-criterion 0.5.1-1 has caused the Debian Bug report #1031306, regarding rust-criterion: autopkgtest regression to be marked as done. This means that you claim that the problem has been

Processed: src:python-xarray: fails to migrate to testing for too long: FTBFS

Processing control commands: > close -1 2023.06.0-1 Bug #1041213 [src:python-xarray] src:python-xarray: fails to migrate to testing for too long: FTBFS The source 'python-xarray' and version '2023.06.0-1' do not appear to match any binary packages Marked as fixed in versions

Bug#1041213: src:python-xarray: fails to migrate to testing for too long: FTBFS

Source: python-xarray Version: 2023.01.0-1.1 Severity: serious Control: close -1 2023.06.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1039871 Dear maintainer(s), The Release Team considers packages that are out-of-sync between

Processed: forwarded 1040628 https://github.com/elceef/dnstwist/issues/194

Processing commands for cont...@bugs.debian.org: > forwarded 1040628 https://github.com/elceef/dnstwist/issues/194 Bug #1040628 [src:dnstwist] dnstwist autopkg tests fail with pillow 10.0.0 Set Bug forwarded-to-address to 'https://github.com/elceef/dnstwist/issues/194'. > End of message, stopping

Bug#1041211: libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit

Source: libsdl-perl, sdl12-compat Control: found -1 libsdl-perl/2.548-3 Control: found -1 sdl12-compat/1.2.64-5 Control: block 1039911 by -1 Severity: serious Tags: trixie sid ftbfs User: debian...@lists.debian.org Usertags: breaks needs-update Since sdl12-compat took over the libsdl1.2debian

Processed: libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit

Processing control commands: > found -1 libsdl-perl/2.548-3 Bug #1041211 [src:libsdl-perl, src:sdl12-compat] libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit Marked as found in versions libsdl-perl/2.548-3. > found -1 sdl12-compat/1.2.64-5 Bug #1041211

Bug#1041022: marked as done (easyloggingpp FTBFS with googletest 1.13.0)

Your message dated Sat, 15 Jul 2023 17:35:44 + with message-id and subject line Bug#1041022: fixed in easyloggingpp 9.97.0+dfsg-2 has caused the Debian Bug report #1041022, regarding easyloggingpp FTBFS with googletest 1.13.0 to be marked as done. This means that you claim that the problem

Bug#1037646: marked as done (falcosecurity-libs: ftbfs with GCC-13)

Your message dated Sat, 15 Jul 2023 17:36:12 + with message-id and subject line Bug#1037646: fixed in falcosecurity-libs 0.11.3+repack-1 has caused the Debian Bug report #1037646, regarding falcosecurity-libs: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem

Bug#1034881: marked as done (falcosecurity-scap-dkms: Cannot compile linux kernel 6.2.12 due to failure with scap dkms)

Your message dated Sat, 15 Jul 2023 17:36:12 + with message-id and subject line Bug#1034881: fixed in falcosecurity-libs 0.11.3+repack-1 has caused the Debian Bug report #1034881, regarding falcosecurity-scap-dkms: Cannot compile linux kernel 6.2.12 due to failure with scap dkms to be marked

Bug#1037605: marked as done (claws-mail: ftbfs with GCC-13)

Your message dated Sat, 15 Jul 2023 17:10:15 + with message-id and subject line Bug#1037605: fixed in claws-mail 4.1.1-3 has caused the Debian Bug report #1037605, regarding claws-mail: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1041024: marked as done (movit FTBFS with googletest 1.13.0)

Your message dated Sat, 15 Jul 2023 16:41:20 + with message-id and subject line Bug#1041024: fixed in movit 1.7.0-1 has caused the Debian Bug report #1041024, regarding movit FTBFS with googletest 1.13.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1037785: marked as done (nageru: ftbfs with GCC-13)

Your message dated Sat, 15 Jul 2023 16:41:29 + with message-id and subject line Bug#1037785: fixed in nageru 2.2.2-1 has caused the Debian Bug report #1037785, regarding nageru: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1039686: marked as done (nvidia-open-gpu-kernel-modules: CVE-2023-25515, CVE-2023-25516)

Your message dated Sat, 15 Jul 2023 16:32:11 + with message-id and subject line Bug#1039686: fixed in nvidia-open-gpu-kernel-modules 525.125.06-1~deb12u1 has caused the Debian Bug report #1039686, regarding nvidia-open-gpu-kernel-modules: CVE-2023-25515, CVE-2023-25516 to be marked as done.

Bug#1039685: marked as done (nvidia-graphics-drivers-tesla: CVE-2023-25515, CVE-2023-25516)

Your message dated Sat, 15 Jul 2023 16:32:11 + with message-id and subject line Bug#1039685: fixed in nvidia-graphics-drivers-tesla 525.125.06-1~deb12u1 has caused the Debian Bug report #1039685, regarding nvidia-graphics-drivers-tesla: CVE-2023-25515, CVE-2023-25516 to be marked as done.

Bug#1039678: marked as done (nvidia-graphics-drivers: CVE-2023-25515, CVE-2023-25516)

Your message dated Sat, 15 Jul 2023 16:32:11 + with message-id and subject line Bug#1039678: fixed in nvidia-graphics-drivers-tesla 525.125.06-1~deb12u1 has caused the Debian Bug report #1039678, regarding nvidia-graphics-drivers: CVE-2023-25515, CVE-2023-25516 to be marked as done. This

Bug#1039678: marked as done (nvidia-graphics-drivers: CVE-2023-25515, CVE-2023-25516)

Your message dated Sat, 15 Jul 2023 16:32:10 + with message-id and subject line Bug#1039678: fixed in nvidia-graphics-drivers 525.125.06-1~deb12u1 has caused the Debian Bug report #1039678, regarding nvidia-graphics-drivers: CVE-2023-25515, CVE-2023-25516 to be marked as done. This means

Processed: reassign 1040835 to src:rust-log, reassign 1040995 to src:rust-log ..., affects 1040837

Processing commands for cont...@bugs.debian.org: > reassign 1040835 src:rust-log Bug #1040835 [librust-async-std-dev] librust-async-std-dev: impossible to install: missing dependency librust-log-0.4+kv-unstable-dev Bug reassigned from package 'librust-async-std-dev' to 'src:rust-log'. No longer

Bug#1041207: debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE

Package: debootstrap Version: 1.0.128+nmu3 Severity: grave bluca's NMU on 2023-07-15 makes debootstrap produce chroots using the aliased-dirs scheme. While it's currently the default scheme for non-buildd systems, it is both not supported by dpkg (with no solution in sight), but is also likely

Processed (with 1 error): forcibly merging 1040837 1040835 1040995

Processing commands for cont...@bugs.debian.org: > forcemerge 1040837 1040835 1040995 Bug #1040837 [src:rust-log] rust-log: breaks API without coordination Unable to merge bugs because: package of #1040995 is 'librust-kv-log-macro-dev' not 'src:rust-log' package of #1040835 is

Processed: tagging 1037605

Processing commands for cont...@bugs.debian.org: > tags 1037605 + pending Bug #1037605 [src:claws-mail] claws-mail: ftbfs with GCC-13 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037605:

Bug#1037603: marked as done (civetweb: ftbfs with GCC-13)

Hi Sebastien, seems you closed the wrong bug with your upload. The package you uploaded is orthanc-postgresql but the bug concerns civetweb. Kind regards Andreas. Am Sat, Jul 15, 2023 at 12:09:18PM + schrieb Debian Bug Tracking System: > Your message dated Sat, 15 Jul 2023 12:07:17

Bug#1041206: python-clickhouse-driver: FTBFS if source is included: aborting due to unexpected upstream changes

Source: python-clickhouse-driver Version: 0.2.5-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! With any build type that includes the source, your package fails with: dpkg-source: info: local changes detected, the modified files

Bug#1041203: FTBFS: InvalidRequirement: Expected end or semicolon

Source: macs Version: 2.2.7.1-6 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! I'm afraid your package fails to build, with: pkg_resources.extern.packaging._tokenizer.ParserSyntaxError: Expected end or semicolon (after name and no

Bug#1017619: nautilus-wipe not present in bookworm

Dear nautilus-wipe maintainers and uploaders, I recently upgraded my system to debian 12 and I was surprised that nautilus-wipe was not present in bookworm and not even in testing. It is planned to add it back in testing from sid and maybe also add it to bookworm-backports? Thanks a lot for

Bug#1041138: marked as done (memtailor FTBFS with googletest 1.13.0)

Your message dated Sat, 15 Jul 2023 15:38:05 + with message-id and subject line Bug#1041138: fixed in memtailor 1.0~git20220104-2 has caused the Debian Bug report #1041138, regarding memtailor FTBFS with googletest 1.13.0 to be marked as done. This means that you claim that the problem has

Bug#1037565: marked as done (4ti2: ftbfs with GCC-13)

Your message dated Sat, 15 Jul 2023 15:21:32 + with message-id and subject line Bug#1037565: fixed in 4ti2 1.6.10+ds-1 has caused the Debian Bug report #1037565, regarding 4ti2: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1040837: [Pkg-rust-maintainers] Bug#1040837: rust-log: breaks API without coordination

Quoting Jonas Smedegaard (2023-07-15 09:55:04) > Quoting Fabian Grünbichler (2023-07-12 19:53:08) > > The feature in question is probably not a good candidate for packaging > > though, given the lack of stability guarantees provided by upstream[0]: > > > > > This module is unstable and breaking

Processed: owner 1041075

Processing commands for cont...@bugs.debian.org: > owner 1041075 ! Bug #1041075 [src:libphonenumber] libphonenumber FTBFS with googletest 1.13.0 Owner recorded as tony mancill . > thanks Stopping processing here. Please contact me if you need assistance. -- 1041075:

Bug#1037717: marked as done (libbpp-core: ftbfs with GCC-13)

Your message dated Sat, 15 Jul 2023 14:41:17 + with message-id and subject line Bug#1037717: fixed in libbpp-core 2.4.1-10 has caused the Debian Bug report #1037717, regarding libbpp-core: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: ca-certificates-java: openjdk-17 update caused install regressions

Processing control commands: > severity -1 critical Bug #1039472 [ca-certificates-java] ca-certificates-java: openjdk-17 update caused install regressions Severity set to 'critical' from 'serious' -- 1039472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039472 Debian Bug Tracking System

Bug#1039472: ca-certificates-java: openjdk-17 update caused install regressions

Package: ca-certificates-java Followup-For: Bug #1039472 Control: severity -1 critical This makes unrelated software on the system break, making unrelated packages unusable without guidance on how to fix it.

Bug#1037740: marked as done (libsigc++-3.0: ftbfs with GCC-13)

Your message dated Sat, 15 Jul 2023 09:51:46 -0400 with message-id and subject line Re: libsigc++-3.0: ftbfs with GCC-13 has caused the Debian Bug report #1037740, regarding libsigc++-3.0: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1037702: marked as done (jellyfish: ftbfs with GCC-13)

Your message dated Sat, 15 Jul 2023 13:36:00 + with message-id and subject line Bug#1037702: fixed in jellyfish 2.3.0-16 has caused the Debian Bug report #1037702, regarding jellyfish: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1000133: marked as done (kannel: depends on obsolete pcre3 library)

Your message dated Sat, 15 Jul 2023 13:36:12 + with message-id and subject line Bug#1000133: fixed in kannel 1.4.5-13 has caused the Debian Bug report #1000133, regarding kannel: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt

Bug#1037765: maildir-utils: ftbfs with GCC-13

On 2023-07-15, at 12:19:47 +0100, Jeremy Sowden wrote: > On 2023-07-15, at 07:29:54 -0300, David Bremner wrote: > > Matthias Klose writes: > > > Package: src:maildir-utils > > > Version: 1.8.14-1 > > > Severity: normal > > > Tags: sid trixie > > > User: debian-...@lists.debian.org > > > Usertags:

Bug#1039621: marked as done (libngs-jni: Installs shared object in wrong directory)

Your message dated Sat, 15 Jul 2023 13:02:08 + with message-id and subject line Bug#1039621: fixed in sra-sdk 3.0.3+dfsg-6~deb12u1 has caused the Debian Bug report #1039621, regarding libngs-jni: Installs shared object in wrong directory to be marked as done. This means that you claim that

Bug#1037226:

Control: tags -1 pending Conrtol: block -1 by 1040799 This bug has been fixed in unstable with the binNMU 1.0.3-1b3, see #1040858 It is also scheduled to be fixed in the next stable-point-release, see #1040799 -- tobi

Processed: Re: Bug#1037226:

Processing control commands: > tags -1 pending Bug #1037226 [libnginx-mod-http-modsecurity] libnginx-mod-http-modsecurity fails to start after update libmodsecurity3 to v3.0.9 Added tag(s) pending. -- 1037226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037226 Debian Bug Tracking System

Processed: notfixed 1037226 in 1.0.3-1

Processing commands for cont...@bugs.debian.org: > notfixed 1037226 1.0.3-1 Bug #1037226 [libnginx-mod-http-modsecurity] libnginx-mod-http-modsecurity fails to start after update libmodsecurity3 to v3.0.9 No longer marked as fixed in versions libnginx-mod-http-modsecurity/1.0.3-1. > thanks

Bug#1037917: marked as done (gnutls28: leaves processes running after build: gnutls-serv, openssl s_server)

Your message dated Sat, 15 Jul 2023 12:36:31 + with message-id and subject line Bug#1037917: fixed in gnutls28 3.8.0+git20230713-1 has caused the Debian Bug report #1037917, regarding gnutls28: leaves processes running after build: gnutls-serv, openssl s_server to be marked as done. This

Bug#1000100: Would configuring with -DPERL_REGEX=OFF be an option?

Would configuring with -DPERL_REGEX=OFF be an option, or does that cost too much functionality? cu Adrian

Processed: tagging 1000074

Processing commands for cont...@bugs.debian.org: > tags 174 + upstream Bug #174 [src:gsmartcontrol] gsmartcontrol: depends on obsolete pcre3 library Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 174:

Bug#1026635: marked as done (rust-packed-simd: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

Your message dated Sat, 15 Jul 2023 12:08:41 + with message-id and subject line Bug#1026635: fixed in rust-packed-simd 0.3.8-1 has caused the Debian Bug report #1026635, regarding rust-packed-simd: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 to be

  1   2   >