[pkg-eucalyptus-maintainers] Updated euca2ools to version 1.2 in Debian.

Steffen Möller steffen_moeller at gmx.de
Fri Mar 12 14:22:11 UTC 2010

Hello Dustin,

have many thanks for your friendly and constructive email.

Dustin Kirkland wrote:
> On Thu, 2010-03-11 at 13:25 +0900, Charles Plessy wrote:
>> I did not manage to find a way to get the bzr source of euca2ools as a git
>> branch (the last commit of the git-bzr tool is not encouraging: “Add a note
>> saying I'm really not interested in this anymore ”). However, I can add the bzr
>> repository to the mr configuration file, so that by default the euca2ools
>> Debian package would be checked out in an euca2ools directory, and the Bzr
>> upstream source in an euca2ools-upstream directory, for instance.
> I've had a conversation with the Eucalyptus guys about the bzr branch
> and the Launchpad project.
> Very soon, I hope, the Eucalyptus guys should be using a separate
> project in Launchpad for euca2ools, which should be at:
>  * http://launchpad.net/euca2ools
> This project would have it's own branch, separate from the eucalyptus
> source tree.

This might simplify bits ... a bit.

>> I see that the euca2ools package is evolving at a fast pace in Ubuntu. In the
>> short term, do we want to do the same in Debian, or do we go for the official
>> releases only as long as we do not have a full Eucalyptus system operational in
>> Debian?
> This is basically euca2ools 1.2, with a number of cherry picked commits,
> up to the upstream bzr revision r262, in order to fix a number of bugs
> for the Lucid release.
> We will likely continue filing/fixing/upstreaming/cherrypicking such
> bugs all the way up until the Lucid release slated for April 30, 2010.
> For this reason, we will not be able to be "downstream" of Debian for
> the euca2ools package.  However, I'm very keen on sharing the changes we
> make to the euca2ools packages with Debian in any way that makes sense.

Hm. What you describe makes perfect sense to me. There is no point to
keep unstable in complete sync with the trunk, so having patches on top
of 1.2 is already extremely nice. You can upload to Debian (and become a
Debian Maintainer for that rather easily) what you upload to Ubuntu if
you want, I presume Charles to agree. Now we have this git repository
set up. I am not sure how to use that, probably one just adds the latest
version number and checks for possibly differently named dependencies
over what you have with Ubuntu.

I am very excided about the positive vibrations that you send to Debian.
Is there any particular way in that you would profit from our
activities? We have updated a few packages over what is in Ubuntu, Chris
is doing a lot on his upstream end to accomodate for the various
differences between versions. But I do not see how you directly profit
from being nice to us but very much like to see that.

Many greetings


More information about the pkg-eucalyptus-maintainers mailing list