Bug 237169 - [NEW PORT] www/grafana6: Dashboard and graph editor for multiple data stores
Summary: [NEW PORT] www/grafana6: Dashboard and graph editor for multiple data stores
Status: Closed DUPLICATE of bug 236858
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Kubilay Kocak
URL:
Keywords: feature, needs-qa
Depends on:
Blocks:
 
Reported: 2019-04-09 21:34 UTC by David O'Rourke
Modified: 2019-04-10 01:38 UTC (History)
0 users

See Also:

Attachments
www/grafana6: new port (126.94 KB, text/plain)
2019-04-09 21:34 UTC, David O'Rourke 		no flags Details
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 David O'Rourke 2019-04-09 21:34:15 UTC 
Created attachment 203548 [details]
www/grafana6: new port

This patch takes www/grafana5 and updates it to www/grafana6. The version of Grafana used is 6.1.3.

This work supercedes the port at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236858, as it is a newer version and includes the grafana.conf.in updates. It is submitted as a new issue as the work was done before searching the bug tracker and I'm unsure of how I'd update the other issue.

The following were updated in the move to Grafana 6:
  - pkg-plist: Many added/removed files
  - grafana.conf.in: Updated to latest from upstream sample.ini

As with the grafana5 submission, the maintainer is left as swills@.

-David
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2019-04-10 01:38:21 UTC 
@David Thank you for the submission!

Updating bug 236858 is a matter of attaching the updated patch, and selecting [x] Obsolete during attachment to obsolete the existing patch/attachment. 

That's the better course of action in this case to reduce overhead/bug management and we encourage collaboration on an existing issue/patch in most cases by default

I'll mark this as a duplicate, if you could update the patch in the original bug that would be greatly appreciated :)

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