I’ve noticed in the last few months (since the beginning of the current calendar year, maybe) that checkrebuild frequently misses applications that need rebuilding after an update, particularly if they are python applications.
Has anyone come up with any alternatives? Other than just maintaining a list of said applications and trying to run them following an update and reboot?
Is it about aur-check-rebuild?
It’s rebuild-detector.
I use the rebuild-detector pacman hook, which just runs /usr/bin/checkrebuild/, which is a script, not a binary. There is no reference to aur in checkrebuild, so I would say, no, it is not about aur-check-rebuild.
I see. The last update of this was 2 years ago, cf. GitHub - max-baz/rebuild-detector: Detects which Arch Linux packages need to be rebuilt · GitHub
To me, that means it’s not really surprising that it’s starting to overlook things.
One has to differentiate between a bug and a missing function. It has some limitations that are written in the documentation, and it also skips some checks for performance reasons. Not a perfect solution but better than nothing.
Pretty sure python subversions were just not planned at all to be scanned. Or maybe it is a bug, who knows.
Supported checks:
ldd: An executable is linked against a non-existent shared library
python: A package was built against an older Python version
perl: A package was built against an older Perl version
ruby: A package was built against an older Ruby version
haskell: A package was built against an older Haskell version
So yes, keep a list of applications that get ignored by checkrebuild and try executing them from a terminal immediately after every update if they are not mentioned in the output of the pacman hook. If they were broken by the update, rebuild them.