Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1272302 > unrolled thread

Bug#1059087: Out of date golang-google-api package

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1059087: Out of date golang-google-api package Andrew Lee <ajqlee@debian.org> - 2025-12-01 16:50 +0100
    Bug#1059087: Out of date golang-google-api package Simon Josefsson <simon@josefsson.org> - 2025-12-01 17:10 +0100
      Bug#1059087: Out of date golang-google-api package Andrew Lee <ajqlee@debian.org> - 2026-01-15 18:10 +0100
        Bug#991942: Out of date golang-google-api package Simon Josefsson <simon@josefsson.org> - 2026-01-19 10:40 +0100
          Bug#991942: Out of date golang-google-api package Simon Josefsson <simon@josefsson.org> - 2026-01-23 15:20 +0100
            Bug#991942: Out of date golang-google-api package Stephen Kitt <skitt@debian.org> - 2026-01-24 18:20 +0100

#1272302 — Bug#1059087: Out of date golang-google-api package

Hello List,

I have sent an email to all uploaders of golang-google-api package but
no answer yet for a week, so that I'm here asking on the list.

I saw the `golang-google-api` package stays in the same upstream
version from oldstable:
golang-google-api | 0.61.0-1      | oldstable    | source
golang-google-api | 0.61.0-6      | stable       | source
golang-google-api | 0.61.0-6      | testing      | source
golang-google-api | 0.61.0-6      | unstable     | source

I wonder if it's any specific reason to keep this verion without any update?

If there is there is still no input for any specific reason to stays
in this old verion for another week. I will hands on it to make an
updated version upload to experimental.

Best regards,
-- 
-Andrew

[toc] | [next] | [standalone]

#1272304

[Multipart message — attachments visible in raw view] — view raw

Hi.  Having a new version of this package is something I would want to
see too, it seems to be a required dependency of some packages I work on
(I try to patch things into something working but doing that isn't
sustainable).  Quite some time ago I started work on bringing it up to
0.157 but there is a lot of more fixing needed to get this to work:

https://salsa.debian.org/jas/golang-google-api/

So +1 on you preparing a experimental upload based on latest upstream
version.  I think you will find that all the new build dependencies is
not simple to resolve.  Then we can try reverse building everything that
depends on golang-google-api to see how much of Debian unstable breaks
(I fear quite a lot, but we need to start and fix it).

/Simon

Andrew Lee <ajqlee@debian.org> writes:

> Hello List,
>
> I have sent an email to all uploaders of golang-google-api package but
> no answer yet for a week, so that I'm here asking on the list.
>
> I saw the `golang-google-api` package stays in the same upstream
> version from oldstable:
> golang-google-api | 0.61.0-1      | oldstable    | source
> golang-google-api | 0.61.0-6      | stable       | source
> golang-google-api | 0.61.0-6      | testing      | source
> golang-google-api | 0.61.0-6      | unstable     | source
>
> I wonder if it's any specific reason to keep this verion without any update?
>
> If there is there is still no input for any specific reason to stays
> in this old verion for another week. I will hands on it to make an
> updated version upload to experimental.
>
> Best regards,

[toc] | [prev] | [next] | [standalone]

#1278555

Hello team and Simon,

I worked a bit on updating the `golang-google-api` package in my branch today.

It turns out that only an updated version of `golang-google-cloud` package is
missing now. See the log:
   https://salsa.debian.org/ajqlee/golang-google-api/-/jobs/8892146#L1648

I wonder if anyone who can update `golang-google-cloud` package?
It stays in the same version from oldoldstable:
```
golang-google-cloud | 0.56.0-1      | oldoldstable | source
golang-google-cloud | 0.56.0-3      | oldstable    | source
golang-google-cloud | 0.56.0-6      | stable       | source
golang-google-cloud | 0.56.0-6      | testing      | source
golang-google-cloud | 0.56.0-6      | unstable     | source
```

Any specific reason for keep the version this old for three Debian releases?

Best regards,
-Andrew

On Mon, Dec 1, 2025 at 5:04 PM Simon Josefsson <simon@josefsson.org> wrote:
>
> Hi.  Having a new version of this package is something I would want to
> see too, it seems to be a required dependency of some packages I work on
> (I try to patch things into something working but doing that isn't
> sustainable).  Quite some time ago I started work on bringing it up to
> 0.157 but there is a lot of more fixing needed to get this to work:
>
> https://salsa.debian.org/jas/golang-google-api/
>
> So +1 on you preparing a experimental upload based on latest upstream
> version.  I think you will find that all the new build dependencies is
> not simple to resolve.  Then we can try reverse building everything that
> depends on golang-google-api to see how much of Debian unstable breaks
> (I fear quite a lot, but we need to start and fix it).
>
> /Simon
>
> Andrew Lee <ajqlee@debian.org> writes:
>
> > Hello List,
> >
> > I have sent an email to all uploaders of golang-google-api package but
> > no answer yet for a week, so that I'm here asking on the list.
> >
> > I saw the `golang-google-api` package stays in the same upstream
> > version from oldstable:
> > golang-google-api | 0.61.0-1      | oldstable    | source
> > golang-google-api | 0.61.0-6      | stable       | source
> > golang-google-api | 0.61.0-6      | testing      | source
> > golang-google-api | 0.61.0-6      | unstable     | source
> >
> > I wonder if it's any specific reason to keep this verion without any update?
> >
> > If there is there is still no input for any specific reason to stays
> > in this old verion for another week. I will hands on it to make an
> > updated version upload to experimental.
> >
> > Best regards,



-- 
-Andrew

[toc] | [prev] | [next] | [standalone]

#1278971 — Bug#991942: Out of date golang-google-api package

[Multipart message — attachments visible in raw view] — view raw

Andrew Lee <ajqlee@debian.org> writes:

> Hi Maytham,
>
> Thank you for your reply. Append information to #991942 on BTS.
>
> On Sat, Jan 17, 2026 at 10:22 AM Maytham Alsudany <maytham@debian.org> wrote:
>>
>> On Thu, 2026-01-15 at 17:57 +0100, Andrew Lee wrote:
>> > It stays in the same version from oldoldstable:
>> > ```
>> > golang-google-cloud | 0.56.0-1      | oldoldstable | source
>> > golang-google-cloud | 0.56.0-3      | oldstable    | source
>> > golang-google-cloud | 0.56.0-6      | stable       | source
>> > golang-google-cloud | 0.56.0-6      | testing      | source
>> > golang-google-cloud | 0.56.0-6      | unstable     | source
>> > ```
>> >
>> > Any specific reason for keep the version this old for three Debian releases?
>>
>> AFAIK it's only due to the difficulty in updating the package. It has a
>> bunch of reverse build-dependencies that would need updating, and if my
>> memory serves me right, I'm pretty sure there's some circular dependency
>> issues as well between the latest upstream versions of the golang-
>> google-* packages.
>
> I found there is version `0.115.0` imported in git. I will continue to
> work on that and then upload to experimental.

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...

/Simon

[toc] | [prev] | [next] | [standalone]

#1279489 — Bug#991942: Out of date golang-google-api package

[Multipart message — attachments visible in raw view] — view raw

Andrew Lee <ajqlee@debian.org> 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 <ajqlee@debian.org> wrote:
>>
>> Hi Simon,
>>
>> On Mon, Jan 19, 2026 at 10:30 AM Simon Josefsson <simon@josefsson.org> 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

[toc] | [prev] | [next] | [standalone]

#1279640 — Bug#991942: Out of date golang-google-api package

[Multipart message — attachments visible in raw view] — view raw

On Fri, 23 Jan 2026 15:21:43 +0100, Andrew Lee <ajqlee@debian.org> wrote:
> On Fri, Jan 23, 2026 at 3:15 PM Simon Josefsson <simon@josefsson.org> 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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web