Dear Maintainer,
* What led up to the situation?
After installing imv on debian Bookwork, the binary is not saved in
/usr/bin but can instead only be found in /usr/libexec/imv/imv
This makes using imv on the command line impossible, most noteable when
using terminal file manager like ranger
* What exactly did you do (or not do) that was effective (or
ineffective)?
Running: imv testimage.png
* What was the outcome of this action?
The application was not found
* What outcome did you expect instead?
imv should be installed in /usr/bin to be found in $PATH
[...] Quote /usr/share/doc/imv/README.Debian: | Starting from upstream version 4.0.0 imv ships two binaries that | handle Wayland and X11 natively: imv-wayland and imv-x11. To allow | seamless usage to users upstream provides a /usr/bin/imv wrapper that | checks whether a Wayland compositor is available before running the | appropriate binary. | The Debian package does not ship the wrapper script to avoid a file | name clash with the renameutils package. Invoking either imv-wayland or imv-x11 should work perfectly fine on the commandline. cu Andreas
[...] Quote /usr/share/doc/imv/README.Debian: | Starting from upstream version 4.0.0 imv ships two binaries that | handle Wayland and X11 natively: imv-wayland and imv-x11. To allow | seamless usage to users upstream provides a /usr/bin/imv wrapper that | checks whether a Wayland compositor is available before running the | appropriate binary. | The Debian package does not ship the wrapper script to avoid a file | name clash with the renameutils package. Invoking either imv-wayland or imv-x11 should work perfectly fine on the commandline. cu Andreas
[Andreas Metzler] This sound like a normal or wishlist issue, not a grave error. Reducing severity accordingly.
[Andreas Metzler] This sound like a normal or wishlist issue, not a grave error. Reducing severity accordingly.
Hi You may add the following line to your ~/.bashrc file: export PATH=$PATH:/usr/libexec/imv If you don't install renameutils package in your system, you may run this imv now. As renameutils package already ship /usr/bin/imv command before, so the imv package must to avoid a file name clash with the renameutils package. Regards,