Thx for a review.
So far, it seems we have one blocker , which prevents us from
rebuilding packages which are using %setup macro for .gem expansion. We
are about to revert  to unblock the rebuild. We will see what
upstream is going to do about it.
Dne 07. 01. 19 v 11:19 Jun Aruga napsal(a):
Thanks for that.
I will look at your PR.
On Fri, Jan 4, 2019 at 4:18 PM Vít Ondruch <vondruch(a)redhat.com> wrote:
> As planned, Ruby 2.6 was released during Christmas. So I updated my PR
> with the changes required for the official build. There are things which
> could be improved, but there is no blocker IMO (but I have not tested
> the package extensively). So please take look at the PR, here is the
> Koji build (not sure why the koji-simple-ci fails, it seems it somehow
> mangles some dates or ....):
> and here is Copr repo for easier testing:
> If there is no issue, I'll ask for side tag and star with rebuild soon.
> Probably next week already unless I am on PTO. Anyway, mass rebuild is
> scheduled on 30th of January (unless I am mistaken), so everything
> should land in Fedora prior that date.
> Dne 16. 11. 18 v 17:43 Vít Ondruch napsal(a):
>> Hi everybody,
>> I just created PR with .spec file updated to build Ruby 2.6.0.preview3:
>> It is very much WIP, but it builds at least. I have even not tried to
>> install or run the package. Pagure is so nice, that it should provide
>> the recent scratch builds via simple-koji-ci, so I am not going to link
>> it here.
>> So far, there are 3 things missing/ignored:
>> 1. Bundler is completely removed. I am afraid the situation has not
>> improved much since last year. E.g. Molinillo, the dependency solver is
>> included in Ruby twice, once via RubyGems, second time via Bundler, etc.
>> not nice.
>> 2. IRB was gemified, therefore it should be moved into rubygem-
>> subpackage and the original ruby-irb should be obsoleted.
>> 3. I am still undecided how to go forward with JIT. It requires compiler
>> and it has to be explicitly required, therefore we should do nothing
>> IMO. Later, we should probably Suggest or even Require the compiler? Not
>> And as always, please let me know any feedback, either here or in PR.
>> ruby-sig mailing list -- ruby-sig(a)lists.fedoraproject.org
>> To unsubscribe send an email to ruby-sig-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
> ruby-sig mailing list -- ruby-sig(a)lists.fedoraproject.org
> To unsubscribe send an email to ruby-sig-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: