When updating tonight with both EnOS x86_64 and EnOS ARM and with Plasma, I got the following from yay
:: Synchronizing package databases...
endeavouros is up to date
core is up to date
extra is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
-> Orphan (unmaintained) AUR Packages: kfilemetadata5
-> kfilemetadata5: local (5.116.0-2) is newer than AUR (5.116.0-1)
there is nothing to do`:: Synchronizing package databases...
endeavouros is up to date
core is up to date
extra is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
-> Orphan (unmaintained) AUR Packages: kfilemetadata5
-> kfilemetadata5: local (5.116.0-2) is newer than AUR (5.116.0-1)
there is nothing to do
Attention to the lines
-> Orphan (unmaintained) AUR Packages: kfilemetadata5
-> kfilemetadata5: local (5.116.0-2) is newer than AUR (5.116.0-1)
The AUR does have kfilemetadata5-5.116.0-1 and the regular Archlinux package repository does not have any version of kfilemetadata5. So where did
kfilemetadata5-5.116.0-2 come from??
Yes, it would have stayed there as long as something else required it that was also in the repo. Once whatever package was requiring it was updated to not use it anymore, it would have been dropped from the repos.
This has been slowly happening with many k*5 packages as they are no longer needed.