[ANN] RubyInstaller 2.0.0-p0 released

5,367 views
Skip to first unread message

Luis Lavena

unread,
Feb 24, 2013, 4:24:46 PM2/24/13
to rubyin...@googlegroups.com, Ruby Talk
In combination with the rest of the RubyInstaller team, I'm very
pleased to announce the release of RubyInstaller packages for Ruby
2.0.0-p0

This new version of Ruby also brings new changes to RubyInstaller.

Starting with 2.0.0, the packages will be provided in two versions:
32bits (x86) and 64bits (x64).

This is possible thanks to newer compiler provided by mingw-w64 project.

Over the past months our Continous Integration worker has been compiling and
running tests against GCC 4.7.2, ensuring this version satisfy the compilation
requirements of Ruby.

This also means newer DevKit package is required to use with this version.

As usual, installer and 7z packages are available at RubyInstaller
website and RubyForge for download:

http://rubyinstaller.org/downloads
http://rubyforge.org/frs/?group_id=167&release_id=47158

For verification, MD5 signatures of each file released are provided:

db47fc5837be2623d5f37dc3ef32ce4f *ruby-2.0.0-p0-doc-chm.7z
cc3d1262c3e80ddb72942966a5119dc4 *ruby-2.0.0-p0-i386-mingw32.7z
fd54283746ba0161aa06af6c2c886abf *ruby-2.0.0-p0-x64-mingw32.7z
ccdf7de8b77c29aea4254c409a40fe98 *rubyinstaller-2.0.0-p0.exe
5a6a605d3e38e2cb572dd418152a2fed *rubyinstaller-2.0.0-p0-x64.exe

Installer is also digitally signed to avoid alterations and UAC warnings.

You can read Ruby's own announcement here:

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/404900

= What's new in Ruby, for Windows users?

Ruby's announcement was generic in relation to all the new features added to
the language.

However, it missed enhancements specific to our platform of choice.

* Enhancements:
* Faster startup due improved Windows-specific API. [Bug #6836]
* Support ANSI-colors out of the box without the need of external tools
or gems. [Feature #6418]
* Fixes for native 64bits builds for Windows under MinGW

= What's new in RubyInstaller?

Beyond what is covered by Ruby itself, we have our own set of improvements:

* Enhancements:
* Upgraded Ruby 2.0.0 to patchlevel 0
* Upgraded OpenSSL to version 1.0.0k
* Upgraded rb-readline to 0.5.0.pre.1 (compatible with Ruby 2.0)

* Bugfixes:
* Generate documentation for target version of Ruby

= Important Notes

* Ruby 2.0.0-p0 is brand new

While officially 2.0.0 is stable, that doesn't mean all the software will
magically work on it.

Use 2.0.0 for development and verify your application, scripts and tools works
properly before deciding to run this in your production environment.

* Existing pre-compiled gems are not Ruby 2.0 compatible

Ruby 2.0 introduces ABI breakage which means compiled C extensions with previous
1.9.3 will work with Ruby 2.0.

DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3, or try to use compiled
extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies required for that gem to
compile. Look at the gem documentation for the requirements.

* Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of older version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

= Alternate download links

Sometimes RubyForge might have issues when trying to download the above files.

Please try adding "/noredirect" to the file download URLs so skip the entire
RubyForge's mirror functionality.

If that still doesn't work, try using RubyInstaller CDN directly by using
above filenames combined with the archive folder:

http://cdn.rubyinstaller.org/archives/2.0.0-p0/<filename.ext>

Same applies to DevKit URLs:

http://cdn.rubyinstaller.org/archives/devkits/<filename.ext>

--
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry

Roy Pardee

unread,
Feb 24, 2013, 4:53:57 PM2/24/13
to rubyinstaller, Ruby Talk
Holy cow that was fast!  Thanks so much!

Dušan D. Majkić

unread,
Feb 24, 2013, 5:07:29 PM2/24/13
to rubyin...@googlegroups.com
> pleased to announce the release of RubyInstaller
> packages for Ruby 2.0.0-p0

Excellent! Thank you.

Luis Lavena

unread,
Feb 24, 2013, 5:07:33 PM2/24/13
to rubyin...@googlegroups.com, Ruby Talk
On Sun, Feb 24, 2013 at 7:05 PM, Tim0 <tig...@gmail.com> wrote:
>
>> >{....
>>
>> * Existing pre-compiled gems are not Ruby 2.0 compatible
>>
>> Ruby 2.0 introduces ABI breakage which means compiled C extensions with
>> previous 1.9.3 will work with Ruby 2.0.
>>
>> DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3, or try to use
>> compiled
>> extensions with it. ..}
>
>
>
> Hi Luis
> Congratulations for the long-awaited Ruby 2.0 p0 exe
> may i just ask
> when i read '..gems will not work' and next sentence
> compiled C extensions '1.9.3 will work'
>
> is the word 'not' missing in the latter sentence?
>

Yes, that is a typo, but I think last sentence make it clear:

DO NOT install Ruby 2.0.0 on top of existing Ruby 1.9.3 or try to use
compiled extensions with it.

Richard Campbell

unread,
Feb 24, 2013, 5:09:54 PM2/24/13
to rubyin...@googlegroups.com, Ruby Talk
Just an FYI for anyone with issues with sqlite3, i installed it by extracting both the source and DLL/DEF (from the sqlite3 website) to C:\tmp and then i ran:

gem install sqlite3 -- --with-sqlite3-include=C:/tmp --with-sqlite3-lib=C:/tmp --platform=ruby

Thanks,
Rich

On Sunday, February 24, 2013 4:58:04 PM UTC-5, Richard Campbell wrote:
Awesome!  Great work!  Though I am already having issues with the 64 bit version and sqlite3.

Luis Lavena

unread,
Feb 24, 2013, 5:11:24 PM2/24/13
to rubyin...@googlegroups.com, Ruby Talk
On Sun, Feb 24, 2013 at 6:58 PM, Richard Campbell <bet...@gmail.com> wrote:
> Awesome! Great work! Though I am already having issues with the 64 bit
> version and sqlite3.
>

sqlite3 gem?

As indicated in the "Important Notes", existing pre-compiled gems will
not work with Ruby 2.0 as the gems do not contain pre-compiled
extension for it.

You need to force compilation, which requires you install development
headers and libraries that are dependencies of the gem/extension
you're trying to compile.

So: to compile sqlite3 for Ruby 2.0, you need:

* sqlite3 headers and libraries compiled and available
* force installation of sqlite3 to use "ruby" platform (as indicated
in the notes) and provide the directory where it will find sqlite3
headers and libraries.

For sqlite3 will be something like

gem install sqlite3 --platform=ruby --
--with-sqlite3-include=C:/path/to/sqlite3/include
--with-sqlite3-lib=C:/path/to/sqlite3/lib

See the documentation of each gem about that.

Karey Powell

unread,
Feb 24, 2013, 5:06:38 PM2/24/13
to rubyin...@googlegroups.com
Really awesome works guys! I was just on the site today looking at all the things that are used to make the Ruby setup on Windows painless, especially the GCC compiler in the DevKit. I was pondering why the 3.x version was being used as opposed to the 4.x version, but to my surprise on the release of Ruby 2.0 the RubyInstaller was updated for that as well in, basically no time at all. I am reading the docs and paying attention to the things being improved on and those that are in the process, because I want to jump in and contribute to this as well.

On Sun, Feb 24, 2013 at 4:53 PM, Roy Pardee <rpa...@gmail.com> wrote:
Holy cow that was fast!  Thanks so much!

--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyinstalle...@googlegroups.com.
To post to this group, send email to rubyin...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyinstaller?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--

Mr. Karey H. Powell
Software Engineer & Consultant

Skype: k_cipher_p

Karey Powell

unread,
Feb 24, 2013, 6:18:31 PM2/24/13
to rubyin...@googlegroups.com
Does anybody here have a problem running the 'bundle install' command for your Rails apps?

I am currently getting this error:

Unfortunately, a fatal error has occurred. Please see the Bundler troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
C:/Ruby200-x64/lib/ruby/2.0.0/net/http.rb:917:in `connect': SSL_connect returned
=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (OpenSSL::SSL::SSLError)

An issue has been opened and one of the comment stated that it may be a result of the _ruby-build_

--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyinstalle...@googlegroups.com.
To post to this group, send email to rubyin...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyinstaller?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Luis Lavena

unread,
Feb 24, 2013, 6:25:38 PM2/24/13
to rubyin...@googlegroups.com
On Sun, Feb 24, 2013 at 8:18 PM, Karey Powell <karey...@gmail.com> wrote:
> Does anybody here have a problem running the 'bundle install' command for
> your Rails apps?
>

Please note that "bundle install" will attempt to install binary gems
that are not compatible with Ruby 2.0, see the "Important notes" on
the announcement.

> I am currently getting this error:
>
> Unfortunately, a fatal error has occurred. Please see the Bundler
> troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
> C:/Ruby200-x64/lib/ruby/2.0.0/net/http.rb:917:in `connect': SSL_connect
> returned
> =1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
> (OpenSSL::SSL::SSLError)
>

An OpenSSL error might indicate issues connecting with RubyGems.

Can you confirm your Gemfile uses "https://rubygems.org" as source.

RubyGems bundled in RubyInstaller (2.0.0) already contains the
required certificates to successfully install gems.

I tested this before making the release.

Can you install any other gem manually?

gem install gem-exefy --source "https://rubygems.org" --debug -V

Let's see where the error is coming from.

Thank you.

Karey Powell

unread,
Feb 24, 2013, 6:40:20 PM2/24/13
to rubyin...@googlegroups.com
Yes I'm able to install other gems manually.

--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyinstalle...@googlegroups.com.
To post to this group, send email to rubyin...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyinstaller?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Luis Lavena

unread,
Feb 24, 2013, 6:41:48 PM2/24/13
to rubyin...@googlegroups.com
On Sun, Feb 24, 2013 at 8:40 PM, Karey Powell <karey...@gmail.com> wrote:
> Yes I'm able to install other gems manually.
>

Without more details on how your Gemfile looks like or more contextual
information on where it is failing during the installation, there
isn't much else I can do.

You copied just the error message and give us no context about it.

If you're kind enough to fill the gaps on the above points, perhaps we
could replicate the issue or determine where is the problem.

Karey Powell

unread,
Feb 24, 2013, 6:48:27 PM2/24/13
to rubyin...@googlegroups.com
This is how my Gemfile looks:


gem 'rails', '3.2.12'
gem 'pg'

# Gems used only for assets and not required
# in production environments by default.
group :assets do
  gem 'sass-rails',   '~> 3.2.3'
  gem 'coffee-rails', '~> 3.2.1'

  gem 'uglifier', '>= 1.0.3'
end

gem 'jquery-rails'
gem 'paperclip'

group :development do
gem 'annotate', '2.5.0'
end

==========================================================

This is the full context of the error I get when I run the 'bundle install' command:

Unfortunately, a fatal error has occurred. Please see the Bundler
troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
C:/Ruby200-x64/lib/ruby/2.0.0/net/http.rb:917:in `connect': SSL_connect returned
=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (Ope
nSSL::SSL::SSLError)
        from C:/Ruby200-x64/lib/ruby/2.0.0/net/http.rb:917:in `block in connect'

        from C:/Ruby200-x64/lib/ruby/2.0.0/timeout.rb:51:in `timeout'
        from C:/Ruby200-x64/lib/ruby/2.0.0/net/http.rb:917:in `connect'
        from C:/Ruby200-x64/lib/ruby/2.0.0/net/http.rb:861:in `do_start'
        from C:/Ruby200-x64/lib/ruby/2.0.0/net/http.rb:856:in `start'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/vendor/net/http/persistent.rb:628:in `start'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/vendor/net/http/persistent.rb:570:in `connection_for'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/vendor/net/http/persistent.rb:930:in `request'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/fetcher.rb:169:in `fetch'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/fetcher.rb:151:in `use_api'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/source/rubygems.rb:223:in `block in remote_specs'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/source/rubygems.rb:223:in `select'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/source/rubygems.rb:223:in `remote_specs'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/source/rubygems.rb:162:in `fetch_specs'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/source/rubygems.rb:66:in `specs'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/lazy_specification.rb:52:in `__materialize__'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/spec_set.rb:86:in `block in materialize'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/spec_set.rb:83:in `map!'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/spec_set.rb:83:in `materialize'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/definition.rb:114:in `specs'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/definition.rb:109:in `resolve_remotely!'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/installer.rb:83:in `run'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/installer.rb:14:in `install'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/cli.rb:247:in `install'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/vendor/thor/task.rb:27:in `run'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/vendor/thor/invocation.rb:120:in `invoke_task'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/vendor/thor.rb:344:in `dispatch'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/vendor/thor/base.rb:434:in `start'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/bin/bun
dle:20:in `block in <top (required)>'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/lib/bun
dler/friendly_errors.rb:4:in `with_friendly_errors'
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/bundler-1.3.0.pre.8/bin/bun
dle:20:in `<top (required)>'
        from C:/Ruby200-x64/bin/bundle:23:in `load'
        from C:/Ruby200-x64/bin/bundle:23:in `<main>'


--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyinstalle...@googlegroups.com.
To post to this group, send email to rubyin...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyinstaller?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Karey Powell

unread,
Feb 24, 2013, 6:59:10 PM2/24/13
to rubyin...@googlegroups.com
This might also be of some help, https://github.com/sstephenson/ruby-build/issues/307. It is the same error encountered by OSX users, they fixed it by renaming cacert.pem to cert.pem.

Luis Lavena

unread,
Feb 24, 2013, 7:04:38 PM2/24/13
to rubyin...@googlegroups.com
On Sun, Feb 24, 2013 at 8:48 PM, Karey Powell <karey...@gmail.com> wrote:
> This is how my Gemfile looks:
>
> source 'https://rubygems.org'
>
> gem 'rails', '3.2.12'
> gem 'pg'
>

Please note that you will require postgresql development headers and
libraries for "pg" gem to work under Ruby x64

>
> ==========================================================
>
> This is the full context of the error I get when I run the 'bundle install'
> command:
>
> Unfortunately, a fatal error has occurred. Please see the Bundler
> troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
> C:/Ruby200-x64/lib/ruby/2.0.0/net/http.rb:917:in `connect': SSL_connect
> returned
> =1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
> (Ope
> nSSL::SSL::SSLError)
> from C:/Ruby200-x64/lib/ruby/2.0.0/net/http.rb:917:in `block in
> connect'
>
>

Are you certain this is the full output after you hit enter to "bundle
install" command?

I just commented out "pg" gem and is installing with issues:

https://gist.github.com/luislavena/5026351

Please note that reports about ruby-build have nothing to do with
RubyInstaller, Ruby or Bundler itself.

From the error message:

SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B:
certificate verify failed (OpenSSL::SSL::SSLError)

It seems there are issues connecting from your current location to a
secure RubyGems server mirror.

Luis Lavena

unread,
Feb 24, 2013, 7:06:54 PM2/24/13
to rubyin...@googlegroups.com
On Sun, Feb 24, 2013 at 9:04 PM, Luis Lavena <luisl...@gmail.com> wrote:
>
> Please note that reports about ruby-build have nothing to do with
> RubyInstaller, Ruby or Bundler itself.
>
> From the error message:
>
> SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B:
> certificate verify failed (OpenSSL::SSL::SSLError)
>
> It seems there are issues connecting from your current location to a
> secure RubyGems server mirror.
>

Some other folks are getting the same thing on different platforms. It
could be rubygems servers are a bit saturated and SSL is timing out.

Karey Powell

unread,
Feb 24, 2013, 7:30:32 PM2/24/13
to rubyin...@googlegroups.com
I am sure that is the full output of the error that returned after running the command. Also, I tried it again following what you did, commented out the 'pg' gem and the issue still persist, the connection keeps timing out. I am going to try another test project with the 1.9.3-p392 and see if I get the said issue. Note, it worked on 1.9.3-p392 before, so if it doesn't now, then it might be a result of connecting to RubyGems server as you previously stated.

--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyinstalle...@googlegroups.com.
To post to this group, send email to rubyin...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyinstaller?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Karey Powell

unread,
Feb 24, 2013, 8:06:19 PM2/24/13
to rubyin...@googlegroups.com
Luis,

I tried it on a next computer with version 1.9.3-p392 and it worked. What I did noticed though is that the 'bundle install' command doesn't work for me using the bundler 1.3.0.pre.8 version gem, which is the version I was previously running for Ruby 2.0 and getting that error. However, I reverted to bundler v1.2.4 gem and Ruby 1.9.3-p392.

Luis Lavena

unread,
Feb 24, 2013, 8:08:05 PM2/24/13
to rubyin...@googlegroups.com
On Sun, Feb 24, 2013 at 10:06 PM, Karey Powell <karey...@gmail.com> wrote:
> Luis,
>
> I tried it on a next computer with version 1.9.3-p392 and it worked. What I
> did noticed though is that the 'bundle install' command doesn't work for me
> using the bundler 1.3.0.pre.8 version gem, which is the version I was
> previously running for Ruby 2.0 and getting that error. However, I reverted
> to bundler v1.2.4 gem and Ruby 1.9.3-p392.
>

So you're saying that bundler 1.3.0.pre.8 is not working even on 1.9.3-p392?

Can you try uninstall bundler and install 1.3.0.pre.7?

Just to determine if the issue is in latest prerelease.

Karey Powell

unread,
Feb 24, 2013, 8:16:30 PM2/24/13
to rubyin...@googlegroups.com
I installed the bundler v1.3.0.pre.7 gem and it worked without any issues. It has no problem fetching and installing the gems. So, it looks like the problem is with v1.3.0.pre.8 and not RubyGems servers after all.

--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyinstalle...@googlegroups.com.
To post to this group, send email to rubyin...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyinstaller?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Luis Lavena

unread,
Feb 24, 2013, 8:19:30 PM2/24/13
to rubyin...@googlegroups.com
On Sun, Feb 24, 2013 at 10:16 PM, Karey Powell <karey...@gmail.com> wrote:
> I installed the bundler v1.3.0.pre.7 gem and it worked without any issues.
> It has no problem fetching and installing the gems. So, it looks like the
> problem is with v1.3.0.pre.8 and not RubyGems servers after all.
>

Can you please report this issue to Bundler?

Provide the Gemfile, the entire backtrace, the version of Ruby and RubyGems.

Thank you.
Reply all
Reply to author
Forward
0 new messages