[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Migration from Alioth to Salsa

On 03/31/2018 09:35 AM, Sebastiaan Couwenberg wrote:
> On 12/26/2017 11:08 AM, Sebastiaan Couwenberg wrote:
>> Yesterday I started to import the git repositories from Alioth manually,
>> because I didn't find a comfortable API. Today I continued using
>> Christoph Bergs salsa-import script [1]. Importing large repositories
>> (e.g. gdal, mapnik, etc) tends to fail, which requires creating the bare
>> repository manually and pusing all branches and tags to Salsa from a
>> checkout. At the time of writing the imports for the qgis &
>> qgis-upstream repositories in still in progress, and these are likely to
>> fail as well.
> Now that the SSL issues with the GitLab pages have been fixed. It's a
> good time to migrate to Salsa officially.
> All the repositories on Alioth have been locked, they don't accept
> pushes any more, and show a message that the repository has been moved
> to Salsa.
> Please update your working copies by changing the origin URL:
>  git remote set-url origin \
>  https://salsa.debian.org/debian-gis-team/<package>.git
>  git remote set-url --push origin \
>  git@salsa.debian.org:debian-gis-team/<package>.git
> Instead of <package> you can use $(basename $(pwd)) if working copy
> directory matches the repository name.

The Vcs-* fields in pretty much all packages have been updated, but no
uploads have been done so far.

For packages in (old)(old)stable the Vcs-* fields won't be updated, and
the redirect for anonscm.debian.org to salsa.debian.org should take care
of most usage (all HTTP requests). The PR for the AliothRewriter has not
been merged at time of writing yet:


All git:// & git+ssh:// URLs need to be changed manually.

Kind Regards,


Reply to: