Promoting a package into main
This document describes the requirements for a package to be considered for inclusion into the supported set of Ubuntu packages (into main), which entails that this package receives the full scope of security and QA support.
The MainInclusionProcess page describes the steps of the process.
The package must fulfill the following requirements:
Availability: The package must already be in the Ubuntu universe, and must build for the architectures it is designed to work on.
Rationale: There must be a certain level of demand for the package, for example:
- The package is useful for a large part of our user base.
- The package is a new build dependency or dependency of a package that we already support.
- The package helps meet a specific Blueprint goal.
- The package replaces another package we currently support and promises higher quality and/or better features, so that we can drop the old package from the supported set.
Security: The security history and the current state of security issues in the package must allow us to support the package for at least 9 months (60 for LTS support) without exposing its users to an inappropriate level of security risks. This requires checking of several things that are explained in detail in the subsection Security checks.
- After installing the package it must be possible to make it working with a reasonable effort of configuration and documentation reading.
- The package must not ask debconf questions higher than medium if it is going to be installed by default. The debconf questions must have reasonable defaults.
- There are no long-term outstanding bugs which affect the usability of the program to a major degree. To support a package, we must be reasonably convinced that upstream supports and cares for the package.
- The package is maintained well in Debian/Ubuntu (check out the Debian PTS)
- The package should not deal with exotic hardware which we cannot support.
- If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build.
- The package uses a debian/watch file whenever possible. In cases where this is not possible (e. g. native packages), the package should either provide a debian/README.source file or a debian/watch file (with comments only) providing clear instructions on how to generate the source tar file.
It is often useful to run lintian --pedantic on the package to spot the most common packaging issues in advance
- The package should not rely on obsolete or about to be demoted packages. That currently includes package dependencies on Python2 (without providing Python3 packages), and packages depending on GTK2.
UI standards: (generally only for user-facing applications)
- End-user applications must be internationalized (translatable), using the standard intltool/gettext build and runtime system and produce a proper PO template during build.
- End-user applications must ship a standard conformant desktop file.
All binary dependencies (including Recommends:) must be satisfiable in main (i. e. the preferred alternative must be in main). If not, these dependencies need a separate MIR report (this can be a separate bug or another task on the main MIR bug)
Standards compliance: The package should meet the FHS and Debian Policy standards. Major violations should be documented and justified. Also, the source packaging should be reasonably easy to understand and maintain.
Maintenance: The package must have an acceptable level of maintenance corresponding to its complexity:
- All packages must have a designated "owning" team, regardless of complexity, which is set as a package bug contact.
- Simple packages (e.g. language bindings, simple Perl modules, small command-line programs, etc.) might not need very much maintenance effort, and if they are maintained well in Debian we can just keep them synced
- More complex packages will usually need a developer or team of developers paying attention to their bugs, whether that be in Ubuntu or elsewhere (often Debian). Packages that deliver major new headline features in Ubuntu need to have commitment from Ubuntu developers willing to spend substantial time on them.
- The package descriptions should explain the general purpose and context of the package. Additional explanations/justifications should be done in the MIR report.
- If the package was renamed recently, or has a different upstream name, this needs to be explained in the MIR report.
- Check how many vulnerabilities the package had in the past and how they were handled by upstream and the Debian/Ubuntu package:
http://cve.mitre.org/cve/search_cve_list.html: Search in the National Vulnerability Database using the package as a keyword
check OSS security mailing list (feed 'site:www.openwall.com/lists/oss-security <pkgname>' into search engine)
- Ubuntu CVE Tracker
- Check for security relevant binaries. If any are present, this requires a more in-depth security review.
Executables which have the suid or sgid bit set.
Executables in /sbin, /usr/sbin.
Packages which install services / daemons (/etc/init.d/*, /etc/init/*, /lib/systemd/system/*)
Packages which open privileged ports (ports < 1024).
- Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc)