Summary: | [PATCH] devel/rubygem-concurrent-ruby: update to 1.0.0 | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Po-Chuan Hsieh <sunpoet> | ||||
Component: | Individual Port(s) | Assignee: | Michael Moll <mmoll> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | Keywords: | patch | ||||
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(mmoll) |
||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Po-Chuan Hsieh
2015-11-28 13:17:10 UTC
Thank you, I opened https://github.com/Dynflow/dynflow/issues/175 for the dynflow guys to check. No other ports depend on concurrent-ruby at the moment (I think the dependency of sysutils/rubygem-smart_proxy_dynflow is only over dynflow, not directly). FYI, there are 2 upcoming updates require concurrent-ruby 1.0.0: - devel/rubygem-sidekiq 4.0.1 - devel/rubygem-sprockets3 3.5.0 A commit references this bug: Author: mmoll Date: Fri Dec 4 15:43:11 UTC 2015 New revision: 402995 URL: https://svnweb.freebsd.org/changeset/ports/402995 Log: devel/rubygem-concurrent-ruby: update to 1.0.0 PR: 204874 Submitted by: sunpoet Changes: head/devel/rubygem-concurrent-ruby/Makefile head/devel/rubygem-concurrent-ruby/distinfo committed, thanks! |