Hello, Arve. On Mon, Feb 09, 2026 at 16:26:14 +0100, Arve Barsnes wrote: > On Mon, 9 Feb 2026, at 15:27, Alan Mackenzie wrote: > > So, the question remains, why is emerge @preserved-rebuild trying to > > merge php-8.2.30? Nothing uses it. Why does the emerge -pqeO command > > even show this ebuild? This feels like a bug.
> First of all, how did you decide on this command? -e and -O seem to be > opposing options that I bet could lead to weird results. It was listed on the wiki page Package_sets as a way to see the content of a set. > Second, did you ever install this manually, putting it in your @world > set? Try emerge -pcv dev-lang/php:8.2 to see if it can be easily > removed, and it will tell you what, if anything, keeps the package > there. There is now nothing depending on php:8.2. > You obviously don't want it there, so try to remove it before trying to > figure out the potentially deep dependency that brings it in. The problem in my system seems to be that /var/db/pkg/dev-lang/php-8.2.28-r1 exists, but /usr/portage/dev-lang/php/php-8.2.28-r1.ebuild doesn't. I suspect this happened when 8.2.28-r1 was superseded by a later version, leaving other packages dependent upon that version. Some while later, 8.2.28-r1 was removed from the repository, but without the other packages being updated to use its replacement. So the old package persisted in /var/db/pkg/.... Or something like that. > Regards, > Arve -- Alan Mackenzie (Nuremberg, Germany).
