If you're running Prosody in a jail and experience problems, please add
the following to the global section of your prosody.cfg.lua:
interfaces = { 'x.x.x.x' }
where 'x.x.x.x' is the public IP you wish Prosody to bind to.
Shown after upgrading
Prosody 13.0 will function correctly on any config file that is compatible
with 0.12. No changes are required, however there may be some recommendations.
The best way to find these is to run:
prosodyctl check config
If you are upgrading from an earlier release and you use PostgreSQL or SQLite
for storage, Prosody may refuse to initialize storage until you complete a
schema upgrade. To check for any necessary schema upgrades and apply them, run:
prosodyctl mod_storage_sql upgrade
For more detailed information check the release notes at:
https://prosody.im/doc/release/13.0.0
Shown after removing
===> post-deinstallation information for prosody:"
Note:
Prosody related user accounts and groups were not removed.
To remove the user and group which were created by
the installation of this package, run:
pw userdel -n prosody
pw groupdel -n prosody
and to remove all server data:
rm -rf /var/db/prosody"
rm -rf /var/run/prosody"
Packages by version and architecture
latest
FreeBSD version
amd64
aarch64
i386
FreeBSD 16
13.0.7
13.0.7
–
FreeBSD 15
13.0.7
13.0.7
–
FreeBSD 14
13.0.7
13.0.7
13.0.7
quarterly (2026Q4)
FreeBSD version
amd64
aarch64
i386
FreeBSD 15
13.0.7
13.0.7
–
FreeBSD 14
13.0.7
13.0.7
13.0.7
version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.
Unaddressed and VuXML only (0)
No unaddressed CVE and nothing reported by pkg audit for the packaged version 13.0.7.
Fixed (6)
Show 6 fixed
VuXML entries whose affected range the packaged version has left.
Problem reports (0) · open in Bugzilla, most recently changed first
None.
Commits (107)
Gerald Pfeifer (gerald) · 0.11.2_2
Bump PORTREVISION for ports depending on the canonical version of GCC as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3 to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
- Switch textproc/luaexpat to default version of lua - Introduce textproc/luaexpat-51 that uses lua 5.1 - Use textproc/luaexpat-51 in net-im/prosody
This fixes the build of multimedia/libquvi-scripts09 (60 ports skipped,
including gnome3)
With hat: portmgr
net-im/prosody: Document SSL requirement and rework port makefile
This makefile had both <pre> and <options> but only the <options>
include was necesssary so the <pre> and <post> includes were remoed.
Most of the variables conventionally introduced before the <options>
include were wrapped and moved up to ensure they were defined when
needed. Finally SSL flags were added to support non-base SSL linkage.
Approved by: SSL blanket + general blankets
Improve shebangfix framework
- Support multiple values in *_OLD_CMD, i.e. we can now fix both "/usr/bin/python" and "/usr/bin/env python" at the same time
- Default *_OLD_CMD values are now always appended, so you don't need to specify them in individual ports
- Add lua support (depends on USES=lua)
- Add more default values, such as "/usr/bin/env foo" for python, perl, bash, ruby and lua
- Shebangfix now matches whole words, e.g. we will no longer (erroneously) replace "/usr/bin/perl5.005" with "${perl_CMD}5.005" (but "/usr/bin/perl -tt" is still (correctly) replaced with "${perl_CMD} -tt")
Note that *_OLD_CMD items containing spaces must now be quoted (e.g. perl_OLD_CMD=/bin/perl /usr/bin/perl "/usr/bin/env perl")
Update shebangfix usage according to new rules in many ports:
- Remove *_OLD_CMD for patterns now replaced by default
- Quote custom *_OLD_CMD which contain spaces
Fix shebangfix usage in many ports (irrelevant to infrastructure change):
- Remove redundant SHEBANG_LANG (no need to duplicate default langs)
- Remove redundant *_CMD (such as python_CMD=${LOCALBASE}/bin/python${PYTHON_VER} when USES=python is present)
- Never use *_OLD_CMD in REINPLACE_CMD matchers, these should always look for exact string
Approved by: portmgr (bapt)
Differential Revision: D3756
Retire MANCOMPRESSED.
Also the compat NO_INSTALL_MANPAGES shim.
Differential Revision: https://reviews.freebsd.org/D730
Reviewed by: antoine
With hat: portmgr
Sponsored by: Absolight
dns/libidn: - Add USES=libtool and bump dependent ports - Add INSTALL_TARGET=install-strip - Always install libidn-components.png because it is used by libidn.info - Add -lintl to Libs.private instead of Libs in libidn.pc
Remove indefinite articles and trailing periods from COMMENT, plus minor COMMENT typos and surrounding whitespace fixes. A few Makefiles where not included as they contain Latin-1 characters that break the Phabricator workflow. Category N.
CR: D307
Approved by: portmgr (bapt)
Replace lang/lua with the new lang/lua51
lang/lua51 is working the same way lang/lua52, chase ports using lua 5.1
Make the default lua lua52
Make all lua ports using USES=lua
Approved by: portmgr (implicit)
In the rc.d scripts, change assignments to rcvar to use the literal name_enable wherever possible, and ${name}_enable when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
Update to 0.8.2, a bugfix release. Also, update certificate makefile to specify "gmake", and regenerate localhost certs before install, in case someone carelessly uses them in production.
Update to prosody 0.7.0, take maintainership and fix some PREFIX-related stuff. Note that configuration file options and format have changed; however, existing configs should work correctly.
Approved by: kelly.hays@jkhfamily.org (maintainer)