Rails 2.3.8 in Rawhide

[Mohammed Morsi]

  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.
>>>
>>>       -Mo
>> 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).
>>
>> Regards,
>> Mamoru
>> _______________________________________________
>> ruby-sig mailing list
>> ruby-sig at lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
> 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.
>
>     -Mo
>
>
> _______________________________________________
> ruby-sig mailing list
> ruby-sig at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/ruby-sig

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?

Also somewhat related, I've noticed that bohdi is now preventing me from 
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?

   -Mo