The following reply was made to PR ports/152214; it has been noted by GNATS.
From: Eric
To:
Cc:
Subject: Re: ports/152214: [PATCH] update devel/rubygem-holidays 0.9.3 ->
1.0.0
Date: Sat, 13 Nov 2010 21:56:56 +
Approve my own update.
Must be more careful with email addresses
The following reply was made to PR ports/153144; it has been noted by GNATS.
From: Eric
To:
Cc:
Subject: Re: ports/153144: [PATCH] update mail/rubygem-mail to the recent
version
Date: Tue, 14 Dec 2010 23:07:47 +
Rejected.
Sorry it's already on version 2.2.12, thanks for the PR t
The following reply was made to PR ports/155232; it has been noted by GNATS.
From: Eric
To:
Cc:
Subject: Re: ports/155232: [Update]mail/rubygem-mail: Update to 2.2.15
Date: Thu, 03 Mar 2011 18:58:18 +
Rejected. Sorry.
There is already a pending PR (ports/154938) to upgrade to 2.2.15
ding somewhere that
release was planned for May(ish).
Regards
Eric
___
freebsd-ruby@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ruby
To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
on as almost the default tool for doing upgrades of ports then it
does seem sensible that we should all try our best to fix it.
I personally think we should still aim to get to the default of 1.9 and
aiming for the 9.0 release seems a sensible target to go for, if part of
that proces
ht try to have a proper bash at it over the weekend.
That said however a superficial glance at ports/144605 and the portupgrade
sources affected by it would seem to indicate that portupgrade is already
fixed as per that PR (although not with that actual patch applied) and that
PR is redundant.
Eric
___
/install -c -o root -g wheel -m 0755 bdb.so
/usr/local/lib/ruby/gems/1.9/gems/bdb-0.0.2/lib
I'm afraid I'm getting to the slightly randomly prodding stuff stage - I'm
not a big C person (*the shame* - I know)
Sorry not much of use I know, anyone a bit more knowledgeable got some
ide
not building with 1.9':
http://chillibear.com/freebsd/ruby19-notbuilding.html
For those dependent on one of the others:
http://chillibear.com/freebsd/ruby19-dependent.html
Hopefully that might save a few minutes searching thorough the various port
information sources. I
ectic!
My thanks to both you and Knu for all the effort on this.
> On 03/20/11 13:27, Eric wrote:
>> [SNIP]
>>
>>>> Portupgrade is a bit of a problem. Perhaps it's due to my patches, but
>>>> at the moment I can't get databases/ruby-bdb to build wi
The following reply was made to PR ports/156672; it has been noted by GNATS.
From: Eric
To:
Cc:
Subject: Re: ports/156672: [NEW PORT] devel/rubygem-state_machine (state
machine funcitonality for ruby classes)
Date: Wed, 27 Apr 2011 15:12:36 +0100
My apologies for the cut and paste mess
ure release.
That said we'd want to make sure it was fairly trivial for a user to revert
to a 1.8 install since it's still a popular version.
Also I do keep meaning to test your 1.9 patch and try it out when I get some
time! Promise!
Regards
Eric
've
done it.
> I am not used with Ruby gems packaging, and I would like to be sure that
> this is a problem that should be signaled upstream before acting: is it?
I've never looked at the Gem internals to see how it determines file
permissions of those files it installs, but g
> From: Steve Wills
>
>> Steve Wills schrieb:,
>>
>>> If you'd like to try to fix things, the possibly incomplete and/or
>>> inaccurate list of ports that don't work with 1.9 is:
>>
>> I can't figure out how to add patches to a gem distribution
>> so i can be build under FreeBSD ports again.
>>
I did that when solving this PR: ports/147809, also see
ports/150775 for the actual 'second' gem port.
Regards
Eric
___
freebsd-ruby@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ruby
To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
The following reply was made to PR ports/162000; it has been noted by GNATS.
From: Eric
To:
Cc:
Subject: Re: ports/162000: [PATCH] textproc/rubygem-sanitize: update to 2.0.3
Date: Sat, 12 Nov 2011 13:36:05 +
Approved. Thank you for the patch
The following reply was made to PR ports/167115; it has been noted by GNATS.
From: Eric
To:
Cc:
Subject: Re: ports/167115: [PATCH] net/rubygem-whois: update to 2.5.0
Date: Fri, 20 Apr 2012 11:36:32 +0100
Approved, thank you for the patch
The following reply was made to PR ports/169087; it has been noted by GNATS.
From: Eric
To:
Cc:
Subject: Re: ports/169087: [PATCH] net/rubygem-whois: update to 2.6.2
Date: Fri, 22 Jun 2012 21:54:27 +0100
Rejected. Port is currently on 2.6.1 not 2.5.0.
I'll send a PR in myself to u
>> On 01/05/13 20:58, Olli Hauer wrote:
>> It seems there are new releases for ruby because an security issue
>> CVE-2012-5664
>>
> The issue is in Ruby On Rails, not Ruby itself. There's an update to
> Ruby 1.9, but it's not a security issue. I'll see what I can do about
> the Rails update first,
The following reply was made to PR ports/156630; it has been noted by GNATS.
From: Eric Freeman
To:
Cc:
Subject: Re: ports/156630: [NEW PORT] devel/rubygem-terminal-table: Simple,
feature rich ascii table generation library
Date: Mon, 25 Apr 2011 06:46:01 +0100
FYI this appears to be be
19 matches
Mail list logo
