Translation(s): English - Italiano

This page is maintained primarily by the administrators of Salsa to help spread knowledge about the service. You can also check the other Salsa-related pages:

1. Usage

1.1. How can I verify the ssh key for

Like all systems there are several options:

If you have a secure path to a DNSSEC enabled resolver (install unbound and use it for DNS), use the existing DNSSEC and SSHFP records by turning on SSH host key verification via DNS:

$ cat >> ~/.ssh/config <<"EOF"
Host *
 VerifyHostKeyDNS yes

If you have already verified the SSH host key of a host, you can download the full Debian SSH host key list over SSH from any host:

scp ~/.ssh/debian_known_hosts

If you haven't verified the SSH host key of any host yet, you can download the full Debian SSH host key list via HTTPS, pinned to the Lets Encrypt parent CA.

$ wget --ca-directory /dev/null --ca-certificate /usr/share/ca-certificates/mozilla/ISRG_Root_X1.crt -O ~/.ssh/debian_known_hosts

You can either append the full Debian SSH key list to your usual known_hosts file or store it in a separate file and configure SSH to look at it for hosts:

$ cat >> ~/.ssh/config <<"EOF"
Host *
 UserKnownHostsFile ~/.ssh/debian_known_hosts

You can also get the SSH host keys for salsa from the godard entry in Debian LDAP, which are also available via the web interface. You should then save these in your known_hosts file.

$ ldapsearch -ZLLL -x -h -b ou=hosts,dc=debian,dc=org host=godard sshRSAHostKey
$ wget --ca-directory /dev/null --ca-certificate /usr/share/ca-certificates/mozilla/ISRG_Root_X1.crt -qO- | grep -o ssh-.* | sed 's/<br>/\n/g' >> ~/.ssh/known_hosts

1.2. How can I use without JavaScript?

The gitlab web interface requires ?JavaScript for a lot of different features. The gitlab upstream developers are hostile to changing this. You won't be able to view replies to issues or reply to issues for example. If you are not going to turn on ?JavaScript you are probably better off deleting your account, using the GitLab API, using GitLab CLI frontends to the API (like salsa from devscripts) or only using it for git based operations.

One limited workaround is to set up an account on with Javascript enabled, send all notifications via email and send all updates via email and git.

1.3. How can I use via email?

It is possible to do a lot of things on GitLab via email, including creating and manipulating issues and merge requests. Most things can be done via email by replying to the notification. It is also possible to open issues via email. GitLab has quite a lot of text commands aka "quick actions"

1.4. How can I get a plain text patch for a single commit?

Append ".patch" to the URL for a commit. So will get you a plain text patch of the commit 0f48ae64dae.

2. Features

2.1. How can I create a mailing list?

For communication within a packaging team or with users you may want to create a mailing list on See the howto for requesting a new mailing list.

Legacy "commit" or "bug" mailinglists are superseded by the notification system of gitlab.

Former Alioth-based mailing lists can be partially migrated to or to a separate service, or to a address. See Salsa/AliothMigration#Import_mailing_list for details.

2.2. How do I create a Group? I see no button for that!

Group creation is disabled on the Debian GitLab instance, as we want to enforce namespacing guidelines. You can create a group for the team according to the namespacing guidelines from the signup page

2.2.1. Where is collab-maint?

The "debian" group performs a similar function.

3. How do we migrate X from Alioth?

Salsa/AliothMigration has documentation on what can be migrated and Alioth#Deprecation_of_Alioth goes through all the Alioth services and states what will happen to them.

4. What can be hosted on salsa

The answer is simple: As long as it is opensource and/or can be included in Debian, it is fine to use salsa. If in doubt, ask.