Actions

Developer Area/Packaging

From Mahara Wiki

< Developer Area
Revision as of 16:54, 22 Haziran 2011 by Francois (talk | contribs) (things to do when preparing new packages)

Here is a description of the work that is involved in maintaining the Mahara packages in Debian and Ubuntu.

If you want to get involved, get in touch with one of the members of the packaging team.

Prerequisites

You need to build packages in the target distribution. So for the most common type of uploads (to Debian unstable), you need to have a Debian unstable virtual machine of some sort.

Then install these packages:

sudo aptitude install git-buildpackage build-essential debhelper dh-make pristine-tar

Then you need to get access to the repo:

  1. Create a new account on Alioth
  2. Ask the Alioth admins to add you to the collab-maint group on git.debian.org

Put the following in your ~/.gbp.conf:

[DEFAULT]
pristine-tar = True

[git-buildpackage]
sign-tags = True
keyid = 0x007C98D1
export-dir = ../build-area/

and something like this in your ~/.bashrc:

export DEBEMAIL="[email protected]"
export DEBFULLNAME="Francois Marier"
export DEBSMTP="localhost"
export GPGKEY="007C98D1"

Getting the code from the packaging repo

All of the packaging is stored in a separate git repository.

Here's how to clone this repo:

gbp-clone ssh://git.debian.org/git/collab-maint/mahara.git

Building packages

Once you have the repo cloned, run this to build packages:

git buildpackage

They will end up in ../build-area/ where you can check them using lintian:

lintian -I --pedantic --color=auto mahara_1.4.0-1_amd64.changes

and test them on your box by installing the deb:

sudo dpkg -i mahara*1.4.0-1*deb

Upgrading the package for a new upstream release of Mahara

First of all, download the latest stable tarball in .tar.gz format (not .zip or .tar.bz2).

Then go inside your clone of the packaging repo, on the master branch and import the tarball:

git import-orig ../mahara-1.4.0.tar.gz

Once that's done (fix any conflicts if needed), you can bump the version number in the changelog:

dch -i

Then commit this:

debcommit -a

and finally build the package and test it (see previous section).

Things to do when preparing a new package