archive mirror
 help / color / mirror / Atom feed
From: Christian Eggers <>
To: <>
Cc: OpenBMC Maillist <>,
	Matt Johnston <>,
	Khem Raj <>
Subject: Re: [oe] openssh-dev package and populate_sdk conflicts
Date: Fri, 24 Sep 2021 11:28:23 +0200	[thread overview]
Message-ID: <2617274.mvXUDI8C0e@n95hx1g2> (raw)
In-Reply-To: <>

On Friday, 24 September 2021, 05:08:04 CEST, Matt Johnston wrote:
> 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].

I had a similar problem. It set the following in my rootfs image recipe:

# SDK: openssh-dev cannot be installed because dropbear is already installed.


      parent reply	other threads:[~2021-09-27  1:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24  2:45 Matt Johnston
2021-09-24  4:29 ` [oe] " Khem Raj
2021-09-24  9:28 ` Christian Eggers [this message]

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:

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

  git send-email \
    --in-reply-to=2617274.mvXUDI8C0e@n95hx1g2 \ \ \ \ \ \
    --subject='Re: [oe] openssh-dev package and populate_sdk conflicts' \

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