Bug 1674809
| Summary: | digikam: FTBFS in Fedora rawhide/f30 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
| Component: | digikam | Assignee: | Rex Dieter <rdieter> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | alekcejk, awilliam, gmarr, kde-sig, kwizart, me, rdieter, smparrish, than, viktor.vix.jancik | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | AcceptedFreezeException | ||||||||||
| Fixed In Version: | digikam-6.0.0-5.fc30 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-03-12 20:00:45 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: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1574714, 1674516 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Fedora Release Engineering
2019-02-11 17:04:23 UTC
Created attachment 1529708 [details]
build.log
file build.log too big, will only attach last 1024 bytes
Created attachment 1529709 [details]
root.log
file root.log too big, will only attach last 1024 bytes
Created attachment 1529710 [details]
state.log
This will be resolved once digikam 6 comes to rawhide. Blocking issue is that digikam-6 sources no longer includes kipi-plugins, upstream ml discussion ongoing: https://mail.kde.org/pipermail/digikam-devel/2019-February/101660.html Arg, now hit a ppc64le specific issue, filed bug upstream, https://bugs.kde.org/show_bug.cgi?id=404853 FTBFS is arch-limited, updating summary. Going with ExcludeArch for now, until we have something better and/or feedback from upstream Resetting back to FTBFS on f30 to use for freeze exception digikam-6.0.0-5.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-99fba7aceb Proposed as a Freeze Exception for 30-beta by Fedora user rdieter using the blocker tracking app because: fix FTBFS digikam-6.0.0-5.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-99fba7aceb digikam-6.0.0-5.fc30 has been pushed to the Fedora 30 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-2019-99fba7aceb Well, this isn't really just an FTBFS fix - it's a new version. In stable right now is 5.9.0, so granted this an FE effectively is granting an FE to update the package to 6.0.0. Is 5.9.0 badly broken or uninstallable? 5.9.0 is uninstallable due to broken dependencies Discussed during the 2019-03-11 blocker review meeting: [1] The decision to classify this bug as an "AcceptedFreezeException" was made on the grounds that since the existing package cannot be installed due to broken dependencies, we accept this as an FE (fixing broken dependencies in the stable package set is usually a good idea). [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2019-03-11/f30-blocker-review.2019-03-11-16.04.txt digikam-6.0.0-5.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. |