Promoting a package into main

Scope

babl is a gegl dependency, which is needed for gimp 2.6 as the engine of new gimp version. Gimp is obviously in main and a MIR has been written for gegl.

Requirements

The package must fulfil the following requirements:

1. Availability: http://archive.ubuntu.com/ubuntu/pool/universe/b/babl; available for i386 and amd64

2. Rationale: There must be a certain level of demand for the package, for example:

   • New build dependency for gegl which is a dependency of Gimp 2.5 and so... 2.6, part of default installation
   • The package is a new build dependency or dependency of a package that we already support.

3. Security:

   • No CVE entries
   • No secunia history
   • No binaries running as root or suid/sgid. No daemon either.
   • Doesn't open any port

4. Quality assurance:

   • The package does not need configuration file (only ldconfig is called on configure)
   • No debconf call.

   • Debian bugs: no showstopper.

   • Maintenance in Debian is vigorous (relatively new package)

   • Upstream is vigorous (subteam of gegl)

   • No Upstream bug tracker (may be the same as gegl upstream buttracker)

   • Is there a test suite in the upstream source or packaging ? Is it enabled to run in the build ?

5. Standards compliance:

   • FHS and Debian Policy compliant

   • Debian library packaging guide standards compliant

   • Packaging system used is cdbs. No patch system.

6. Dependencies:

   • libbabl-0.0-0: libc6

   • libbabl-0.0-0-dev: libbabl-0.0-0 (included in this MIR)

   • libbabl-0.0-0-doc: no dependency

7. Maintenance:

   • It is a young project, with a simple package, but upstream seems to be reactive as this a new vital part of gimp.
   • This package may be managed by the desktop team as a dependency of gimp.

Reviewers

MIR bug: https://launchpad.net/bugs/279565

• DidierRoche (didrocks)