On Sat, Jul 21, 2018 at 10:34:48PM +0200, Andreas Enge wrote:
> Does this ring a bell?
Nix has a patch:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/qt-5/5.11/qtwebkit.patch
diff --git a/Source/WebKit2/PlatformQt.cmake b/Source/WebKit2/PlatformQt.cmake
--- a/Source/
On Sat, Jul 21, 2018 at 09:52:25PM +0300, Efraim Flashner wrote:
> I see, debian moved to the same source. I am worried though that that
> repo hasn't seen any action in 6 months.
And it does not compile at all with our current recipe:
The custom phases 'fix-qmlwebkit-plugins-rpath and 'patch-inst
On Sat, Jul 21, 2018 at 08:48:22PM +0200, Andreas Enge wrote:
> On Sat, Jul 21, 2018 at 09:38:30PM +0300, Efraim Flashner wrote:
> > I see a new version of Calibre was just pushed to master, does that
> > build as expected?
>
> Yes and no; it builds, but then using it fails with
> ...
> File
>
On Sat, Jul 21, 2018 at 09:38:30PM +0300, Efraim Flashner wrote:
> I see a new version of Calibre was just pushed to master, does that
> build as expected?
Yes and no; it builds, but then using it fails with
...
File
"/gnu/store/brj5xv8zqa1w7byz8b1fz0fd1hmy3kd4-calibre-3.28.0/lib/calibre/calibr
On Sat, Jul 21, 2018 at 08:13:58PM +0200, Andreas Enge wrote:
> On Sat, Jul 21, 2018 at 07:32:03PM +0200, Andreas Enge wrote:
> > So this needs to be corrected with respect to the disappearance of
> > QtWebKitWidgets from Qt, I will have a look now.
>
> This is due to the following commit:
>
> co
On Sat, Jul 21, 2018 at 08:13:58PM +0200, Andreas Enge wrote:
> Interestingly enough, there is a commit in Calibre which claims to work
> on Qt 5.11 compatibility:
>
> https://github.com/kovidgoyal/calibre/commit/68bbec179abc980ebcb3f13854d2e4fd46f4897c
> So the Calibre author apparently has ma
On Sat, Jul 21, 2018 at 07:32:03PM +0200, Andreas Enge wrote:
> So this needs to be corrected with respect to the disappearance of
> QtWebKitWidgets from Qt, I will have a look now.
This is due to the following commit:
commit c0e7a52996edf75a403ef6c454072271fd1c277a
Author: Efraim Flashner
Date:
Hi,
I'm trying to understand why Berlin web API times out[1].
I think the SQlite built in busy handler may block the Fibers scheduler.
We use "PRAGMA busy_timeout = 3;", which is an alternative to
calling sqlite3_busy_timeout(), whose description[2] is:
This routine sets a busy handler t
Hi,
https://berlin.guixsd.org:8081/ times out.
I'm using the exact same config at home to try to reproduce the issue.
Clément
