Your message dated Fri, 31 Oct 2025 11:05:59 +0000
with message-id <[email protected]>
and subject line Bug#1118655: fixed in lua-ldoc 1.5.0-3
has caused the Debian Bug report #1118655,
regarding lua-ldoc: depends on lua5.1 | lua5.3 | lua5.4, but only works if
lua5.1 or lua5.2 is installed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1118655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118655
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lua-ldoc
Version: 1.5.0-2
Severity: serious
Justification: Policy 3.5
Tags: ftbfs
Control: affects -1 src:awesome
X-Debbugs-Cc: [email protected], [email protected],
[email protected]
If you install lua-ldoc together with lua5.3 (but not lua5.1), it
installs successfully but does not work:
$ podman run --rm -it docker.io/debian:sid-slim
# apt update
# apt install lua-ldoc lua5.3
# ldoc --help
Error: no suitable Lua interpreter found
Error: supported versions are: 5.2 5.1
This appears to be causing src:awesome (which uses lua5.3) to FTBFS in
Ubuntu (and possibly Debian too, I haven't checked), for example:
https://launchpadlibrarian.net/826360840/buildlog_ubuntu-resolute-amd64.awesome_4.3-8_BUILDING.txt.gz
The same would presumably happen for lua5.4.
Perhaps dh-lua needs a mechanism to parse scripts that run via lua-any,
and generate a dependency that is limited to their supported versions,
similar to the way dh-python recognises #!/usr/bin/python3.9 scripts and
generates a dependency on python3.9 specifically?
smcv
--- End Message ---
--- Begin Message ---
Source: lua-ldoc
Source-Version: 1.5.0-3
Done: Victor Seva <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lua-ldoc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Victor Seva <[email protected]> (supplier of updated lua-ldoc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 31 Oct 2025 11:17:20 +0100
Source: lua-ldoc
Architecture: source
Version: 1.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Lua Team <[email protected]>
Changed-By: Victor Seva <[email protected]>
Closes: 1118655
Changes:
lua-ldoc (1.5.0-3) unstable; urgency=medium
.
* refresh supported lua version using lua-any (Closes: #1118655)
Checksums-Sha1:
66508a068b3835e9852614af1c1ea16a75c7ac2a 1389 lua-ldoc_1.5.0-3.dsc
b2875ea2a5daefd8fb1062cb28856020927b7b97 5256 lua-ldoc_1.5.0-3.debian.tar.xz
df9d0988b22d7901a04bdfadaa7807c2057e3e46 5715 lua-ldoc_1.5.0-3_amd64.buildinfo
Checksums-Sha256:
b68aa32dd683c713ebd578fb74e97a0e8e2cd281519730ba4a9b38c03c8f9eed 1389
lua-ldoc_1.5.0-3.dsc
95ce01e630f81c97d2c3f679b94fd15d9887f673b0c973dc0247b3d9a1ee09ca 5256
lua-ldoc_1.5.0-3.debian.tar.xz
a579c38e9afb060626d9169309b7d9f0be97e299b42e23f3ee9e9a5d6b5f6529 5715
lua-ldoc_1.5.0-3_amd64.buildinfo
Files:
736017bd89b6e6d28da98eda7836e972 1389 interpreters optional
lua-ldoc_1.5.0-3.dsc
fdef2b3cb7afcda6ffd6b6c65e4571e4 5256 interpreters optional
lua-ldoc_1.5.0-3.debian.tar.xz
cbafa0792e1fe1d2552190ee19f6692c 5715 interpreters optional
lua-ldoc_1.5.0-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iIcEARYKAC8WIQQq6AO8RS0zF4SC1vh9e2XEKg7IsgUCaQSOrxEcdnNldmFAZGVi
aWFuLm9yZwAKCRB9e2XEKg7Isr9QAPoCTvtmXkeP8zCDoB2GAQxXtpl7jBXwJifg
ABVsxnrUGQEA4s7JE8b7jvycp5hiCjliKWEjz5b++SucY/6gi779tAA=
=N4zG
-----END PGP SIGNATURE-----
pgpZtni2641b_.pgp
Description: PGP signature
--- End Message ---
