Update issue with zsh-theme-powerlevel10k

wind77 · 22 February 2025 21:34

Hi all.

Today Pamac prompted me to update, one of the apps was zsh-theme-powerlevel10k coming from AUR.

However, when I proceeded to update, I was prompted with the following:

The PGP key 8B060F8B9EB395614A669F2A90ACE942EB90C3DD is needed to verify zsh-theme-powerlevel10k source files.
Trust Roman Perepelitsa roman.perepelitsa@gmail.com and import the PGP key ?

I’m not familiar of who is who, and basic check shows that zsh-theme-powerlevel10k is maintained by yochananmarqos, packaged by Mark Wagie.
The name Roman Perepelitsa does not fit anywhere.

Naturally, I rejected the prompt, and here was the outcome:

Building zsh-theme-powerlevel10k...
==> Making package: zsh-theme-powerlevel10k 1.20.0-4 (Sun 23 Feb 2025 05:24:06 AM +08)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating powerlevel10k git repo...
  -> Found libgit2-tag-2ecf33948a4df9ef45a66c68b8ef24a5e60eaac6.tar.gz
==> Validating source files with sha256sums...
    powerlevel10k ... Passed
    libgit2-tag-2ecf33948a4df9ef45a66c68b8ef24a5e60eaac6.tar.gz ... Passed
==> Verifying source file signatures with gpg...
    powerlevel10k git repo ... FAILED (unknown public key 90ACE942EB90C3DD)
==> ERROR: One or more PGP signatures could not be verified!
Failed to build zsh-theme-powerlevel10k

So what is happening here?

Nachlese · 22 February 2025 21:41

it is in AUR
but it is in the regular repos as well

use pacman to update - or pamac with AUR support disabled

the AUR package should not be the higher priority

wind77 · 22 February 2025 21:46

I usually do not install anything from AUR explicitly.
And this app was “installed as a dependency for another package”.
So, is some app installed as official repo, got moved to AUR without user’s consent?

I updated my Pamac, and it is not present in official repo.

Nachlese · 22 February 2025 21:52

pamac’s fault

it is in the repos

Branch compare for Manjaro

… don’t rely on pamac - use pacman and some other AUR helper rather than pamac
… or deal with such things …

is my personal opinion!

scotty65 · 22 February 2025 21:55

Maybe you are using outdated mirrors. Try refreshing your mirrorlist and updating with pacman to make sure your system is fully up-to-date:

sudo pacman-mirrors --continent && sudo pacman -Syu

wind77 · 22 February 2025 22:00

I’m clueless now…

sudo pacman-mirrors --continent && sudo pacman -Syu                                                                                                                              INT ✘  1m 55s  
::INFO Downloading mirrors from Manjaro
::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json
::INFO => Mirror status: https://repo.manjaro.org/status.json
::INFO User generated mirror list
::------------------------------------------------------------
::INFO Custom mirror file saved: /var/lib/pacman-mirrors/custom-mirrors.json
::INFO Using default mirror file
::INFO Querying mirrors - This may take some time
  0.528 Bangladesh     : http://mirror.xeonbd.com/manjaro/
  0.451 Bangladesh     : https://bd.mirror.vanehost.com/Manjaro/
  1.429 China          : https://mirrors.sjtug.sjtu.edu.cn/manjaro/
  0.214 Indonesia      : http://kartolo.sby.datautama.net.id/manjaro/
  0.484 Japan          : http://ftp.tsukuba.wide.ad.jp/Linux/manjaro/
  0.645 Japan          : https://mirror.phoepsilonix.love/manjaro/
  0.636 Taiwan         : http://free.nchc.org.tw/manjaro/
  0.500 Taiwan         : https://mirror.archlinux.tw/Manjaro/
::INFO Writing mirror list
::Indonesia       : http://kartolo.sby.datautama.net.id/manjaro/stable
::Bangladesh      : https://bd.mirror.vanehost.com/Manjaro/stable
::Japan           : http://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable
::Taiwan          : https://mirror.archlinux.tw/Manjaro/stable
::Bangladesh      : http://mirror.xeonbd.com/manjaro/stable
::Taiwan          : http://free.nchc.org.tw/manjaro/stable
::Japan           : https://mirror.phoepsilonix.love/manjaro/stable
::China           : https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
^C
Interrupt signal received

Is the archive damaged at my end, or the server’s end?

Nachlese · 22 February 2025 22:15

it’s why I prefer to recommend to do the needed commands one at a time

sudo pacman-mirrors --continent
went fine

the issue arose with the second command (after &&)

sudo pacman-mirrors --continent && sudo pacman -Syu

cscs · 22 February 2025 22:17

sudo pacman -Scc

Then

sudo pacman -Syu zsh-theme-powerlevel10k

Nachlese · 22 February 2025 22:20

… but
why?
and
how did you know?
would OP ask
perhaps

cscs · 22 February 2025 22:22

The first command will present prompts to clear the cache.

( So should be easy for the user to see what they do. )

The second one is the same as before except it points at zsh-theme-powerlevel10k.

( This has not been mentioned before … but if for whatever reason the user does not currently have the repo version then this will replace with it. )

wind77 · 22 February 2025 22:55

sudo pacman -Scc                                                                                                                                                                    INT ✘  10s  

Cache directory: /var/cache/pacman/pkg/
:: Do you want to remove ALL files from cache? [y/N] y
removing all files from cache...

Database directory: /var/lib/pacman/
:: Do you want to remove unused repositories? [Y/n] y
removing unused sync repositories...

sudo pacman -Syu zsh-theme-powerlevel10k                                                                                                                                                ✔  18s  
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
error: target not found: zsh-theme-powerlevel10k

I don’t know what to ask / do now.

Nachlese · 22 February 2025 22:56

context, my friend

I do not know a solution.
only that the package in question is available from the regular repos.
No need for AUR.

nothing is insolvable here - just take minute and think …

wind77 · 22 February 2025 22:58

Again, “I don’t know what to ask.”.

Nachlese · 22 February 2025 23:03

don’t mind me or my opinion,
you need to address these errors:

wind77:

warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
error: target not found: zsh-theme-powerlevel10k

wind77 · 22 February 2025 23:04

Yes, I know.
if I knew how, I would.

cscs · 22 February 2025 23:05

Mk. How about this (its a script … you can inspect the gitlab contents)

bash <(curl -s https://gitlab.com/cscs/mapare/-/raw/main/mapare) -K

Nachlese · 22 February 2025 23:07

and if I knew of the top of my head, I’d tell you
but I don’t

I’d have to search and look through the forum to find it - to then present the findings here.

Am I going to do that?
(0)
(1)

wind77 · 22 February 2025 23:10

No worry.
Your kindness is appreciated.
Help what you could, and leave the rest to other gurus.

wind77 · 22 February 2025 23:20

bash <(curl -s https://gitlab.com/cscs/mapare/-/raw/main/mapare) -K                                                                                                                    1 ✘  9s  

 Manjaro Package Restore

 Retrieve and reinstall package lists

 Keyring Assistant

Clearing the package cache may be useful to remove corrupted packages.

Remove unused repositories and ALL files from cache (y/N)? y
Done

Remove local pacman keys (y/N)? y
Done

Download current keyring packages (y/N)? y
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
Done

Install downloaded keyring packages (y/N)? y
loading packages...
warning: archlinux-keyring-20250123-1 is up to date -- reinstalling
warning: manjaro-keyring-20230719-3 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (2) archlinux-keyring-20250123-1  manjaro-keyring-20230719-3

Total Installed Size:  1.77 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] y
(2/2) checking keys in keyring                                                                                               [###########################################################################] 100%
(2/2) checking package integrity                                                                                             [###########################################################################] 100%
(2/2) loading package files                                                                                                  [###########################################################################] 100%
(2/2) checking for file conflicts                                                                                            [###########################################################################] 100%
(2/2) checking available disk space                                                                                          [###########################################################################] 100%
:: Processing package changes...
(1/2) reinstalling archlinux-keyring                                                                                         [###########################################################################] 100%
(2/2) reinstalling manjaro-keyring                                                                                           [###########################################################################] 100%
 >>> Run `pacman-key --init` to set up your pacman keyring.
 >>> Then run `pacman-key --populate manjaro` to install the Manjaro keyring.
:: Running post-transaction hooks...
(1/4) Reloading system manager configuration...
(2/4) Restarting marked services...
(3/4) Arming ConditionNeedsUpdate...
(4/4) Refreshing PackageKit...
Done

Initialize and populate keys (y/N)? y
gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/22F8529999FDDF186367C0516B5A3E9D4E1550D3.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Appending keys from manjaro.gpg...
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signed 23 keys.
==> Importing owner trust values...
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
  -> Disabled 53 keys.
==> Updating trust database...
gpg: Note: third-party key signatures using the SHA1 algorithm are rejected
gpg: (use option "--allow-weak-key-signatures" to override)
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:  20  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  20  signed: 101  trust: 0-, 0q, 0n, 20m, 0f, 0u
gpg: depth: 2  valid:  78  signed:  21  trust: 78-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2025-06-16
Done

Reset mirror pool (y/N)? y
::INFO Downloading mirrors from Manjaro
::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json
::INFO => Mirror status: https://repo.manjaro.org/status.json
::INFO Using default mirror file
::INFO Querying mirrors - This may take some time

The update list is long, so I will just skip this part.

::INFO Writing mirror list

Again, long list, so I will skip.

::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database
error: could not read db 'extra' (Damaged tar archive)
warning: lua-luarepl: unknown key '%CHECKDEPENDS%perln' in sync database

And I ended up with same error.

scotty65 · 22 February 2025 23:26

Try the following:

sudo mv /var/lib/pacman/sync /var/lib/pacman/sync.old

Then:

sudo pacman -Syu

If those steps go okay, then you should have a new /var/lib/pacman/sync directory with the databases in it, and you can remove the /var/lib/pacman/sync.old directory:

sudo rm -fr /var/lib/pacman/sync.old

You should then refresh your Pamac databases. Leave the AUR out of it for this first step:

pamac update --no-aur --force-refresh

Then update the AUR database for Pamac:

pamac update --aur --force-refresh