Consider the following pipeline:
1. `makepkg` is creating a package
```
==> Creating package "clion-lldb"...
-> Generating .PKGINFO file...
```
2. a package is upgraded with `pacman -Syu`
```
:: Processing package changes...
(1/1) upgrading cuda-11.7
```
3. `makepkg` writes `.BUILDINFO`
```
-> Generating .BUILDINFO file...
error: could not open file /var/lib/pacman/local/cuda-11.7-11.7.1-3.1/desc: No such file or directory
```
The error happens from `write_buildinfo()` calling `run_pacman -Qi`, but `run_pacman()` does not lock on `pacman -Q*`. Whether the same hazard occurs with `pacman -Qq` for `RMDEPS` needs further research.
↧