Skip to contentSkip to conversation

How to find out the rdepends of certain package

DISCUSSION John Rama 1 participant 1 message Jun 30, 2017

lore
Share & tools
lore

John Rama

author
#0 lore raw

Hi, experts

I'm facing following problem, when building a image.

--------------------------------------------------------
The following packages have unmet dependencies:
openssh-dev : Depends: openssh (= 7.1p2-r0.0) but it is not going to be installed
Recommends: openssh-misc-dev but it is not installable
Recommends: shadow-sysroot-dev but it is not installable
Recommends: libcrypto-dev but it is not installable
Recommends: openssh-sshd-dev but it is not installable
Recommends: update-alternatives-opkg-dev but it is not installable
Recommends: openssh-scp-dev but it is not installable
Recommends: openssh-ssh-dev but it is not installable
Recommends: openssh-sftp-server-dev but it is not installable
Recommends: openssh-keygen-dev but it is not installable
Recommends: openssh-sftp-dev but it is not installable
E: Unable to correct problems, you have held broken packages.
--------------------------------------------------------

I know this can be resolved by adding "openssh" to the IMAGE_INSTALL_append list.

But, I'm very curious which recipes try to use openssh-dev, or which package depends on openssh-dev.

1. I just greped entire recipe tree with "openssh-dev", but there is no hit.
2. Run bitbake -g <image> option to generate the *-depends.dot file, then grepped with "openssh-dev", two hits.

package-depends.dot:31228:"openssh-staticdev" -> "openssh-dev" [style=dashed] pn-depends.dot:4474:"openssh" -> "openssh-dev" [style=dashed]

However, these are not used by using the similiar method of #1 and #2.

Is there any good way to find out why openssh-dev is in the installed package list ?

John