Mohammed Morsi wrote, at 09/02/2010 04:25 AM +9:00:
On 08/30/2010 10:30 PM, Mohammed Morsi wrote:
> On 08/26/2010 09:38 AM, Mamoru Tasaka wrote:
>> Mohammed Morsi wrote, at 08/26/2010 11:35 AM +9:00:
>>> After some vetting (thanks Mamoru) the Rails 2.3.8 rpms are Fedora
>>> ready and pushed into rawhide. Feel free to pull from there to get the
>>> latest stable 2.3.x rails build.
>>> It's too late for the F14 release and I was contemplating whether or not
>>> these should go into F14 updates. Would anyone object to this? If there
>>> is any major incompatibilities or API changes between versions, we
>>> should probably hold off to F15, but it would be nice to be able to
>>> access these sooner than that.
>> Well, actually F-14 is to be released on 2010-11-02, F-14 beta release is
>> 2010-09-14, so I don't think it is too late for F-14 release.
>> I think we should push rails 2.3.8 related packages to also F-14 tree
>> (first for dist-f14-updates-testing).
> When I said too late for the F14 release, I meant the main feature
> freeze / repo fork (which contains rails 2.3.5), not F14-updates.
> Regardless, since there doesn't seem to be any objections I'll push
> these to F14-updates tommorow.
The SRPMS have been pushed to the f14 repo branch. I'm having some
trouble with 'fedpkg build' though, activesupport is building fine, but
the other packages which require it (as well as a few other
interdependencies) are not because the updated version is not available
in the repo. To get around this in rawhide, I chain-built the rpms, but
I can't do so in updates without filing a rel-eng ticket. What is the
correct way to proceed?
Filing a rel-eng ticket is actually the correct way.
Note that you have to
- once ask rel-eng team to get activesupport 2.3.8 tagged as dist-f14-override
- then build activerecord, again ask rel-eng team to get this tagged as override
- then build actionpack, again ask...
Well, this may take time. So if you feel this is annoying for you, you
can comment out "BuildRequires(check)" dependency and disable check
(for F-14: I think for rawhide always enabling %checkis preferable)
Also somewhat related, I've noticed that bohdi is now preventing
pushing updates (even new packages) until they meet the "package update
criteria". The thing is I can figure out how to get them to pass this,
and was wondering if anyone had an idea?
For "normal" (i.e. non crit-path) packages, if one week passes since the
package is pushed into testing, the package "passes the update criteria".
Instead you can set "Threshold for pushing to stable" (to 1, for example)
and if someone else votes +1 karma for the updates request you submitted,
the package can go to the stable. So if you want to get some ruby related
package pushed into stable soon, you can post to this mailing list
the information of updates request you submitted on bodhi, and we may
vote karma soon.