Bug 222493 - sysutils/nomad: Update to 0.6.3
Summary: sysutils/nomad: Update to 0.6.3
Status: Closed DUPLICATE of bug 222474
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:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-21 16:20 UTC by John Hixson
Modified: 2017-10-04 19:50 UTC (History)
1 user (show)

See Also:

Attachments
port diff file (3.29 KB, patch)
2017-09-21 16:20 UTC, John Hixson 		dbaio: maintainer-approval+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Hixson freebsd_committer freebsd_triage 2017-09-21 16:20:07 UTC 
Created attachment 186593 [details]
port diff file
Comment 1 Danilo G. Baio freebsd_committer freebsd_triage 2017-09-21 23:15:16 UTC 
Thank you for your contribution. Could you please:

Confirm that this change passes QA (portlint, poudriere in particular). 
For more information, see: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing.html
Comment 2 Danilo G. Baio freebsd_committer freebsd_triage 2017-09-21 23:15:32 UTC 
Comment on attachment 186593 [details]
port diff file

Set the maintainer-approval flag value to + on attachments for ports you are maintainer of. 
Attachment -> Details -> maintainer-approval [+]
Comment 3 John Hixson freebsd_committer freebsd_triage 2017-09-22 18:12:24 UTC 
john@pcbsd /usr/home/john/ports/nomad$ portlint -ac
WARN: Consider to set DEVELOPER=yes in /etc/make.conf
0 fatal errors and 1 warning found.
Comment 4 Thomas Zander freebsd_committer freebsd_triage 2017-10-04 19:50:23 UTC 
Submitted and committed in the course of bug #222474

This report did not show up in the "Ports bugs, that do not have been looked at yet" query on the Dashboard (presumably because dbaio@ had alread edited it), otherwise I would have merged it with #222474 earlier. My apologies.

*** This bug has been marked as a duplicate of bug 222474 ***