Hi Dimitri,
On Wed, Aug 23, 2017 at 10:54:31PM +0100, Dimitri John Ledkov wrote:
> On 23 August 2017 at 22:09, Salvatore Bonaccorso <car...@debian.org> wrote:
> > Hi Dimitri,
> >
> > On Wed, Aug 23, 2017 at 03:32:09PM +0100, Dimitri John Ledkov wrote:
> >> Package: criu
> >> Version: new upstream release v3.4, enable arm64 and s390x
> >> Severity: normal
> >>
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA256
> >>
> >> Dear Maintainer,
> >>
> >> Is it ok to update criu to v3.4?
> >>
> >> I did gbp pristine-tar import, and did a test build and tested the
> >> package. It seems to work fine for trivial checkpoint &
> >> restore. Pushed as xnox branch into the collab-maint, without any
> >> other changes. Could you prepare upload v3.4, or may I?
> >>
> >> I have also enabled builds on arm64 and s390x. I have root access to
> >> both machines and for trivial checkpoint & restore they appear to work
> >> fine.
> >
> > I saw your bug report a bit late. Okay so if both were tested then I'm
> > going to enable it in the next upload.
>
> Let me be more specific "it works as good as amd64" for me.
>
> I'm mostly interested in lxd checkpoint & restore - Meaning with like
> latest ubuntu containers with networkd on all architectures
> chepints/restores fail in similar fashion. Due to held up sockets /
> unread messages etc.
> But yeah, for trivial processes things work fine across the board.
Yes I see. I have uploaded already to experimental 3.4 and will move
it to unstable once I have verified ppc64el builds again as well.
Regards and thanks
Salvatore
p.s.: currently i think criu is unsuitable for a stable release, thus I
have a blocking bug in place since several months by now. But
generally I should be relatively fast to upload the new upstream
versions to experimental first, then unstable.
