Russ Allbery <rra@debian.org> writes: > Simon Josefsson <simon@josefsson.org> writes: >> Ian Jackson <ijackson@chiark.greenend.org.uk> writes: > >>> No. The git commitid of the upstream source is named in the tag >>> generated by git-debpush. (So that upstream git branch has to be in >>> your git repo somewhere - just not in your branch.) The t2u server >>> will use that (ultimately, via git-archive). > >> How does t2u find out the URL to the upstream git repository? Is >> https:// enforced, or are http:// or git:// URLs supported? Is the >> upstream git branch recorded anywhere, or just the commit? > > My understanding is that there is no separate upstream Git repository. I > believe that's what Ian means by "the upstream Git branch has to be in > your Git repo somewhere." In other words, you have to push upstream to > your Salsa packaging repository to use tag2upload, but you don't have to > merge it with your packaging branch. Oh. That doesn't rime well with some people's git workflow, but that is consistent with the t2u approach serving a subset of all package maintainers. This is the most relevant documentation that I can find: https://salsa.debian.org/dgit-team/dgit/-/blob/dc9f26a84d34ffc4438252e7caf3bde24090e4ed/tag2upload.5.pod#L108 /Simon
Attachment:
signature.asc
Description: PGP signature