Russ Allbery <r...@debian.org> writes: > Ansgar 🙀 <ans...@43-1.org> writes:
>> It doesn't require dak to reproduce whatever steps tag2upload runs to >> generate the .dsc from that or source packages to be reproducible; the >> uploader only needs to know which files end up in the source package, >> something I would expect an uploader to know. > No, the uploader doesn't know this. Some of the files (the ones in > debian/patches) are synthesized from Git commits and do not exist at all > in the checkout of the Git tree, which will often be in patches-applied > form. I should have clarified: this is not *always* true, of course. There are simple cases such as packages with no patches to the upstream source, and there are maintainers who like workflows where they manually maintain the patches in debian/patches and thus have them on hand. But it is true in the general case, including in several popular Git workflows and a lot of interestingly complex packaging team standards that are supported correctly by the tag2upload design today. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
