On 24/02/17 19:01, Nish Aravamudan wrote: > On 24.02.2017 [18:37:41 +0100], Daniel Pocock wrote: >> >> Hi Nishanth, >> >> Thanks for the patch, is the fix for this bug[1] submitted upstream >> and/or already fixed in another way in newer upstream releases? > > It looks to be fixed (at least my patches bits): > > https://github.com/rsyslog/loganalyzer/commit/058de0cdc8f3490a8481918bb9c46432d501cbab > > https://github.com/rsyslog/loganalyzer/commit/6a917a62f8dba241164a4ee40d74563c0377c9be > > And there are subsequent changes since then to fix more PHP7 > compatibility. > >> If so, maybe we should update the version of loganalyzer in Debian/Ubuntu > > Agreed, I wonder if we should bump all the way up to 4.1.5? 3.6.6 is > rather old at this point (2014). >
Thanks for looking into it. Would you like to check with the release managers to see if they will accept this version jump during the freeze? They might ask for a debdiff, but maybe it is still early enough in the freeze that it can just be uploaded Regards, Daniel
