The version hasn't been updated in years, so even though there are newer
upstream releases, bumping the version is not straightforward. Thus, use the
'minimum policy version' override for now.
Signed-off-by: Moritz Haase <Moritz.Haase@bmw.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Please see
https://git.yoctoproject.org/poky/commit/?id=4dd321f8b83afecd962393101b2a6861275b5265
for what changes are needed, and sed commands that can be used to make them en masse.
I've verified that bitbake -c patch world works with these, but did not run a world
build; the majority of recipes shouldn't need further fixups, but if there are
some that still fall out, they can be fixed in followups.
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is the result of automated script (0.9.1) conversion:
oe-core/scripts/contrib/convert-overrides.py .
converting the metadata to use ":" as the override character instead of "_".
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* otherwise may fail with:
ERROR: synergy-1.7.3+1.7.4-rc8+AUTOINC+588fb4b805-r0 do_unpack_extra: Function failed: do_unpack_extra (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/synergy/1.7.3+1.7.4-rc8+AUTOINC+588fb4b805-r0/temp/log.do_unpack_extra.11874)
ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/synergy/1.7.3+1.7.4-rc8+AUTOINC+588fb4b805-r0/temp/log.do_unpack_extra.11874
Log data follows:
| DEBUG: Executing shell function do_unpack_extra
| /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/synergy/1.7.3+1.7.4-rc8+AUTOINC+588fb4b805-r0/temp/run.do_unpack_extra.11874: 105: /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/synergy/1.7.3+1.7.4-rc8+AUTOINC+588fb4b805-r0/temp/run.do_unpack_extra.11874: unzip: not found
| WARNING: exit code 127 from a shell command.
| ERROR: Function failed: do_unpack_extra (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/synergy/1.7.3+1.7.4-rc8+AUTOINC+588fb4b805-r0/temp/log.do_unpack_extra.11874)
NOTE: recipe synergy-1.7.3+1.7.4-rc8+AUTOINC+588fb4b805-r0: task do_unpack_extra: Failed
ERROR: Task 0 (/home/jenkins/oe/world/shr-core/meta-openembedded/meta-oe/recipes-support/synergy/synergy_git.bb, do_unpack_extra) failed with exit code '1'
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
The synergy project on synergy.googlecode.com is defunct. The
sources cannot be downloaded from there anymore. The new project
home is synergy-project.org, but sources can only be downloaded
from ther with a login. The source code repo is on github.com/synergy.
New recipe to check out the code from GitHub. The code contains
zip archives for gmock and gtest, which need to be extracted before
do_configure. The license file has changed from COPYING to LICENSE. The
authors apparently added their copyright information before the GPLv2
license text. Hence, the md5sum is different.
Signed-off-by: Rudolf J Streif <rudolf.streif@gmail.com>
Changes:
- rename SUMMARY with length > 80 to DESCRIPTION
- rename DESCRIPTION with length < 80 to (non present tag) SUMMARY
- drop final point character at the end of SUMMARY string
- remove trailing whitespace of SUMMARY line
Note: don't bump PR
Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com>
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>
Moritz Haase
Alexander Kanavin
Peter Marko
Martin Jansa
Denys Dmytriyenko
Khem Raj
Rudolf J Streif
Yi Zhao
Matthieu CRAPET
Tasslehoff Kjappfot