Bug#1067829: marked as done (nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-We

Your message dated Sun, 07 Apr 2024 05:21:43 + with message-id and subject line Bug#1067829: fixed in nfs-utils 1:2.6.4-4 has caused the Debian Bug report #1067829, regarding nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but

Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET

Hello, On Sat 06 Apr 2024 at 09:30pm +02, Sebastian Andrzej Siewior wrote: > On 2024-04-06 17:17:45 [+0800], Sean Whitton wrote: >> Hello, > Hi, > >> It looks like the problem is opening YAPET1.0-format databases, which >> the manpage explicitly says is meant to work. >> >> I've made a sample

Processed: Re: Bug#1066763: liferea: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

Processing control commands: > notfixed -1 1.15.5-1 Bug #1066763 {Done: Paul Gevers } [src:liferea] liferea: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 No longer marked as fixed in versions 1.15.5-1. -- 1066763:

Bug#1066763: liferea: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

control: notfixed -1 1.15.5-1 On 04-04-2024 6:04 p.m., Paul Gevers wrote: So, marking the bug as not affecting the version in testing to avoid autoremoval. And also removing the fixed version. There was only a *time* that liferea was broken (by liblzma), not a version of liferea, nor was

Bug#1066630: marked as done (libnet-ldapapi-perl: FTBFS: LDAPapi.c:624:18: error: implicit declaration of function ‘ldap_bind_s’ [-Werror=implicit-function-declaration])

Your message dated Sun, 07 Apr 2024 04:21:09 + with message-id and subject line Bug#1066630: fixed in libnet-ldapapi-perl 3.0.7-4 has caused the Debian Bug report #1066630, regarding libnet-ldapapi-perl: FTBFS: LDAPapi.c:624:18: error: implicit declaration of function ‘ldap_bind_s’

Bug#1066346: sc: FTBFS: sc.c:1301:46: error: implicit declaration of function ‘list_frames’; did you mean ‘list_ranges’? [-Werror=implicit-function-declaration]

Hi, I've fixed the bug. And I'll do NMU if no one object in 10 days. I'll upload it to the delay/10 queue. Attachment is the debdiff. Please review it. Yours, Paul diff -Nru sc-7.16/debian/changelog sc-7.16/debian/changelog --- sc-7.16/debian/changelog2022-01-26 01:22:23.0 +0800

Processed: tags 1054822 patch

Processing commands for cont...@bugs.debian.org: > tags 1054822 patch Bug #1054822 [src:opam] opam: FTBFS: sed: can't read opam.install: No such file or directory Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054822:

Bug#1066620: marked as done (zzuf: FTBFS: zzat.c:482:32: error: implicit declaration of function ‘_IO_getc’ [-Werror=implicit-function-declaration])

Your message dated Sun, 07 Apr 2024 03:06:15 + with message-id and subject line Bug#1066620: fixed in zzuf 0.15-3 has caused the Debian Bug report #1066620, regarding zzuf: FTBFS: zzat.c:482:32: error: implicit declaration of function ‘_IO_getc’ [-Werror=implicit-function-declaration] to be

Bug#1054822: opam: FTBFS: sed: can't read opam.install: No such file or directory

Hi, On Fri, Oct 27, 2023 at 09:42:50PM +0200, Lucas Nussbaum wrote: ; windows_unicode = false } ; instrument_with = [] } Actual targets: - _build/default/opam-installer.install - _build/default/opam.install Running[1]: (cd _build/default/src/client && /bin/sh -c 'git describe --exact

Bug#1068526: samba-dsdb-modules dependencies unsatisfiable on 32-bit non-i386 architectures.

Package: samba-dsdb-modules Version: 2:4.19.5+dfsg-4 Tags: trixie, sid Severity: grave User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, samba-dsdb-modules depends on both libgpgme11 and libgpgme11t64. As a result it is uninstallable on

Bug#1067290: marked as done (pymeeus: FTBFS: FAILED tests/test_interpolation.py::test_interpolation_call - RuntimeError: I...)

Your message dated Sun, 07 Apr 2024 02:51:18 + with message-id and subject line Bug#1067290: fixed in pymeeus 0.5.12+dfsg1-1 has caused the Debian Bug report #1067290, regarding pymeeus: FTBFS: FAILED tests/test_interpolation.py::test_interpolation_call - RuntimeError: I... to be marked as

Processed: Bug#1067290 marked as pending in pymeeus

Processing control commands: > tag -1 pending Bug #1067290 [src:pymeeus] pymeeus: FTBFS: FAILED tests/test_interpolation.py::test_interpolation_call - RuntimeError: I... Added tag(s) pending. -- 1067290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067290 Debian Bug Tracking System

Bug#1067290: marked as pending in pymeeus

Control: tag -1 pending Hello, Bug #1067290 in pymeeus 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#1067916: FTBFS: tests failed

On Fri, Mar 29, 2024 at 12:13:57AM +0500, Andrey Rakhmatullin wrote: > Source: capnproto > Version: 1.0.1-3 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=capnproto=armhf=1.0.1-3%2Bb2=1711652087=0 Thank you for the bug report. I'm not able to reproduce the

Bug#1068068: bobcat, time_t transition lead to apparent ABI break (was: Need rebootstrapping on armel and armhf).

On Wed, Apr 03, 2024 at 11:37:20AM +0200, Frank B. Brokken wrote: > Dear Peter Green, you wrote: > > > Also, the bootstrapping procedure is only required when icmake isn't > > > available ... > > Thanks for your bugreport: I'm about to update icmake so that the circular > dependency between

Bug#1068068: marked as done (Need rebootstrapping on armel and armhf)

Your message dated Sat, 06 Apr 2024 21:37:44 + with message-id and subject line Bug#1068068: fixed in icmake 12.00.01-1 has caused the Debian Bug report #1068068, regarding Need rebootstrapping on armel and armhf to be marked as done. This means that you claim that the problem has been dealt

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

Your message dated Sat, 6 Apr 2024 18:23:51 -0300 with message-id <655eb736-4a34-40e1-a15c-e11d1d962...@yaerobi.com> and subject line cachy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 has caused the Debian Bug report #1067321,

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

Your message dated Sat, 6 Apr 2024 17:56:03 -0300 with message-id <4080bf9e-5d31-4f44-8837-110e79b2a...@debian.org> and subject line cachy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 has caused the Debian Bug report #1067321,

Bug#1064192: marked as done (openrefine: CVE-2024-23833)

Your message dated Sat, 06 Apr 2024 20:37:30 + with message-id and subject line Bug#1064192: fixed in openrefine 3.7.8-1 has caused the Debian Bug report #1064192, regarding openrefine: CVE-2024-23833 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1068513: dablin: FTBFS on arm{el,hf}: manually disables mpg123's large file API

Source: dablin Version: 1.15.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=dablin=armel=1.15.0-1%2Bb2=1712391165=0 [ 97%] Linking CXX executable

Processed: fixed 1068100 in 0.3.1~beta-7.1

Processing commands for cont...@bugs.debian.org: > fixed 1068100 0.3.1~beta-7.1 Bug #1068100 {Done: Drew Parsons } [src:armci-mpi] armci-mpi: autopkgtest spuriously fails Marked as fixed in versions armci-mpi/0.3.1~beta-7.1. > thanks Stopping processing here. Please contact me if you need

Bug#1068512: welle.io: FTBFS on arm{el,hf}: manually disables mpg123's LFS API

Source: welle.io Version: 2.4+ds-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=welle.io=armel=2.4%2Bds-2%2Bb3=1712391447=0 [ 99%] Linking CXX

Bug#1068363: src:autopkgtest: flaky autopkgtest (host dependent?) on ppc64el

The mystery continues. On 04-04-2024 10:08 p.m., Paul Gevers wrote: I forgot that on amd64, autopkgtest's autopkgtest now runs in qemu which doesn't benefit yet as much from tmpfs as lxc does, so it's not a good comparison. On ci-worker13: """

Bug#1067829: Fails to build on arm{el,hf} with 64bit time_t: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-We

> On Apr 6, 2024, at 3:15 PM, Salvatore Bonaccorso wrote: > > Hi Chuck, hi Steve, > > In Debian, as you might have heard there is a 64bit time_t > transition[1] ongoing affecting the armel and armhf architectures. > While doing so, nfs-utils was found to fail to build for those >

Bug#1060977: marked as done (dfdatetime: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13)

Your message dated Sat, 06 Apr 2024 19:34:13 + with message-id and subject line Bug#1060977: fixed in dfdatetime 20240220-1 has caused the Debian Bug report #1060977, regarding dfdatetime: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13 to be

Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET

On 2024-04-06 17:17:45 [+0800], Sean Whitton wrote: > Hello, Hi, > It looks like the problem is opening YAPET1.0-format databases, which > the manpage explicitly says is meant to work. > > I've made a sample YAPET1.0 database using a stretch VM. Using the > attached: > > - On bookworm, invoke

Processed: bug 1067829 is forwarded to https://lore.kernel.org/linux-nfs/zhgfupxclzeoz...@eldamar.lan/T/#u

Processing commands for cont...@bugs.debian.org: > forwarded 1067829 > https://lore.kernel.org/linux-nfs/zhgfupxclzeoz...@eldamar.lan/T/#u Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4

Processed: tagging 1067829

Processing commands for cont...@bugs.debian.org: > tags 1067829 + confirmed pending Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’}

Bug#1067829: Fails to build on arm{el,hf} with 64bit time_t: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-We

Hi Chuck, hi Steve, In Debian, as you might have heard there is a 64bit time_t transition[1] ongoing affecting the armel and armhf architectures. While doing so, nfs-utils was found to fail to build for those architectures after the switch, reported in Debian as [2]. Vladimir Petko from Ubuntu

Processed: tagging 1067829

Processing commands for cont...@bugs.debian.org: > tags 1067829 + upstream Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=] Added

Processed: Re: vde: FTBFS on arm{el,hf}: /tmp/ccwOo5J4.s:341: Error: symbol `open64' is already defined

Processing commands for cont...@bugs.debian.org: > found 1065951 vde2/2.3.2+r586-9 Bug #1065951 [src:vde2] vde: FTBFS on arm{el,hf}: /tmp/ccwOo5J4.s:341: Error: symbol `open64' is already defined Marked as found in versions vde2/2.3.2+r586-9. > End of message, stopping processing here. Please

Bug#1066308: marked as done (click: FTBFS: clickpreload.c:422:16: error: implicit declaration of function ‘__fxstat’; did you mean ‘__xstat’? [-Werror=implicit-function-declaration])

Your message dated Sat, 06 Apr 2024 17:35:11 + with message-id and subject line Bug#1066308: fixed in python-whey 0.0.26-1 has caused the Debian Bug report #1066308, regarding click: FTBFS: clickpreload.c:422:16: error: implicit declaration of function ‘__fxstat’; did you mean ‘__xstat’?

Bug#1067936: marked as done (Explicitly depends on a pre-t64 library name)

Your message dated Sat, 06 Apr 2024 17:19:39 + with message-id and subject line Bug#1067936: fixed in libgsecuredelete 0.3-3.2 has caused the Debian Bug report #1067936, regarding Explicitly depends on a pre-t64 library name to be marked as done. This means that you claim that the problem

Processed: tag ftbfs

Processing commands for cont...@bugs.debian.org: > tags 1064676 + ftbfs Bug #1064676 [src:android-platform-tools-apksig] android-platform-tools-apksig: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle

Processed: Also happening in stable

Processing commands for cont...@bugs.debian.org: > found 1064034 3.1.2-7 Bug #1064034 {Done: Chris Hofstaedtler } [src:ruby3.1] FTBFS: Expired test certificate Marked as found in versions ruby3.1/3.1.2-7. > tags 1064034 + bookworm Bug #1064034 {Done: Chris Hofstaedtler } [src:ruby3.1] FTBFS:

Processed: Already happening in stable

Processing commands for cont...@bugs.debian.org: > tags 1056196 + bookworm trixie sid Bug #1056196 [src:python3-onelogin-saml2] python3-onelogin-saml2: Please package new version 1.16.0, as current version will FTBFS soon Added tag(s) sid, bookworm, and trixie. > thanks Stopping processing here.

Processed: Also happening in stable

Processing commands for cont...@bugs.debian.org: > tags 1055877 + bookworm trixie sid Bug #1055877 {Done: Ole Streicher } [src:ndcube] ndcube: FTBFS in bookworm: leap-second file is expired Added tag(s) sid, bookworm, and trixie. > thanks Stopping processing here. Please contact me if you need

Processed: also happening in stable

Processing commands for cont...@bugs.debian.org: > found 1057544 2.4.0+dfsg-3 Bug #1057544 [src:barrier] barrier: FTBFS: failing test Marked as found in versions barrier/2.4.0+dfsg-3. > tags 1057544 + bookworm Bug #1057544 [src:barrier] barrier: FTBFS: failing test Added tag(s) bookworm. > thanks

Processed: Also happening in stable

Processing commands for cont...@bugs.debian.org: > tags 1064676 + bookworm Bug #1064676 [src:android-platform-tools-apksig] android-platform-tools-apksig: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home

Bug#1066910: marked as done (chromium: downloads non-free component libchromescreenai.so without asking)

Your message dated Sat, 06 Apr 2024 16:32:10 + with message-id and subject line Bug#1066910: fixed in chromium 123.0.6312.86-1~deb12u1 has caused the Debian Bug report #1066910, regarding chromium: downloads non-free component libchromescreenai.so without asking to be marked as done. This

Bug#1066136: marked as done (python3-xapian-haystack: unusable on stable due to use of deprecated module django.utils.six)

Your message dated Sat, 06 Apr 2024 16:32:29 + with message-id and subject line Bug#1066136: fixed in python-xapian-haystack 2.1.1-1+deb12u1 has caused the Debian Bug report #1066136, regarding python3-xapian-haystack: unusable on stable due to use of deprecated module django.utils.six to be

Processed: python-workalendar: FTBFS because of failing tests

Processing commands for cont...@bugs.debian.org: > forwarded 1060939 https://github.com/workalendar/workalendar/issues/764 Bug #1060939 [src:python-workalendar] python-workalendar: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Bug#1060939: python-workalendar: FTBFS because of failing tests

forwarded 1060939 https://github.com/workalendar/workalendar/issues/764 tags 1060939 + bookworm thanks

Processed: Re: opentracker: libowfat headers have moved

Processing control commands: > severity -1 serious Bug #1068449 [src:opentracker] opentracker: libowfat headers have moved Severity set to 'serious' from 'important' -- 1068449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068449 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1066609: marked as done (yagiuda: FTBFS: input.c:60:9: error: implicit declaration of function ‘gets’; did you mean ‘fgets’? [-Werror=implicit-function-declaration])

Your message dated Sat, 06 Apr 2024 15:04:14 + with message-id and subject line Bug#1066609: fixed in yagiuda 1.19-11 has caused the Debian Bug report #1066609, regarding yagiuda: FTBFS: input.c:60:9: error: implicit declaration of function ‘gets’; did you mean ‘fgets’?

Bug#1067794: marked as done (flask-login: FTBFS: failing tests)

Your message dated Sat, 06 Apr 2024 14:49:04 + with message-id and subject line Bug#1067794: fixed in flask-login 0.6.3-2 has caused the Debian Bug report #1067794, regarding flask-login: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt

Bug#1068100: marked as done (armci-mpi: autopkgtest spuriously fails)

Your message dated Sat, 06 Apr 2024 14:34:11 + with message-id and subject line Bug#1068100: fixed in armci-mpi 0.3.1-beta+git20221202.f1c4dae-1 has caused the Debian Bug report #1068100, regarding armci-mpi: autopkgtest spuriously fails to be marked as done. This means that you claim that

Processed: severity of 1062709 is grave

Processing commands for cont...@bugs.debian.org: > severity 1062709 grave Bug #1062709 [src:python-aiohttp] python-aiohttp: CVE-2024-23334 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1062709:

Bug#1067691: FTBFS: double free or corruption

Hi Andrey, on my aarch64 Raspberry Pi 4, I can successfully build the armel package. How can I find a way to reproduce that memory error? Maybe I should remove the fft const test. Thanks for the help. -- Matteo Bini

Processed: your mail

Processing commands for cont...@bugs.debian.org: > notfound 1068228 4:24.2.2-3 Bug #1068228 {Done: René Engelhard } [libreoffice-core] libreoffice-core: fails to open any documents (ods/odt) after latest upgrades, missing components No longer marked as found in versions libreoffice/4:24.2.2-3.

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 1068228 grave Bug #1068228 {Done: René Engelhard } [libreoffice-core] libreoffice-core: fails to open any documents (ods/odt) after latest upgrades, missing components Severity set to 'grave' from 'important' > tag 1068228 +

Processed: Re: Bug#1068393: src:pytest-testinfra: unsatisfied build dependency in testing: ansible

Processing control commands: > block -1 by 1061781 Bug #1068393 [src:pytest-testinfra] src:pytest-testinfra: unsatisfied build dependency in testing: ansible 1068393 was not blocked by any bugs. 1068393 was not blocking any bugs. Added blocking bug(s) of 1068393: 1061781 -- 1068393:

Bug#1068393: src:pytest-testinfra: unsatisfied build dependency in testing: ansible

Control: block -1 by 1061781 Hi Paul, On Thu, 2024-04-04 at 14:38 +0200, Paul Gevers wrote: > Dose [1] is reporting a build issue with your package, it's missing a > build dependency. Obviously your build dependencies shouldn't be > removed from testing, but unfortunately there are multiple

Processed: found 1068045 in 3.2.1-3

Processing commands for cont...@bugs.debian.org: > found 1068045 3.2.1-3 Bug #1068045 [libssl3,yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB There is no source info for the package 'libssl3' at version '3.2.1-3' with architecture '' There is no source info for the package

Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET

Hi Sean, On Sat, Apr 06, 2024 at 04:54:14PM +0800, Sean Whitton wrote: > control: reassign -1 libssl3,yapet > control: found -1 libssl3/3.1.5-1 > control: found -1 yapet/2.6-1 > control: retitle -1 libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB > > Hello, > > On Sat 30 Mar 2024 at

Bug#1068045: Bug#1064724: yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

Hi, On Thu, Mar 21, 2024 at 09:09:02AM +0100, Salvatore Bonaccorso wrote: > Hi Vladimir, > > On Thu, Mar 21, 2024 at 08:39:32PM +1300, Vladimir Petko wrote: > > Package: yapet > > Followup-For: Bug #1064724 > > User: ubuntu-de...@lists.ubuntu.com > > Usertags: origin-ubuntu noble ubuntu-patch >

Processed: tagging 1064724

Processing commands for cont...@bugs.debian.org: > tags 1064724 - patch Bug #1064724 [src:yapet] yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need

Bug#1066469: marked as done (tack: FTBFS: configure: error: No curses header-files found)

Your message dated Sat, 06 Apr 2024 13:05:15 + with message-id and subject line Bug#1066469: fixed in tack 1.09+20230201-1 has caused the Debian Bug report #1066469, regarding tack: FTBFS: configure: error: No curses header-files found to be marked as done. This means that you claim that the

Bug#1058291: marked as done (python-urllib3: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13)

Your message dated Sat, 6 Apr 2024 16:06:15 +0500 with message-id and subject line Re: Bug#1058291: python-urllib3: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13 has caused the Debian Bug report #1058291, regarding python-urllib3: FTBFS:

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 1058653 grave Bug #1058653 {Done: Rene Engelhard } [libreoffice-writer-nogui] libreoffice-writer-nogui: fails to convert ODT to PDF without libreoffice-core (libcuilo.so): Error: source file could not be loaded Severity set to 'grave'

Processed: bug 1056435 is forwarded to https://github.com/ponyorm/pony/issues/703, tagging 1056435

Processing commands for cont...@bugs.debian.org: > forwarded 1056435 https://github.com/ponyorm/pony/issues/703 Bug #1056435 [src:ponyorm] ponyorm's autopkg tests fail with Python 3.12 Set Bug forwarded-to-address to 'https://github.com/ponyorm/pony/issues/703'. > tags 1056435 + upstream Bug

Bug#1056458: marked as done (python-b2sdk's autopkg tests fail with Python 3.12)

Your message dated Sat, 6 Apr 2024 16:31:31 +0500 with message-id and subject line Re: Bug#1056458: python-b2sdk's autopkg tests fail with Python 3.12 has caused the Debian Bug report #1056458, regarding python-b2sdk's autopkg tests fail with Python 3.12 to be marked as done. This means that

Processed: bug 1058300 is forwarded to https://github.com/tholo/pytest-flake8/issues/100

Processing commands for cont...@bugs.debian.org: > forwarded 1058300 https://github.com/tholo/pytest-flake8/issues/100 Bug #1058300 [src:python-pytest-flake8] python-pytest-flake8: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Processed: affects 1063957

Processing commands for cont...@bugs.debian.org: > affects 1063957 src:python-b2sdk Bug #1063957 [src:python-pytest-lazy-fixture] python-pytest-lazy-fixture: autopkgtest regression with pytest 8 Bug #1063973 [src:python-pytest-lazy-fixture] python-marshmallow-sqlalchemy: autopkgtest regression

Processed: bug 1059647 is forwarded to https://github.com/scikit-fmm/scikit-fmm/issues/78

Processing commands for cont...@bugs.debian.org: > forwarded 1059647 https://github.com/scikit-fmm/scikit-fmm/issues/78 Bug #1059647 [src:scikit-fmm] scikit-fmm: autopkgtest failure with Python 3.12 Set Bug forwarded-to-address to 'https://github.com/scikit-fmm/scikit-fmm/issues/78'. > thanks

Bug#1063418: mdp ftbfs in unstable

It currently fails even earlier: ImportError while loading conftest '/<>/mdp/test/conftest.py'. mdp/__init__.py:133: in utils.symeig = configuration.get_symeig(numx_linalg) mdp/configuration.py:335: in get_symeig args = getargs(numx_linalg.eigh)[0] /usr/lib/python3.11/inspect.py:1379: in

Bug#1068502: Dead upstream and broken, remove or switch to a fork?

Source: python-pytest-flake8 Severity: serious https://github.com/tholo/pytest-flake8/issues/98 https://github.com/tholo/pytest-flake8/issues/97 https://github.com/tholo/pytest-flake8/issues/92 https://github.com/tholo/pytest-flake8/issues/91 -- System Information: Debian Release: trixie/sid

Bug#1068500: Installs /usr/LICENSE

Package: python3-xmlrunner Version: 3.2.0-2 Severity: serious drwxr-xr-x root/root 0 2023-01-22 01:39 ./ drwxr-xr-x root/root 0 2023-01-22 01:39 ./usr/ -rw-r--r-- root/root 1532 2022-02-02 16:17 ./usr/LICENSE Note that it's caught by lintian: W: python3-xmlrunner:

Bug#1068473: icinga2: crashes on startup on ppc64el

On 4/6/24 1:29 PM, Aurelien Jarno wrote: On 2024-04-06 08:01, Sebastiaan Couwenberg wrote: On 4/5/24 9:51 PM, Aurelien Jarno wrote: For Bookworm given we can not fix the compiler easily, I propose to just build icinga2 with -O1 on ppc64el. If you are fine with that option, I can take care of

Bug#1068497: golang-github-antonini-golibjpegturbo: FTBFS: Tries to access the network during build

Package: src:golang-github-antonini-golibjpegturbo Version: 0.0~git20141208.c03a2fa-2 Severity: serious Tags: ftbfs [...] github.com/antonini/golibjpegturbo dh_auto_test -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 20

Bug#1064852: fixed in incus 0.6-2

(Touching bug to reset AUTORM countdown.) signature.asc Description: This is a digitally signed message part

Processed: Processed: Severity for 1036805 was serious and we even released with it

Processing commands for cont...@bugs.debian.org: > severity 1036805 important Bug #1036805 [libreoffice-writer] libreoffice's toolbar buttons became hard to see after upgrading to Debian 12 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you

Bug#1068473: icinga2: crashes on startup on ppc64el

On 2024-04-06 08:01, Sebastiaan Couwenberg wrote: > On 4/5/24 9:51 PM, Aurelien Jarno wrote: > > For Bookworm given we can not fix the compiler easily, I propose to just > > build icinga2 with -O1 on ppc64el. If you are fine with that option, I > > can take care of proposing a patch and submitting

Processed: affects 1068349 + src:python-pint

Processing commands for cont...@bugs.debian.org: > affects 1068349 + src:python-pint Bug #1068349 [python3-nbconvert,python3-lxml] nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean Added indication that 1068349 affects src:python-pint > block 1067229 by 1068349 Bug #1067229

Bug#1065547: marked as done (gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments)

Your message dated Sat, 06 Apr 2024 11:05:54 + with message-id and subject line Bug#1065547: fixed in pygobject 3.48.2-1 has caused the Debian Bug report #1065547, regarding gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments to be marked as done. This means that you claim

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

Your message dated Sat, 06 Apr 2024 10:00:10 + with message-id and subject line Bug#1064170: fixed in mediastreamer2 1:5.2.0+dfsg-3.2 has caused the Debian Bug report #1064170, regarding mediastreamer2: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim

Bug#1063419: marked as done (sugar-artwork: Please package version 0.121 needed by sugar-session)

Your message dated Sat, 06 Apr 2024 09:36:56 + with message-id and subject line Bug#1063419: fixed in sugar-artwork 0.121-1 has caused the Debian Bug report #1063419, regarding sugar-artwork: Please package version 0.121 needed by sugar-session to be marked as done. This means that you claim

Bug#1068157: siridb-server: FTBFS on armhf: ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT

Hi William, I noticed you "binNMU"-ed siridb-server in Ubuntu where it built successfully on all arches. In Debian I got the bug below reported. Any idea what the difference could be between the state of Debian and the state of Ubuntu that causes this? reproducible-builds [1] confirms that

Bug#1068479: libreoffice-writer: space between paragraphs missing in spacing and indentation

tag 1068479 + moreinfo tag 1068479 + unreproducible severity 1068479 important thanks Hi, Am 06.04.24 um 00:34 schrieb José Luis González: The setting for spacing between paragraphs is missing in the spacing and indentation tab of the paragraph dialog. ? It's definitely there. Format

Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET

Hello, On Sat 30 Mar 2024 at 03:01pm +01, Sebastian Andrzej Siewior wrote: > On 30 March 2024 13:14:37 CET, Sean Whitton wrote: > >>I downgraded, changed the password for my database to 'asdf', >>changed it back to the password it had before, upgraded libssl3, >>and the bug did not appear. >>

Processed: Bug#1068479: libreoffice-writer: space between paragraphs missing in spacing and indentation

Processing commands for cont...@bugs.debian.org: > tag 1068479 + moreinfo Bug #1068479 [libreoffice-writer] libreoffice-writer: space between paragraphs missing in spacing and indentation Added tag(s) moreinfo. > tag 1068479 + unreproducible Bug #1068479 [libreoffice-writer] libreoffice-writer:

Bug#1068463: marked as done (procyon: Untrusted code execution via cwd in classpath)

Your message dated Sat, 06 Apr 2024 09:21:26 + with message-id and subject line Bug#1068463: fixed in procyon 0.6.0-2 has caused the Debian Bug report #1068463, regarding procyon: Untrusted code execution via cwd in classpath to be marked as done. This means that you claim that the problem

Processed: notfound 1068045 in libssl3/3.1.5-1, found 1068045 in openssl/3.0.13-1~deb12u1 ...

Processing commands for cont...@bugs.debian.org: > notfound 1068045 libssl3/3.1.5-1 Bug #1068045 [libssl3,yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB The source libssl3 and version 3.1.5-1 do not appear to match any binary packages No longer marked as found in versions

Processed: Re: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET

Processing control commands: > reassign -1 libssl3,yapet Bug #1068045 [libssl3] libssl3: breaks YAPET Bug reassigned from package 'libssl3' to 'libssl3,yapet'. No longer marked as found in versions openssl/3.0.13-1~deb12u1. No longer marked as fixed in versions openssl/3.0.11-1~deb12u2. > found

Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET

control: reassign -1 libssl3,yapet control: found -1 libssl3/3.1.5-1 control: found -1 yapet/2.6-1 control: retitle -1 libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB Hello, On Sat 30 Mar 2024 at 03:01pm +01, Sebastian Andrzej Siewior wrote: >> >>> Also, yapet is unchanged in unstable.

Bug#1036805: Processed: Severity for 1036805 was serious and we even released with it

severity 1036805 important thanks Hi, > Serious severity because it has a major effect on the usability of the > package without rendering it completely unusable, not minor No, it's not. "serious" has it's own meaning though and that's not it. At most it's important but I don't buy this

Processed: Bug#1068463 marked as pending in procyon

Processing control commands: > tag -1 pending Bug #1068463 [procyon-decompiler] procyon: Untrusted code execution via cwd in classpath Added tag(s) pending. -- 1068463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068463 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1068463: marked as pending in procyon

Control: tag -1 pending Hello, Bug #1068463 in procyon 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#1067796: marked as done (mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment)

Your message dated Sat, 06 Apr 2024 08:42:52 + with message-id and subject line Bug#1067796: fixed in mailscripts 29-1 has caused the Debian Bug report #1067796, regarding mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment to be marked as done. This

Bug#1067796: mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment

control: tag -1 + pending Hello, On Sat 06 Apr 2024 at 01:23am -04, Daniel Kahn Gillmor wrote: > On Sat 2024-04-06 11:40:14 +0800, Sean Whitton wrote: >> On Thu 04 Apr 2024 at 06:37pm -04, Daniel Kahn Gillmor wrote: >> >>> On Wed 2024-04-03 13:03:19 +0800, Sean Whitton wrote: Thanks, but

Processed: Re: Bug#1067796: mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment

Processing control commands: > tag -1 + pending Bug #1067796 [src:mailscripts] mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment Added tag(s) pending. -- 1067796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067796 Debian Bug Tracking System Contact

Processed: severity of 1068179 is important

Processing commands for cont...@bugs.debian.org: > severity 1068179 important Bug #1068179 [ghc] FTBFS: error: warning: assignment to ‘ffi_arg’ {aka ‘long unsigned int’} from ‘HsPtr’ {aka ‘void *’} makes integer from pointer without a cast Severity set to 'important' from 'serious' > thanks

Bug#1068204: marked as done (pdl: FTBFS on i386: Failed 1/45 test programs. 2/2262 subtests failed.)

Your message dated Sat, 06 Apr 2024 07:34:36 + with message-id and subject line Bug#1068204: fixed in pdl 1:2.087-1 has caused the Debian Bug report #1068204, regarding pdl: FTBFS on i386: Failed 1/45 test programs. 2/2262 subtests failed. to be marked as done. This means that you claim that

Processed: reassign 1068179 to ghc, affects 1068179 ...

Processing commands for cont...@bugs.debian.org: > reassign 1068179 ghc 9.4.7-3 Bug #1068179 [src:haskell-gi-gtk] FTBFS: error: warning: assignment to ‘ffi_arg’ {aka ‘long unsigned int’} from ‘HsPtr’ {aka ‘void *’} makes integer from pointer without a cast Bug reassigned from package

Bug#1068473: icinga2: crashes on startup on ppc64el

On 4/5/24 9:51 PM, Aurelien Jarno wrote: For Bookworm given we can not fix the compiler easily, I propose to just build icinga2 with -O1 on ppc64el. If you are fine with that option, I can take care of proposing a patch and submitting it to the stable release team. A patch for this is very