Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt

[Ville Korhonen]

Hi,

On Fri, 19 Feb 2016 17:50:31 +0100 intrigeri  wrote:
> Antonio Terceiro wrote (19 Feb 2016 12:48:29 GMT) :
> > On Wed, Feb 17, 2016 at 07:18:58PM +0100, intrigeri wrote:
> >> It would be awesome if this could be uploaded within the next few
> >> weeks or months [...]
>
> > by all means, please go ahead.
>
> Woohoo, this is encouraging, thanks :)
>
> I can certainly do the initial upload.

Any progress on this? I'd be very happy to test this package after it has
entered experimental/unstable... And it would be really nice to have this
package in next stable so I could do "apt-get remove virtualbox". :)


-ville

Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt

[intrigeri]

Hi,

Antonio Terceiro wrote (19 Feb 2016 12:48:29 GMT) :
> On Wed, Feb 17, 2016 at 07:18:58PM +0100, intrigeri wrote:
>> It would be awesome if this could be uploaded within the next few
>> weeks or months [...]

> by all means, please go ahead.

Woohoo, this is encouraging, thanks :)

I can certainly do the initial upload.

But I can't reasonably commit to maintain these two packages on the
long term; besides, not being a Ruby guy, I'm concerned that just
staying on top of current pkg-ruby-extras best practices would add
some overhead on my side that I'd rather skip. So I'd rather not be
listed in the Uploaders field.

What I can do, though, is use the packages daily, on my personal
systems (sid) and on the Tails infrastructure (generally Debian
stable), file as good bug reports as I can, and send you folks pull
requests whenever I can do that without leaving my comfort zone
too much.

So, who wants to be commit to maintain the package (== be listed in
the Uploaders field)? Antonio and/or Miguel? Anyone else?

Another option (that I like less, but well) could be that I try to
maintain the package as long as it's easy, and I shout and ask for
help whenever it gets harder / more Ruby -specific.

> when you have code to create the boxes, would you please add them to
> http://anonscm.debian.org/cgit/cloud/debian-vm-templates.git/ ?

> (feel free to send me patches if you don't want to go through the hoops to
> obtaining write access etc)

I'll check with anonym how we do boxes, and we'll see if/how it
applies to Debian cloud images.

> or does it use the virtualbox boxes the way they are?

I think we can either trivially convert a VirtualBox box with
qemu-img, or build a dedicated one e.g. with vmdebootstrap.

Cheers!
-- 
intrigeri

Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt

[Antonio Terceiro]

On Wed, Feb 17, 2016 at 07:18:58PM +0100, intrigeri wrote:
> Hi Miguel, Antonio and others,
> 
> Miguel Landaeta wrote (14 Aug 2015 20:10:32 GMT) :
> > On Thu, Aug 13, 2015 at 03:52:11PM +0200, intrigeri wrote:
> >> It would not be reasonable of me to add these packages to my plate,
> >> but perhaps the pkg-ruby-extras team could?
> 
> > Awesome, if nobody beats me to it I could take a look at them and
> > upload them soon.
> 
> Excellent!
> 
> I wanted to move this forward a bit, so I've merged Antonio's previous
> work into mine (we had Git history without any common ancestor), and
> then updated both packages to the latest upstream release.
> 
> The current state of my work can be found there:
> 
>   https://git-tails.immerda.ch/intrigeri/ruby-fog-libvirt/
>   https://git-tails.immerda.ch/intrigeri/vagrant-libvirt/
> 
> The resulting binary packages have seen a bit of manual testing,
> conducted by my Tails team-mate anonym (Cc'ed). I assume he'll be
> happy to go on testing preliminary packages if needed :)
> 
> It would be awesome if this could be uploaded within the next few
> weeks or months (we'll likely need this for working on making Tails
> builds reproducible soonish, and in any case getting rid of our
> dependency on VirtualBox would make the life of some of our developers
> easier).

by all means, please go ahead.

when you have code to create the boxes, would you please add them to
http://anonscm.debian.org/cgit/cloud/debian-vm-templates.git/ ?

(feel free to send me patches if you don't want to go through the hoops to
obtaining write access etc)

or does it use the virtualbox boxes the way they are?

> Antonio: for vagrant-libvirt, it seems that you haven't pushed your
> upstream and pristine-tar branches, nor the upstream/0.0.31 tag, while
> you pushed the corresponding changes in the master branch. And for
> ruby-fog-libvirt, it seems that you haven't pushed the upstream/0.0.2
> tag. Can you please push the missing bits? Thanks in advance!

argh, sorry about that. just did it.


signature.asc
Description: PGP signature

Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt

[intrigeri]

Hi Miguel, Antonio and others,

Miguel Landaeta wrote (14 Aug 2015 20:10:32 GMT) :
> On Thu, Aug 13, 2015 at 03:52:11PM +0200, intrigeri wrote:
>> It would not be reasonable of me to add these packages to my plate,
>> but perhaps the pkg-ruby-extras team could?

> Awesome, if nobody beats me to it I could take a look at them and
> upload them soon.

Excellent!

I wanted to move this forward a bit, so I've merged Antonio's previous
work into mine (we had Git history without any common ancestor), and
then updated both packages to the latest upstream release.

The current state of my work can be found there:

  https://git-tails.immerda.ch/intrigeri/ruby-fog-libvirt/
  https://git-tails.immerda.ch/intrigeri/vagrant-libvirt/

The resulting binary packages have seen a bit of manual testing,
conducted by my Tails team-mate anonym (Cc'ed). I assume he'll be
happy to go on testing preliminary packages if needed :)

It would be awesome if this could be uploaded within the next few
weeks or months (we'll likely need this for working on making Tails
builds reproducible soonish, and in any case getting rid of our
dependency on VirtualBox would make the life of some of our developers
easier).

Antonio: for vagrant-libvirt, it seems that you haven't pushed your
upstream and pristine-tar branches, nor the upstream/0.0.31 tag, while
you pushed the corresponding changes in the master branch. And for
ruby-fog-libvirt, it seems that you haven't pushed the upstream/0.0.2
tag. Can you please push the missing bits? Thanks in advance!

Cheers,
--
intrigeri

Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt

[Miguel Landaeta]

On Thu, Aug 13, 2015 at 03:52:11PM +0200, intrigeri wrote:
 
 I've prepared an initial, untested packaging of vagrant-libvirt and
 its only missing dependency:
 
   https://git-tails.immerda.ch/intrigeri/vagrant-libvirt
   https://git-tails.immerda.ch/intrigeri/ruby-fog-libvirt
 
 It would not be reasonable of me to add these packages to my plate,
 but perhaps the pkg-ruby-extras team could?

Awesome, if nobody beats me to it I could take a look at them and
upload them soon.

Thanks!

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
Faith means not wanting to know what is true. -- Nietzsche


signature.asc
Description: Digital signature

Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt

[intrigeri]

Hi,

Antonio Terceiro wrote (16 Jun 2015 18:19:57 GMT) :
 Now it is even easier to package vagrant plugins, instructions are in
 the README.Debian for vagrant: [...]

Confirmed, thanks a lot for making it this simple!

I've prepared an initial, untested packaging of vagrant-libvirt and
its only missing dependency:

  https://git-tails.immerda.ch/intrigeri/vagrant-libvirt
  https://git-tails.immerda.ch/intrigeri/ruby-fog-libvirt

It would not be reasonable of me to add these packages to my plate,
but perhaps the pkg-ruby-extras team could?

If someone (or preferably a team) volunteers, then I'm sure that
someone at Tails will happily test packages before they are uploaded
to the archive. Many thanks in advance!

Cheers,
--
intrigeri

Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt

[Antonio Terceiro]

Hello all,

On Thu, Aug 14, 2014 at 11:31:31AM -0300, Antonio Terceiro wrote:
 Hi,
 
 On Sat, Aug 02, 2014 at 06:00:23PM -0300, Miguel Landaeta wrote:
  block 753012 by 740165
  thanks
  
  I pushed my packaging to 
  git://anonscm.debian.org/pkg-ruby-extras/vagrant-libvirt.git.
  
  This is not ready because:
  
  * It needs to be tested with vagrant = 1.5. (see #741478).
  * Support for vagrant plugin is needed in Debian. (see #740165).
  
  I based my work on what Antonio Terceiro did for vagrant-lxc, so I'm
  CCing him in case he wants to add a comment about this.
 
 A heads up:
 
 I recently uploaded vagrant with the patch supporting Debian plugins,
 but it turned out to break installing plugins via vagrant itself
 (#758033), so I had to revert that and reopen the original bug for
 Debian-provided plugins (#740165).
 
 I will have to figure out a different way of providing plugins via
 debian packages that does not break the standard one.

Since then, I was able to finally make it work, and vagrant-lxc is even
already in the archive and working; I use it on a daily basis.

Now it is even easier to package vagrant plugins, instructions are in
the README.Debian for vagrant:

https://anonscm.debian.org/cgit/collab-maint/vagrant.git/tree/debian/README.Debian

-- 
Antonio Terceiro terce...@debian.org


signature.asc
Description: Digital signature

Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt

[Antonio Terceiro]

Hi,

On Sat, Aug 02, 2014 at 06:00:23PM -0300, Miguel Landaeta wrote:
 block 753012 by 740165
 thanks
 
 I pushed my packaging to 
 git://anonscm.debian.org/pkg-ruby-extras/vagrant-libvirt.git.
 
 This is not ready because:
 
 * It needs to be tested with vagrant = 1.5. (see #741478).
 * Support for vagrant plugin is needed in Debian. (see #740165).
 
 I based my work on what Antonio Terceiro did for vagrant-lxc, so I'm
 CCing him in case he wants to add a comment about this.

A heads up:

I recently uploaded vagrant with the patch supporting Debian plugins,
but it turned out to break installing plugins via vagrant itself
(#758033), so I had to revert that and reopen the original bug for
Debian-provided plugins (#740165).

I will have to figure out a different way of providing plugins via
debian packages that does not break the standard one.

-- 
Antonio Terceiro terce...@debian.org


signature.asc
Description: Digital signature

Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt

[Miguel Landaeta]

block 753012 by 740165
thanks

I pushed my packaging to 
git://anonscm.debian.org/pkg-ruby-extras/vagrant-libvirt.git.

This is not ready because:

* It needs to be tested with vagrant = 1.5. (see #741478).
* Support for vagrant plugin is needed in Debian. (see #740165).

I based my work on what Antonio Terceiro did for vagrant-lxc, so I'm
CCing him in case he wants to add a comment about this.

Cheers,

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
Faith means not wanting to know what is true. -- Nietzsche


signature.asc
Description: Digital signature

Bug#753012: ITP: vagrant-libvirt -- Vagrant provider for libvirt

[Antonio Terceiro]

On Sat, Aug 02, 2014 at 06:00:23PM -0300, Miguel Landaeta wrote:
 block 753012 by 740165
 thanks
 
 I pushed my packaging to 
 git://anonscm.debian.org/pkg-ruby-extras/vagrant-libvirt.git.
 
 This is not ready because:
 
 * It needs to be tested with vagrant = 1.5. (see #741478).
 * Support for vagrant plugin is needed in Debian. (see #740165).
 
 I based my work on what Antonio Terceiro did for vagrant-lxc, so I'm
 CCing him in case he wants to add a comment about this.

I want to add that the support for plugins that I wrote against vagrant
1.4 does not apply at all to vagrant 1.5 and that is why I didn't upload
vagrant-lxc yet; I am still to try vagrant 1.6 to see where we stand
there.

-- 
Antonio Terceiro terce...@debian.org


signature.asc
Description: Digital signature