Bug 222474 - sysutils/nomad: Update to upstream version 0.6.3
Summary: sysutils/nomad: Update to upstream version 0.6.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: Thomas Zander
URL:
Keywords: easy, patch, patch-ready
: 222493 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-09-20 15:31 UTC by Thomas Zander
Modified: 2017-10-14 08:29 UTC (History)
1 user (show)

See Also:
riggs: maintainer-feedback-


Attachments
Update to 0.6.3 (3.23 KB, text/plain)
2017-09-20 15:31 UTC, Thomas Zander
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Zander freebsd_committer freebsd_triage 2017-09-20 15:31:59 UTC
Created attachment 186569 [details]
Update to 0.6.3

Removed GH_TUPLE as the port includes all its Go dependencies in the vendor subdir.
Comment 1 Thomas Zander freebsd_committer freebsd_triage 2017-10-04 17:07:59 UTC
Maintainer timeout
Comment 2 commit-hook freebsd_committer freebsd_triage 2017-10-04 17:09:43 UTC
A commit references this bug:

Author: riggs
Date: Wed Oct  4 17:09:14 UTC 2017
New revision: 451237
URL: https://svnweb.freebsd.org/changeset/ports/451237

Log:
  Update to upstream version 0.6.3, remove GH_TUPLE (no longer needed)

  PR:		222474
  Submitted by:	riggs
  Approved by:	maintainer timeout
  MFH:		2017Q4

Changes:
  head/sysutils/nomad/Makefile
  head/sysutils/nomad/distinfo
Comment 3 John Hixson freebsd_committer freebsd_triage 2017-10-04 17:50:03 UTC
I submitted a port update, why do you guys keep doing this? Does being a maintainer not mean anything anymore? I update this port religiously. So you guys sit on my update and commit (and in some cases give away) other peoples updates, what gives? This project is filled with a bunch of snobby bullies and it's getting really old dealing with this crap.
Comment 4 Thomas Zander freebsd_committer freebsd_triage 2017-10-04 19:44:30 UTC
(In reply to jhixson from comment #3)

First, I believe a little politeness is in order. There is no need for swearing or insulting. I can assure you there was no intent of bullying or being snobby in this commit.
Of course maintainership means a lot in this project. If you check the lifecycle of this bug report, you can find that it was submitted more than two weeks ago. You can also see that a request for maintainer feedback was sent out upon submission. After the absence of any reaction whatsoever on your behalf for two weeks, when I saw the report lurking in my todo-list, I assumed you were not able to look into this at the moment, so I logged the maintainer timeout and committed the changeset as indicated in the log below. This is in accordance with the documented policies in this project.
It was definitely not my intention to insult you or undervalue your maintainership, and I hope that you continue to constructively work on FreeBSD.
Comment 5 Thomas Zander freebsd_committer freebsd_triage 2017-10-04 19:50:23 UTC
*** Bug 222493 has been marked as a duplicate of this bug. ***
Comment 6 John Hixson freebsd_committer freebsd_triage 2017-10-04 21:06:44 UTC
(In reply to Thomas Zander from comment #4)

My apologies for any attitude I have. I've been trying to get a port commit for ~10 years? So I value the ports I maintain so I can at least have some sort of history, since I continuously am denied due to "not having enough history". I have also submitted new ports that were then promptly given to someone else. This is not your fault, however, my patience has worn thin and my faith has dwindled to zero. My port submissions are often sat on for long periods of time and then others commit without even looking at mine. Again, I apologize for my attitude and snarkyness, I'll try to maintain better composure in the future.
Comment 7 John Hixson freebsd_committer freebsd_triage 2017-10-04 21:08:04 UTC
(In reply to jhixson from comment #6)

I'd also like to add these things keep getting marked as spam.