I'm going to upload a change to add versioned build-dependency on the
version of dpkg-dev that enables the time64 abi for armhf and other
architectures. Patch attached, which will close this bug.
diff -Nru falcosecurity-libs-0.14.1/debian/changelog falcosecurity-libs-0.14.1/debian/changelog
---
On Sat, Feb 03, 2024 at 04:28:30PM -0800, Dima Kogan wrote:
> Oops. I was trying to save yall time, but I guess I didn't do it right.
> Please advise. Here's what happened, in order:
> - 0.14.1-3 was in the archive
> - 0.14.1-3.1 the NMU in experimental
> - 0.14.1-4 I fixed an unrelated bug;
Oops. I was trying to save yall time, but I guess I didn't do it right.
Please advise. Here's what happened, in order:
- 0.14.1-3 was in the archive
- 0.14.1-3.1 the NMU in experimental
- 0.14.1-4 I fixed an unrelated bug; no time64 changes
- 0.14.1-5 I added the time64 stuff to my
Control: reopen -1
Control: notfixed -1 falcosecurity-libs/0.14.1-5
This bug is not fixed. You have uploaded to unstable prematurely, before
the toolchain changes have landed, and therefore now have a binary package
with the right new name and the wrong ABI on armhf. Reopening the bug
report
Source: falcosecurity-libs
Version: 0.14.1-3
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
5 matches
Mail list logo
