Bug 180798

Summary:	app-admin/gnome-system-tools-2.14.0 emerge fails
Product:	Gentoo Linux	Reporter:	Luís Costa <luisfcosta>
Component:	[OLD] GNOME	Assignee:	Gentoo Linux Gnome Desktop Team <gnome>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Luís Costa 2007-06-03 22:56:16 UTC

here is the log

>>> Emerging (1 of 2) app-admin/gnome-system-tools-2.14.0 to /
 * gnome-system-tools-2.14.0.tar.bz2 RMD160 ;-) ...                            [ ok ]
 * gnome-system-tools-2.14.0.tar.bz2 SHA1 ;-) ...                              [ ok ]
 * gnome-system-tools-2.14.0.tar.bz2 SHA256 ;-) ...                            [ ok ]
 * gnome-system-tools-2.14.0.tar.bz2 size ;-) ...                              [ ok ]
 * checking ebuild checksums ;-) ...                                           [ ok ]
 * checking auxfile checksums ;-) ...                                          [ ok ]
 * checking miscfile checksums ;-) ...                                         [ ok ]
 * checking gnome-system-tools-2.14.0.tar.bz2 ;-) ...                          [ ok ]
>>> Unpacking source...
>>> Unpacking gnome-system-tools-2.14.0.tar.bz2 to /var/tmp/portage/app-admin/gnome-system-tools-2.14.0/work
 * Fixing OMF Makefiles ...                                                    [ ok ]
 * Running elibtoolize in: gnome-system-tools-2.14.0
 *   Applying portage-1.5.10.patch ...
 *   Applying max_cmd_len-1.5.14.patch ...
 *   Applying sed-1.5.6.patch ...
 * Applying gnome-system-tools-2.14.0-as-needed.patch ...                      [ ok ]
 * Applying gnome-system-tools-2.14.0-ALL_LINGUAS.patch ...                    [ ok ]
 * Applying gnome-system-tools-2.14.0-doc.patch ...                            [ ok ]
 * Running eautoreconf in '/var/tmp/portage/app-admin/gnome-system-tools-2.14.0/work/gnome-system-tools-2.14.0' ...
 * Running aclocal ...                                                         [ ok ]
 * Running libtoolize --copy --force --automake ...                            [ ok ]
 * Running aclocal ...                                                         [ ok ]
 * Running autoconf ...                                                        [ !! ]
 
 * Failed Running autoconf !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/app-admin/gnome-system-tools-2.14.0/temp/autoconf-18822.out
 
 
!!! ERROR: app-admin/gnome-system-tools-2.14.0 failed.
Call stack:
  ebuild.sh, line 1615:   Called dyn_unpack
  ebuild.sh, line 752:   Called qa_call 'src_unpack'
  ebuild.sh, line 44:   Called src_unpack
  gnome-system-tools-2.14.0.ebuild, line 53:   Called eautoreconf
  autotools.eclass, line 95:   Called eautoconf
  autotools.eclass, line 165:   Called autotools_run_tool 'autoconf'
  autotools.eclass, line 218:   Called die
 
!!! Failed Running autoconf !
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/app-admin/gnome-system-tools-2.14.0/temp/build.log'.
 
-----
 
costa@quarK-g ~ $ cat /var/tmp/portage/app-admin/gnome-system-tools-2.14.0/temp/autoconf-18822.out
***** autoconf *****
 
configure.in:198: error: possibly undefined macro: AM_PATH_SYSTEM_TOOLS_BACKENDS
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.

Reproducible: Always

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2007-06-04 19:22:35 UTC

Re-emerge app-admin/system-tools-backends?

Comment 2 Luís Costa 2007-06-04 19:59:25 UTC

(In reply to comment #1)
> Re-emerge app-admin/system-tools-backends?
> 

Doesn't work :S It's strange because I had emerged the package when I istalled gentoo but then I removed it later on. when I tried to re-emerge the package I got this error

Comment 3 Daniel Gryniewicz (RETIRED) gentoo-dev

2007-06-04 21:41:27 UTC

I just tested, and it works fine here.  That macro is defined in /usr/share/aclocal/system-tools-backends.m4, which is installed by system-tools-backends.  Which version of system-tools-backends do you have?

Comment 4 Luís Costa 2007-06-04 22:35:29 UTC

(In reply to comment #3)
> I just tested, and it works fine here.  That macro is defined in
> /usr/share/aclocal/system-tools-backends.m4, which is installed by
> system-tools-backends.  Which version of system-tools-backends do you have?
> 

I did an emerge -c app-admin/system-tools-backends just in case a simple rebuild didn't work. I emerged it again and I still get the same problem with gnome-system-tools

My version of system backends is: app-admin/system-tools-backends-2.2.1 which is marked as stable.

I can live without gnome-system-tools but emerge --depclean gives me errors resolving dependencies because of it.

any ideas?

Comment 5 Luís Costa 2007-06-04 22:51:31 UTC

I think I know what's happening. I don't have any /usr/share/aclocal/system-tools-backends.m4 file. why is it not being created?

Comment 6 Gilles Dartiguelongue (RETIRED) gentoo-dev

2007-08-04 15:18:41 UTC

> My version of system backends is: app-admin/system-tools-backends-2.2.1 which is marked as stable.

this is only true with the sabayon overlay so marking as invalid. Please reopen if  you can actually reproduce with portage's versions.