aur

Affected Version

Tested:
yay v11.1.0 - libalpm v13.0.1
yay v11.1.0.r4.g09695c6 - libalpm v13.0.1
The issue likely goes back for many versions.

Describe the bug

If you attempt to install an AUR devel package and it fails for whatever reason, the package still gets added to vcs.json. This means that the git repository for the package will be checked on any system upgrade with

pikaur -Vq

Pikaur v1.10.1
Pacman v6.0.1 - libalpm v13.0.1 - pyalpm v0.10.6

Description:

Some AUR packages result in dependency cycles because of their checkdeps=(). Examples include many R libraries, that pull in r-testthat for testing, which in turn has hard dependencies on some of the libraries themselves.

My workaround is usually iterative: first build packag

Is your feature request related to a problem? Please describe.
Files stored in /var/log are usually temporary, for pacstall however, it's not. When I was cleaning my system with bleachbit, it automatically deleted /var/log/pacstall/metadata which causes pacstall to not recognize any installed pacstall programs.

Describe the solution you'd like
Move /var/log/pacstall/metadata to

It would be very helpful to be able to list all packages managed by rua, and list what's the currently installed version, as well as whether there is a newer verson available.