Package Details: 1password-cli 2.26.1-1

Git Clone URL: (read-only, click to copy)
Package Base: 1password-cli
Description: 1Password command line tool
Upstream URL:
Keywords: 1password
Licenses: custom
Submitter: Sh4rk
Maintainer: slurpee
Last Packager: slurpee
Votes: 43
Popularity: 1.22
First Submitted: 2017-09-07 18:54 (UTC)
Last Updated: 2024-04-16 21:50 (UTC)

Pinned Comments

slurpee commented on 2022-03-22 11:18 (UTC) (edited on 2024-01-21 23:34 (UTC) by slurpee)

As of the 2.24.0-2 release, Zsh shell completion is no longer provided by the package to mirror the official packages. Users that wish to use shell completion can add a line to their shell's dotfile.

See the official docs for instructions specific to your shell:

It is recommended to verify the authenticity of the binary by using Agilebits's PGP code signing key. Their public key ID is published in the install documentation.

gpg --receive-keys 3FEF9748469ADBE15DA7CA80AC2D62742012EA22

Latest Comments

1 2 3 4 5 6 Next › Last »

slurpee commented on 2024-01-21 23:31 (UTC)

Appreciate the report. I've opted to stop installing completion, letting the user add it to their shell's dotfile, if they wish. The 2.24.0-2 release removes the previously provided file, /usr/share/zsh/site-functions/_op.

The 1P documentation has users set up their dotfile and the official packages do not ship completion either. IMO, it's good to have parity with the official package when possible.

Detailed instructions on setting up completion can be found in the 1P docs:

sschmelzer commented on 2024-01-20 12:48 (UTC)

Building the pkg is stuck with the following message: Would you like to turn on the 1Password app integration? This allows you to sign in to 1Password CLI using the 1Password app. [Y/n]. No matter what is answered, the process wont finish.

Looking at the fopens during the process it turned out to be a check if ~/.config/op/config exists (with a minimal config) during the execution of "${pkgdir}"/usr/bin/op completion zsh > "${pkgdir}"/usr/share/zsh/site-functions/_op. If the file exists build passes without any user interaction.

Providing a dummy config via --config helps to avoid the user interaction on build.

Minimal config:

    "latest_signin": "",
    "device": "",
    "accounts": null,
    "dismissed_system_auth_prompt": true

strickczq commented on 2023-12-28 06:23 (UTC)

@0BAD-C0DE Add Agilebits's PGP key reference

curl -sS | gpg --import

0BAD-C0DE commented on 2023-11-01 13:29 (UTC)

Latest version fails to check signature. Any hint?

gpg: Signature made mar 24 ott 2023, 19:13:13 CEST
gpg:                using RSA key 3FEF9748469ADBE15DA7CA80AC2D62742012EA22
gpg: Can't check signature: No public key
==> ERROR: A failure occurred in check().
error: failed to build '1password-cli-2.22.0-1': 
error: packages failed to build: 1password-cli-2.22.0-1

Sacro commented on 2023-08-23 19:24 (UTC)

Line 35, should be install -dm755 not install -d 755

g_sokol commented on 2023-03-21 20:15 (UTC)

On attempt of sign in via 1password app it returns the following error:

➜  ~ op signin        
[ERROR] 2023/03/21 22:01:50 connecting to desktop app: read: connection reset, make sure the CLI is correctly installed and Connect with 1Password CLI is enabled in the 1Password app

It also seems to be in a proper group:

➜  ~ ls -la $(which op)
-rwxr-sr-x 1 root onepassword-cli 19197952 Mar  6 15:28 /usr/bin/op

InTerFace commented on 2022-07-21 07:25 (UTC)

clean your locally cloned package repo of any existing build artifacts/archives and run makepkg again?

this fixed it for me. thx

slurpee commented on 2022-07-20 09:51 (UTC) (edited on 2022-07-20 09:52 (UTC) by slurpee)

To help troubleshoot, could you all please:

  • clean your locally cloned package repo of any existing build artifacts/archives and run makepkg again?
  • download the source archives directly, outside of your local repo and post the SHA256 sums of those archives?

I ran some tests to see if I was hitting a caching layer with their CDN and downloading the incorrect archive, but the tests ended up with the SHA256 sums in the current HEAD.

Auerhuhn commented on 2022-07-20 07:18 (UTC)

@slurpee Since the latest PKGBUILD version 2.5.1-2, is failing the SHA-256 check for me.

slurpee commented on 2022-07-19 22:33 (UTC)

Hey @ElijahLynn, did you pull the -2 pkgrel? Building correctly for me on latest HEAD. If you're still receiving an error, could you send a gist of your full makepkg output?