For the two months hotwayd 0.7.1 is in portage there were no bugs reported. I 'd like to see it marked stable in portage because I need the proxy support and don't like to explicitly skip it when I update. Reproducible: Always Steps to Reproduce:
Hotwayd has been updated to version 0.7.3, after the hotwayd team fixed a couple minor bugs on the past two days. Renaming the current 0.7.1 ebuild works without a problem, so I'd also like to suggest a version bump.
I have also found a new dependency in the old version of net-mail/hotwayd-0.5.3 ebuild and libxml2. With the upgrade to the latest dev-libs/libxml2-2.6.3 ebuild, an upgrade is required to hotwayd-0.7.1 or later. This can be confirmed by reading the FAQ on the hotwayd homepage http://hotwayd.sourceforge.net/faq/#libxml2_incompat Using libxml2-2.6.3 and hotwayd-0.5.3 will produce an error when checking my mail.
Changed Severity because of the above. Upgrading solves it.
As mentioned on the hotwayd mailing list: The current xinetd.conf contains a bug; it has a line: server_args = -s This causes new hotwayd version to fail (old version do _not_ use commandline arguments and will ignore this argument). New versions (as of the 0.7 series) do accept commandline arguments (and do not accept -s). I is best to include an example of the new possible arguments (to enable a proxy): #server_args= -p http:proxy:8080 -u proxy_user -q proxy_password
That new example line should be #server_args= -p http://proxy:8080 -u proxy_user -q proxy_password Do not forget the http://
Just to keep track of things, hotwayd is now in its 0.7.4 version. Same ebuild still works.
Here's a "works for me" using the files attached to bug 39441 which build 0.7.4. (bug 39441 seems like it could be marked as a duplicate of this one)
hotwayd-0.7.4 is stable in portage. Closing...
