I've trying to look at this bug. https://bugzilla.redhat.com/show_bug.cgi?id=572722
I think an option is simply to create a rails2.3 package. I realize this probably less than ideal, but the only real solution I see for the problem. Thoughts?
Mike
Michael Stahnke wrote, at 05/20/2010 03:54 AM +9:00:
I've trying to look at this bug. https://bugzilla.redhat.com/show_bug.cgi?id=572722
I think an option is simply to create a rails2.3 package. I realize this probably less than ideal, but the only real solution I see for the problem. Thoughts?
Mike
Well, I don't oppose to making parallel-installable rails 2.3.x related packages on EPEL itself.
However I don't know if EPEL's policy allows such decision like "We made rails 2.3.x packages so please use them. Althogh rails 2.1.x is still shipped on EPEL5, well, WONTFIX" (note that I don't know EPEL's policy well). I guess even if rails 2.3.x packages are imported into EPEL5, if bug 572722 is due to bug in rails 2.1.x it should be fixed anyway and so the cause of bug 572722 should be investigated anyway.
Regards, Mamoru
Mamoru Tasaka wrote:
Michael Stahnke wrote, at 05/20/2010 03:54 AM +9:00:
I've trying to look at this bug. https://bugzilla.redhat.com/show_bug.cgi?id=572722
I think an option is simply to create a rails2.3 package. I realize this probably less than ideal, but the only real solution I see for the problem. Thoughts?
Mike
Well, I don't oppose to making parallel-installable rails 2.3.x related packages on EPEL itself.
However I don't know if EPEL's policy allows such decision like "We made rails 2.3.x packages so please use them. Althogh rails 2.1.x is still
shipped
on EPEL5, well, WONTFIX" (note that I don't know EPEL's policy well). I guess even if rails 2.3.x packages are imported into EPEL5, if bug 572722 is due to bug in rails 2.1.x it should be fixed anyway and so the cause of bug 572722 should be investigated anyway.
I've tried to determine what the actual cause is here, and it seems that the connection pooling in activerecord in 2.1.x is fubar. Can somebody confirm that for me please?
I've tried making the puppet master explicitly give up the connection (disconnect) but that wouldn't fly; it'd result in "MySQL::Error - the mysql server went away" type of errors.
-- Jeroen
I started making rails23 packages (and all the deps) but then ran into a question. If rubygems natively lets you install multiple gem versions, should we allow that with RPMS? The only conflicts are in the /usr/bin directory and those normally contains ruby scripts to help find the proper gem version. Originally I was making rails and rack conflict with the older versions (these are rubygem-rails23 and rubygem-rack1), but I am not certain that is the best approach?
Thoughts?
I have my work thus far up on my fedora people. Keep in mind that this will be for EPEL5 only, as RHEL6 has rails. I'm open to any feedback before I submit reviews.
http://stahnma.fedorapeople.org/newrails/
stahnma
ruby-sig@lists.fedoraproject.org
-
Jeroen van Meeuwen -
Mamoru Tasaka -
Michael Stahnke