On Thu, Oct 13, 2016 at 05:49:00PM +0200, Thomas Goirand wrote:
> On 10/13/2016 02:03 AM, Santiago Vila wrote:
> > No. If A "build-depends: B" and B "build-depends: C", that would be
> > three mirror pulses at most, and we have a mirror pulse every six
> > hours. Between the first and the third mirror pulse we would only have
> > 12 hours of "breakage", but we are talking about unstable, so that's
> > normal and expected.
> I also need to sleep sometime, you know... :)
Well, it would be possible to use cron and upload in chunks automatically.
But I think the suggestion from Ondrej is even better: Upload everything
in source-only form at once and let the autobuilders do their job.
> Though for the "propagate to testing", I need to find out a way to fix
> the current state of things, because right now, it's really done in a
> *very* messy way for which I'm not satisfied at all. We currently have
> half of Newton not yet migrated to Testing. Do you know if there's
> another way than just opening an RC bug on each and every package?
That's a very good question.
One possibility is to use the urgency field for the uploads.
For example, when uploading python-fixtures, using "high" instead of
"medium" would have reduced the time the packages are broken in
I think it is also possible to modify the urgency of an already
uploaded package by asking the release managers specifically.
For example, I think it would be possible to submit a bug against
release.debian.org saying "please modify the urgency for the following
source packages to be 20 days instead of the 5 days I used for the
But maybe the thing that would help most to avoid the breakage
that happened in testing this time would be a britney script
which honors build-dependencies and not just dependencies.
Hopefully some FTPMaster some day will fix that. If not, the code for
"dak" is in git, so we would just need a little bit of time, patience,