git-packaging workflows

Jonas Smedegaard dr at jones.dk
Fri Aug 22 15:47:12 UTC 2014


Quoting Felipe Sateler (2014-08-22 17:08:17)
> Resurrecting an old thread
> 
> On Sat, Apr 6, 2013 at 4:32 AM, Reinhard Tartler <siretart at gmail.com> wrote:
>> Recently, Russ' blog post was echoed on http://planet.debian.org:
>>
>> http://www.eyrie.org/~eagle/journal/2013-04/001.html
>>
>> In that post, he describes how to combine both the "import tarball" 
>> and the "have upstream history" available in the upstream packaging 
>> branch. AFAIUI, the heavy work is implemented in git-buildpackage's 
>> --upstream-vcs-tag <tag> option.
>>
>> While that option is news to me, I wonder if maybe anyone else 
>> already experiments with this? Does the team feel that making it 
>> mandatory for our package would be beneficial and appropriate?
>
> I know some in the team have experimented with this new workflow. 
> Could you share your experiences with it? I'm thinking that we should 
> encourage this workflow a bit more: it makes collaboration with 
> upstream easier (in both directions). However I'm still not too clear 
> on what would it look like, so I'd like to hear from people that have 
> been using it about their thoughts.
> 
> Questions of interest: are you using gbp pq? If not, how do you pick 
> patches from upstream? How do you post patches back to upstream?

I don't use gbp pq.  I only "follow the stream" - i.e. I treat upstream 
as someone "up the stream" from me when doing Debian work - I only track 
their work, don't try do two-way sync.  I pass patches back upstream 
using plain old patch files.


> I do think we need to somehow restrict the commits that get posted on 
> the commit list. Sometimes we get a mailbomb of new commits... :p

Try talk to those in the Perl team who knows about irc bots running 
there (i.e. not me): here's an example of how it looks when I "mailbomb" 
a new git-tracked upstream source related to that team:

(16:31:50) KGB-0: Jonas Smedegaard master 12cbc4c meta .mrconfig add mrconfig for libmoox-cmd-perl * http://deb.li/VLUx
(16:31:53) KGB-2: master 1297c0d libmoox-cmd-perl Branch 'master' created * http://deb.li/3No1E
(16:31:53) KGB-2: Jonas Smedegaard master 2888cb5 libmoox-cmd-perl (12 files in 3 dirs) Initial packaging. * http://deb.li/Ron4
(16:31:54) KGB-2: Jonas Smedegaard pristine-tar 5aeb49a libmoox-cmd-perl libmoox-cmd-perl_0.009.orig.tar.gz.delta libmoox-cmd-perl_0.009.orig.tar.gz.id pristine-tar data for libmoox-cmd-perl_0.009.orig.tar.gz * http://deb.li/3qldD
(16:31:54) KGB-2: Jonas Smedegaard upstream 1297c0d libmoox-cmd-perl New branch with 47 commits pushed
(16:32:02) KGB-0: Jonas Smedegaard libmoox-cmd-perl Pushed 0.001, 0.002, 9 other tags and upstream/0.009


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20140822/2af554bd/attachment.sig>


More information about the pkg-multimedia-maintainers mailing list