I'm closing since we aren't currently patching webkitgtk and 2 years
have passed.
On Sun, Jan 07, 2018 at 04:23:31PM -0500, Mark H Weaver wrote:
> My best guess is that it's caused by the fact that
> our 'patch-and-repack' mechanism, which generates the patched tarball,
> resets all the timestamps to 0, whereas previously we built the upstream
> tarball directly with non-zero ti
On Sun, Jan 07, 2018 at 04:23:31PM -0500, Mark H Weaver wrote:
> I recently wrote on guix-devel:
>
> > I just followed this up with a Spectre mitigation for WebKitGTK+
> > backported from upstream WebKit:
> >
> >
> > https://git.savannah.gnu.org/cgit/guix.git/commit/?id=56804398a94bea941183ae4e
I recently wrote on guix-devel:
> I just followed this up with a Spectre mitigation for WebKitGTK+
> backported from upstream WebKit:
>
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=56804398a94bea941183ae4ed29d2a9f82069a6f
Unfortunately, this seems to have introduced non-determinis
