Differences between revisions 11 and 12
Revision 11 as of 2013-03-02 15:38:40
Size: 3006
Editor: ?Cédric Boutillier
Comment: indicate one needs to log in on git.debian.org, and go to /git/pkg-ruby-extras
Revision 12 as of 2013-03-02 15:58:29
Size: 2898
Editor: ?VamseeKanakala
Comment: Remove a rather confusing instruction to log into alioth.debian.org - in this context, we only need git.debian.org
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:
Now login to alioth as follows:
ssh alioth-user@alioth.debian.org
To access to the machine with read/write access to the Git repositories, use:
Now login to git.debian.org (vasks) as follows:

Translation(s): none


Once you are done with all the steps of packaging the gem, it is time to add it to the pkg-ruby-extras git repo at alioth. For that you will have to request for a membership in the pkg-ruby-extras team from here:

It may take a while to get it approved. Once you get added to the team you can add your package to the debian git repository directly using your login name and following the steps below.

You will find more detailed information about this here:

Alioth SSH

To create a repository at debian git you have to login to alioth via ssh. Add your ssh public key to your alioth user page. It may take around an hour to get activated. Now login to git.debian.org (vasks) as follows:

ssh alioth-user@git.debian.org

For more info on ssh access refer Alioth/SSH.

Creating a pkg-ruby-extras git repo

Once you are logged in on git.debian.org, go to the directory /git/pkg-ruby-extras and create the new repository there.

cd /git/pkg-ruby-extras/
./setup-repository <ruby-timecop>

ruby-timecop being a pattern. The last command will create an empty git repository named ruby-timecop at git.debian.org.

Adding your package to the repo

Now clone this empty repository on your local machine. Go to some new directory in your local machine and clone this repo as follows:

git clone alioth-login@git.debian.org:/git/pkg-ruby-extras/ruby-timecop.git

This should give you some errors as the repo is empty. So ignore them.

Assuming that you have an up-to-date gitorious repo for the current package, pull all the branches from gitorious repo to the cloned one in your local machine.

git pull address_of_gitorious_repo
git fetch address_of_gitorious_repo upstream:upstream
git fetch address_of_gitorious_repo pristine-tar:pristine-tar

Now it's time to push it to the repo at git.debian.org. Before that make sure that you have all the three branches, which are:

  • master
  • pristine-tar
  • upstream

You can also use any git visualization tool like gitg (for Gnome), qgit (for KDE) or tig (for terminal) for verification.

Once you have made sure that all is well, go ahead and push everything to the repo at debian git.

git push --all
git push --tags

Commits are sent by email to the pkg-ruby-extras-commits@lists.alioth.debian.org mailing list. These messages from people not subscribed to that list are moderated. Please subscribe to the list with the email address you used to configure Git, so that these emails go through directly.