First of all, thanks for fix bug #551050 ☺ But when today I've tried to switch =net-p2p/i2p-0.9.22 from local overlay to gentoo I've find 0.9.22 version ebuild unstartable. So, probably it should be removed. The next version I try was =net-p2p/i2p-0.9.22-r1. It started, that's already good. But with this vesion I've failed to open any external resource (for example http://pastethis.i2p/ ). The messages log showed the following error: Oct 23 20:54:32 tux i2p[7071]: Unable to write to the configured log file: /var/lib/i2p/.i2p/wrapper.log (Нет такого файла или каталога) Oct 23 20:54:32 tux i2p[7071]: Unable to write to the default log file: wrapper.log (Отказано в доступе) Copying ebuild back to local overlay and re-emergeing it with my updated init script made it not only startable, but operable. # diff -Naur /usr/portage/gentoo/net-p2p/i2p/files/i2p.initd /usr/portage/local/net-p2p/i2p/files/i2p.initd --- /usr/portage/gentoo/net-p2p/i2p/files/i2p.initd 2015-08-09 23:34:53.000000000 +0300 +++ /usr/portage/local/net-p2p/i2p/files/i2p.initd 2015-06-06 13:53:57.000000000 +0300 @@ -1,18 +1,17 @@ #!/sbin/runscript -# Copyright 1999-2013 Gentoo Foundation +# Copyright 1999-2015 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 -# $Id$ +# $Header: /var/cvsroot/gentoo-x86/net-p2p/i2p/files/i2p.initd,v 1.1 2015/05/22 05:44:58 zlg Exp $ depend() { need net } HOME="/var/lib/i2p" -USER_HOME="$HOME" JAVABINARY="/etc/java-config-2/current-system-vm/bin/java" INSTALL_PATH="/usr/share/i2p" I2P="$INSTALL_PATH" -I2P_CONFIG_DIR="$USER_HOME/.i2p" +I2P_CONFIG_DIR="/var/cache/i2p" SYSTEM_java_io_tmpdir="$I2P_CONFIG_DIR" I2PTEMP="$SYSTEM_java_io_tmpdir" LOGFILE="$I2P_CONFIG_DIR/wrapper.log" P.S. Probably, similiar issue present in systemd unit.
stanley - Security Padawan Could you testrun the ebuild of 0.9.22 version, On proving borken, I suggest you request to purge it and the i2p-0.9.18.ebuild, then I suggest considering down the track requesting stabilisation of net-p2p/i2p-0.9.22-r1. Once this bug is resolved ofcourse.
i2p-0.9.18.ebuild will soon be removed since it is relying on a very very old version of jakarta-jstl (certainly unsecured by now) that is slated for removal (as well as the ebuild). It is one of the reason I personally version bumped i2p myself instead of waiting for the maintainer's approval.
I'm not sure what is causing this error but from what I gather, it's not coming from the new dependency. dev-java/jakarta-jstl being removed, the new dependencies are now dev-java/tomcat-jstl-{impl,spec}. Truth to be told, I'm not particularly into using i2p so you'd have to wait until Sergey looks through the problem. Sorry.
There is a new ebuild out, in which I didn't actively fix your issue (because I was unable to reproduce it), but it is hopefully working now, please get back to me if it okay now. In general, if you have issues, try removing the i2p config in /var/lib/i2p/.i2p, then re-emerge the package.
As per previous comment, test the new version and report back if necessary. Thank you.