newlib: Upgrade to latest yearly release 3.3.0
PATCH 1/1 newlib: Upgrade to latest yearly release 3.3.0
Upgrade to the latest snapshot, also drop md5sum while were at it.
---
.../newlib/{libgloss_3.2.0.bb => libgloss_3.3.0.bb} | 0
meta/recipes-core/newlib/newlib.inc | 3 +--
meta/recipes-core/newlib/{newlib_3.2.0.bb => newlib_3.3.0.bb} | 0
3 files changed, 1 insertion(+), 2 deletions(-)
rename meta/recipes-core/newlib/{libgloss_3.2.0.bb => libgloss_3.3.0.bb} (100%)
rename meta/recipes-core/newlib/{newlib_3.2.0.bb => newlib_3.3.0.bb} (100%)meta/recipes-core/newlib/libgloss_3.3.0.bb renamed from meta/recipes-core/newlib/libgloss_3.2.0.bb +0 -0
meta/recipes-core/newlib/newlib.inc +1 -2
@@ -16,8 +16,7 @@ LIC_FILES_CHKSUM = " \ " SRC_URI = "https://sourceware.org/pub/newlib/newlib-${PV}.tar.gz" -SRC_URI[md5sum] = "afb3a01c8c82b6717ea55659a4de30ec" -SRC_URI[sha256sum] = "f7b2322964a1e3b37bec0768da20f50dfb62247d729110974dd95756a53bb6d4" +SRC_URI[sha256sum] = "58dd9e3eaedf519360d92d84205c3deef0b3fc286685d1c562e245914ef72c66" INHIBIT_DEFAULT_DEPS = "1" DEPENDS = "virtual/${TARGET_PREFIX}gcc"
meta/recipes-core/newlib/newlib_3.3.0.bb renamed from meta/recipes-core/newlib/newlib_3.2.0.bb +0 -0
Signature · 1 line
2.17.1
✗ patchtest: failure for newlib: Upgrade to latest yearly release 3.3.0
== Series Details ==
Series: newlib: Upgrade to latest yearly release 3.3.0
Revision: 1
URL : https://patchwork.openembedded.org/series/23943/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:
* Issue Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at 26eb22191f)
If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).
---
Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
Re: [OE-core] ✗ patchtest: failure for newlib: Upgrade to latest yearly release 3.3.0
My bad, this meant to be a patch for Dunfell since its been merged on master already, please disregard this failure
Alejandro
Quoted 36 lines · Patchwork
== Series Details ==
Series: newlib: Upgrade to latest yearly release 3.3.0
Revision: 1
URL : https://patchwork.openembedded.org/series/23943/
State : failure== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:
* Issue Series does not apply on top of target branch [test_series_merge_on_head] Suggested fix Rebase your series on top of targeted branch Targeted branch master (currently at 26eb22191f)If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).
---
Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
Re: [OE-core] ✗ patchtest: failure for newlib: Upgrade to latest yearly release 3.3.0
Quoted 2 lines · Alejandro Hernandez
My bad, this meant to be a patch for Dunfell since its been merged on master already, please disregard this failure
If you'd like me to consider a patch for dunfell, I'll need a little more info than just that it is a version upgrade.
For dunfell patches to be considered they should be in one of the following categories:
Acceptable:
Security and CVE fixes
Fixes for bugs
Changes to follow an upstream stable series or LTS that aligns with the original release (based on compatibility)
Potentially Acceptable:
Fixes so codebase works with newly released distros (only in the first six months after a given release series first releases)
Bug fix only version upgrades for upstreams with a good stable process
So if you could tag any patches for dunfell LTS with [dunfell] in the subject and let me know which of the above categories the patch falls into I will be a happy maintainer ;-)
Steve
Quoted 38 lines · Patchwork
== Series Details ==
Series: newlib: Upgrade to latest yearly release 3.3.0
Revision: 1
URL : https://patchwork.openembedded.org/series/23943/
State : failure== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:
* Issue Series does not apply on top of target branch [
test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at26eb22191f)If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).
---
Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
Re: [OE-core] ✗ patchtest: failure for newlib: Upgrade to latest yearly release 3.3.0
Quoted 25 lines · Steve Sakoman
Quoted 2 lines · Alejandro Hernandez
My bad, this meant to be a patch for Dunfell since its been merged on
master already, please disregard this failure
If you'd like me to consider a patch for dunfell, I'll need a little more info than just that it is a version upgrade.
For dunfell patches to be considered they should be in one of the following categories:
Acceptable:
Security and CVE fixes
Fixes for bugs
Changes to follow an upstream stable series or LTS that aligns with the original release (based on compatibility)Potentially Acceptable:
Fixes so codebase works with newly released distros (only in the first six months after a given release series first releases)
Bug fix only version upgrades for upstreams with a good stable process
Quoted 6 lines
So if you could tag any patches for dunfell LTS with [dunfell] in the subject and let me know which of the above categories the patch falls into I will be a happy maintainer ;-)
Steve
Understood, I don't think it fits any of those, so lets keep this one off Dunfell for now.
Thanks Steve
Cheers,
Alejandro
Quoted 46 lines
Quoted 12 lines · Patchwork
== Series Details ==
Series: newlib: Upgrade to latest yearly release 3.3.0
Revision: 1
URL : https://patchwork.openembedded.org/series/23943/
State : failure== Summary ==
Quoted 7 lines
Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:
* Issue Series does not apply on top of target branch
[
test_series_merge_on_head]Quoted 6 lines
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at26eb22191f)If you believe any of these test results are incorrect, please reply to
the
Quoted 1 line
mailing list ([email protected]) raising your
concerns.
Quoted 1 line
Otherwise we would appreciate you correcting the issues and submitting a
new
Quoted 1 line
version of the patchset if applicable. Please ensure you add/increment
the
Quoted 1 line
version number when sending the new version (i.e. [PATCH] -> [PATCH v2]
->
Quoted 4 lines
[PATCH v3] -> ...).
---
Guidelines:https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Quoted 5 lines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe