The attached fixes make RubyGems setup.rb complete succesfully...but there's a catch.During the install of the sources-0.0.1.gem, two odd things seem to be happening:- sources-0.0.1.gem is modified, and corrupted
- the files contained in the original uncorrupted gem do not appear to be written out
I committed a fix so Time.dup now works correctly. Give it
a spin.
-Tom
On Fri, 24 Mar 2006, Ola Bini defenestrated me:
> Easy fix for this one, add this method to RubyTime.java:
>
> /** rb_time_dup
> *
> */
> public IRubyObject dup() {
> return new_at(this.getMeta
I have a good fix for RubyTime dup. I will fix later today. I am
adding a bunch of unit tests.
-Tom
On Sat, 25 Mar 2006, Ola Bini defenestrated me:
> Hi.
>
> The initialize_copy-error comes from Time#dup not working correctly. My
> quickie-fix solves that. (add a dup-method with more or le
On 3/24/06, Nick Sieger <[EMAIL PROTECTED]> wrote:
On 3/24/06, Thomas E Enebo <[EMAIL PROTECTED]
> wrote:
Could time.at() be used to avoid all the extra sets? I think theyboth use seconds since Epoch. Unless it is timezone screwy?That would certainly simplify it if it works. I'll try that thi
This is great news! I am going to start preparing for a 0.8.3 release
for this coming week then.
-Tom
On Fri, 24 Mar 2006, David Corbin defenestrated me:
> As near as I can tell, HEAD now works as well as 082 does. I've got a couple
> of tests that are failing, but they're equal-opportunit
Hi.
The initialize_copy-error comes from Time#dup not working correctly. My
quickie-fix solves that. (add a dup-method with more or less the same
contents as RubyString)... as Thomas pointed out, this is not really so
great, since there are stuff that solution disregards, but it works for now.
/O
