You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Toolchain pulls reference.RFC.*.xml files from Internet. On my system it requires using Web proxy , defined in env vars HTTP_PROXY, HTTPS_PROXY and such.
Somehow, those settings are ignored:
. . .
/Users/ur20980/.cache/xml2rfc/reference.RFC.4306.xml: renewing (stale by 10.6 days) from https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4306.xml
/Users/ur20980/.cache/xml2rfc/reference.RFC.2459.xml: renewing (stale by 10.6 days) from https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2459.xml
/Users/ur20980/.cache/xml2rfc/reference.RFC.2119.xml: renewing (stale by 10.6 days) from https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml
/Users/ur20980/.cache/xml2rfc/reference.RFC.8174.xml: renewing (stale by 10.6 days) from https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml
/Users/ur20980/.cache/xml2rfc/reference.RFC.5247.xml: renewing (stale by 10.6 days) from https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5247.xml
make: *** [draft-uri-lamps-pquake.xml] Error 127
make: *** Deleting file `draft-uri-lamps-pquake.xml'
Of course, one workaround that I use is manually downloading those RFCs and placing them in the expected dir. But it would be much less irritating if the toolchain could manage this task by itself.
The text was updated successfully, but these errors were encountered:
I'm not seeing in the above any error messages related to the fetches; the messages look like a normal trace of fetching the I-Ds.
I would expect messages like "*** Can't get with persistent HTTP: Failed to open TCP connection" if you can't use HTTP directly.
(It doesn't help that I don't know whether you are using KRAMDOWN_PERSISTENT -- I-D-template normally does.)
Anyway, all looks normal so far, and I don't know where the error 127 then comes in.
In any case, I have found a way to explicitly feed the environment variables to net/http/persistent, and I will release a new revision presently.
See martinthomson/i-d-template#472
Of course, one workaround that I use is manually downloading those RFCs and placing them in the expected dir. But it would be much less irritating if the toolchain could manage this task by itself.
The text was updated successfully, but these errors were encountered: