From: Mike Looijmans <mike.looijmans@topic.nl>
To: openembedded-core@lists.openembedded.org
Subject: Not selecting <old version of package> as installing it would break existing dependencies
Date: Tue, 24 Mar 2015 18:16:05 +0100 [thread overview]
Message-ID: <55119BD5.8060002@topic.nl> (raw)
After upgrading a library to a newer version, for example, something
called libdvbsi++ from 0.3.6 to 0.3.7, running opkg upgrade outputs the
following cryptic error message:
Not selecting libdvbsi++1 0.3.6 as installing it would break existing
dependencies.
Adding "-V2" to opkg upgrade expands that with the following message:
opkg_prepare_upgrade_pkg: Package libdvbsi++1 (0.3.7-r2.0) installed in
root is up to date.
So apparently it knows about the later version, so why complain about
the old one?
There is only one package that (r)depends on that lib (enigma2). Nothing
else needs it.
This often happens with other packages as well. Is this a bug in opkg,
or is it trying to tell us we're doing something wrong?
--
Mike Looijmans
next reply other threads:[~2015-03-24 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 17:16 Mike Looijmans [this message]
2015-03-27 21:21 ` Not selecting <old version of package> as installing it would break existing dependencies Alejandro del Castillo
2015-03-28 13:04 ` Mike Looijmans
2015-03-30 19:16 ` Alejandro del Castillo
2015-03-31 10:01 ` Mike Looijmans
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=55119BD5.8060002@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@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