21.02.2024 12:03, Michael Hudson-Doyle wrote:
...
Yes, this is exactly what I had in mind, and already prepared the very same
changes
locally in the package git repository.
> I think the ideal way forward would be to upload to experimental asap to
check it builds and to let Helmut run dumat on it and then upload the
> unstable patch when the transition starts in earnest (planned for Friday
this week). The changes are pretty orthogonal to the differences
between what
> is unstable and experimental currently afaict.
Yes, that's what I was thinking about, too.
Still, I prefer to have 4.19 in unstable so far, not 4.20-rc.
That makes sense. We definitely do not want to have to coordinate with other transitions for this, so it sounds like we (or maybe you!) should just
patch the 4.19 in unstable and then you can migrate 4.20 when it suits you.
I just uploaded a new release to experimental. Here are the 2 commits:
https://salsa.debian.org/samba-team/samba/-/commits/debian/2%254.20.0_rc2+dfsg-3
which makes the t64 changes (note the X-Time64-Compat header, too).
Exactly the same changes applies on top of 4.19 currently in unstable.
I especially split it into two commits, one actual change and one
d/changelog, so the two can be applied separately, - since obviously
d/changelog changes wont apply cleanly and needs manual edit.
So we can either do an NMU of 4.19, based on your
nmu_samba_UNstable.debdiff,
or I can do a regular upload once the transition starts.
In some sense it would be easiest to just NMU samba like we are planning to
with everything else but I don't have a strong feeling about this.
Yeah, - can be done either way, that's why I'm making it easier.
Thanks,
/mjt
