From: Khem Raj <raj.khem@gmail.com>
To: Matt Johnston <matt@codeconstruct.com.au>,
openembedded-devel@lists.openembedded.org
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [oe] openssh-dev package and populate_sdk conflicts
Date: Thu, 23 Sep 2021 21:29:26 -0700 [thread overview]
Message-ID: <5b7e2d77-85f7-cc88-5260-05e6b012f3ad@gmail.com> (raw)
In-Reply-To: <94429904ec0c9d75919cda42339a2fafcbc35fe4.camel@codeconstruct.com.au>
On 9/23/21 20:08, Matt Johnston wrote:
> Hi OE list,
>
> Recently OpenBMC merged a change to install openssh-sftp-server package
> alongside dropbear sshd [1]. That caused a conflict in "populate_sdk" which
> installs all available -dev packages [2]. 'openssh-dev' pulls in an
> 'openssh' -> 'openssh-sshd' dependency which conflicts with 'dropbear' [3].
>
> What would be the recommended way to handle that situation? For now OpenBMC
> has merged a change to disable building openssh-dev (it's empty since
> openssh doesn't have libraries) [4].
>
> Should non-library packages handle -dev packages differently? The default
> -dev package comes from bitbake.conf .
>
perhaps set
RDEPENDS:${PN}-dev = ""
in openssh
> Cheers,
> Matt
>
> [1]
> https://github.com/openbmc/openbmc/commit/26dbcdbd917e4f22fb400153da0d3e7255c8e646
> [2]
> https://github.com/openbmc/openbmc/blob/49465582e16221caf74cbdea11c87600a02bf47b/poky/meta/classes/populate_sdk_base.bbclass#L5
>
> [3] https://github.com/openbmc/openbmc/issues/3819
> * - package openssh-8.7p1-r0.arm1176jzs conflicts with dropbear provided
> by dropbear-2020.81-r0.arm1176jzs
> * - package openssh-dev-8.7p1-r0.arm1176jzs requires openssh = 8.7p1-r0,
> but none of the providers can be installed
>
> [4] https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/47089
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#93114): https://lists.openembedded.org/g/openembedded-devel/message/93114
> Mute This Topic: https://lists.openembedded.org/mt/85831414/1997914
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2021-09-24 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 2:45 openssh-dev package and populate_sdk conflicts Matt Johnston
2021-09-24 4:29 ` Khem Raj [this message]
2021-09-24 9:28 ` [oe] " Christian Eggers
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=5b7e2d77-85f7-cc88-5260-05e6b012f3ad@gmail.com \
--to=raj.khem@gmail.com \
--cc=matt@codeconstruct.com.au \
--cc=openbmc@lists.ozlabs.org \
--cc=openembedded-devel@lists.openembedded.org \
/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;
as well as URLs for NNTP newsgroup(s).