Bug 456599

Summary:	rubygem-rails 2.1.0 is available, please update
Product:	[Fedora] Fedora	Reporter:	Robert Scheck <redhat-bugzilla>
Component:	rubygem-rails	Assignee:	Michael Stahnke <mastahnke>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	mastahnke, sseago
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-09-11 17:08:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Robert Scheck 2008-07-24 20:46:03 UTC

Description of problem:
rubygem-rails 2.1.0 is available since a longer time now, please update on all 
active branches; especially the EPEL ones. And for me it seems to work everywhere.

Version-Release number of selected component (if applicable):
rubygem-rails-2.0.2-2

Expected results:
rubygem-rails-2.1.0-1 or newer on all active branches.

Comment 1 David Lutterkort 2008-07-25 16:42:46 UTC

I'll try and do that early next week (unless Michael wants to beat me to it)

What applications/plugins have you tested it with ?

Pushing it into F8/F9 has to be done very carefully; we really need to avoid
breaking people's apps. And with Rails, there's always a chance that that happens.

Comment 2 Robert Scheck 2008-07-25 19:08:53 UTC

Pushing to EPEL has do be done same carefully. The mysql and rmagick extensions 
are working for me, but the applications are company internal, so no OSS software 
or similar. I'm running the 2.1.0 generation with the other packages on Fedora 8 
and EPEL 4/5, no problems so far with it. Even a rebuild of the whole ruby/rails 
collection is working on SLES 9 for me :)

But feel free to do also several testings with your own applications etc., but I
unfortunately need some 2.1.0 features which made me privately upgrading and also
testing...

Comment 3 Michael Stahnke 2008-08-01 03:35:36 UTC

I have updated in devel.  We are still discussing whether or not EPEL will be
updated, as updating for no good reason is generally considered against practice.

Comment 4 Fedora Update System 2008-08-03 23:44:14 UTC

rubygem-rails-2.1.0-1.fc8 has been submitted as an update for Fedora 8

Comment 5 Fedora Update System 2008-08-03 23:44:54 UTC

rubygem-rails-2.1.0-1.fc9 has been submitted as an update for Fedora 9

Comment 6 Fedora Update System 2008-08-07 23:54:01 UTC

rubygem-rails-2.1.0-1.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update rubygem-rails'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-7065

Comment 7 Fedora Update System 2008-08-08 00:00:23 UTC

rubygem-rails-2.1.0-1.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update rubygem-rails'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-7131

Comment 8 Fedora Update System 2008-09-11 17:07:59 UTC

rubygem-rails-2.1.0-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2008-09-11 17:12:16 UTC

rubygem-rails-2.1.0-1.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.