[DRE-maint] Bug#1049999: vagrant: the future of packaging vagrant in Debian
Kentaro HAYASHI
kenhys at xdump.org
Fri Aug 18 06:56:28 BST 2023
Package: vagrant
Version: 2.3.4+dfsg-1
Severity: normal
X-Debbugs-Cc: kenhys at xdump.org
Dear Maintainer,
* What led up to the situation?
HashiCorp adopts the BSL.
https://ir.hashicorp.com/news-releases/news-release-details/hashicorp-adopts-
business-source-license-future-releases-its
Currently, vagrant 2.3.4+dfsg-1 was packaged in debian.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Should we keep non-BSL licenced version (A) or drop it (B)?
* What was the outcome of this action?
Plan A.
- Update to 2.3.7 and hold it. (2.3.7 is the last non-BSL licenced
version)
- Follow a newer version only when BSL limitation expired (4 years).
- As a result, we can't use newer feature in timely manner if you stick
on packaged vagrant in Debian.
Plan B.
- Drop vagrant because of that changed licence and no need to
keep older vagrant.
- No vagrant avaiable in Debian. Just use upstream's package.
* What outcome did you expect instead?
N/A
More information about the Pkg-ruby-extras-maintainers
mailing list