Jabberd gets error with enewgroup

swarrenjr · n00b Joined: 31 Mar 2006 Posts: 2 Location: Iowa

I am not sure what is causing this. I have searched the forums and haven't come up with a solution. I am trying to emerge jabberd and always come up with the following error.

>>> Install jabberd-1.4.3-r5 into /var/tmp/portage/jabberd-1.4.3-r5/image/ category net-im
* '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-1.4.3-r5 failed.
!!! Function enewgroup, Line 648, Exitcode 0
!!! Bad package! enewgroup is only for use in pkg_* functions!
!!! If you need support, post the topmost build error, NOT this status message.

I am guessing this may be something simple I am overlooking. I ran the following commands:

emerge --sync
emerge portage
emerge -av mu-conference

The emerge for mu-conference starts off with jabberd first. I never get past that. Thanks for any help!
_________________
Sam Warren, Jr.

UncleOwen · Posted: Tue Apr 25, 2006 8:24 pm Post subject:

That's a bug in the ebuild. Report it at bugs.gentoo.org - but please make sure, that this wasn't reported before.

mariourk · Posted: Fri Apr 28, 2006 10:09 am Post subject:

Is there any solution for this? I'm getting the same error with both version 2.0.9 and 2.0.10.
I tried to uninstall jabberd 1.4 before installing 2.x but that didn't make any difference.
_________________
If there is one thing to learn from history, it's that we usualy don't learn anything from it, at all.

mariourk · Posted: Fri Apr 28, 2006 10:30 am Post subject:

I found a solution. The error was caused because the ebuild was trying to add the group and user 'jabber'.
But those allready existed from an old 1.4 install. So, I edited /usr/portage/net-im/jabberd/jabberd-2.0.10.ebuild

UncleOwen · Posted: Fri Apr 28, 2006 5:09 pm Post subject:

mariourk · Posted: Fri Apr 28, 2006 9:32 pm Post subject:

Ok, I filed it.
As far as I could see, it wasn't filed allready.

update:
Well, I'll be... I was filed allready after all... :oops:

_________________
If there is one thing to learn from history, it's that we usualy don't learn anything from it, at all.

swarrenjr · n00b Joined: 31 Mar 2006 Posts: 2 Location: Iowa

I looked at the bugs and it looked like it was already filed when I looked. Sorry if I should have done something and didn't. My work around was to go back to an older portage. I restored my server to before I updated Portage and I could do the e-merge without any problem. I guess you could also get an older portage snapshot from the Gentoo mirrors instead of doing a restore.
_________________
Sam Warren, Jr.