From owner-freebsd-ports@FreeBSD.ORG Sat Mar 5 16:12:47 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C60ED16A4CE for ; Sat, 5 Mar 2005 16:12:47 +0000 (GMT) Received: from hooters.chaossolutions.net (a.ns.chaossolutions.org [209.216.77.5]) by mx1.FreeBSD.org (Postfix) with SMTP id DE1DF43D3F for ; Sat, 5 Mar 2005 16:12:46 +0000 (GMT) (envelope-from marrandy@chaossolutions.org) Received: (qmail 10563 invoked from network); 5 Mar 2005 16:05:19 -0000 Received: from unknown (HELO ?192.168.1.1?) (209.216.76.1) by a.ns.chaossolutions.org with SMTP; 5 Mar 2005 16:05:19 -0000 From: marrandy To: Kris Kennaway Date: Sat, 5 Mar 2005 11:13:02 -0500 User-Agent: KMail/1.7.2 References: <200503042150.38465.marrandy@chaossolutions.org> <20050305151502.GB26240@hub.freebsd.org> In-Reply-To: <20050305151502.GB26240@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503051113.02507.marrandy@chaossolutions.org> cc: freebsd-ports@freebsd.org cc: autrijus@autrijus.org Subject: Re: marked as broken - P5-Log-Dispatch-2.10 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2005 16:12:47 -0000 On Saturday 05 March 2005 10:15, you wrote: > > Submit a patch with send-pr(1) that corrects the problem(s). > > Kris Hello Kris. Unfortunately, I'm not a programmer, haven't submitted patches before and really don't know what the message means or why it was added. I had already emailed the maintainer, autriju at autrijus.org, but he is probably busy, as we all are. Background - There is an issue with the current helpdesk/inventory software at work and I was hoping to offer Request Tracker (there is also Roundup, OTRS & Eventum) as a possible replacement, but the current 30-day timetable, after 3-days, has just changed to 10-days so I'm under the bullet to install and test a suitable alternative. The RT-3/3.2 port seemed the best way to get it installed, up and running and then there is data transfer from the other system, which is another matter. If the port is broken and not fixable in time, then my best option, at the moment, seems to be to build from source. It's unfortunate, as the port would have saved me a lot of time Thanks for the reply. Regards...Martin