Admin message

Due to an influx of spam, we have had to require each new account to be manually approved. Please register an account and then write an email to accountsupport@archlinux.org to get it approved. Sorry for the inconvenience.

makepkg --install leaves stray download-XXXXXX dir behind
This appears to be a new regression in `pacman-7.1`. I noticed it while building pkgs with `devtools` (the default Arch build tools enable `namcap` which results in the just-built pkg [getting installed into the clean chroot with `makepkg --install`](https://gitlab.archlinux.org/archlinux/devtools/-/blob/v1.4.0/src/makechrootpkg.in?ref_type=tags#L306)). # Steps to reproduce: 1. build any pkg with `makepkg --install` 2. check the default cachedir and notice a stray "download" dir is left behind e.g. `/var/cache/pacman/pkg/download-GKRsZK`
issue