Skip to content

Debian Trixie migration for sonic-gnmi#649

Closed
amrutasali wants to merge 1 commit intosonic-net:masterfrom
amrutasali:trixie_migration_for_sonic_gnmi
Closed

Debian Trixie migration for sonic-gnmi#649
amrutasali wants to merge 1 commit intosonic-net:masterfrom
amrutasali:trixie_migration_for_sonic_gnmi

Conversation

@amrutasali
Copy link
Copy Markdown

Why I did it -
Required for sonic-net/SONiC#2169.
Migrate sonic-gnmi from Debian Bookworm to Debian Trixie.

How I did it -
Switched Azure Pipelines/build templates to Trixie (sonic-slave-trixie, Trixie artifacts, Trixie wheel paths).
Added Trixie-specific dependency handling, including libpcre3 packages required by libyang.
Updated test-job Microsoft repo path from Debian 12 to Debian 13.
Bumped Go version to 1.24.4 and refreshed go.mod/go.sum for toolchain compatibility.
Fixed Go 1.24 format-string/vet issues across gNOI/gNSI/auth/dbus/server code paths.
Included minor test cleanup and a //go:noinline safeguard for GetCrlUrls.

How to verify it -
sonic-gnmi builds successfully with Trixie pipeline/container flow (amd64 and arm64).
Dependency install stage succeeds with Trixie libpcre3/libyang/libnl artifacts.
Unit tests pass with Go 1.24.4.
Basic gNMI/gNOI sanity checks work on a recent SONiC image.

Dependent/Related PRs:
sonic-net/sonic-buildimage#26548,
sonic-net/sonic-mgmt-common#211,
sonic-net/sonic-mgmt-framework#158.

Signed-off-by: Amruta Sali <amruta_sali@dell.com>
@mssonicbld
Copy link
Copy Markdown
Contributor

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

@amrutasali
Copy link
Copy Markdown
Author

A similar PR got merged - #645

@amrutasali amrutasali closed this Apr 14, 2026
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