Bug 226662 - sysutils/vagrant: update to 2.0.3
Summary: sysutils/vagrant: update to 2.0.3
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL: https://github.com/hashicorp/vagrant/...
Keywords: easy, patch, patch-ready
Depends on:
Blocks:
 
Reported: 2018-03-16 19:05 UTC by Christoph Moench-Tegeder
Modified: 2018-03-16 20:42 UTC (History)
1 user (show)

See Also:
joe: maintainer-feedback+


Attachments
update vagrant to 2.0.3 (33.62 KB, patch)
2018-03-16 19:05 UTC, Christoph Moench-Tegeder
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Moench-Tegeder freebsd_committer freebsd_triage 2018-03-16 19:05:13 UTC
Created attachment 191558 [details]
update vagrant to 2.0.3

vagrant 2.0.3 has been released.

Github account mitchellh now redicrects to hashicorp, so GH_ACCOUNT has been updated accordingly.

Tests are not installed any longer, this shortens pkg-plist significantly.

The "simple build script" .runner.sh has no value to the package and it's installation is probably a mistake, so let's just rm it.

The new gemfiledeps check (ports r459673) fails as this port's Gemfile depends on an external repository (vagrant-spec) which we don't install. This check also fails on vagrant-2.0.2 but wasn't present at the time of the last update. Let's ignore this warning for the time being.

Having written that: port passes "poudriere testport" and still "works for me".
Comment 1 joe 2018-03-16 20:06:31 UTC
Comment on attachment 191558 [details]
update vagrant to 2.0.3

I've approved the patch; however, this version bump does not seem to change any of the actual source code to Vagrant. I won't why they actually published it, then.

-Joe
Comment 2 Christoph Moench-Tegeder freebsd_committer freebsd_triage 2018-03-16 20:37:13 UTC
(In reply to joe from comment #1)
Uh, there have been changes:

$ diff -Nru vagrant-2.0.2 vagrant-2.0.3 | wc -l   
    2039

And from the diff I think it's at least plausible that the items from the changelog are actually there.
Comment 3 Christoph Moench-Tegeder freebsd_committer freebsd_triage 2018-03-16 20:42:03 UTC
committed ports r464729 - thanks
Comment 4 commit-hook freebsd_committer freebsd_triage 2018-03-16 20:42:13 UTC
A commit references this bug:

Author: cmt
Date: Fri Mar 16 20:41:44 UTC 2018
New revision: 464729
URL: https://svnweb.freebsd.org/changeset/ports/464729

Log:
  update sysutils/vagrant to 2.0.3

  The port's upstream github account was changed/renamed, this is reflected
  in the GH_ACCOUNT change.
  Tests are not installed anymore, so pkg-plist is a lot shorter now.
  The ".runner" "simple build script" is not required for the port and
  installed by accident, so just rm it.

  PR:		226662
  Approved by:	joe at thrallingpenguin com

Changes:
  head/sysutils/vagrant/Makefile
  head/sysutils/vagrant/distinfo
  head/sysutils/vagrant/pkg-plist