linux/poky.git/meta/conf/distro/include/default-versions.inc, branch uninative-2.6

openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-04T10:03:56+00:00

I believe the time has come to do this: openssl 1.0 upstream support stops at the end of 2019, and we do not want a situation where a supported YP release contains an unsupported version of a critical security component. Openssl 1.0 can still be utilized by depending on 'openssl10' recipe. (From OE-Core rev: 876466145f2da93757ba3f92177d0f959f5fe975) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

default-versions.inc: use weak assignments to allow overwrite

2018-06-18T10:07:57+00:00

default-versions.inc is included by defaultsetup.conf which in bitbake.conf is included after local/machine/distro.conf. If these are hard assignments distros can's overwrite them. (From OE-Core rev: b9fb89fb7189e631b615868d567e1eab504ee3c2) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

openssl10: rename back to openssl and make it the default via PREFERRED_VERSION

2017-08-19T21:15:39+00:00

openssl 1.1 broke 3rd party layers a lot more than was expected; let's flip the switch at the start of next development cycle. Add a PROVIDES = "openssl10" to openssl 1.0 recipe; any dependency that is not compatible with 1.1 should use that in its DEPENDS, as the 1.0 recipe will later be renamed back to openssl10. This does not always work: http://lists.openembedded.org/pipermail/openembedded-core/2017-August/140957.html but for many recipes it does. (From OE-Core rev: 5585103c195104e85ed7ac1455bef91b2e88a04d) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

liberation-fonts: update to 2.00.1

2017-05-16T13:08:30+00:00

'fontforge issue' was actually a non-issue; fontforge is required only when building ttf fonts from sfd source. We took prebuilt ttf fonts when using 1.04 version, and can do the same thing with 2.00.1 version, it's just that the tarball name for prebuilt fonts has slightly changed and no one noticed somehow. License has changed from GPLv2 to Open Font License v.1.1 (From OE-Core rev: 9b60def67028df65fa8894c49cf09e601f1670df) Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

db: remove the 6.x recipe

2017-03-14T14:42:16+00:00

Version 6.x of Berkeley DB has been rejected by open source community due to its hostile AGPLv3 license; both Fedora and Debian are sticking with db 5.x - and by extension, all the open source projects are still developed and tested with db 5.x In oe-core the only thing that was requiring db 6.x was rpm 5.x, and so there's no reason to continue carrying db 6.x in oe-core. If someone needs API features that are only available in db 6.x, it can be re-added to meta-oe. (From OE-Core rev: 2694de76542840f79e3953c546d07b8ae479b8a1) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

default-versions.inc: drop python-related defaults

2016-06-01T11:38:41+00:00

There is only one version of python 2.x provided, so no need to set a preferred version. PYTHON_BASEVERSION is now set explicitly in python-dir.bbclass and python3-dir.bbclass, so fix up a few recipes that relied on it being set in default-versions.inc without inheriting python-dir. (From OE-Core rev: e0c75841078bf65905c1c9aa2946241b2474a7e2) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

python: Upgrade 2.7.9 > 2.7.11

2016-01-20T17:07:14+00:00

- no license change, just dates Rebased: - check-if-target-is-64b-not-host.patch - add-CROSSPYTHONPATH-for-PYTHON_FOR_BUILD.patch (From OE-Core rev: 9ed4ef038a4a8140accfa97b2eb6b75f8bed3693) Signed-off-by: Alejandro Hernandez Signed-off-by: Richard Purdie

Python: Upgrade from 2.7.3 to 2.7.9:

2015-02-23T17:35:29+00:00

- Based on Paul Eggletons work to partially upgrade to Python 2.7.6 Modified: default-versions.inc: switched to python 2.7.9 generate-manifest-2.7.py: fixed _sysconfigdata python-2.7-manifest.inc: fixed _sysconfigdata python.inc: Updated checksums and source, no LICENSE change just updated some dates python-native_2.7.3 -> python-native_2.7.9 and updated patches python_2.7.3 -> python_2.7.9, and added ac_cv_file__dev_ptmx=no ac_cv_file__dev_ptc=no in EXTRA_OECONF to solve python issue #3754, only needed when cross compiling, also updated patches use_sysroot_ncurses_instead_of_host.patch: New patch to use ncursesw from sysroot instead of hosts, introduced by fix for python issue #15268 Rebased: 01-use-proper-tools-for-cross-build.patch 03-fix-tkinter-detection.patch 05-enable-ctypes-cross-build.patch 06-avoid_usr_lib_termcap_path_in_linking.patch avoid_warning_about_tkinter.patch builddir.patch fix_for_using_different_libdir.patch host_include_contamination.patch multilib.patch nohostlibs.patch search_db_h_in_inc_dirs_and_avoid_warning.patch Deleted (fixed on upstream): 06-ctypes-libffi-fix-configure.patch CVE-2013-4073_py27.patch gcc-4.8-fix-configure-Wformat.patch json-flaw-fix.patch posix_close.patch pypirc-secure.patch python-2.7.3-CVE-2012-2135.patch python-2.7.3-CVE-2013-1752-smtplib-fix.patch python-2.7.3-CVE-2014-1912.patch python-2.7.3-CVE-2014-7185.patch python-2.7.3-berkeley-db-5.3.patch python-fix-build-error-with-Readline-6.3.patch remove-BOM-insection-code.patch remove_sqlite_rpath.patch python2.7.3-nossl3.patch [YOCTO #7059] (From OE-Core rev: d4ad95f0d5f08891637c644e85b09da9c4585059) Signed-off-by: Alejandro Hernandez Signed-off-by: Richard Purdie

default-versions.inc: let INCOMPATIBLE_LICENSE supports wildcard

2014-12-19T18:08:00+00:00

While wildcard in INCOMPATIBLE_LICENSE, such as INCOMPATIBLE_LICENSE = "*GPL-3", PREFERRED_VERSION_db-native could have the correct value "5.%" [YOCTO #5592] (From OE-Core rev: fddca246f15ff72828a0198d8c4d3e58d8bf4442) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

default-versions.inc: match version of db and db-native while "AGPL-3.0" in ${INCOMPATIBLE_LICENSE}

2014-10-24T16:36:15+00:00

The db 6.0.30's LICENSE is 'AGPL-3.0', and db 5.3.28 LICENSE is 'Sleepycat' While building rpm image with "AGPL-3.0" in ${INCOMPATIBLE_LICENSE}, db 6.0.30 and db-native 5.3.28 were built, the different versions caused the rpm doesn't work on target. ... root@qemux86-64:~# rpm -qa |rpmdb: BDB2531 Unacceptable log file /var/lib/rpm/./log/log.0000000001: unsupported log version 21 |rpmdb: BDB2527 Invalid log file: log.0000000001: Invalid argument |rpmdb: BDB0061 PANIC: Invalid argument |==> rpmdbe_event_notify(0x623f40, PANIC(0), 0x7fffee0fbc0c) app_private (nil) |rpmdb: BDB1546 unable to join the environment |error: db_init:tmp/work/core2-64-poky-linux/rpm/5.4.14-r0/rpm-5.4.14/ rpmdb/db3.c:1144: dbenv->open(-30973): BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery ... [YOCTO #6858] (From OE-Core rev: e5a40391dfa12c44f31bdb7550df1275edda3864) Signed-off-by: Hongxu Jia Signed-off-by: Ross Burton Signed-off-by: Richard Purdie