On Tue, Jan 23, 2024 at 08:32:18AM +0400, Yadd wrote: > Control: tags -1 + moreinfo
> On 1/23/24 00:43, Steve Langasek wrote: > > Package: cyrus-common > > Version: 3.8.1-1 > > Severity: serious > > User: debian-...@lists.debian.org > > Usertags: time-t > > Dear maintainers, > > Analysis of the archive for the 64-bit time_t transition[0][1] identifies > > cyrus-common as an affected package, on the basis that the headers could not > > be compiled and analyzed out of the box using abi-compliance-checker[2], so > > we have to assume it's affected. > > However, cyrus-commons's shlibs file declares a dependency on a library > > package name that contains no ABI information: > according to > https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/logs/cyrus-dev/base/log.txt > , this issue looks like a false-positive: test failed because of C error, > not bad report > Am I right here ? We do not *know* that it's a false positive; we only know that we were unable to analyze the header files under a-c-c to prove that the ABI is not affected. Patches to the check-armhf-time_t script at https://salsa.debian.org/vorlon/armhf-time_t/-/blob/main/check-armhf-time_t?ref_type=heads to quirk this package and allow its headers to be analyzed, or changes to the source package to not ship uncompilable headers ("apt-file search lib/strarray.h" returns no results), would both be welcome. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
