[pkg-lxc-devel] Bug#908223: Bug#908192

[Matthias Heinz]

Hi,

well, from my point of view it's a huge amount. Just have a look at this, it 
compares stable-2.0 with the tag for 2.0.9:

https://github.com/lxc/lxc/compare/lxc-2.0.9...stable-2.0

(Sadly the direct link to all changes for conf.c doesn't work. You'll have to 
scroll down. Sorry for the inconvenience.)

I don't know what the right choice would be. Maybe there will be a 2.0.10 
release soon, which would render this bug obsolete. On the other hand LXC 2.0 
will only get updates until June 1st 2021. This could be right in time for 
Bullseye, but I wouldn't count on it.

Switching to 3.0 will be necessary one day. But it will be a lot of work, I 
guess. Is it worth it doing this transition a few month before the freeze 
(even though there's no official date yet afaik)?

I don't know.

Best regards
Matthias


Am Montag, 22. Oktober 2018, 14:29:19 CEST schrieb Pierre-Elliott Bécue:
> Cc-ing Christian as he proposed the patch.
> 
> Le jeudi 18 octobre 2018 à 14:32:12+0200, Matthias Heinz a écrit :
> > Hi,
> > 
> > I've tried applying the patch to the 2.0.9 source. Unfortunately there
> > have
> > been more changes to conf.c since the release of lxc 2.0.9 and this patch
> > wont apply without applying these changes as well.
> 
> What amount of patches would it represent? Would it be relevant to consider
> updating lxc in buster to a newer release?
> 
> Cheers,