[solved] llvm rR ?

[flysideways]

Recently llvm (11, 12, 13) on ~arm64 wants to be rebuilt, repeatedly. What is going on?

python 3.9 and 3.10, glib 2.7, gobject-introspection, and p11-kit also are rebuilding.

It's the rR output. The man page indicates it is due to slots changing. There is no message indicating what is causing the rebuilds, I thought I remembered seeing that message when there were rebuilds, but not here.

[alamahant]

You should have noted at the end of emerge output

"this and that package are causing rebuilds"

"rR" maybe caused from new USE or dependency updates.
_________________

[flysideways]

That's just it, the message is not there.

[flysideways]

Doing equery depends on the updated packages yields nothing, as does equery depgraph on the rR packages. After the update, the box still wants to do the rebuilds.

[Hu]

Perhaps a slot has already been changed, and LLVM and friends should have been updated then, but were not, so this is a delayed update, and that is why no package is cited as a cause? That would not explain why they keep rebuilding if you allow Portage to do them once, though.

[GDH-gentoo]

[flysideways]

[Hu]

It looks like the Gentoo maintainers only mark ESR series as stable, and keep non-ESR as testing. If so, then it should be sufficient to set Portage to only accept stable-keyworded www-client/firefox.

[flysideways]

Thanks Hu. Of course it is that easy. Once and done.