Comment 13 for bug 1559420

Revision history for this message
Jean-Pierre van Riel (jpvr) wrote :

Still impacting me, and xenial is meant to be LTS, so leaving vagrant broken is a bit rough?

Also, while upstream provides an alternative, it's quite nasty as it ends up bundling all it's own lib dependencies and, in my case, replaced/force upgraded libarchive13 causing some package dependency issues.

Options:
- backport patch
- update to newer upstream vagrant version

Assuming vagrant 1.8.x series, 1.8.5 includes a huge set of bug fixes and should be mostly backward compatible with 1.8.1, given it's not a major version change. There was only 3 points noted under "BREAKING CHANGES" for 1.8.3. They didn't seem to be major concerns.