I would like really like an ebuild for the latest versions of Privoxy and Bfilter. Thanks in advance! Reproducible: Always Steps to Reproduce: 1. 2. 3.
The privoxy version bump is bug #112290
Alan, could you please adapt your droppriv patch to bfilter-0.10.1?
Created attachment 72905 [details, diff] bfilter-0.10.1-droppriv.patch Updated droppriv patch for bfilter 0.10.1. Uses the same semantics as previous patch for bfilter 0.9.4. Tested for user/group only, chroot only and both user/group and chroot. (I did consider adding configuration file options too but I the C++ code is slightly tangled. Perhaps in the future when I do a bit more C++.)
Created attachment 72910 [details, diff] bfilter-0.10.1-ebuild.patch Patch to the bfilter-0.9.4.ebuild file to update it to bfilter-0.10.1.ebuild. However the build fails due to a SCons generated files not being created for some reason I cannot currently figure out. The ebuild fails on the (un)generated HtmlLexerCore.h file under main/htmllexer directory. Building by hand works perfectly of course. None of files generated by hand in the main/htmllexer directory are present in the ebuild. Sandboxing configuration issue perhaps? Missing RDEPEND? In other news BFilter now uses the ACE library and is now threaded instead of a forker. I did only test with unstable ACE 5.4.6 after I puked on the amount of rubbish such as Makefiles that the stable ACE 5.4-r2 installed. The man page needs updated for the filtering configuration changes and is commented out until I have time to update it.
version bumped. fixed compile error described in comment #4 by forcing make options to -j1. @Alan: open a bug when you have the new man page; please send your improvements (patch + man page) to upstream for inclusion in future versions.
Weired problem: # bfilter terminate called after throwing an instance of 'std::length_error' what(): basic_string::_S_create Aborted
I don't see the connection between your problem and this bug... Anyway, since it works for me with default configs, I guess you violated the syntax rules in your configuration files. Open a new bug with a proper subject and your configuration files attached to it (preferably a diff between the default and yours /etc/bfilter).
