On Tue, 2025-08-19 at 02:30 +0200, Drew Parsons wrote: > Package: wnpp > Followup-For: Bug #1059083 > > Drew Parsons wrote: > > Using 68.0.0+git* is a reasonable workaround for the upstream > > versioning challenge. My only request is that (in general at least) > > the tarball be taken from an official release tarball > > (https://github.com/Azure/azure-sdk-for-go/tags) not git HEAD. > ... > > e.g. sdk/internal/v1.11.2 → 68.0.0+git20250729.066f6f9+internal.1.11.2 > > Actually if this is to be a separate new package > golang-github-azure-azure-sdk-for-go-sdk-v2 not > golang-github-azure-azure-sdk-for-go-sdk > > then "0.0+git20250729.066f6f9+internal.1.11.2" > makes sense. Might as well drop the '68' if it no longer has meaning. > > (maybe even "2.0+git..." if it's "v2"). You've missed some existing discussion on this :) Currently the plan is: - Track HEAD. It doesn't matter if we're using tags or not, since one component will be tagged while another is in between versions. - Separate package so not to break things that rely on the old-style package. See: https://salsa.debian.org/go-team/packages/golang-github-azure-azure-sdk-for-go-sdk This was also discussed extensively on debian-go@l.d.o. The current blocker is d/copyright review, which I currently don't have time to do. -- Maytham
Attachment:
signature.asc
Description: This is a digitally signed message part