linux/poky.git/meta/conf/distro, branch hardknott

uninative: Upgrade to 3.5

2022-03-02T00:22:13+00:00

Add support for glibc 2.35. (From OE-Core rev: 5bde365accec6837dc5751e1ac01b767898a2c5d) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie (cherry picked from commit 347b8c87fb4e2c398644f900728cf6e22ba4516d) Signed-off-by: Anuj Mittal (cherry picked from commit eeae63c343c8ebd418679915ee20aa8c02fa0fdc) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

default-distrovars.inc: Switch connectivity check to a yoctoproject.org page

2022-02-20T15:32:27+00:00

example.com is proving unreliable at present so switch to our own connectivity page instead. That page is very simple avoiding app overhead on our web server which was an original reason for switching to example.com. (From OE-Core rev: 3d9f68e06736817871d8694fe0c6e779c005872b) Signed-off-by: Richard Purdie (cherry picked from commit dc6b043cb75c5751b5a98afd2201aa31f9b4b9f6) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

gcc: upgrade to gcc-10.3 version

2022-01-31T21:56:01+00:00

gcc-10.2 in Hardknott branch has been upgraded to gcc-10.3 version that includes many bug fixes. Regression tested on X86-64, Arm and Aarch64 without issues. (From OE-Core rev: 87fbe11fbe04a6f2d3e798d282935b26fbc43e77) Signed-off-by: pgowda Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

cve-extra-exclusions: add db CVEs to exclusion list

2021-12-15T07:40:29+00:00

Since Oracle relicensed bdb, the open source community is slowly but surely replacing bdb with supported and open source friendly alternatives. As a result these CVEs are unlikely to ever be fixed. (From OE-Core rev: b3056b937a76ddd6c02cd6b17e7a0c178931add4) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie (cherry picked from commit 679fc70f907fb221f4541ebf30c1610e937209b7) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

uninative: Add version to uninative tarball name

2021-12-05T12:35:43+00:00

uninative works via hashes and doesn't need the version in the tarball name but it does make things easier to inspect in DL_DIR. There were reasons such as ease of publication of the build tarballs but we can handle those differently now and the signature issues from the early code aren't an issue now. From 3.4 onwards we can use a version'd name. [YOCTO #12970] (From OE-Core rev: e3ba0041ccb9633ec21241cb6852aa50c2663677) Signed-off-by: Richard Purdie (cherry picked from commit dadba70d6a24d8ebb5576598efffa973151c7218) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

meta/scripts: Manual git url branch additions

2021-11-21T11:40:35+00:00

Following the scripted conversion adding branches to git:// SRC_URI entries, add the remaining references, mainly in the selftests and recipetool. (From OE-Core rev: 87ac0c0a643cca436784dfcd86472adcf2e04130) Signed-off-by: Richard Purdie (cherry picked from commit 5340c0d688036c1be6c938f05d8a8c1e3b49ec38) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

uninative: Upgrade to 3.4

2021-11-01T10:36:35+00:00

This adds a patch to glibc which allows it to work with Docker and clone3 syscall issues cased by EPERM vs ENOSYS. (From OE-Core rev: 47e638ada946af7d69fb65619858a1e4564613c4) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie

uninative: Upgrade to 3.3, support glibc 2.34

2021-10-29T10:17:21+00:00

(From OE-Core rev: 8759cc146661bd8d06ab0e8b4168b1d9e6bd16c2) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie (cherry picked from commit 4aa4dcd5f31657073f2207a9a4a43247322c7eb1) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

Update mailing list address

2021-10-07T14:10:40+00:00

(From OE-Core rev: c2531bf2503e8dd736bba0acde9e329a439f3fda) Signed-off-by: Jon Mason Signed-off-by: Richard Purdie (cherry picked from commit 83169c33f7585da25560784f79eaad2c6f029f3c) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

cve-extra-exclusions.inc: add exclusion list for intractable CVE's

2021-05-30T07:19:35+00:00

The preferred methods for CVE resolution are: 1. Version upgrades where possible 2. Patches where not possible 3. Database updates where version info is incorrect 4. Exclusion from checking where it is determined that the CVE does not apply to our environment In some cases none of these methods are possible. For example the CVE may be decades old with no apparent resolution, and with broken links that make further research impractical. Some CVEs are vauge with no specific action the project can take too. This patch creates a mechanism for users to remove this type of CVE from the cve-check results via an optional include file. Based on an initial patch from Steve Sakoman but extended heavily by RP. (From OE-Core rev: 4a70af7b89d2ddff341b724a97cb96987874a3b0) Signed-off-by: Richard Purdie