Your message dated Sun, 06 Apr 2025 23:19:56 +0000
with message-id <[email protected]>
and subject line Bug#1100389: fixed in sysdig 0.40.0+repack-2
has caused the Debian Bug report #1100389,
regarding sysdig: FTBFS on riscv64: ‘luaL_setfuncs’ was not declared in this
scope;
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.)
--
1100389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100389
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: sysdig
Version: sysdig: 0.40.0+repack-1
Severity: serious
Tags: ftbfs, patch
User: [email protected]
Usertags: riscv64
X-Debbugs-Cc: [email protected], [email protected]
Dear Maintainer,
sysdig has one FTBFS issue on risv64:
```
/build/reproducible-path/sysdig-0.40.0+repack/userspace/chisel/chisel.cpp:985:9:
error: ‘luaL_setfuncs’ was not declared in this scope; did you mean
‘lua_setfenv’?
985 | luaL_setfuncs(ls, ll_tool, 0);
| ^~~~~~~~~~~~~
| lua_setfenv
/build/reproducible-path/sysdig-0.40.0+repack/userspace/chisel/chisel.cpp: In
member function ‘void sinsp_chisel::load(std::string, bool)’:
/build/reproducible-path/sysdig-0.40.0+repack/userspace/chisel/chisel.cpp:1196:9:
error: ‘luaL_setfuncs’ was not declared in this scope; did you mean
‘lua_setfenv’?
1196 | luaL_setfuncs(m_ls, ll_tool, 0);
| ^~~~~~~~~~~~~
| lua_setfenv
...
```
Please to see the full buildd log:
https://buildd.debian.org/status/fetch.php?pkg=sysdig&arch=riscv64&ver=0.40.0%2Brepack-1&stamp=1741839403&raw=0
It seems the build-dependence on riscv64 will need switch to
libluajit-5.1-dev[0] also and it works on my local build.
BTW, sysdig has FTBFS issues on armel, mips64el, ppc64el and
s390x[1], I guess once libfalcosecurity0-dev catch up on armel and s390x
the building will be okay. In fact, I did a giveback on mips64el and it
worked. But for ppc64el, unfortunately, these is no libluajit-5.1
supported, so unless other workaround, otherwise it has FTBFS on ppc64el
always. So I am ccing the ppc porter to have a look at this.
[0]: https://tracker.debian.org/pkg/luajit
[1]: https://buildd.debian.org/status/package.php?p=sysdig
--
Regards,
--
Bo YU
diff -Nru sysdig-0.40.0+repack/debian/changelog
sysdig-0.40.0+repack/debian/changelog
--- sysdig-0.40.0+repack/debian/changelog 2025-02-22 00:51:54.000000000
+0000
+++ sysdig-0.40.0+repack/debian/changelog 2025-03-13 08:01:04.000000000
+0000
@@ -1,3 +1,11 @@
+sysdig (0.40.0+repack-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Build dependence with libluajit-5.1-dev explicitly on riscv64.
+ (Closes: #-1)
+
+ -- Bo YU <[email protected]> Thu, 13 Mar 2025 08:01:04 +0000
+
sysdig (0.40.0+repack-1) unstable; urgency=medium
* New upstream release (Closes: #1095317)
diff -Nru sysdig-0.40.0+repack/debian/control
sysdig-0.40.0+repack/debian/control
--- sysdig-0.40.0+repack/debian/control 2024-10-17 13:04:37.000000000 +0000
+++ sysdig-0.40.0+repack/debian/control 2025-03-13 08:01:04.000000000 +0000
@@ -20,7 +20,7 @@
zlib1g-dev,
uthash-dev,
# Same as the dependency in falcosecurity-libs
- libluajit-5.1-dev [amd64 arm64 armel armhf i386 mips64el s390x]
| liblua5.1-0-dev
+ libluajit-5.1-dev [amd64 arm64 armel armhf i386 mips64el
riscv64 s390x] | liblua5.1-0-dev
Standards-Version: 4.5.0
Homepage: https://www.sysdig.com/
Vcs-Git: https://salsa.debian.org/debian/sysdig.git
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: sysdig
Source-Version: 0.40.0+repack-2
Done: Dima Kogan <[email protected]>
We believe that the bug you reported is fixed in the latest version of
sysdig, 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.
Dima Kogan <[email protected]> (supplier of updated sysdig 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: Sun, 06 Apr 2025 16:01:16 -0700
Source: sysdig
Architecture: source
Version: 0.40.0+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Dima Kogan <[email protected]>
Changed-By: Dima Kogan <[email protected]>
Closes: 1100389
Changes:
sysdig (0.40.0+repack-2) unstable; urgency=medium
.
* On riscv64 we Build-Depends: libluajit-5.1-dev (Closes: #1100389)
Thanks to Bo YU <[email protected]> for finding and solving the issue
Checksums-Sha1:
954ec02b89ebd36076506237f21d245403b132cc 2367 sysdig_0.40.0+repack-2.dsc
98bc1c8b04d77dfabe28020f4dfc3e2305a6bfc2 7320
sysdig_0.40.0+repack-2.debian.tar.xz
8b673d497a8d447b990c0270991b1698e428cba5 10060
sysdig_0.40.0+repack-2_source.buildinfo
Checksums-Sha256:
9c06e99d53d59cca97f7c55e5eea931def1713d8203182af79d6609ac62dce8c 2367
sysdig_0.40.0+repack-2.dsc
6c3609991fcfe435698363aba17d68713798921f5139f7d8a09389cc24e7346f 7320
sysdig_0.40.0+repack-2.debian.tar.xz
1819472f625ccfd04f9a2789e755d96f1ef4d1db5694a1fb72a3c46e57952c5e 10060
sysdig_0.40.0+repack-2_source.buildinfo
Files:
764f3c4f3682973f9f733ed2cf86fadf 2367 admin optional sysdig_0.40.0+repack-2.dsc
7a48920e9d1116c7d10dd01184975a38 7320 admin optional
sysdig_0.40.0+repack-2.debian.tar.xz
8d56901cfd455be3c1069732692432c5 10060 admin optional
sysdig_0.40.0+repack-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmfzB/QSHGRrb2dhbkBk
ZWJpYW4ub3JnAAoJEKzHws8wlBGIEb0P/RPa39tdtqnnXGAnt+vygVhlfxtSyNak
KkUSOv66AajcujfeoDS8CYrRyszlKtyRPLbS++bRrXa4QPxObtvSvL61QLP8Vm6c
sCH46E59Ih4FG7hRGYE9VpnjhyFdkL6TvzN5eEOPWnO+P5Pl0L/Qzy8SwRRKUr8K
CuSUmyP7KSNgMekgWUphMS9LBsQgz1wDkraKoYTcy5+3rMsW2iCBSSo0N5+LY48a
vDUB3N9WhgPIHlQMT8fEUSNXPO3u3SI9FR5bv9xYgM7WqJmU+1e5S6kG85m7dSRH
9HgZeCTHmIDpNPV1SwLUADg9L8rxB92bLNcE3GcBvNch06p4fY5Z/gfjPhvPD/oF
b1KJtUOP4U5V1NTQ6vQDiXiaZ/bdJL1Uac12miMuFbKjOIp268D1WVFvPkz/cmZK
wYLGUcQYbwhzUHokZkU24eoSRRlZI0+tZxzacVc3U9QEQXEBRGUcx+WFxWCrNvSv
xNGcckxbDaTK0DBgaKtQd6rSGyj9pf8yQ1/2MSvKcDXaTdlhM6gG4BGu7d6Tbh8f
KUxS29XDqKrt9xBHkfHSNOVyOVumKFcijs4tytn5uhHPVFo1/kVCDpclnQOKAVih
s/JEj8b+hhi18WRo4dBhVcAxOoSVZlrviyaoF341PzLzyzMrYsadD92mtlRZ+316
8On9xXQK8En2
=zC8g
-----END PGP SIGNATURE-----
pgpHzg2xCoGb3.pgp
Description: PGP signature
--- End Message ---
