Is your feature request related to a problem? Please describe.
We are using docker-pkg-build to build GStreamer packages (with downstream patches) through CLO. We publish the packages to an APT repo in CLO. This APT repo in CLO is used with --extra-repo to resolve Build-dependencies for other projects. We add a qcom suffix to the latest upstream version and publish the debs.
Now I see a scenario where there is a new security release in upstream and the upstream version exceeds the version in CLO APT repository. In this case the Build-Depends will get resolved to the upstream version and build of our project will fail.
Loïc Minier (@lool) has suggested to use APT pinning for installation. This works when we have packages built and published into artifactory.
However we have a case where IMSDK Build-depends on these patched gstreamer debians and there is no option to set priority in docker-pkg-build. Can we add an option to configure this?
Describe the solution you'd like
Additional parameter in docker-pkg-build to set priority to the extra-repo configured.
Additional context
Consider gst-plugins-base1.0 as an example.
Latest upstream version: 1.26.2-1+deb13u1
Qualcomm patched version in CLO APT repo: 1.26.2-1+deb13u1+qcom1
Now if upstream releases 1.26.2-1+deb13u2, it will be preferred to resolve Build-Depends. We want to have an option to set priority along with --extra-repo for this case.
CC: Robie Basak (@basak-qcom)
Is your feature request related to a problem? Please describe.
We are using docker-pkg-build to build GStreamer packages (with downstream patches) through CLO. We publish the packages to an APT repo in CLO. This APT repo in CLO is used with --extra-repo to resolve Build-dependencies for other projects. We add a qcom suffix to the latest upstream version and publish the debs.
Now I see a scenario where there is a new security release in upstream and the upstream version exceeds the version in CLO APT repository. In this case the Build-Depends will get resolved to the upstream version and build of our project will fail.
Loïc Minier (@lool) has suggested to use APT pinning for installation. This works when we have packages built and published into artifactory.
However we have a case where IMSDK Build-depends on these patched gstreamer debians and there is no option to set priority in docker-pkg-build. Can we add an option to configure this?
Describe the solution you'd like
Additional parameter in docker-pkg-build to set priority to the extra-repo configured.
Additional context
Consider gst-plugins-base1.0 as an example.
Latest upstream version: 1.26.2-1+deb13u1
Qualcomm patched version in CLO APT repo: 1.26.2-1+deb13u1+qcom1
Now if upstream releases 1.26.2-1+deb13u2, it will be preferred to resolve Build-Depends. We want to have an option to set priority along with --extra-repo for this case.
CC: Robie Basak (@basak-qcom)