Re: [PATCH 1/1] fix(dpkg-build): deploy debs via shared sstate dir

["'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>]

On 29.07.26 13:18, Felix Moessbauer wrote:
> The built debs were stored in a WORKDIR-internal plaindir and consumed
> from there by do_deploy_deb. do_deploy_deb is a task that mutates
> the external isar-apt repository and can therefore never be sstate
> cached, so it always runs and relies on the plaindir being present on
> disk.
> 
> When do_dpkg_build is served from the sstate cache, that WORKDIR-internal
> plaindir is not guaranteed to be materialized (e.g. when the task is
> covered via hash equivalence without a setscene restore). do_deploy_deb
> then runs against an empty deploy dir, passes an unexpanded glob to
> dpkg-deb and aborts the build.

Not getting it: why is dpkg_build_setscene not properly filling
DEPLOYDIR then? We told it that the build will fill it, it picked things
up from there for caching, and it should refill it when it skips the task.

> 
> Fix it by deploying the debs into a shared, sstate-tracked DEPLOY_DIR_DEB
> via sstate-inputdirs/sstate-outputdirs.

This is creating yet another copy of the generated deb files in our
build dirs. Sounds inefficient, specifically when we have larger artifacts.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/0aebf31c-d213-4805-9cbb-d0d106024f83%40siemens.com.