Re: [Debian-science-sagemath] Help needed to backport jupyter-notebook (Was: Help needed for backporting node-esprima (Was: Backporting sagemath))
Andreas Tille:
> [..] Now I get:
>
>
> ...
> module 29: nodejs ../../fakewebpack-postprocess.js ./node_modules/font-awesome/fonts/fontawesome-webfont.woff2 ../../fakewebpack/docs.modules
> Traceback (most recent call last):
> File "./fakewebpack-generate.py", line 80, in <module>
> sys.exit(main(*sys.argv[1:]))
> File "./fakewebpack-generate.py", line 61, in main
> cwd=srcdir).decode("utf-8")
> File "/usr/lib/python3.4/subprocess.py", line 620, in check_output
> raise CalledProcessError(retcode, process.args, output=output)
> subprocess.CalledProcessError: Command '['nodejs', '../../fakewebpack-postprocess.js', './node_modules/font-awesome/fonts/fontawesome-webfont.woff2', '../../fakewebpack/docs.modules']' returned non-zero exit status 1
> fakewebpack.mk:55: recipe for target 'fakewebpack-build/docs.stamp' failed
> make[2]: *** [fakewebpack-build/docs.stamp] Error 1
> ...
>
> and to create the javascript backtrace:
>
> /build/ipywidgets-5.2.2/debian/fakewebpack-unpacked/node-libs-browser# nodejs ../../fakewebpack-postprocess.js ./node_modules/font-awesome/fonts/fontawesome-webfont.woff2 ../../fakewebpack/docs.modules
> fs.js:549
> return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
> ^
>
> Error: ENOENT: no such file or directory, open './node_modules/font-awesome/fonts/fontawesome-webfont.woff2'
> at Error (native)
> at Object.fs.openSync (fs.js:549:18)
> at Object.fs.readFileSync (fs.js:397:15)
> at Object.<anonymous> (/build/ipywidgets-5.2.2/debian/fakewebpack-postprocess.js:193:19)
> at Module._compile (module.js:409:26)
> at Object.Module._extensions..js (module.js:416:10)
> at Module.load (module.js:343:32)
> at Function.Module._load (module.js:300:12)
> at Function.Module.runMain (module.js:441:10)
> at startup (node.js:139:18)
>
>
> Do you have any further hints for this packaging magic? ;-)
>
It looks like font-awesome 4.2.0 contains slightly different files from 4.7.0. Perhaps it would be easier to backport 4.7.0 rather than trying to continue with 4.2.0. I should have mentioned this in my last email as well, but I forgot.
$ apt-cache policy fonts-font-awesome
fonts-font-awesome:
Installed: 4.7.0~dfsg-1
Candidate: 4.7.0~dfsg-1
Version table:
4.7.0~dfsg-2 100
100 ftp://ftp.de.debian.org/debian experimental/main amd64 Packages
100 ftp://ftp.de.debian.org/debian experimental/main i386 Packages
*** 4.7.0~dfsg-1 990
990 ftp://ftp.de.debian.org/debian testing/main amd64 Packages
990 ftp://ftp.de.debian.org/debian testing/main i386 Packages
300 ftp://ftp.de.debian.org/debian unstable/main amd64 Packages
300 ftp://ftp.de.debian.org/debian unstable/main i386 Packages
100 /var/lib/dpkg/status
X
--
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git
Reply to: