From Fedora Project Wiki
(→‎Open review requests: rm climate_control and dependor)
Line 28: Line 28:
{|border="2" cellpadding="2" cellspacing="0"
{|border="2" cellpadding="2" cellspacing="0"
! Gem !! Package Review Request
! Gem !! Package Review Request
| climate_control || {{bz|1017994}}
| unicorn || {{bz|786636}}
| unicorn || {{bz|786636}}
Line 42: Line 40:
| virtus || {{bz|1040180}}
| virtus || {{bz|1040180}}
| dependor || {{bz|1036944}}

Revision as of 22:00, 23 December 2013

This document outlines the steps to get Gitorious into Fedora and EPEL.

High Level Steps and Issues


  1. Get all Gitorious' dependencies into Fedora.
    • Several Rubygems.
    • Several Javascripts.
  2. Get Gitorious into Fedora.
    • Bundler issues: If we use different Gem versions than upstream, Bundler wants to write to Gemfile and Gemfile.lock. We will use bundler_ext to work around this. This will require the rubygem-bundler_ext package and a lot of testing.
    • Init scripts: Create equivalent systemd unit files for Fedora & RHEL 7.
    • Ruby version: Upstream "next" branch works with Ruby 1.9.3 and 2.0.0. I'm working with upstream to maintain this compatibility via Jenkins.
    • Gem versions: Upstream uses different Gem versions than Fedora has. The biggest difference is Rails, but others are documented below. Plan of attack is to ensure that the test suite passes with both.
    • Javascript libs: There are several Git submodules in upstream (bane, capillary-js, raphael, spin.js, others). We must unbundle these and package them separately.
    • GeoIP data: Gitorious bundles GeoIP.dat, which is already available in Fedora as the "GeoIP" package.
    • FHS considerations: for the Gitorious web application itself, we need to discover how to split up the package to fit the FHS conventions of /etc/, /usr/, and so on.


  1. Get all Gitorious's dependencies into EPEL.
    • Rails. I don't have experience packaging Rails, and there's been questions about which version to put into EPEL.
    • Various Rubygems must be branched for EPEL.
  2. Get Gitorious into EPEL.
    • Unfortunately upstream has dropped support for Ruby 1.8, so formal EPEL inclusion can only happen after RHEL 7 is released and EPEL 7 is branched.

Open review requests

Please review some of these. I'm willing to trade reviews.

Gem Package Review Request
unicorn RHBZ #786636
org-ruby RHBZ #1036901
resque-cleaner RHBZ #1037278
resque-job-stats RHBZ #1037900
wikicloth RHBZ #1039818
virtus RHBZ #1040180

Checking progress with rhgc.rb

In order to see the list of gems that must still be packaged:

  1. git clone git:// gitorious
  2. git clone git:// rhgc
  3. ./rhgc/rhgc.rb --gemfile gitorious/Gemfile

You will need rubygem-gemnasium-parser in order to run rhgc.rb, but this package is not yet in Fedora. You can find it here:

Gem dependency graph

You can view the outstanding Gem dependency chart (graphviz source). I will attempt to keep this graph up to date, but it is a manual process. For "live" data, see the rhgc.rb section above.

This graph does not take into account Javascript libraries.