Bug 1421671
Summary: | lightdm-1.22.0 is available | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
Component: | lightdm | Assignee: | Björn 'besser82' Esser <besser82> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rawhide | CC: | christoph.wickert, leigh123linux, rdieter | ||||
Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | lightdm-1.22.0-1.fc26 | Doc Type: | Enhancement | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-06-09 19:03:15 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
2017-02-13 12:15:13 UTC
Latest upstream release: 1.21.5 Current version/release in rawhide: 1.18.3-2.fc26 URL: https://launchpad.net/lightdm/1.18 Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/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/1813/ Latest upstream release: 1.22.0 Current version/release in rawhide: 1.18.3-2.fc26 URL: https://launchpad.net/lightdm/1.18 Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/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/1813/ Created attachment 1280195 [details]
1.22.0 spec file patch
1.22.0 builds fine with minimal changes to spec file only, no patch changes needed.
I have also tested the build and the logs seem clear of any new warnings.
lightdm-1.22.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-ef1cd1cf38 As lightdm maintainer, I object to this update, I typically only support LTS lightdm releases (unless I missed something and 1.22.0 is in fact a LTS-supported release). That said, I've always said too, if others want to step up to maintain more active lightdm branches, I'd be happy to step aside as primary maintainer of lightdm. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. lightdm-1.22.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-ef1cd1cf38 lightdm-1.22.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. |