XPost: linux.debian.bugs.dist
From: [email protected]

--XYYxCDx0wYlNPLnW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: dpkg-dev
Version: 1.21.22
Tags: patch
User: [email protected]
Usertags: origin-ubuntu mantic patch

Hi Guillem,

The discussion on debian-devel around 64-bit time_t has died down, so I
figure it's time to propose some patches to implement what's been discussed there.

I'm not sure whether you were persuaded that i386 should stay with the
current ABI, but anyway thought I would propose the patches and we could discuss further if necessary.

--
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/ [email protected] [email protected]

--XYYxCDx0wYlNPLnW
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-lfs-and-time64-are-no-longer-future-call-them-featur.patch"
Content-Transfer-Encoding: quoted-printable

From 5a861d19b1610ae82bf95e6c5142a3365436fbd2 Mon Sep 17 00:00:00 2001
From: Steve Langasek <[email protected]>
Date: Fri, 2 Jun 2023 14:30:20 +0000
Subject: [PATCH 1/3] lfs and time64 are no longer "future", call them
"feature" instead

Recognize future= for backwards compatibility.
---
scripts/Dpkg/Vendor/Debian.pm | 32 ++++++++++++++++++++++----------
scripts/t/Dpkg_BuildFlags.t | 2 +-
2 files changed, 23 insertions(+), 11 deletions(-)

diff --git a/script

XPost: linux.debian.bugs.dist
From: [email protected]

Hi.

libmrcal-dev does not use time_t. I'm seeing the abi-compliance-checker
failure here:

https://adrien.dcln.fr/misc/armhf-time_t/2024-02-01T09%3A53%3A00/logs/libmrcal-dev/base/log.txt

The cause is that the tool takes all the headers in /usr/include/mrcal
in an arbitrary order, and tries to #include them. That does not work
here. "mrcal-internal.h" should not be #included explicitly since it is
already #included by mrcal.h. Removing that header from the command in
the error log above makes the errors disappear.

Can we do that, and remove libmrcal-dev from this transition?

Thanks.

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hi *,

from my experience, adding -Werror=* flags causes breakage
because way too many configure scripts miss the appropriate
headers when probing for symbols, so this wouldn’t lead to
build failures but to changed feature sets or the programs
using older/fallback APIs (e.g. if probing openat() fails,
a program could unconditionally use open in an insecure way
as fallback, and the missing header would be there in the
site that actually uses it but autoconf generally misses
them).

In MirBSD, I’ve worked around this by appending a new flag -Werror-maybe-reset to CFLAGS and CXXFLAGS which has no
effect in GCC unless an extra environment variable is set,
in which case it does -Wno-error. Then, we set that env
during the configure call but not during make all/install.
This was achieved with a trivial local GCC patch.

I know we already add -Werror=format-security in many
cases, but that has less chance to break the configue
stage (even so I’d look sceptical at it).

bye,
//mirabilos
--
<hecker> cool ein Ada Lovelace Google-Doodle. aber zum 197. Geburtstag? Hätten die nicht noch 3 Jahre warten können? <mirabilos> bis dahin gibts google nicht mehr <hecker> ja, könnte man meinen. wahrscheinlich ist der angekündigte welt-
untergang aus dem maya-kalender die globale abschaltung von google ☺ und darum
müssen die die doodles vorher noch raushauen

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

I need to upload qpdf 11.9.0-1 to unstable. Since this is newer than 11.8.0-1.1~exp1 in experimental with the 64-bit time_t NMU, it will
cause that to disappear. In an effort to avoid that and keep things in
sync with the time_t transition, I have ported the NMU forward to
11.9.0-1 and will upload 11.9.0-2~exp1 with the time_t changes to
experimental right after I upload 11.9.0-1 to experimental. I am
hoping that I am not messing anything up with this. Please feel free
to adjust tags, do a separate NMU, or whatever is needed if I have
gotten things out of sync. In any case, I want to get 11.9.0-1
uploaded right away since I'd like it to sync to Ubuntu before the
24.04 feature freeze.

I'm sending this to the qpdf NMU debdiff bug and to the bug
referenced in that issue. Thanks.

--Jay Berkenbilt <[email protected]>, qpdf maintainer

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)