Re: [cip-dev][isar-cip-core][PATCH] swupdate-config: Set DPKG_ARCH to any

Jan Kiszka <[email protected]>
Newsgroups org.cip-project.lists.cip-dev
Message-ID <[email protected]>
On 26.06.26 17:19, Quirin Gylstorff wrote:
> From: Quirin Gylstorff <[email protected]>
> 
> This avoids the following error.
> 
> | Building dependency tree...
> | Reading state information...
> | Package swupdate-config is a virtual package provided by:
> |   swupdate-config-qemu-riscv64 0.2
> |   swupdate-config-qemu-arm64 0.2
> |
> | E: Package 'swupdate-config' has no installation candidate
> 
> This solution works in this case, but to confirm with the Debian
> standard we would need to add a conflict to all other versions of
> this packages.

...or add the machine name to the package name. How about that?

I assume you ran into that due to a rebuild over the same build folder,
first arm, then riscv or so, right? Please describe that as well.

Jan

> 
> Signed-off-by: Quirin Gylstorff <[email protected]>
> ---
>  .../{swupdate-config_0.2.bb => swupdate-config_0.3.bb}         | 3 +++
>  1 file changed, 3 insertions(+)
>  rename recipes-core/swupdate-config/{swupdate-config_0.2.bb => swupdate-config_0.3.bb} (90%)
> 
> diff --git a/recipes-core/swupdate-config/swupdate-config_0.2.bb b/recipes-core/swupdate-config/swupdate-config_0.3.bb
> similarity index 90%
> rename from recipes-core/swupdate-config/swupdate-config_0.2.bb
> rename to recipes-core/swupdate-config/swupdate-config_0.3.bb
> index b48e3d1..013b957 100644
> --- a/recipes-core/swupdate-config/swupdate-config_0.2.bb
> +++ b/recipes-core/swupdate-config/swupdate-config_0.3.bb
> @@ -19,6 +19,9 @@ DEBIAN_PROVIDES := "${PN}"
>  
>  PN .= "-${MACHINE}"
>  
> +# architecture specific package as it depends on the machine
> +DPKG_ARCH = "any"
> +
>  SRC_URI = "file://swupdate.cfg \
>             file://hwrevision.tmpl"
>  

-- 
Siemens AG, Foundational Technologies
Linux Expert Center
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.