From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Francois Perrad <francois.perrad.86@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH 2/2] package/prosody: bump to version 0.12.6
Date: Sat, 10 Oct 2026 10:33:22 +0200 [thread overview]
Message-ID: <asn4EgwWMncL9NZe@windsurf> (raw)
In-Reply-To: <20261005134056.94384-2-francois.perrad.86@gmail.com>
Hello,
On Mon, Oct 05, 2026 at 03:40:56PM +0200, Francois Perrad wrote:
> Lua 5.4 is recommended for this branch,
> Lua 5.1 (& LuaJIT) is deprecated.
> see https://prosody.im/doc/release/0.12.0#lua-version-support
>
> Signed-off-by: Francois Perrad <francois.perrad.86@gmail.com>
> ---
> package/prosody/0001-enable-syslog.patch | 4 +-
> package/prosody/0002-add-pidfile.patch | 6 +--
> package/prosody/Config.in | 8 +--
> package/prosody/S50prosody | 3 +-
> package/prosody/prosody.hash | 11 ++--
> package/prosody/prosody.mk | 12 ++---
> support/testing/tests/package/test_prosody.py | 51 ++++++++-----------
> .../rootfs-overlay/etc/resolv.conf | 0
Could you comment on why you need this empty /etc/resolv.conf in the
rootfs overlay for the test?
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-10 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 13:40 [Buildroot] [PATCH 1/2] package/luaunbound: new package Francois Perrad
2026-10-05 13:40 ` [Buildroot] [PATCH 2/2] package/prosody: bump to version 0.12.6 Francois Perrad
2026-10-10 8:33 ` Thomas Petazzoni via buildroot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=asn4EgwWMncL9NZe@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=francois.perrad.86@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox