Hi Simon, On Wed, Aug 26, 2026 at 9:25 AM Simon Josefsson <[email protected]> wrote: > While hunting from zombie packages, I found some archived GitHub > projects as upstreams. That by itself is a serious QA signal.
Thank you for hunting these archived upstream. > Found total of 164 archived Go packages > | > [golang-github-aws-aws-sdk-go](https://tracker.debian.org/pkg/golang-github-aws-aws-sdk-go) > | 16381 115 0 7 2 106 | This brings my attention. After checked the module status on https://pkg.go.dev. I found it says: Warning Deprecated: aws-sdk-go is deprecated. Use aws-sdk-go-v2. Details: https://pkg.go.dev/github.com/aws/aws-sdk-go And from it's go.mod: // Deprecated: aws-sdk-go is deprecated. Use aws-sdk-go-v2. // See https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/. Details: https://github.com/aws/aws-sdk-go/blob/main/go.mod >From these we learnt. We should keep the package as identical as upstream's `Go Import Path` with the major versioning in it's package name. I am preparing a document for Module-Aware Builds transition, I will try to cover all these into the document and publish on wiki ASAP. Best regards, -Andrew
