Error key "xxx...xxx" could not be looked up remotely on ArchLinux

 Here is the answer that worked for me, from:

https://superuser.com/questions/1675153/error-key-xxx-xxx-could-not-be-looked-up-remotely-on-archlinux


pacman-key --init

pacman-key --populate archlinux
 

Then tried 


pacman -Sy sudo

again and it was fine!

Comments

Post a Comment

Popular posts from this blog

Getting networking going with new Archlinux installation

 So I installed Archlinux as per the instructions. I'm not a noob, but surely I can't be alone in thinking  https://wiki.archlinux.org/title/Installation_guide is a little light on details. Let's give an example. Having not managed to get networking going I was following the step by step.  It says consider installing... "... software necessary for   networking " Oh. That thing in blue is a hyperlink. Ok, networking is kinda important, I'll click on it. https://wiki.archlinux.org/title/Network_configuration#Network_management " To troubleshoot a network connection"  it says , ensure, among other things, that "Your network interface has an   IP address ." Ok let's look at IP address.   Not exactly a step by step guide!  But thankfully some dude has posted a youtube video. Yes, after 3 evenings of reading the briefest of wikis, I've resorted to youtube tutorials. https://www.youtube.com/watch?v=iedzVZlAbqI Arch Linux Enable Networki...
Read more

Partitioning using command line and parted

Getting this error when trying to partition my disk Warning: The resulting partition is not properly aligned for best performance. Finding this out to get past this took more googling than it should (a hint in parted's response would have saved about 20 minutes here). parted will calculate proper alignment if you use percentages instead of sectors: (parted) mkpart Partition name? []? part1 File system type? [ext2]? ext4 Start? 0% End? 100% from: https://askubuntu.com/questions/932545/the-resulting-partition-is-not-properly-aligned-for-best-performance
Read more

Dual boot Linux and windows (separate disks) using Grub2 SHOULDN'T BE THIS TRICKY

ISSUE: has the grub menu disappeared? does your system boot straight into windows? Explanation Each disk has its own OS, and efI bootloader 1) Linux bootlader (xubuntu) is sda1 2) Windows 10 bootloader is sdb2 Now, the grub2 files that matter are: /etc/default/grub in which you need to make sure  GRUB_TIMEOUT_STYLE=menu and doesn't say  GRUB_TIMEOUT_STYLE=hidden This makes sure you see the grub menu and /etc/grub.d/40_custom (see  https://linuxvox.com/blog/grub-config-file-ubuntu /) where we add our extra menu option for Windows 10 (see https://askubuntu.com/questions/661947/add-windows-10-to-grub-os-list ) viz: type  lsblk  to identify your windows EFI partition, then blkid /dev/sda1   (with the partition /dev name) to find the UUID of the EFI (call that  YOUR_WIN_EFI_UUID) then FINALLY, the code to add in the  /etc/grub.d/40_custom\ is menuentry 'Windows 10' { search --fs-uuid --no-floppy --set=root YOUR_WIN_EFI_UUID chainloader (${root}...
Read more