Translation(s): none


After you have successfully built the package with dpkg-buildpackage and made sure it is lintian clean, checked with pbuilder if all dependencies are added to debian/control and send an ITP, it is time to upload it to the debian gitlab service (

For that you will need to create a new dsc file in a temporary directory, so that all of your changes are listed in the git history.

A repo in your namespace is used instead ofruby-team at salsa.

The same problem is described at the ruby-team packaging page:

It might be clearer there.


Make an account at salsa. Create an ssh-key ?installing ssh-keys and add it to your gitlab account via web-interface.

In short you run:


to create an ssh-key, and upload the public key, which ends with .pub. If you have picked a custom name you can add the following to ~/.ssh/config (if it does not exist yet just create the file):

User git
PreferredAuthentications publickey
IdentityFile ~/.ssh/custom_name_gitlab_rsa

Simply replace the path to your key in the last line.

git remote add

Create a repository add the team site via webinterface. Add it as remote to your git repo:

git remote add origin<your salsa username>/ruby-devise.git

Remove the debian tag:

git tag

to list it and

git tag -d debian/2.1.2-1 # if you have not removed it already

to remove it (2.1.2-1 in this case. Use what git tag shows you)

push the changes to the git-repo at salsa

git push -u --all --follow-tags

gbp buildpackage

Note: To build your package from the git repo, use gbp buildpackage command.

When you want to build the package on a different machine or you want to build a package already available in salsa.

gbp clone --pristine-tar<your salsa username>/ruby-devise.git
cd ruby-devise
gbp buildpackage