[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Rails 3.2 sessions broken with Rack 1.5



On Thu, Jun 06, 2013 at 04:28:23PM -0400, Sam Ruby wrote:
> On 06/05/2013 11:50 AM, Antonio Terceiro wrote:
> >
> >I will be happy to replace my very simple Rails test which yours. Is
> >there a way to run those tests without installing anything, so that I
> >can just do `apt-get install rails` and then run the tests? I couldn't
> >figure this out from a quick read at the README.
> 
> I'm now at the point where you should be able to reproduce my
> results. See the attached testrails.sh for instructions.

That's awesome - I have just run the whole thing on a clean chroot here!

The only missing part in the script was installing git, but that should
be an issue in the CI environment since git would be a prerequisite for
pulling the test repository in the first place.

I have no plans to support rvm at all. Can we drop rvm-capistrano there?

The TODO list for getting your tests running on a pure-Debian system
look quite encouraging:

- get jquery-ui-rails packaged
- get gorp packaged
- fix the rack issue

I saw you are already working on the rack issue, thanks a lot. Do you
want to tackle the packaging too? :-)

> I've also attached the consolidated output from the run as
> checkdepot.html.  A quick spot check of the output indicates that
> many (if not all) of the errors are covered by bug 709431[1].

Cool.

> Along the way I encountered two other problems that I merely
> captured and moved on.  Now that I have completed the first-pass at
> this, please let me know the best way to report these problems.
> 
> The first problem is that an install of ruby-bcrypt doesn't make the
> bcrypt-ruby gem available.  See bcrypt.log.

Cédric already pushed a fix for this (thanks Cédric!).

> The second problem is that mysql-server-5.5 isn't installable using
> the default configuration.  See mysql.log.

What you mean with default configuration? I tried installing
mysql-server-5.5 (5.5.31-1) on a clean chroot twice (one time setting
the DB root password, and the other not doing it), and both times it
worked for me.

You may want to review the existing bugs at
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=mysql-server-5.5;dist=unstable
and see if any of those matches your problem, if not you might want to
report a new one.

So all those tests were run against sqlite3 only, right?

-- 
Antonio Terceiro <terceiro@debian.org>

Attachment: signature.asc
Description: Digital signature


Reply to: