Holger Levsen writes ("Re: [RFC] General Resolution to deploy tag2upload"):
> the RFC for this GR only links to some design documents, at least
> that's what the RFC says, I haven't followed those links yet.
>
> And it certainly doesnt describe a (minimal) version/git tag/release of said
> implementation.
I think we probably need to provide more links, then.
Let me try to help.
The implementation is in src:dgit, which is maintained here:
https://salsa.debian.org/dgit-team/dgit
The tag generation is done by `git-debpush`:
https://salsa.debian.org/dgit-team/dgit/-/blob/master/git-debpush?ref_type=heads
The tag interpretation is done by `dgit-repos-server`
in its `tag2upload` invocation mode:
https://salsa.debian.org/dgit-team/dgit/-/blob/master/infra/dgit-repos-server?ref_type=heads
Source package construction etc. is done by calling out
to `dgit`, which embodies all the knowledge of how different Debian
git workflows (eg, the patches-unapplied git branches typically
used with git-buildpackage) correspond to source packages.
This latter is the really hard part, partly because there are multiple
git workflows, but also because there are a *lot* of wrinkly edge
cases even in the most common git packaging workflows. Happily
for tag2upload. `dgit push-source` already needs to be able to do all
this stuff and is extremely mature and robust.
The missing (not yet implemented) parts are the daemon(s) to receive
webhook requests, set up and tear down chroots, and so on. Plumbing
(albeing security-relevant plumbing), basically.
Hope this helps.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> 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.
