[Pkg-ganeti-devel] Ganeti package

[Apollon Oikonomopoulos]

On 17:44 Fri 12 Jul     , Guido Trotter wrote:
> +Iustin who's also a debian packake maintainer:
Hi Iustin :)

> 
> On Fri, Jul 12, 2013 at 5:44 PM, Guido Trotter <ultrotter at google.com> wrote:
> > On Fri, Jul 12, 2013 at 4:33 PM, Apollon Oikonomopoulos
> > <apoikos at gmail.com> wrote:
> >> Hi Guido,
> >>
> >> Just wanted to let you know that I pushed the following (minor) changes to the
> >> Debian package repository:
> >>
> >> Apollon Oikonomopoulos (5):
> >>       Canonicalize Vcs-* fields
> >>       Bump compat to 9
> >>       Bump standards version to 3.9.4
> >
> > Are you sure we are 3.9.4 compatible? In particular I was trying to
> > figure out if we were ok for 7.8 "Built-Using".

I don't think it applies to us, see #688251[1]. Do you have any specific 
examples of 3rd party sources we use to build Ganeti? From what I can 
gather from #688251 and a discussion I remember in -devel, Built-Using 
is actually meant to address some very special needs, it's just the 
policy wording that makes it easy to think ligbhc-*-dev should be 
included there.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688251

> >
> >
> >>       Convert to dh_python2
> >>       Do not ship underscore.js
> >>
> >> The debdiff output is what I expected. One question though: I chose to
> >> Build-Depend on python-all rather than python (or pythonX.Y), so that the
> >> ganeti module ships for all available python versions. Any objections to that?
> >>
> >
> > That's ok for me, as long as we're compatible with all those versions
> > (for example I know that we're not compatible with python 3, IIRC).
> > How does it behave exactly? Which versions do we ship with?

For unstable, right now python-all depends only on 2.7. For stable it 
depends on both, 2.6 and 2.7, so if we put out a bpo for wheezy it will 
support both 2.6 and 2.7.  I don't expect it to ever depend on python 
2.x and 3 at the same time TBH (python3 is a different package and 
considered a completely different runtime by the Debian Python Policy 
[2]), but at some point it will also depend on 2.8 for unstable.

[2] http://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-versions

> >
> >> Next week I plan on adding logrotate support (I use it on my servers
> >> anyway).
> >>
> >
> > Thanks. Could you also add a changelog entry (for 2.7.0-2, as I
> > already uploaded 2.7.0-1) with your name and changes? We can then
> > upload that or upload 2.7.1-1, with both. In general it'd be best to
> > keep debian/changelog up to date with the changes, I believe.

Will do, I didn't know if you use git-dch or something like that.

Apollon