Hi Tomasz, > unfortunately you cannot (generally speaking) expect to be able to > build new versions of nghttp2 on jessie.
Yes I expected it ;) and I did it (almost) easily: - install the smallest possible jessie - add deb-src from stretch - apt-get install build-essential devscripts - apt-get source nghttp2=1.7.0-1 - apt-get build-dep nghttp2 (says it miss libspdylay) - apt-get install libspdylay from a personal backport (this one get backported fine from stretch) - apt-get build-dep nghttp2 (now build dependencies get installed fine) - cd nghttp2-* - debuild It fails with the initial error message I sent you (missing rubydomain) - wget http://ftp.de.debian.org/debian/pool/main/s/sphinxcontrib-rubydomain/python-sphinxcontrib.rubydomain_0.1~dev-20100804-1_all.deb (from stretch) - dpkg -i python-sphinxcontrib.rubydomain_0.1~dev-20100804-1_all.deb (get installed fine, which means this package can be backported as-it-is to Jessie ;), it has no specific dependency ) - debuild (of nghttp2 1.7 on Jessie) Build successfull As a result, a backport of nghttp2 to jessie is doable (no need of python-sphinxcontrib.rubydomain at INSTALL time, it's just a BUILD dependency) It needs libspdylay7 backported too though. > (you will have to remove libspdylay-dev from Build-Depends too). > > At some point I was considering backporting nghttp2 to jessie-backports. > If there is interest, I can do it. You can find those packages (libspdylay, nghttp2) built for Jessie on deb http://debian.octopuce.fr/octopuce experimental main And yes, nghttp2 is building fine on a sid machine without python-sphinxcontrib.rubydomain So yes, this bug only apply to those who want to build for jessie. regards, bs://
