Bug 2239903 - Please update golang-cloud-google to latest
Summary: Please update golang-cloud-google to latest
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: golang-cloud-google
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Mikel Olasagasti Uranga
QA Contact: Fedora Extras Quality Assurance
URL: https://github.com/googleapis/google-...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-09-20 18:06 UTC by Mark E. Fuller
Modified: 2023-11-20 18:18 UTC (History)
2 users (show)

Fixed In Version: golang-cloud-google-0.110.9-1.fc40~bootstrap
Clone Of:
Environment:
Last Closed: 2023-11-20 18:18:51 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Mark E. Fuller 2023-09-20 18:06:48 UTC 
golang-google-{grpc, genproto} are dependent on a significant number of missing import paths compared to current Fedora version

I'm not really familiar or sure about how upstream is versioned, so I will try to assemble a PR, but if possible to update it would be very helpful

Reproducible: Always
Comment 1 Mikel Olasagasti Uranga 2023-09-20 18:19:31 UTC 
golang-cloud-google moved to modular releases, similar to what Azure is doing with their SDK. The issue is that they import path did not change compared with what Azure did. 

Help to build updated packages is welcome and the approach used for Azure's specs can be used for Google.
Comment 2 Mark E. Fuller 2023-09-22 13:21:04 UTC 
thanks for the quick and helpful response - will try to schedule some time to work on pushing this along in the next couple weeks
Comment 3 Fedora Update System 2023-11-20 18:17:03 UTC 
FEDORA-2023-f23d9c5057 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f23d9c5057
Comment 4 Fedora Update System 2023-11-20 18:18:51 UTC 
FEDORA-2023-f23d9c5057 has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.