prosody
Prosody is a flexible communications server for Jabber/XMPP written in Lua. It aims to be easy to use, and light on resources. For developers it aims to be easy to extend and give a flexible
system on which to rapidly develop added functionality, or prototype new protocols.
- Devel package for openSUSE:Factory
-
3
derived packages
- Links to openSUSE:Factory / prosody
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:languages:lua/prosody && cd $_ - Create Badge
Refresh
Refresh
Source Files (show merged sources derived from linked package)
| Filename | Size | Changed |
|---|---|---|
| _link | 0000000124 124 Bytes | |
| prosody-0.12.4.tar.gz | 0000616043 602 KB | |
| prosody-0.12.4.tar.gz.asc | 0000000833 833 Bytes | |
| prosody-cfg.patch | 0000000997 997 Bytes | |
| prosody-configure.patch | 0000000702 702 Bytes | |
| prosody-lua54coexist.patch | 0000000706 706 Bytes | |
| prosody.changes | 0000050892 49.7 KB | |
| prosody.keyring | 0000030936 30.2 KB | |
| prosody.service | 0000000644 644 Bytes | |
| prosody.spec | 0000004420 4.32 KB | |
| prosody.tmpfile | 0000000074 74 Bytes |
Comments 9
Is there a reason why the prosody package still uses lua 5.1 rather than one of the newer versions?
I just noticed that prosody these days warns about 5.1 on startup:
Lua 5.1 has several issues and support is being phased out, consider upgradingAnd their web page says that the 0.12 series of releases will be the last to support for 5.1:
https://prosody.im/doc/release/0.12.0#lua-version-support
Reason was that it was 5.1 before and I didn't have enough time to test it with 5.3. So I left it as long as they support it. When I talked with upstream they even mentioned that at that point 5.1 might work better. This might have changed by now and we can upgrade to 5.3
FYI, I just created a branch of prosody for Lua 5.4 and so far it runs fine on my server. In that branch I also removed the pre-created certificates from the package, because I think it is bad security practice and I've had cases where prosody picked up these shipped certificates instead of the ones I had configured on my server.
If I don't find any issues with this on my own server I'll submit it in a few days.
https://build.opensuse.org/project/show/home:rmax:branches:devel:languages:lua
Great! If you want you can also send a maintainer request. I have used Prosody for a couple of years but have then switched to ejabberd. It would be great to have an an (additional) maintainer that uses Prosody actively!
I've sent the SRs for prosody and the modules package. Feel free to check the "add as a maintainer" box when accepting the submissions if you want to have me as an additional maintainer, but be warned that I know virtually nothing about lua.
BTW, do you think it would make sense to move prosody (and for that matter ejabberd as well) from their respective devel:languages project to server:messaging where jabberd lives as well? I think devel:languages is mainly meant for the cores, libraries and toools around those languages, but shouldn't contain applications that just happen to be implemented in a particular language.
Yes good point. prosody was here when I joined so I never changed that. In the meantime I created
network:messaging:xmppthough. For all kinds of xmpp libraries and clients and servers. I also pinged maintainers of other xmpp software to move it there but noone did so far (gajim, and another client which i forgot..).SR accepted. And added you as maintainer as well :)
Cannot install this version of prosody on OpenSuse 15.5. Reason is that RPM prosody-0.12.4-lp155.88.1.x86_64 depends on 'lua54-luaexpat', but 'lua54-luaexpat' is not avail in devel:languages:lua; only lua51-luaexpat is avail here, and lua53-luaexpat in repo Leap 15.5.
Sorry, I initially misread your comment.
lua54-luaexpatdoes not build on 15.5, because it requires a newer expat version than what is available there.But it looks like the luaexpat package takes this version dependency stricter than it would be needed:
https://github.com/lunarmodules/luaexpat/releases/tag/1.5.0
So, assuming that we have fixed these CVEs in 2.4.4 for 15.5 as well it should be possible to loosen that dependency to
libexpat-devel >= 2.4.0.