Develop Packaging

Packages maintained by the Debian Multimedia Team

Here you can find a list of packages maintained by the Debian Multimedia Team: (deprecated)

New packages should set the Maintainer field to Debian Multimedia Maintainers <>. Existing packages should move to using that address on a best-effort basis.

All source packages must be hosted at multimedia-team on Salsa.

How to help with packaging

The Debian Multimedia Maintainers need help to create new Debian packages and maintain the existing ones. If you want to contribute to this effort, but you are new to the Debian packaging systems, here follows some information to get you started. Also see DebianMultimedia/Sponsoring for Best Practices with regard to obtaining sponsorship for your uploads if you are not a DD or DM.

Packaging guidelines

Workflow guidelines


Proposing new packages for the Multimedia Team

Working on existing packages with git for newbies

$ gbp clone --pristine-tar

$ git pull --rebase origin

$ git pull origin

$ git rebase -i origin/master

Common tasks for team members

Uploading proposed package to the team git repository

$ cd /path/to/sources/
$ gbp import-dsc --pristine-tar <project>_0.0.1-1.dsc
$ cd <project>
$ git remote add origin<project>.git
$ git push origin master upstream pristine-tar --follow-tags

$ git tag -d debian/0.0.1-1

Uploading new upstream version to existing repository

Removing/Adding debian tags to repository

Common configuration options

These parameters should be placed in the debian/gbp.conf file. (uncomment compression line if upstream tarball(s) are not gzip-compressed)

pristine-tar = True
#compression = bzip2

If you adopt the dpkg source format 3.0 (quilt) you should:

* Add this to debian/source/format file

3.0 (quilt)

* Add this to .gitignore file


Bugs for packages found in DMO

If there is a bug that is not found in the Debian version of a package but found only in the DMO version of the package, it is helpful to mark such bugs with a usertag. The procedure we take to mark such bugs is as follows.

Send an email to close the bug ( and also to the BTS bug control interface ( Closing the bug will automatically notify the submitter of the bug as well. The contents of the email must begin with the following lines.

usertags NNNNNN dmo
tags NNNNNN = unreproducible
notfound NNNNNN <version1>
notfound NNNNNN <version2>
notfixed NNNNNN <version1>
notfixed NNNNNN <version2>

These lines are read by the BTS bug control interface. The 'user' line must be set to '' so that the usertag can be set. The 'usertags' marks the bug with the usertag 'dmo'. The 'tags' line will reset all tags on the bug so that it will only contain one tag, the 'unreproducible' tag. The 'notfound' lines removes all instances where the BTS says the bug is found. These lines need to be added for each version the BTS says the bug is found against. In case the BTS says there are versions of the package the bug is fixed, the 'notfixed' lines must also be added just like the 'notfound' lines to unmark all versions where the BTS says the bug is fixed. Finally, the 'stop' line stops processing for the BTS control interface.

After the 'stop' line, write a message explaining that this bug does not exist against the version of the package in Debian and is being close and marked as such. It's also helpful to recommend users to report the bug to dmo.

All such marked bugs can be viewed at;

Work in progress : We're checking all the WNPP bugs and updating infos on this page.