Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1029238: imv not found in $PATH
152 views
Skip to first unread message
Andreas Metzler
Jan 21, 2023, 10:40:04 AM1/21/23
to
On 2023-01-20 tester732732 via Pkg-phototools-devel <pkg-photot...@alioth-lists.debian.net> wrote:
> Package: imv
> Version: 4.3.0-1.1+b3
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: devnul...@proton.me
> 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
[...]
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
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
> Package: imv
> Version: 4.3.0-1.1+b3
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: devnul...@proton.me
> 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
[...]
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
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Petter Reinholdtsen
Feb 14, 2023, 6:30:06 AM2/14/23
to
Control: severity -1 normal
[Andreas Metzler]
severity accordingly.
--
Happy hacking
Petter Reinholdtsen
[Andreas Metzler]
> | 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.
This sound like a normal or wishlist issue, not a grave error. Reducing
> | 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.
severity accordingly.
--
Happy hacking
Petter Reinholdtsen
0 new messages