On 10/13/2016 02:29 AM, Santiago Vila wrote:
> For the record, here is a tarball for the 38 unbuildable source
> packages in testing I detected today related to OpenStack.
> It could be that the intention was to avoid FTBFS, but this has been
> the result.
> We might better have FTBFS happen in buildd.debian.org in unstable,
> as that's really the best way to ensure that packages are buildable.
> Thanks.


It's very easy to throw stones at me for not following the best practice
in this way. Checking if a package builds correctly is indeed important,
but I consider that runtime is even more important, as it impacts
directly our users. On this ground, I did the correct work, and the
disruption in unstable was very short. I was also able to reach the
deadline of the OpenStack release on time for this release, just right
after finishing to move all packages to upstream Gerrit. This wasn't a
trivial task.

For the next release, I hope to have more time and build all in sbuild,
as I used to, with a local repository of already built packages, which
I'll be able to upload all at once as well. I've done that in the past,
and I'll do again. I have no doubts that this is the correct way to do
things, don't worry about that, you don't need to convince me on this.
This is by the way my plans for building jessie-backports of OpenStack
Newton, which is what I did for Mitaka (and uploaded all just right
before debconf 16, all at once, without any issue).

Back to the issue: can you check if #835177 is really solved, and aodh
builds fine for you with eatmydata?


Thomas Goirand (zigo)

Reply via email to