Bug 132392

Summary:	jabberd-2.0.11 fails to emerge on ~arch systems
Product:	Gentoo Linux	Reporter:	Jason Wever (RETIRED) <weeve>
Component:	Current packages	Assignee:	Gustavo Felisberto (RETIRED) <humpback>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	sparc
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Jason Wever (RETIRED) gentoo-dev

2006-05-05 15:11:23 UTC

~arch keyworded systems running recent versions of portage will fail to be able to emerge jabberd-2.0.11 (and possibly other versions of jabberd) due to the enewgroup function being called in src_install.  Sample emerge failure looks like the following:

make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/var/tmp/portage/jabberd-2.0.11/work/jabberd-2.0s11'
make[1]: Leaving directory `/var/tmp/portage/jabberd-2.0.11/work/jabberd-2.0s11'
 * 'enewgroup()' called from 'install()' which is not a pkg_* function.
 * Package fails at QA and at life.  Please file a bug.

!!! ERROR: net-im/jabberd-2.0.11 failed.
Call stack:
  ebuild.sh, line 1525:   Called dyn_install
  ebuild.sh, line 1002:   Called src_install
  jabberd-2.0.11.ebuild, line 64:   Called enewgroup 'jabber'
  eutils.eclass, line 648:   Called die

!!! Bad package!  enewgroup is only for use in pkg_* functions!
!!! If you need support, post the topmost build error, and the call stack if relevant.

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2006-05-05 15:23:11 UTC

emerge --sync time ;)

*** This bug has been marked as a duplicate of 130849 ***