svn commit: r464421 - head/security/rubygem-devise_pam_authenticatable2

[Sunpoet Po-Chuan Hsieh]

On Thu, Mar 15, 2018 at 7:09 AM, Joseph Mingrone <jrm at freebsd.org> wrote:

> Sunpoet Po-Chuan Hsieh <sunpoet at FreeBSD.org> writes:
>
> > Author: sunpoet
> > Date: Tue Mar 13 20:31:38 2018
> > New Revision: 464421
> > URL: https://svnweb.freebsd.org/changeset/ports/464421
>
> > Log:
> >   Update to 9.0.0
>
> >   - Add LICENSE_FILE
> >   - Update WWW
>
> >   Changes:    https://github.com/devkral/dev
> ise_pam_authenticatable2/commits/master
>
> This _again_ breaks net-im/mastodon.
>

Author: jrm
Date: Tue Mar 13 20:04:57 2018
New Revision: 464403

You just added that dependency to net-im/mastodon less than half an hour
before my commit.
That is, there wasn't any port depends on it when I checked the dependency.
I cannot predict that there will be a port depends on an older version when
I prepare the update.
Then I committed it (along with other updates) after the poudriere build
(of a bunch of updates) finished.


> security/rubygem-devise_pam_authenticatable2 was just added to the tree
> and the only port depending on it is net-im/mastodon.  The commit log
> even said "Add new Ruby Gem dependency ports for upcoming Mastodon
> v2.3.1".  Yet, you either did not care that the Gemfile required a
> version less than 9 or you did not bother to check.


I fetch the update list from portscout.
And I won't spend time to check why a port on that list was added to the
tree unless it has suffix for specific version or dependency.


> I asked you to either clarify how we should deal with these issues with
> rubygems or if you would refrain from making these types of breaking
> updates, but I was ignored.  Could you please clarify?
>
> I patched the Gemfile for net-im/mastodon.  Let's hope
> everything works fine with a version that the authors specifically
> block.
>
> Joseph
>
> P.S., I released net-im/mastodon to ports at .  Feel free to pick it up.
>