Skip to main content
When using the same workspace for base and custom builds, you can observe the following signatures: 
ERROR: <package>-<version> do_packagedata_setscene: QA Issue: Package
version for package wpa-supplicant-src went backwards which would break
package feeds (from 0:2.10.qcom-r0 to 0:2.10-r0) [version-going-backwards]
For example: 
ERROR: wpa-supplicant-2.10-r0 do_packagedata_setscene: QA Issue: Package
version for package wpa-supplicant-src went backwards which would break
package feeds (from 0:2.10.qcom-r0 to 0:2.10-r0) [version-going-backwards]
This quality assurance (QA) issue occurs with the custom variant of recipes in the meta-qcom-hwe layer. For example, the wpa_supplicant recipe has its version set as 2.10.qcom. The .qcom in the version indicates that the recipes build a different source tree compared to the recipe in poky/meta/recipes-connectivity. When you build the base variant after building the custom variant, the BitBake build system detects that the version is regressing from wpa-supplicant_2.10 to wpa-supplicant-2.10.qcom. BitBake warns that this regression could cause problems if you use it for creating package feeds. To avoid this QA issue or to set up package feeds without problems, do any of the following:
  • Create different workspaces for base and custom build variants.
  • In the same workspace, create separate build directories as follows:
    For build variantCommand to create a build directoryCreated build directory
    base
    • MACHINE=qcs9100-ride-sx DISTRO=qcom-wayland QCOM_SELECTED_BSP=base \
    • source setup-environment build-qcom-wayland-base
    		/<workspace>/Qualcomm_Linux/build-qcom-wayland-base/
    custom
    • MACHINE=qcs9100-ride-sx DISTRO=qcom-wayland QCOM_SELECTED_BSP=custom \
    • source setup-environment build-qcom-wayland-custom
    		/<workspace>/Qualcomm_Linux/build-qcom-wayland-custom/