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 1488688
Summary: | kde-partitionmanager-v3.1.1 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | kde-partitionmanager | Assignee: | Mattia Verga <mattia.verga> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | andrius-redhat, kevin, mattia.verga |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | kde-partitionmanager-3.1.2-1.fc26 kde-partitionmanager-3.1.2-1.fc27 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-09-17 03:50:54 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
2017-09-06 00:20:27 UTC
3.1.2 fixes missing docs (https://download.kde.org/stable/partitionmanager/3.1.2/src/partitionmanager-3.1.2.tar.xz.mirrorlist) This release fixes a fairly bad crash that can result in data loss.| https://phabricator.kde.org/R17:feb2e374e496c65011e036f2a611fa7cc5b4e940 Version affected: 1.2.0 - 3.1.0 (In reply to Andrius Štikonas from comment #1) > 3.1.2 fixes missing docs > (https://download.kde.org/stable/partitionmanager/3.1.2/src/partitionmanager- > 3.1.2.tar.xz.mirrorlist) > > This release fixes a fairly bad crash that can result in data loss.| > > https://phabricator.kde.org/R17:feb2e374e496c65011e036f2a611fa7cc5b4e940 > > Version affected: 1.2.0 - 3.1.0 I've pushed 3.1.2 into F28 and F27. F26 still have kpmcore 3.0.3 / partitionmanager 3.0.1. Andrius, is it safe to build partitionmanager 3.1.2 against kpmcore 3.0.3? If not, I need to update kpmcore and cause a soname bump. Or can I only backport the relevant patch? (should be feb2e374e496c65011e036f2a611fa7cc5b4e940, isn't it?) F25 is on 2.x series and I don't plan to upgrade it. You can backport just that patch. In fact only the second line is necessary: i.e. &ApplyProgressDialog::reject->&ApplyProgressDialog::onCancelButton But it should be safe to build against KPMcore 3.0.x (see KPMCORE_MIN_VERSION "3.0.0" in CMakeLists.txt). kde-partitionmanager-3.1.2-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-81ded3d59a kde-partitionmanager-3.1.2-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-9502d6caac kde-partitionmanager-3.1.2-1.fc27 has been pushed to the Fedora 27 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-9502d6caac kde-partitionmanager-3.1.2-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-81ded3d59a kde-partitionmanager-3.1.2-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. kde-partitionmanager-3.1.2-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. |