Bug#1067957: marked as done (FTBFS: error: call of overloaded ‘__gmp_expr(__time64_t&)’ is ambiguous)

2024-04-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Apr 2024 11:07:36 + with message-id and subject line Bug#1067957: fixed in maude 3.4-1 has caused the Debian Bug report #1067957, regarding FTBFS: error: call of overloaded ‘__gmp_expr(__time64_t&)’ is ambiguous to be marked as done. This means that you claim that

Processed: more tags

2024-04-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # This package entered testing today, > # which does not seem ok, as it ftbfs in trixie and sid > # Maybe this is the result of me adding the bookworm tag > # So I'm adding now the remaining tags just in case > tags 1057544 + trixie sid Bug #10575

Bug#1068562: crmsh: autopkgtest regression: unsupported operand type(s) for -: 'NoneType' and 'int'

2024-04-07 Thread Paul Gevers
Source: crmsh Version: 4.6.0-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it started to fail in testing several days ago. Can you please investigate the situation and fix it? I copied some of the

Bug#1068038: FTBFS: error: ‘struct input_event’ has no member named ‘time’

2024-04-07 Thread Dmitry Shachnev
Control: tags -1 + pending Hi, On Sat, Mar 30, 2024 at 02:10:56AM +0500, Andrey Rakhmatullin wrote: > Source: flightgear > Version: 1:2020.3.18+dfsg-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=flightgear&arch=armhf&ver=1%3A2020.3.18%2Bdfsg-1%2Bb2&stamp=

Processed: Re: Bug#1068038: FTBFS: error: ‘struct input_event’ has no member named ‘time’

2024-04-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #1068038 [src:flightgear] FTBFS: error: ‘struct input_event’ has no member named ‘time’ Added tag(s) pending. -- 1068038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068038 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1066709: marked as done (fastdnaml: FTBFS: fastDNAml.h:228:28: error: implicit declaration of function ‘free’ [-Werror=implicit-function-declaration])

2024-04-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Apr 2024 09:34:04 + with message-id and subject line Bug#1066709: fixed in fastdnaml 1.2.2-16 has caused the Debian Bug report #1066709, regarding fastdnaml: FTBFS: fastDNAml.h:228:28: error: implicit declaration of function ‘free’ [-Werror=implicit-function-declara

Bug#1060926: simgear: FTBFS: Compositor.hxx:137:34: error: field ‘_uniforms’ has incomplete type ‘simgear::compositor::Compositor::BuiltinUniforms’ {aka ‘std::array, 14>’}

2024-04-07 Thread Dmitry Shachnev
Control: tags -1 + pending Hi, On Tue, Jan 16, 2024 at 08:36:13PM +0100, Lucas Nussbaum wrote: > Source: simgear > Version: 1:2020.3.18+dfsg-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240115 ftbfs-trixie > > Hi, > > During a

Processed: Re: Bug#1060926: simgear: FTBFS: Compositor.hxx:137:34: error: field ‘_uniforms’ has incomplete type ‘simgear::compositor::Compositor::BuiltinUniforms’ {aka ‘std::array

2024-04-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #1060926 [src:simgear] simgear: FTBFS: Compositor.hxx:137:34: error: field ‘_uniforms’ has incomplete type ‘simgear::compositor::Compositor::BuiltinUniforms’ {aka ‘std::array, 14>’} Added tag(s) pending. -- 1060926: https://bugs.debian.org/

Bug#1068473: icinga2: crashes on startup on ppc64el

2024-04-07 Thread Aurelien Jarno
Hi, On 2024-04-06 14:17, Sebastiaan Couwenberg wrote: > 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 icing

Bug#1067916: FTBFS: tests failed

2024-04-07 Thread Andrey Rakhmatullin
On Sat, Apr 06, 2024 at 10:31:52PM +, tony mancill wrote: > 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&arch=armhf&ver=1.0.

Bug#1066065: marked as done (libvformat: FTBFS: vf_reader.c:178:33: error: implicit declaration of function ‘read’; did you mean ‘fread’? [-Werror=implicit-function-declaration])

2024-04-07 Thread Debian Bug Tracking System
Your message dated Sun, 07 Apr 2024 08:37:33 + with message-id and subject line Bug#1066065: fixed in libvformat 1.13-12.2 has caused the Debian Bug report #1066065, regarding libvformat: FTBFS: vf_reader.c:178:33: error: implicit declaration of function ‘read’; did you mean ‘fread’? [-Werror

Bug#1068540: chromium: depends on pre-t64 library

2024-04-07 Thread Sebastian Ramacher
Source: chromium Version: 123.0.6312.105-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org chromium has a hard-coded dependency on libgtk-3-0 which changed the package name as part of the time_t transition. Please update the dependency accordingly - or even better - derive the dependency from

Bug#1068538: ruby-ffi-libarchive: arch:all package depends on pre-t64 library

2024-04-07 Thread Sebastian Ramacher
Source: ruby-ffi-libarchive Version: 1.0.1-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org ruby-ffi-libarchive builds an Architecture: all package that depends on a library involved in the time_t transition (libarchive13). Please ensure that the package wroks with the library using the new

Bug#1068537: ruby-ethon: arch:all package depends on pre-t64 library

2024-04-07 Thread Sebastian Ramacher
Source: ruby-ethon Version: 0.16.0-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org ruby-ethon builds an Architecture: all package that depends on a library that is involved in the t64 package (libcurl4). Please make sure that the packages works with the package using the new 64 time_t ABI a

Bug#1066308: Fwd: 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])

2024-04-07 Thread Mike Gabriel
Control: notfixed -1 python-whey/0.0.26-1 Hi Josenilson, I think you closed the wrong bug with upload of python-why 0.0.26-1. Please amend your changelog post-upload and close the real bug you wanted to fix. Regarding #1066308: It was already closed, so please don't reopen it. Mike

Processed: Fwd: 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])

2024-04-07 Thread Debian Bug Tracking System
Processing control commands: > notfixed -1 python-whey/0.0.26-1 Bug #1066308 {Done: Josenilson Ferreira da Silva } [src:click] click: FTBFS: clickpreload.c:422:16: error: implicit declaration of function ‘__fxstat’; did you mean ‘__xstat’? [-Werror=implicit-function-declaration] No longer marke

Processed: Re: libvformat: FTBFS: vf_reader.c:178:33: error: implicit declaration of function ‘read’; did you mean ‘fread’? [-Werror=implicit-function-declaration]

2024-04-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1066065 [src:libvformat] libvformat: FTBFS: vf_reader.c:178:33: error: implicit declaration of function ‘read’; did you mean ‘fread’? [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1066065: https://bugs.debian.org/cgi-bin/bugrep

Bug#1066065: libvformat: FTBFS: vf_reader.c:178:33: error: implicit declaration of function ‘read’; did you mean ‘fread’? [-Werror=implicit-function-declaration]

2024-04-07 Thread Steve Langasek
Package: libvformat Version: 1.13-12.1 Followup-For: Bug #1066065 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Please find the fix for this attached. As this is fallout from the time_t transition, I am uploading this as a 0-day NMU. Thanks

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

2024-04-07 Thread Sean Whitton
Hello, On Sat 06 Apr 2024 at 03:24pm +02, Salvatore Bonaccorso wrote: > As it is a regression caused by libssl3 3.0.11 based to 3.0.13, why is > it reassigned to yapet? (the regression is as well present in > unstable). I was just thinking that it may be a flaw in how YAPET calls into openssl, a

<    1   2