Package Details: 1password-cli 2.15.0-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: 38
Popularity: 1.98
First Submitted: 2017-09-07 18:54 (UTC)
Last Updated: 2023-03-21 19:06 (UTC)

Pinned Comments

slurpee commented on 2022-03-22 11:18 (UTC) (edited on 2022-04-20 06:55 (UTC) by slurpee)

Due to a file conflict in the bash-completion package bash completion is not installed automatically; the upstream op completion has been deprecated in favor of the completion generated by op, but a new release has not been cut containing the fix. In the meantime, bash users seeking command completion should add the following to their .bashrc:

source <(op completion bash)

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 Next › Last »

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?

ElijahLynn commented on 2022-07-19 21:37 (UTC)

==> Validating source_x86_64 files with sha256sums... ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error making: 1password-cli

slurpee commented on 2022-07-19 19:08 (UTC)

It appears that AgileBits was running some beta tests and the beta binaries were inadvertently uploaded to their CDN. They have reverted this change on the 18th of July.

I confirmed the binaries have been reverted to the previous versions (GPG and sha256 of the binary) and updated the sha256sums to match the current ZIP archives available on their CDN.

slurpee commented on 2022-07-18 19:58 (UTC)

I reached out to AgileBits to verify the hashes were changed. The GPG signatures are still valid, which means the updated binaries are genuine.

slurpee commented on 2022-07-16 22:28 (UTC)

Thanks for the heads up! I'll reach out to 1password; this has happened in the past.

I'll be able to push an update later today if necessary.

hiddeco commented on 2022-07-16 10:11 (UTC)

The checksums of the v2.5.1 release files appear to have changed:

$ sha256sum 
$ sha256sum