![](https://popplesburger.hilciferous.nl/pictrs/image/c1ad0046-f2ee-4988-aa2d-533aca036635.jpeg)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Looks like the maintainer has better things to do
In post on the Gradience Discord, the tool’s primary developer David Lapshin (daudix) explains: –
“Archiving the project […] will make it clear that Gradience is, well, unmaintained, and will prevent the issue tracker from being filled with duplicates asking when new release will be out/why nautilus sidebar is white.”
“And, if someone will want to maintain it one day, it can always be unarchived with a press of a button.”
This usually happens when Manjaro doesn’t carry a package that Arch does carry (and that the package you’re trying to install from the AUR depends on).
This is always a risk when combining Manjaro with the AUR, as Manjaro is a few weeks behind Arch when it comes to packaging. You can try if the beta repositories have the package, but otherwise you’ll just have to wait for Manjaro to update its packages. It’ll probably resolve itself, eventually.
You can try looking on the Manjaro forums (I don’t see a workaround other than switching to testing/unstable) to check if there’s a fix, but please don’t bother the Arch/AUR people, they can’t help you.