On Wed, Feb 08, 2017 at 01:36:13PM +0100, Wouter Verhelst wrote: > On Thu, Jan 19, 2017 at 06:20:30PM +0100, Michael Stapelberg wrote: > > Would a mirror of the git repository on alioth be sufficient? I had > > planned to set that up, but didn’t get around to it yet. Any help with > > that would be very welcome. > > I realize you've already done so, but for future reference, this is > ridiculously easy for anyone who's a Debian Developer or otherwise has > an account on alioth: > > ssh to git.debian.org, and run: > > mkdir -p public_git/repo.git > cd public_git/repo.git > git init --bare > > log out again; then, in your local repository, run: > > git remote add --mirror debian git.debian.org:public_git/repo.git > git push debian > > you're done. > > Alternatively, if you don't want to push all branches, drop the --mirror > part on the 'git remote add' thing, and add a branch to every "git push > debian" command. This works for all remotes btw, not just the alioth > ones.
If using git-buildpackage there's also a "gbp create-remote-repo" defaulting to colab maint to ease repo setup. To get the above you would use a config like: [remote-config alioth] remote-url-pattern = ssh://git.debian.org/~/public_html/%(pkg)s.git in your ~/.gbp.conf and from there on just: gbp create-remote-repo --remote-config=alioth from you any packaging dir to create a remote repo there and push things initially. > > Personally, I tend to push my code to multiple git hosting services, > because it's so simple to do. > > -- > < ron> I mean, the main *practical* problem with C++, is there's like a dozen > people in the world who think they really understand all of its rules, > and pretty much all of them are just lying to themselves too. > -- #debian-devel, OFTC, 2016-02-12 >
