Bug 598377

Summary: request for update to 3.6
Product: [Fedora] Fedora Reporter: Rakesh Pandit <rpandit>
Component: bugzillaAssignee: Emmanuel Seyman <emmanuel>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: emmanuel, itamar, jeff.raber, mike
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: 2010-06-01 12:28:11 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 Rakesh Pandit 2010-06-01 09:09:29 UTC
May you update to latest release (stable) in rawhide ?

/rakesh

Comment 1 Emmanuel Seyman 2010-06-01 12:11:29 UTC
I've been working on this for the last week. There are still some rough edges on the .spec file but that's what rawhide is for, I guess.

Comment 2 Emmanuel Seyman 2010-06-01 12:28:11 UTC
http://koji.fedoraproject.org/koji/taskinfo?taskID=2221992

Coming soon to a rawhide mirror near you.

Comment 3 Michael Cronenworth 2010-06-17 15:35:20 UTC
Would it be possible to include this into Fedora 13? AFAIK there have been no changes to the perl requirements from 3.4.x.

Comment 4 Emmanuel Seyman 2010-06-25 08:42:19 UTC
(In reply to comment #3)
>
> Would it be possible to include this into Fedora 13? AFAIK there have been no
> changes to the perl requirements from 3.4.x.

Now that 3.6.1, this is feasible, at least. It will require a lot of testing and it will likely be irreversible (unless there are no changes in the database schema, which I doubt). I don't have the time to do this, personally.

FYI, 3.4.7 is being pushed out as an update.

Comment 5 Rakesh Pandit 2010-06-25 09:15:48 UTC
I don't endorse to do it on stable version i.e 3.6 to stable.

Comment 6 Emmanuel Seyman 2010-07-01 23:26:08 UTC
*** Bug 610275 has been marked as a duplicate of this bug. ***