Bug#1069841: marked as done (python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab')

2024-04-25 Thread Debian Bug Tracking System
Your message dated Fri, 26 Apr 2024 05:04:24 + with message-id and subject line Bug#1069841: fixed in python-icalendar 5.0.12-1 has caused the Debian Bug report #1069841, regarding python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab' to be marked as done. This

Bug#1069357: cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 --test-arg

2024-04-25 Thread Julian Gilbey
On Sat, Apr 20, 2024 at 01:59:57PM +0200, Lucas Nussbaum wrote: > Source: cpp-httplib > Version: 0.14.3+ds-1.1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 > > Hi, > > During a rebuild of all

Bug#1060939: marked as done (python-workalendar: FTBFS: CalendarError: Need configure 2024 for China.)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Fri, 26 Apr 2024 04:19:14 + with message-id and subject line Bug#1069827: Removed package(s) from unstable has caused the Debian Bug report #1060939, regarding python-workalendar: FTBFS: CalendarError: Need configure 2024 for China. to be marked as done. This means that

Bug#1069381: marked as done (sslh: FTBFS on arm64: cat: /tmp/bZv3B_U_mJ/sslh.pid: No such file or directory)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Fri, 26 Apr 2024 04:19:22 + with message-id and subject line Bug#1069381: fixed in sslh 2.1.1-1 has caused the Debian Bug report #1069381, regarding sslh: FTBFS on arm64: cat: /tmp/bZv3B_U_mJ/sslh.pid: No such file or directory to be marked as done. This means that you

Bug#1068414: marked as done (obs-advanced-scene-switcher - still depends on old libcurl after binnmu)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 22:34:42 + with message-id and subject line Bug#1068414: fixed in obs-advanced-scene-switcher 1.25.5-1 has caused the Debian Bug report #1068414, regarding obs-advanced-scene-switcher - still depends on old libcurl after binnmu to be marked as done. This

Bug#1069624: marked as done (rapidfuzz: Fails to build on arch: all)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 21:48:49 + with message-id and subject line Bug#1069624: fixed in rapidfuzz 3.6.2+ds-3 has caused the Debian Bug report #1069624, regarding rapidfuzz: Fails to build on arch: all to be marked as done. This means that you claim that the problem has been

Bug#1069586: marked as done (Chromium native Wayland support broken)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 21:48:05 + with message-id and subject line Bug#1069586: fixed in chromium 124.0.6367.60-2 has caused the Debian Bug report #1069586, regarding Chromium native Wayland support broken to be marked as done. This means that you claim that the problem has been

Bug#1068936: marked as pending in libcanberra

2024-04-25 Thread Michael Biebl
Control: tag -1 pending Hello, Bug #1068936 in libcanberra reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1068936 marked as pending in libcanberra

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1068936 [libcanberra-gtk3-module] libcanberra-gtk3-module: hard-coded dependency on libgtk-3-0 Added tag(s) pending. -- 1068936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068936 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1069859: atop: Fix atop for 64-bit time_t on arm

2024-04-25 Thread Steve Langasek
Package: atop Version: 2.10.0-2 Severity: grave Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Hi Marc, Although atop currently builds successfully on armhf and armel, it is broken at runtime because it tries to use a time_t in a format string which

Bug#1069800: marked as done (FTBFS: test failures in buildd environment)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 20:45:04 + with message-id and subject line Bug#1069800: fixed in cloud-init 24.1.4-2 has caused the Debian Bug report #1069800, regarding FTBFS: test failures in buildd environment to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1069842 4.4.0-1 Bug #1069842 [r-base] rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory Marked as found in versions r-base/4.4.0-1. > affects 1069842 + src:rjava Bug #1069842 [r-base] rjava: FTBFS: /usr/bin/ld:

Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory

2024-04-25 Thread Santiago Vila
found 1069842 4.4.0-1 affects 1069842 + src:rjava thanks Thanks for the quick reply! [ I'm adding the affects so that the bug is shown on the web page for src:rjava. This helps to avoid duplicates, as there are more people reporting FTBFS bugs ] Thanks.

Bug#1069844: More debug info

2024-04-25 Thread Alex Bennée
Alex Bennée writes: > Julian Andres Klode writes: > >> On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote: >>> >>> Continuing to debug on QEMU it seems there is an incompatibility with >>> the images and the peloader (which overrides the normal efi loader): >>> > >> In the error

Bug#1069334: marked as done (Not installable due to hardcoded pre-t64 library deps)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 19:49:29 + with message-id and subject line Bug#1069334: fixed in nautilus-wipe 0.4.alpha2-0.2 has caused the Debian Bug report #1069334, regarding Not installable due to hardcoded pre-t64 library deps to be marked as done. This means that you claim that

Bug#1069844: More debug info

2024-04-25 Thread Alex Bennée
Julian Andres Klode writes: > On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote: >> >> Continuing to debug on QEMU it seems there is an incompatibility with >> the images and the peloader (which overrides the normal efi loader): >> >> Thread 1 hit Breakpoint 3.2,

Bug#1067623: FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}

2024-04-25 Thread Andreas Rönnquist
Control: tags -1 + pending I have NMU'd this package fixing this bug with Steve's patch - Thanks Steve! I have uploaded this to DELAYED/2 - please let me know if I should delay it further. Debdiff attached. best /Andreas Rönnquist gus...@debian.org acm_time_t64.debdiff Description: Binary

Processed: Re: FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #1067623 [src:acm] FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’} Added tag(s) pending. -- 1067623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067623 Debian

Processed: [bts-link] source package src:strace

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:strace > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:freebayes

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:freebayes > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:libapache2-mod-auth-cas

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:libapache2-mod-auth-cas > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Processed: [bts-link] source package nomacs

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package nomacs > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

Processed: [bts-link] source package src:azure-cli

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:azure-cli > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:pybdsf

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:pybdsf > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:jupyter-client

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:jupyter-client > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Processed: [bts-link] source package src:procdump

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:procdump > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package hyperspy

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package hyperspy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:python-bottle

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:python-bottle > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Processed: [bts-link] source package src:tracker

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:tracker > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#1069841: python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab'

2024-04-25 Thread Benjamin Drung
On Thu, 2024-04-25 at 18:13 +0100, Simon McVittie wrote: > Control: retitle -1 python-icalendar: FTBFS with tzdata 2024a: > UnknownTimeZoneError: 'America/Godthab' > > On Thu, 25 Apr 2024 at 18:27:15 +0200, Santiago Vila wrote: > > E pytz.exceptions.UnknownTimeZoneError:

Processed (with 2 errors): Re: ncl: FTBFS (ld: cannot find -lNGras: No such file or directory)

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #1069845 [src:ncl] ncl: FTBFS (ld: cannot find -lNGras: No such file or directory) Added tag(s) upstream. > user debian-...@lists.debian.org Unknown command or malformed arguments to command. > usertag -1 hdf-4.3 Unknown command or malformed

Bug#1069845: ncl: FTBFS (ld: cannot find -lNGras: No such file or directory)

2024-04-25 Thread Sebastiaan Couwenberg
Control: tags -1 upstream Control: user debian-...@lists.debian.org Control: usertag -1 hdf-4.3 On 4/25/24 7:35 PM, Bas Couwenberg wrote: The buildlogs shows many instances of these: /usr/bin/ld: cannot find -lNGctrans: No such file or directory /usr/bin/ld: cannot find -lNGras: No such

Bug#1069844: More debug info

2024-04-25 Thread Julian Andres Klode
On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote: > > Continuing to debug on QEMU it seems there is an incompatibility with > the images and the peloader (which overrides the normal efi loader): > > Thread 1 hit Breakpoint 3.2, grub_load_normal_mode () at >

Bug#1069844: More debug info

2024-04-25 Thread Alex Bennée
Continuing to debug on QEMU it seems there is an incompatibility with the images and the peloader (which overrides the normal efi loader): Thread 1 hit Breakpoint 3.2, grub_load_normal_mode () at ../../../grub-core/kern/main.c:241 241 in

Processed: found 1069630 in 2.0.0-1, notfound 1069800 in 21.1.4-1, found 1069800 in 24.1.4-1, tagging 1069790

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1069630 2.0.0-1 Bug #1069630 [libcupsfilters2-dev] libcupsfilters-dev and libcupsfilters2-dev have an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libcupsfilters.a, /usr/lib/x86_64-linux-gnu/libcupsfilters.so and

Processed: Re: Bug#1069841: python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab'

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: > 'America/Godthab' Bug #1069841 [src:python-icalendar] python-icalendar: FTBFS: pytz.exceptions.UnknownTimeZoneError: 'America/Godthab' Changed Bug title to 'python-icalendar: FTBFS with

Bug#1069841: python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab'

2024-04-25 Thread Simon McVittie
Control: retitle -1 python-icalendar: FTBFS with tzdata 2024a: UnknownTimeZoneError: 'America/Godthab' On Thu, 25 Apr 2024 at 18:27:15 +0200, Santiago Vila wrote: > E pytz.exceptions.UnknownTimeZoneError: 'America/Godthab' This was presumably triggered by this change in tzdata

Processed: Re: Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > found -1 libreoffice/4:24.2.3~rc1-3 Bug #1069835 {Done: Rene Engelhard } [libreoffice-kf5] libreoffice-kf5: documents may get lost on SMB shares Marked as found in versions libreoffice/4:24.2.3~rc1-3 and reopened. > notfixed -1 libreoffice/4:24.2.2-1 Bug #1069835

Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares

2024-04-25 Thread Andreas B. Mundt
Control: found -1 libreoffice/4:24.2.3~rc1-3 Control: notfixed -1 libreoffice/4:24.2.2-1 Control: reopen -1 Control: tags -1 - moreinfo Hi again, On Thu, Apr 25, 2024 at 06:43:17PM +0200, Rene Engelhard wrote: > Am 25.04.24 um 18:37 schrieb Andreas B. Mundt: > > On Thu, Apr 25, 2024 at

Bug#1069804: marked as done (rust-mio-0.6 accesses network resources during the build)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 17:04:33 + with message-id and subject line Bug#1069804: fixed in rust-mio-0.6 0.6.23-4 has caused the Debian Bug report #1069804, regarding rust-mio-0.6 accesses network resources during the build to be marked as done. This means that you claim that the

Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory

2024-04-25 Thread Dirk Eddelbuettel
reassign 1069842 r-base thanks On 25 April 2024 at 18:27, Santiago Vila wrote: | Package: src:rjava | Version: 1.0-11-1 | Severity: serious | Tags: ftbfs | | Dear maintainer: | | During a rebuild of all packages in unstable, your package failed to build: Thanks for this. It is caused by the

Processed: Re: Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1069842 r-base Bug #1069842 [src:rjava] rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory Bug reassigned from package 'src:rjava' to 'r-base'. No longer marked as found in versions rjava/1.0-11-1. Ignoring

Processed: Re: Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > found -1 libreoffice/4:24.2.0-1 Bug #1069835 {Done: Rene Engelhard } [libreoffice-kf5] libreoffice-kf5: documents may get lost on SMB shares Marked as found in versions libreoffice/4:24.2.0-1. -- 1069835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069835

Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares

2024-04-25 Thread Andreas B. Mundt
Control: found -1 libreoffice/4:24.2.0-1 Hi Rene, thanks for your quick reply and sorry for not providing detailed version information! On Thu, Apr 25, 2024 at 05:43:29PM +0200, Rene Engelhard wrote: > > Am 25.04.24 um 17:03 schrieb Andreas B. Mundt: > > For now, we traced the issue back to

Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares

2024-04-25 Thread Rene Engelhard
Hi, Am 25.04.24 um 18:37 schrieb Andreas B. Mundt: On Thu, Apr 25, 2024 at 05:43:29PM +0200, Rene Engelhard wrote: Am 25.04.24 um 17:03 schrieb Andreas B. Mundt: For now, we traced the issue back to libreoffice-kf5. If this package is removed, neither the document disappears on closing

Bug#1069844: grub-efi-arm64: grub fails to load Xen hypervisor on arm64 EFI systems (AVA & QEMU)

2024-04-25 Thread Alex Bennée
Package: grub-efi-arm64 Version: 2.12-2~deb13u1 Severity: serious Attempting to boot Xen on an arm64 EFI system fails. Further attempts to select another boot entry fails and the system needs to be rebooted before you can load the kernel without Xen. This is likely due to boot services having

Bug#1069843: zarr: FTBFS: failing tests

2024-04-25 Thread Santiago Vila
Package: src:zarr Version: 2.17.2+ds-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary

Bug#1069841: python-icalendar: FTBFS: pytz.exceptions.UnknownTimeZoneError: 'America/Godthab'

2024-04-25 Thread Santiago Vila
Package: src:python-icalendar Version: 5.0.11-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary

Bug#1069842: rjava: FTBFS: /usr/bin/ld: cannot find -ldeflate: No such file or directory

2024-04-25 Thread Santiago Vila
Package: src:rjava Version: 1.0-11-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --buildsystem R

Bug#1069838: khard: FTBFS: ERROR: test_query (unittest.loader._FailedTest.test_query)

2024-04-25 Thread Santiago Vila
Package: src:khard Version: 0.19.1-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --with python3

Bug#1069839: libcommons-fileupload-java: FTBFS: failing tests

2024-04-25 Thread Santiago Vila
Package: src:libcommons-fileupload-java Version: 1.5-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh

Bug#1069840: maven-dependency-analyzer: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile (default-testCompile) on project maven-dependency-analyz

2024-04-25 Thread Santiago Vila
Package: src:maven-dependency-analyzer Version: 1.13.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh

Processed: Re: antlr4-maven-plugin: please provide debian-versioned maven coordinates

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1065660 serious Bug #1065660 [antlr4-maven-plugin] antlr4-maven-plugin: please provide debian-versioned maven coordinates Severity set to 'serious' from 'normal' > tags 1065660 + ftbfs Bug #1065660 [antlr4-maven-plugin]

Processed: Pending

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #1024889 [src:pplacer] pplacer: build-depends on dropped package Added tag(s) pending. > block -1 by 1064596 Bug #1024889 [src:pplacer] pplacer: build-depends on dropped package 1024889 was not blocked by any bugs. 1024889 was not blocking any

Bug#1024889: Pending

2024-04-25 Thread Andreas Tille
Control: tags -1 pending Control: block -1 by 1064596 thanks Pplacer needs to be build against the old version of MCL which is featuring some OCAML patch. This old version was just uploaded to new. Kind regards Andreas. -- https://fam-tille.de

Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares

2024-04-25 Thread Rene Engelhard
Hi, Am 25.04.24 um 17:03 schrieb Andreas B. Mundt: For now, we traced the issue back to libreoffice-kf5. If this package is removed, neither the document disappears on closing libreoffice nor the popup is shown when 'nobrl' is removed from the mount options. Which doesn't do IO itself

Processed: your mail

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1069835 4:7.4.7-1 Bug #1069835 {Done: Rene Engelhard } [libreoffice-kf5] libreoffice-kf5: documents may get lost on SMB shares Marked as found in versions libreoffice/4:7.4.7-1. > End of message, stopping processing here. Please contact

Processed: Re: Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1069835 4:24.2.2-1 Bug #1069835 [libreoffice-kf5] libreoffice-kf5: documents may get lost on SMB shares Marked as fixed in versions libreoffice/4:24.2.2-1. Bug #1069835 [libreoffice-kf5] libreoffice-kf5: documents may get lost on SMB

Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares

2024-04-25 Thread Rene Engelhard
close 1069835 4:24.2.2-1 forwarded 1069835 https://bugs.documentfoundation.org/show_bug.cgi?id=55004 tag 1069835 + moreinfo thanks Am 25.04.24 um 17:03 schrieb Andreas B. Mundt: Package: libreoffice-kf5 Version? Severity: grave Come on... Not downgrading just yet, but I don't believe

Bug#1066618: marked as done (libt3key: FTBFS: .config.c:8:13: error: implicit declaration of function ‘setupterm’; did you mean ‘set_term’? [-Werror=implicit-function-declaration])

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 15:21:03 + with message-id and subject line Bug#1066618: fixed in libt3key 0.2.10-1.1 has caused the Debian Bug report #1066618, regarding libt3key: FTBFS: .config.c:8:13: error: implicit declaration of function ‘setupterm’; did you mean ‘set_term’?

Bug#1069835: libreoffice-kf5: documents may get lost on SMB shares

2024-04-25 Thread Andreas B. Mundt
Package: libreoffice-kf5 Severity: grave Dear Rene, everybody, we run Debian bookworm KDE plasma clients with home directories mounted from an SMB share. From time to time, users reported that libreoffice documents have disappeared completely when closing libreoffice. We were now able to

Bug#950372: marked as done (Is radare2 suitable for stable Debian releases?)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 14:52:15 + with message-id and subject line Bug#950372: fixed in radare2 5.9.0+dfsg-1 has caused the Debian Bug report #950372, regarding Is radare2 suitable for stable Debian releases? to be marked as done. This means that you claim that the problem has

Bug#1014478: marked as done (radare2: CVE-2022-1714 CVE-2022-1809 CVE-2022-1899 CVE-2022-0849 CVE-2022-1052 CVE-2022-1061 CVE-2022-1207 CVE-2022-1237 CVE-2022-1238 CVE-2022-1240 CVE-2022-1244 CVE-2022

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 14:52:15 + with message-id and subject line Bug#1014478: fixed in radare2 5.9.0+dfsg-1 has caused the Debian Bug report #1014478, regarding radare2: CVE-2022-1714 CVE-2022-1809 CVE-2022-1899 CVE-2022-0849 CVE-2022-1052 CVE-2022-1061 CVE-2022-1207

Bug#1069834: sccache FTBFS with itoa != 0.3.4

2024-04-25 Thread Adrian Bunk
Source: sccache Version: 0.8.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=sccache=0.8.0-1 ... test test_rust_cargo_cmd_readonly_preemtive_block ... FAILED failures: test_rust_cargo_cmd_readonly_preemtive_block stdout Error: Unexpected failure.

Processed: severity of 1067047 is wishlist

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1067047 wishlist Bug #1067047 [src:gnucash] Buildng the package removes debian/.gitlab-ci.yml Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1067047:

Processed: Bug#1069551 marked as pending in numpy

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1069551 [src:numpy] numpy: FTBFS on armel: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13 Added tag(s) pending. -- 1069551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069551 Debian Bug

Processed: Re: Bug#1067047: Buildng the package removes debian/.gitlab-ci.yml

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1067047 {Done: Dmitry Smirnov } [src:gnucash] Buildng the package removes debian/.gitlab-ci.yml Bug reopened Ignoring request to alter fixed versions of bug #1067047 to the same values previously set -- 1067047:

Bug#1069551: marked as pending in numpy

2024-04-25 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1069551 in numpy 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#1067047: Buildng the package removes debian/.gitlab-ci.yml

2024-04-25 Thread Andrey Rakhmatullin
Control: reopen -1 On Fri, Apr 26, 2024 at 12:12:06AM +1000, Dmitry Smirnov wrote: > > Source: gnucash > > Version: 1:5.5-1.1 > > Severity: serious > > > > Simply build the package from source produces a source package that doesn't > > contain debian/.gitlab-ci.yml in debian.tar, one needs to

Bug#1067047: marked as done (Buildng the package removes debian/.gitlab-ci.yml)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Fri, 26 Apr 2024 00:12:06 +1000 with message-id <3341693.tJ1Z21uVQO@deblab> and subject line Re: Bug#1067047: Buildng the package removes debian/.gitlab-ci.yml has caused the Debian Bug report #1067047, regarding Buildng the package removes debian/.gitlab-ci.yml to be marked as

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

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 13:34:54 + with message-id and subject line Bug#1066745: fixed in pytest-mpl 0.17.0-1 has caused the Debian Bug report #1066745, regarding pytest-mpl: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit

Bug#1063963: marked as done (pytest-mpl: autopkgtest regression with pytest 8)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 13:34:54 + with message-id and subject line Bug#1063963: fixed in pytest-mpl 0.17.0-1 has caused the Debian Bug report #1063963, regarding pytest-mpl: autopkgtest regression with pytest 8 to be marked as done. This means that you claim that the problem has

Bug#1069688: marked as done (libsequoia-octopus-librnp has an undeclared file conflict on /usr/lib/thunderbird/librnp.so)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 13:19:29 + with message-id and subject line octopus file conflict resolved has caused the Debian Bug report #1069688, regarding libsequoia-octopus-librnp has an undeclared file conflict on /usr/lib/thunderbird/librnp.so to be marked as done. This means

Processed: Re: Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 ruby-curb: test regression with curl 8.7.1: client read function > EOF fail, only only 4/5 of needed bytes read Bug #1069258 [src:ruby-curb] ruby-curb: FTBFS: 178 tests, 699 assertions, 0 failures, 7 errors, 0 pendings, 0 omissions, 0 notifications

Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read

2024-04-25 Thread Simon McVittie
Control: retitle -1 ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read User: debian...@lists.debian.org Usertags: breaks needs-update On Thu, 18 Apr 2024 at 22:42:11 +0200, Sebastian Ramacher wrote: > Error:

Bug#1069830: libccrtp-doc: missing Breaks+Replaces: libccrtp-dev (<< 2.0.9-3)

2024-04-25 Thread Andreas Beckmann
Package: libccrtp-doc Version: 2.0.9-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to

Processed: Re: Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1065626 [aptitude,libgtk2.0-0t64] libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common Severity set to 'important' from 'serious' -- 1065626:

Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-04-25 Thread Julian Andres Klode
Control: severity -1 important Control: user release.debian@packages.debian.org Control: usertags -1 time-t-downgrade On Thu, Mar 07, 2024 at 04:10:17PM +0100, Vincent Lefevre wrote: > Package: libgtk2.0-0t64 > Version: 2.24.33-4 > Severity: serious > > During an upgrade with aptitude: > >

Bug#1069793: wrong package name mnt-reform-setup-wizard -- should be reform-setup-wizard

2024-04-25 Thread Andreas Beckmann
Followup-For: Bug #1069793 reform-setup-wizard misses Breaks+Replaces: mnt-reform-setup-wizard (<< 0.1.0-3) for the package rename. Andreas

Bug#1069826: stravalib: FTBFS: tests fail with ModuleNotFoundError: No module named 'pytz'

2024-04-25 Thread Andreas Beckmann
Source: stravalib Version: 1.3.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source stravalib recently started to FTBFS, probably due to a change in on eof its (transitive) build-depends: ERRORS

Bug#1065425: marked as done (Does not upgrade from libpam0t64)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 13:49:54 +0200 with message-id and subject line Re: Bug#1065425: Does not upgrade from libpam0t64 has caused the Debian Bug report #1065425, regarding Does not upgrade from libpam0t64 to be marked as done. This means that you claim that the problem has been

Processed: netavark: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # also happens on amd64 > retitle 1069350 netavark: FTBFS: dh_auto_test: error: > /usr/share/cargo/bin/cargo build returned exit code 101 Bug #1069350 [src:netavark] netavark: FTBFS on arm64: dh_auto_test: error: /usr/share/cargo/bin/cargo

Processed: tag

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1068730 + ftbfs Bug #1068730 {Done: Luca Boccassi } [src:systemd] Fails to build from source since removal of liblz4-tool Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068730:

Processed: tag

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1068389 + ftbfs Bug #1068389 [src:pcp] src:pcp: unsatisfied build dependency in testing: python3-bpfcc Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068389:

Processed: retitle 1069821 to satpy: FTBFS: tests failed

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1069821 satpy: FTBFS: tests failed Bug #1069821 [src:satpy] FTBFS: tests failed Changed Bug title to 'satpy: FTBFS: tests failed' from 'FTBFS: tests failed'. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#999922: marked as done (xneur: depends on obsolete pcre3 library)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 10:54:43 + with message-id and subject line Bug#22: fixed in xneur 0.20.0-3.1 has caused the Debian Bug report #22, regarding xneur: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt

Bug#1037902: marked as done (xneur: ftbfs with GCC-13)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 10:54:43 + with message-id and subject line Bug#1037902: fixed in xneur 0.20.0-3.1 has caused the Debian Bug report #1037902, regarding xneur: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1069030: marked as done (subread FTBFS on 32bit architectures: -Werror=implicit-function-declaration)

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 10:54:32 + with message-id and subject line Bug#1069030: fixed in subread 2.0.6+dfsg-3 has caused the Debian Bug report #1069030, regarding subread FTBFS on 32bit architectures: -Werror=implicit-function-declaration to be marked as done. This means that

Bug#1069821: FTBFS: tests failed

2024-04-25 Thread Andrey Rakhmatullin
Source: satpy Version: 0.47.0-2 Severity: serious Tags: ftbfs ERRORS ___ ERROR collecting satpy/tests/reader_tests/test_viirs_edr_active_fires.py ___ satpy/tests/reader_tests/test_viirs_edr_active_fires.py:30: in

Bug#1069818: FTBFS: tests failed

2024-04-25 Thread Andrey Rakhmatullin
Source: toolz Version: 0.12.0-2 Severity: serious Tags: ftbfs === FAILURES === test_inspect_wrapped_property _ def test_inspect_wrapped_property(): class Wrapped(object):

Bug#1069819: FTBFS: tests failed

2024-04-25 Thread Andrey Rakhmatullin
Source: python-tooz Version: 4.2.0-2 Severity: serious Tags: ftbfs == FAIL: tooz.tests.test_mysql.TestMySQLDriver.test_parsing_blocking_settings tooz.tests.test_mysql.TestMySQLDriver.test_parsing_blocking_settings

Bug#1069816: Autopkgtests fail

2024-04-25 Thread Andrey Rakhmatullin
Package: python3-argcomplete Version: 3.1.4-1 Severity: serious https://ci.debian.net/packages/p/python-argcomplete/unstable/amd64/45886560/ 102s == 102s ERROR: test_repl_parse_after_complete

Bug#1069815: wesnoth-1.8-server: new package installs systemd unit in aliased location

2024-04-25 Thread Helmut Grohne
Package: wesnoth-1.18-server Version: 1:1.17.26-1 Severity: serious Justification: do not introduce aliased files into Debian Hi, I noticed that wesnoth-1.18-server is a new package and installs a file below /lib, which is an aliased location that we try to empty to complete the /usr-move

Processed: Bug#1069030 marked as pending in subread

2024-04-25 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1069030 [src:subread] subread FTBFS on 32bit architectures: -Werror=implicit-function-declaration Added tag(s) pending. -- 1069030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069030 Debian Bug Tracking System Contact

Bug#1069030: marked as pending in subread

2024-04-25 Thread Michael R. Crusoe
Control: tag -1 pending Hello, Bug #1069030 in subread 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#1069814: golang-github-aydinnyunus-blockchain: FTBFS: Tries network access during build

2024-04-25 Thread Santiago Vila
Package: src:golang-github-aydinnyunus-blockchain Version: 0.0~git20220623.647ebea-1 Severity: serious Tags: ftbfs Dear maintainer: This package tries network access during build: = TESTING ADDRESSES =

Bug#1053334: galera-4: FTBFS because of expired certificates

2024-04-25 Thread Santiago Vila
El 25/4/24 a las 7:15, Otto Kekäläinen escribió: Bullseye oldstable update request filed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069802 You can +1 it if you want to show support. Thanks a lot! We don't +1 because this is not twitter/facebook :-) but I have just made a comment to

Bug#1064311: rdkit: NMU diff for 64-bit time_t transition

2024-04-25 Thread Andrius Merkys
Hi Chris, On 2024-04-25 00:57, Chris Hofstaedtler wrote: t64 is already in unstable and making its way to testing. So you are a bit late with getting rdkit fixed for t64. An upload with t64 binaries is required as soon as possible. Given the packages have to go to binary-NEW, you must upload

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

2024-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2024 08:43:32 + with message-id and subject line Bug#1066753: fixed in python-django-extensions 3.2.3-2 has caused the Debian Bug report #1066753, regarding python-django-extensions: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p

Bug#1069762: pdns-recursor: CVE-2024-25583 - 4.8.8 for stable

2024-04-25 Thread Chris Hofstaedtler
* Moritz Muehlenhoff [240425 08:44]: > On Thu, Apr 25, 2024 at 08:37:14AM +0200, Chris Hofstaedtler wrote: > > Hi Moritz, > > > > could we once again use the upstream release for stable? > > debdiff 4.8.7-1 -> 4.8.8-1 is attached. > > Ack. Following the 4.8 releases has served us well. debdiff

  1   2   >