Hello, Le 28/09/2025 à 16:13, Christian Kastner a écrit :
On 2025-09-28 00:22, Christian BAYLE wrote:Any objection if i start to do this for all package building in sid ?I forgot to mention: many of the packages in unstable also need transitions. All in all, I think the uploads to unstable must happen following some previously thought out strategy that minimizes disruption in unstable. With some (small) grace period between individual upload to allow for CI testing and pinpointing of root causes.
Would it help, if for exampleI start to upload built on unstable rocm-llvm (just tested that it builds) to apt.ai.debian.net ?
I think at least it would allow to test transitions, not waiting too much for NEW queue
That would also allow me to work a bit more on the meta rocm-* packagesI would also add the documentation build without creating NEW entries like I just did for miopen.
I would suggest to name branches apt-ai/unstable to identify that clearly in salsa
Regards Christian