gst-plugins-bad/1.27.50 package update

[octo-sts]

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]

🔢 Build Failed: Dependency Version Mismatch

Dependency gstreamer-1.0 found: NO. Found 1.27.2 but need: '>= 1.27.50'

Build Details

Category	Details
Build System	Meson
Failure Point	meson setup configuration phase - dependency resolution for gstreamer-1.0

Root Cause Analysis 🔍

The build requires GStreamer version >= 1.27.50 but only version 1.27.2 is available in the build environment. The meson build system cannot find a compatible version of the gstreamer-1.0 dependency and fails when attempting to resolve the subproject without a subprojects directory present.

---

🔍 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

• gst-plugins-bad/1.27.2 package update #65522
• gst-plugins-base/1.27.2 package update #65523
• gst-plugins-bad/1.27.2 package update #65522

Suggested Changes

File: gst-plugins-bad.yaml

• version_downgrade at line 3 (package.version)
  Original:

version: "1.27.50"

Replacement:

version: "1.27.2"

Content:

Change package version from 1.27.50 to 1.27.2 to match available GStreamer version

• commit_hash_update at line 52 (pipeline git-checkout expected-commit)
  Original:

expected-commit: 98f0ec4b5dd48b36365e85ad8695e88b4a7d7ec0

Replacement:

expected-commit: 285de3cf1de94b5b370a1af39446a7d1498d7c2c

Content:

Update expected commit hash to match the 1.27.2 tag

Click to expand fix analysis

Analysis

The similar fixes show a consistent pattern: when GStreamer dependency version mismatches occur, the solution is to update the package version and corresponding expected-commit hash to match the available GStreamer version in the build environment. All three examples show upgrades from version 1.27.1 to 1.27.2 with commit hash updates from 1fa56616fb2684d505091213ae898887309ed3a0 to 285de3cf1de94b5b370a1af39446a7d1498d7c2c. The current failure indicates that version 1.27.50 requires GStreamer >= 1.27.50, but only 1.27.2 is available, suggesting the package version needs to be downgraded to match the available GStreamer version in the build environment.

Click to expand fix explanation

Explanation

The current build failure occurs because the package is trying to build version 1.27.50 which requires GStreamer >= 1.27.50, but the build environment only has GStreamer 1.27.2 available. The similar fixes show that the solution is to align the package version with the available GStreamer version in the build environment. By downgrading the package version from 1.27.50 to 1.27.2 and updating the corresponding git commit hash, the build will use a version that is compatible with the available GStreamer 1.27.2 dependency. The commit hash 285de3cf1de94b5b370a1af39446a7d1498d7c2c corresponds to the 1.27.2 tag as evidenced by the similar fixes. This approach ensures version compatibility between gst-plugins-bad and the core GStreamer framework.

Click to expand alternative approaches

Alternative Approaches

• Upgrade the GStreamer packages in the build environment to version 1.27.50 or higher to match the current package version requirement
• Wait for GStreamer 1.27.50 to be available in the Wolfi package repository and then rebuild
• Modify the meson configuration to use a lower minimum GStreamer version requirement if the 1.27.50 features are not critically needed

---

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