https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-text/poppler-24.01.0 fails to compile. Discovered on: arm64 (internal ref: tinderbox_arm64) Info about the issue: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CF0014
Created attachment 883710 [details] build.log build log and emerge --info
Error(s) that match a know pattern in addition to what has been reported in the summary: Could not find a package configuration file provided by "Qt5Gui" (requested Could not find the 5.12 version of Qt5Gui. If you're not interested in the
Can you show the output of emerge -p -uvDU @world as the system currently is? emerge -p -uvDU @world --debug would be useful too
(In reply to Sam James from comment #3) > Can you show the output of emerge -p -uvDU @world as the system currently is? > > emerge -p -uvDU @world --debug would be useful too ~ $ emerge -p -uvDU @world These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 7.33 s (backtrack: 0/100). Total: 0 packages, Size of downloads: 0 KiB I will add the debug as attachment
Created attachment 883714 [details] debug.txt.xz debug.txt (compressed because it exceeds attachment limit, use 'xzless' to read it)
There's only: ``` runtime cycle digraph (4 nodes): (media-libs/freetype-2.13.2-2:2/2::gentoo, installed) depends on (media-libs/harfbuzz-8.3.0-2:0/6.0.0::gentoo, installed) (runtime) (media-libs/harfbuzz-8.3.0-2:0/6.0.0::gentoo, installed) depends on (x11-libs/cairo-1.18.0-1:0/0::gentoo, installed) (runtime_slot_op) (media-libs/freetype-2.13.2-2:2/2::gentoo, installed) (runtime_slot_op) (x11-libs/cairo-1.18.0-1:0/0::gentoo, installed) depends on (media-libs/fontconfig-2.15.0-1:1.0/1.0::gentoo, installed) (runtime) (media-libs/freetype-2.13.2-2:2/2::gentoo, installed) (runtime) (media-libs/fontconfig-2.15.0-1:1.0/1.0::gentoo, installed) depends on (media-libs/freetype-2.13.2-2:2/2::gentoo, installed) (runtime) ``` I know you mentioned before you have --complete-graph in all your emerge invocations in your scripts, but could you add it into EMERGE_DEFAULT_OPTS in case it's missing from one? It would also mean we can see it in bugs immediately so don't need to ask then.
(In reply to Sam James from comment #6) > I know you mentioned before you have --complete-graph in all your emerge > invocations in your scripts, but could you add it into EMERGE_DEFAULT_OPTS > in case it's missing from one? It would also mean we can see it in bugs > immediately so don't need to ask then. Atm I don't remember exactly what but I think I had an issue with that, that's the reason because it is manually added only when needed. Anyway good hint. Do you think is possible make portage add in the build log which options was passed to emerge? So we always have a complete list.
