Bug 204609 - [MAINTAINER] security/govpn: Update to 4.2
Summary: [MAINTAINER] security/govpn: Update to 4.2
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: Jason Unovitch
URL:
Keywords: easy, patch, patch-ready
Depends on:
Blocks:
 
Reported: 2015-11-16 19:54 UTC by Sergey Matveev
Modified: 2015-11-22 01:51 UTC (History)
1 user (show)

See Also:


Attachments
Update patch from 4.1 -> 4.2 (771 bytes, patch)
2015-11-16 19:54 UTC, Sergey Matveev
koobs: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Matveev 2015-11-16 19:54:11 UTC
Created attachment 163208 [details]
Update patch from 4.1 -> 4.2

Update patch from 4.1 -> 4.2
Comment 1 commit-hook freebsd_committer 2015-11-22 01:42:01 UTC
A commit references this bug:

Author: junovitch
Date: Sun Nov 22 01:41:28 UTC 2015
New revision: 402211
URL: https://svnweb.freebsd.org/changeset/ports/402211

Log:
  security/govpn: update 4.1 -> 4.2

  Changes:
  - Fixed non-critical bug when server may fail if up-script is not executed
    successfully.

  PR:		204609
  Submitted by:	Sergey Matveev <stargrave@stargrave.org> (maintainer)

Changes:
  head/security/govpn/Makefile
  head/security/govpn/distinfo
Comment 2 Jason Unovitch freebsd_committer 2015-11-22 01:49:51 UTC
Sergey,
Thanks!  QA in the next PR submission would be super helpful but this was quick enough to check myself.

For the record:

portlint -ac:
looks fine.

poudriere build tests on:
9.3-RELEASE-p30      amd64
9.3-RELEASE-p30      i386
10.1-RELEASE-p24     amd64
10.1-RELEASE-p24     i386
10.2-RELEASE-p7      amd64
10.2-RELEASE-p7      i386
11.0-CURRENT r291120 amd64
11.0-CURRENT r291120 i386
Comment 3 Jason Unovitch freebsd_committer 2015-11-22 01:51:52 UTC
Also, a mention of big issues fixed from "https://github.com/stargrave/govpn/blob/develop/doc/news.texi" would be helpful as well so we can mention it in the Changes: portion of the commit message.  Thanks again!