On Thu, 15 Oct 2015 01:05:11 +0100 Tim Retout <dioc...@debian.org> wrote: > Hello Dominik! > > On 14 October 2015 at 12:33, Dominik George <d.geo...@tarent.de> wrote: > > > As I am now sitting here at my dayjob with resources to get this package > > straight, can you please update me on the current status and what I can > > do to get a working version into Debian real soon? Do we still fix the > > old package, or should I start creating a new package for 2.0.0 to > > replace this? If not, what is left to test and fix to make the package > > fit for sid and then create a backport after migration to testing? > > > > My take on this is not positive, as my understanding now is that phantomjs > upstream itself is under-resourced compared to the scale of the problem > they're tackling. :/ In a similar position at my day job, we are migrating > our test suite from ghostdriver to chromedriver, which is both faster and > maintained by the Chromium team. If you are using a lot of the Javascript > API that phantomjs provides, I can imagine that this would not be possible, > however. > > To fix the package in Debian, you need to get some v2.x version working, > because this is the only route to building with system Qt and webkit. So > far, however, takaki says the git snapshot doesn't compile. >
I also need to do this for $dayjob and will have a go over the next few hours. Please catch me on IRC if there's any special details that I should know. > Because I've found a workaround for $dayjob, I'm not actively working on > this any more, I'm afraid. > Yes, my current workaround is to just use 'xvfb-run karma --browsers Chrome' and be done with it. Much easier than using "drivers", which are usually slightly different from what end-users run, anyhow. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
