openssh: do not create an empty openssh-dev package
When building an SDK (with populate_sdk), all '-dev' packages are installed. And empty 'openssh-dev' package would pull in 'openssh-sshd' package even if our image is only depending on 'openssh-sftp'. This causes a conflict with 'dropbear' server, which is only using openssh-sftp. Fix: Problem: package dropbear-dev-2020.81-r0.4.cortexa7t2hf_neon requires dropbear = 2020.81-r0.4, but none of the providers can be installed - package dropbear-2020.81-r0.4.cortexa7t2hf_neon conflicts with openssh provided by openssh-8.9p1-r0.7.cortexa7t2hf_neon - package openssh-8.9p1-r0.7.cortexa7t2hf_neon conflicts with dropbear provided by dropbear-2020.81-r0.4.cortexa7t2hf_neon - package openssh-dev-8.9p1-r0.7.cortexa7t2hf_neon requires openssh = 8.9p1-r0.7, but none of the providers can be installed - conflicting requests Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit is contained in:
parent
814cc5043e
commit
34625f886f
|
|
@ -0,0 +1,11 @@
|
|||
# Copyright (C) 2022 Digi International.
|
||||
|
||||
# Don't create an empty openssh-dev package.
|
||||
#
|
||||
# When building an SDK (with populate_sdk), all '-dev' packages are
|
||||
# installed. And empty 'openssh-dev' package would pull in 'openssh-sshd'
|
||||
# package even if our image is only depending on 'openssh-sftp'.
|
||||
#
|
||||
# This causes a conflict with 'dropbear' server, which is only using
|
||||
# openssh-sftp.
|
||||
ALLOW_EMPTY:${PN}-dev = "0"
|
||||
Loading…
Reference in New Issue