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

Your message dated Fri, 23 Dec 2022 15:51:33 +0800 with message-id <3d2a0539-d2cc-07c6-6473-bc3e58c53...@debian.org> and subject line Re: concalc: Removal of obsolete debhelper compat 5 and 6 in bookworm has caused the Debian Bug report #965467, regarding concalc: Removal of obsolete debhelper com

Bug#1025106: python-icecream: (autopkgtest) needs update for python3.11: ValueError: not enough values to unpack (expected 2, got 1)

Dear Maintainer, After upload of executing/1.2.0 to unstable, your package builds fine and all tests pass (both with python3.10 and python3.11). I've checked in a sid (not bookworm) chroot environment. Kind Regards [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025030

Bug#1026347: marked as done (python-dtcwt: autopkgtest needs update for new version of numpy: IndexError)

Your message dated Fri, 23 Dec 2022 07:20:44 + with message-id and subject line Bug#1026347: fixed in python-dtcwt 0.12.0-4 has caused the Debian Bug report #1026347, regarding python-dtcwt: autopkgtest needs update for new version of numpy: IndexError to be marked as done. This means that y

Bug#1026858: Dependency on debconf dropped prematurely

Thanks Faidon for your analysis and Cyril for forwarding this bug report to me. On Thu, 22 Dec 2022 23:06:05 +0100 Cyril Brulebois wrote: Faidon Liambotis (2022-12-22): > Going forward there are a few options: > * Revert the change and depend on debconf again. This is the safest > optio

Bug#1026489: marked as done (wine: FTBFS: make[1]: *** [debian/rules:126: override_dh_auto_configure] Error 1)

Your message dated Fri, 23 Dec 2022 06:57:38 + with message-id and subject line Bug#1026489: fixed in wine 7.0~repack-11 has caused the Debian Bug report #1026489, regarding wine: FTBFS: make[1]: *** [debian/rules:126: override_dh_auto_configure] Error 1 to be marked as done. This means that

Bug#1016963: u-boot: delay migration to testing to test more platforms

On 2022-08-20, Vagrant Cascadian wrote: > On 2022-08-10, Vagrant Cascadian wrote: >> This bug is just to delay migration to testing while more platforms get >> tested. If you have a relevent board, please consider testing and >> reporting the status: >> >> https://wiki.debian.org/U-boot/Status >

Bug#1026653: marked as done (libhibernate-validator4-java: FTBFS: make: *** [debian/rules:4: build] Error 25)

Your message dated Fri, 23 Dec 2022 02:36:50 + with message-id and subject line Bug#1026653: fixed in libhibernate-validator4-java 4.3.4-6 has caused the Debian Bug report #1026653, regarding libhibernate-validator4-java: FTBFS: make: *** [debian/rules:4: build] Error 25 to be marked as done.

Bug#974118: marked as done (rust-pbkdf2: FTBFS build-depends on librust-base64-0.10+default-dev)

Your message dated Fri, 23 Dec 2022 01:31:10 + with message-id and subject line Bug#974118: fixed in rust-pbkdf2 0.11.0-1 has caused the Debian Bug report #974118, regarding rust-pbkdf2: FTBFS build-depends on librust-base64-0.10+default-dev to be marked as done. This means that you claim tha

Processed: Bug#1026685 marked as pending in streamex

Processing control commands: > tag -1 pending Bug #1026685 [src:streamex] streamex: FTBFS: make: *** [debian/rules:4: build] Error 25 Added tag(s) pending. -- 1026685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problem

Bug#1026685: marked as pending in streamex

Control: tag -1 pending Hello, Bug #1026685 in streamex 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/java-team/streamex/-/commit/7b9d35e3a7ffdee89230974fa20b

Processed: found in stable

Processing commands for cont...@bugs.debian.org: > found 1010120 0.13.0-6 Bug #1010120 {Done: Laszlo Boszormenyi (GCS) } [src:thrift] thrift: FTBFS in bullseye (expired certificates in test suite) Marked as found in versions thrift/0.13.0-6. > thanks Stopping processing here. Please contact me i

Bug#1010120: found in stable

found 1010120 0.13.0-6 thanks

Processed: reassign 1026683 to apache-log4j2, forcibly merging 1026666 1026683

Processing commands for cont...@bugs.debian.org: > reassign 1026683 apache-log4j2 2.19.0-1 Bug #1026683 [src:jengelman-shadow] jengelman-shadow: FTBFS: make[1]: *** [debian/rules:6: override_dh_auto_build] Error 25 Bug reassigned from package 'src:jengelman-shadow' to 'apache-log4j2'. No longer m

Bug#1026664: misspell-fixer: FTBFS: grep: work/R.txt: Permission denied

Hi, Thanks for checking this. I suspect this report is the same as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026771 Could you please help me how I can test these issues in the infrastructure? Thank you. Best regards, Lajos On Tue, 20 Dec 2022, Lucas Nussbaum wrote: > Source: misspell

Bug#1026771: misspell-fixer: flaky autopkgtest

Hi Paul, Thank you. How can I test my changes on the below infrastructure? Does https://mentors.debian.net/ run those tests? Or is this something different? Thank you. Best regards, Lajos On Tue, 20 Dec 2022, Paul Gevers wrote: > Source: misspell-fixer > Version: 0.4-1 > Severity: serious > Us

Bug#1026538: marked as done (aiosmtplib: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)

Your message dated Thu, 22 Dec 2022 23:49:16 + with message-id and subject line Bug#1026538: fixed in aiosmtplib 2.0.0-1 has caused the Debian Bug report #1026538, regarding aiosmtplib: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit co

Processed: retitle 1026666 to liblog4j2-java pom includes junit-bom

Processing commands for cont...@bugs.debian.org: > retitle 102 liblog4j2-java pom includes junit-bom Bug #102 {Done: tony mancill } [apache-log4j2] Please make liblog4j2-java depend on junit5 Bug #1026668 {Done: tony mancill } [apache-log4j2] Please make liblog4j2-java depend on junit5 C

Processed: Bug#1026538 marked as pending in aiosmtplib

Processing control commands: > tag -1 pending Bug #1026538 [src:aiosmtplib] aiosmtplib: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13 Added tag(s) pending. -- 1026538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026538 De

Bug#1026538: marked as pending in aiosmtplib

Control: tag -1 pending Hello, Bug #1026538 in aiosmtplib 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/aiosmtplib/-/commit/6962e84cab248

Bug#1024795: python-llvmlite

Sure, I think we can ship a snapshot version as long as it works fine with llvm-14. Could you please verify the snapshot hash again? https://github.com/numba/llvmlite/commit/c65b3e662b7b08920172b710419d7a06b660be59 The commit seems missing. If it was close to the master branch, I can directly pul

Processed: affects 1026666

Processing commands for cont...@bugs.debian.org: > affects 102 jengelman-shadow Bug #102 {Done: tony mancill } [apache-log4j2] Please make liblog4j2-java depend on junit5 Bug #1026668 {Done: tony mancill } [apache-log4j2] Please make liblog4j2-java depend on junit5 Added indication that

Bug#1026471: marked as done (python-aiosmtpd: FTBFS: AttributeError: 'SSLProtocol' object has no attribute 'data_received')

Your message dated Thu, 22 Dec 2022 22:49:48 + with message-id and subject line Bug#1026471: fixed in python-aiosmtpd 1.4.3-1 has caused the Debian Bug report #1026471, regarding python-aiosmtpd: FTBFS: AttributeError: 'SSLProtocol' object has no attribute 'data_received' to be marked as done

Bug#1025019: marked as done (python-aiosmtpd: (autopkgtest) needs update for python3.11: Can't decode base64)

Your message dated Thu, 22 Dec 2022 22:49:48 + with message-id and subject line Bug#1025019: fixed in python-aiosmtpd 1.4.3-1 has caused the Debian Bug report #1025019, regarding python-aiosmtpd: (autopkgtest) needs update for python3.11: Can't decode base64 to be marked as done. This means

Bug#1011863: guix: FTBFS in bullseye because of expired certificates used in tests

reopen 1011863 found 1011863 1.2.0-4 fixed 1011863 1.3.0-5 retitle 1011863 guix: FTBFS in bullseye because of expired certificates used in tests tags 1011863 + patch thanks Hello. Reopening because packages in bullseye must build in bullseye. I attach an upload proposal for bullseye, it's just

Processed: guix: FTBFS in bullseye because of expired certificates used in tests

Processing commands for cont...@bugs.debian.org: > reopen 1011863 Bug #1011863 {Done: Vagrant Cascadian } [src:guix] guix: FTBFS: tests fail '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 reopened N

Processed: unarchive for bullseye

Processing commands for cont...@bugs.debian.org: > unarchive 1011863 Bug #1011863 {Done: Vagrant Cascadian } [src:guix] guix: FTBFS: tests fail Unarchived Bug 1011863 > thanks Stopping processing here. Please contact me if you need assistance. -- 1011863: https://bugs.debian.org/cgi-bin/bugrepo

Bug#1026471: marked as pending in python-aiosmtpd

Control: tag -1 pending Hello, Bug #1026471 in python-aiosmtpd 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/python-aiosmtpd/-/commit/29a

Processed: Bug#1026471 marked as pending in python-aiosmtpd

Processing control commands: > tag -1 pending Bug #1026471 [src:python-aiosmtpd] python-aiosmtpd: FTBFS: AttributeError: 'SSLProtocol' object has no attribute 'data_received' Added tag(s) pending. -- 1026471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026471 Debian Bug Tracking System C

Bug#1025019: marked as pending in python-aiosmtpd

Control: tag -1 pending Hello, Bug #1025019 in python-aiosmtpd 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/python-aiosmtpd/-/commit/29a

Processed: Bug#1025019 marked as pending in python-aiosmtpd

Processing control commands: > tag -1 pending Bug #1025019 [src:python-aiosmtpd] python-aiosmtpd: (autopkgtest) needs update for python3.11: Can't decode base64 Added tag(s) pending. -- 1025019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025019 Debian Bug Tracking System Contact ow...@b

Bug#1026858: Dependency on debconf dropped prematurely

Hi Faidon, and many thanks for the detailed analysis. Faidon Liambotis (2022-12-22): > Going forward there are a few options: > * Revert the change and depend on debconf again. This is the safest > option, as this has been the status quo since 2007. That would look good to me. I'll admit

Bug#1026714: marked as done (streamlink: FTBFS: dh_install: error: missing files, aborting)

Your message dated Thu, 22 Dec 2022 21:27:05 + with message-id and subject line Bug#1026714: fixed in streamlink 5.1.2-1 has caused the Debian Bug report #1026714, regarding streamlink: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the

Bug#1005414: marked as done (Modules fail to build for Linux 5.11 onward)

Your message dated Thu, 22 Dec 2022 21:19:42 + with message-id and subject line Bug#1005414: fixed in cloop 3.14.1.3+nmu1 has caused the Debian Bug report #1005414, regarding Modules fail to build for Linux 5.11 onward to be marked as done. This means that you claim that the problem has been

Bug#1005413: marked as done (FTBFS with gcc 11)

Your message dated Thu, 22 Dec 2022 21:19:42 + with message-id and subject line Bug#1005413: fixed in cloop 3.14.1.3+nmu1 has caused the Debian Bug report #1005413, regarding FTBFS with gcc 11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1024221: marked as done (intel-gpu-tools: FTBFS with libproc2)

Your message dated Thu, 22 Dec 2022 21:04:17 + with message-id and subject line Bug#1024221: fixed in intel-gpu-tools 1.26+git20220524-1.1 has caused the Debian Bug report #1024221, regarding intel-gpu-tools: FTBFS with libproc2 to be marked as done. This means that you claim that the problem

Bug#1008694: marked as done (kdevelop-python: Build-Depends: python3.9-dev)

Your message dated Thu, 22 Dec 2022 21:05:12 + with message-id and subject line Bug#1008694: fixed in kdevelop-python 22.12.0-1 has caused the Debian Bug report #1008694, regarding kdevelop-python: Build-Depends: python3.9-dev to be marked as done. This means that you claim that the problem h

Bug#1026735: clusterssh: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255

Hi Gregor, On Tue, Dec 20, 2022 at 07:31:55PM +0100, gregor herrmann wrote: > Control: tag -1 + confirmed upstream > > On Tue, 20 Dec 2022 18:28:10 +0100, Lucas Nussbaum wrote: > > > Source: clusterssh > > Version: 4.16-3 > > Severity: serious > > Justification: FTBFS > > Tags: bookworm sid ftbf

Processed: NMU fixing FTBFS and reproducible builds issues

Processing control commands: > tags 787996 pending Bug #787996 [src:cloop] cloop: please make the build reproducible Ignoring request to alter tags of bug #787996 to the same tags previously set > tags 1005413 pending Bug #1005413 [src:cloop] FTBFS with gcc 11 Ignoring request to alter tags of bug

Bug#1005413: NMU fixing FTBFS and reproducible builds issues

Control: tags 787996 pending Control: tags 1005413 pending Control: tags 1005414 pending I have uploaded an NMU fixing FTBFS and reproducible builds issues: diff -Nru cloop-3.14.1.3/advancecomp-1.15/file.cc cloop-3.14.1.3+nmu1/advancecomp-1.15/file.cc --- cloop-3.14.1.3/advancecomp-1.15/file.cc

Processed: NMU fixing FTBFS and reproducible builds issues

Processing control commands: > tags 787996 pending Bug #787996 [src:cloop] cloop: please make the build reproducible Ignoring request to alter tags of bug #787996 to the same tags previously set > tags 1005413 pending Bug #1005413 [src:cloop] FTBFS with gcc 11 Ignoring request to alter tags of bug

Processed: NMU fixing FTBFS and reproducible builds issues

Processing control commands: > tags 787996 pending Bug #787996 [src:cloop] cloop: please make the build reproducible Added tag(s) pending. > tags 1005413 pending Bug #1005413 [src:cloop] FTBFS with gcc 11 Added tag(s) pending. > tags 1005414 pending Bug #1005414 [src:cloop] Modules fail to build f

Processed: lua-nvim: flaky autopkgtest: times out on ppc64el and s390x

Processing control commands: > found -1 0.2.3-1-1 Bug #1026869 [src:lua-nvim] lua-nvim: flaky autopkgtest: times out on ppc64el and s390x Marked as found in versions lua-nvim/0.2.3-1-1. -- 1026869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026869 Debian Bug Tracking System Contact ow..

Bug#1026869: lua-nvim: flaky autopkgtest: times out on ppc64el and s390x

Source: lua-nvim Version: 0.2.2-1-1 Severity: serious User: debian...@lists.debian.org Usertags: flaky timeout Control: found -1 0.2.3-1-1 Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails on s390x and ppc64el due to an autopkgtest

Bug#1026868: node-puppeteer: autopkgtest regression: 13 failing

Source: node-puppeteer Version: 13.4.1+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it recently (around august 2022) started to fail consistently in testing. Paul https://ci.debian.net/pack

Bug#997715: libapache-poi-java: FTBFS in bullseye: tests failed

Dear maintainers: This package FTBFS for me on bullseye, tried several times on different machines. (I'm attaching a build log) I think it is the same bug reported by Lucas back in October 2021 (i.e. this one), which was fixed only in bookworm. Unfortunately, I'm not 100% sure, because I trie

Bug#1026865: libthrust: flaky autopkgtest (host dependent)

Source: libthrust Version: 1.16.0-2 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails on amd64. The failures seem related on the host that runs the test. The tests

Bug#1026666: Please make liblog4j2-java depend on junit5

Hi again tony, Le 22/12/2022 à 16:16, tony mancill a écrit : Hi Pierre, On Thu, Dec 22, 2022 at 07:31:30AM +0100, Pierre Gruet wrote: Hi tony, Le 21/12/2022 à 22:58, tony mancill a écrit : On Tue, Dec 20, 2022 at 11:45:54PM +0100, Pierre Gruet wrote: Control: retitle -1 Please make liblog4j

Bug#1026864: dmrgpp: flaky autopkgtest on amd64: times out

Source: dmrgpp Version: 6.02-3 Severity: serious User: debian...@lists.debian.org Usertags: flaky timeout Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails on amd64 because it times out after 2 hours and 47 minutes. Apparently thi

Processed: unarchive for bullseye

Processing commands for cont...@bugs.debian.org: > unarchive 997715 Bug #997715 {Done: Markus Koschany } [src:libapache-poi-java] libapache-poi-java: FTBFS: tests failed Unarchived Bug 997715 > thanks Stopping processing here. Please contact me if you need assistance. -- 997715: https://bugs.de

Bug#1026809: Xlib: sequence lost (0x10000 > 0x...) in reply type 0x... when running emacs

Vincent Lefevre kirjoitti 21.12.2022 klo 15.01: Package: libx11-6 Version: 2:1.8.3-2 Severity: grave Justification: renders package unusable or possible data loss? After the upgrade to libx11-6 2:1.8.3-2, I get the following errors when running emacs: e.g. Xlib: sequence lost (0x1 > 0x473

Bug#1026021: pytest-forked: FTBFS with pytest 7.2

* Scott Talbert [2022-12-22 12:29]: Thanks, I did notice this but I was planning to wait on a new upstream release which should fix this (hopefully coming soon). No problem. I found your PR in the mean time (better than my hotfix btw), and pytest still has a few other regressions anyway, so

Bug#1026856: [3dprinter-general] Bug#1026856: cura-engine: FTBFS: 14 tests segfault

cura-engine/experimental recently started to FTBFS: 46% tests passed, 14 tests failed out of 26 This is caused by the recent protobuf transition, see gdb log below. It will be fixed in libarcus 5.0.0-2, which is waiting for release: https://salsa.debian.org/3dprinting-team/libarcus/-/commit/c2

Bug#1016938: marked as done (konclude: autopkgtest regression on armhf, flaky test on s390x (with timeout))

Your message dated Thu, 22 Dec 2022 18:50:53 + with message-id and subject line Bug#1016938: fixed in konclude 0.7.0+1138+git20220514~dfsg-1 has caused the Debian Bug report #1016938, regarding konclude: autopkgtest regression on armhf, flaky test on s390x (with timeout) to be marked as done.

Bug#1023917: marked as done (cpm: FTBFS against libgpgme-dev >= 1.18.0-2 [checking for gpgme-config... no])

Your message dated Thu, 22 Dec 2022 18:34:09 + with message-id and subject line Bug#1023917: fixed in cpm 0.32-1.5 has caused the Debian Bug report #1023917, regarding cpm: FTBFS against libgpgme-dev >= 1.18.0-2 [checking for gpgme-config... no] to be marked as done. This means that you clai

Bug#1026809: Xlib: sequence lost (0x10000 > 0x...) in reply type 0x... when running emacs

Control: affects -1 emacs-gtk mlterm This also affects mlterm, when I resize the terminal. In the upstream bug, someone says that it also affects xterm, but I cannot reproduce the issue with xterm. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Processed: Re: Xlib: sequence lost (0x10000 > 0x...) in reply type 0x... when running emacs

Processing control commands: > affects -1 emacs-gtk mlterm Bug #1026809 [libx11-6] Xlib: sequence lost (0x1 > 0x...) in reply type 0x... when running emacs Added indication that 1026809 affects emacs-gtk and mlterm -- 1026809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026809 Debian

Bug#1026021: pytest-forked: FTBFS with pytest 7.2

On Tue, 13 Dec 2022, Timo Röhling wrote: Source: pytest-forked Version: 1.4.0-1 Severity: serious Tags: ftbfs patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package FTBFS with pytest 7.2; the test summary has been augmented with a reason, which is not captured by

Processed: affects 1026854

Processing commands for cont...@bugs.debian.org: > affects 1026854 src:bazel-bootstrap Bug #1026854 [libgoogle-auto-common-java] libgoogle-auto-common-java: ships /usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom Added indication that 1026854 affects src:bazel-boots

Processed: tagging 1026854

Processing commands for cont...@bugs.debian.org: > tags 1026854 + ftbfs Bug #1026854 [libgoogle-auto-common-java] libgoogle-auto-common-java: ships /usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom Added tag(s) ftbfs. > thanks Stopping processing here. Please conta

Bug#1026858: Dependency on debconf dropped prematurely

Source: cdebconf Version: 0.265 Severity: critical cdebconf 0.265 dropped the "debconf" dependency, that Joey Hess "temporarily" added in 2007 with cdebconf 0.123[1]. This was added to "avoid anyone breaking their systems by removing debconf, which dependencies now allow". Unfortunately, that rem

Bug#1026856: cura-engine: FTBFS: 14 tests segfault

Source: cura-engine Version: 1:5.0.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, cura-engine/experimental recently started to FTBFS: 46% tests passed, 14 tests failed out of 26 Total Test time (real) = 2.57 sec The follow

Bug#1026855: libgoogle-auto-service-java: ships /usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom

Package: libgoogle-auto-service-java Version: 1.0~rc7-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, libgoogle-auto-service-java ships two dubious files that should probably not be in the package at all: /usr/share/maven-repo/build-only/build-only/NO_VERSION/build

Bug#1026854: libgoogle-auto-common-java: ships /usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom

Package: libgoogle-auto-common-java Version: 1.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, libgoogle-auto-common-java ships two dubious files that should probably not be in the package at all: /usr/share/maven-repo/build-only/build-only/NO_VERSION/build-onl

Bug#1026853: rust-svgdom: (build-)depends on old version of rust-roxmltree

Package: rust-svgdom Version: 0.18.0-2 Severity: serious svgdom depends on version 0.7 of the roxmltree crate. Debian sid now has version 0.16. I tried bumping the dependency but it fails to build with the following errors. error[E0599]: no method named `write_buf` found for struct `Document`

Bug#1026058: marked as done (rust-xmlparser: FTBFS: src/lib.rs - map_err_at (line 396))

Your message dated Thu, 22 Dec 2022 16:12:35 + with message-id <393f4387-e558-0502-24db-776c73439...@debian.org> and subject line re: rust-xmlparser: FTBFS: src/lib.rs - map_err_at (line 396) has caused the Debian Bug report #1026058, regarding rust-xmlparser: FTBFS: src/lib.rs - map_err_at (li

Bug#1026666: marked as done (Please make liblog4j2-java depend on junit5)

Your message dated Thu, 22 Dec 2022 16:04:41 + with message-id and subject line Bug#102: fixed in apache-log4j2 2.19.0-2 has caused the Debian Bug report #102, regarding Please make liblog4j2-java depend on junit5 to be marked as done. This means that you claim that the problem has be

Bug#1026668: marked as done (Please make liblog4j2-java depend on junit5)

Your message dated Thu, 22 Dec 2022 16:04:41 + with message-id and subject line Bug#102: fixed in apache-log4j2 2.19.0-2 has caused the Debian Bug report #102, regarding Please make liblog4j2-java depend on junit5 to be marked as done. This means that you claim that the problem has be

Processed: Bug#1026666 marked as pending in apache-log4j2

Processing control commands: > tag -1 pending Bug #102 [apache-log4j2] Please make liblog4j2-java depend on junit5 Bug #1026668 [apache-log4j2] Please make liblog4j2-java depend on junit5 Added tag(s) pending. Added tag(s) pending. -- 102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#1026666: marked as pending in apache-log4j2

Control: tag -1 pending Hello, Bug #102 in apache-log4j2 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/java-team/apache-log4j2/-/commit/09c0a7960e19ebad43

Bug#1019666: marked as done (ruby-simplecov: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(@stderr).to be_empty)

Your message dated Thu, 22 Dec 2022 15:20:46 + with message-id and subject line Bug#1019666: fixed in ruby-simplecov 0.21.2-2 has caused the Debian Bug report #1019666, regarding ruby-simplecov: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(@stderr).to be_empty

Bug#1026666: Please make liblog4j2-java depend on junit5

Hi Pierre, On Thu, Dec 22, 2022 at 07:31:30AM +0100, Pierre Gruet wrote: > Hi tony, > > Le 21/12/2022 à 22:58, tony mancill a écrit : > > On Tue, Dec 20, 2022 at 11:45:54PM +0100, Pierre Gruet wrote: > > > Control: retitle -1 Please make liblog4j2-java depend on junit5 > > > > > > Hello, > > >

Bug#1019608: marked as done (rubocop: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 40.2) Failure/Error: expect($stderr.string).to eq(''))

Your message dated Thu, 22 Dec 2022 20:42:40 +0530 with message-id <20221222151240.lrbcci3qyhcg6...@nileshpatra.info> and subject line Re: rubocop: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 40.2) Failure/Error: expect($stderr.string).to eq('') has caused the Debian Bug report #1019608, reg

Bug#1026495: marked as done (python-ltfatpy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)

Your message dated Thu, 22 Dec 2022 14:39:37 + with message-id and subject line Bug#1026495: fixed in python-ltfatpy 1.0.16-9 has caused the Debian Bug report #1026495, regarding python-ltfatpy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returne

Bug#1025122: marked as done (python-stone: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec')

Your message dated Thu, 22 Dec 2022 13:04:21 + with message-id and subject line Bug#1025122: fixed in python-stone 3.3.1-2 has caused the Debian Bug report #1025122, regarding python-stone: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec' to be marked

Bug#1026733: marked as done (pytroll-schedule: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)

Your message dated Thu, 22 Dec 2022 12:06:50 + with message-id and subject line Bug#1026733: fixed in pytroll-schedule 0.6.0-5 has caused the Debian Bug report #1026733, regarding pytroll-schedule: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" retu

Bug#1026843: Not suitable for testing yet (due to outstanding migration tests)

Package: mini-buildd Version: 1.9.112 Severity: serious While working quite well already on a new setup, some crucial testing has not yet been fully done yet -- especially * migration tests (i.e., upgrading an existing installation from 1.0.x->2.0.x) * new 'setup' system's maintenance facilities

Bug#999236: marked as done (dnshistory: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Thu, 22 Dec 2022 18:34:54 +0800 with message-id and subject line dnshistory: missing required debian/rules targets build-arch and/or build-indep has caused the Debian Bug report #999236, regarding dnshistory: missing required debian/rules targets build-arch and/or build-indep

Processed: tagging 1026814

Processing commands for cont...@bugs.debian.org: > tags 1026814 - ftbfs bookworm Bug #1026814 {Done: Pino Toscano } [libmarble-dev] libmarble-dev: missing qtwebengine5-dev dependency when built using QtWebEngine Removed tag(s) bookworm and ftbfs. > thanks Stopping processing here. Please contact

Bug#1024221: Bug#1022573: transition: procps

On Thu, 22 Dec 2022 at 19:50, Paul Gevers wrote: > That's (in general) sub-optimal for the release team. We try hard to > avoid entangling transitions and therefor we try to finish transitions > sooner rather than later. My preference would be that you NMU (minimal > changes) now; the maintainer

Bug#1026814: marked as done (libmarble-dev: missing qtwebengine5-dev dependency when built using QtWebEngine)

Your message dated Thu, 22 Dec 2022 10:13:09 + with message-id and subject line Bug#1026814: fixed in marble 4:22.12.0-2 has caused the Debian Bug report #1026814, regarding libmarble-dev: missing qtwebengine5-dev dependency when built using QtWebEngine to be marked as done. This means that

Bug#1018039: marked as done (FTBFS on ppc64el with gcc-12)

Your message dated Thu, 22 Dec 2022 10:13:37 + with message-id and subject line Bug#1018039: fixed in powerpc-utils 1.3.10-1 has caused the Debian Bug report #1018039, regarding FTBFS on ppc64el with gcc-12 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#977192: marked as done (libappimage: CVE-2020-25265)

Your message dated Thu, 22 Dec 2022 10:00:12 + with message-id and subject line Bug#977192: fixed in libappimage 1.0.4-1 has caused the Debian Bug report #977192, regarding libappimage: CVE-2020-25265 to be marked as done. This means that you claim that the problem has been dealt with. If thi

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

Your message dated Thu, 22 Dec 2022 09:34:11 + with message-id and subject line Bug#965493: fixed in dnshistory 1.3-3 has caused the Debian Bug report #965493, regarding dnshistory: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that t

Bug#1026044: marked as done (libodsstream-dev: FTBFS for other packages)

Your message dated Thu, 22 Dec 2022 09:20:33 + with message-id and subject line Bug#1026044: fixed in libodsstream 0.9.1-2 has caused the Debian Bug report #1026044, regarding libodsstream-dev: FTBFS for other packages to be marked as done. This means that you claim that the problem has been

Bug#1026696: marked as done (golang-github-prometheus-client-model: FTBFS: make: *** [debian/rules:6: binary] Error 25)

Your message dated Thu, 22 Dec 2022 09:19:36 + with message-id and subject line Bug#1026696: fixed in golang-github-prometheus-client-model 0.3.0-2 has caused the Debian Bug report #1026696, regarding golang-github-prometheus-client-model: FTBFS: make: *** [debian/rules:6: binary] Error 25 t

Bug#1026696: golang-github-prometheus-client-model: FTBFS: make: *** [debian/rules:6: binary] Error 25

On 22.12.22 20:52, Shengjing Zhu wrote: Hmm, this works for me, the generated pb.go uses old timestamp type. I have added above change and built the package, then checked the result. My mistake, I think I must have looked at a stale build. The suggested .proto mapping workaround seems to do w

Bug#1024221: Bug#1022573: transition: procps

Hi Craig, On 22-12-2022 00:28, Craig Small wrote: BUT, procps is in transition and this linking needs to happen before the first freeze milestone so I will upload 20220525 linked to libproc2 if we get near to running out of time. That's (in general) sub-optimal for the release team. We try ha

Bug#1026795: marked as done (acl2: FTBFS: make: *** [debian/rules:160: infix-stamp] Error 2)

Your message dated Thu, 22 Dec 2022 08:39:22 + with message-id and subject line Bug#1026795: fixed in acl2 8.5dfsg-2 has caused the Debian Bug report #1026795, regarding acl2: FTBFS: make: *** [debian/rules:160: infix-stamp] Error 2 to be marked as done. This means that you claim that the pro

Bug#1025122: python-stone: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'

Control: tags -1 pending The bug is fixed in Git. The package needs fixing of its autopkgtest which shows the same issue. I admit I have no idea why it fails here. -- http://fam-tille.de

Processed: Re: python-stone: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec'

Processing control commands: > tags -1 pending Bug #1025122 [src:python-stone] python-stone: (autopkgtest) needs update for python3.11: module 'inspect' has no attribute 'getargspec' Added tag(s) pending. -- 1025122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025122 Debian Bug Tracking

Processed: reassign 1026814 to libmarble-dev ..., affects 1026814, tagging 1026814

Processing commands for cont...@bugs.debian.org: > reassign 1026814 libmarble-dev marble/4:22.12.0-1 Bug #1026814 [src:kreport] kreport: FTBFS: dh_install: error: missing files, aborting Bug reassigned from package 'src:kreport' to 'libmarble-dev'. No longer marked as found in versions kreport/3.