It will be migrated when we do the bulk migration. Until then, if you want to do the less work possible, I think that what Michael has said is fine:
- Create new repositories on salsa - Don't migrate anything, unless you update the rewritemap, setup the right branch permissions and hooks yourself. To create repositories on Salsa, please use dh-make-golang as it will setup branch permissions and hooks for you. It is not documented yet, but there is a command in dh-make-golang: - dh-make-golang create-salsa-project <projectname> FWIW not setting permissions and hooks isn't that bad because I will run a script that does it for all projects after the migration. Same thing goes for the rewritemap. Just make sure that whatever package we have in unstable points to the right git url so that we don't interfere with tools that try to do bulk work on our packages. On 2018-02-20 02:53 AM, Michael Stapelberg wrote: > Done. > > On Tue, Feb 20, 2018 at 8:30 AM, Arnaud > <[email protected] > <mailto:[email protected]>> wrote: > > >> >> >> >> For the repository we're talking about right now, I >> understand there's no need to bump the version right now, as >> long as I'm not sure it's needed. >> >> Should I just delete it, or at least take it out of the go >> packages group, and keep it as a personal repo ? >> >> >> Yes please (whichever of the two you prefer). >> > > I don't have the permission to delete the project from the go > packages group, at > https://salsa.debian.org/go-team/packages/golang-github-urfave-cli/edit > <https://salsa.debian.org/go-team/packages/golang-github-urfave-cli/edit>. > I think you can do it ? > > Thanks > > Arnaud > > > > > -- > Best regards, > Michael -- Alexandre Viau [email protected]
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-go-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
