Le 2025-05-14 20:52, Otto Kekäläinen a écrit :
The `gbp.conf` field `upstream-vcs-tag` (e.g. `upstream-vcs-tag = v%(version%~%-)s`) could probably be added as a new upstream metadata field if Jelmer and Guido agree on what to call it and how to roll it out in a backwards compatible way.
(...)
The only other field that might be generic is `upstream-signatures`
I'm not sure that upstream metadata is the right place for that kind of technical details. It would also be interesting to design this feature in a way that could eliminate the need for specific uscan configuration in most cases (gbp's upstream configuration strings are probably not sufficient for that purpose). Uscan could then be modified to use this feature by default, while still allowing more specific configuration where needed.
For the sake of deduplication deprecating the use of Homepage: in source d/control in favor of d/upstream/metadata might also be something worth doing; it could eventually be re-added in binary d/control at build time from branch d/upstream/metadata, or added by the toolchain to Packages indices from either branch or current (latest) upstream metadata.
Also concerning the Source field in d/copyright, personally I see it as the place from where the source was obtained when it was initially packaged (and in some cases that might be "the place where the source used to be published" which might no longer exist, or might no longer be usable); in other terms what's in this field is primarily there to help checking licensing compliance. In my view it's not meant to be kept up-to-date unless there are changes that are relevant for evaluating current licensing compliance.
Cheers, -- Julien Plissonneau Duquène