Check what's the future of Vagrant for Tails
In the latest update on sid I read this:
vagrant (2.3.7+git20230731.5fc64cde+dfsg-1) unstable; urgency=medium
[ Antonio Terceiro ]
* Drop myself from Uploaders
[ Lucas Nussbaum ]
* New upstream version 2.3.7+git20230731.5fc64cde+dfsg
+ This is the last commit before the license change to BUSL.
* Add patch: 0009-Raise-error-if-openssl-headers-not-found.patch
* Add build-dep on libssl-dev and switch to Architecture: any to build the
vagrant_ssl extension
* Fix rubygems-integration path due to the above arch:any change
* Drop Build-dep on ruby-net-ftp, which is provided by libruby3.X anyway.
Closes: #1070420
* Remove watch file: we don't expect upstream updates
* Add patch 0010-Remove-shebang-from-bash-completion-file.patch to fix
lintian warning.
-- Lucas Nussbaum <lucas@debian.org> Mon, 06 May 2024 21:08:41 +0200
Note in particular "we don't expect upstream updates" and "This is the last commit before the license change to BUSL".
The discussion on the Debian front is happening on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049999.
Timing:
- Let's first wait for the dust to settle a bit on the Debian side.
- This has nothing to do with Tails 7.0 strictly speaking, but likely by the time we'll be preparing 7.0, it'll be great time to look into this, hence the milestone to ensure we don't forget about it.
Edited by intrigeri