Skip to content

Revert "qcom-multimedia-image: Add gst-plugins-imsdk"#168

Merged
lumag merged 1 commit intomainfrom
revert-149-enable_imsdk
Feb 16, 2026
Merged

Revert "qcom-multimedia-image: Add gst-plugins-imsdk"#168
lumag merged 1 commit intomainfrom
revert-149-enable_imsdk

Conversation

@lumag
Copy link
Contributor

@lumag lumag commented Feb 16, 2026

Reverts #149, it broke qcom-armv7a builds with:

ERROR: Nothing RPROVIDES 'gst-plugins-imsdk-oss-meta' (but /work/build/../meta-qcom-distro/recipes-products/images/qcom-multimedia-image.bb RDEPENDS on or otherwise requires it)\n", 'gst-plugins-imsdk RPROVIDES gst-plugins-imsdk-oss-meta but was skipped: incompatible with machine qcom-armv7a (not in COMPATIBLE_MACHINE)\n', "ERROR: Required build target 'qcom-multimedia-image' has no buildable providers.\n", "Missing or unbuildable dependency chain was: ['qcom-multimedia-image', 'gst-plugins-imsdk-oss-meta

Signed-off-by: Dmitry Baryshkov dmitry.baryshkov@oss.qualcomm.com

@lumag
Copy link
Contributor Author

lumag commented Feb 16, 2026

cc @Raja-Ganapathi-Busam

Reverts #149, it broke qcom-armv7a builds with:

ERROR: Nothing RPROVIDES 'gst-plugins-imsdk-oss-meta' (but
/work/build/../meta-qcom-distro/recipes-products/images/qcom-multimedia-image.bb
RDEPENDS on or otherwise requires it)\n", 'gst-plugins-imsdk RPROVIDES
gst-plugins-imsdk-oss-meta but was skipped: incompatible with machine
qcom-armv7a (not in COMPATIBLE_MACHINE)\n', "ERROR: Required build
target 'qcom-multimedia-image' has no buildable providers.\n", "Missing
or unbuildable dependency chain was: ['qcom-multimedia-image',
'gst-plugins-imsdk-oss-meta

Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
@lumag lumag force-pushed the revert-149-enable_imsdk branch from 49aa3ec to 6f46fc7 Compare February 16, 2026 17:21
@lumag
Copy link
Contributor Author

lumag commented Feb 16, 2026

Force-merging to unbreak builds.

@lumag lumag merged commit 70288f7 into main Feb 16, 2026
2 checks passed
@ndechesne
Copy link
Contributor

why was it not caught by the PR CI?

@lumag
Copy link
Contributor Author

lumag commented Feb 16, 2026

why was it not caught by the PR CI?

Because it's qcom-distro, which is not being CI'd.

@quaresmajose
Copy link

quaresmajose commented Feb 16, 2026

why was it not caught by the PR CI?

Because it's qcom-distro, which is not being CI'd.

It was caught in the meta-qcom-distro/139 CI https://github.com/qualcomm-linux/meta-qcom-distro/actions/runs/22067575109/job/63775945587

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.

4 participants

Comments