Re: inn-2.4.3 - need comments and testing

2008-08-02 Thread Toni Mueller
Hi, [ same procedure as every year... ;-} ] On Thu, 19.07.2007 at 23:54:18 -0500, Gilles Chehade [EMAIL PROTECTED] wrote: http://www.evilkittens.org/~veins/inn.tgz unfortunately, this domain currently does not have any name service, despite still being registered. In the meantime, and

Re: inn-2.4.3 - need comments and testing

2007-07-23 Thread Gilles Chehade
On Fri, Jul 20, 2007 at 04:25:14PM -0500, Deanna Phillips wrote: That should read something like: have a look at the other INN ports from me and Toni Mueller including the patches floating around the archives. I found it.. it's out of date but might help as a reference. This is the

inn-2.4.3 - need comments and testing

2007-07-20 Thread Gilles Chehade
Hi ports@, I'm almost done with the inn port except that: 1- even though the PLIST starts with @newuser, the user does not get created and I am forced to create it manually. Anyone can explain what I do wrong ? 2- this one being my first port, I probably did some thing(s) wrong,

Re: inn-2.4.3 - need comments and testing

2007-07-20 Thread Matthias Kilian
On Thu, Jul 19, 2007 at 11:54:18PM -0500, Gilles Chehade wrote: 1- even though the PLIST starts with @newuser, the user does not get created and I am forced to create it manually. Anyone can explain what I do wrong ? You mean during fake stage? Well, the user is created add install

Re: inn-2.4.3 - need comments and testing

2007-07-20 Thread Gilles Chehade
On Fri, Jul 20, 2007 at 06:01:42PM +0200, Matthias Kilian wrote: On Thu, Jul 19, 2007 at 11:54:18PM -0500, Gilles Chehade wrote: 1- even though the PLIST starts with @newuser, the user does not get created and I am forced to create it manually. Anyone can explain what I do wrong ?

Re: inn-2.4.3 - need comments and testing

2007-07-20 Thread Matthias Kilian
On Fri, Jul 20, 2007 at 05:25:27AM -0500, Gilles Chehade wrote: ksh: }fmt: not found floating around the archives), especially on patch-support_install-sh. Unfortunately, Deannas port seems to be unavailable. I don't get that :-) Argh! I garbled my own mail. Sorry. That should read