Date: Fri, 30 Nov 2018 23:32:21 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 233677] sysutils/vagrant: update to 2.2.2 Message-ID: <bug-233677-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233677 Bug ID: 233677 Summary: sysutils/vagrant: update to 2.2.2 Product: Ports & Packages Version: Latest Hardware: Any URL: https://github.com/hashicorp/vagrant/blob/v2.2.2/CHANG ELOG.md OS: Any Status: New Keywords: easy, patch, patch-ready Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: cmt@freebsd.org CC: joe@thrallingpenguin.com CC: joe@thrallingpenguin.com Flags: maintainer-feedback?(joe@thrallingpenguin.com) Created attachment 199699 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D199699&action= =3Dedit update vagrant to 2.2.2 A new release, once again. This release is said to fix an regression with the new default NIC type for virtualbox guests, see - https://github.com/hashicorp/vagrant/pull/10383 - https://github.com/hashicorp/vagrant/issues/10448 - https://github.com/hashicorp/vagrant/pull/10450 I can't reproduce the problem, and don't see regressions with the fix (but then, as far as this PR here is concerned, my host is running neither MacOS= nor Ubuntu, for very obvious reasons). Anyways, let's have the patch so we get rid of vagrant's upgrade notifier a= nd stay close to upstream. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233677-7788>