Bug 62516 - hostsenty port is unusable as packaged
Summary: hostsenty port is unusable as packaged
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-08 07:50 UTC by Dan Mahoney
Modified: 2004-07-06 14:54 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Mahoney 2004-02-08 07:50:11 UTC
The ports/security/hostsentry port is a port that is supposed to be able to monitor for a user's suspicious activity, however, 
it requires the python syslog modules, and python dbm and/or gdbm modules.  Presently, this module will fail to build under 
any FreeBSD python ports (or if attempting to build python from scratch).

Also of note is that the port installs to /usr/local/abacus rather than to /usr/local/etc as is the BSD standard.

Fix: 

An add-on for the python port to make this port add the correct module could fix this.  Additionally, requiring the py23-gdbm 
port should be helpful as well.  This port is FAR from ready for prime time, which is a shame, as it's potentially VERY 
useful.
How-To-Repeat: 
Install the hostsentry port and try to configure it.
Comment 1 Kris Kennaway 2004-03-06 13:43:49 UTC
On Sun, Feb 08, 2004 at 02:54:54AM -0500, Dan Mahoney wrote:

> The ports/security/hostsentry port is a port that is supposed to be able to monitor for a user's suspicious activity, however, 
> it requires the python syslog modules, and python dbm and/or gdbm modules.  Presently, this module will fail to build under 
> any FreeBSD python ports (or if attempting to build python from scratch).
> 
> Also of note is that the port installs to /usr/local/abacus rather than to /usr/local/etc as is the BSD standard.

This port is unmaintained and should be removed if no-one can come
forward to address this.  Thanks for bringing it up.

Kris
Comment 2 Volker Stolz freebsd_committer freebsd_triage 2004-03-14 21:14:09 UTC
State Changed
From-To: open->analyzed

kris iniated the de-orbit burn; unless somebody steps 
forward to fix the port it will be deleted.
Comment 3 Pav Lucistnik freebsd_committer freebsd_triage 2004-07-06 14:54:11 UTC
State Changed
From-To: analyzed->closed

Port was fixed today, thanks to Michael Ranner. Check 
http://www.freebsd.org/cgi/query-pr.cgi?q=68642 for details.