CLI 2.0 fails to install on Raspberry Pi: 403 Forbidden [IP: 18.64.103.58 443]

XIII

When following the Apt guide CLI 2.0 fails to install on Raspberry Pi:

➜ sudo apt update && sudo apt install 1password-cli
Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 https://deb.nodesource.com/node_16.x bullseye InRelease
Err:4 https://downloads.1password.com/linux/debian/armhf stable InRelease
  403  Forbidden [IP: 18.64.103.58 443]
Reading package lists... Done
E: Failed to fetch https://downloads.1password.com/linux/debian/armhf/dists/stable/InRelease  403  Forbidden [IP: 18.64.103.58 443]
E: The repository 'https://downloads.1password.com/linux/debian/armhf stable InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

---

1Password Version: CLI 2.0.0
Extension Version: n/a
OS Version: Raspberry Pi OS (bullseye)

Justin.Yoon_1P

This may be caused by a bug in our installation instructions. Do you mind printing out this command and letting me know?

echo $(dpkg --print-architecture)

We use that line to determine the architecture, but only support amd64, 386, arm, and arm64. I have a feeling it is going to print armhf on your machine.

Depending on your OS, you can try replacing the $(dpkg --print-architecture) statements in the instructions with either arm or arm64. From my very recent Google search, it looks like Raspberry Pi 3 and above are 64 bit.

Thanks for reporting this, it is very helpful in improving our installation docs for all users.

XIII

➜ echo $(dpkg --print-architecture)
armhf

and

➜ uname -m
armv7l

They only recently introduced a 64-bits version of the OS: https://www.raspberrypi.com/news/raspberry-pi-os-64-bit/

(I have not upgraded my Raspberry Pi 3 to that yet; I'm still running the 32 bit version of their OS)

XIII

Using arm I get a bit further, but no success yet:

➜ sudo apt update && sudo apt install 1password-cli
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:3 https://deb.nodesource.com/node_16.x bullseye InRelease
Get:4 https://downloads.1password.com/linux/debian/arm stable InRelease [4,240 B]
Get:5 https://downloads.1password.com/linux/debian/arm stable/main arm Packages [439 B]
Fetched 4,679 B in 2s (2,338 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package 1password-cli

(results are the same with arm64 instead of arm)

Justin.Yoon_1P

Hey @XIII I think that's actually an issue on our end.. I've just tested this and received the same error.

Just to confirm, this is the repo I added from the modified version of step 2:

echo "deb [arch=arm signed-by=/usr/share/keyrings/1password-archive-keyring.gpg] https://downloads.1password.com/linux/debian/arm stable main" | tee /etc/apt/sources.list.d/1password.list

I'm going to look into this, because it was definitely passing a few days ago when we tested the repositories.

For the time being, it looks like you got installation on the Raspberry Pi sorted out using the direct downloads.

Thank you for reporting this.

XIII

Direct link works indeed, but I'd rather use apt.

Justin.Yoon_1P

Hey @XIII

Agreed. This is a problem on our end, and the error was reproducible by multiple folks on our team. We will be looking at this over the next weeks.

Justin.Yoon_1P

Hey @XIII

Just wanted to follow up on our findings.

The issue arose from a mis-naming of the 32-bit arm architecture as arm. It should have been labelled as armhf.

For the time being, you can run the dpkg --add-architecture arm command just before running apt install 1password-cli in the last step so that it can download the package from the repo.

For our next release, we will be setting up the Debian package for the armhf architecture instead of arm.

Thanks for bringing this up, let us know if that step works for you, should you decide to try it. Otherwise, stay tuned for the fix in the next release!

XIII

Yes, this seems to work (though it now installs into /usr/bin, where I manually put it in /usr/local/bin, so I might have to update some scripts). Thanks!

Do I need to do anything additional when you change from arm to armhf in the next release?

(Can/Should I delete architecture arm again?)

Justin.Yoon_1P

Hey @XIII

Thank you for confirming.

For the next release, you can delete the arm architecture and the default armhf should work.

XIII

Confirmed: it works for 2.0.1 now.

https://app-updates.agilebits.com/product_history/CLI2

Justin.Yoon_1P

Happy to hear @XIII !