Repository navigation
Bump cpp-example-collection from 7abd4b9 to 90f13f1 - #293
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [cpp-example-collection](https://github.com/livekit-examples/cpp-example-collection) from `7abd4b9` to `90f13f1`. - [Commits](livekit-examples/cpp-example-collection@7abd4b9...90f13f1) --- updated-dependencies: - dependency-name: cpp-example-collection dependency-version: 90f13f11a081281924f1bffc5d2eda4182e5e544 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
| @@ -1 +1 @@ | |||
| Subproject commit 7abd4b97aebd33a681cfbbed9b739fdc5c2c17e3 | |||
| Subproject commit 90f13f11a081281924f1bffc5d2eda4182e5e544 | |||
There was a problem hiding this comment.
🔴 Ubuntu 22.04 examples use incompatible SDK
On Ubuntu 22.04, _lk_detect_host selects the 24.04 bundle despite a published 22.04 bundle. Its newer glibc dependencies can prevent the examples from running.
Learn more
The example collection downloads an SDK release when LIVEKIT_LOCAL_SDK_DIR is unset. Its updated _lk_detect_host treats every Linux host as Ubuntu 24.04, while the SDK release workflow builds distinct 22.04 and 24.04 artifacts. Ubuntu 22.04 users therefore receive an artifact built against a newer system libc, so compiling or launching the examples can fail. In-tree SDK builds supply a local SDK and do not exercise this download path.
Example: On an Ubuntu 22.04 x64 machine, configuring the examples without LIVEKIT_LOCAL_SDK_DIR requests livekit-sdk-ubuntu-24.04-x64-<version>.tar.gz, not the available livekit-sdk-ubuntu-22.04-x64-<version>.tar.gz. The resulting binary can fail to load with a missing GLIBC version.
Recommended fix: Update _lk_detect_host in the example collection to select the matching Ubuntu release for Linux hosts, including a clear failure for unsupported hosts. Keep its triple names aligned with the release matrix.
Was this helpful? React with 👍 or 👎 to provide feedback.
Bumps cpp-example-collection from
7abd4b9to90f13f1.Commits
90f13f1Update to newer linux artifact (#24)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)