https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-text/poppler-25.01.0 installs the same files with USE=doc. Discovered on: amd64 (internal ref: ci) NOTE: To reproduce this issue: 1) Install the package without USE=doc 2) Put the list of the installed files into a file ( qlist -e PACKAGE:SLOT | sort | uniq > /tmp/qlist1 ) 3) Install the package with USE=doc 4) Put the list of the installed files into a file ( qlist -e PACKAGE:SLOT | sort | uniq > /tmp/qlist2 ) 5) See the diff between the two files ( diff -ru /tmp/qlist_1 /tmp/qlist_2 ) On this machine: - the installed files without USE=doc are 142 - the installed files with USE=doc are still 142 Usually USE=doc is supposed to build and install documentation files, so a build with USE=doc should install more files. If that's not the case, feel free to close. This type of report comes from a check that is a bit outside of the tinderbox, that's the reason because build.log was not provided (however in cases like these the build.log doesn't help much) but if you need further help to diagnose this issue feel free to ask.
It would be nice to still get logs with such a bug report. The *assumption* here going into the bug is that this is being reproduced by poppler[-cairo], as there's this in the ebuild: > if use cairo && use doc && [[ ${PV} != *9999* ]]; then ...because *with* USE=cairo, there is an installed files difference: * app-text/poppler-25.01.0[cairo,-doc] Total files : 220 Total size : 10.11 MiB * app-text/poppler-25.01.0[cairo,doc] Total files : 274 Total size : 11.76 MiB The installed documentation is popper-glib related only, which is shipped pre-generated, whereas we do not generate docs for other frontends. Since it makes no sense to ship it with cairo disabled, but it also is nonsensical to obsess about USE=doc too much, a REQUIRED_USE="doc? ( cairo )" was never added.
(In reply to Andreas Sturmlechner from comment #1) > It would be nice to still get logs with such a bug report. You absolutely right, but as stated they happens a bit before tinderbox. The idea is that if maintainer can't reproduce the issue, a build log can be re-generated and sent here. Anyway the assumption of -cairo is right.
