CFT: net/freeradius2 upgrade to 2.0.5 (was FreeBSD Port: freeradius-mysql-1.1.7_3)

[David Wood]

(please skip down to the line of **** if you just want the Call for 
Testers)

Hi Scott, Giovanni and all,

In message <20080626233338.GA36931 at sysmon.tcworks.net>, Scott Lambert 
<lambert at lambertfam.org> writes
>On Thu, Jun 26, 2008 at 11:25:48PM +0200, Giovanni Venturi wrote:
>> Hello,
>> what is the difference between freeradius-mysql-1.1.7_3 and
>> freeradius-2.0.3_1 ? In this last one is MySQL support disabled?
>>
>> Has been released Free Radius 2.0.5 on  the 7th June. You could update the
>> port :) . Thank you from now for your reply.

I started work on 2.0.5 immediately it was released, as did mm at .


>Do not use the freeradius 1.x stuff, especially if this is a new
>installation.  2.x is much better.

I agree - FreeRADIUS 1.x is deprecated and is already far behind 2.x. 
All new deployments should be 2.x now.


Once I've got 2.0.5 sorted, I intend to ask for a repocopy of 
net/freeradius to net/freeradius1 as part of my ongoing plan to 
deprecate the 1.x port. The FreeRADIUS 2.x port has a higher footprint 
than 1.x because of its current unconditional dependency on python which 
matters for embedded users.

I believe bsd.options.mk is now available for use following the EoL of 
FreeBSD 5.x, 6.1 and 6.2. That being the case, I can use bsd.options.mk 
to create a PYTHON option without the ugly hack in the FreeRADIUS 1.x 
port.


>The freeradius2 port gives you the
>option of adding whatever database support you desire.

Indeed. The freeradius-mysql port is simply freeradius with the MYSQL 
option forced on. It exists to ensure that a FreeRADIUS 1.x package with 
MySQL support is available on the FreeBSD FTP servers. This is required 
for some work that's being done on the pfSense firewall.


>Check the mailing list archives from the past week or so for why the
>freeradius2 port has not yet been updated.

As Scott later said, the thread was over at freeradius-users.

PR ports/124439 is where we're up to on updating the port to 2.0.5 - 
that's
http://www.freebsd.org/cgi/query-pr.cgi?pr=124439


I believe the port is now correct - though I'm waiting on word from mm@ 
about testing it (I've copied him into this reply). I want to revisit 
the new pkg-message, also I need to write an entry for UPDATING - I'm 
hoping to have this done within the next 48 hours. It will be later 
today if I can get through some other tasks.

I'm very conscious of the need not to trash people's configurations when 
they upgrade, which is why we're taking our time over this upgrade. I 
hadn't anticipated the reorganisation of the raddb configuration folder 
in 2.0.5, though I do support it. Without changing the behaviour of the 
port, we'd finish up with those upgrading from an older versions having 
two copies of the configuration for each module, with only one linked in 
to their live configuration. That's a recipe for disaster.


The pre-release 2.0.5 port has some new features that means that it's 
much easier to get FreeRADIUS going 'out of the box' - you get a 
pkg-message that walks you through what needs to be done. Please try the 
pre-release port - I'd be glad to receive your feedback.


****************************************************************

I open this to all FreeRADIUS users - please try the pre-release 2.0.5 
port.

Those updating from 1.x should read the UPDATING message of 20080118. I 
do encourage all FreeRADIUS users to upgrade now - the FreeRADIUS 
developers have indicated that there will be no further development of 
1.x. Amongst many things, 2.x has many bug fixes that are not feasible 
in the 1.x code base.

Everyone who is upgrading should make sure you take a backup of your 
configuration *before* uninstalling your existing FreeRADIUS port. 
Reading PR ports/124439 is recommended.


My message on freeradius-users
http://www.nabble.com/Re%3A-Dependencies-of-Freeradius-2.0.5-p18040698.ht
ml
will walk you through creating a patched copy of the port and installing 
FreeRADIUS 2 from it.

Those who are upgrading will need to uninstall your existing port before 
the final 'make install' step - if you want to keep the downtime to a 
minimum, 'make build', uninstall your existing port, then 'make 
install'. Don't forget to '/usr/local/etc/rc.d/radiusd start' after the 
upgrade.


I do not anticipate any further changes in the code, though I am going 
to tidy the pkg-message a little and write an UPDATING entry.

I will keep the patch mentioned in the PR updated, so you'll get 
wherever I'm up to at the time. It would help if any comments gave the 
'revision' number in the third line of the patch file; I can relate that 
back to the Subversion repository in which I develop these ports. The 
current revision is 202.


Comments on the new pkg-message and bootstrap behaviour are especially 
welcomed.


Best wishes,




David
(maintainer of net/freeradius2)
-- 
David Wood
david at wood2.org.uk