From: John Rama <john.rama01@gmail.com>
To: yocto@yoctoproject.org
Subject: How to find out the rdepends of certain package
Date: Fri, 30 Jun 2017 11:19:00 -0400 [thread overview]
Message-ID: <59566BE4.2040305@gmail.com> (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
reply other threads:[~2017-06-30 15:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59566BE4.2040305@gmail.com \
--to=john.rama01@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.