[Debian-iot-maintainers] Bug#1062257: Bug#1062257: libcoap3: NMU diff for 64-bit time_t transition

[Carsten Schoenert]

Hello Steve,

Am 31.01.24 um 21:59 schrieb Steve Langasek:
...
> Please find the patch for this NMU attached.
> 
> If you have any concerns about this patch, please reach out ASAP.
                                              ^^^^^^^^^^^^^^^^^^^^^^
>  Although
> this package will be uploaded to experimental immediately, there will be a
> period of several days before we begin uploads to unstable; so if information
> becomes available that your package should not be included in the transition,
> there is time for us to amend the planned uploads.

I'm a bit puzzled and disappointed.

libcopap3 isn't a package that is within the QA group nor is it bit rotting.

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 read the wiki page mentioned from the initial email again, also there 
I can't find a written plan that would explain me why the bug reporting 
together with a direct upload did happen. I see no plan there what will 
happen on what time.

Why no usual muss bug filling did happen so groups and maintainers would 
have some knowledge about these planned changes? BTW: I've no problem 
with the technical thing what is happen, but I need to deal also with 
other things too like a CVE fix for libcopa3.

-- 
Regards
Carsten