| Summary: | media-gfx/digikam - /usr/bin/cleanup_digikamdb: line 61: kreadconfig: command not found | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Vit Pelcak <v.pelcak> |
| Component: | Current packages | Assignee: | Andreas K. Hüttel <dilfridge> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kde |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://phabricator.kde.org/D9235 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
What fun. Seems upstream still relies on a binary from kreadconfig:4 from long obsolete kde-runtime. The correct binary name would be kreadconfig5, found in kconfig:5. Please check if it works with a manually created link to kreadconfig5. Answer to myself: That works. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=12401247632313d3494f864cf75d38916ed2aad4 commit 12401247632313d3494f864cf75d38916ed2aad4 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2017-12-06 21:46:09 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2017-12-06 22:08:00 +0000 media-gfx/digikam: Fix cleanup_digikamdb, DB w/ >=mariadb-10.2 Closes: https://bugs.gentoo.org/639032 Package-Manager: Portage-2.3.16, Repoman-2.3.6 media-gfx/digikam/digikam-5.7.0-r2.ebuild | 174 +++++++++++++++++++++ .../digikam/files/digikam-5.7.0-kreadconfig5.patch | 28 ++++ .../files/digikam-5.7.0-mariadb-10.2-1.patch | 58 +++++++ .../files/digikam-5.7.0-mariadb-10.2-2.patch | 117 ++++++++++++++ 4 files changed, 377 insertions(+) |
On digikam 5.7.0: $ cleanup_digikamdb --help /usr/bin/cleanup_digikamdb: line 61: kreadconfig: command not found /usr/bin/cleanup_digikamdb: wrong switch – - Usage: cleanup_digikamdb <options> options: -t Include thumbnail databases -T Only cleanup thumbnail databases -p <path> Specify a different database path. If the specified path is invalid, the entry from the configuration file will be used. -h Show this help. Attempting to run cleanup_digikamdb ends up with the same error. Reproducible: Always