[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ 9 ] [ 10 ] [ A ] [ next ]

Debian New Maintainers' Guide
Chapter 9 - Updating the package

9.1 New Debian revision

Let's say that a bug report was filed against your package, #54321, and it describes a problem that you can solve. To create a new Debian revision of the package, you need to:

9.2 New upstream release (basic)

Now let's consider a different, slightly more complicated situation - a new upstream version was released, and of course you want it packaged. You need to do the following:

Note that if you set up a `debian/watch' file as described in watch.ex, Section 5.10, you can run uscan(1) to automagically look for revised sources, download them, and run uupdate.

9.3 New upstream release (realistic)

When preparing packages for the the Debian archive, you must check the resulting packages in detail. Here is a more realistic example of this procedure.

  • Verify changes in upstream source

  • Port the old Debian packaging to the new version.

  • Build the new package as described in The debuild command, Section 6.3 or The pbuilder package, Section 7.6. Use of pbuilder is desirable.

  • Verify new packages are built correctly.

  • If any changes were made to correct anything in the packaging along the way, go back to the step 2 until satisfied.

  • If your upload needs to be sponsored, be sure to note any special options required when building the package (like 'dpkg-buildpackage -sa -v ...') and be sure to inform your sponsor so he or she builds it correctly.

  • If you are uploading yourself, perform Uploading the package, Chapter 8.

  • 9.4 The orig.tar.gz file

    If you try to build packages only from the new source tree with debian/ directory without the orig.tar.gz file in its parent directory, you will end up unintentionally creating a native source package, which comes without the diff.gz file. This type of packaging is only appropriate for the debian-specific packages, which will never be useful in another distribution. [5]

    In order to obtain a non-native source package which consists of both the orig.tar.gz file and the diff.gz file, you must manually copy the upstream tarball to the parent directory with its file name changed into <packagename>_<upstream_version>.orig.tar.gz as it was done by dh_make command in Initial "debianization", Section 2.4.

    9.5 The cvs-buildpackage command and similes

    You should consider using a source code management system to manage packaging activity. There are several wrapper scripts which are customized to be used with the most popular ones.

    These commands also automate the packaging of new upstream releases.

    9.6 Verifying package upgrades

    When you build a new version of the package, you should do the following to verify that the package can be safely upgraded:

    If the package makes use of non-trivial pre/post/inst/rm scripts, be sure to test the upgrade paths of those.

    Bear in mind that if your package has previously been released in Debian, people will often be upgrading to your package from the version that was in the last Debian release. Remember to test upgrades from that version too.

    [ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ 9 ] [ 10 ] [ A ] [ next ]

    Debian New Maintainers' Guide

    version 1.2.11, 12 January 2007.

    Josip Rodin [email protected]