I actually did this again on an identical machine, making sure to create
the sites-enabled directory correctly with symlinks to sites-available,
and the directory still got removed on dist-upgrade from stretch to
buster...
So I think that is a bug. This directory should not get removed - it
breaks freeradius.
-Josiah
On 6/7/22 3:12 PM, Wm. Josiah Erikson wrote:
As the subject line says, on my machine,
/etc/freeradius/3.0/sites-enabled directory was removed entirely for
me after upgrade from stretch to buster.
I believe this was because I had failed to use symlinks in there -
they were actual separate files, which was not as designed... but
probably just removing the directory as a result is poor behavior.
I re-added the directory, restored the files that had been in
sites-enabled to sites-available instead, made symlinks in
sites-enabled, and things appear to be working.
Merely mentioning it here because if the original reporter of this bug
did the same thing as me, it could explain the behavior, and also that
script might want to be changed to not do what it did to me... or
perhaps users could just not be as boneheaded as me :)
--
Wm. Josiah Erikson
Associate Director of IT, Infrastructure and Web Applications Groups
Network Engineer
System Administrator, HPC and CS
Staff Trustee
Hampshire College
Amherst, MA 01002
(413) 559-6091
pronouns: he/him/his
