From: Jaap de Jong <jaap.dejong@nedap.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: opkg v0.3.2 bug
Date: Thu, 30 Jun 2016 15:59:26 +0200 [thread overview]
Message-ID: <577525BE.6020602@nedap.com> (raw)
Hi All,
I've already put this in
https://groups.google.com/forum/#!topic/opkg-devel but I really want to
hear what your experiences are.
I have this package A for which package B has a dependency?
I was using v0.2.3 before and 'opkg remove A' did not remove it.
With v0.3.2 the same errors:
Removing package A from root...
Collected errors:
* print_dependents_warning: Package A is depended upon by packages:
* print_dependents_warning: B
* print_dependents_warning: These might cease to work if package A is
removed.
* print_dependents_warning: Force removal of this package with
--force-depends.
* print_dependents_warning: Force removal of this package and its
dependents
* print_dependents_warning: with --force-removal-of-dependent-packages.
But package A is removed nevertheless....
This sounds as a severe error!
Or is it me doing something wrong??
Thanks,
Jaap
next reply other threads:[~2016-06-30 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 13:59 Jaap de Jong [this message]
2016-06-30 20:05 ` opkg v0.3.2 bug Alejandro del Castillo
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=577525BE.6020602@nedap.com \
--to=jaap.dejong@nedap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox