Bug 206735
| Summary: | expire a number of Rails 4.1 ports | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Torsten Zühlsdorff <ports> | ||||
| Component: | Individual Port(s) | Assignee: | Kurt Jaeger <pi> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | CC: | pi, robak | ||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
A commit references this bug: Author: pi Date: Fri Jan 29 21:01:20 UTC 2016 New revision: 407495 URL: https://svnweb.freebsd.org/changeset/ports/407495 Log: databases/rubygem-activemodel41 databases/rubygem-activerecord41 databases/rubygem-after_commit_queue-rails41 databases/rubygem-paranoia-rails41 devel/rubygem-actionview41 devel/rubygem-activesupport41 devel/rubygem-coffee-rails41 devel/rubygem-jbuilder-rails41 devel/rubygem-omniauth_crowd-rails41 devel/rubygem-sprockets-rails-rails41 mail/rubygem-actionmailer41 textproc/rubygem-sass-rails4-rails41 www/rubygem-actionpack41 www/rubygem-railties41 www/rubygem-turbolinks-rails41 - DEPRECATE those ports in favor of Rails 4.2 PR: 206735 Submitted by: Torsten Zuehlsdorff <ports@toco-domains.de> Changes: head/databases/rubygem-activemodel41/Makefile head/databases/rubygem-activerecord41/Makefile head/databases/rubygem-after_commit_queue-rails41/Makefile head/databases/rubygem-paranoia-rails41/Makefile head/devel/rubygem-actionview41/Makefile head/devel/rubygem-activesupport41/Makefile head/devel/rubygem-coffee-rails41/Makefile head/devel/rubygem-jbuilder-rails41/Makefile head/devel/rubygem-omniauth_crowd-rails41/Makefile head/devel/rubygem-sprockets-rails-rails41/Makefile head/mail/rubygem-actionmailer41/Makefile head/textproc/rubygem-sass-rails4-rails41/Makefile head/www/rubygem-actionpack41/Makefile head/www/rubygem-railties41/Makefile head/www/rubygem-turbolinks-rails41/Makefile Pending removal on 1st of April. (In reply to Kurt Jaeger from comment #2) After committing the patch: is the PR still needed as reminder or will the ports be removed automatically? I'll need it to remember to remove the ports. Today is the day ;) Seems like this is already completed and there's no action on it for a while, so I'm closing this PR. |
Created attachment 166269 [details] patch to expire Rails 4.1 ports Hello, attached a patch to expire a number of Rails 4.1 ports. These ports where all introduced by my in order to support the work at the GitLab port. But GitLab recently switched to Rails 4.2 and no other port has a dependency to them. Therefore i expired the ports - the could be removed without any harm. Greetings, Torsten