Specify system architecture #116
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using 'dpkg --print-architecture' rather than fixed arm64 for amd64 compatibility.
Probably unrelated, but in my duplication of reported fault I used the command with only 'sudo' used for 'tee' entry and update passed, therefore replicating my usage here too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Users report tor key and update error messages regarding incorrect detection of (1) armhf system architecture and (2) key signature update.
Proposed fixes:
(1) Using 'dpkg --print-architecture' rather than fixed setting a fixed "arch=arm64" for amd64 compatibility. The script will determine architecture and input value for dpkg to source correct tor build. Should work for our ARM devices and also AMD64 too. Errors should now more reliable be genuine if 32 bit/i386 device tries to install.
(2) - Closest related fault - https://forum.torproject.org/t/tor-relays-expkeysig-when-running-apt-update/3646 - This error confused me and I'm not at the cause yet. Seems the tor key image error became out of date, despite our usage of tor install manual instructions and gpg key matching at https://support.torproject.org/apt/tor-deb-repo/
Anyway, we continue to follow those instructions, we follow both step 3 and 4:
Only change is we require 'sudo' to tee the entry to /usr/share/keyrings/deb.torproject.org-keyring.gpg