Esko Dijk <[email protected]> wrote: > Noticed a minor typo in the name of the .yang file in this line:
> <CODE BEGINS> file"[email protected]"
> That should be:
> <CODE BEGINS> file"[email protected]"
Okay, fixed that in my copy.
> (https://datatracker.ietf.org/doc/draft-ietf-anima-rfc8366bis/).
> While pyang 2.7.1 validates ok, yanglint 2.1.30 does not - see
> below the errors.
My memory is that yanglint is unable to deal with sx:structure, and so I
haven't even tried lately.
> Bumping the YANG module date to say @2025-12-18 is something we
> could try but most likely it won't resolve the issue. This would
> force yanglint to really get the latest version of the module. It
> seems quicker to just try run yanglint locally on the files.
I'm happy to push the date multiple times. That's in the Makefile.
I picked today for now.
Let's do it again *after* the AD review, setting it to the date it does IESG
telechat.
(We'll know that before the actual telechat day, so the contents can be
Hmm. The .sid files have the module-revision in the filename.
Is there a reason to do that? I don't think so.
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
