FYI, DT has upgraded yanglint to 2.1.30, and that solves the problems that were raised at NETMOD at 122. That said, it does add support for additional NEW checks.
A question came up about why didn’t DT move to yanglint 3.7.8. DT tries, as best they can, to track the latest stable Debian packages. Today, that package is 2.1.30. There is a bleeding edge package for 3.7.8, but it is not yet stable. If there is a strong need for YL 3.7.8, I’ll consider creating my own package to see if the tools team will take it. But for now, the immediate problem seems to be solved. Joe From: Joe Clarke (jclarke) <[email protected]> Date: Wednesday, March 19, 2025 at 02:46 To: Joe Clarke (jclarke) <[email protected]>, NETMOD Group <[email protected]> Subject: Re: DataTracker and module compilation I opened https://github.com/ietf-tools/datatracker/issues/8701 for this. Joe From: Joe Clarke (jclarke) <[email protected]> Date: Wednesday, March 19, 2025 at 02:42 To: NETMOD Group <[email protected]> Subject: [netmod] DataTracker and module compilation I’ve been poking at this from a YANG Catalog perspective. It seems like one of the main issues is that the tools are a bit old. If I run yanglint against the current module with the same ieee-dot1q-types, I do not get the warnings. I think tools needs to update yanglint, and this problem will go away. I can open an issue in the DT GitHub. And speaking of the module/draft that triggered this investigation, can the authors of draft-ietf-netmod-sub-intf-vlan-model update their XML to set the “type” of the two YANG modules’ sourcecodes to ‘type=”yang”’? Then the module will get extracted into YANG Catalog. Joe
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
