On 18/01/18 04:30 PM, Michael Stapelberg wrote: > Thanks for the draft! Comments inline: > > On Wed, Jan 17, 2018 at 10:31 PM, Alexandre Viau <[email protected] > <mailto:[email protected]>> wrote: > > You might want to wait a couple of days after the migration before > spending time doing this because I might automate it for all > repositories. > > > Let’s figure this out before starting the process :). I’m in favor for > automating the step. The less people have to do mindless work that can > easily go wrong, the better (as evidenced by a number of incorrect > Vcs-* tags in our packages).
Alright, done. I have updated my migration script to edit Vcs-* urls! (https://salsa.debian.org/aviau/migrate-pkg-go-to-salsa) It does not create a changelog entry yet, but I'll fix that before the migration. > > > - A copy of the migrated repositories will remain available in > > > “A read-only copy” please. Okay, I agree. > > > git.debian.org:/git/pkg-go/packages-migrated-to-salsa > > - You will still be able to create repositories on Alioth, but there > will be no other bulk migration. > > - If all went well, we might disable repository creation on Alioth a > couple of days after the migration. > > > I’d like to disable repository creation at the start of the migration. > There’s no point in allowing backslide/stragglers like that. > Everything should be in one place. Okay, but can you allow me to do that? You are the only owner of the setup-repository script. I would just `chmod -x setup-repository`. That would be my new draft announcement: ``` Dear pkg-go contributors, I will be migrating all of pkg-go's Alioth repositories to salsa.debian.org <http://salsa.debian.org/> on <date>. === About the migration === - A mail will be sent to [email protected] <mailto:[email protected]> when the migration starts and when it ends - All repositories in git.debian.org:/git/pkg-go/packages will be migrated to the pkg-go-team group on salsa.debian.org <http://salsa.debian.org/>[1] You should join the group if you are not already in it! - Repositories will keep the same name, with ".git" removed. - HTTP anonscm.debian.org <http://anonscm.debian.org/> links of migrated repositories will be redirected to the new location. for example, you can test the following links: - https://anonscm.debian.org/cgit/pkg-go/packages/syncthing <https://anonscm.debian.org/cgit/pkg-go/packages/syncthing> - https://anonscm.debian.org/git/pkg-go/packages/syncthing.git <https://anonscm.debian.org/git/pkg-go/packages/syncthing.git> - Vcs-* urls will be automatically replaced in debian/control - Repository creation on Alioth will be created when the migration starts. It will not be re-enabled. === During the migration === - You may still push to Alioth. However, your pushes could be denied because the repository no longer exists.Don't panic! It was moved to Gitlab. If you push to Alioth during the migration, take a moment to confirm that your changes are available on salsa after the migration, just in case there was some sort of race condition. - You may start using salsa repositories immediately after they are created. No need to wait for the migration to end. === After the migration === - A read-only copy of the migrated repositories will remain available in git.debian.org:/git/pkg-go/packages-migrated-to-salsa - You may point your git working directories to the new remote address with this oneliner: ``git remote set-url origin [email protected]:pkg-go-team/$(git config --get remote.origin.url | tr "/" "\n" | tail -n 1)`` 1. https://salsa.debian.org/pkg-go-team <https://salsa.debian.org/pkg-go-team> Cheers, ``` We will wait for an answer from tincho before we pick a date, but do you have any other comments on the announcement? Thanks, -- 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
