Hi Lucas An alternative approach would be to 1) keep the vagrant 2.3.7 package as long as it stays maintainable, 2) point out that the HashiCorp Cloud Platform is incompatible and 3) publish updated Debian Vagrant images somewhere else.
TBH I have no idea how feasible 1) is.Generating appropriate metadata JSONs for 3) does not seem to be rocket science.
Best Christopher
smime.p7s
Description: Kryptografische S/MIME-Signatur
_______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
