On 2018年08月12日 00:10, richard.pur...@linuxfoundation.org wrote:
On Fri, 2018-08-10 at 16:14 +0800, kai.k...@windriver.com wrote:
From: Kai Kang
Some allarch packages rdepends non-allarch packages. When multilib is
used, it doesn't expand the dependency chain correctly, e.g.
core-image-sato
On Fri, 2018-08-10 at 16:14 +0800, kai.k...@windriver.com wrote:
> From: Kai Kang
>
> Some allarch packages rdepends non-allarch packages. When multilib is
> used, it doesn't expand the dependency chain correctly, e.g.
>
> core-image-sato -> ca-certificates(allarch) -> openssl
>
> we expect
On 2018年08月10日 17:24, richard.pur...@linuxfoundation.org wrote:
On Fri, 2018-08-10 at 16:14 +0800, kai.k...@windriver.com wrote:
From: Kai Kang
Some allarch packages rdepends non-allarch packages. When multilib is
used, it doesn't expand the dependency chain correctly, e.g.
core-image-sato
On Fri, 2018-08-10 at 16:14 +0800, kai.k...@windriver.com wrote:
> From: Kai Kang
>
> Some allarch packages rdepends non-allarch packages. When multilib is
> used, it doesn't expand the dependency chain correctly, e.g.
>
> core-image-sato -> ca-certificates(allarch) -> openssl
>
> we expect
From: Kai Kang
Some allarch packages rdepends non-allarch packages. When multilib is
used, it doesn't expand the dependency chain correctly, e.g.
core-image-sato -> ca-certificates(allarch) -> openssl
we expect dependency chain for lib32-core-image-sato:
lib32-core-image-sato ->
