From: Gary Thomas <gary@mlbassoc.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: Issues installing GTK based packages
Date: Mon, 11 Apr 2016 07:46:32 +0200 [thread overview]
Message-ID: <570B3A38.9000000@mlbassoc.com> (raw)
When installing epiphany into an existing system, I'm now
getting these errors:
Configuring libgtk-3.0.
///var/lib/opkg/info/libgtk-3.0.postinst: line 3: glib-compile-schemas: not found
Configuring gsettings-desktop-schemas.
///var/lib/opkg/info/gsettings-desktop-schemas.postinst: line 2: glib-compile-schemas: not found
Configuring epiphany.
///var/lib/opkg/info/epiphany.postinst: line 2: glib-compile-schemas: not found
I believe this is because glib-compile-schemas was moved from
glib-2.0-utils to glib-2.0-dev by this change (Poky)
commit cc97d5760100415ed22fa329e8962e5f37b8d741
Author: Jussi Kukkonen <jussi.kukkonen@intel.com>
Date: Wed Mar 23 10:59:08 2016 +0200
glib-2.0: Fix packaging
* move gdbus-codegen to ${PN}-codegen
* move other development tools and data files to ${PN}-dev
* remove references to non-existent paths
(From OE-Core rev: 351064e9c5deb6411c8a0d40ebd4fd4f83299d4e)
Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Installing glib-2.0-dev just to get this tool doesn't seem reasonable as
it hauls in a boatload of other packages, including bash and friends, which
I don't want on my target.
Filed as bug #9431
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2016-04-11 5:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 5:46 Gary Thomas [this message]
2016-04-11 6:44 ` Issues installing GTK based packages Jussi Kukkonen
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=570B3A38.9000000@mlbassoc.com \
--to=gary@mlbassoc.com \
--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 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.