https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: sys-fs/gfs2-utils-3.3.0 uses automake in maintainer-mode. Discovered on: amd64 (internal ref: guru_tinderbox)
Created attachment 701436 [details] build.log build log and emerge --info
Changing the Assignee as per https://archives.gentoo.org/gentoo-dev/message/74ee632e9fe2f4c12890524fec132205
Changing TRACKER as requested by QA.
guru_tinderbox has reproduced this issue with version 3.4.1 - Updating summary.
I can't reproduce this neither in 3.4.1 nor in newly added 3.5.1. The ebuild already calls `eautoreconf`, so as far as I understand this QA shouldn't fire. Any pointers on how to reproduce/fix this one?
It's detecting this line: https://pagure.io/gfs2-utils/blob/b52677874d0e9fe4d311bd0ce430299e7ddc4c3c/f/tests/Makefile.am#_72 Still exists in 3.5.1.
(In reply to Takuya Wakazono from comment #6) > It's detecting this line: > https://pagure.io/gfs2-utils/blob/b52677874d0e9fe4d311bd0ce430299e7ddc4c3c/f/ > tests/Makefile.am#_72 > Still exists in 3.5.1. Ok, I have no idea if it is a correct behaviour or what should we do instead. Note: In ::gentoo (likely) to mitigate the same issue sys-apps/kbd and net-firewall/firewalld has next lines: -------------- # Testsuite's Makefile.am calls missing(!) # ... but this seems to be consistent with the autoconf docs? # Needs more investigation: https://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/autom4te-Invocation.html QA_AM_MAINTAINER_MODE=".*--run autom4te --language=autotest.*" -------------- All in all, I don't understand it, so I won't touch it...