From: Josh Mahonin <jmahonin@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] Issues with 'RDEPENDS kernel' in module.bbclass using .deb packages
Date: Tue, 04 Aug 2009 14:58:50 -0400 [thread overview]
Message-ID: <4A7884EA.7070104@cbnco.com> (raw)
Hi all,
I'm working on an updated recipe for nvidia-display, but unfortunately
during the rootfs stage of building an image it errors out on :
---
The following packages have unmet dependencies:
nvidia-display: Depends: kernel (= 2.6.30) but 2.6.30-r1 is to be
installed
---
Now I'm building debian style packages, so when I check /var/dpkg/status
under the rootfs (which classes/rootfs_deb.bbclass uses) , sure enough I
have an entry for the kernel, with both the PV and PR in the 'Version'
field:
---
Package: kernel
Status: install ok unpacked
...
Version: 2.6.30-r1
...
---
In classes/module.bbclass, however, we have the RDEPENDS which matches
only on PV, without the PR:
---
RDEPENDS += "kernel (${KERNEL_VERSION}) update-modules"
---
In the meantime I've worked around it by removing the KERNEL_VERSION
requirement in module.bbclass, although I don't think that's really the
right way to do it.
I suppose I could remove writing the PR to the status file, although
that might be useful to keep as a reference when upgrading packages
later. It looks IPK-style packages also keep the PR in the version
field - is this an issue for those users as well, or is this DEB specific?
Are there any thoughts as to the right way to fix this issue?
Thanks in advance,
Josh
reply other threads:[~2009-08-04 19:14 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=4A7884EA.7070104@cbnco.com \
--to=jmahonin@cbnco.com \
--cc=openembedded-devel@lists.openembedded.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.