New packages

For a piece of software to be included in Ubuntu, it must meet the Ubuntu License Policy.

Requesting a new package for Ubuntu

Packages that have recently been added to Debian unstable will be automatically synced into Ubuntu prior to the Debian Import Freeze (DIF). After the Debian Import Freeze, you must file a bug with the summary field “Please sync <packagename> from debian <distro>” where <packagename> is the package you would like to see.

To get a package into Ubuntu, file a bug in Launchpad and make sure it has the tag needs-packaging.

In the bug, mention where to get the source for it and which license it is under. An example request is shown here. Make sure you check which packages have already been requested.

Since we want Free Software to reach as many people as possible and do not want too much duplication of packaging effort, it is useful for packages that meet the requirements of the Debian Free Software Guidelines to be requested within Debian’s Work-Needing and Prospective Packages (WNPP) process by filing a Request for Package (RFP) bug on the WNPP package in Debian’s bug tracker.

If you file a needs-packaging bug, please link it to the Debian WNPP bug as well.

Packaging it yourself

If you want to try packaging it yourself, refer to our guide on How to create a new package.

NEW packages through Debian

Ubuntu regularly incorporates source packages from Debian, so it is encouraged to upload a package to Debian first. Your package will reach a much broader audience if it is in Debian and all of its derivatives.

To have faster reviews, several teams have been set up to manage subsets of packages, including:

See the full list of teams. If there is no team available that takes care of the group of packages you are interested in, contact the Debian mentors (see “Further Reading” below).

Ubuntu does virtually all package maintenance in teams. If your package is related to any of the existing teams within Debian, work with that team to get the package uploaded to Debian. If there is no team already, consider starting a new team within Debian (e.g. at Alioth) for any package that is likely to have a significant number of bugs or other maintenance overheads (like architecture-specific issues).

Additionally, there are roughly an order of magnitude more Debian Developers than Ubuntu Developers. It is comparably more difficult to get a new package into Ubuntu due to the sheer volume of requests compared to the available resources for reviews. In many cases, people have an easier time getting their package into Ubuntu via Debian than doing so directly.

If you choose to do this, file an Intent to Package (ITP) bug on the WNPP package in Debian to let others know you’re working on it (reportbug -B debian wnpp should do the right thing). Then, go through the Debian Mentors to get the package uploaded. A number of Ubuntu Developers are also Debian Maintainers or Debian Developers, so they may be able to help you navigate Ubuntu/Debian interactions.

Some good tips

Going through MOTU

Submitting new packages through Debian is the preferred path. However, if your package is Ubuntu-specific or can’t go into Debian for some other reason, you can submit it directly to MOTU. There are a limited number of available reviewers, so you may encounter delays here.

New packages require extra scrutiny and go through a special review process, before they get uploaded and get a final review by the Archive Admins. More information on the review process, including the criteria that will be applied, can be found on the Code Reviewers page. Developers are encouraged to examine their own packages using these guidelines prior to submitting them for review.

To receive higher quality bug reports, consider writing an apport hook for your package.

The MOTU team approval policy for new packages:

The MOTU team uses the following workflow:

  • Join the #devel:ubuntu.com channel on Matrix and talk with the MOTU. It’s good to do this early on, to get advice on how to package (avoid common mistakes), to find out if your package is likely to be accepted (before you invest a lot of work in packaging it), and to find mentors willing to sponsor your package or to point you in the right direction.

  • When you start to work on a new package, assign the needs-packaging bug to yourself and set it to In Progress (if there is no needs-packaging bug, file one first).

  • Once you have an initial package, follow the new packaging instructions to upload it to your PPA or a Launchpad branch, then add a link to the package in the description of the bug. Requests for changes or other communication about your package will be made as comments on your bug. Subscribing ubuntu-sponsors to sponsorship requests is generally advised, as it makes the request appear on the list that people look at.

  • Once the approved package is uploaded, the uploading MOTU will set the bug status to Fix Committed.

  • When the package clears the NEW queue it will automatically be set to {guilabelFix Released (debian/changelog must close the needs-packaging bug). This is done with a bullet point that follows the format:

    • Initial release (LP: #242910)

    where “LP” refers to “Launchpad”. See the debian/ directory page for more information on changelogs.

  • Even if you don’t run Debian as your primary OS, most packaging can be tested perfectly well in a chroot, or failing that, in a Virtual Machine (and most packages will work fine without any changes anyway). (→ Using Development Releases)

  • #debian-ubuntu on OFTC and the debian-derivatives mailing list are good places for Ubuntu Developers to ask questions.

Deadline

Feature Freeze is the latest approval date. It is recommended to get things done a couple of weeks earlier than that, as getting approval may take some time. If you have a deadline, make sure you factor review and approval time into your timeline.

Review of new packages

After the new package is uploaded, it will show up and be held in the NEW queue. It is then checked by the Archive Admin team.

Further reading