Red Hat Bugzilla – Bug 967332
Review Request: rubygem-chardet - Character encoding auto-detection in Ruby
Last modified: 2016-01-04 03:59:38 EST
Spec URL: http://anujmore.fedorapeople.org/pkgs/rubygem-chardet/rubygem-chardet.spec
SRPM URL: http://anujmore.fedorapeople.org/pkgs/rubygem-chardet/rubygem-chardet-0.9.0-1.fc19.src.rpm
Description: Character encoding auto-detection in Ruby
Fedora Account System Username: anujmore
Builds on mock: https://raw.github.com/execat/Packages/master/rpmspecs/rubygem-chardet/mock
rpmlint does not complain:
3 packages and 0 specfiles checked; 0 errors, 0 warnings.
I will take it for a review.
From your spec file:
# URL: http://blog.vava.cn/ # This URL is mentioned in the Gem but doesn't open
The original chardet gem is actually hosted on RubyForge and maintained by Hui Zheng. The release is from 2006 and I don't see any new development or updates here.
The URL you are mentioning belongs to chardet2, which is pretty new, it's based on chardet and seems to be maintained.
Apart from that I am unsure whether is chardet Ruby 2.0 ready or not, since I can see that there is a commit regarding Ruby 2.0 compatibility in chardet2. Fedora 19 will use Ruby 2.0 as a default and it would be pointless to package a sort-of dead project that wasn't tested on Ruby 2.0 (although backporting of the above mentioned commit could solve it).
Is there a reason to package this gem? Wouldn't be better to bring chardet2 to Fedora?
I discussed this with the maintainer yesterday:
The change in URL and the repo name was done less than 10 days ago, where as I packaged the Gem quite some time ago.
After a discussion with vondruch, I packaged this Gem again as chardet2, and it worked with no major changes made to this specfile.
This runs fine on mock as well.
I was thinking of removing this request and filing another one for chardet2, but I was going to discuss this with the GitLab guys before doing that. Nevermind, though.
Anuj, as I see the upstream ticket, they are not really helpful unfortunately :/ They don't mind to propose even yet another fork, which is exactly the opposite of what we want. Could you please try to contact the original chardet author and try it the other way around? I.e. the original author will revive the development, or give them commit access and allow them to push new gems to rubygems.org. Thank you.
Closing this stalled review.