Glance build-depends on python-all (>= 2.6.6-3~)

[Monty Taylor]

On 11/25/2011 06:45 PM, Thomas Goirand wrote:
> Hi,
> 
> Thanks Monty for your reply, and voicing your view.

You can always count on me for that! :)

> On 11/26/2011 01:28 AM, Monty Taylor wrote:
>> Setting the build depends on python-all to 2.6.6-3~ makes backports very
>> difficult, and means that we'd have to fork the packaging to handle
>> anything that isn't either wheezy, natty or oneiric. Don't even get me
>> started on how terrible the transition to dh_python2 has been
>> orchestrated - but suffice it to say, for us continuing to sanely
>> support squeeze and lucid is important, so breaking the packaging for
>> them is a non-starter.
> 
> I could agree with that if there was consistency. But that's not the
> case. Nova has a build-depends on python-all-dev (>= 2.6.6-3~) but not
> Glance who only build-depends on python-all-dev without version!

There has been dissent within our ranks about the right way to do this...

> As for supporting Squeeze, I'm not aware of anyone supporting it (but
> Rackspace internally maybe), and not I'm not aware either of any
> messages sent to debian-backports at lists.debian.org asking or announcing
> support for Squeeze. Have you seen otherwise?

In this case, I believe the word "us" is quite vague, for which I
apologize. The ongoing issue that arises in the conversations around
packaging and OpenStack (and other places as well, but specifically
here) is the difference in intent or focus between upstream and distros,
and how to resolve that when upstream is directly involved in packaging
efforts.

When I say "us" or "we" in this context, I am speaking in my role as
upstream. While sid and precise are both extremely important for
OpenStack, the current production targets that I am personally aware of
are squeeze, lucid and in one case natty. For that reason, the thing
that I am most concerned with is suitability of packages for released
and still supported yet old versions of the distros, while I understand
fully that what the distros are most interested in (quite correctly) is
the most recently released version of OpenStack for the upcoming distro
(sid or precise)

> More over, it's the general consensus that we shouldn't sacrifice SID
> (and even less transitions) just in order to facilitate back-porting. If
> you want to do that in Ubuntu, then fine, but I don't think my fellow
> DDs will in SID. Also, adding the version warns the backporter that he
> should not forget to add a build-depends on python-support / python-central.

Again, and sorry I wasn't clear before, but I'm speaking as upstream,
not as Ubuntu. Ubuntu agrees with you - although they have a similar
focus, so a single source package that builds for lucid, squeeze, and
sid is more important to me than to either of you.

That the current dh_python2 transition did not provide any mechanism for
supporting use cases of upstreams such as mine is something that I find
extremely frustrating. But I'm doing my best to figure something out. :)

>> However, you'll notice that in the debian/rules file we check for the
>> existence of dh_python2, and if it is there, we use it, otherwise we
>> don't - so we do not actually have a build depend on that version of python.
> 
> That's very good, and I support this. However, having it without a
> build-depends on python-central or python-support is pretty useless, so
> anyway you put it, an eventual backport would have to deal with
> rewriting debian/control, and then I believe having a build-depends with
> version isn't an issue at all.

Good point - I shall add a build-depend on python-support. Turns out,
even though that will add an addition unnecessary build depend on sid,
oneiric and precise, it does result in a source pacakge that works on
all releases without modification. Again though - I understand if this
is something that you don't care about strongly.

>>> Also, on next upload, could you set:
>>>
>>> Maintainer: openstack-packaging at lists.ubuntu.com
>>> Uploaders: Ghe Rivero <ghe at debian.org>, Thomas Goirand <zigo at debian.org>
>>>
>>> rather than me as maintainer? Otherwise, I'll be the only one to receive
>>> bug reports.
>>
>> I'm not seeing you as the maintainer in the packaging? Where are you
>> looking?
> 
> In the recently uploaded packages in Debian, not in Ubuntu!

Aha! This explains why I didn't see it in the packaging repo.

> I was planning to make an announcement to this list separately, but
> let's do that one. I was the one who uploaded Cactus in Debian, but now,
> I'm very happy to announce that we are a team of 4 DDs working on
> OpenStack. And I have to admit that I didn't do anything for it recently
> but criticize others work... I hope to have more time for it soon, and
> spend more time and love with OpenStack. Specifically, I am planning on
> doing real life tests in SID.

Excellent! I'm thrilled to hear/see this.

> Here's the current team on Alioth:
> 
> Thomas Goirand <zigo at debian.org> (eg: myself)
> Ghe Rivero <ghe at debian.org>
> Julien Danjou <acid at debian.org>
> Loic Dachary <loic at debian.org>
> 
> Please warmly welcome them 3! :)

Welcome everybody! And thanks for all the work!

Monty