Created attachment 700734 [details]
build.log as attachment.
I believe you should report it upstream, I cannot really imagine supporting live builds in terms of such errors.
This was hit by a tinderbox run, I have no personal attachment to this project.
What do you think about removing -9999 ebuild if you cba to maintain it?
Let me clarify to not sound that rude (it was not my intention):
Usually upstream keeps flags like these on during development cycles, and I have no clue what's causing the issue as I'm not invested in upstream. But the fix to get this compiled on Gentoo is easy, just strip / patch out any -Werror flags.
(In reply to Joonas Niilola from comment #2)
> What do you think about removing -9999 ebuild if you cba to maintain it?
It has it's purposes, running it via tinderbox when it's intentionally not even keyworded is not one of them. I do not want to remove it just because you hit a build failure there
Looked more into it. The girara_command_run was not present in girara 0.3.5 that your bug report seems to be using, I see single mention of it in your log
Run-time dependency girara-gtk3 found: YES 0.3.5
In the current girara 0.3.7 it is declared in girara/commands.h header as bool and the header is in fact included, in 0.3.5 it was there, but did not had girara_commands_run at all. The ebuilds already has >=0.3.7 dependency on girara so I believe this is addressed now.
Author: Piotr Karbowski <email@example.com>
Date: 2023-01-08 16:28:02 +0100
app-text/zathura: 0.5.2-r1, 9999: add subslot.
The plugins needs to be rebuilt after zathura updates in order to work.
Signed-off-by: Piotr Karbowski <firstname.lastname@example.org>
The commit syncs 9999 and 0.5.2-r1 ebuilds ensuring dependencies parity bumping girara on 9999 ebuild to >=0.3.7.
I still would like to challenge the feasibility of reporting issues of this kind in live ebuilds. Here we had a new zathura code that was depending on new girara dependency, while I bumped it in tree on 2022-03-28, your report from 2021-04-19 seems to be using the old version 0.3.5, I do not think it is reasonable to expect 9999 ebuilds to have always up to date deps as soon as upstream changes the development branch, if it had, it would pull the 0.3.7 update on your testing system and we wouldn't have this bug.
If you still insist on going with 9999 testing and reports, please make sure that you provide some more information, like dump of installed packages, and if possible, try to update your @world to latest and re-trying 9999 ebuild before filling a report. Thanks.
Sorry, I did it again, mixed the dates, 2021 != 2022, of course you couldn't had the latest girara that was added year after your report. Though I stand strong with rest of the comment re 9999 testing. It failed because there was no compatible girara in tree.