Created attachment 907117 [details] log of the failed build this ebuild has been broken for a few weeks (maybe longer idk) building from upsource works.
It builds fine for me. Can you attach your emerge --info?
Created attachment 907118 [details] emerge --info here you go
Created attachment 907120 [details] log of successful build with clang It also fails to build for me, but only with GCC. It successfully merged using a per-package Clang environment, here is the log.
Created attachment 907121 [details] carbohydration emerge --info If it helps, here is my emerge --info.
i would also note that the -9999.ebuild also doesn't work
I tried downgrading sdbus-c++ to 1.4.0-r1 but both the 1.3.3-r2 and 9999 ebuilds still fail.
I also still trying to find a way to solve it I also gonna update it since stdbus++ 2.0 landed. But it very strange why only gcc is giving this problem
The only possibly relevant fix I see in sdbus-c++ git is https://github.com/Kistler-Group/sdbus-cpp/commit/c6705faf2f1a4743e3d49038b37815f9b943da20.
For me building with sdbus-c++:0/1 suceeds and with :0/2 fails. That's why I have commited https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=71d561fc4322089d6287c3ba237a1b5cc57fd098. I did not check for open bugs so I did not tag the commit.
(In reply to Filip Kobierski from comment #9) > For me building with sdbus-c++:0/1 suceeds and with :0/2 fails. > > That's why I have commited > https://gitweb.gentoo.org/repo/proj/guru.git/commit/ > ?id=71d561fc4322089d6287c3ba237a1b5cc57fd098. > > I did not check for open bugs so I did not tag the commit. You should always have some reference when adding a </pinning a dep, otherwise it'll rot forever.
so I should include a comment explaining the limit in the ebuild?
(In reply to Filip Kobierski from comment #11) > so I should include a comment explaining the limit in the ebuild? At the very least, yes. It should usually be accompanied by at least a link to a Gentoo bug as well and usually an upstream report.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=f8f43ea166cdc764b87b33b519f75e7dcd1d76e3 commit f8f43ea166cdc764b87b33b519f75e7dcd1d76e3 Author: Filip Kobierski <fkobi@pm.me> AuthorDate: 2024-10-31 12:39:35 +0000 Commit: Filip Kobierski <fkobi@pm.me> CommitDate: 2024-10-31 12:39:35 +0000 gui-libs/xdg-desktop-portal-hyprland: drop 1.3.3-r2 I have added the r3 yesterday and now I noticed that portage wants to upgrade hyprlock and downlgrade the desktop portal. That is unacceptable as r2 does not build so I remove it to not allow that. Closes: https://bugs.gentoo.org/942404 Signed-off-by: Filip Kobierski <fkobi@pm.me> .../xdg-desktop-portal-hyprland-1.3.3-r2.ebuild | 72 ---------------------- 1 file changed, 72 deletions(-) Additionally, it has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=1bf6c46f258f6813aaaea02c5190f7881b96bfd0 commit 1bf6c46f258f6813aaaea02c5190f7881b96bfd0 Author: Filip Kobierski <fkobi@pm.me> AuthorDate: 2024-10-31 13:38:02 +0000 Commit: Filip Kobierski <fkobi@pm.me> CommitDate: 2024-10-31 13:38:02 +0000 gui-libs/xdg-desktop-portal-hyprland: fix previous commit Bug: https://bugs.gentoo.org/942404 Signed-off-by: Filip Kobierski <fkobi@pm.me> .../xdg-desktop-portal-hyprland-1.3.3-r3.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
