Your message dated Tue, 25 Mar 2025 21:23:53 +0100 with message-id <9922e5c1-c5f5-4312-bc6a-a70866c39...@debian.org> and subject line Fixed has caused the Debian Bug report #1089636, regarding libcap.so.2 lacks a _IO_stdin_used symbol to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1089636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libcap2 Version: 1:2.66-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, * What led up to the situation? I observed the failure for this package to buildd with powerpc architecture. * What exactly did you do (or not do) that was effective (or ineffective)? Attempted to sbuild it locally and saw the same result. * What was the outcome of this action? The package does not build successfully on this platform due to a segmentation fault in 'libcapsotest'. A debug session with gdb shows that the segmentation fault occurs when it attempts to call 'printf'. gdb shows the 'printf' symbol to be NULL. * What outcome did you expect instead? A successful package build including running the test suite. It works on ppc64 and ppc64el. -- System Information: Debian Release: trixie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: ppc64 Foreign Architectures: powerpc Kernel: Linux 6.12.3-powerpc64 (SMP w/2 CPU threads) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcap2 depends on: ii libc6 2.40-4 libcap2 recommends no packages. libcap2 suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1:2.75-4~exp1 The the cherry-picked patches seem to have fixed the FTBFS.
--- End Message ---
