On Mon, Feb 05, 2024 at 02:43:30PM -0300, Lucas Kanashiro wrote: > Source: pari > Version: 2.15.4-2 > Severity: serious > Tags: patch pending sid trixie > Justification: library ABI skew on upgrade > User: debian-...@lists.debian.org > Usertags: time-t > > NOTICE: these changes must not be uploaded to unstable yet! > > Dear maintainer, > > As part of the 64-bit time_t transition required to support 32-bit > architectures in 2038 and beyond > (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified > pari as a source package shipping runtime libraries whose ABI > either is affected by the change in size of time_t, or could not be > analyzed via abi-compliance-checker (and therefore to be on the safe > side we assume is affected). > > To ensure that inconsistent combinations of libraries with their > reverse-dependencies are never installed together, it is necessary to > have a library transition, which is most easily done by renaming the > runtime library package. > > Since turning on 64-bit time_t is being handled centrally through a change > to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is > important that libraries affected by this ABI change all be uploaded close > together in time. Therefore I have prepared a 0-day NMU for pari > which will initially be uploaded to experimental if possible, then to > unstable after packages have cleared binary NEW.
Have you actually checked that pari will really be build with the relevant flags ? If there is a new ABI, then one should take the opportunity to remove CFLAGS_i386 := -mpc64 There is no need for a lintian override, this is a well-known lintian bug... Cheers, Bill
