<br><div class="gmail_quote">On Wed, Jun 22, 2011 at 5:50 AM, Alessio Treglia <span dir="ltr"><<a href="mailto:alessio@debian.org" target="_blank">alessio@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>On Tue, Jun 21, 2011 at 10:36 AM, Jeremy Salwen <<a href="mailto:jeremysalwen@gmail.com" target="_blank">jeremysalwen@gmail.com</a>> wrote:<br>
> Alessio, in the workflow you described, the upstream.trunk branch is what I<br>
> was referring to as "intermediate packaging work"<br>
><br>
> I have an account on alioth (jeremysalwen-guest) and I requested to join the<br>
> team a little while ago, but I haven't been accepted yet.<br>
<br>
</div>I've added you, so... welcome aboard! :)<br>
<br>
I've already set up both lv2file and so-synth-lv2 repos:<br>
<div> <a href="http://anonscm.debian.org/gitweb/?p=pkg-multimedia/lv2file.git" target="_blank">http://anonscm.debian.org/gitweb/?p=pkg-multimedia/lv2file.git</a><br>
<a href="http://anonscm.debian.org/gitweb/?p=pkg-multimedia/so-synth-lv2.git" target="_blank">http://anonscm.debian.org/gitweb/?p=pkg-multimedia/so-synth-lv2.git</a><br>
<br>
</div>Your "upstream" branches on github have been merged into the<br>
respective UPSTREAM.trunk branches.<br>
To retrieve the code and set up your local copy:<br>
<br>
gbp-clone git+ssh://<a href="http://git.debian.org/git/pkg-multimedia/$PACKAGE.git" target="_blank">git.debian.org/git/pkg-multimedia/$PACKAGE.git</a><br>
cd $PACKAGE && git fetch origin UPSTREAM.trunk:UPSTREAM.trunk<br>
<br>
So now you are able to work as upstream by directly committing your<br>
changes to the UPSTREAM.trunk branches.<br>
When you feel comfortable with a certain state of things, please keep<br>
in mind what follows:<br>
<br>
* Use the capitalized form "UPSTREAM/%(version)s" to mark commits<br>
in your "trunk" branches in order to avoid conflicts with the<br>
"upstream/%(version)s" used when importing the new release into<br>
the upstream branches.<br>
* After tagging a new release, please create a tarball and follow the<br>
procedure described in our wiki:<br>
<br>
git-import-orig --pristine-tar ../$(PACKAGE)_$(RELEASE).orig.tar.gz<br>
<br>
Please don't forget the --pristine-tar option (which is set by default<br>
in the debian/gbp.conf config file, though), it is needed to avoid<br>
downloading stuff from the Debian archive at build time.<br>
For any question or if you don't like this way, let me know!<br>
<div><div></div><div><br>
Cheers,<br>
<br>
--<br>
Alessio Treglia | <a href="http://www.alessiotreglia.com" target="_blank">www.alessiotreglia.com</a><br>
Debian Developer | <a href="mailto:alessio@debian.org" target="_blank">alessio@debian.org</a><br>
Ubuntu Core Developer | <a href="mailto:quadrispro@ubuntu.com" target="_blank">quadrispro@ubuntu.com</a><br>
0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0<br>
</div></div></blockquote></div><br>Hi Alessio,<br><br>
How would I get access to the <a href="http://git.debian.org">git.debian.org</a> server? Right now I get
public key denied errors if I try to ssh in or do a non-anonymous clone.<br>
<br>
Jeremy<br>
<br>