[OE-core] Conflicting providers for ssh/sshd (dropbear and openssh)

[Scott Garman]

On 06/28/2011 03:41 PM, Khem Raj wrote:
> ERROR: Multiple .bb files are due to be built which each provide ssh
> (/home/kraj/work/angstrom/sources/openembedded-core/meta/recipes-core/dropbear/dropbear_0.52.bb
> /home/kraj/work/angstrom/sources/openembedded-core/meta/recipes-connectivity/openssh/openssh_5.8p2.bb).
>   This usually means one provides something the other doesn't and should.
> ERROR: Multiple .bb files are due to be built which each provide sshd
> (/home/kraj/work/angstrom/sources/openembedded-core/meta/recipes-core/dropbear/dropbear_0.52.bb
> /home/kraj/work/angstrom/sources/openembedded-core/meta/recipes-connectivity/openssh/openssh_5.8p2.bb).
>   This usually means one provides something the other doesn't and should.
>
> reason is that dropbear only provides ssh and sshd packages openssh
> provides a few more e.g. openssh-sftp-server which is demanded by
> some images and at same time wants dropbear to provide sshd and ssh
>
> Now both recipes are to be built but are in contention for providing
> ssh and sshd
>
> How to solve this problem. ? Are other packages that openssh provides
> strictly depending on ssh/sshd from openssh ? or will they work on
> any ssh/sshd ?
>
> If they are independent then may be the openssh recipe should be
> divided into openssh-ssh and openssh-rest so one can use openssh
> provided daemon or dropbear provided as they wish

I've run into that and have been wondering how to resolve it as well.

If there are currently existing images which are pulling in dropbear's 
ssh and sshd while using openssh's sftp-server, then that would imply 
they can work independently, even though that combo seems like an 
aggressive space optimization that I would tend to avoid.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center