I really hope this didn’t stump any of you. It’s okay, if it did, you probably didn’t use the console and therefor probably didn’t see what actually failed. So, the link to the package, nitrux-icon-theme_3.5.3.tar.gz, is dead. Which makes it kind of hard for the PKGBUILD script to download it, build it and install it.
Locating the missing source for nitrux-icon-theme on the AUR
And, if you run a quick pacman -Qi nitrux-icon-theme you quickly see there’s supposed to be a nitrux website at https://nitrux.in/. But, trying to go there, you can see they closed their doors. The project forked into two projects now known as NX Desktop and Nitrux OS.
I’m probably wrong (according to my girlfriend, I am always wrong), but since the launchpad.net team references the Nitrux OS domain, and it was the last source in the PKGBUILD in the AUR, I kind of assume it was the more “official” source (at least as far as following the package maintainer’s intent). Looking quickly at their website, we get sent off to trusty old GitHub where the repository is now Archived (this means, no longer supported).
Quick patching the PKGBUILD file for missing source nitrux-icon-theme
There’s a chance here the AUR package maintainer has noticed this and simply wants the package to die. He’s not responded to quite a few comments on the AUR as well. Anywho, here’s the fix:
Yikes! This page went to shit during migrations. I apologize for that. I will make a note to pay better attention to my SEO errors. The gist of this blog post was covering errors around “yay build file exists“. So, I’ll rebuild it from memory, the best I can. Hope this helps!
error: failed to commit transaction (conflicting files)
yay build file exists
yay build file exists
nss & lib32-nss: /usr/lib/p11-kit-trust.so exists in filesystem
As we can see above yay has run into an error where a file that it does not expect to still exist, does still exist and it has stopped running. This is a pretty easy fix. However, it startled me because of the packages that it flagged on ‘nss’ and ‘lib32-nss’ respectively. These are very important packages on almost any modern linux distribution.
Fortunately for you, and unfortunately for me, I have a bit of a wonton attitude when it comes to my personal machines. So, without hesitation, I threw in the –overwrite toggles on these two bad boys and simply crossed my fingers.
This worked out just fine for me. The files were safely overwritten and the machine continue to function without any problems. So, if it’s simply a matter of an existing file that’s not shared by other packages, feel free to overwrite it.