Hi, I've uploaded the fix to this issue.
I also added the following collab-maint repository: http://anonscm.debian.org/gitweb/?p=collab-maint/vlogger.git;a=summary If you use vlogger this heavily, I urge you to create a vlogger fork on github or somewhere and make your fixes there. That way I won't be in the hotspot for reviewing and adding patches. Once you reached a version that you think should be released into debian, tag it as 1.4 (or something) and open a bug report on vlogger asking me to upgrade to that version. It's a lot easier to collaborate in git and apply patches quickly in a github repo than sending upstream patches to the BTS. This is also the only way to have these fixes move to Fedora, BSDs, etc. Sorry, but I currently can't volunteer to maintain vlogger and to continuously review major new patches and features. Either outside or inside Debian. Thanks, Gergely On Thu, 16 Jan 2014 12:10:20 +0100, Declercq Laurent <[email protected]> writes: > Hello ; > > First, sorry for my previous report.. It was too much sarcastic for > you as I see. > > Well, I can provide you a patch for all the bugs linked here. It's not > a problem for me since we are using our own vlogger version for our > control panel. Therefor, I would be happy to help as long you accept > those patches. > > I can also add some improvements. For the record, when using the DBI > tracker feature, Apache will fail miserably if the MySQL connnection > is failing for any reason. Well, in our version I've revisited that > part to make vlogger more safe. Eg, if the MySQL connection fail for > any reason, vlogger will simply turn off that feature and continue its > main job. Of course, an option should be added to let the admin decide > whether or not the script should follow such a behavior. > > Another thing is about how vlogger is reading traffic data from > mod_logio. A sample line should be added to warn the admin that the > logio variables should be added just after the %v variable. Or even > better, vlogger should simply search for those variables in the whole > logFormat string instead of just make assumption on their position... > > As you can see, I'm ready to help you because I support Debian like > you cannot ever imagine. The fact is that I suprised to see such bug > reported since a while, which is not fixed yet. Even if the upstream > author doesn't works much for a new release, it's not our problem. As > long the vlogger is part of the Debian repository, it should be > fixed. I know that you prefer warn the upstream author about such a > bug and wait for a new release but this do not work as you can see. > > Thank you. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
