Desktop Environment (if applicable):
Docker container running on an M1 macOS laptop
Problem Description: apt install liblua5.5-dev writes a pkgconf lua5.5.pc that contains a typo which breaks luarocks. I have tried two workarounds below, but neither fixes the problem.
Relevant System Information:
It is a Docker container.
You should send a proper bug report. Plus, it’s not a typo, so you may want to be more clear in your report. To me it looks like up to and including v5.4 the version number was hardcoded and has since been replaced by a macro, which is why the grep ... |cut ... pipeline returns the whole line.
The value the package rules script is after had been renamed to LUA_VERSION_RELEASE_N. I presume, there were other places needing pure numerical value and not string. In any case, it is the packaging bug, pkg-config files do not exist upstream.
FYI, just trying to run ubuntu-bug should trigger the command not found hook, which searches for it, to then suggest:
sudo apt install apport
Or one can install apt-file and then do apt-file search ubuntu-bug. The benefit of the command not found hook is, that it also searches the snap store.
Given that this bug renders the package and others pretty much useless, as it seems, you should raise the importance to “high”, if you can. I think, as the author of the report, you should be able to do that. The reason lies in the package being virtually unusable. Such is a release criticial bug in Debian speak, i.e. it will never make it into a (Debian) stable release with such a bug pending. If such are found after a release, they warrant a package upgrade, even if it’s not security related.
I’m not too familiar with Ubuntu’s policy and how this works on Lauchpad, but I’m pretty sure that’s a slam dunk, even if policies and terminology may differ.
Good job tracing the problem back to Debian!
But I don’t see a Debian bug report (which will ping the package maintainer).
Looks like you merely commented on the patch (which won’t ping the maintainer).
After you create the Debian bug (bugs.debian.org), be sure to link the Launchpad bug to the Debian bug.
Please see my last comment there. Mind you, I’m not a luarocks user, so I may have misunderstood what the expected behavior is. Running the config steps with a (manually) fixed lua5.5.pc seems to work.