[prev in list] [next in list] [prev in thread] [next in thread] 

List:       debian-devel
Subject:    Re: time_t and backports
From:       Andreas Metzler <ametzler () bebt ! de>
Date:       2024-02-26 14:51:26
Message-ID: Zdylbh9WAWCSs0j7 () argenau ! bebt ! de
[Download RAW message or body]

On 2024-02-26 John Goerzen <jgoerzen@complete.org> wrote:
> Hi folks,

> As a person that frequently uploads to bookworm-backports, I am
> wondering how we are handling the time_t transition there?

> The picture of synchronization with testing is a little complicated over
> there.  If you change the default build flags, you produce unexpected
> surprises over bookworm.  If you don't, the t64 packages aren't really
> t64.

Hello,

Imho you would need to undo the t64 rename for bpo instead of fiddling
with buildflags. We needed a transition because the whole distribution
needs to be built consistently with (or without) t64.  bookworm is built
without.

If you backported a libfoo3 which had replaced libfoo2t64 things will
get complicated, it would be necessary to upload as libfoo3t32 but the
tooling (${t32:Provides} does not exist.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

[prev in list] [next in list] [prev in thread] [next in thread]