Hello,
On Thu, Feb 12, 2026 at 06:00:50PM +0000, Ian Jackson wrote:
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.
That was more or less what I had to do, actually, and aide
0.19.2-3exp1 seems to have made it to the archive okay.
Two minor things. My ~/.gbp.conf contains
[buildpackage]
export-dir=../build-area
tarball-dir=../tarballs
since I am not too fond of my parent directory being cluttered with
build artifacts. for dgit rpush, I had to move the origtargz to my git's
parent directory, and the build artifacts were palced there. Is that
configurable in dgit? It would be nice if digit would read gbp's
configuration here, or have its own configuration to influence this.
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!
Yes, and most of the docs handle a very special case, doing NMUs or
security updates.
If you're hesitant, you could try uploading to experimental maybe.
Done.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
