Opened 11 years ago
Last modified 11 years ago
#42055 new defect
freeradius @2.1.9_2 - Update overwrites all config files
Reported by: | srothe@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | Cc: | ||
Port: | freeradius |
Description
Hello,
a couple of days ago, there was again an update for freeradius. I installed it, but again all my config files were overwritten in /opt/local/etc/raddb with the default files.
I guess there is some kind of bug.
OSX 10.9.1
Thanks,
Change History (3)
comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | freeradius mavericks removed |
---|---|
Port: | freeradius added |
comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
comment:3 Changed 11 years ago by srothe@…
I have modified the following files:
/opt/local/etc/raddb/users /opt/local/etc/raddb/clients.conf /opt/local/etc/raddb/sites-available/default /opt/local/etc/raddb/sites-enabled/default
But I think if freeradius is already installed on the target machine, it should not overwrite any of these files in /opt/local/etc/raddb.
Note: See
TracTickets for help on using
tickets.
It's an undesired behavior to be sure, but it's not exactly a bug. We simply configure, build and install freeradius according to the rules that the freeradius developers have programmed into their build system. Those rules happen to install some files that users are intended to modify, which is a problem when MacPorts upgrades them next time and throws out your changes. /opt/local/etc/raddb contains a lot of files. Are they all configuration files? For each configuration file, we need to manually instruct MacPorts to handle that file differently and not throw it away on upgrades.