Andrew Lee <[email protected]> writes: > Hello team, > > I have been trying to update golang-google-cloud package. However I > didn't relized that was a huge package. It ran out of disk space in > sbuild due to only 24G available in /tmp is tmpfs. I end up tried to > build it in ~/sbuild on my disk instead. Also out of disk space and > took a lot time. > > And then after review the `go.mod` file in newer `golang-google-api`. > It seems only three submodules are required from cloud: > cloud.google.com/go/auth v0.17.0 > cloud.google.com/go/auth/oauth2adapt v0.2.8 > cloud.google.com/go/compute/metadata v0.9.0 > > I would like to package these three submodules to get > golang-google-api updated. If it's policy violation, please let me > know. And we should think of other way around then.
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... /Simon > Best regards, > -Andrew > > On Thu, Jan 22, 2026 at 12:39 PM Andrew Lee <[email protected]> wrote: >> >> Hi Simon, >> >> On Mon, Jan 19, 2026 at 10:30 AM Simon Josefsson <[email protected]> wrote: >> > >> > Good luck! Indeed, the difficulty in getting this package to build with >> > all changing build dependencies, and then making sure it doesn't break >> > any reverse build dependencies, has been the challenge AFAIK. So far, >> > I've been able to work around all dependencies on more recent >> > golang-google-cloud, but getting the latest into experimental (and then >> > unstable) would be great... >> >> Does this mean you have a more recent golang-google-cloud pckage >> already or working in progress? >> Mind to share under your own branch? So that I can test the newer >> golang-google-api package builds or not. >> >> Best regards, >> -- >> -Andrew
signature.asc
Description: PGP signature
