Hi Daniel, On 29/02/2024 12:42 am, Daniel Swarbrick wrote:
In the case of azure-sdk-for-go, I see that upstream has tags in the form of "sdk/azcore/vX.Y.Z" (among many others). Can we assume that "azcore" is as close an analog as we are going to get to the former simple "vX.Y.Z" tags?Several large libraries (e.g. aws-sdk-go-v2) seem to now publish releases almost daily, which simply isn't rational or feasible for Debian packagers to track. We need to identify which releases are actual major milestone releases, and not merely a dependency bump in go.mod due to some overly eager dependabot.
+1We could just version by git commits rather than relying on the upstream's separate versioning.
Obviously we will need to bump the epoch on such packages where the new upstream tagging convention would result in a lower version number than what is currently packaged.Could we avoid bumping the epoch by suffixing the version with the git commit? e.g. for the case of azure-sdk-for-go, the next version would be 68.0.0+git20240229.d33ad0-1s
Kind regards, Maytham
OpenPGP_0xD597897206C5F07F.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
