Bug 1818095 - groonga-10.0.1 is available
Summary: groonga-10.0.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: groonga
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kentaro Hayashi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-27 16:44 UTC by Upstream Release Monitoring
Modified: 2020-05-03 05:29 UTC (History)
2 users (show)

Fixed In Version: groonga-10.0.1-1.fc30 groonga-10.0.1-1.fc31 groonga-10.0.1-1.fc32
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-03 04:40:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 10.0.0 (#1818095) (988 bytes, patch)
2020-03-27 16:44 UTC, Upstream Release Monitoring
no flags Details | Diff
[patch] Update to 10.0.1 (#1818095) (988 bytes, patch)
2020-03-30 06:33 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2020-03-27 16:44:38 UTC
Latest upstream release: 10.0.0
Current version/release in rawhide: 9.1.2-1.fc33
URL: http://packages.groonga.org/source/groonga/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/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/1255/

Comment 1 Upstream Release Monitoring 2020-03-27 16:44:55 UTC
Created attachment 1674121 [details]
[patch] Update to 10.0.0 (#1818095)

Comment 2 Upstream Release Monitoring 2020-03-27 16:54:44 UTC
the-new-hotness/release-monitoring.org's scratch build of groonga-10.0.0-1.fc30.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=42802743

Comment 3 Upstream Release Monitoring 2020-03-30 06:32:58 UTC
Latest upstream release: 10.0.1
Current version/release in rawhide: 9.1.2-1.fc33
URL: http://packages.groonga.org/source/groonga/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/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/1255/

Comment 4 Upstream Release Monitoring 2020-03-30 06:33:08 UTC
Created attachment 1674632 [details]
[patch] Update to 10.0.1 (#1818095)

Comment 5 Upstream Release Monitoring 2020-03-30 06:56:09 UTC
the-new-hotness/release-monitoring.org's scratch build of groonga-10.0.1-1.fc30.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=42858286

Comment 6 Fedora Update System 2020-04-24 01:02:54 UTC
FEDORA-2020-8e3d798a03 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8e3d798a03

Comment 7 Fedora Update System 2020-04-24 01:19:16 UTC
FEDORA-2020-4811cfe899 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4811cfe899

Comment 8 Fedora Update System 2020-04-24 01:36:07 UTC
FEDORA-2020-bbc9bc1919 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-bbc9bc1919

Comment 9 Fedora Update System 2020-04-25 04:18:52 UTC
FEDORA-2020-4811cfe899 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-4811cfe899`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4811cfe899

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2020-04-25 04:55:26 UTC
FEDORA-2020-bbc9bc1919 has been pushed to the Fedora 30 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-bbc9bc1919`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-bbc9bc1919

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2020-04-25 12:20:50 UTC
FEDORA-2020-8e3d798a03 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8e3d798a03`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8e3d798a03

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2020-05-03 04:40:41 UTC
FEDORA-2020-bbc9bc1919 has been pushed to the Fedora 30 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2020-05-03 04:53:49 UTC
FEDORA-2020-4811cfe899 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2020-05-03 05:29:32 UTC
FEDORA-2020-8e3d798a03 has been pushed to the Fedora 32 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.