Skip to content

docker_deb_build: add watch file support for prebuilt binary packages#40

Open
Keerthi Gowda (keerthi-go) wants to merge 1 commit into
mainfrom
dev/watchfilesupport
Open

docker_deb_build: add watch file support for prebuilt binary packages#40
Keerthi Gowda (keerthi-go) wants to merge 1 commit into
mainfrom
dev/watchfilesupport

Conversation

@keerthi-go

Copy link
Copy Markdown
Contributor

Summary

For packages that use debian/watch to fetch a prebuilt upstream tarball from Artifactory (e.g. pkg-qcom-fastcv-binaries), the local build path had no mechanism to obtain the orig tarball before building.

Changes

When debian/watch exists and references qartifactory, run uscan --download-current-version inside the container to fetch the orig tarball into /workspace, then use gbp buildpackage -S --git-no-create-orig to produce the .dsc without gbp overwriting the fetched tarball. Pass the .dsc to sbuild for the binary build.

Backward compatibility

  • Packages with debian/watch pointing to a git forge (GitHub etc.) → unaffected, qartifactory guard keeps them on the normal gbp path
  • Packages using upstream.conf (PREBUILT_MODE=true) → unaffected
  • Native packages → unaffected
  • --skip-gbp path → unaffected

Local usage

No pre-download step needed:

python3 docker_deb_build.py \
  --source-dir /path/to/pkg-qcom-fastcv-binaries \
  --output-dir /tmp/out \
  --distro resolute

Related

Mirrors the same change made to qcom-build-utils .github/actions/build_package/action.yml.

For packages that use debian/watch to fetch a prebuilt upstream tarball
from Artifactory, the local build path had no mechanism to obtain the
orig tarball before building.

When debian/watch exists and references qartifactory, run uscan
--download-current-version inside the container to fetch the orig
tarball into /workspace, then use gbp buildpackage -S
--git-no-create-orig to produce the .dsc without gbp overwriting the
fetched tarball. Pass the .dsc to sbuild for the binary build.

Packages with debian/watch pointing to a git forge (GitHub etc.) are
unaffected — the qartifactory guard keeps them on the normal gbp orig
creation path. Packages using upstream.conf and native packages are
also unaffected.

Mirrors the same change made to qcom-build-utils build_package action.

Signed-off-by: Keerthi Gowda <kbalehal@qti.qualcomm.com>
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.

1 participant