Bug 1248310
Summary: | Obsolete lxpanel 0.6.1 used, upstream has 0.8.1 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pavel Roskin <plroskin> |
Component: | lxpanel | Assignee: | Mamoru TASAKA <mtasaka> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | christoph.wickert, mtasaka |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-19 17:15:47 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pavel Roskin
2015-07-30 05:11:20 UTC
F-23 (currently being planned to be released on 2015-10-27) has lxpanel-0.8.1-1.fc23 (and on F-23, all LXDE components are updated to the latest). For F-22, currently I have no plan to update the versions of any LXDE components, as usually on stable branches updates should be bug fix only and lxpanel 0.6.1 -> 0.8.1 is somewhat not a small change. By the way, I have prepared LXDE-next repo for those who wants to try using them on F-22: https://copr.fedoraproject.org/coprs/mtasaka/LXDE-next/ If there are more testers for the above repo and I get more feedback, I may change my thought. That's awesome news! I'll test the repo ASAP. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |