On Sun, Sep 21, 2014 at 09:36:24PM +0200, Jeremiah C. Foster wrote: > On Thu, Sep 11, 2014 at 10:52:41AM -0300, Antonio Terceiro wrote: > > Hello, thanks for getting in touch. > > > > On Wed, Sep 10, 2014 at 10:01:21PM +0200, Jeremiah C. Foster wrote: > > > Package: vagrant > > > Version: 1.4.3+dfsg1-2 > > > Severity: wishlist > > > > > > Dear Maintainer, > > > > > > Vagrant is 1.6.5 upstream and upstream appears to have deb's available > > > so packaging a newer vagrant for Debian might be low hanging fruit. > > > > Unfortunately that is not the case. > > I'm sorry to hear that. > > > The upstream .deb's are just .debs, > > but do not follow the Debian policy at all. Packaging vagrant in a sane > > way (from Debian's POV) is not trivial. > > What is the best way to find what is needed to help package Vagrant? > Should one `debdiff` the package to find what is different with > Debian's version and try and Debianize the package that way?
looking at debian/patches/ inside the source package should be enough. > have a handy list of the steps you take to update a package for > Vagrant so I might be able to see if there is something I might help > with? Basically the vagrant code is full of assumptions about it being installed by it's own installer. we need to patch vagrant to remove those assumptions. -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
