Removing packages that have broken dependencies in F22 tree

Kalev Lember kalevlember at gmail.com
Tue Apr 28 09:35:40 UTC 2015


On 04/28/2015 10:16 AM, Vít Ondruch wrote:
> Dne 28.4.2015 v 00:45 Kalev Lember napsal(a):
>> rubygem-rugged          tdawson
>>
> 
> I am not maintainer of this, but please do not remove this. Rugged was
> broken by unannounced libgit2 update and there is still not official
> release fixing the compatibility. Removing this rubygem will mean just
> more work for everybody involved.

libgit2 is at 0.22.2 and looks like there's a matching new Rugged
release at https://rubygems.org/gems/rugged/versions/0.22.1b1 and the
package just needs updating. I am not sure what's up with the
maintainer, but maybe you could help them out by comaintaining
rubygem-rugged?

When it comes to shipping F22, I don't think it makes sense to include a
package that is so horribly broken that it cannot even be installed. But
if you guys are actively working on fixing it, I am sure we can try and
convince releng to give it a few more days before blocking so that it
can be pulled in through the freeze through the FE process:
https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

Also, please note that Fedora policies allow adding new packages in the
updates repo, so even if something gets dropped now, it can always be
fixed and shipped in the updates repo at a later date.

-- 
Hope this helps,
Kalev


More information about the devel mailing list