You probably noticed, that there is ongoing build of all Python packages
in Copr  and today, I was approached by Miroslav Suchý, that he'd
like to do the same for rubygems. And this in turn triggered these
1) Would you be interested to create ruby-sig group in FAS? We could
make the group owner of some packages and in turn, the members of the
group could maintain the packages, without explicitly asking for some ACLs.
2) For the Copr rebuild of rubygems, there needs to be some FAS group
again. Python guys are asking for "pypi-builds-sig" group , hence
following their lead, I'd like to ask for "rubygems-builds-sig" group
(note that although I don't like the '-sig' suffix in this case, it is
mandated by the infrastructure ticket template).
So what are your thoughts?
Time is running past and it is almost 6 months of development of Ruby
2.4. So I started to prepare some test build again. I am pushing all the
changes into private-ruby-2.4 branch of dist-git if you are interested
and here is the build of r55184:
One notable change is that XMLRPC library was extracted into separate
gem, so rubygem-xmlrpc is now available as Ruby subpackage.
Please give it a try and let me know if anything goes wrong.
Hi, Ruby-sig folks
Now Rails 5.0.0.rc2 has been released, the stable version coming soon.
So, I have created the Rails 5.0 proposal page, including the estimate of the tasks to create the package.
Feel free to ask me if there is something.
chm ... should I read it as I should retire rubygem-rsolr as well?
Nothing depends on it in Fedora I guess.
Dne 2.6.2016 v 16:05 gil napsal(a):
> i retired solr and parquet depend on hadoop that was retired
> parquet-format was used only by parquet
> devel mailing list