04-13-2022, 01:20 PM
Hi,
I've a problem installing packages on my pinephone pro, pacman is constantly complaining about invalid signatures. At first I thought this is the keyring problem easily fixable with pacman-key --init && pacman-key --populate but that wasn't it. Then I tried reflashing to latest manjaro image but that didn't help either. Then it hit me to just try checking the checksum myself and well...
The file didn't change between the commands (at least not by me anyway), yet the computed checksum is different almost every time. Funny thing is, the phone works just fine otherwise.
It doesn't matter whenever the system is booted from eMMC or SD card, the file can also be in /tmp, won't matter either
Anyone else experienced similar issues? Not sure if this is a hardware bug or perhaps broken kernel or something
I've a problem installing packages on my pinephone pro, pacman is constantly complaining about invalid signatures. At first I thought this is the keyring problem easily fixable with pacman-key --init && pacman-key --populate but that wasn't it. Then I tried reflashing to latest manjaro image but that didn't help either. Then it hit me to just try checking the checksum myself and well...
Code:
[tomek@manjaro-arm tmp]$ sha256sum go-2\:1.18-1-aarch64.pkg.tar.xz
7beace40002edd6668dd856cc971b0d05bf1755984da25ecfc88fcdcd39d3c72 go-2:1.18-1-aarch64.pkg.tar.xz
[tomek@manjaro-arm tmp]$ sha256sum go-2\:1.18-1-aarch64.pkg.tar.xz
9c95f77b4b0f58ed802ab22ba34f5e99398de2ec56adcbf0cbeae675066dd2c8 go-2:1.18-1-aarch64.pkg.tar.xz
[tomek@manjaro-arm tmp]$ sha256sum go-2\:1.18-1-aarch64.pkg.tar.xz
4c49706386cd075dae40b37d37472696b02ba5aac6f4acc430804b35616899c5 go-2:1.18-1-aarch64.pkg.tar.xz
[tomek@manjaro-arm tmp]$ sha256sum go-2\:1.18-1-aarch64.pkg.tar.xz
e2ac9c2252aca3b2c40c99313ccecfee77c63e8b13811b0193e93ca0f528eb6d go-2:1.18-1-aarch64.pkg.tar.xz
[tomek@manjaro-arm tmp]$ sha256sum go-2\:1.18-1-aarch64.pkg.tar.xz
bb28aaf0382394814bf5e1c018e309971bb265342020a100d5a0dc596ce40cdc go-2:1.18-1-aarch64.pkg.tar.xz
[tomek@manjaro-arm tmp]$ sha256sum go-2\:1.18-1-aarch64.pkg.tar.xz
ae3f74ca2212f50a31176eb88c4d832cd57e57add24ed0eca6280bba5234f89e go-2:1.18-1-aarch64.pkg.tar.xz
[tomek@manjaro-arm tmp]$ sha256sum go-2\:1.18-1-aarch64.pkg.tar.xz
75141abdb49cbb24a0a4990ccc027c8a4bd9a5b2716781bfdb402026029f5889 go-2:1.18-1-aarch64.pkg.tar.xz
[tomek@manjaro-arm tmp]$ sha256sum go-2\:1.18-1-aarch64.pkg.tar.xz
75141abdb49cbb24a0a4990ccc027c8a4bd9a5b2716781bfdb402026029f5889 go-2:1.18-1-aarch64.pkg.tar.xz
[tomek@manjaro-arm tmp]$ sha256sum go-2\:1.18-1-aarch64.pkg.tar.xz
ae3f74ca2212f50a31176eb88c4d832cd57e57add24ed0eca6280bba5234f89e go-2:1.18-1-aarch64.pkg.tar.xzThe file didn't change between the commands (at least not by me anyway), yet the computed checksum is different almost every time. Funny thing is, the phone works just fine otherwise.
It doesn't matter whenever the system is booted from eMMC or SD card, the file can also be in /tmp, won't matter either
Anyone else experienced similar issues? Not sure if this is a hardware bug or perhaps broken kernel or something