From: Mike Looijmans <mike.looijmans@topic.nl>
To: OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: How do I change the "Architecture" of a package?
Date: Tue, 30 Dec 2014 16:24:34 +0100 [thread overview]
Message-ID: <54A2C3B2.9010006@topic.nl> (raw)
What if the architecture of a package was accidentally left at its
default, but it should have been "all" for example?
Just putting "inherit allarch" or simply PACKAGE_ARCH="all" into the
recipe is not enough. You get stuck with a "more specific" older
version, so that no device wants to upgrade to the newer version that's
"all" architecture compatible.
Only way to fix this was to manually remove the old version from the
feeds and also manually remove it from the device, and then reinstall
it. This works for me personally, but what if I want to apply this to
about a million devices that are already in the field?
What can I do to get them to upgrade from the (in this case) "mipsel32"
to "all" package?
(and I have a few dozen of these mis-architectured packages...)
--
Mike Looijmans
next reply other threads:[~2014-12-30 15:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 15:24 Mike Looijmans [this message]
2014-12-30 17:59 ` How do I change the "Architecture" of a package? Paul Barker
2014-12-31 19:13 ` Mike Looijmans
2015-01-02 8:48 ` Mike Looijmans
2015-01-02 9:16 ` Richard Purdie
2015-01-02 9:24 ` Mike Looijmans
2015-01-02 9:28 ` Mike Looijmans
2015-01-04 15:20 ` Bug: PR server changes the PKGV variable too Mike Looijmans
2015-01-05 9:27 ` Richard Purdie
2015-01-05 9:41 ` Mike Looijmans
2015-01-05 10:07 ` Richard Purdie
2015-01-05 10:36 ` Mike Looijmans
2015-01-05 11:37 ` Richard Purdie
2015-01-05 12:09 ` Mike Looijmans
2015-01-05 16:03 ` Mike Looijmans
2015-01-03 10:52 ` How do I change the "Architecture" of a package? 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=54A2C3B2.9010006@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