On 10/13/2016 02:03 AM, Santiago Vila wrote:
>> Then only, B can be built, which also
>> takes so long. Then only A can be built.
>> All of this could take maybe 2 days.
> 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... :)
> They are still unbuildable in testing and they will remain unbuildable
> in testing for four additional days:
All of that because I forgot to upload a single build-dependency:
python-fixtures. Sorry. Hopefully, I'll succeed convincing the current
package maintainers that everything from github.com/testing-cabal needs
to be maintained as a whole, by a single packaging team. Right now, it's
messy, with mock and fixtures maintained elsewhere.
> If you really care about doing "nice" things, I can think of many
> things a lot nicer than uploading 38 unbuildable source packages for
> unstable and then letting them to propagate to testing.
I do feel bad about it, and hopefully, I will have less time pressure
moving forward. I was clearly a bit late for Newton.
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?
> The right thing is still to use a clean sid chroot or doing
> source-only uploads.
The right thing, IMO, is having a sid CI comparable to what I have for
Jessie. Yes, what you wrote works, but it would take too much time.
Thomas Goirand (zigo)