On 1/30/24 16:32, Lukas Märdian wrote:
Am 30.01.24 um 16:06 schrieb Sebastiaan Couwenberg:
On 1/30/24 15:57, Lukas Märdian wrote:
But please remember that this is meant to only hit experimental for
now, until the dpkg change lands in unstable.
So please don't upload it into unstable just yet.
gdal will need to be rebuilt once fyba moves to unstable, how will
these transitions be coordinated?
Regular transitions are staged in experimental, and once the Release
Team gives the go-ahead the package is uploaded to unstable after
which they schedule binNMUs.
Presumably there will be and overarching t64 transition to determine
the order in which packages need to be moved to unstable triggering
their respective transition which may include packages having their
own t64 transition pending in experimental.
Please see prior discussion in https://bugs.debian.org/1036884 for the
overall game plan.
That only mentions:
"
- sourceful NMUs of all the libraries will be reuploaded to unstable
(without binaries, so that they can be promoted to testing without
additional uploads).
"
Should we assume that to mean that everything will be uploaded at the
same time without taking inter-dependencies into account?
How will the t64 transitions be coordinated with the release team?
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
