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

List:       debian-devel
Subject:    Re: [Debian-iot-maintainers] Bug#1062257: libcoap3: NMU diff for 64-bit time_t transition
From:       Sune Vuorela <nospam () vuorela ! dk>
Date:       2024-02-01 8:18:35
Message-ID: upfk4r$10ib$1 () ciao ! gmane ! io
[Download RAW message or body]

On 2024-02-01, Carsten Schoenert <c.schoenert@t-online.de> wrote:
> What is the rationale behind rising a bug report at 9:51pm my time and 
> firing a *direct* NMU upload just 11min later (according to the time 
> stamps from the emails)?
> I as the uploader for libcoap have no chance to do any action on this 
> bug report! This behavior I'm not expecting within Debian.
> What are the plans now with forwarding the underlying issue to upstream?
> Upstream is very responsive and I've good contacts to the upstream 
> authors, but who is doing this work now?

I'm mostly a bystander here. But there is no underlying issue to forward
to upstream. Ex. The debian toolchain has been changed on most 32bit
architectures to produce different code if time-related types are
involved.

This involves doing a giant library transition involving a 4 digit
number of source packages, and it will while the transition is ongoing,
be a *nightmare* of crashes for anyone with a machine on one of the
involved 32bit architectures, so it need to happen in a very short
timeframe.

We should just be happy that there is at least 4 people working in
shifts around the clock trying to get this done in less than a week of
calendar time.

/Sune

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