| 2022-08-31 20:39:03 |
M. Vefa Bicakci |
description |
Brief Description
-----------------
When a Debian-based StarlingX package makes use of a "dl_hook" and when the dl_files and src_files entries in the meta_data.yaml do /not/ take into account all of the files fed into the build system, then using "build-pkgs -c -p mypkg" does not regenerate the *.dsc and the *.orig.tar.gz files for the package, which may cause older versions of the "untracked" source files to be used.
In these cases, the only way to ensure a fresh build is to remove the *.dsc file from "/localdisk/loadbuild/<project>/<"std"|"rt">/<package>/*.dsc".
I have prepared a fix for this shortcoming, which is more easily triggered with some of my kernel packaging changes. This is why I am opening this bug.
Severity
--------
Minor: This is a build issue affecting packages whose meta_data.yaml files have a "dl_hook" entry and whose input files are only partially covered by meta_data.yaml.
I did not acquire the number of packages matching this criteria, but my thinking is that this is a minor issue, especially as the official nightly builds are always non-incremental builds (i.e., nightly builds always build from scratch and hence are not affected by this issue).
Note
----
I already have a patch for this, and I am opening this bug report as a placeholder to refer to. This is why this template is incomplete. |
Brief Description
-----------------
When a Debian-based StarlingX package makes use of a "dl_hook" and when the dl_files and src_files entries in the meta_data.yaml do /not/ take into account all of the files fed into the build system, then using "build-pkgs -c -p mypkg" does not regenerate the *.dsc and the *.orig.tar.gz files for the package, which may cause older versions of the "untracked" source files to be used.
In these cases, the only way to ensure a fresh build is to remove the *.dsc file from "/localdisk/loadbuild/<user>/<project>/<"std"|"rt">/<package>/*.dsc".
I have prepared a fix for this shortcoming, which is more easily triggered with some of my kernel packaging changes. This is why I am opening this bug.
Severity
--------
Minor: This is a build issue affecting packages whose meta_data.yaml files have a "dl_hook" entry and whose input files are only partially covered by meta_data.yaml.
I did not acquire the number of packages matching this criteria, but my thinking is that this is a minor issue, especially as the official nightly builds are always non-incremental builds (i.e., nightly builds always build from scratch and hence are not affected by this issue).
Note
----
I already have a patch for this, and I am opening this bug report as a placeholder to refer to. This is why this template is incomplete. |
|
