Bug 1416829 - golang-googlecode-google-api-client: update to a recent version
Summary: golang-googlecode-google-api-client: update to a recent version
Alias: None
Product: Fedora
Classification: Fedora
Component: golang-googlecode-google-api-client
Version: 26
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Fridolín Pokorný
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-26 14:46 UTC by Frantisek Kluknavsky
Modified: 2018-05-29 11:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-29 11:22:48 UTC
Type: Bug

Attachments (Terms of Use)

Description Frantisek Kluknavsky 2017-01-26 14:46:09 UTC
Description of problem:
Upstream git repo contains code which is not present in Fedora yet. Updating will allow to unbundle  'golang(google.golang.org/api/iterator)' and 'golang(google.golang.org/api/option)'

Version-Release number of selected component (if applicable):

Comment 1 Jan Chaloupka 2017-01-26 17:35:42 UTC
Which version is that? 0.6.0 https://github.com/GoogleCloudPlatform/google-cloud-go/releases/tag/v0.6.0 ?

Comment 2 Fedora End Of Life 2017-02-28 11:04:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 3 Ed Marshall 2017-03-05 03:21:34 UTC
Jan, I believe you're thinking of golang-google-golangorg-cloud.

This bug is for golang-googlecode-google-api-client, located at: https://github.com/google/google-api-go-client

There's been at least two new APIs added to it since the release in fedora, "iterator" and "option".

Comment 4 Ed Marshall 2017-10-09 21:57:47 UTC
Something else to note as part of an update to this package: the import paths have changed across the board: https://code.google.com/archive/p/google-api-go-client/

    This has moved to Github:
    And the new imports are of the form "google.golang.org/api/storage/v1"
    To avoid breaking users, this code will stay here, but will not be updated.

Most of the Provides in this package will need to be updated, and even then, the package name is technically "wrong".

Maybe it would be better for a new package to be rolled under the new name that provides all the new paths, and leave this one frozen in time like the upstream project?

Comment 5 Fedora End Of Life 2018-05-03 08:08:56 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2018-05-29 11:22:48 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.