Perhaps I wasn't clear. Syslog-ng is at version 4.10; the entware version of it is at 4.7. The @version switch in syslog-ng controls what level features are enabled. If you set the @version to 3.5, features introduced in later versions would not be enabled. But, if the installed version is newer than the @version switch, syslog-ng throws an alert when it starts. To stifle the alert, @cmkelley stuck in some code that updated the @version switch to whatever the installed version of syslog-ng is.
The scribe code now doesn't test what level of syslog-ng is installed, it tests whether the fifo size/message size parameters have been updated (I think), which I think is just a scribe thing (and a good change), and if so (unnecessarily, confusingly) changes the @version switch from 4.7 to 4.7. There isn't any need to change the scribe version.
I don't quite agree with @cmkelley's solution, as I think it should be an option along the lines of updating the filters.
But yes, I get that syslog-ng is one project for the linuxsphere, and scribe is handled for our routers, brilliantly, by another developer.
