DeveloperResources

"Ubuntu -- where the release cycles are short and furious"

©2005 Adam Conrad

Building packages for Ubuntu

• Set the target suite in debian/changelog to be 'edgy'. e.g. "dch -D edgy"

• When working with a package which originated in Debian, use a version number derived from the Debian version number with ubuntu<revision> appended. i.e. Debian 1.0-2 becomes 1.0-2ubuntu1, followed by 1.0-2ubuntu2, etc.

• Packages not in debian yet should end with revision -0ubuntu1 (To Be Discussed: see [https://launchpad.net/distros/ubuntu/+spec/package-version-conflicts] )

• Make source-only uploads, i.e. use "dpkg-buildpackage -S"

• when uploading to [:REVU], please include the orig tarball (use parameters -S -sa)
• Once you have created your packages, see [:Uploads] for how to upload

• You may want to build them in a [:DebootstrapChroot] or in [:PbuilderHowto:pbuilder]

• You may also build packages using [:BuildDaemons]

• Package search by file and on-demand package installation tool: [:AutoApt:auto-apt]

• [https://lists.ubuntu.com/archives/ubuntu-motu/2006-February/000443.html howto write watchfiles ] for sourceforge.net hosted projects

• Backports are explained at [:BackportsHowto]

Anchor(freezes)

Freezes

• Freeze states are described on the release schedule for the current release

• To request an exception, follow FreezeExceptionProcess

Anchor(syncs)

Syncs

• Syncing a package is importing it unmodified from Debian or another Debian-source repository.

• NB: syncs (like uploads) can not be reversed or undone. ALWAYS thoroughly check a package before asking for a sync.

• You should always sync a package rather than upload the unmodified source by hand.

• If you know you're going to have to modify the package and make an -<n>ubuntu<n> upload, don't ask for a sync. However, be sure to always use the exact same .orig.tar.gz as Debian (or whoever).

• If we're in UpstreamVersionFreeze, syncs of a newer upstream version require [#freezes explicit UVF exception approval].

• If there are Ubuntu changes in the current package, you must ensure the Ubuntu changes have been merged or are no longer relevant.
• Only versions in a 'suite' or 'distribution', i.e. things in a Sources file, can be synced.
• When requesting a 'sync', please include the following information:
  • Source package name
  • Source package version number to sync
  • Where to sync from (e.g. 'Debian sid main', 'Debian experimental non-free')
  • A copy of the entries from debian/changelog corresponding to the changes relative to the current version in Ubuntu
  • If there are Ubuntu changes:
    • a description of each of the Ubuntu changes (a bullet point list is fine, but copies of debian/changelog aren't)
    • a brief explanation of why each one may be dropped (e.g., it's been merged into Debian, is no longer appropriate, etc.)
    • an explicit confirmation that the Ubuntu changes should be overridden

• To request a sync, [https://launchpad.net/distros/ubuntu/+filebug file a bug in Launchpad] with the above information, and subscribe (NOT assign) the ubuntu-archive team to the bug. This team will process the request and close the bug when it is complete.

• Martin Pitt has written a [http://people.ubuntu.com/~pitti/scripts/requestsync script to file sync requests].

• The list of outstanding archive administration requests can be found here: https://launchpad.net/people/ubuntu-archive/+subscribedbugs

• Please only subscribe ubuntu-archive to a bug once you have a clear action for the archive team to perform. Do not ask ubuntu-archive to help you decide what to do.

Removing packages

• Normally speaking, packages that have been removed from Debian will be removed from Ubuntu semi-automatically shortly afterwards. There is generally no need to explicitly request removal of such a package.

• There are some cases where this will not happen semi-automatically: for example, if a package is in Ubuntu main then we assume that it shouldn't be removed until and unless it's demoted to universe. If you're expecting a package to be removed and it isn't for some reason, then subscribe (NOT assign) the ubuntu-archive team to a relevant bug. Please only subscribe ubuntu-archive to a bug once you have a clear action for the archive team to perform. Do not ask ubuntu-archive to help you decide what to do.

New to packaging?

• Reference to all new MOTUs [http://www.debian.org/doc/maint-guide/ Debian New Maintainer Guide].

• A nice tutorial is available from the [http://women.alioth.debian.org/wiki/English/PackagingTutorial debian women wiki]

• also interesting is this clarification for [http://women.alioth.debian.org/wiki/English/MaintainerScripts MaintainerScripts]

• Also see [https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml CDBS Manual]

• For deeper understanding of the packaging process, you might want to have a look at this one: http://women.alioth.debian.org/wiki/English/BuildingWithoutHelper

• For your private archives, this has interesting notes: http://people.debian.org/~calvin/unofficial/

• Forum Thread: How to make Debian-standard debs from scratch [http://ubuntuforums.org/showthread.php?t=51003&page=1&pp=10]

• Short HowTo about [https://wiki.ubuntu.com/MOTU/School/PatchingSources how to patch Ubuntu packages] (from the MOTU school)

Package archive

• Information about the archive and its mirrors can be found on the ["Archive"] page

• You can [http://packages.ubuntu.com/ search for a package in various Ubuntu releases].

• Old versions of packages which are no longer published in the archive can be retrieved from Launchpad

Seed management

• The official seed lists are available here: http://people.ubuntu.com/~cjwatson/seeds/

• Germinate output for dapper is available here: http://people.ubuntu.com/~cjwatson/germinate-output/dapper/ (use this to determine why packages are in main)

• SeedManagement explains how these pieces fit together to determine which packages go where

• The actual movement of packages between main and universe is semi-automatic: a tool called [http://people.ubuntu.com/~cjwatson/anastacia.txt anastacia] produces a report on what should be promoted or demoted according to the seeds, which the archive administrators review by hand and process.

• "Obvious" main/universe changes (e.g. library renames) can be processed right away. Non-obvious promotions to main require a [:UbuntuMainInclusionRequirements:main inclusion review].

Build logs

An explanation of the build daemon processing: BuildDaemons

• The Launchpad source package overview page (e. g. https://launchpad.net/distros/ubuntu/+source/coreutils for coreutils) has a list of all uploaded versions in the various Ubuntu releases. Clicking on a particular version shows a page with links to the build logs on all platforms.

• https://launchpad.net/+builds shows the status of all build daemons, with links to the currently active build.

[http://people.ubuntu.com/~cjwatson/cd-build-logs/ CD image build logs] BR [http://people.ubuntu.com/~cjwatson/livefs-build-logs/ Live filesystem build logs]

Changes

For each new version of a package which enters the archive, a message is sent to the [http://lists.ubuntu.com/mailman/listinfo/edgy-changes edgy-changes mailing list]. Similar mailing lists exist for previous releases (e. g. [http://lists.ubuntu.com/mailman/listinfo/dapper-changes dapper-changes]) which receive uploads to the -updates pocket of stable releases.

Changelogs for all packages can be found at http://changelogs.ubuntu.com/changelogs/ (this is the source used by update-manager and synaptic).

RSS Feeds of these messages are available at http://www.ubuntulinux.nl/files/ [http://www.ubuntulinux.nl/files/warty.xml warty] [http://www.ubuntulinux.nl/files/hoary.xml hoary] [http://www.ubuntulinux.nl/files/breezy.xml breezy] [http://www.ubuntulinux.nl/files/dapper.xml dapper] [http://www.ubuntulinux.nl/files/edgy.xml edgy]

Updates to Stable Releases

• SecurityUpdateProcedures details the special procedures for making security uploads

• StableReleaseUpdates describes the policy and procedure for non-security-related bugfixes for stable releases

Ongoing merge

Debian maintainers take note: there is a constant merge from Debian sid (unstable) into Ubuntu until UpstreamVersionFreeze. After that there are no more automatic merges, but you can request a manual merge in case that you consider that the selected version is sub-optimal. You can see the merge in action on the [http://lists.ubuntu.com/archives/ubuntu-changes-auto ubuntu-changes-auto] mailing list.

Automated merging of packages from Debian unstable into main (?)

• [http://people.ubuntu.com/~scott/ongoing-merge/README Introduction]

• [http://people.ubuntu.com/~scott/ongoing-merge/ Package listings]

A by-product of the automated merging is a set of patches that denote the current difference between Debian and Ubuntu. These are naively categorised and made publicly available.

• [http://people.ubuntu.com/~scott/patches/README Introduction]

• [http://people.ubuntu.com/~scott/patches/ Package listings]

Bugs

• [https://launchpad.net/distros/ubuntu/+bugs Ubuntu bugs]

• HelpingWithBugs

• More information on BugTracking

Broken packages

• Britney output (a report of uninstallable packages) can be found here: http://people.ubuntu.com/~cjwatson/testing/

CategoryUbuntuTeams