[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-05-29 Thread Christian Ehrhardt 
*** This bug is a duplicate of bug 1876055 *** https://bugs.launchpad.net/bugs/1876055 Thanks Jamie, that will fix this bug here as well then, IMHO we should mark it as a dup then. ** This bug has been marked a duplicate of bug 1876055 SRU: Backport 2.4.3-1ubuntu2 from groovy to

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-05-28 Thread Jamie Strandboge
There is actually an SRU in progress for libseccomp: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu.

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-05-27 Thread Lucas Kanashiro
** Also affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Changed in: docker.io (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu.

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-03-26 Thread xantares
Focal may be affected after all then -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist Status in libseccomp package in

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-03-26 Thread xantares
turns ou we may also need this fix in docker: https://github.com/moby/moby/pull/40739 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-03-25 Thread xantares
of course, you do: cd /tmp && git clone https://github.com/xantares/test-seccomp-time64.git && docker build test-seccomp-time64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu.

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-03-25 Thread Rafael David Tinoco
I believe the patch you're mentioning is worth backporting to Bionic and Eoan is this: $ git log -1 -p be65b26b67099be2b2b4890d736dbd1ad15adf36 | diffstat include/seccomp-syscalls.h| 208 +- src/arch-aarch64-syscalls.c | 35 ++-

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-03-25 Thread Rafael David Tinoco
Could you provide a failing test case so we can base the SRU (stable release update) on that use it as a non-regression test ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu.

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-03-24 Thread Ubuntu Foundations Team Bug Bot
The attachment "backport time64 syscalls from 2.4.2 into 2.4.1" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

2020-03-24 Thread xantares
** Patch added: "backport time64 syscalls from 2.4.2 into 2.4.1" https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+attachment/5340882/+files/libseccomp241-time64.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is