Hi, On Sat, Aug 24, 2024 at 09:08:14PM +0200, Aleksandr Mikhalitsyn wrote: > On Sat, Aug 24, 2024 at 8:48 PM Salvatore Bonaccorso <car...@debian.org> > wrote: > > > > Hi, > > Hi Salvatore, > > > > > On Sat, Aug 24, 2024 at 08:28:20PM +0200, Alexander Mikhalitsyn wrote: > > > Dear friends, > > > > > > I'm trying to fix CRIU package in Ubuntu Noble: > > > https://bugs.launchpad.net/ubuntu/+source/criu/+bug/2066148 > > > > > > We had a discussion with my colleague Simon Déziel about my > > > debdiff [1] for CRIU package in Ubuntu and he pointed me out that > > > there is a bug on Debian bugtracker about these build issues. > > > > > > Of course, I would like to help to fix all problems with CRIU > > > package in Debian too. (And hopefully, these changes will > > > be autoinherited by Ubuntu.) > > > > > > As far as I understand, I need to prepare a PR that includes > > > patches from debdiff for master branch (based on CRIU 3.19). > > > What I can't understand is why debian/sid still uses 3.17 release? > > > Do I need to fix 3.17 branch too? > > > > > > JFYI. We are preparing a new CRIU release 4.0: > > > https://github.com/checkpoint-restore/criu/pull/2467 > > > > The main issue right now I have with criu and blocking 3.19 is the > > build part for the python code, I'm unable to make it ocrrectly build > > with pyproject. > > Is this locally reproducible? > Can I just take the debian/sid container, pull the master branch from > https://salsa.debian.org/debian/criu and do debuild to see the problem?
Yes, that plus the current WIP patch to try to make the python code build with pybuild integration. Once I have this resoved I'm really more than happy to move on with the version (and then timely follow with 4.0 once thats out). Regards, Salvatore
