07-25-2017 06:26 PM
My last post seemed to disappear so I am re-posting my issue. This concerns the petalinux 2017.2 release for the zcu102 board.
When I disable all dropbear references in petalinux-config -c rootfs, the petalinux-build still attempts to include it.
In 2016.4, I was able to disable all dropbear references and enable openssh instead.
When I try this with 2017.2, the build process gives me this error:
Computing transaction...error: Can't install packagegroup-core-ssh-dropbear-1.0-r1@all: unable to install provider for dropbear:
error: dropbear-2016.74-r0@aarch64 is conflicted by openssh-7.3p1-r0@aarch64
I have verified all dropbear references have been disabled from the rootfs configuration:
Symbol: dropbear [=n]
Symbol: dropbear-dbg [=n]
Symbol: dropbear-dev [=n]
Symbol: dropbear-openssh-sftp-server [=n]
Symbol: packagegroup-core-ssh-dropbear [=n]
Symbol: packagegroup-core-ssh-dropbear-dbg [=n]
I saw this same issue with 2017.1, but was hoping it would be fixed in 2017.2... Any ideas on how to fix this?
10-12-2017 10:30 AM
I went into:
and deleted ssh-server-dropbear from the COMMON_FEATURES variable. Rebuilt it and things are what I expect now.
10-23-2017 01:46 PM
Confirmed the previous reply fixes the issue. Only additional comment is the full path to the file is:
11-15-2017 11:42 AM
One thing that should also work... Add the following line to <project>/project-spec/meta-user/conf/layer.conf:
COMMON_FEATURES_remove = "ssh-server-dropbear"
This way the Petalinux installation directory doesn't have to be modified. Then you should be able to add openssh (ie, IMAGE_INSTALL_append = " openssh") without conflict.
11-16-2017 08:34 PM
> add this IMAGE_FEATURES_remove += "ssh-server-dropbear" in meta-user/conf/petalinuxbsp.conf
> unselect packagegroup-dropbear, select openssh and openssh-server from petalinux-config -c rootfs