Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 May 2010 08:27:45 +0200
From:      Stefan Bethke <stb@lassitu.de>
To:        freebsd-ports@freebsd.org, netatalk-admins <netatalk-admins@lists.sourceforge.net>
Subject:   Re: RFT: netatalk-2.1
Message-ID:  <F68B0724-483B-4310-81A6-B6FABE782DBB@lassitu.de>
In-Reply-To: <EA9DEC75-E453-41A0-B0B2-C0512E4F1E69@lassitu.de>

index | next in thread | previous in thread | raw e-mail

Am 22.05.2010 um 19:08 schrieb Stefan Bethke:

> Hi,
> 
> I'm working on updating the net/netatalk port from 2.0.5 to 2.1.  You can find the most current version of my work at http://www.lassitu.de/freebsd/netatalk/
> 
> Initial testing looks promising.  There's one outstanding issue: upgrading from 2.0.5 to 2.1 appears to fail because of the wrong order of include paths.  You can work around this by deinstalling 2.0.5 before building the new version.
> 
> This work is also being tracked in PR#146576.

I've uploaded new version which I believe to be committable: http://www.lassitu.de/freebsd/netatalk/netatalk_2.1.1-1.tar.bz2

I have not tested Kerberos support since I'm lacking the environment.

If your system has IPv6 configured, you will need to configure a server each for IPv4 and IPv6.  Note that both afpd and cnid_metad will by default bind to IPv6 addresses.


Thanks,
Stefan

-- 
Stefan Bethke <stb@lassitu.de>   Fon +49 151 14070811





home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F68B0724-483B-4310-81A6-B6FABE782DBB>