Arch Linux User Repository

powerlevel10k git repo ... FAILED (unknown public key 90ACE942EB90C3DD) ==> ERROR: One or more PGP signatures could not be verified! I'm getting this while switching from the repo package to the AUR package. Do I need to manually import a key?

The latest build solution,

# build gitstatus
  cd "$srcdir/powerlevel10k/gitstatus"
  export CXXFLAGS+=" -I${srcdir}/libgit2-${_libgit2ver}/include -DGITSTATUS_ZERO_NSEC -D_GNU_SOURCE"
  export LDFLAGS+=" -L${srcdir}/libgit2-${_libgit2ver}"
+ sed -i 's/-Werror/#-Werror/g' Makefile
  make

the later commit have already remove -Werror

Getting new error here not described -- any suggestions??:

-flto=auto -I/home/kevdog/.cache/yay/zsh-theme-powerlevel10k/src/libgit2-tag-2ecf33948a4df9ef45a66c68b8ef24a5e60eaac6/include -DGITSTATUS_ZERO_NSEC -D_GNU_SOURCE -std=c++14 -funsigned-char -O3 -DNDEBUG -DGITSTATUS_VERSION=v1.5.4 -Wall -Werror  -Wall -c -o obj/tag_db.o src/tag_db.cc

src/tag_db.cc: In member function ‘std::string gitstatus::TagDb::TagForCommit(const git_oid&)’:
src/tag_db.cc:133:43: error: ignoring return value of ‘std::unique_lock<_Mutex>::unique_lock(mutex_type&) [with _Mutex = std::mutex; mutex_type = std::mutex]’, declared with attribute ‘nodiscard’ [-Werror=unused-result]
  133 |   if ((std::unique_lock<std::mutex>(mutex_), id2name_dirty_)) {
      |                                           ^
In file included from /usr/include/c++/14.1.1/condition_variable:43,
                 from src/tag_db.h:27,
                 from src/tag_db.cc:18:
/usr/include/c++/14.1.1/bits/unique_lock.h:70:16: note: declared here
   70 |       explicit unique_lock(mutex_type& __m)
      |                ^~~~~~~~~~~
cc1plus: all warnings being treated as errors
make: *** [Makefile:32: obj/tag_db.o] Error 1
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: zsh-theme-powerlevel10k-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
zsh-theme-powerlevel10k - exit status 4

My installation gave exactly the same error as my friend @micwoj92.
So I did the configuration that @thayne explained, leaving it like this:

pkgname=zsh-theme-powerlevel10k
pkgver=1.20.0
pkgrel=3
 pkgdesc="Powerlevel10k is a theme for Zsh. It emphasizes speed, flexibility and out-of-the-box experience."
 arch=('x86_64')
 url='https://github.com/romkatv/powerlevel10k'
 license=('MIT')
depends=('glibc' 'zsh' 'gitstatus')
 optdepends=(
   'ttf-meslo-nerd-font-powerlevel10k: recommended font'
   'powerline-fonts: patched fonts for powerline')
 replaces=('zsh-theme-powerlevel9k')
 source=("powerlevel10k-${pkgver}.tar.gz::https://github.com/romkatv/powerlevel10k/archive/v${pkgver}.tar.gz")
sha256sums=('d8187d44b697b3a37a8c4896678b4380e717cbf2850179529358348780a2d3d7')

 package() {
  cd "powerlevel10k-${pkgver}"
  # only copy over the files we need
  install -D LICENSE "${pkgdir}/usr/share/license/${pkgname}"
  install -d "${pkgdir}/usr/share/${pkgname}"
  install powerlevel10k.zsh-theme powerlevel9k.zsh-theme \
    prompt_powerlevel10k_setup prompt_powerlevel9k_setup \
    "${pkgdir}/usr/share/${pkgname}"

  find config internal -type f -exec install -D '{}' "${pkgdir}/usr/share/${pkgname}/{}" ';'
  # p10k expects gistatus to be under the p10k directory, so create a symlink
  ln -s /usr/share/gitstatus "${pkgdir}/usr/share/${pkgname}/gitstatus"

   cd "${pkgdir}/usr/share/${pkgname}"
  for file in *.zsh-theme internal/*.zsh; do
     zsh -fc "emulate zsh -o no_aliases && zcompile -R -- $file.zwc $file"
   done
 }

Before installing it, I installed the gitstatus-bin package. Better than waiting 2 hours for the other package to compile.
Then I installed this package and it didn't give any errors, it was fast and it worked. It's that simple.
It would be better to change this configuration to what @thayne suggested.

If here in the AUR there are already the zsh-theme-powerlevel10k-git and zsh-theme-powerlevel10k-bin-git packages, I don't see any point in this one also being a git version.

About the font, I found one that is the equivalent of "ttf-meslo-nerd-font-powerlevel10k", which is the ttf-meslo-nerd. Very good it.

Build fails:

src/tag_db.cc: In member function ‘std::string gitstatus::TagDb::TagForCommit(const git_oid&)’:
src/tag_db.cc:133:43: error: ignoring return value of ‘std::unique_lock<_Mutex>::unique_lock(mutex_type&) [with _Mutex = std::mutex; mutex_type = std::mutex]’, declared with attribute ‘nodiscard’ [-Werror=unused-result]
  133 |   if ((std::unique_lock<std::mutex>(mutex_), id2name_dirty_)) {
      |                                           ^
In file included from /usr/include/c++/14.1.1/condition_variable:43,
                 from src/tag_db.h:27,
                 from src/tag_db.cc:18:
/usr/include/c++/14.1.1/bits/unique_lock.h:70:16: note: declared here
   70 |       explicit unique_lock(mutex_type& __m)
      |                ^~~~~~~~~~~
cc1plus: all warnings being treated as errors
make: *** [Makefile:31: obj/tag_db.o] Error 1
make: *** Waiting for unfinished jobs....
==> ERROR: A failure occurred in build().
    Aborting...

Something else of note is that the xz package uses a git source along with a checksum. Is it not possible to do that here as well, using e.g. makepkg --geninteg?

@phonemic That's because xz uploaded their own tarballs instead of relying on GitHub's automatic tarballs that are guaranteed to be the actual, unmodified repo code and cannot be modified. Notice that the xz package relied on "releases/download", while this package relied on "archive". I'd also support having the xz package use GitHub's automatic tarballs instead.

@aliu I'm not sure what you mean. A malicious maintainer can put files in tarballs that are not in the git repo. The fix for xz was moving from using the tarballs to the repo directly.

https://gitlab.archlinux.org/archlinux/packaging/packages/xz/-/commit/881385757abdc39d3cfea1c3e34ec09f637424ad

@phonemic One cannot modify tarballs on GitHub.

@aliu based on the recent xz shenanigans, I think more packages should move away from tarballs and build off git directly.