" Full IPv6 support for all services (c2s, s2s, HTTP, etc.) Server-to-server authentication using certificates (SASL EXTERNAL) A new and improved HTTP subsystem, supporting virtual hosts and fully-reloadable modules Basic pubsub service Many other fixes and improvements, see our release notes for more information. " Published on 2013-05-13 by The Prosody Team Please add it to the tree
Full IPv6 support needs a patched dev-lua/luasocket. I tried to package it, but its build system is so horrible, I couldn't get it to work at all. Will try and find some time on the weekend.
"After a very successful beta, we decided it's time for a release candidate. We have made only a few small changes since beta1: With s2s_secure_auth enabled, we required encryption for domains listed in s2s_insecure_domains, even if s2s_require_encryption was not set. Some minor fixes to commands in the telnet console. Automatically disable SSL compression if luasec-prosody is installed. Fix a traceback in mod_bosh when used in combination with some plugins. Fix pubsub "get subscriptions" action. "
Not sure if you have seen it: https://github.com/diegonehab/luasocket 3.0_rc1 was tagged some hours ago, maybe this eases the packaging pain :) http://prosody.im/doc/depends/luasec/prosody I'm not sure how to deal with this. Should it be added as a seperate package or be seen as the "new" upstream for luasec?
I'd make it a use-switched dependency: if prosody is built with USE=ipv6, use the forked luasec library. Thus, the forked one would be a separate package that has is configured to conflict with the normal one. That way, users can choose whether they want to have a forked library or not. And in the case of the forked luasec not working with something else, they can choose whether they prefer it over having v6-support in Prosody. Luckily, Prosody degrades gracefully if you use the classic luasec.
rc3 released
Created attachment 354192 [details] prosody-0.9.0_rc3.ebuild Luasocket here: https://bugs.gentoo.org/show_bug.cgi?id=477344 Both in emery overlay.
I've used the two ebuilds to update my own installation. Will test drive it for a bit before adding the ebuilds to the tree.
Looks like all stuff from prosody-luasec was commited right here https://github.com/brunoos/luasec (original upstream) and we could add a luasec-0.5_pre to the tree?
0.9.0 release is out http://blog.prosody.im/prosody-0-9-0-released/
Any news on this one? Is help/testing needed?
*prosody-0.9.1 (15 Sep 2013) 15 Sep 2013; Tobias Klausmann <klausman@gentoo.org> +prosody-0.9.1.ebuild: Add new ebuild for version 0.9.1, provided by Emery Hemingway.
It appears that the 0.9.1 ebuild newly added to the tree incorrectly specifies a dependency on luasocket 3.0, which Prosody does not appear to support yet. Launching Prosody fails with "Prosody was unable to find luasocket" after upgrading. Copying prosody-0.9.1.ebuild to an overlay, changing the luasocket dependency to "=dev-lua/luasocket-2*" and re-emerging solves the issue.
(In reply to Jasper Bryant-Greene from comment #12) > It appears that the 0.9.1 ebuild newly added to the tree incorrectly > specifies a dependency on luasocket 3.0, which Prosody does not appear to > support yet. > > Launching Prosody fails with "Prosody was unable to find luasocket" after > upgrading. > > Copying prosody-0.9.1.ebuild to an overlay, changing the luasocket > dependency to "=dev-lua/luasocket-2*" and re-emerging solves the issue. I created bug https://bugs.gentoo.org/show_bug.cgi?id=485074 for that issue. Prosody 0.8* ebuilds seem to have had a workaround for the luasocket path. The 0.9.1 ebuild does not have that. Not sure if prosody or luasocket is wrong, but probably luasocket.
I was just told that luasocket 2 works with prosody 0.9.1, but for ipv6 support luasocket 3 is necessary.
I thought I'd used the same ebuild for luasocket as was in tree for my testing. Turns out I didn't. I'll mask prosody and figure out what from "my" luasocket ebuild to use with the luasocket maintainer.
I've attached a patch in bug 485074
After another small SNAFU regarding mutltilib, 0.9.0-r1 is in tree. It's been working just dandy for me. Closing. If you find any bugs, please open a new ticket. I'll also set a reminder for myself for stabilization in 30 days.
