Bug 2171141
| Summary: | qutebrowser-2.5.4 is available | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||||
| Component: | qutebrowser | Assignee: | Timothée Floure <timothee.floure> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | sanjay.ankur, timothee.floure | ||||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | qutebrowser-2.5.4-1.fc37 qutebrowser-2.5.4-1.fc38 | Doc Type: | --- | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2023-06-19 01:18:22 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
2023-02-18 07:43:11 UTC
Created attachment 1944933 [details]
Update to 2.5.3 (#2171141)
the-new-hotness/release-monitoring.org's scratch build of qutebrowser-2.5.3-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=97660205 Releases retrieved: 2.5.4 Upstream release that is considered latest: 2.5.4 Current version/release in rawhide: 2.5.2-3.fc38 URL: http://www.qutebrowser.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/9759/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/qutebrowser Created attachment 1950632 [details]
Update to 2.5.4 (#2171141)
the-new-hotness/release-monitoring.org's scratch build of qutebrowser-2.5.4-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=98686727 FEDORA-2023-bd2d6f3957 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-bd2d6f3957 FEDORA-2023-aa4f770130 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-2023-aa4f770130` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-aa4f770130 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-bd2d6f3957 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-bd2d6f3957` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-bd2d6f3957 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-aa4f770130 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-bd2d6f3957 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. |