Noble's now in proposed and looks to have built successfully so I'll
mark that Fix Committed. I'm just uploading the mantic and jammy SRUs
(the jammy one took a little longer as the fix is slightly different
there; appears the build system changed between jammy and mantic).
** Changed in: lxc
Okay, good enough for me -- I'll sponsor my aforementioned branch for
noble and have a look at the mantic and jammy SRUs tomorrow, assuming
everything builds happily in noble.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thanks, Dave!
Your branch and changes are looking good to me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2039873
Title:
liblxc-dev was built with LXC_DEVEL=1 in Ubuntu
I had a little time to look over this again in my patch-pilot shift. I
agree it's almost certainly best to just get LXC_DEVEL set correctly
quickly. Andreas' suggested branch is a good start, but I agree with the
critique that the DEP-8 test should be checking the installed headers
rather than the
>What are your thoughts on (a) and (b)?
>being marked as superficial won't block a migration if it fails (IIRC:
at least, it's definitely not a hard error). And we do want this to
"stop the line" if it fails, right?
Ideally, it's better to block upload of package if this fails, yes.
Because it's
I updated the tasks on this bug after having verified what has LXC_DEVEL
set to 1, so we should be good now in terms of affected releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
In fact, the same but updated note was already on
https://documentation.ubuntu.com/lxd/en/latest/installing/#install-lxd-
from-source where it mentions that it affects 22.04 onward while the one
you dug up says 23.04/23.10 are not affected ;)
--
You received this bug notification because you are
Food for thought for an SRU, here is an example of an upstream that
noted[1] this problem:
NOTE: If you use the `liblxc-dev` package and get compile time errors
when building the `go-lxc` module,
ensure that the value for `LXC_DEVEL` is `0` for your `liblxc` build. To check
that, look
I imported your noble debdiff and pushed to this branch:
https://code.launchpad.net/~ahasenack/ubuntu/+source/lxc/+git/lxc/+ref/noble-
lxc-drop-devel-2039873
If you run "git ubuntu clone lxc; cd lxc; git ubuntu remote add
ahasenack; git checkout noble-lxc-drop-devel-2039873" you should have a
** Also affects: lxc (Ubuntu Noble)
Importance: Undecided
Status: Confirmed
** Also affects: lxc (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Mantic)
Importance: Undecided
Status: New
--
You received this bug notification because
Updated debdiff for Mantic/Noble (added Launchpad bug reference)
PPA:
https://launchpad.net/~mihalicyn/+archive/ubuntu/lxc-test-ppa-for-mantic-and-noble
** Patch added: "debdiff for mantic/noble (they have the same version
1:5.0.1-0ubuntu7)"
debdiff for Jammy
PPA:
https://launchpad.net/~mihalicyn/+archive/ubuntu/lxc-test-ppa-for-jammy
** Patch added: "debdiff for jammy"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+attachment/5740492/+files/debdiff_for_jammy.diff
--
You received this bug notification because you
debdiff for mantic/noble (they have the same version 1:5.0.1-0ubuntu7
currently)
+lxc (1:5.0.1-0ubuntu8) mantic; urgency=medium
+
+ * Fix the LXC_DEVEL value to be 0
+- d/p/0003-meson-Set-DEVEL-flag-post-release.patch was dropped
+ as it should not be in the production builds
+ * Added
I agree with Stéphane, it would be better to get the LXC_DEVEL issue
fixed quickly and then deal with the packaging refresh separately.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
My two cents here are that we should:
- Rapidly fix the LXC_DEVEL situation across all supported Ubuntu releases.
- Separately prepare a new package for noble which performs the Debian merge
and introduces the needed transitional packages to get users from the current
Ubuntu-specific naming
Alternatively, I can just pull a new upstream LXC sources and we keep
the Ubuntu-specific package as it is without switching to a Debian base
if it's so complex procedure. WDYT?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Dear colleagues,
I have taken a look on this ubuntu-import/rebase thing, thanks a lot for
your suggestions and advice.
Unfortunately, I can't see any possibility to follow this Ubuntu-import
way. Because the last Debian-based version of the LXC package was in
2012 (!) [
Hi Aleksandr,
Let me try to clarify this for you. The two options presented by you are
not what we want. We want to grab the package from Debian unstable (with
the latest changes) and merge what we have in Ubuntu, which means having
a complete changelog (including the previous Ubuntu changes).
Ok, I have tried to do that but get stuck and have a few questions about
the process.
>In this case, the commits in the repo would be based on debian/sid
rather than ubuntu/noble-devel. This >would ensure we incorporate the
changes Debian has placed on top of lxc, as well as our own (and means
in
Thanks, Aleksandr.
I am unsubscribing ubuntu-sponsors until
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/comments/21
is addressed. Please subscribe it back here when it is done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Hello, Dave!
Huge thanks for your attention to this bug!
>The major thing that I think needs correction is that this patch is
built on top of ubuntu/noble-devel by importing the upstream 5.0.3, but
what Stéphane suggested in comment 14 was to take the Debian upstream
(currently 5.0.3-2) and
Thanks very much for the updated debdiff. There's a lot of changes here
to look at and unfortunately I've run out of time looking through it all
during my patch-pilot shift, but here's what I've got so far:
The major thing that I think needs correction is that this patch is
built on top of
The ubuntu-sponsors team has been subscribed to the bug
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2039873
Title:
liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04
Ok, I'm attaching a debdiff for Noble.
Changelog:
Import LXC 5.0.3
- imported LXC 5.0.3 original sources
- dropped all debian/patches which are present in the LXC 5.0.3 already
- added autopkgtest to ensure that LXC_DEVEL is always 0
- aligned package names with the
** Summary changed:
- 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
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
25 matches
Mail list logo
