Date: Wed, 5 Feb 2014 11:40:08 GMT From: Tim Bishop <tim@bishnet.net> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/186479: irc/anope: port doesn't work Message-ID: <201402051140.s15Be8b5077734@oldred.freebsd.org> Resent-Message-ID: <201402051150.s15Bo14I071041@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 186479
>Category: ports
>Synopsis: irc/anope: port doesn't work
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Feb 05 11:50:01 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Tim Bishop
>Release: 10.0 amd64
>Organization:
>Environment:
FreeBSD myhost 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
This port appears to have numerous issues. I've done my best to summarise them here.
1. It has the following configure flag: --with-rungroup=ircdru
The port does not create this group so the application will not start.
Looking at the Subversion history and related PR, I can't see any
reason why this was added. I'd guess it's for someone's rather
specific setup.
2. It fails on FreeBSD 10 with errors like this:
/usr/local/share/anope/modules/runtime/inspircd20.so.3Tbklm: Undefined symbol "del_exception"
I'm expecting this is a compiler issue, although I've not
investigated. It works on FreeBSD 9. (both amd64)
3. It installs its runtime data in ${DATADIR}.
It then expects to be able to write here at runtime, which it may be
able to if it's running as root, but it should probably be under /var
somewhere instead.
It also logs to it's current working directory, so the RC script would
need to chdir here before running.
4. The RC script suggests setting the following:
anope_user="nobody"
anope_chroot="/usr/local/share/anope"
The first won't work because the files (see 3) are owned by root. The
second doesn't work because ${command} then no longer points at the
binary.
>How-To-Repeat:
>Fix:
1. This can be fixed by just removing the configure flag.
2. I'm not sure about this one, sorry. Maybe setting USE_GCC would do it, but someone with more of an insight in this area might be able to fix it.
3 and 4. These could possibly be resolved by modifing the RC script:
- The port can't install its data directly to /var, but the RC script
could copy the tree there on first run if it doesn't exist, and then
chown it to ${anope_user}.
- The RC script can set ${anope_chdir} to the directory under /var,
and also set ${command_args} to "-dir /var/whatever".
I've not tested this thoroughly or produced a patch, sorry. But it
works in principal.
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402051140.s15Be8b5077734>