Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Pavel Zhukov" <pavel@zhukoff.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3 1/4] dummy-sdk-package.inc: Filter packages which are marked for installation
Date: Thu, 12 Oct 2023 09:36:03 +0200	[thread overview]
Message-ID: <20231012093603.53a79e61@booty> (raw)
In-Reply-To: <20231009144001.21150-1-pavel@zhukoff.net>

Hello Pavel,

On Mon,  9 Oct 2023 16:39:58 +0200
"Pavel Zhukov" <pavel@zhukoff.net> wrote:

> if packages is provided by dummysdk and in the same time marked for
> installation with IMAGE_INSTALL it causes conflict in apt because virtual providers are
> not taken into account if package is asked to be installed explicitly.
> Filter such packages from provides/conflicts to workaround this problem.
> This workaround brakes RPM usecase because of file conlicts with
> DUMMYPROVIDES, use DUMMYPROVIDES_PACKAGES_MULTILIB instead (which
> doesn't include file based conflicts).
> While this is needed for the case of package_deb only adding it for all
> package managers to not complicate the code.
> 
> Fixes: [Yocto #13338] [Yocto #14066]
> 
> Fixes:
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  target-sdk-provides-dummy : Conflicts: bash
> E: Unable to correct problems, you have held broken packages.
> 
> Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>

Testing with this series applied results in lots of errors like these:

stdio: ERROR: core-image-minimal-1.0-r0 do_rootfs: No SPDX file found for package base-files, False sstate:base-files:qemux86_64-poky-linux:3.0.14:r0:qemux86_64:11: sstate:base-files::3.0.14:r0::11:
stdio: ERROR: core-image-minimal-mtdutils-1.0-r0 do_rootfs: No SPDX file found for package base-files, False sstate:base-files:qemux86_64-poky-linux:3.0.14:r0:qemux86_64:11: sstate:base-files::3.0.14:r0::11:

See the full log at:

https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/5894/steps/14/logs/stdio

Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2023-10-12  7:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 14:39 [PATCH v3 1/4] dummy-sdk-package.inc: Filter packages which are marked for installation Pavel Zhukov
2023-10-09 14:39 ` [PATCH v3 2/4] package_deb: Revert versioned providers workaround Pavel Zhukov
2023-10-09 14:40 ` [PATCH v3 3/4] dummy-sdk-package.inc: Specify providers version Pavel Zhukov
2023-10-09 14:40 ` [PATCH v3 4/4] selftest: Add tests for populate_sdk task Pavel Zhukov
2023-10-12  7:36 ` Luca Ceresoli [this message]
2023-12-18 10:28   ` [OE-core] [PATCH v3 1/4] dummy-sdk-package.inc: Filter packages which are marked for installation pazhukov
2024-01-01 12:57     ` Alexandre Belloni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231012093603.53a79e61@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pavel@zhukoff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox