Re: Bug#547658: Status regarding new Rails version packaging?
On 25/05/2010 18:34, Adam Majer wrote:
> On Thu, May 06, 2010 at 01:42:03PM -0500, Gunnar Wolf wrote:
>> Adam, the four blocker points you mentioned back in February
>> (libactivesupport-ruby, libactiverecord-ruby, libi18n-ruby1.8 and
>> libmemcache-client-ruby1.8) have all been taken care of; what is the
>> status regarding the upload of a 2.3.x Rails package?
>> I am not poking just to bother you - libgettext-ruby is now broken
>> with my Rails applications, and I was about to make an ITP and package
>> libgettext-rails-ruby - But it requires a 2.3.x Rails...
>> I see you have set up a public Git repository for packaging Rails. I
>> cloned it, but without a TODO, I don't know what should I start
>> tackling - Tell me any pressing points that are blocking a release,
>> and I will gladly work on them.
> Sorry, was AWOL from Debian for a while. I'm just catching up with the
> emails now.
> Rails 2.3.5 was uploaded last night. I'll update it to 2.3.8 and fix
> any problems with packaging that might emerge this week.
I successfully packaged redmine for rails 2.3.5, and it seems to run fine.
It's very nice to have it now, and i thank you for that.
However i have some remarks :
* /usr/share/doc/rails/README.Debian is outdated.
It mentions rails-app-debianize, which has disappeared.
* accordingly, some documentation about how to use rails would be nice.
in the case of redmine, i simply had to
ln -s /usr/share/rails-ruby1.8 vendor/rails
and removed previous links that's been setup by rails-app-debianize
* i can't run integration tests. It's been reported already , let's hope
it's been fixed in 2.3.8.
* Warning: Gem::Dependency#version_requirements= is deprecated is still
there. That scares people :)