Processed: notfound 1075824 in 1:9.0.1+ds-1, fixed 1075824 in 1:9.0.1+ds-1

2024-07-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1075824 1:9.0.1+ds-1 Bug #1075824 [src:qemu] qemu: CVE-2024-4467 Ignoring request to alter found versions of bug #1075824 to the same values previously set > fixed 1075824 1:9.0.1+ds-1 Bug #1075824 [src:qemu] qemu: CVE-2024-4467 Marked a

Processed: Re: Bug#1075824: qemu: CVE-2024-4467

2024-07-05 Thread Debian Bug Tracking System
Processing control commands: > found -1 Bug #1075824 {Done: Michael Tokarev } [src:qemu] qemu: CVE-2024-4467 No longer marked as fixed in versions 1:9.0.1+ds-1 and reopened. -- 1075824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075824 Debian Bug Tracking System Contact ow...@bugs.debia

Bug#1075824: qemu: CVE-2024-4467

2024-07-05 Thread Michael Tokarev
Control: found -1 06.07.2024 00:35, Salvatore Bonaccorso wrote: .. This is fixed by qemu uploaded earlier today. Patches are already prepared for bookworm (for qemu 7.2.x series) and already verified upstream and passed the tests. Yes thanks, had only the 1:8.2.5+ds-2 initially to check. Sur

Bug#1071930: marked as done (kwallet-pam: Searches for libgcrypt with libgcrypt-config)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Sat, 06 Jul 2024 06:20:02 + with message-id and subject line Bug#1071930: fixed in kwallet-pam 5.27.11-2 has caused the Debian Bug report #1071930, regarding kwallet-pam: Searches for libgcrypt with libgcrypt-config to be marked as done. This means that you claim that the p

Processed: tagging 1071930

2024-07-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1071930 + pending Bug #1071930 [src:kwallet-pam] kwallet-pam: Searches for libgcrypt with libgcrypt-config Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071930: https://bugs.debian.o

Bug#1061001: marked as done (scikit-fmm: FTBFS: avx512pfintrin.h:180:3: error: ‘base’ may be used uninitialized [-Werror=maybe-uninitialized])

2024-07-05 Thread Debian Bug Tracking System
Your message dated Sat, 06 Jul 2024 05:36:47 + with message-id and subject line Bug#1061001: fixed in scikit-fmm 2024.05.29-1 has caused the Debian Bug report #1061001, regarding scikit-fmm: FTBFS: avx512pfintrin.h:180:3: error: ‘base’ may be used uninitialized [-Werror=maybe-uninitialized] t

Bug#1059647: marked as done (scikit-fmm: autopkgtest failure with Python 3.12)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Sat, 06 Jul 2024 05:36:47 + with message-id and subject line Bug#1059647: fixed in scikit-fmm 2024.05.29-1 has caused the Debian Bug report #1059647, regarding scikit-fmm: autopkgtest failure with Python 3.12 to be marked as done. This means that you claim that the problem

Bug#1074673: libktoblzcheck: FTBFS: tests failed

2024-07-05 Thread Micha Lenk
Control: tags -1 moreinfo Hi Lucas, Thank you for taking the time to file this bug report. Unfortunately not all reproduction details are available. And given these two lines in the logs: > 4: Could not read directory "/usr/share/ktoblzcheck": No such file or > directory > 4: Oops, no bank da

Processed: Re: Bug#1074673: libktoblzcheck: FTBFS: tests failed

2024-07-05 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #1074673 [src:libktoblzcheck] libktoblzcheck: FTBFS: tests failed Added tag(s) moreinfo. -- 1074673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1073339: marked as done (abiword: FTBFS: ut_stringbuf.cpp:578:17: error: ‘xmlFree’ was not declared in this scope; did you mean ‘xmlFreeURI’?)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Sat, 06 Jul 2024 05:04:24 + with message-id and subject line Bug#1073339: fixed in abiword 3.0.5~dfsg-3.3 has caused the Debian Bug report #1073339, regarding abiword: FTBFS: ut_stringbuf.cpp:578:17: error: ‘xmlFree’ was not declared in this scope; did you mean ‘xmlFreeURI’

Bug#1070892: marked as done (abiword: Please use pkg-config instead of libgcrypt-config to locate libgcrypt)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Sat, 06 Jul 2024 05:04:24 + with message-id and subject line Bug#1070892: fixed in abiword 3.0.5~dfsg-3.3 has caused the Debian Bug report #1070892, regarding abiword: Please use pkg-config instead of libgcrypt-config to locate libgcrypt to be marked as done. This means th

Bug#1073397: marked as done (vedo: FTBFS: build-dependency not installable: python3-vtk9 (< 9.1.1))

2024-07-05 Thread Debian Bug Tracking System
Your message dated Sat, 06 Jul 2024 02:36:28 + with message-id and subject line Bug#1073397: fixed in vedo 2024.5.2-1 has caused the Debian Bug report #1073397, regarding vedo: FTBFS: build-dependency not installable: python3-vtk9 (< 9.1.1) to be marked as done. This means that you claim that

Bug#1073344: marked as done (libsmpp34: FTBFS: ../test_apps/esme.h:32:16: error: implicit declaration of function ‘strtol’; did you mean ‘strtok’? [-Werror=implicit-function-declaration])

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 23:49:05 + with message-id and subject line Bug#1073344: fixed in libsmpp34 1.14.4-1 has caused the Debian Bug report #1073344, regarding libsmpp34: FTBFS: ../test_apps/esme.h:32:16: error: implicit declaration of function ‘strtol’; did you mean ‘strtok’?

Bug#1075832: tk-html3: Completely remove hv3 (and tk-html3), for good reasons

2024-07-05 Thread Boyuan Yang
Source: tk-html3 Severity: serious Version: 3.0~fossil20110109-9 X-Debbugs-CC: oleb...@debian.org Dear Debian tk-html3/hv3 package maintainers, Today I encountered a discussion around package hv3 in Debian. With some brief investigation, I found some abnormally high popcon values [2] for hv3 and

Bug#1075793: plastimatch FTBFS with DCMTK 3.6.8

2024-07-05 Thread Gregory Sharp
Hi Mathieu, Thank you for the report. This was fixed long ago upstream, but I did not deploy a new version. Sorry for the FTBFS, that is my bad. Greg Sharp gregsh...@geocities.com

Bug#1075794: marked as done (orthanc-wsi FTBFS with DCMTK 3.6.8)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 23:21:18 + with message-id and subject line Bug#1075794: fixed in orthanc-wsi 2.0+dfsg-3 has caused the Debian Bug report #1075794, regarding orthanc-wsi FTBFS with DCMTK 3.6.8 to be marked as done. This means that you claim that the problem has been dealt

Bug#1075795: marked as done (orthanc FTBFS with DCMTK 3.6.8)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 22:35:43 + with message-id and subject line Bug#1075795: fixed in orthanc 1.12.4+dfsg-2 has caused the Debian Bug report #1075795, regarding orthanc FTBFS with DCMTK 3.6.8 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1075824: closed by Michael Tokarev (Re: Bug#1075824: qemu: CVE-2024-4467)

2024-07-05 Thread Salvatore Bonaccorso
Hi, On Fri, Jul 05, 2024 at 09:27:03PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:qemu package: > > #1075824: qemu: CVE-2024-4467 > > It has been closed by Michael Tokarev . > > Their explanation is at

Bug#1075824: marked as done (qemu: CVE-2024-4467)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Sat, 6 Jul 2024 00:23:36 +0300 with message-id <85f6d51a-8c62-46ce-b38b-7ec5d4409...@tls.msk.ru> and subject line Re: Bug#1075824: qemu: CVE-2024-4467 has caused the Debian Bug report #1075824, regarding qemu: CVE-2024-4467 to be marked as done. This means that you claim that th

Bug#1075712: marked as done (graphite-carbon: daemon does not start)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 21:05:52 + with message-id and subject line Bug#1075712: fixed in graphite-carbon 1.1.10-1 has caused the Debian Bug report #1075712, regarding graphite-carbon: daemon does not start to be marked as done. This means that you claim that the problem has been

Bug#1074696: marked as done (graphite-carbon: FTBFS: AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you mean: 'read'?)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 21:05:51 + with message-id and subject line Bug#1074696: fixed in graphite-carbon 1.1.10-1 has caused the Debian Bug report #1074696, regarding graphite-carbon: FTBFS: AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you mean: 'read'? to

Bug#1072207: marked as done (click: fails to upgrade from bookworm: prerm fails to run click)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 21:05:08 + with message-id and subject line Bug#1072207: fixed in click 0.5.2-4 has caused the Debian Bug report #1072207, regarding click: fails to upgrade from bookworm: prerm fails to run click to be marked as done. This means that you claim that the pro

Bug#1065863: marked as done (galpy: Please drop dependencies on python3-distutils)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 21:05:28 + with message-id and subject line Bug#1065863: fixed in galpy 1.8.1-3 has caused the Debian Bug report #1065863, regarding galpy: Please drop dependencies on python3-distutils to be marked as done. This means that you claim that the problem has be

Bug#1075824: qemu: CVE-2024-4467

2024-07-05 Thread Salvatore Bonaccorso
Source: qemu Version: 1:8.2.5+ds-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for qemu. CVE-2024-4467[0]: | A flaw was found in the QEMU disk image utility (qemu-im

Bug#1072207: click: fails to upgrade from bookworm: prerm fails to run click

2024-07-05 Thread Mike Gabriel
On Fr 05 Jul 2024 22:29:30 CEST, Mike Gabriel wrote: Do I actually upload a second time then, because I think that at build time of click, the already installed dh_click gets used? Remembered it now and found the part in d/rules. Click uses its own dh_click from the source tree at build ti

Processed: closing 1067312

2024-07-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1067312 2024.1-1 Bug #1067312 [src:spirv-tools] spirv-tools: FTBFS: operand.kinds-unified1.inc:566:97: error: ‘SPV_OPERAND_TYPE_NAMED_MAXIMUM_NUMBER_OF_REGISTERS’ was not declared in this scope Marked as fixed in versions spirv-tools/2024

Bug#1072207: click: fails to upgrade from bookworm: prerm fails to run click

2024-07-05 Thread Mike Gabriel
Hi, On Do 30 Mai 2024 12:14:59 CEST, Andreas Beckmann wrote: Package: click Version: 0.5.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'bookworm'. It installed fine in 'bookworm', then th

Processed: Bug#1072207 marked as pending in click

2024-07-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1072207 [click] click: fails to upgrade from bookworm: prerm fails to run click Added tag(s) pending. -- 1072207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1072207: marked as pending in click

2024-07-05 Thread Mike Gabriel
Control: tag -1 pending Hello, Bug #1072207 in click 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/ubports-team/click/-/commit/15ceca04c61f0ec4e62b81b7d8cf155

Processed: retitle 1074716 to package-update-indicator FTBFS with gettext 0.22

2024-07-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1074716 package-update-indicator FTBFS with gettext 0.22 Bug #1074716 [src:package-update-indicator] package-update-indicator: FTBFS: make[2]: *** [Makefile:227: org.guido-berhoerster.code.package-update-indicator.desktop] Error 1 Change

Bug#1075821: summer can get size wrong on 32-bit host!

2024-07-05 Thread Ian Jackson
Package: chiark-utils-bin Version: 7.0.1 Severity: serious Seen in a backup confirmation checksum diff -08b4ed2ab7e1723fdf84ca56f055cabb 5656798178 660 0 ... +08b4ed2ab7e1723fdf84ca56f055cabb 1361830882 660 0 ... These two values differ by 2^32. (This is with a l

Bug#1065899: marked as done (lomiri-calculator-app: Please drop dependencies on python3-distutils)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 19:18:58 + with message-id and subject line Bug#1065899: fixed in lomiri-calculator-app 4.0.2-2 has caused the Debian Bug report #1065899, regarding lomiri-calculator-app: Please drop dependencies on python3-distutils to be marked as done. This means that y

Processed: Re: Bug#1067507: lomiri-ui-toolkit ftbfs with Python 3.12

2024-07-05 Thread Debian Bug Tracking System
Processing control commands: > close -1 Bug #1067507 [src:lomiri-ui-toolkit] lomiri-ui-toolkit ftbfs with Python 3.12 Marked Bug as done > fixed -1 1.3.5100+dfsg-1 Bug #1067507 {Done: Mike Gabriel } [src:lomiri-ui-toolkit] lomiri-ui-toolkit ftbfs with Python 3.12 Marked as fixed in versions lomir

Bug#1067507: lomiri-ui-toolkit ftbfs with Python 3.12

2024-07-05 Thread Mike Gabriel
Control: close -1 Control: fixed -1 1.3.5100+dfsg-1 On Fr 22 Mär 2024 17:44:56 CET, Matthias Klose wrote: Package: src:lomiri-ui-toolkit Version: 1.3.5012+dfsg-5 Severity: important Tags: sid trixie patch User: debian-pyt...@lists.debian.org Usertags: python3.12 lomiri-ui-toolkit ftbfs with P

Bug#1065899: marked as pending in lomiri-calculator-app

2024-07-05 Thread Mike Gabriel
Control: tag -1 pending Hello, Bug #1065899 in lomiri-calculator-app 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/ubports-team/lomiri-calculator-app/-/commit

Processed: Bug#1065899 marked as pending in lomiri-calculator-app

2024-07-05 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1065899 [src:lomiri-calculator-app] lomiri-calculator-app: Please drop dependencies on python3-distutils Added tag(s) pending. -- 1065899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065899 Debian Bug Tracking System Contact ow...@bugs.d

Bug#1075813: marked as done (Krb5: fails to pick up debian configuration)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 17:49:49 + with message-id and subject line Bug#1075813: fixed in krb5 1.21.3-3 has caused the Debian Bug report #1075813, regarding Krb5: fails to pick up debian configuration to be marked as done. This means that you claim that the problem has been dealt

Bug#1075814: plotpy: Fails to build on arm64

2024-07-05 Thread Jeremy Bícha
Source: plotpy Version: 2.4.0-1 Severity: serious Tags: ftbfs User: debian-...@lists.debian.org Usertags: arm64 X-Debbugs-CC: debian-...@lists.debian.org, lola...@debian.org plotpy fails to build on arm64. Because it built once on arm64, its build needs to be fixed or you could file a RM bug to re

Bug#1075815: plotpy: Failing autopkgtests

2024-07-05 Thread Jeremy Bícha
Source: plotpy Version: 2.4.0-1 Severity: serious X-Debbugs-CC: debian-...@lists.debian.org, lola...@debian.org plotpy is unable to migrate to Testing because its autopkgtests are failing. (This is true even though its autopkgtests have always failed.) https://qa.debian.org/excuses.php?package=pl

Processed: found 1063648 in 1.21.3-2

2024-07-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1063648 1.21.3-2 Bug #1063648 {Done: Sam Hartman } [src:krb5] krb5: FTBFS on IPv6-only buildds: "Can't resolve hostname" in dh_auto_test Marked as found in versions krb5/1.21.3-2; no longer marked as fixed in versions krb5/1.21.3-2 and reo

Bug#1075813: Krb5: fails to pick up debian configuration

2024-07-05 Thread Sam Hartman
package: krb5-kdc severity: grave version: 1.21.3-2 A typo in version 1.21.3-2 incorrectly interrupts the configure args, among other things causing sysconfdir to be incorrectly set. This breaks krb5-kdc because it does not read /etc/krb5kdc/kdc.conf. Found by CI tests. signature.asc Descriptio

Bug#1075785: marked as done (exim4: CVE-2024-39929: Incorrect parsing of multiline rfc2231 header filename)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 16:35:06 + with message-id and subject line Bug#1075785: fixed in exim4 4.98~RC3-2 has caused the Debian Bug report #1075785, regarding exim4: CVE-2024-39929: Incorrect parsing of multiline rfc2231 header filename to be marked as done. This means that you

Bug#1075804: marked as done (rust-libp2p-identity: Fails to build)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 18:28:04 +0200 with message-id <172019688421.255930.9675021562993103...@auryn.jones.dk> and subject line Re: Bug#1075804: rust-libp2p-identity: Fails to build has caused the Debian Bug report #1075804, regarding rust-libp2p-identity: Fails to build to be marked a

Bug#1075799: chiark-utils: ftbfs with time_t errors

2024-07-05 Thread Ian Jackson
Jeremy Bícha writes ("Bug#1075799: chiark-utils: ftbfs with time_t errors"): > chiark-utils fails to build on 64-bit architectures with errors like: > > /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is > allowed only with _FILE_OFFSET_BITS=64" >26 | # error "_TIME_BITS=64

Bug#1075811: autokey-qt can be installed but will nor run

2024-07-05 Thread Joe
Package: autokey-qt Version: 0.95.10-2.1 Severity: grave Justification: renders package unusable Dear Maintainer, Autokey is loaded on login, but not always used. Today I found it did not function, and had not been loaded. I believe it has been used within the last three weeks. Installing autoke

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-07-05 Thread Sam Hartman
> "Chris" == Chris Hofstaedtler writes: Chris> Adam (adsb) points out that the test code in Chris> lib/rpc/unit-test/client.c [1] uses code that does not Chris> support IPv6(-only). I.e. gethostbyname for a name that has Chris> no IPv4 address will fail. So, are the builds goi

Processed: (No Subject)

2024-07-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1072969 https://github.com/pytorch/pytorch/issues/129228 Bug #1072969 [src:pytorch] pytorch: CVE-2024-5480 Set Bug forwarded-to-address to 'https://github.com/pytorch/pytorch/issues/129228'. > End of message, stopping processing here.

Bug#1074222: pycorrfit FTBFS with Python 3.12 as default

2024-07-05 Thread Alex Mestiashvili
Hi All, AFAIK pycorrfit GUI should know about the location of the pdf file. Though it is a minor issue. Please feel free to upload, otherwise I'll try to have a look the next week. Thanks, Alex On 7/5/24 15:27, Bo YU wrote: Hi, On Fri, Jul 5, 2024 at 1:55 PM Andreas Tille wrote: Control:

Bug#1074222: pycorrfit FTBFS with Python 3.12 as default

2024-07-05 Thread Bo YU
Hi, On Fri, Jul 5, 2024 at 1:55 PM Andreas Tille wrote: > > Control: tags -1 pending > > Am Tue, Jul 02, 2024 at 05:07:08PM +0200 schrieb Andreas Tille: > > I'm fine with whatever solution you might find and you can > > perfectly skip me when doing some team upload. > > Could someone please fix >

Processed: Debian bugs #1057286, #1057287, #1074722, #1074575, #1074576, #1070376, #1051496, #1069767

2024-07-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1057286 + pending Bug #1057286 [xtrkcad] xtrkcad: Please package current stable version 5.2.2aGA Added tag(s) pending. > tags 1057287 + pending Bug #1057287 [src:xtrkcad] xtrkcad: please update Maintainer / Uploaders list Added tag(s) pending

Bug#1075804: rust-libp2p-identity: Fails to build

2024-07-05 Thread Jeremy Bícha
Source: rust-libp2p-identity Version: 0.2.9+ds-2 Severity: serious Tags: ftbfs rust-libp2p-identity fails to build. Here's the build log excerpt: error: failed to select a version for the requirement `rmp-serde = "^1.3"` candidate versions found which didn't match: 1.1.1 https://buildd.debian.or

Bug#1069361: marked as done (libgweather4: FTBFS on arm64: Location 'Greenland' has invalid timezone 'America/Godthab')

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 12:35:06 + with message-id and subject line Bug#1069361: fixed in libgweather4 4.4.2-2 has caused the Debian Bug report #1069361, regarding libgweather4: FTBFS on arm64: Location 'Greenland' has invalid timezone 'America/Godthab' to be marked as done. This

Bug#1073464: marked as done (libgweather4: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 12:35:06 + with message-id and subject line Bug#1069361: fixed in libgweather4 4.4.2-2 has caused the Debian Bug report #1069361, regarding libgweather4: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monito

Bug#1073384: marked as done (tpm2-pytss: FTBFS: make: *** [debian/rules:17: binary] Error 25)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 11:49:05 + with message-id and subject line Bug#1073384: fixed in tpm2-pytss 2.3.0-1 has caused the Debian Bug report #1073384, regarding tpm2-pytss: FTBFS: make: *** [debian/rules:17: binary] Error 25 to be marked as done. This means that you claim that th

Bug#1075799: chiark-utils: ftbfs with time_t errors

2024-07-05 Thread Jeremy Bícha
Source: chiark-utils Version: 7.0.1 Severity: serious Tags: ftbfs User: debian-...@lists.debian.org Usertags: time-t chiark-utils fails to build on 64-bit architectures with errors like: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

Bug#1075798: tifffile: Failing autopkgtest on s390x

2024-07-05 Thread Jeremy Bícha
Source: tifffile Version: 20240702-1 Severity: serious X-Debbugs-CC: oleb...@debian.org tifffile is unable to migrate to Testing because its autopkgtest is failing on s390x which is a release architecture. https://qa.debian.org/excuses.php?package=tifffile Additionally, a source-only upload is n

Bug#1074731: marked as done (gtkhash: FTBFS: make[4]: *** [Makefile:570: libgtkhash-properties-caja.caja-extension] Error 1)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 10:04:38 + with message-id and subject line Bug#1074731: fixed in gtkhash 1.5-2 has caused the Debian Bug report #1074731, regarding gtkhash: FTBFS: make[4]: *** [Makefile:570: libgtkhash-properties-caja.caja-extension] Error 1 to be marked as done. This m

Bug#1075795: orthanc FTBFS with DCMTK 3.6.8

2024-07-05 Thread Mathieu Malaterre
Source: orthanc Version: 1.12.4+dfsg-1 Severity: serious Tags: ftbfs -- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable OPENSSL_ROOT_DIR (missing: OPENSSL_CRYPTO_LIBRARY OPENSSL_INCLUDE_DIR) CMake Error at /<>/OrthancFramework/Resources/CMake/OpenSslConfi

Bug#1075794: orthanc-wsi FTBFS with DCMTK 3.6.8

2024-07-05 Thread Mathieu Malaterre
Source: orthanc-wsi Version: 2.0+dfsg-2 Severity: serious Tags: ftbfs /<>/Framework/Inputs/CytomineImage.cpp:36:10: fatal error: openssl/hmac.h: No such file or directory 36 | #include | ^~~~ compilation terminated. https://people.debian.org/~emollier/transitions/d

Bug#1064232: marked as done (rust-axum: Failing autopkgtests)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jul 2024 09:19:44 + with message-id and subject line Bug#1064232: fixed in rust-axum 0.6.20-19 has caused the Debian Bug report #1064232, regarding rust-axum: Failing autopkgtests to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1075792: sight FTBFS with DCMTK 3.6.8

2024-07-05 Thread Mathieu Malaterre
Source: sight Version: 23.1.0-3 Severity: serious Tags: ftbfs sight::core::com::Slot&, unsigned int, const std::__cxx11::basic_string&)>::sptr)’: /<>/libs/io/dimse/SeriesEnquirer.cpp:140:41: error: ‘UID_RFC2557MIMEEncapsulationTransferSyntax’ was not declared in this scope; did you mean ‘UID_RETIR

Bug#1075793: plastimatch FTBFS with DCMTK 3.6.8

2024-07-05 Thread Mathieu Malaterre
Source: plastimatch Version: 1.9.4+dfsg.1-2 Severity: serious Tags: ftbfs /<>/src/plastimatch/base/dcmtk_rtss.cxx: In member function ‘void Dcmtk_rt_study::rtss_save(const char*)’: /<>/src/plastimatch/base/dcmtk_rtss.cxx:475:46: error: ‘DCM_ROIObservationLabel’ was not declared in this scope; did

Bug#1072847: fixed in lacme 0.8.3-1

2024-07-05 Thread Guilhem Moulin
Hi Sakari, On Fri, 05 Jul 2024 at 08:23:56 +, Sakari Ailus wrote: > The removal of the intermediate certificates (or not including the current > ones) however is an issue as the server using the issued certificate still > needs to provide them to the clients. The path pointed to by ‛certifica

Bug#1072847: fixed in lacme 0.8.3-1

2024-07-05 Thread Sakari Ailus
Hi Guilhem, Thank you for fixing the post-issuange logic. The removal of the intermediate certificates (or not including the current ones) however is an issue as the server using the issued certificate still needs to provide them to the clients. Some clients may already have them, such as Firefox

Bug#1070910: marked as done (llvm-toolchain-18: autopkgtest fails on amd64)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 5 Jul 2024 10:03:06 +0200 with message-id <864825be-7ae8-44d0-a60f-6fcbdf2ee...@debian.org> and subject line Fixed: llvm-toolchain-18: autopkgtest fails on amd64 has caused the Debian Bug report #1070910, regarding llvm-toolchain-18: autopkgtest fails on amd64 to be marked a

Bug#1074175: netkit-rwho: remove for trixie?

2024-07-05 Thread Simon Josefsson
Hi. Most tools from netkit are candidates for migration to GNU InetUtils, and rwho(d) may be another one -- see email and bug report below. Cc'ing debian-devel to have broader discussion. First, I think we need to understand the rationale for doing anything about 'netkit-rwho': do we want to do s

Bug#1071885: marked as done (rust-glycin: FTBFS: unsatisfiable build-dependencies)

2024-07-05 Thread Debian Bug Tracking System
Your message dated Fri, 5 Jul 2024 09:28:54 +0200 with message-id <20741d73-593a-4d83-a5af-3eb7ceb8c...@riseup.net> and subject line has caused the Debian Bug report #1071885, regarding rust-glycin: FTBFS: unsatisfiable build-dependencies to be marked as done. This means that you claim that the p