[Bug 226278] www/gohugo: Update to 0.37
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Mar 1 13:20:53 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226278
Bug ID: 226278
Summary: www/gohugo: Update to 0.37
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: ben.lavery at hashbang0.com
Created attachment 191100
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=191100&action=edit
svn diff to upgrade to 0.37
gohugo has been updated to 0.37
(https://github.com/gohugoio/hugo/releases/tag/v0.37):
The attached svn diff brings this port up from 0.36.1 to 0.37
Change log:
- Add template func for TOML/JSON/YAML docs examples conversion. This is
mainly motivated by the needs of the Hugo docs site
- Refactor tests for JSON, YAML and TOML equivalency, add coverage
- Re-enable YAML data tests disabled
- Preserve color palette for PNG images
- Use Floyd-Steinberg dithering for PNGs
- Make ge, le etc. work with the Hugo Version number
- Update dependencies
- Update to Go 1.10 (!)
- Add WARNING for integer YAML keys
- Tune stringifyMapKeys
- Rename stringifyYAMLMapKeys to stringifyMapKeys
- Add benchmarks for stringifyYAMLMapKeys
- Add support for YAML array data files
- Account for array type data in data dir merge/override logic
- Add "target" and "rel" parameters to figure shortcode "image" property, not
"twitter:image:src"
- Continue GitInfo lookup on error
- Fix paginator URL for sections with URL in front matter
- Fix bug in Site.assembleSections method
- Update Blackfriday to fix footnote HTML5 validation error
- Fix YAML maps key type
- Remove ERROR on missing baseURL
Tested against amd64/i386 10.4-RELEASE, 11.1-RELEASE, 11.1-STABLE, and
12.0-CURRENT. Poudriere logs attached, and also found here for a limited time:
https://logs.bnix.club/gohugo-0.37_2018-03-01/
portlint -AC:
looks fine.
poudriere bulk -tC:
10_4-RELEASE__amd64: success
10_4-RELEASE__i386: success
11_1-RELEASE__amd64: success
11_1-RELEASE__i386: couldn't get jail to start...
11_1-STABLE__amd64: success
11_1-STABLE__i386: success
12_0-CURRENT__amd64: success
12_0-CURRENT__i386: success
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list