Activity log for bug #2039873

Date Who What changed Old value New value Message
2023-10-19 17:04:16 Aleksandr Mikhalitsyn bug added bug
2023-10-19 17:05:31 Aleksandr Mikhalitsyn bug added subscriber Thomas Parrott
2023-10-19 19:25:40 Simon Déziel bug added subscriber Simon Déziel
2023-10-20 13:25:48 Aleksandr Mikhalitsyn bug added subscriber Serge Hallyn
2023-10-20 17:27:17 Aleksandr Mikhalitsyn attachment added set LXC_DEVEL to 0 https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5711815/+files/debdiff.diff
2023-10-20 17:54:08 Aleksandr Mikhalitsyn attachment removed set LXC_DEVEL to 0 https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5711815/+files/debdiff.diff
2023-10-20 17:54:28 Aleksandr Mikhalitsyn attachment added set LXC_DEVEL to 0 https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5711843/+files/debdiff.diff
2023-10-20 17:58:00 Aleksandr Mikhalitsyn bug added subscriber Stéphane Graber
2023-10-21 16:16:30 Ubuntu Foundations Team Bug Bot tags patch
2023-10-21 16:16:33 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Sponsors
2023-10-22 15:46:12 Aleksandr Mikhalitsyn description Dear colleagues, As I can see from: - https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy - https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/kinetic 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/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. 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://github.com/canonical/lxd/pull/12420). 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://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). 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://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. 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://github.com/lxc/lxc/tree/lxc-5.0.0). 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 [ Impact ] 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/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. 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://github.com/canonical/lxd/pull/12420). 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://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). 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://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] -
2023-10-22 15:46:43 Aleksandr Mikhalitsyn description [ Impact ] 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/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. 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://github.com/canonical/lxd/pull/12420). 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://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). 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://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. 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://github.com/canonical/lxd/pull/12420). 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://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). 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://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] -
2023-10-23 07:51:33 Launchpad Janitor lxc (Ubuntu): status New Confirmed
2023-10-23 15:42:21 Robie Basak bug added subscriber Robie Basak
2023-10-31 20:59:54 Bryce Harrington removed subscriber Ubuntu Sponsors
2023-11-23 14:01:27 Simon Déziel summary liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
2023-11-25 11:07:00 Aleksandr Mikhalitsyn attachment added debdiff for noble https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5723397/+files/noble_5.0.1_to_5.0.3_debdiff.diff
2023-12-07 08:46:34 Aleksandr Mikhalitsyn bug added subscriber Ubuntu Sponsors
2023-12-13 17:15:09 Athos Ribeiro removed subscriber Ubuntu Sponsors
2023-12-14 15:41:36 Thomas Hipp bug added subscriber Thomas Hipp
2023-12-14 15:41:41 Thomas Hipp removed subscriber Thomas Hipp
2024-01-04 15:39:30 Robie Basak bug added subscriber Ubuntu Sponsors
2024-01-18 16:06:40 Aleksandr Mikhalitsyn attachment added debdiff for mantic/noble (they have the same version 1:5.0.1-0ubuntu7) https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5740489/+files/debdiff_for_mantic_and_noble.diff
2024-01-18 16:34:43 Aleksandr Mikhalitsyn attachment added debdiff for jammy https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5740492/+files/debdiff_for_jammy.diff
2024-01-18 16:35:30 Aleksandr Mikhalitsyn attachment added debdiff for mantic/noble (they have the same version 1:5.0.1-0ubuntu7) https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5740493/+files/debdiff_for_mantic_and_noble.diff
2024-01-18 16:35:40 Aleksandr Mikhalitsyn attachment removed debdiff for mantic/noble (they have the same version 1:5.0.1-0ubuntu7) https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5740489/+files/debdiff_for_mantic_and_noble.diff
2024-01-19 19:11:27 Andreas Hasenack nominated for series Ubuntu Noble
2024-01-19 19:11:27 Andreas Hasenack bug task added lxc (Ubuntu Noble)
2024-01-19 19:11:27 Andreas Hasenack nominated for series Ubuntu Jammy
2024-01-19 19:11:27 Andreas Hasenack bug task added lxc (Ubuntu Jammy)
2024-01-19 19:11:27 Andreas Hasenack nominated for series Ubuntu Mantic
2024-01-19 19:11:27 Andreas Hasenack bug task added lxc (Ubuntu Mantic)
2024-01-19 19:46:21 Andreas Hasenack lxc (Ubuntu Mantic): status New Confirmed
2024-01-19 19:47:45 Andreas Hasenack lxc (Ubuntu Jammy): status New Confirmed
2024-01-19 20:12:03 Andreas Hasenack bug added subscriber Andreas Hasenack
2024-01-24 16:28:53 Dave Jones lxc (Ubuntu Noble): status Confirmed Fix Committed
2024-01-24 21:42:56 Ubuntu Archive Robot bug added subscriber Dave Jones
2024-01-24 22:14:53 Dave Jones summary liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
2024-01-24 22:15:07 Dave Jones removed subscriber Ubuntu Sponsors
2024-01-25 01:40:35 Launchpad Janitor lxc (Ubuntu Noble): status Fix Committed Fix Released
2024-02-02 07:47:08 Timo Aaltonen lxc (Ubuntu Mantic): status Confirmed Fix Committed
2024-02-02 07:47:10 Timo Aaltonen bug added subscriber Ubuntu Stable Release Updates Team
2024-02-02 07:47:11 Timo Aaltonen bug added subscriber SRU Verification
2024-02-02 07:47:15 Timo Aaltonen tags patch patch verification-needed verification-needed-mantic
2024-02-02 10:20:00 Timo Aaltonen lxc (Ubuntu Jammy): status Confirmed Fix Committed
2024-02-02 10:20:06 Timo Aaltonen tags patch verification-needed verification-needed-mantic patch verification-needed verification-needed-jammy verification-needed-mantic
2024-02-02 14:03:43 Simon Déziel tags patch verification-needed verification-needed-jammy verification-needed-mantic patch verification-done-jammy verification-needed verification-needed-mantic
2024-02-02 14:58:54 Simon Déziel tags patch verification-done-jammy verification-needed verification-needed-mantic patch verification-done verification-done-jammy verification-done-mantic
2024-02-12 10:37:13 Launchpad Janitor lxc (Ubuntu Mantic): status Fix Committed Fix Released
2024-02-12 10:37:16 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2024-02-12 10:46:41 Launchpad Janitor lxc (Ubuntu Jammy): status Fix Committed Fix Released