rott_1.1.2+svn287-3_source.changes ACCEPTED into unstable

[Simon McVittie]

On Mon, 15 Jan 2018 at 12:47:29 +0100, Fabian Greffrath wrote:
> Say, how did you migrate the GIT repo from alioth to salsa? Using scp or
> is there some more elaborate approach?

https://wiki.debian.org/Salsa/Doc#Import_git_repository

I've mostly been using the web UI rather than the script, since I'm
currently only migrating packages that I'm also editing at the same time.
There's some setup that I think we should have, but for which I don't
currently have automation, so I'm using the web UI or git(1) for these
anyway:

* set a memorable avatar (icon) for the game, assuming one is available
* email push notifications to dispatch at tracker.debian.org
* set up the tagpending web hook
* set the new VCS in debian/control
* push the "Move to salsa" commit to alioth as a hint to contributors
* install a pre-receive hook on alioth so no further commits are allowed

and tbh this is often a good opportunity to do a general packaging
refresh (for instance I expect that 99% of our games could
use Rules-Requires-Root: no to avoid suffering from fakeroot
bugs/limitations).

While I'm moving things around anyway, I'm tempted to move
non-native packages to DEP-14 branch names (usually debian/master and
upstream/latest), but so far I've only been doing that on packages where
I'm the main uploader (so not today's rott and opentyrian uploads).

    smcv