Sorry for top posting… It’s easier for me to wait as I don’t want use custom repository for my sbuild chroots. Hence the wait…
Ondrej -- Ondřej Surý <ond...@sury.org> (He/Him) > On 11. 1. 2023, at 21:01, Paul Gevers <elb...@debian.org> wrote: > > Hi Ondřej, > >> On 11-01-2023 20:42, Ondřej Surý wrote: >> Now, what should I do about: >> • Not built on buildd: arch amd64 binaries uploaded by ondrej >> • Not built on buildd: arch all binaries uploaded by ondrej, a new >> source-only upload is needed to allow migration >> Do I really have to reupload everything that had to pass NEW with no-change >> source-only upload? > > I have already NMU'd one of them (no change source only), because yes, our > infrastructure currently doesn't enable us to do binNMU that survives for > arch:all (we can do arch:any). > >>> yes, I will take care of those, I’m just uploading them in batches as the >>> dependencies require. > > Just in case you aren't aware, if the problem is that Build-Dependencies > aren't available yet (because of your previous batch), you don't need to wait > with uploading. The buildd's will know what to do and the package will stay > in "Builds Dependencies unavailable" until their B-D's are built and > available on the buildd. > > Paul
