Bug 411566 - Krename exiv2 plugin is not enabled
Summary: Krename exiv2 plugin is not enabled
Status: RESOLVED FIXED
Alias: None
Product: neon
Classification: KDE Neon
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-03 19:31 UTC by Vangelis
Modified: 2025-09-09 16:07 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vangelis 2019-09-03 19:31:19 UTC
Krename installed in a KDE neon installation doesn't provide access to the Exiv2 rename plugin. It seems the problem is that the file `cmake/modules/FindExiv2.cmake` is trying to extract version information from the file `${EXIV2_INCLUDE_DIR}/exiv2/version.hpp`, but in the latest version of exiv2 that is shipped again from the kde neon repository the actual version information is provided by the file `${EXIV2_INCLUDE_DIR}/exiv2/exv_conf.h`.

This bug has been fixed in the upstream krename with this commit: https://phabricator.kde.org/R758:b22de9135ba2a5abdbd2b275a60933a50f074010

Please consider updating the krename package!

$ apt-cache policy krename
krename:
  Installed: 5.0.0-1+18.04+bionic+build6
  Candidate: 5.0.0-1+18.04+bionic+build6
  Version table:
 *** 5.0.0-1+18.04+bionic+build6 500
        500 http://archive.neon.kde.org/user bionic/main amd64 Packages
        100 /var/lib/dpkg/statu


$ apt-cache policy exiv2
exiv2:
  Installed: 0.27.1-0+18.04+bionic+build12
  Candidate: 0.27.1-0+18.04+bionic+build12
  Version table:
 *** 0.27.1-0+18.04+bionic+build12 500
        500 http://archive.neon.kde.org/user bionic/main amd64 Packages
        100 /var/lib/dpkg/status
Comment 1 Jonathan Riddell 2019-09-05 13:22:38 UTC
This needs a release of krename
Comment 2 BRYANTDL7 2025-09-09 16:07:18 UTC
This ticket has been archived due to the age of this request, in order to keep currently present issues at the forefront for proper resolution. If this issue is still present, please reopen this ticket and provide additional details related to the request.