From: Michael Tremer <michael.tremer@ipfire.org>
To: Valters Jansons <valter.jansons@gmail.com>
Cc: IPFire Location Mailing List <location@lists.ipfire.org>
Subject: Re: debian: Build the Lua module for Lua 5.2 and 5.3, too
Date: Wed, 28 Oct 2026 18:17:24 +0000 [thread overview]
Message-ID: <8CC8EF20-5338-4562-834D-1D36BC29F6CC@ipfire.org> (raw)
In-Reply-To: <CA+sCei1Pq-h9srNSZ6SDmgxru2mf9BTX0RDEFhGx8+sJyvbz4Q@mail.gmail.com>
Hello Valters,
I enabled the other versions:
https://git.ipfire.org/?p=location/libloc.git;a=commitdiff;h=704e60c5fb64202a735f208907daa732ceae3405
If we cannot run the tests, well I don’t know what else we can do. But I would argue that this is low risk since we at least test the code on one version. It would be preferable if we could test it on the others, too, but the differences are small enough that I am taking the risk.
All the best,
-Michael
> On 27 Oct 2026, at 21:57, Valters Jansons <valter.jansons@gmail.com> wrote:
>
> Michael,
>
> I wanted to adopt this into wider use, but lua-unit dropped Lua 5.2
> builds in Debian around 11 months ago. debian/3.4-2 was the latest
> luaunit that had support, so trixie will build fine (and so will
> bookworm). However, forky has 3.5-1 already, so trying to build there
> results in:
>
> lua5.2: tests/lua/main.lua:20: module 'luaunit' not found
>
> Would you prefer we package only 5.4 and 5.1 now, or do you have
> thoughts about the testing approach?
>
> --Valters
prev parent reply other threads:[~2026-10-28 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 21:57 Valters Jansons
2026-10-28 18:17 ` Michael Tremer [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=8CC8EF20-5338-4562-834D-1D36BC29F6CC@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=location@lists.ipfire.org \
--cc=valter.jansons@gmail.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