You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The gstreamer plugin bbappends on kirkstone-dev (specifically plugins-bad at the moment) are breaking builds with latest YP kirkstone. The reason is similar to the issue that was seen on scarthgap-dev; upstream poky kirkstone is now on 1.20.7 plus a large stack of CVE fix patches, while the bbappends are switching back to a base of 1.20.3. If at all possible, please backport the changes to switch to standalone 1.20.3 gstreamer recipes with PREFERRED_PROVIDER selection from scarthgap-dev to kirkstone-dev. For the moment I am BBMASKing out all the gstreamer plugin bbappends in our AGL build, but this is not ideal since it prevents AGL downstream users from leveraging Renesas's optimizations on our Quillback LTS branch.
The text was updated successfully, but these errors were encountered:
The gstreamer plugin bbappends on kirkstone-dev (specifically plugins-bad at the moment) are breaking builds with latest YP kirkstone. The reason is similar to the issue that was seen on scarthgap-dev; upstream poky kirkstone is now on 1.20.7 plus a large stack of CVE fix patches, while the bbappends are switching back to a base of 1.20.3. If at all possible, please backport the changes to switch to standalone 1.20.3 gstreamer recipes with PREFERRED_PROVIDER selection from scarthgap-dev to kirkstone-dev. For the moment I am BBMASKing out all the gstreamer plugin bbappends in our AGL build, but this is not ideal since it prevents AGL downstream users from leveraging Renesas's optimizations on our Quillback LTS branch.
The text was updated successfully, but these errors were encountered: