Marc Haber writes ("Re: tag2upload general availability"):
> So all I need to do is like
> gbp buildpackage -S
> dgit puhs-source ../build-area/*_source.changes?You don't need torun gbp buildpackage -S. You don't need to specify any .changes file. dgit push-source builds the source package itself (and double-checks that it is identical to your git). So instead, assuming you're using patches-unapplied, dgit --gbp push-source is the only command to run. > I find it confusing to have to use two different tools, one of them > incredibly complex, with documentation only grokkable if you' eat git > plumbing for breakfast, and the other one brand-new, for essentially the > same task. I can see this point of view. One problem with dgit's documentation is that dgit is, actually, a fully general bidrectional gateway between git (including Debian's various git branch formats) and Debian-style archives. That necessarily means it has a lot of ways it can be used! I would encourage you to try it though. It's really quite bulletproof. When people have trouble with it, their usual complaint is that it keeps complaining about things and won't do its job. We've gone to a great deal of effort to avoid it making messes. If you're hesitant, you could try uploading to experimental maybe. Ian. -- Ian Jackson <[email protected]> These opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
