Groups > linux.debian.bugs.dist > #964059

Bug#896904: New upstream available

From	Antonio Terceiro <terceiro@debian.org>
Newsgroups	linux.debian.bugs.dist
Subject	Bug#896904: New upstream available
Date	2019-07-10 20:40 +0200
Message-ID	<yipFw-3sQ-7@gated-at.bofh.it> (permalink)
References	<vIuQa-7CO-5@gated-at.bofh.it> <yipFw-3sQ-9@gated-at.bofh.it> <vIuQa-7CO-5@gated-at.bofh.it> <yipFw-3sQ-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Control: tag -1 + wontfix

On Wed, Jul 10, 2019 at 04:55:06PM +0200, Inaki Malerba wrote:
> Dear Maintainer,
> 
> This issue is still present. I tested version 2.2.4 from upstream and
> works fine.

Any version that you test from upstream will work, because installing a
vagrant plugin means directly installing Ruby packages (the plugins
themselves and their dependencies) from rubygems.org into a
vagrant-specific location.

In Debian, this is patched to use regular Debian packages, and when you
install a vagrant plugin via vagrant, sometimes the plugins
dependencies, specially version constraints, won't be met by the package
correspondent packages in Debian.

> Please consider packaging the latest version.

This will not solve the problem. If you *need* to install stuff that is
not in Debian, the only certain solution at the moment is using Vagrant
from upstream as well.

Back to linux.debian.bugs.dist | Previous | Next | Find similar | Unroll thread

Thread

Bug#896904: New upstream available Antonio Terceiro <terceiro@debian.org> - 2019-07-10 20:40 +0200

csiph-web