openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Johnston <matt@codeconstruct.com.au>
To: openembedded-devel@lists.openembedded.org
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: openssh-dev package and populate_sdk conflicts
Date: Fri, 24 Sep 2021 10:45:49 +0800	[thread overview]
Message-ID: <94429904ec0c9d75919cda42339a2fafcbc35fe4.camel@codeconstruct.com.au> (raw)

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 .

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


             reply	other threads:[~2021-09-24  2:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24  2:45 Matt Johnston [this message]
2021-09-24  4:29 ` [oe] " Khem Raj
2021-09-24  9:28 ` 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=94429904ec0c9d75919cda42339a2fafcbc35fe4.camel@codeconstruct.com.au \
    --to=matt@codeconstruct.com.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --subject='Re: openssh-dev package and populate_sdk conflicts' \
    /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

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).