devel/rubygem-hoe: update to 3.13.0
- Fix PLIST when NLS option is off
If either of OSVERSION or UNAME_r is improperly set when building in a
jail/chroot, a number of unexpected errors can occur.

  1. autotools fixup may not run when needed. This could be avoided by always
     running it [PR 177980, 177403].
  2. Not having UNAME_r set will cause many unknown
     errors. Many ports use OSREL (derived from UNAME_r) to determine the name
     of files. This is usually also due to the port build itself using uname -r
     to derive filenames or 'built for' messages. [PR 192449, 191943] Without
     having these sanity checks it is very easy for users to get into
     situations where "everything worked" until they touch a certain port that
     reads uname(1) output or OSVERSION. It has always been necessary to define
     all of the UNAME_ vars and OSVERSION (or have a proper sys/param.h
     present), but many users do not know this.

Remove the fallback on the kernel for kern.osreldate as it easily gets the
answer wrong.

I have added sanity checks to ensure OSVERSION==OSREL==UNAME_r as these are the
most critical vars to have set properly.

Differential Revision:	https://reviews.freebsd.org/D869
PR:			177980, 177403, 192449, 191943
Reviewed by:		antoine, bapt, gjb
With hat:		portmgr
textproc/rubygem-sanitize: update to 3.0.2
net/rubygem-octokit: update to 3.4.0
- Fix PKGNAME collision
Update from 1.7.5 to 1.7.6.

<ChangeLog>

*) Change: the deprecated "limit_zone" directive is not supported
   anymore.

*) Feature: the "limit_conn_zone" and "limit_req_zone" directives now
   can be used with combinations of multiple variables.

*) Bugfix: request body might be transmitted incorrectly when retrying a
   FastCGI request to the next upstream server.

*) Bugfix: in logging to syslog.

</ChangeLog>