ruby-rails is in the reposity, it's not the same ?

Keywords: (none) => Backport
CC: (none) => lev

Apparently, it is; since rails is a development framework, I imagine that it would be preferable to keep the package named ruby-rails (although the corresponding Mandriva package is named rails). Should I remove the rails package from svn?

Is it possible to modify the provides of the ruby-rails package to ensure a safe and painless upgrade from mandriva 2010.2 ?

I removed rails from svn, updated ruby-rails to 2.3.12 (the gem had apparently been updated, but the package had not been rebuilt for some reason), made ruby-rails-devel obsolete rails to facilitate upgrading from mdv 2010.2, and built the package for 1/core_updates.

Status: NEW => RESOLVED
Component: New RPM package request => All
Hardware: x86_64 => i586
Version: 1 => trunk
Resolution: (none) => FIXED
Product: Mageia => Websites
Target Milestone: --- => Mageia 1

Hey ! Have you really read the updates_policy ?

Status: RESOLVED => REOPENED
Version: trunk => 1
Keywords: Backport => (none)
Component: All => RPM Packages
Resolution: FIXED => (none)
Summary: Requests for backports : Rails => ruby-rails; wrong provide
Target Milestone: Mageia 1 => ---
Product: Websites => Mageia

Wrong.

Submitting rails alone only leads to broken dependencies.

Rails depends on at least 5 other packages:
ruby-activerecord
ruby-activesupport
ruby-activeresource
ruby-actionpack
ruby-actionmailer

If you donât upgrade these 5 gems, it wonât work.

Besides, many rails apps are tied to a particular version of rails. You cannot push a new rails without upgrading these apps or patch them so that they accept this particular version of rails. Thatâs the reason I didnât push these packages into cauldron, due to lack of time and internet connection I couldnât test these apps with the new rails.

Thatâs the case for chiliproject, redmine, teambox and mageia-maintainers-database

On top of that, ruby-rails provides rails (see http://svnweb.mageia.org/packages/updates/1/ruby-rails/current/SPECS/ruby-rails.spec?revision=156672&view=markup line 13), so something else depending on the old rails package is blocking the upgrade (from mandriva, the candidates I see are redmine or gitorious)

Please remove the ruby-rails-2.3.12 package from updates_testing, or do the changes described above.

Regards

CC: (none) => shikamaru

You're right - I should have been more careful; I thought the presence of a 2.3.12 gem in binrepo was due to an incomplete upgrade of the package.

Do I need to resort to an updated epoch to get rid of the 2.3.12 package in 1/core/updates_testing? Or is there some way to remove the package from updates_testing explicitly?

Ask sysadmins.

CC: (none) => sander.lepik

Removed fron updates_testing

CC: (none) => tmb

Package in svn reverted to 2.3.11 for Mageia 1.

Can this bug report be closed then?

CC: (none) => davidwhodgins

Seems yes.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED