This is probably caused by incorrect order of building of packages. mate-desktop-1.28.2 is scheduled for build, but much later than mate-settings-daemon-1.28.0. The issue has occurred while trying to run `emerge --ask --emptytree @world` as required by profile update instructions. Reproducible: Always
Created attachment 896695 [details] emerge --info
Created attachment 896696 [details] build order
Created attachment 896697 [details] build log
Thanks for reporting. Putting mate-base/mate-desktop as bdepend will solve this once and for all. (Leaving note for when I return)
I don't see what this has to do with bdepend? It's looked up via pkg-config. It's also already in both DEPEND and RDEPEND, but the version bounds specifies: >=mate-base/mate-desktop-1.25.0 This is surely incorrect -- if the build system is probing for >= 1.27.1 then that means you can add a user-specific mask for newer versions to prevent upgrading, and install a mate-settings-daemon binpackage that does not work.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=94c8e8823fe2ede3f16fad27302b858afabdd67a commit 94c8e8823fe2ede3f16fad27302b858afabdd67a Author: Pacho Ramos <pacho@gentoo.org> AuthorDate: 2024-07-08 21:32:47 +0000 Commit: Pacho Ramos <pacho@gentoo.org> CommitDate: 2024-07-08 21:32:47 +0000 mate-base/mate-settings-daemon: Build needs mate-desktop >= 1.27.1 Closes: https://bugs.gentoo.org/935279 Signed-off-by: Pacho Ramos <pacho@gentoo.org> mate-base/mate-settings-daemon/mate-settings-daemon-1.28.0.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)