This email is just to know if anyone from this SIG will be attending
Tempe Fudcon2011, i will, so it would be nice to use FUDCon to promote
ruby in general so i would like to start gathering info to get together
Toshio proposed to me the idea of coding dojos for fudcons but this idea
My bet is we could use fudcon to make fedora-ruby a better platform in
all senses, maybe solve issues at the hackfests.
After some vetting (thanks Mamoru) the Rails 2.3.8 rpms are Fedora
ready and pushed into rawhide. Feel free to pull from there to get the
latest stable 2.3.x rails build.
It's too late for the F14 release and I was contemplating whether or not
these should go into F14 updates. Would anyone object to this? If there
is any major incompatibilities or API changes between versions, we
should probably hold off to F15, but it would be nice to be able to
access these sooner than that.
I tried to triage many of the rubygem reviews last night. We have
roughly 35 of them.
I would really appreciate it if somebody could look at the review
request for rubygem-rack1 for epel. Having that package in epel will
fix some dependency bugs and eventually allow sinatra in epel.
keeping my wonders and researchs on building rpms and since im creating
a -doc pkg for rubygem-state_machine, because it seems it's a good idea
and following previous discussión about if tests are documentation or
not, it came to me the question about what about devel docs vs user doc
rpm pkgs (where user is a regular user who uses certain app, and devel
is a programmer who uses the app or library to devel certain derivative
Should the -devel pkg include the whole documentation files in it? or it
would requires furthers splitting as -doc-devel (-devel-doc)? (not so
good idea for me)
If the main pkg is a user application one might think about -user-doc
if the main pkg is a library, one might think about a -devel-doc subpkg.
any thoughts or policies about this?
I have doubt here... i guess both are different sw... but look...
 yum install graphviz-ruby
 gem install ruby-graphviz
should i start packaging the 2nd, what about the first? (confused)
This appeared on adopting rubygem-state_machine (testing it):
$ ruby unit/state_test.rb
Skipping GraphViz StateMachine::State tests. `gem install ruby-graphviz`
>= v0.9.0 and try again.
Then i tried the existing rpm  without luck for state_machine, the i
tried the gem version , which fixes the output warning.
- F14 feature freeze is tomorrow !
- Mohammed's ruby srpm was almost complete (as far as I tried using):
I slightly modified Mohammed's srpm and imported into rawhide build tree.
Now it is available on
A summary of changes from Mohammed's ruby-188.8.131.529-3.fc13:
- Some cleanups
- Make -irb, -rdoc subpackage noarch
- Make dependencies between arch-dependent subpackages isa specific
- Improve sample documentation gathering
I hope the imported new ruby won't break things (so much).
I appreciate all peoples' contributing to ruby 187 packages.
Forwarding from fedora-devel mailing list
The following ruby related packages are currently orphaned and
will be removed from F-14 tree if no one take them.
Will someone going to pick up these?
-------- Original Message --------
Subject: [ACTION REQUIRED] orphaned packages in F-14
Date: Wed, 4 Aug 2010 12:32:23 -0400
From: Bill Nottingham <notting(a)redhat.com>
Reply-To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>
Each release, we undergo the effort to track down owners for orphaned
packages in the release, and block those orphaned packages where
necessary. It's that time again for Fedora 14.
The following packages are currently orphaned and exist in F-14. As
you can see, there are a lot of dependencies on these packages. Please
pick up these packages if you have a need for them.
Unblocked orphan ruby-openid
Unblocked orphan rubygem-RedCloth
Unblocked orphan rubygem-gruff
Unblocked orphan rubygem-rubigen
Unblocked orphan rubygem-rufus-scheduler
Unblocked orphan rubygem-state_machine
Unblocked orphan rubygem-test-spec
List of deps left behind by orphan removal:
rubygem-newgem requires rubygem(RedCloth) = 4.2.2
rubygem-yard requires rubygem(RedCloth) = 4.2.2
rubygem-newgem requires rubygem(rubigen) = 1.5.4
rubygem-templater requires rubygem(rubigen) = 1.5.4
rubygem-rack requires rubygem(test-spec) = 0.10.0
rubygem-snmp requires rubygem(test-spec) = 0.10.0
The script that generated this page can be found at
There you can also report bugs and RFEs.
devel mailing list