Your message dated Tue, 24 May 2022 21:28:19 -0400 with message-id <[email protected]> and subject line has caused the Debian Bug report #996788, regarding libnginx-mod-http-lua: Please enable luajit for arm64 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.) -- 996788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996788 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libnginx-mod-http-lua Severity: wishlist Tags: patch Currently libnginx-mod-http-lua declares architecture-specific build-deps to choose either liblua5.1 or libluajit-5.1. For the arm64 architecture, liblua5.1 is used even though luajit is availabile on this architecture. I've locally built nginx with the following change to debian/control and performed basic testing of the resulting packages: diff --git a/debian/control b/debian/control index fe24d3e..3415fd8 100644 --- a/debian/control +++ b/debian/control @@ -10,8 +10,8 @@ Build-Depends: debhelper-compat (= 13), libgd-dev, libgeoip-dev, libhiredis-dev, - liblua5.1-0-dev [!i386 !amd64 !kfreebsd-i386 !armel !armhf !powerpc !powerpcspe !mips !mipsel], - libluajit-5.1-dev [i386 amd64 kfreebsd-i386 armel armhf powerpc powerpcspe mips mipsel], + liblua5.1-0-dev [!i386 !amd64 !kfreebsd-i386 !arm64 !armel !armhf !powerpc !powerpcspe !mips !mipsel], + libluajit-5.1-dev [i386 amd64 kfreebsd-i386 arm64 armel armhf powerpc powerpcspe mips mipsel], libmaxminddb-dev, libmhash-dev, libpam0g-dev, Please enable libluajit for the arm64 builds of libnginx-mod-http-lua. Let me know if you have concerns about this request or would like to see further evidence of testing. Thanks noah
--- End Message ---
--- Begin Message ---Control: fixed -1 1.18.0-9 This was fixed back in 1.18.0-9 during our QA cleanup of the package. Thomas
--- End Message ---
