"mongrel_rails --version" reporting 1.1.2 instead of 1.1.3

FYI.

  • Brian G.

http://opensolaris.org/os/project/nycosug/

On Dec 31, 2007 8:43 PM, Brian G. [email protected] wrote:

FYI.

From your signature I guess is OpenSolaris.

  • Did you install it from rubygems or downloaded the tgz package?

The http11 set the platform correctly, so I honestly don’t know why
are you getting it (the tgz, the mongrel-1.1.1.gem and the
mongrel-1.1.3-i386-mswin32.gem display it correctly).

Could I just answer to this: “Works for me”? :smiley:

Happy New Year!


Luis L.
Multimedia systems

A common mistake that people make when trying to design
something completely foolproof is to underestimate
the ingenuity of complete fools.
Douglas Adams

I can reproduce. Can you file a ticket?

Evan

Rubygems… The “gem list” command show the updated version number
(1.1.3), but “mongrel_rails --version” shows 1.1.2, which was never
isntalled on my system.

-Brian

On Dec 31, 2007 10:35 PM, Luis L. [email protected] wrote:

mongrel-1.1.3-i386-mswin32.gem display it correctly).
something completely foolproof is to underestimate
the ingenuity of complete fools.
Douglas Adams


Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users

  • Brian G.

http://opensolaris.org/os/project/nycosug/

On Jan 1, 2008 4:50 AM, Evan W. [email protected] wrote:

I can reproduce. Can you file a ticket?

Then that means rubyforge picked the older file before we replaced
with the correct one.

That means Tom C. is lying! :wink:
(about how gems the replicated into the mirrors) :slight_smile:

Maybe we should fill a ticket on Rubyforge support?


Luis L.
Multimedia systems

A common mistake that people make when trying to design
something completely foolproof is to underestimate
the ingenuity of complete fools.
Douglas Adams

On Jan 2, 2008 2:34 AM, Evan W. [email protected] wrote:

I think someone (you?) forgot to commit the version change.

Damn, I did it, but as you said, forgot the commit (maybe is in my WC
at office).

I had to re-release the gem to fix the daemons dependency problem (due to the
FORCE_PURE thing you added, which I committed a fix for).

Please excuse Evan this took you time away from your life (since is
January 1st of a new year!).

I think part of the problem was the urgent need to release a new
version with the proper fix, neglecting things like that.

For what matters, we could alter the extconf.rb to use a define and
get the proper version build inside the http11 extension.

Currently I’m doing something like that for mongrel_service.

Either that or somehow I accidentally reversed your change. I’ll patch
things up regardless.

Again, thank you Evan.

Have a nice week and talk soon.


Luis L.
Multimedia systems

A common mistake that people make when trying to design
something completely foolproof is to underestimate
the ingenuity of complete fools.
Douglas Adams

Not necessarily…

mongrel/branches/stable_1-1 eweaver$ ack 1.1.2
ext/http11_java/org/jruby/mongrel/Http11.java
218:
req.aset(runtime.newString(“SERVER_SOFTWARE”),runtime.newString(“Mongrel
1.1.2”));

lib/mongrel/const.rb
68: MONGREL_VERSION=“1.1.2”.freeze

I think someone (you?) forgot to commit the version change. I had to
re-release the gem to fix the daemons dependency problem (due to the
FORCE_PURE thing you added, which I committed a fix for).

Either that or somehow I accidentally reversed your change. I’ll patch
things up regardless.

Evan

Either way, if someone can figure out why the C/Java extensions
don’t/can’t refer to the same constant in the first place, that would
be sweet. I haven’t had time to investigate that in detail.

Evan

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs