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:
|/AliothMigration /Doc /FAQ /SSO|
- How do we migrate X from Alioth?
- What can be hosted on salsa
1.1. How can I verify the ssh key for salsa.debian.org?
Like all debian.org 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 *.debian.org VerifyHostKeyDNS yes EOF
If you have already verified the SSH host key of a debian.org host, you can download the full Debian SSH host key list over SSH from any debian.org host:
scp master.debian.org:/etc/ssh/ssh_known_hosts ~/.ssh/debian_known_hosts
If you haven't verified the SSH host key of any debian.org 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/DST_Root_CA_X3.crt -O ~/.ssh/debian_known_hosts https://db.debian.org/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 debian.org hosts:
$ cat >> ~/.ssh/config <<"EOF" Host *.debian.org UserKnownHostsFile ~/.ssh/debian_known_hosts EOF
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 db.debian.org -b ou=hosts,dc=debian,dc=org host=godard sshRSAHostKey $ wget --ca-directory /dev/null --ca-certificate /usr/share/ca-certificates/mozilla/DST_Root_CA_X3.crt https://db.debian.org/machines.cgi?host=godard -qO- | grep -o ssh-.* | sed 's/<br>/\n/g' >> ~/.ssh/known_hosts
1.3. How can I use salsa.debian.org 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 notifications. 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 https://salsa.debian.org/debian/htop/commit/0f48ae64dae.patch will get you a plain text patch of the commit 0f48ae64dae.
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 lists.debian.org. 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 lists.debian.org or to a separate service, or to a tracker.debian.org 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?
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.