Navigation: / Packaging
Language: en

Packaging

Check titanpad ONGOING work for more updated info.

Now that we have our package checked out we can start make changes to it.

Say epiphany-browser had been orphaned and we were adopting it, then we would add ourselves as the maintainer in the debian/control.in file, (The debian/control file is automatically generated from this in the clean rule)

Source: epiphany-browser
Section: gnome
Priority: optional
Maintainer: Your Name <your@email.address>
Uploaders: @GNOME_TEAM@
...

Now that you have done this you may want to make sure the debian/control file is regenerated, you can do this by running:

fakeroot debian/rules clean

Then you will want to add an entry to the changelog. If you have not used debchange (dch) before, put the following in your ~/.devscripts config file:

DEBCHANGE_RELEASE_HEURISTIC=changelog

You can change the editor it uses by setting the EDITOR environment variable. There are several different circumstances in which you’ll want to change the changelog:

# Increase the Debian release number, adding a new changelog entry
    dch -i
# Append a new entry to the current changelog
    dch -a
# Don't change version number or add a new changelog entry,
# just update the changelog's stamp and open up an editor
    dch -e

So say we wanted to increase the debian release version, we would do the following inside the epiphany-browser directory we had just checked out:

dch -i

We would then be given the following:

epiphany-browser (2.20.1-4) UNRELEASED; urgency=low

  *

 -- Your Name <your@email.address>  Thu, 22 Nov 2007 17:01:00 +0000

+--  7 lines: epiphany-browser (2.20.1-3) unstable; urgency=low -- Other Person
+--...

We can then add an entry saying that the package has a new maintainer:

epiphany-browser (2.20.1-4) UNRELEASED; urgency=low

  * New Maintainer. Closes: #NNNNNN

 -- Your Name <your@email.address>  Thu, 22 Nov 2007 17:01:00 +0000

+--  7 lines: epiphany-browser (2.20.1-3) unstable; urgency=low -- Other Person
+--...

You will probably also want to check that the package still builds, and that you haven’t broken anything. Firstly you need to obtain the original tarball and put it in the ../tarballs directory.

cd ..
mkdir tarballs
cd tarballs
wget http://http://ftp.de.debian.org/debian/pool/main/e/epiphany-browser/epiphany-browser_2.20.1.orig.tar.gz
cd ../epiphany-browser

Once you have done this you can build the package using:

svn-buildpackage --svn-lintian --svn-ignore-new

The resulting package with then be located in ../build-area/

Next: Committing >>