Re: ruby 2.0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It was rebuilds against Ruby 2.1 and they had been done in f21-ruby side tag, which was merged at Wednesday.

Dne 1.5.2014 12:30, Richard W.M. Jones napsal(a):
Lots and lots of ruby broken deps this morning, eg:

Interesting set of packages you have picked up :)
[deltacloud-core]
	deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudfiles)

This was broken already before Ruby 2.1 landed, due to retired rubygem(cloudfiles)

[gofer]
	ruby-gofer-0.77-1.fc21.noarch requires rubygem(qpid) >= 0:0.16.0

Don't know nothing about this, but it seems unrelated to Ruby 2.1 change IMO.

[hivex]
	ruby-hivex-1.3.10-2.fc21.i686 requires ruby(release) = 0:2.0.0

Versioned ruby(release) require should be used only for exceptional cases. I doubt this is the case.


You should notice my announcement here: https://lists.fedoraproject.org/pipermail/devel/2014-April/198800.html


Vít


I'm unclear what we need to do about them.  I noticed some rebuilds
against ruby 2.0 flying past over the last few days.  Does this mean
there are rebuilds which are just waiting to be tagged into koji?

Rich.



--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux