Hi Gioele On Mon, Feb 06, 2023 at 12:31:07PM +0100, Gioele Barabucci wrote: > On 06/02/23 12:14, Bastian Blank wrote: > > Can you please show the error you got from the upload? > A -2 version will be REJECTed by mentors.d.n if version -1 is still being > processed:
I'm interested about the error you got while uploading to the main Debian archive, not mentors.d.n. You have reached out to the maintainers of the main archive. Otherwise you have to talk to the mentors people. > > Failed to connect to network resource. > > Url was: https://deb.debian.org/debian/pool/main/....orig.tar.gz Then explicitly add the file to you upload, by using "-sa" on the dpkg-buildpackage call. > The bigger picture is: packages are not part of the Debian build > infrastructure (buildd, piuparts, etc) for hours and this blocks many > development activities. They are. The buildd use incoming.d.o with accepted packages as additional source. Again, please show what you see. If this is again about mentors.d.n, talk to them and ask them to use incoming.d.o, because that's what it is for. > > Not sure what you mean. Can you please explain the workflow you are > > talking about? > The linked Michale Stapelberg's blog post explains it better than I can: But I wanted to hear from you, not Michael. And all he talked about being able to install packages, not workflow. > > It takes up to three hours. This process includes the overall updates > > to all the mirrors outside of Debian. > Yes, sometimes it can take a long time, but usually it finishes in 30 to 40 > minutes [1]. And that time is going to be even shorter if dinstall is run > more frequently and there are thus fewer packages waiting to be processed. Sorry, I don't have time to describe to you how this fits together. It takes 2 hours after what you see in this diagram to finish. Regards, Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, "Errand of Mercy", stardate 3198.9
