Bug 2180539 - golang-github-vultr-govultr-2-3.0.2 is available
Summary: golang-github-vultr-govultr-2-3.0.2 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: golang-github-vultr-govultr-2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Major Hayden 🤠
QA Contact:
URL:
Whiteboard:
Depends On: 2185044
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-21 17:33 UTC by Upstream Release Monitoring
Modified: 2023-04-06 20:50 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-04-06 20:50:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2023-03-21 17:33:30 UTC
Releases retrieved: 3.0.0, 3.0.1
Upstream release that is considered latest: 3.0.1
Current version/release in rawhide: 2.17.2-3.fc38
URL: https://github.com/vultr/govultr

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/205451/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/golang-github-vultr-govultr-2

Comment 1 Major Hayden 🤠 2023-03-22 14:44:54 UTC
Made a PR for this update: https://src.fedoraproject.org/rpms/golang-github-vultr-govultr/pull-request/1

Also verified that vultr-cli builds fine with this update in place.

Comment 2 Major Hayden 🤠 2023-03-22 14:51:22 UTC
Oof, put this PR in the old govultr repo and not the new one. Fixing...

Comment 3 Major Hayden 🤠 2023-03-22 15:08:00 UTC
Will need to wait on the next vultr-cli release before we can update this package. There's a big upstream patch that needs to go in first:

https://github.com/vultr/vultr-cli/commit/cf376a593e28d56d78e790a2bab1bc6311f4f020

Comment 4 Upstream Release Monitoring 2023-03-31 19:08:31 UTC
Releases retrieved: 3.0.2
Upstream release that is considered latest: 3.0.2
Current version/release in rawhide: 2.17.2-3.fc38
URL: https://github.com/vultr/govultr

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/205451/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/golang-github-vultr-govultr-2

Comment 5 Major Hayden 🤠 2023-04-06 15:10:09 UTC
Per the packaging guidelines, we will need to make a golang-github-vultr-govultr-3 for this update.

https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/#_naming

Comment 6 Fedora Update System 2023-04-06 20:48:11 UTC
FEDORA-2023-6085e44fed has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6085e44fed

Comment 7 Fedora Update System 2023-04-06 20:50:54 UTC
FEDORA-2023-6085e44fed has been pushed to the Fedora 39 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.