1.0.2 release candidates

Server Mongrel
1

Hello Mongrels,

Release candidates for Mongrel 1.0.2 and its dependencies are now
available. Note that gems are now signed, so please add the Mongrel
public certificate via:

$ wget
http://rubyforge.org/frs/download.php/25325/mongrel-public_cert.pem
$ gem cert --add mongrel-public_cert.pem

Now you can verify and install the candidates via gem install:

$ sudo gem install mongrel --include-dependencies --source
http://mongrel.rubyforge.org/releases/ -P HighSecurity

Manual downloads are available from
http://mongrel.rubyforge.org/releases/ .

Please report problems on the Rubyforge tracker at
http://rubyforge.org/tracker/?group_id=1306 . We will finalize the
release in a week or two, barring unforeseen difficulties.

Thanks,

Evan, and the Mongrel Team

PS. If you really don’t care about authenticity, and don’t want to
install the public certificate, you can omit the ‘-P HighSecurity’
option in ‘gem install’.

2

great!

3

What’s the word on the changes?

4

The CHANGELOG message for Mongrel is just:

v1.0.2. Signed gem; various bugfixes and patches.

There should be no breaking changes. If you’re interested in a
specific bug, check the tracker and see what the resolution was.

The detailed SVN log up to and including 1.0.2 is at
http://mongrel.rubyforge.org/releases/Changelog .

Mongrel_cluster v1.0.3 includes Capistrano 2 recipes. That’s probably
the most significant new feature.

Evan

5

Hi all,

The candidates have been updated with some bugfixes. Please uninstall
and reinstall.

$ sudo gem install mongrel --include-dependencies --source
http://mongrel.rubyforge.org/releases/ -P HighSecurity

Evan

6

I ran into an issue with upgrading to mongrel 1.0.2. This was last
Friday, so this may be fixed now. The REMOTE_ADDR environment
variable comes across in IPv6 format now, instead of IPv4 (as in
1.0.1).

This caused some issues in a ruby library that didn’t know how to
handle IPv6 IPs. No huge deal, but thought I’d throw it out there…

Ed

7

Sounds like a bug; can you file a ticket? Ideally with a test?

Evan

8

Yeah, I can do that soon.