On 15 Jul 2013, at 10:04, Arran Cudbard-Bell <[email protected]> wrote:
> > On 15 Jul 2013, at 09:30, Stefan Winter <[email protected]> wrote: > >> Hi, >> >>> If you are planning on deploying 3.0 and have an existing 2.x.x >>> configuration you were planning to migrate when the 3.0 is released, now >>> would be a good time to try that, and to report any issues or problematic >>> behaviour changes you notice. >> >> The errors for people upgrading from 2.x are a bit cryptic. Of course >> reading README.rst will solve it, but the initial complaints when just >> starting with -X are: > > > Ah! CONF_PARSER structs also have a data pointer, as well as the offset! Joy. > I'll fix that. Ok, fix pushed. The deprecated items stuff is pretty dumb. If the current config item is deprecated, it just looks at the next in the CONFIG_PARSER struct and checks to see if the offset and now data pointers are the same, and if they are it prints our the 'Replace x with y' message. It will not, for example, tell you to move config items into new nested sections. Arran Cudbard-Bell <[email protected]> FreeRADIUS Development Team - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
