pacman

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

Pacman hook for regenerating the graph should possibly run after other PostTransaction hooks, which might for example handle .pacnew files. According to man 5 alpm-hooks the running order is defined by the alphabetical order of the hooks filenames, so 10-pacwall.hook is one of the first hooks to be triggered, while it should actually be the last. R

https://zacharypatten.github.io/dotnet-console-games/Draw

The game buttons in the Website project are currently just slapped on without much thought. This makes the games pretty hard and annoying to play on mobile or any platform where the user can't use a keyboar

I have multiple packages installed from AUR which are offered for update every time I run yup but IMHO they shouldn't.

I.e. in todays output:

==> Checking for AUR updates...

==> Found 2 local package(s) that are newer than their AUR package
    numix-icon-theme-pack-git  r6767-1 has AUR version r6086-1
    ttf-consolas-with-yahei-powerline-git  r.-1 has AUR version r14.b6e9163-1

If packages/database uses signing then one needs to run gpg --detach-sign manually each time a package is added to the repo.

It makes sense if repoctl has an option to automate the signing process. i.e.

• run gpg signing for the package before adding it to database
• run gpg signing for the database after the package is added to database