[DRE-maint] Bug#823397: vagrant-libvirt: backport to jessie

2016-09-25 Thread intrigeri
Hi,

Antonio Terceiro:
> I do not have plans to work on this.

> Please go ahead, and feel free to ask on debian-ruby@l.d.o if you have
> issues with the backports.

Time has passed, we did not act on it, and now Stretch is getting
closer, so it's time to clarify that we (Tails) won't be doing
this backport.

JFTR what we're doing currently is installing vagrant-libvirt and
a few dependencies from Stretch (plus a patched ruby-libvirt due to
#823395). It's good enough for us until Stretch is released.

So, maintainers: feel free to close this bug if you wish :)

Cheers,
-- 
intrigeri

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#823397: vagrant-libvirt: backport to jessie

2016-05-04 Thread Antonio Terceiro
On Wed, May 04, 2016 at 09:43:14AM +, anonym wrote:
> Package: vagrant-libvirt
> Severity: wishlist
> 
> Dear Maintainer,
> 
> In Tails [0] we are in the process of migrating our Vagrant-based build
> system from the VirtualBox provider to the Libvirt one thanks to the
> newly uploaded vagrant-livirt package. Since we like Tails to remain
> buildable on Jessie, the vagrant-libvirt package would have to be
> backported to Jessie. In addition, due to its dependencies, the
> following packages would have to be backported to Jessie as well:
> 
> * vagrant
> * ruby-excon
> * ruby-fog-core
> * ruby-fog-libvirt
> * ruby-fog-xml
> 
> Luckily I expect all of these backports to be trivial rebuilds -- at the
> moment installing these packages from Stretch into Jessie works fine.
> 
> In addition to the above, bug #823395 must also be fixed since
> ruby-fog-libvirt requires a ruby-libvirt *with* rubygems integration. An
> alternative would be to also backport ruby-libvirt, since Stretch's
> version already is fixed (it is not installable in Jessie, though, so
> the backporting could be more complicated, YMMV).

I do not have plans to work on this.

Please go ahead, and feel free to ask on debian-ruby@l.d.o if you have
issues with the backports.  ruby-libvirt probably just needs to be built
on jessie (Depends: libvirt0 (>= 1.2.11~rc1) is not satisfiable in
jessie)


signature.asc
Description: PGP signature
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#823397: vagrant-libvirt: backport to jessie

2016-05-04 Thread anonym
Package: vagrant-libvirt
Severity: wishlist

Dear Maintainer,

In Tails [0] we are in the process of migrating our Vagrant-based build
system from the VirtualBox provider to the Libvirt one thanks to the
newly uploaded vagrant-livirt package. Since we like Tails to remain
buildable on Jessie, the vagrant-libvirt package would have to be
backported to Jessie. In addition, due to its dependencies, the
following packages would have to be backported to Jessie as well:

* vagrant
* ruby-excon
* ruby-fog-core
* ruby-fog-libvirt
* ruby-fog-xml

Luckily I expect all of these backports to be trivial rebuilds -- at the
moment installing these packages from Stretch into Jessie works fine.

In addition to the above, bug #823395 must also be fixed since
ruby-fog-libvirt requires a ruby-libvirt *with* rubygems integration. An
alternative would be to also backport ruby-libvirt, since Stretch's
version already is fixed (it is not installable in Jessie, though, so
the backporting could be more complicated, YMMV).

Cheers!

[0] https://tails.boum.org/

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers