Summary: | www/gophernicus: Update to 3.1.1 and take maintainership | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Anton McClure <anton> | ||||||
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||||
Status: | Closed Overcome By Events | ||||||||
Severity: | Affects Only Me | CC: | anton, ygy | ||||||
Priority: | --- | Keywords: | needs-qa, patch | ||||||
Version: | Latest | ||||||||
Hardware: | Any | ||||||||
OS: | Any | ||||||||
Attachments: |
|
(In reply to Anton McClure from comment #0) It is usually preferred to adopt a port while updates its version. From a quick search, the latest release is 3.1.1. Can you submit a patch to update a port, along with the maintainer change? Created attachment 225756 [details]
Patch (Revision 2)
Updates port to 3.1.1 along with maintainer change.
Did you test this update? I got: =======================<phase: patch >============================ ===> Patching for gophernicus-3.1.1 ===> Applying FreeBSD patches for gophernicus-3.1.1 from /usr/ports/www/gophernicus/files No file to patch. Skipping... 1 out of 1 hunks ignored--saving rejects to gophernicus.h.rej ===> FAILED Applying FreeBSD patch-gophernicus.h ===> FAILED to apply cleanly FreeBSD patch(es) patch-gophernicus.h *** Error code 1 Ping ;) I no longer wish to maintain Gophernicus, as I have shifted my software focus back to the Microsoft Windows OS family, and more useful/beneficial modern software and protocols. For these reasons, this bug is now closed. |
Created attachment 225751 [details] Patch (Revision 1)