Skip to content

Fix compatibility with the most recent develop upstream - #175

Open
jktjkt wants to merge 9 commits into
CESNET:masterfrom
jktjkt:fix/build-with-develop
Open

jktjkt wants to merge 9 commits into
CESNET:masterfrom
jktjkt:fix/build-with-develop

Conversation

@jktjkt

@jktjkt jktjkt commented Sep 23, 2026

Copy link
Copy Markdown
  • one change in headers
  • different number of compile callback validations for extensions

This needs #173 and #174.

jktjkt and others added 9 commits September 23, 2026 20:00
Due to the way how the tests runners and linters are set up, when
`test_a.py` imported `test_b`, it would pass during regular test
execution and fail with pylint. That ain't good.

Signed-off-by: Jan Kundrát <[email protected]>
Co-authored-by: Claude Sonnet 5 <[email protected]>
Upstream libyang now unconditionally needs certain core YANG modules,
and they are not available as builtins in the library. Load them via the
usual lookups from disk instead.

Since context creation without access to on-disk data is now broken, the
tests which excercie this path have to first change to loading "a
minimal context" with file lookup enabled, and then disable this
feature via a newly wrapped function.

Signed-off-by: Jan Kundrát <[email protected]>
Co-authored-by: Claude Sonnet 5 <[email protected]>
...to the latest that we're testing against.

Signed-off-by: Jan Kundrát <[email protected]>
And I have to add this line here just to make the CI happy, even though
everything is in the first line. Oh well.

Signed-off-by: Jan Kundrát <[email protected]>
And I have to type stuff here just to make CI happy, even though the
subject oneliner above has all the required info. Oh well.

Co-authored-by: Claude Sonnet 5 <[email protected]>
Signed-off-by: Jan Kundrát <[email protected]>
And a placeholder sentence to make the linter happy.

Signed-off-by: Jan Kundrát <[email protected]>
Since upstream commit
CESNET/libyang@b6ccfc9, `libyang.h` no
longer pulls in `plugins.h`, and therefore `lyplg_add_extension_plugin`
was not declared properly.

Co-authored-by: Claude Sonnet 5 <[email protected]>
Signed-off-by: Jan Kundrát <[email protected]>
I do not think that this test tests much, but hey, it's there, so let's
adapt to how the upstream libyang actually behaves and to what it calls
now.

Signed-off-by: Jan Kundrát <[email protected]>
...so that we actually enforce something that we test against.

Signed-off-by: Jan Kundrát <[email protected]>
@jktjkt
jktjkt force-pushed the fix/build-with-develop branch from e773ef3 to 685a471 Compare September 23, 2026 19:03
@samuel-gauthier samuel-gauthier self-assigned this Oct 16, 2026
@samuel-gauthier

Copy link
Copy Markdown
Collaborator

Hi, thanks a lot for your work. Sorry for the delay in reviewing; as usual, I don't have much time allocated for this.
I will take care of this as soon as I can, including 173 and 174, probably by the end of next week; at the latest, the following week.
Seeing your commit logs, I understand you don't like how the linter checks them, but this is how we want to work in this repository. We find a lot of value in meaningful commit logs and trailers, so I will reword your commits.
Also, we only integrate with the master branch (which recently caught up with devel, so your fixes will be reviewed), as we can not afford to manage two branches, especially the devel branch that moves a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants