On Thu, Jun 23, 2016 at 09:33:52AM -0400, Alan DeKok wrote:
This broke in
commit 0b2e4da0c574dedd9309c9dbbdf4f8cb9d869d27
The easiest fix is to change the default config to be "Reject" rather than "REJECT", but that will seemingly unnecessarily break configs when people upgrade from 3.0 so I'm not sure that's the best solution.
TBH, we could just revert that commit. I was making changes in v3.1.x branch before they became too invasive. I rolled back many of the changes, and went on to re-do them in a newly created v4.0.x branch.
If reverting that commit works, just go ahead and do it. At this point, I won't be touching v3.0.x or v3.1.x for anything other than bug fixes.
After a brief go at this it looks like it's a whole chunk of commits after that as well. I've got 20 or so at the moment but still not enough to revert cleanly. So it's probably pretty much roll back to before that commit and apply the few other things that are unrelated, or fix it another way. Which way would you prefer? I'm not familiar with that code so I can try and come up with another fix but it may take a while. Thanks, Matthew -- Matthew Newton, Ph.D. <mcn4@leicester.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>