Bug 2345960
| Summary: | vokoscreenNG-4.4.5 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | vokoscreenNG | Assignee: | Artem <ego.cordatus> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | ego.cordatus, epel-packagers-sig |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | vokoscreenNG-4.4.5-1.fc43 vokoscreenNG-4.4.5-1.fc42 vokoscreenNG-4.4.5-1.fc41 vokoscreenNG-4.4.6-1.fc40 vokoscreenNG-4.4.6-1.el9 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-02-16 11:28:42 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: | |||
|
Description
Upstream Release Monitoring
2025-02-16 09:28:03 UTC
FEDORA-2025-2ee2a97c24 (vokoscreenNG-4.4.5-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-2ee2a97c24 FEDORA-2025-b1ea22a954 (vokoscreenNG-4.4.5-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-b1ea22a954 FEDORA-2025-79a75b88f6 (vokoscreenNG-4.4.5-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-79a75b88f6 FEDORA-2025-2ee2a97c24 (vokoscreenNG-4.4.5-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-b1ea22a954 (vokoscreenNG-4.4.5-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-79a75b88f6 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-79a75b88f6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-79a75b88f6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-79a75b88f6 (vokoscreenNG-4.4.5-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2025-a66ef9e166 (vokoscreenNG-4.4.6-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a66ef9e166 FEDORA-2025-6bdf392fb8 (vokoscreenNG-4.4.6-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-6bdf392fb8 FEDORA-EPEL-2025-a66ef9e166 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a66ef9e166 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-6bdf392fb8 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-6bdf392fb8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-6bdf392fb8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-6bdf392fb8 (vokoscreenNG-4.4.6-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2025-a66ef9e166 (vokoscreenNG-4.4.6-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. |