Support more modern Lua versions - to keep only one in main

[Christian Ehrhardt ]

Hi,
in the past we have tried to move 5.1->5.2 (bug 1324062) but right now we have:
For older Lua versions being held in main I found:
- apache2-bin depends on lua5.2
- dovecot depends depends on lua5.3
And a request for lua5.4 in bug 1909665.

Step I:

I'd request to check if we can:
- at least move apache2 to lua5.3 to be able to demote lua5.2 in Hirsute
- [1] suggests that 5.3 might work right away

Step II:

Further down the road I'd request to check and work on moving dovecot+apache2 to lua5.4 (unless it turns out impossible). Then we could completely move to 5.4 and demote 5.3 as well.
And we could make ibus-libpinyin a sync again then (see bug 1909665).

[1]: https://git.launchpad.net/ubuntu/+source/apache2/tree/modules/lua/config.m4?h=applied/ubuntu/hirsute#n37

[Paride Legovini (paride)]

I verified that apache2 builds fine against lua5.3 and filed [1] in Debian. This is similar to [2] and the apache2 maintainers promptly bumped the build-dep back then.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979501
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820243

[Paride Legovini (paride)]

(I also verified that apache2 does *not* build against lua5.4)

[Paride Legovini (paride)]

apache2 "Fix Committed" in Debian: https://salsa.debian.org/apache-team/apache2/-/commit/809ce1694aeea169bcdbac6327606e3017d1ac42

[Bryce Harrington (bryce)]

I've posted an MP with a merge of the Apache2 with the lua5.2->5.3 change.

[Launchpad Janitor (janitor)]

This bug was fixed in the package apache2 - 2.4.46-4ubuntu1

---------------
apache2 (2.4.46-4ubuntu1) hirsute; urgency=medium

  * Merge with Debian unstable, to allow moving from lua5.2 to
    lua5.3 (LP: #1910372). Remaining changes:
    - debian/{control, apache2.install, apache2-utils.ufw.profile,
      apache2.dirs}: Add ufw profiles.
    - debian/apache2.py, debian/apache2-bin.install: Add apport hook.
    - d/index.html, d/icons/ubuntu-logo.png, d/apache2.postrm: replace
      Debian with Ubuntu on default page.
      + d/source/include-binaries: add Ubuntu icon file
    - d/t/control, d/t/check-http2: add basic test for http2 support
    - d/p/t/apache/expr_string.t: Avoid test suite failure due to timing
      issue reading error log too quickly after request, by adding a sleep.
      (LP #1890302)
    - d/apache2ctl: Also use systemd for graceful if it is in use.
      This extends an earlier fix for the start command to behave
      similarly for restart / graceful. Fixes service failures on
      unattended upgrade.
  * Drop:
    - d/perl-framework/t/modules/allowmethods.t: disable reset test. This
      was re-added by mistake in 2.4.41-1 (Closes #921024)
      [Included in Debian 2.4.46-3]
  * d/apache2ctl: Also use /run/systemd to check for systemd usage
    (LP: #1918209)

 -- Bryce Harrington <email address hidden> Tue, 09 Mar 2021 00:45:35 +0000

[Bryce Harrington (bryce)]

For the aforementioned lua removal I've filed:

https://bugs.launchpad.net/ubuntu/+source/lua5.2/+bug/1918957

[Paride Legovini (paride)]

I think "Step I" of this bug has been reached: we have only lua5.3 in main.

Eventually we'll get to "Step II" and move to lua5.4, which is supported by apache2 >=2.4.47 [1], but there's no MIR for lua5.4 at the moment (LP: #1909665 lua5.4 MIR is a Wontfix), so no action is required at the moment.

[1] http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/CHANGES?view=markup

[Gunnar Hjalmarsson (gunnarhj)]

@Christian: Is it possibly time to re-open the lua5.4 MIR request at bug #1909665?

[Christian Ehrhardt  (paelzer)]

Hi Gunnar, the question is if not (compared to the past) most of the packages in general and all of the packages in main would be able to use lua5.4.
In the past it was a wild mix of 5.2/5.3/5.4 and the common denominator of 5.3 made us settle on that for now. I agree that going forward would be great, but TBH the plan for 22.04 is already rather full and considering that in the 22.10 timeframe would allow more upstreams to move up to the new version.

To track and do that down the road re-opening bug 1909665 should be a good first step.
But since it isn't waiting on the MIR team but on owning teams to resolve things upfront it would go to "incomplete" then.