to which I ask @ r0ckhopper (or anyone) if this advice is still valid?
"So in .cache, there may be a folder called yay. In this folder is the cache of files used when you built each AUR package. There may be a folder for each of auto-cpufreq, idlex, starsector and thonny. Delete each of those and then you can reinstall whichever ones you want from the AUR (as I said hopefully with Python 3.11).
If there is no yay folder in .cache, no need to worry, you can just reinstall those packages."
So, if I took the steps you outlined to identify said folders, then deleted all those folders, uninstall AUR offending foreign packages, rebooted, and reinstalled (rebuild) zoom and librewolf again I should be fine?
This is just rebuild-detector at work. It’s simply telling you that librewolf-bin and zoom (two foreign packages, as in not from the official repos) need to be rebuilt against the new and updated libraries. I bet if you run checkrebuild on the command line, those two AUR packages will be listed out as well (unless you have rebuilt them before running the command, of course).
Foreign packages are the ones that did not come from the repos that you have enabled in your /etc/pacman.conf, but are installed manually. This, by definition, includes all AUR packages.
While running rebuild-detector, I discovered two more packages.
So I used the simple --rebuildtree command with the -S arguments, rebuilt the packages, did a -Syyu for good measure and all foreign disappeared from yay output.
thanks @anthony93 and other responders, this is solved.
Technically, rebuild-detector is the package name. The actual command you ran is checkrebuild, which is provided by the rebuild-detector package. Just putting out there to avoid confusion.
$ pacman -Si rebuild-detector
Repository : extra
Name : rebuild-detector
Version : 4.4.2-1
Description : Detects which packages need to be rebuilt
Architecture : any
URL : https://github.com/maximbaz/rebuild-detector
Licenses : ISC
Groups : None
Provides : None
Depends On : binutils parallel pacutils pacman-contrib
Optional Deps : None
Conflicts With : None
Replaces : None
Download Size : 6.01 KiB
Installed Size : 6.11 KiB
Packager : Maxim Baz <maximbaz@archlinux.org>
Build Date : Wed 22 Mar 2023 05:33:39 AM +08
Validated By : MD5 Sum SHA-256 Sum Signature
I know you did. But what if someone else read what you wrote and got confused thinking that you ran rebuild-detector? I did mention earlier that my reply was meant to be a clarification, didn’t I?
After reading through the pacman hook provided by rebuild-detector, I may have found the answer.
[Trigger]
Operation = Upgrade
Type = Package
Target = *
[Action]
Description = Checking which packages need to be rebuilt
Exec = /usr/bin/checkrebuild
When = PostTransaction
NeedsTargets
The NeedsTargets option is included under the [Action] section, which means that the packages that were upgraded during that transaction will be piped (passed via stdin) into checkrebuild when the hook was triggered. This is different from running checkrebuild from the command line without piping anything into it because if you pass a list of packages into checkrebuild via stdin, checkrebuild will only run ldd checks against direct dependencies of those packages.
My current conjecture (I could be wrong on this, of course) is that the other two extra packages were broken by an older update, not the update that is the focus of this post. Those two extra packages were already broken before you even ran the yay update prior to the original post, but because none of the packages upgraded in that yay update affects the other two packages, the rebuilt-detector hook didn’t detect them.
quite possible–I’d call that a solid conjecture. one was gnome-terminal-transparency and the other was also a lesser AUR package.
they were reported broken by check-rebuild and not by yay because both commands had a different way of seeing (i.e. hooks) makes perfect sense to me.
thanks for looking into it further.
I have added this stuff to my maintenance list!
