Bug#1062545: Processed: Re: falcosecurity-libs: NMU diff for 64-bit time_t transition

2024-02-17 Thread Steve Langasek
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; no time64 changes
> - 0.14.1-5   I added the time64 stuff to my unrelated bug fix

> So what should we do to get both the bug fix in -4 and the time64 stuff?

You could add DEB_BUILD_MAINT_OPTIONS=abi=+time64 in debian/rules to do an
early opt-in to the new ABI?

Or you could upload to unstable to back out the changes from the
experimental NMU, and we will pick it up for NMU ourselves after the
toolchain changes.

-- 
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


Bug#1062545: Processed: Re: falcosecurity-libs: NMU diff for 64-bit time_t transition

2024-02-03 Thread Dima Kogan
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 unrelated bug fix

So what should we do to get both the bug fix in -4 and the time64 stuff?