Need 2.2.2 [was: FR 2.2.1 issue]
jdennis at redhat.com
Fri Sep 20 17:21:08 CEST 2013
On 09/20/2013 05:12 AM, Arran Cudbard-Bell wrote:
>> It seems to still work as intended, but I might have missed something...
> It appeared to be dropping through multiple case statements.
> This highlights why it's important for people to actually test
> pre-release versions when the announcements go out.
This is a serious bug.
One can always apply a patch to 2.2.1 but then it always becomes an
ambiguous question, are you running the broken 2.2.1 or the patched
2.2.1? That makes version information very difficult to manage and
confuses people who want to download and build 2.2.1, they'll have to
know they have to patch it before building and then track the patch
The best solution is to spin a new release with the fix and bump the
version. Yeah that kinda sucks but there really isn't a better solution
when problems like this come up. 
 In the dim past a similar situation arose and the tarball was
regenerated under the same name, that created it's own set of problems.
More information about the Freeradius-Devel