Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 226311 - x11-libs/pango: autotools are being rebuilt through maintainer-mode
Summary: x11-libs/pango: autotools are being rebuilt through maintainer-mode
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
: 226841 (view as bug list)
Depends on: gnome2.30
Blocks: bad-autotools
  Show dependency tree
Reported: 2008-06-13 12:27 UTC by Diego Elio Pettenò (RETIRED)
Modified: 2010-06-13 15:30 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---

x11-libs:pango-1.20.5:20080704-133609.log (x11-libs:pango-1.20.5:20080704-133609.log,191.14 KB, text/plain)
2008-07-17 19:29 UTC, Diego Elio Pettenò (RETIRED)

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Elio Pettenò (RETIRED) gentoo-dev 2008-06-13 12:27:40 UTC
Rebuilding autotools through maintainer-mode is _not_ good, because it usually means you forget to add dependencies, and they'll magically use the same version as used by upstream, which might not be what the user have installed at all.

If you patch or you _have to_ use autotools.eclass and eautomake/eautoreconf. Exceptions are granted _only_ for system packages that would make it impossible to run autotools during stagebuilding.

Please fix your package.
Comment 1 Mart Raudsepp gentoo-dev 2008-07-17 12:04:08 UTC
Please show me the proof that it is actually rebuilt. Patching and together and/or and configure together is no problem in my years of experience. It is a problem when or is patched, but not and eautoreconf is not called - then it will hit maintainer-mode rebuild, but we patch all matching things unless you provide a build.log that shows otherwise.
So this is INVALID until such a time.
Comment 2 Diego Elio Pettenò (RETIRED) gentoo-dev 2008-07-17 12:08:37 UTC
config.status: pango/pango-features.h is unchanged
        backends: FreeType X Xft Cairo
 cd . && /bin/sh /var/tmp/portage/x11-libs/pango-1.20.5/work/pango-1.20.5/missing --run automake-1.10 --gnits  Makefile
aclocal.m4:16: warning: this file was generated for autoconf 2.61.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'. warning: AC_CACHE_VAL(lt_prog_compiler_pic_works, ...): suspicious cache-id, must contain _cv_ to be cached
../../lib/autoconf/general.m4:1973: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:1993: AC_CACHE_CHECK is expanded from...
aclocal.m4:687: AC_LIBTOOL_COMPILER_OPTION is expanded from...
aclocal.m4:4977: AC_LIBTOOL_PROG_COMPILER_PIC is expanded from...
aclocal.m4:2757: _LT_AC_LANG_C_CONFIG is expanded from...
aclocal.m4:2756: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
aclocal.m4:134: AC_LIBTOOL_SETUP is expanded from...
aclocal.m4:114: _AC_PROG_LIBTOOL is expanded from...
aclocal.m4:79: AC_PROG_LIBTOOL is expanded from...
aclocal.m4:6522: AM_PROG_LIBTOOL is expanded from... the top level warning: AC_CACHE_VAL(lt_prog_compiler_static_works, ...): suspicious cache-id, must contain _cv_ to be cached
aclocal.m4:732: AC_LIBTOOL_LINKER_OPTION is expanded from... warning: AC_CACHE_VAL(lt_prog_compiler_pic_works_CXX, ...): suspicious cache-id, must contain _cv_ to be cached
aclocal.m4:2834: _LT_AC_LANG_CXX_CONFIG is expanded from...
aclocal.m4:2833: AC_LIBTOOL_LANG_CXX_CONFIG is expanded from...
aclocal.m4:1882: _LT_AC_TAGCONFIG is expanded from... warning: AC_CACHE_VAL(lt_prog_compiler_static_works_CXX, ...): suspicious cache-id, must contain _cv_ to be cached warning: AC_CACHE_VAL(lt_prog_compiler_pic_works_F77, ...): suspicious cache-id, must contain _cv_ to be cached
aclocal.m4:4056: _LT_AC_LANG_F77_CONFIG is expanded from...
aclocal.m4:4055: AC_LIBTOOL_LANG_F77_CONFIG is expanded from... warning: AC_CACHE_VAL(lt_prog_compiler_static_works_F77, ...): suspicious cache-id, must contain _cv_ to be cached warning: AC_CACHE_VAL(lt_prog_compiler_pic_works_GCJ, ...): suspicious cache-id, must contain _cv_ to be cached
aclocal.m4:4165: _LT_AC_LANG_GCJ_CONFIG is expanded from...
aclocal.m4:4164: AC_LIBTOOL_LANG_GCJ_CONFIG is expanded from... warning: AC_CACHE_VAL(lt_prog_compiler_static_works_GCJ, ...): suspicious cache-id, must contain _cv_ to be cached
 cd . && /bin/sh ./config.status Makefile
config.status: creating Makefile
Making all in pango
Making all in opentype

is this bloody enough for you?
Have you even bothered checking the ebuild? Have you bothered checking  "${FILESDIR}/${PN}-1.2.5-lib64.patch" ?
Comment 3 Rémi Cardona gentoo-dev 2008-07-17 15:18:30 UTC
Hey, chill out friends, it's no big deal :)

I've commented out the first hunk in the patch (now only the C file and are actually modified) and indeed maintainer-mode is no longer activated.

Fixed in CVS.
Comment 4 Mart Raudsepp gentoo-dev 2008-07-17 15:21:15 UTC
This is absolutely wrong. This will break under our nose as soon as we add a complex build system patch that will need an eautoreconf
Comment 5 Mart Raudsepp gentoo-dev 2008-07-17 15:27:33 UTC
(In reply to comment #2)
> Have you even bothered checking the ebuild? Have you bothered checking 
> "${FILESDIR}/${PN}-1.2.5-lib64.patch" ?

Yes, it patches both, so it should be fine. Please elaborate on the appropriate thread on gentoo-dev that I posted about this ordeal two weeks ago with your comments on why this is technically not enough. Because it is for most packages and we should fix it properly, not throw eautoreconf waiting time to all of our users.
Comment 6 Rémi Cardona gentoo-dev 2008-07-17 15:49:12 UTC

I've forced the old patch (that modifies both Makefile.{in,am}) to apply without multilib and I can't reproduce the autoremake.

Could you attach a full build.log and emerge --info so we can compare with what you have on your system?

Comment 7 Diego Elio Pettenò (RETIRED) gentoo-dev 2008-07-17 19:29:11 UTC
Created attachment 160661 [details]

Feel free, I actually told eva more than once about this thing not working properly.

If you want a reason for the problem: 2003 is _way_ behind from today, the rest of the autotools will result newer than the, and there you go with your maintainer mode triggered.
Comment 8 Rémi Cardona gentoo-dev 2008-07-18 09:31:50 UTC
Diego, I have a hunch that the patch is not causing this, because the Makefile causing the autoremake is ${S}/ and not ${S}/pango/ (which is the one modified by the patch).

Could you try rebuilding pango with the lib64 patch completely disabled?

Comment 9 Gilles Dartiguelongue gentoo-dev 2008-08-23 10:53:56 UTC
*** Bug 226841 has been marked as a duplicate of this bug. ***
Comment 10 Gilles Dartiguelongue gentoo-dev 2009-06-29 21:57:05 UTC
This should not happen nowadays because the part is commented out, however I looked at the timestamps of the patch and it doesn't seem to be the reason why the maintainer mode was triggered. I wonder what else could have triggered this.
Comment 11 Mart Raudsepp gentoo-dev 2009-09-19 15:06:01 UTC
We shouldn't be commenting out the chunk.
The patch tool guarantees (I'm 98% sure) us that all files in one patch file will have an equal timestamp after patching.
Comment 12 Martin Mokrejš 2010-01-01 19:33:37 UTC
Just saw it with x11-libs/pango-1.26.2.
Comment 13 Doktor Notor 2010-03-20 17:31:21 UTC
Still there with latest version in the tree.
Comment 14 Pacho Ramos gentoo-dev 2010-06-12 10:41:22 UTC
Will be solved with 1.28
Comment 15 Pacho Ramos gentoo-dev 2010-06-13 15:30:14 UTC
1.28.0 added