Am Mon, Nov 21, 2022 at 04:49:43PM +0100 schrieb Sebastiaan Couwenberg:
This is really hard to do, thought. The new packages are needing those
packages from the transition. I actually injected two packages from
higher levels manually to be able to build one of the new packages. So
we really need to upload the start of the transition and I do not see
any sense in not documenting what we are doing without the transition
tracker.
You can rebuild the packages that are already in the archive and include
them in a local repo (e.g. managed with reprepro) and used by the chroot
where the rebuilds are performed. Use that to prepare the NEW uploads to
experimental, file the transition bugreport once all packages have passed
NEW, and move those to unstable once the transition is ACKed.
Well, probably everything is possible, but as I said the tracker comes
pretty handy to know the dependency relation. I really would like to
know what might be the real problem of the delay of the transition in
this specific case. Making me understand this problem would increase
the motivation to do something else than currently.