ietf-tools / ietf-tools/draftforge

`xml2rfc` based exports fails with `src` attribute

Open
#40 2 comments 0 reactions 1 assignee View on GitHub

@NGPixel is already working on this.

Since Apr 11, 2026.

bug
Dominant language
JavaScript
Stars
12
Forks
8
PR merge metrics
No merged PRs in 30d

Description

Dear draftforge developers,

First of all thanks a lot for the development of this tool, really comprehensive and helps a lot!

Description

I am experiencing a minor issue with the embedded export tools: external files referenced via relative paths (like YANG modules in the root or in a yang/ subdirectory) are not copied over to the temp folder from where commands are executed. This causes xml2rfc to fail because it cannot resolve the relative paths inside the temporary location.

Error for reference:

Command failed: xml2rfc --allow-local-file-access --v3 --bom --id-reference-base-url="https://datatracker.ietf.org/doc/html/" --id-is-work-in-progress --text -o "/home/taarole8/git-repos/draft-netana-nmop-message-broker-bmp-telemetry-message/draft-netana-nmop-message-broker-bmp-telemetry-message-00.txt" "/tmp/draftforge-zGqCcS/1769759774921.xml" /tmp/draftforge-zGqCcS/1769759774921.xml(13): Warning: Setting consensus="true" for IETF STD document (this is not the schema default, but is the only value permitted for this type of document) /tmp/draftforge-zGqCcS/1769759774921.xml(64): Warning: The document date (2026-01-26) is more than 3 days away from today's date /tmp/draftforge-zGqCcS/1769759774921.xml(2360): Error: Expected a file at '/tmp/draftforge-zGqCcS/ietf-bmp-bgp-rib-entry@2026-01-26.yang', but no such file exists Not creating output file due to errors (see above) Unable to complete processing /tmp/draftforge-zGqCcS/1769759774921.xml

Running xml2rfc from the terminal works.

Is there a workaround to force other files to be copied to the temp dir?

Cheers,
Leonardo

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.