The unofficial but great archzfs build has a new maintainer and most important, a new key.
#pacman-key -r F75D9D76
#pacman-key --lsign-key F75D9D76
And you are ready to upgrade. The key was changed since they are now using a buildbot to reduce the time between new kernel release and adapted archzfs package.
Thanks for your great work people!
I've started a regular update by using
sudo pacman -Syyu and the following lines where the final result.
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: key "77193F152BDBE6A6" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
I did what was told me to do .
sudo pacman-key --init
And after running
sudo pacman -Syyu I was asked.
:: Import PGP key 4096R/68B3537F39A313B3E574D06777193F152BDBE6A6, "Arch Linux ARM Build System <[email protected]>", created: 2014-01-18? [Y/n]
"As expected, I though" but than I got a long list of the error mention in the headline (for each package).
I've fixed this by executing the following command.
pacman-key --lsign-key 77193F152BDBE6A6
sudo pacman -Syyu was running fine as expected.
Strange note, all was working fine a week ago (2018-05-25) and the pgp key was created 2014 .
On some machines, I get the following error when I run an "pacman -Syyu".
error: key "CEB167EFB5722BD6" could not be looked up remotely
I've found the best fox so far on this page.
#open /etc/pacman.d/gnupg/gpg.conf as root
#comment out existing server address and replace with following
#save the file afterwards
#run following command as root
#if the upgrade is still not working, signed the key (be aware to know what you are doing here!)
pacman-key --lsign-key CEB167EFB5722BD6
This was working on almost all machines. Only a few percent where still not able to be upgraded.
What I did to fix this issue was to copy the the directory in "/etc/pacman.d/gnupg" from a working host to the not working one (make a backup first of course).
Just had the "joy" to figure out that teamviewer is not starting anymore on my arch linux.
I restarted the deamon and also launched teamviewer from the command line.
CheckCPU: SSE2 support: yes
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Launching TeamViewer ...
Launching TeamViewer GUI ...
And at "Launching TeamViewer GUI ..." that was it, no entries in an error log or the journal, nothing.
After having a look into the aur package log, it quickly turned out to be a solvable problem.
sudo pacman -U lib32-freetype2-2.8-2-x86_64.pkg.tar.xz
Looks like teamviewer decided to use an old and deprecated version of freetype2 within his bugfix release.
If you are using archzfs and the zfsonlinux, you know that it can happen from time to time that you have to wait until packages are updated to the newest kernel (or lts kernel).
Whenever you want to upgrade your system, you get an error like the following.
:: Starting full system upgrade...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: spl-linux-lts: installing linux-lts (4.9.32-1) breaks dependency 'linux-lts=4.9.30'
:: zfs-linux-lts: installing linux-lts (4.9.32-1) breaks dependency 'linux-lts=4.9.30'
:: zfs-utils-linux-lts: installing linux-lts (4.9.32-1) breaks dependency 'linux-lts=4.9.30'
To update your system without the kernel (and its dependencies), you can use the following trick.
#example if you use the lts kernel
#if you use plain pacman
pacman -Syyu --ignore=linux-lts,linux-lts-headers
#if you use pacaur
pacaur pacman -Syyu --ignore=linux-lts,linux-lts-headers
Thats it .