debian: prefer libyang3 over libyang2 when building deb packages

[Jafaral]

No description provided.

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[Jafaral]

@greptile review

[Jafaral]

@Mergifyio backport dev/10.6

[mergify]

backport dev/10.6

✅ Backports have been created

Details

• #20873 debian: prefer libyang3 over libyang2 when building deb packages (backport #20871) has been created for branch dev/10.6

[greptile-apps]

Greptile Summary

This PR swaps the order of the libyang alternative build dependencies in debian/control so that libyang-dev (>= 3.0.3) (libyang3) is preferred over libyang2-dev (>= 2.1.128) when building Debian packages. In Debian's dependency resolution, the first alternative in a | list is the preferred one.

• Reorders libyang-dev (>= 3.0.3) | libyang2-dev (>= 2.1.128) to prefer libyang3, consistent with the project's direction toward libyang3 support
• Fixes a minor spacing inconsistency: ( >= 3.0.3) is now (>= 3.0.3), matching the style used by all other version constraints in the file
• Both versions remain supported as alternatives, so no backwards compatibility is broken
• The configure.ac build system already supports both libyang2 and libyang3 via PKG_CHECK_MODULES([LIBYANG], [libyang >= 2.1.128])

Confidence Score: 5/5

• This PR is safe to merge — it's a minimal, well-understood change to dependency ordering in Debian packaging metadata.
• The change is a single-line reordering of alternative build dependencies with no functional risk. Both libyang2 and libyang3 remain supported. The change follows established Debian packaging conventions and is consistent with the project's existing build system support for both libyang versions.
• No files require special attention.

Important Files Changed

Filename	Overview
debian/control	Swaps the order of libyang alternative build dependencies to prefer libyang3 (libyang-dev >= 3.0.3) over libyang2 (libyang2-dev >= 2.1.128). Also fixes a minor spacing inconsistency in the version constraint parentheses.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Debian Package Build] --> B{Resolve libyang\nbuild dependency}
    B -->|Before PR| C[Try libyang2-dev >= 2.1.128\nfirst]
    C -->|Not available| D[Fall back to\nlibyang-dev >= 3.0.3]
    B -->|After PR| E[Try libyang-dev >= 3.0.3\nfirst]
    E -->|Not available| F[Fall back to\nlibyang2-dev >= 2.1.128]
    C --> G[Build FRR]
    D --> G
    E --> G
    F --> G

Loading

_{Last reviewed commit: f054175}

[mwinter-osr]

Looks good. sbuild prefers first option