Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1820024
Summary: | wingpanel-indicator-session-2.2.8-debian is available | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
Component: | wingpanel-indicator-session | Assignee: | Fabio Valentini <decathorpe> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rawhide | CC: | decathorpe | ||||
Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | wingpanel-indicator-session-2.2.8-1.fc30 wingpanel-indicator-session-2.2.8-1.fc31 wingpanel-indicator-session-2.2.8-1.fc32 | Doc Type: | --- | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-04-11 21:51:19 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
2020-04-02 05:38:18 UTC
Created attachment 1675606 [details]
[patch] Update to 2.2.8-debian (#1820024)
the-new-hotness/release-monitoring.org's scratch build of wingpanel-indicator-session-2.2.8-debian.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=42961649 FEDORA-2020-4fe2de9b65 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4fe2de9b65 FEDORA-2020-e514ab5b35 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e514ab5b35 FEDORA-2020-af3419e9a5 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-af3419e9a5 FEDORA-2020-4fe2de9b65 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-4fe2de9b65` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4fe2de9b65 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-af3419e9a5 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-af3419e9a5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-af3419e9a5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-e514ab5b35 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-e514ab5b35` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e514ab5b35 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-af3419e9a5 has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-e514ab5b35 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-4fe2de9b65 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. |