Hello list, Thanks for the info. I worked on `debian/experimental` branch on top of Peymaneh Nejad's previous WIP update, successfully updated golang-google-cloud package to version 0.115. I listed the versions of all the submodules in d/changelog: https://salsa.debian.org/go-team/packages/golang-google-cloud/-/merge_requests/1
Question to the team: I found the `debian/sid` branch contains more uploaded debian version from 0.56.0-2 until 0.56.0-6 which doesn't in sync with `debian/experimental`. Not sure how go-team noramlly handles sync'ing between sid and experimental branches? However, to make the merge request only contains fast-forward only commits, I also rebased my changes on top of `debian/sid` branch: https://salsa.debian.org/go-team/packages/golang-google-cloud/-/merge_requests/2 Because I intend to get newer google-cloud package into experimental first. I'm thinking of clean up by drop current `debian/experimental` branch and then re-create a sync'ed branch from `debian/sid`. Any objection or a better way? I would proceed the clean up if I don't heard anything in the end of the week. Best regards, -Andrew On Sat, Jan 24, 2026 at 6:15 PM Stephen Kitt <[email protected]> wrote: > > On Fri, 23 Jan 2026 15:21:43 +0100, Andrew Lee <[email protected]> wrote: > > On Fri, Jan 23, 2026 at 3:15 PM Simon Josefsson <[email protected]> wrote: > > > What is your proposal, to be clear? Packaging google-cloud as a > > > separate package, even if severely stripped down, is fine. I wouldn't > > > vendor any of these files, these aren't small or trivial packages... > > > > I relized I was wrong. Even the upstream provides a git tag as > > `auth/v0.17.0`. It still contains the whole google-cloud source package. > > See https://go.dev/ref/mod#vcs-version to understand how tags with submodules > should be interpreted. auth/v0.17.0 applies to everything under auth/, even > though the tree given by the tag contains everything. > > Regards, > > Stephen -- -Andrew
