Joining pkg-multimedia team

Ross Gammon ross at
Tue May 17 17:55:06 UTC 2016

On 05/16/2016 04:38 PM, Lucio Carreras wrote:
> Hi Ross, thank you!

You're welcome :-)

> But I don't find a tutorial that mentions how to upload the public key
> for the git repository.
> only tells that I should use ssh but
> I get a public key error. may be better.

> Other issues:
> 1. The Packaging with Git tutorials says, that I just have to call
>      gbp import-dsc /path/to/package_0.1-1.dsc
>    It's true, everything is imported but the directory structure is not as
>    it is described in the tutorial
>      $ ls
>      package/
>      package_0.1-1.orig.tar.gz

I would do:
mkdir sayonara
cd sayonara
git init
gbp import-dsc --pristine-tar /path/to/package_0.1-1.dsc

(It is also a good idea to add the --sign-tags option to the import
command, to sign the tags with your gpg key at the same time. But you
can always do it later).

>    In my case there's no tar.gz file in the repository afterwards and no
>    extra directory of my package. Just the files and directories which are
>    located inside the my source tree. Also the debian directory shows up
>    in the upstream as well as in the master branch. git diff master
> upstream
>    shows no diffs between master and upstream. The tags are available.

The tarball should not be inside the repository. When you do the next
upstream release, you normally run uscan from inside the repository,
which downloads the tarball to ../ and renames it to *orig.tar.gz. Then
import it with:
gbp import-orig --pristine-tar /path/to/package_0.1-1.dsc

Using --pristine-tar, because this allows someone else (e.g. me) to
recreate the tarball from the git repository without having to download
it manually.

> 2.
>    "The git repository should be hosted in alioth, under the pkg-multimedia
>    project. It should forward commit messages to
>    pkg-multimedia-commits at and
>    dispatch+package at"
>    I am relatively new to git and I could not find anything in the www. How
>    can I do that?

Don't worry - I have already done it :-)

Once you have the import sorted out, and the SSH key up at Alioth, you
can push the repository using:
$ git remote add origin
$ git push --all --set-upstream
$ git push --tags

>    "Do not commit debian/changelog along with the changes. This practice
> makes
>     cherry picking and backporting changes unnecessarily hard."
>    How do users and especially testers know what has changed?

Just do the changelog last. You can automate a lot of this using gbp dch
(and editing out all the mistake commits that the users don't need to
read :-) )

>    "To indicate that the package is ready for upload, update
> debian/changelog
>    to include the target distribution"
>    I thought I should not commit it?

Some of the documentation out there is contradictory, as different
Debian Teams have slightly different workflows. I normally do the
changelog after I have finished a series of commits, and it is either
ready for upload, or I don't plan to do any more work for a while.
Someone else on the team can then pick it up and finish it if they have
the urge (normally after checking with you first).

> As you can see, I am a little bit confused right now. Any help is
> appreciated.

I hope that helps! Otherwise, just keep asking.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the pkg-multimedia-maintainers mailing list