* it depends on libglade which is gone
* project is dead - last release was in 2014
* 0.6.3 tested last time was buggy: keyboard tended to reduce it's size to
few pixels and there was no simple way to undo that
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
* patches were either leftovers or do not match the code
* DESCRIPTION -> shortened SUMMARY
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Added gtk+3 dependency and resolved conflicts
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
* as PNBLACKLIST message says, these recipes are blacklisted for long
time and nobody showed any interest to fix them
* remove all unused .patch and .inc files as well
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
- Fix compile failure against musl C library
- Fixed when compile with "-Wformat -Wformat-security -Werror=format-security"
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* based on discussion in pndeprecated thread:
https://patchwork.openembedded.org/patch/137573/
update the messages to warn possible users that the
recipe will be removed before the end of the next development
cycle (before Yocto 2.4 is released).
* updated with:
sed -i 's/^\(PNBLACKLIST.*".*\)"/\1 - the recipe will be removed on 2017-09-01 unless the issue is fixed"/g' `git grep PNBLACKLIST | sed 's/:.*//g' | sort -u | xargs`
* then noticed couple recipes being blacklisted only based on
DISTRO_FEATURES, so removed those:
meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb
meta-oe/recipes-connectivity/bluez/bluez-hcidump_2.5.bb
meta-oe/recipes-connectivity/bluez/bluez4_4.101.bb
meta-oe/recipes-connectivity/bluez/gst-plugin-bluetooth_4.101.bb
meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb
meta-oe/recipes-navigation/gypsy/gypsy.inc
meta-oe/recipes-navigation/navit/navit.inc
meta-oe/recipes-support/opensync/libsyncml_0.5.4.bb
* if it isn't fixed by this date, it's fair game to be removed
whenever someone gets around to i
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
We currently see:
| /bin/bash: gconftool-2: command not found
| Makefile:841: recipe for target 'install-data-local' failed
| make[3]: *** [install-data-local] Error 127
Presumably this now happens more regularly with demise of the shared
sysroot. Adding gconf-native to the dependency list fixes it.
Cc: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
The latest GTK2 version is 0.5.4, which contains several bug fixes.
Noteable, it fixes an issue where the SVG keys have not been displayed
with recent versions of its dependencies.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes following QA warnings:
tracker-0.14.2: tracker rdepends on libnmglib, but it isn't a build dependency? [build-deps]
tracker-0.14.2: tracker rdepends on libnmutil, but it isn't a build dependency? [build-deps]
tracker-0.14.2: tracker rdepends on nss, but it isn't a build dependency? [build-deps]
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes following floating dependencies:
WARN: tracker: tracker-nautilus-extension rdepends on atk, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on cairo, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on eglibc, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on expat, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on fontconfig, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on freetype, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on gdk-pixbuf, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on glib-2.0, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on gtk+, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on harfbuzz, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libffi, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libpng, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libsqlite3, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libunistring, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libx11, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libxau, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libxcb, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libxcb-render, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libxcb-shm, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libxdmcp, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libxext, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on libxrender, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on pango, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on pixman, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on tracker, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on util-linux-libuuid, but it isn't a build dependency?
WARN: tracker: tracker-nautilus-extension rdepends on zlib, but it isn't a build dependency?
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* it rdepends on gvfs which is available only in meta-gnome and nothing
in meta-oe depends on tracker
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
That's a version requirement for Gnumeric.
Note that goffice 0.10.1 requires gtk3.
Signed-off-by: Mario Domenech Goulart <mario@ossystems.com.br>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* This change is only aesthetic (unlike indentation in Python
tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
tabs is the need to update a lot of recipes). Lately this advice
was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
error prone when someone is not sure if e.g.
do_generate_toolchain_file() is Python or shell task and also allows
to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
potentially bad (shouldn't be used for indenting of multiline
variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
we're quite inconsistent wheater it's first character on line
under opening quote or under first non-whitespace character in
previous line.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
Hongxu Jia
Khem Raj
Armin Kuster
Andreas Müller
Andreas Müller
Martin Jansa
Oleksandr Kravchuk
Paul Gortmaker
Derek Straka
Stefan Agner
Alexander Kanavin
Max Krummenacher
Koen Kooi
Mario Domenech Goulart
Paul Eggleton