Bug 2124119
| Summary: | gpxsee-11.6 is available | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||||||
| Component: | gpxsee | Assignee: | Nikola Forró <nforro> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | nforro | ||||||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | gpxsee-11.6-1.fc36 gpxsee-11.6-1.fc35 gpxsee-11.6-1.fc37 | Doc Type: | --- | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2022-10-20 15:19:32 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Upstream Release Monitoring
2022-09-04 20:42:27 UTC
Created attachment 1909544 [details]
Update to 11.4 (#2124119)
the-new-hotness/release-monitoring.org's scratch build of gpxsee-11.4-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=91629998 Releases retrieved: 11.5 Upstream release that is considered latest: 11.5 Current version/release in rawhide: 11.3-1.fc38 URL: http://www.gpxsee.org/ 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/16205/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gpxsee Created attachment 1915011 [details]
Update to 11.5 (#2124119)
the-new-hotness/release-monitoring.org's scratch build of gpxsee-11.5-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=92419275 Releases retrieved: 11.6 Upstream release that is considered latest: 11.6 Current version/release in rawhide: 11.3-1.fc38 URL: http://www.gpxsee.org/ 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/16205/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gpxsee Created attachment 1917101 [details]
Update to 11.6 (#2124119)
the-new-hotness/release-monitoring.org's scratch build of gpxsee-11.6-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=92885189 FEDORA-2022-643f72b1ff has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-643f72b1ff FEDORA-2022-8c8c92d2e5 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8c8c92d2e5 FEDORA-2022-57f4cc739b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-57f4cc739b FEDORA-2022-8c8c92d2e5 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-8c8c92d2e5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8c8c92d2e5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-643f72b1ff has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-643f72b1ff` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-643f72b1ff See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-57f4cc739b has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-57f4cc739b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-57f4cc739b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-643f72b1ff has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-57f4cc739b has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-8c8c92d2e5 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. |