Differences between revisions 11 and 12
Revision 11 as of 2014-01-01 12:45:55
Size: 2836
Editor: Praveen A
Comment: added link to tests page
Revision 12 as of 2014-10-21 15:37:49
Size: 3004
Editor: Praveen A
Deletions are marked like this. Additions are marked like this.
Line 75: Line 75:
Note: To fetch rails-assets-* gems, you need to provide a different gem source like this example

 gem fetch --source https://rails-assets.org rails-assets-jquery

Translation(s): none

Building with gem2deb

Choose a package

Go to piratepad and choose a package you want to build. Make sure no one else is working with it already.

Use apt-cache to check if it is already packaged for Debian

apt-cache search devise ruby

"devise" being a pattern.

In case you are not running Sid you can also check at:

and make sure you choose "unstable" for Distribution. Check at

if someone is already packaging it. Also check it with

wnpp-check devise

A pdf file which contains the info if a gem is already packaged is to be found here:

Make sure to use an actual version. You will have to check the wnpp site or with wnpp-check anyway.

Setup your environment

Add the following variables in your ~/.bashrc file

export DEBEMAIL=your@email.domain
export DEBFULLNAME='Your Name'
alias lintian='lintian -iIEcv --pedantic --color auto'
alias git-import-dsc='git-import-dsc --author-is-committer --pristine-tar'
alias clean='fakeroot debian/rules clean'

and update your current environment by running

$ source ~/.bashrc

Build the package

First you need install gem2deb

apt-get install gem2deb

Create a build directory and go there

mkdir -p ~/Build/diaspora-packaging && cd $_

You might also want to create a directory for your package

mkdir build_devise && cd $_

and then run

gem2deb devise

will run "gem fetch devise" to download the package. If you get an error that the Test failed, see ruby tests for hints to solve it.

Note: To fetch rails-assets-* gems, you need to provide a different gem source like this example

Now you have to edit files like

  • copyright
  • control
  • changelog

You will find such info at

and the homepage of the package. The homepage you will find at rubygems too.

Note: Read http://www.debian.org/doc/manuals/maint-guide/dreq.en.html to learn more about each file.

Once that is done build the package with


If you get an error that it could not be signed, ignore it for now.

And when it has finished check for lintian errors:

lintian -iIEcv --pedantic --color auto ../ruby-devise*.changes

If you get errors, you have to correct them. Then run dpkg-buildpackage again and test with lintian again.