Bug#760754: Debian freeradius consider all files in modules/ folder, also *.dpkg-* ones...
I'd recommend holding on on fixing this bug until we get freeradius 3 into the archive. We'll still have some sort of problem for policy.d. It may be worth bringing this up on the upstream development list. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760754: Debian freeradius consider all files in modules/ folder, also *.dpkg-* ones...
> I think, as other debian package, only files with a specific extension
> have to be read (*.conf?)
That sounds like a big diversion from upstream, since none of the
current files in that directory contain an extension. The result of this
could be that the various tutorials/howtos on the web can't be applied
to Debian any more.
FreeRADIUS 3 (not in Debian) uses a folder mods-enabled, similar to
sites-enabled. I guess this is the cleanest solution, but backporting it
to v2.x will result in different problems.
> or at least that sources of trouble have to be added to debian
> documentation (README.Debian and something like that).
That sounds less intrusive. Maybe another option is to warn in the logs,
or even fail to start, if a file with a name matching
.{dpkg,ucf}-{dist,new} is encountered (I've got no idea what the
preferred option here should be).
--
Herwin Weststrate
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760754: Debian freeradius consider all files in modules/ folder, also *.dpkg-* ones...
Package: freeradius Version: 2.1.12+dfsg-1.2 I've just upgrade from squeeze to wheezy, and after upgrading freeradius the service does not start. After fiddling a bit with log and '-X' mode, i've found the culprit: the upgrade process create two *.dpkg-dist files on modules/ subfolder, file that i've modify to suit my needs. But the daemon read *all* the file in modules/ dir, also the *.dpkg-* ones, and this clearly can be a bit confusing for freeradius (specifically: there was an ldap file and a ldap.dkpg-dist with wrong parameters). I think, as other debian package, only files with a specific extension have to be read (*.conf?), or at least that sources of trouble have to be added to debian documentation (README.Debian and something like that). Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
