Summary: | security/rubygem-bcrypt: Update to 3.1.13 | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Sir l33tname <sirl33tname> | ||||
Component: | Individual Port(s) | Assignee: | Koichiro Iwao <meta> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | CC: | meta | ||||
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(ruby) meta: merge-quarterly- |
||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
See Also: | https://github.com/codahale/bcrypt-ruby/pull/189 | ||||||
Attachments: |
|
Description
Sir l33tname
2019-06-05 06:23:24 UTC
I think whichever merging quarterly or not is OK. The current 3.1.12 also builds on >= 12 with patches. 3.1.13 can remove these patches. A commit references this bug: Author: meta Date: Thu Jun 6 01:04:23 UTC 2019 New revision: 503556 URL: https://svnweb.freebsd.org/changeset/ports/503556 Log: security/rubygem-bcrypt: Update to 3.1.13 This version build on FreeBSD >= 12 again without patches. PR: 238332 Submitted by: Sir l33tname <sirl33tname@gmail.com> Changes: head/security/rubygem-bcrypt/Makefile head/security/rubygem-bcrypt/distinfo head/security/rubygem-bcrypt/files/ (In reply to Koichiro Iwao from comment #1) Does the quarterly version build (in its current state)? If so, this doesn't need to be merged (set merge-quarterly flag to -, with comment) If not, please MFH, set merge-quarterly flag to + (when merged) and resolve/close at your convenience (In reply to Kubilay Kocak from comment #3) quarterly branch builds. Closing. |