Bug 352824 – dev-cpp/mm-common-0.9.2: QA Notice: Automake "maintainer mode" detected

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Pacho Ramos 2011-01-26 13:17:16 UTC]

And looks like it cannot be avoided even passing --disable-maintainer-mode configure option

>>> Completed installing mm-common-0.9.2 into /var/tmp/portage/dev-cpp/mm-common-0.9.2/image/

 * QA Notice: Automake "maintainer mode" detected:
 * 
 * 	(cd . >/dev/null && /bin/sh ./missing --run tar chof - skeletonmm/autogen.sh skeletonmm/.gitignore skeletonmm/AUTHORS skeletonmm/COPYING skeletonmm/ChangeLog skeletonmm/Makefile.am skeletonmm/README skeletonmm/configure.ac skeletonmm/skeletonmm.doap skeletonmm/build/.gitignore skeletonmm/codegen/Makefile.am skeletonmm/codegen/extradefs/generate_extra_defs_skeleton.cc skeletonmm/codegen/m4/convert.m4 skeletonmm/codegen/m4/convert_skeleton.m4 skeletonmm/codegen/m4/filelist.am skeletonmm/doc/Makefile.am skeletonmm/doc/reference/.gitignore skeletonmm/doc/reference/Doxyfile.in skeletonmm/examples/.gitignore skeletonmm/examples/Makefile.am skeletonmm/examples/example/example.cc skeletonmm/skeleton/.gitignore skeletonmm/skeleton/skeletonmm-uninstalled.pc.in skeletonmm/skeleton/skeletonmm.h skeletonmm/skeleton/skeletonmm.pc.in skeletonmm/skeleton/skeletonmmconfig.h.in skeletonmm/skeleton/skeletonmm/Makefile.am skeletonmm/skeleton/skeletonmm/filelist.am skeletonmm/skeleton/skeletonmm/wrap_init.h skeletonmm/skeleton/skeletonmm/private/.gitignore skeletonmm/skeleton/src/Makefile.am skeletonmm/skeleton/src/filelist.am skeletonmm/skeleton/src/skeleton.ccg skeletonmm/skeleton/src/skeleton.defs skeletonmm/skeleton/src/skeleton.hg skeletonmm/skeleton/src/skeleton_docs.xml skeletonmm/skeleton/src/skeleton_enum.defs skeletonmm/skeleton/src/skeleton_extra.defs skeletonmm/skeleton/src/skeleton_method.defs) | gzip -c >skeletonmm.tar.gz
 * 
 * If you patch Makefile.am, configure.in,  or configure.ac then you
 * should use autotools.eclass and eautomake or eautoreconf. Exceptions
 * are limited to system packages for which it is impossible to run
 * autotools during stage building. See
 * http://www.gentoo.org/proj/en/qa/autofailure.xml for more information.
ecompressdir: bzip2 -9 /usr/share/man

>>> Installing (1 of 1) dev-cpp/mm-common-0.9.2


Reproducible: Always

[Comment 1 Pacho Ramos 2011-01-26 13:18:08 UTC]

Created attachment 260771 [details]
build.log

[Comment 2 Rafał Mużyło 2011-01-26 13:36:28 UTC]

Well, it's a flaw of their build system.

They've put an explicit sed for docdir and PACKAGE_STRING, instead of trusting configure to DTRT in AC_CONFIG_FILES and another explicit call to 'missing',
instead of i.e AC_CHECK_PROG for tar.


See Makefile.am.

[Comment 3 Pacho Ramos 2011-06-04 10:27:31 UTC]

Rafal, I would really appreciate if you could provide a patch for this if you have time. Thanks a lot :-)

[Comment 4 Rafał Mużyło 2011-06-04 14:44:17 UTC]

Created attachment 275801 [details, diff]
patch that doesn't change a thing

The problem is I was a bit too optimistic - short story is that it seems to be a false positive of portage, that we simply need to live with.

See this patch - AM_MISSING_PROG(TAR, tar) results in the same string, that was before.

Unless the portage filter changes, the warning most likely stays.

[Comment 5 Pacho Ramos 2011-06-04 17:11:43 UTC]

(In reply to comment #4)
> Created attachment 275801 [details, diff]
> patch that doesn't change a thing
> 
> The problem is I was a bit too optimistic - short story is that it seems to be
> a false positive of portage, that we simply need to live with.
> 
> See this patch - AM_MISSING_PROG(TAR, tar) results in the same string, that was
> before.
> 
> Unless the portage filter changes, the warning most likely stays.

Thanks for your help, will CC portage team then(In reply to comment #4)

[Comment 6 Zac Medico 2011-06-04 22:45:46 UTC]

@Diego: Can you help us with this? I have no idea what the correct fix would be here.

[Comment 7 Diego Elio Pettenò (RETIRED) 2011-06-05 12:07:39 UTC]

This is not the sole false positive unfortunately :( we should probably limit to ./missing --run auto(conf|make) to warn on.

[Comment 8 Pacho Ramos 2011-06-19 11:59:17 UTC]

If this is a false positive, needs to be handled at package manager side

[Comment 9 Pacho Ramos 2012-10-20 07:01:15 UTC]

Looks finally solved in 0.9.6