Re: passmenu on Debian with Wayland
On Sat 25 Oct 2025 at 09:44:48 (-0400), Greg Wooledge wrote:
> On Sat, Oct 25, 2025 at 14:42:43 +0200, Alex wrote:
> > However, on my machine, the passmenu script is installed to
> >
> > $ dpkg -S passmenu
> > pass: /usr/share/doc/pass/examples/dmenu/passmenu
> >
> > Before raising a bug against the pass package I wanted to understand
> > whether this is correct? Why would an executable script end up in
> > /usr/share/doc?
>
> [ … safecat analogy stuff … ]
>
> In your case, it sounds like the Debian maintainer has done something
> similar. For *whatever* reason, they've chosen not to install this
> wrapper(?) script, and have left it in /usr/share/doc/pass/examples/
> as part of the upstream package's documentation.
It looks to me as if this was a useful script found in something
called dwm (dwm.suckless.org), which was contributed to password-store
perhaps 10 years ago, and was bundled into its contrib/dmenu directory.
The passmenu script itself contains no attribution, copyright, etc,
which contrasts with the rest of the code in pass, so installing it
into /usr/bin would be inappropriate IMO. Is it maintained? Is it
intended that you edit in a configuration if you want to use it?
The square brackets in the README.md would seem to imply that, and
I think you're expected to follow the references, which might help
the OP resolve their problem.
If I were filing a bug, I might argue with its executable permission,
but not its location.
If I were looking for an analogy (but with both attribution and
copyright), perhaps /usr/share/doc/mutt/examples/mutt_oauth2.py would
suffice. There we have a copious README that could hardly be more
extensive. But the script itself can't be added to any final location
because it first needs to be edited/configured.
> My suggestions to you would be to do both of the following:
>
> 1) See whether a bug has already been filed against pass, and if not,
> file one yourself.
>
> 2) Create /usr/local/bin/passmenu which is the missing program that
> you need. Copy it from the /examples/ subdirectory, modify it
> however you need, and use it. Make sure you do this on all the
> systems where you need it, and that it follows you across Debian
> release upgrades, system replacements, and so on.
Cheers,
David.
Reply to: