Skip to content

Conversation

@octo-sts
Copy link
Contributor

@octo-sts octo-sts bot commented Dec 9, 2025

Commit: 98f0ec4b5dd48b36365e85ad8695e88b4a7d7ec0

Note: If you need to make manual changes to this PR, apply the skip:staging-update-bot label so the reconciler won't overwrite them.

@octo-sts octo-sts bot added automated pr gst-libav request-version-update request for a newer version of a package labels Dec 9, 2025
@octo-sts
Copy link
Contributor Author

octo-sts bot commented Dec 9, 2025

🔢 Build Failed: Dependency Version Mismatch

Dependency gstreamer-1.0 found: NO. Found 1.27.2 but need: '>= 1.27.50' - Subproject gstreamer is buildable: NO - Attempted to resolve subproject without subprojects directory present.

Build Details

Category Details
Build System meson
Failure Point meson setup during configure step

Root Cause Analysis 🔍

The build requires GStreamer version >= 1.27.50 but only version 1.27.2 is available in the system. Additionally, meson attempted to fallback to a subproject but failed because no subprojects directory is present in the build environment.


🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Similar PRs with fixes

Suggested Changes

File: gstreamer.yaml

  • version_update at line 3 (package.version)
    Original:
version: "1.27.2"

Replacement:

version: "1.27.50"

Content:

Update GStreamer core version to 1.27.50
  • commit_hash_update (pipeline.git-checkout.expected-commit)
    Original:
expected-commit: 285de3cf1de94b5b370a1af39446a7d1498d7c2c

Replacement:

expected-commit: 98f0ec4b5dd48b36365e85ad8695e88b4a7d7ec0

Content:

Update expected commit hash to match version 1.27.50

File: gst-plugins-base.yaml

  • version_update at line 3 (package.version)
    Original:
version: "1.27.2"

Replacement:

version: "1.27.50"

Content:

Update GStreamer plugins base version to 1.27.50
  • commit_hash_update (pipeline.git-checkout.expected-commit)
    Original:
expected-commit: 285de3cf1de94b5b370a1af39446a7d1498d7c2c

Replacement:

expected-commit: 98f0ec4b5dd48b36365e85ad8695e88b4a7d7ec0

Content:

Update expected commit hash to match version 1.27.50

File: gst-plugins-bad.yaml

  • version_update at line 3 (package.version)
    Original:
version: "1.27.2"

Replacement:

version: "1.27.50"

Content:

Update GStreamer plugins bad version to 1.27.50
  • commit_hash_update (pipeline.git-checkout.expected-commit)
    Original:
expected-commit: 285de3cf1de94b5b370a1af39446a7d1498d7c2c

Replacement:

expected-commit: 98f0ec4b5dd48b36365e85ad8695e88b4a7d7ec0

Content:

Update expected commit hash to match version 1.27.50
Click to expand fix analysis

Analysis

The similar fixes show a consistent pattern: GStreamer version mismatches are resolved by updating the package version to meet the minimum requirement. In all three examples, the fixes involved bumping the version number from an older version to a newer one that satisfies the dependency requirements. Fix #0 and #1 both updated from 1.27.1 to 1.27.2, and Fix #2 updated from 1.24.11 to 1.25.1. Additionally, the fixes updated the expected-commit hash to match the new version tag. The current failure shows gst-libav requires GStreamer >= 1.27.50 but only 1.27.2 is available, indicating the GStreamer core packages need to be updated to version 1.27.50.

Click to expand fix explanation

Explanation

The build failure occurs because gst-libav version 1.27.50 requires GStreamer >= 1.27.50, but the currently available GStreamer packages (gstreamer-dev, gst-plugins-base-dev) are only at version 1.27.2. The dependency chain requires updating the entire GStreamer ecosystem to version 1.27.50. Based on the pattern from similar fixes, this requires updating the core GStreamer package and all related plugin packages to the same version (1.27.50) and updating their corresponding git commit hashes. The gst-libav package is already correctly configured for version 1.27.50 with the proper commit hash (98f0ec4b5dd48b36365e85ad8695e88b4a7d7ec0), so the other GStreamer packages need to be brought up to this same version and commit to resolve the dependency mismatch.

Click to expand alternative approaches

Alternative Approaches

  • Downgrade gst-libav to match the available GStreamer version (1.27.2), but this would go against Wolfi's principle of keeping packages up to date
  • Add build flags to disable strict version checking, but this could lead to runtime compatibility issues
  • Build GStreamer from source as a subproject within gst-libav, but this would significantly increase build complexity and time

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.

@octo-sts octo-sts bot added the ai/skip-comment Stop AI from commenting on PR label Dec 9, 2025
@AmberArcadia AmberArcadia self-assigned this Dec 15, 2025
@octo-sts octo-sts bot added bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. manual/review-needed staging-approver-bot/manual-review-needed approver-bot/manual-review-needed labels Dec 16, 2025
@AmberArcadia AmberArcadia requested a review from a team December 16, 2025 18:21
@OddBloke OddBloke merged commit 39d1f1b into main Dec 16, 2025
24 checks passed
@OddBloke OddBloke deleted the staging-update-bot/gst-libav.yaml branch December 16, 2025 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai/skip-comment Stop AI from commenting on PR approver-bot/manual-review-needed automated pr bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. gst-libav manual/review-needed request-version-update request for a newer version of a package staging-approver-bot/manual-review-needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants