Update Git setup for Debian's move to Salsa
Closed, ResolvedPublic

Description

Debian KDE/Qt team has moved their stuff to Salsa which has not ssh access. Work out how to move our Git syncing setup to that.
https://salsa.debian.org/qt-kde-team/

repos on git.debian but not on salsa, mostly old and obsolete, some are ones I've added and not picked up yet by debian

-akonadi1
-alioth-tooling
-amarok
-appmenu-qt
-atcore
-automoc
-babe
-bangarang
-bespin
-calamares
-calamares-settings-debian
-charmtimetracker
-ci-tooling
-clazy
-colibri
-cutepaste
-debconf-kde
-elisa
-git-hooks
-gtk2-engines-oxygen
-hotspot
-isoimagewriter
-kamerka
-kannasaver
-kasync
-kcheckgmail
-kchildlock
-kcm-gtk
-kcm-tablet
-kdav2
-kde4pimlibs
-kdesrc-build
-kdesudo
-keurocalc
-kftpgrabber
-kgraphviewer
-kimap2
-kio-ftps
-kio-gdrive
-kio-mtp
-kio-stash
-kmarkdownwebview
-knmap
-kobby
-koko
-kpeoplevcard
-kpmcore
-krecipes
-kte-collaborative
-ktexteditorpreviewplugin
-kube
-kxstitch
-latte-dock
-libaccounts-glib
-libfli
-libindi
-libiodbc2
-libkpeople
-libkvkontakte
-libmediawiki
-libnm-qt
-libqinfinity
-libsignon-glib
-libspectre
-libutempter
-libvncserver
-libzip
-lightdm-kde
-mlt
-oxygen-gtk3
-oxygen-transparent
-partitionmanager
-patch-parser
-peruse
-pkg-kde
-pkg-kde-repository
-plasma-mycroft
-plasmate
-plasma-widget-fastuserswitch
-plasma-widget-menubar
-polkit-kde-1
-qca2-plugin-gnupg
-qca2-plugin-ossl
-qca-qt5
-qimageblitz
-qtdeclarative-render2d
-qtenginio
-qt-kde.debian.net
-qt-sdk
-qt-simulator
-qt-web-runtime
-quassel
-recorditnow
-redshift-plasmoid
-robojournal
-ruqola
-signond
-signon-plugin-oauth2
-signon-ui
-simon
-sink
-soprano
-spacebar
-telepathy-accounts-signon
-testy
-tora
-webkitkde
-wv2

repos have changed sub-directories

applications → kde
calligra→kde-extras
frameworks→kde
kde-extras→kde-extras
kde-req→phonon gone to kde-extras, qca-qt5 gone, others obsolete
kde-std→kde-extras
krap→3rdparty
plasma→kde
qt→qt
qt-extras→qt-extras

for the sync repos from debian side I've committed update-gitolite-setup-salsa.py and list-debian-repositories-salsa.py
Now I think I want to get a login to the server, stop the update gitolite script, move repos around and update remotes, then start the new update script

Restricted Application added a subscriber: sysadmin. · View Herald TranscriptMar 1 2018, 7:20 PM

Of the repos not copied over by Debian here's the ones I recon we want to save for Neon, either by talking to Debian and recreating them there or by moving to neon-packaging/

atcore
babe
calamares
elisa
hotspot
isoimagewriter
kasync
kcm-tablet
kdav2
kgraphviewer
kimap2
kio-gdrive
kio-stash
kmarkdownwebview
koko
kpmcore
kube
kxstitch
latte-dock
libindi
frameworks/kpeople
libkvkontakte
libkf5mediawiki5
mlt
partitionmanager
peruse
plasma-mycroft
kde-req/qca-qt5
ruqola
sink
spacebar

I've had a chance to review the scripts and they look fine to me, although I see we'll need to setup a API Token for access to Salsa.
In regards to the "kdeneon-guest" account on Alioth, I assume a similar one has been setup by you on Salsa?

In regards to shell access and switching things over, given this is going to be highly disruptive what I suggest we do is:

  1. Temporarily disable normal access to neon@code.kde.org
  2. Grant you and @sitter standard SSH access to that account so you can do the repository rearrangement. Note that you don't have to update the remotes in the repository manually as the update-gitolite-setup script will take care of that for you (assuming you do a full, non-incremental run)
  3. Normal access is restored to neon@code.kde.org, at which point you'll lose shell access.

I'd prefer not to keep standard shell access around due to the sensitivity of what this machine hosts. Historically only Sysadmins have been granted any form of unrestricted shell access to the machine.

Thoughts?

Ping on this?

Yes that sounds like a good plan

I have an account on salsa with an access token and can pass that over in some secure way

created .salsa-api-token in neon@code

bcooksley closed this task as Resolved.Mar 5 2018, 8:02 PM
bcooksley claimed this task.

This has now been sorted out with @jriddell on IRC.