On Tue, Jul 29, 2014 at 10:23:51AM +0200, Bálint Réczey wrote:
> Hi,
> 
> 2014-07-27 1:51 GMT+02:00 Balint Reczey <bal...@balintreczey.hu>:
> > Control: tags -1 patch
> >
> > On 03/12/2014 09:54 PM, Mert Dirik wrote:
> >> Looks like it is fixed in upstream in commit 27420ad [1] by removing the
> >> offending files. New upstream version (1.5) should fix this bug.
> >>
> >> [1]
> >> https://github.com/mitchellh/vagrant/commit/27420ad2ee78caf1b1effc3eb27744ae2c288009
> > IMO the files still have to be removed from orig.tar.gz by repackaging
> > it as 1.6.3+dfsg1 manually.
> > I see 1.5.3 imported to packaging git, but it still has the files thus
> > would not solve this RC bug.
> > Antonio, do you plan releasing 1.6.3 with the problematic files removed
> > from the source?
> >
> > The attached patch will remove the whole website dir from the source
> > when using uscan --repack.
> >
> > I can push it to the packaging repository, but I did not want to do so
> > before asking first.
> I have pushed the fix to the packaging repository and also created
> 1.5.3+dfsg1 with the website dir filtered out.
> Is there a package update in the plans?

The problem is that I still couldn't make 1.5.3 work on Debian at all.
Apparently several parts of the code assume it was installed using
Vagrant's own installer and will have to be patched to work on Debian.

I would rather try the new upstream release instead.

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

Attachment: signature.asc
Description: Digital signature

Reply via email to