liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Dear colleagues,
As I can see from:
- https:/
- https:/
LXC 5.0.0 was built with LXC_DEVEL=1 set. But for release build we should have LXC_DEVEL=0.
LXC_DEVEL is a variable that appears in the /usr/include/
Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc
from source (for example, LXD, go-lxc: https:/
Q: Why it was not a problem for so long?
A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https:/
This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https:/
And also, as I can see the source code that was used to build LXC 5.0.0 in Jammy/Kinetic is not precisely the same as in the official LXC 5.0.0 tag (https:/
I understand that Jammy is a LTS release and making any changes is a problem and we should go through the SRU process. But I believe that we have to do something at least with LXC_DEVEL to make things work properly.
Kind regards,
Alex
https:/ /git.launchpad. net/ubuntu/ +source/ lxc/tree/ debian/ patches/ 0003-meson- Set-DEVEL- flag-post- release. patch is the patch that should be dropped by the SRU.