On 2023/09/06 18:33:43 +0200, Solène Rapenne <[email protected]> wrote:
> Le mercredi 06 septembre 2023 à 15:04 +0000, Lucas a écrit :
> > Hi ports,
> > 
> > Update for Prosody 0.12.4, fresh out of the oven. Maintainance
> > release,
> > with bugfixes small improvements. Changelog:
> > 
> >  - core.certmanager: Update Mozilla TLS config to version 5.7
> >  - util.error: Fix error on conversion of invalid error stanza
> >  - util.array: Fix new() library function
> >  - util.array: Expose new() on module table
> >  - prosodyctl: Fix output of error messages containing '%'
> >  - util.prosodyctl.check: Correct suggested replacement for
> >    'disallow_s2s'
> >  - util.prosodyctl.check: Allow same config syntax variants as in
> >    Prosody for some options
> >  - util.prosodyctl.check: Fix error where hostname can't be turned
> > into
> >    A label
> >  - util.prosodyctl.check: Hint about the 'external_addresses' config
> >    option
> >  - util.prosodyctl.check: Suggest 'http_cors_override' instead of
> > older
> >    CORS settings
> >  - util.prosodyctl.check: Validate format of module list options
> >  - mod_websocket: Add a 'pre-session-close' event
> >  - mod_smacks: Fix stray watchdog closing sessions
> >  - mod_csi_simple: Disable revert-to-inactive timer when going to
> > active
> >    mode
> >  - mod_csi_simple: Clear delayed active mode timer on disable
> >  - mod_admin_shell: Fix display of remote cert status when expired etc
> >  - mod_smacks: Replace existing watchdog when starting hibernation
> >  - mod_http: Fix error if 'access_control_allow_origins' is set
> >  - mod_pubsub: Send correct 'jid' attribute in disco#items
> >  - mod_http: Unhook CORS handlers only if active to fix an error
> >  - mod_s2s: Add event where resolver for s2sout can be tweaked
> > 
> > It's already running fine in my server.
> > 
> > Partly related: I wanted to switch it to Lua 5.4, but that requires
> > adding lua54 FLAVOR to almost all the deps. Should I make that change
> > in two parts, first enabling the FLAVORs and then switching Prosody to
> > Lua 5.4, or should I fold all those changes into this patch?

I'd first commit this as-is and backport to stable, then bump the deps
to add the missing FLAVOR and switch prosody to lua 5.4.  this way we
avoid changing too many ports in -STABLE.  -STABLE users will get
prosody with lua5.4 with next release.

fwiw i'm perfectly fine with the other way around too however, and
happy to test diffs :-)

> > [...]
> 
> ok solene@
> 
> I tested it on 7.3-stable though, so ok to backport too :)

I tested on 7.3-stable too!  (with postgresql fwiw)

ok op@, both for the update and the backport while you're at it :-)

Reply via email to