16004 2025-10-14 22:19:46 +0000 Yocto Compatible Submission for meta-erlang 2025-11-13 01:43:13 +0000 1 1 6 Yocto Project Subprojects Yocto Project Compatible yocto-project-compatible-requests 3 x86 Multiple RESOLVED FIXED Needs TSC Review Undecided normal --- 1 mhalstead operations JPEWhacker richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 102936 0 mhalstead 2025-10-14 22:19:46 +0000 Organization/Company Name meta-erlang Organization URL https://meta-erlang.github.io/ Contact Name João Henrique Ferreira de Freitas Contact Email joaohf@gmail.com Layer / Product Name meta-erlang Layer URL https://github.com/meta-erlang/meta-erlang Layer / Product Description (180 character limit) The meta-erlang layer provides support for Erlang/OTP (https://www.erlang.org) and Elixir (https://elixir-lang.org) programming languages for use with OpenEmbedded and/or the Yocto Project build system. Not only the two programming languages are supported but also recipes example of how to integration applications written in Erlang/Elixir into YP/OE. Moreover, this layer provides recipes for common Erlang world applications like RabbitMQ, Riak, couchdb and development tools as well. The submitter is a current Yocto Project member (Platinum, Gold, or Silver level), or the submission is being sponsored* by a Yocto Project member or OpenEmbedded (please state which member or indicate OpenEmbedded below). Yes All publicly accessible layers being submitted are listed in the OpenEmbedded Layers index (http://layers.openembedded.org). Yes All layers in the submission contain a SECURITY* file which details how and where to report any security issue arising with the layer. Yes All layers build without errors against OpenEmbedded-Core, with only the required dependencies listed in their README file? Yes All submitted layers only access the network during do_fetch and only use bitbake fetcher APIs for source components during builds so that source mirroring code functions correctly and software manifests are fully complete. Yes Inclusion of any layer in the submission does not change the behavior/configuration of the overall system without the user explicitly opting into those changes No All layers have successfully passed testing with yocto-check-layer Yes Any BSP layers contained follow the format defined in the Yocto Project Board Support Package (BSP) Developers Guide No Hardware support, configuration (distro) policy, and recipe metadata are separated into different layers which do not depend on each other. Yes If the submission includes build system functionality, BitBake and OpenEmbedded-Core are included as components to provide that and can be clearly identified and isolated. Yes Any patches applied to BitBake and OpenEmbedded-Core (if present) have been submitted to the open source community using the upstream review process for the component Yes The submitter attests they are supporting and promoting the OpenEmbedded architecture, layer model, and BSP format. The submitter attests to working towards and supporting the aims and objectives of the Yocto Project including: Decreasing the fragmentation of embedded ecosystem. Focusing around a common shared set of tools, formats and best practices. Avoiding multiple groups of people repeating the same work. Aiming for one set of great tools rather than multiple tools with drawbacks. The submitter attests to making visible contributions to OpenEmbedded and Yocto Project components. Yes The submitter acknowledges the following recommendations: Ideally Linux kernel versions should be based around Yocto Project kernel version. Submitted layers should build with the standard OE-Core toolchain without modification. Submitted layers should add testing and promote automated testing and CI to ensure the best end user experience. Test results for the submission should be published in a format compatible with resulttool to allow for test result interchange and comparison and to document the supported configurations. Yes Comments/Explanation I did not have yet a test report showing the combinations of layers, recipes and machines. Even though, when testing, I usually explore some combinations of machines. 103094 1 JPEWhacker 2025-10-27 16:02:06 +0000 I ran `yocto-check-layer` on master of meta-erlang and got the following errors: INFO: Detected layers: INFO: meta-erlang: LayerType.SOFTWARE, /yocto/meta-erlang INFO: INFO: Setting up for meta-erlang(LayerType.SOFTWARE), /yocto/meta-erlang INFO: Getting initial bitbake variables ... INFO: Getting initial signatures ... INFO: Adding layer meta-erlang INFO: Starting to analyze: meta-erlang INFO: Distro: nodistro INFO: ---------------------------------------------------------------------- INFO: skipped "BSPCheckLayer: Layer meta-erlang isn't BSP one." INFO: test_layerseries_compat (common.CommonCheckLayer) INFO: ... ok INFO: test_parse (common.CommonCheckLayer) INFO: ... ok INFO: test_patches_upstream_status (common.CommonCheckLayer) INFO: ... ok INFO: test_readme (common.CommonCheckLayer) INFO: ... ok INFO: test_security (common.CommonCheckLayer) INFO: ... FAIL INFO: Traceback (most recent call last): File "/yocto/openembedded-core/scripts/lib/checklayer/cases/common.py", line 70, in test_security self.assertTrue(filename, msg="Layer doesn't contain a SECURITY.md file.") AssertionError: None is not true : Layer doesn't contain a SECURITY.md file. INFO: test_show_environment (common.CommonCheckLayer) INFO: ... ok INFO: test_signatures (common.CommonCheckLayer) INFO: ... ok INFO: test_world (common.CommonCheckLayer) INFO: ... ERROR INFO: Traceback (most recent call last): File "/yocto/openembedded-core/scripts/lib/checklayer/cases/common.py", line 90, in test_world get_signatures(self.td['builddir'], failsafe=False) File "/yocto/openembedded-core/scripts/lib/checklayer/__init__.py", line 315, in get_signatures check_command('Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities.', File "/yocto/openembedded-core/scripts/lib/checklayer/__init__.py", line 287, in check_command raise RuntimeError(msg) RuntimeError: Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities. Command: BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS BB_SIGNATURE_HANDLER" BB_SIGNATURE_HANDLER="OEBasicHash" bitbake -S lockedsigs world Output: NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection (#1)... (09:55:51.578187) Loading cache...done. Loaded 2051 entries from dependency cache. NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'snappy' (but /yocto/meta-erlang/recipes-database/riak/riak_3.2.5.bb, /yocto/meta-erlang/recipes-connectivity/vernemq/vernemq_1.13.0.bb DEPENDS on or otherwise requires it) ERROR: Required build target 'meta-world-pkgdata' has no buildable providers. Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'riak', 'snappy'] Summary: There were 2 ERROR messages, returning a non-zero exit code. INFO: test_world_inherit_class (common.CommonCheckLayer) INFO: ... FAIL INFO: Traceback (most recent call last): File "/yocto/openembedded-core/scripts/lib/checklayer/cases/common.py", line 105, in test_world_inherit_class self.fail('\n'.join(msg)) AssertionError: Layer meta-erlang failed additional checks from yocto-check-layer.bbclass See below log for specific recipe parsing errors: Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities. Command: BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS BB_SIGNATURE_HANDLER" BB_SIGNATURE_HANDLER="OEBasicHash" BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS INHERIT" INHERIT="yocto-check-layer" bitbake -S lockedsigs world Output: NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection (#1)... (09:55:57.798989) Loading cache...done. Loaded 2051 entries from dependency cache. NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'snappy' (but /yocto/meta-erlang/recipes-database/riak/riak_3.2.5.bb, /yocto/meta-erlang/recipes-connectivity/vernemq/vernemq_1.13.0.bb DEPENDS on or otherwise requires it) ERROR: Required build target 'meta-world-pkgdata' has no buildable providers. Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'riak', 'snappy'] Summary: There were 2 ERROR messages, returning a non-zero exit code. INFO: skipped "DistroCheckLayer: Layer meta-erlang isn't Distro one." INFO: ====================================================================== INFO: ERROR: test_world (common.CommonCheckLayer) INFO: ---------------------------------------------------------------------- INFO: Traceback (most recent call last): File "/yocto/openembedded-core/scripts/lib/checklayer/cases/common.py", line 90, in test_world get_signatures(self.td['builddir'], failsafe=False) File "/yocto/openembedded-core/scripts/lib/checklayer/__init__.py", line 315, in get_signatures check_command('Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities.', File "/yocto/openembedded-core/scripts/lib/checklayer/__init__.py", line 287, in check_command raise RuntimeError(msg) RuntimeError: Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities. Command: BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS BB_SIGNATURE_HANDLER" BB_SIGNATURE_HANDLER="OEBasicHash" bitbake -S lockedsigs world Output: NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection (#1)... (09:55:51.578187) Loading cache...done. Loaded 2051 entries from dependency cache. NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'snappy' (but /yocto/meta-erlang/recipes-database/riak/riak_3.2.5.bb, /yocto/meta-erlang/recipes-connectivity/vernemq/vernemq_1.13.0.bb DEPENDS on or otherwise requires it) ERROR: Required build target 'meta-world-pkgdata' has no buildable providers. Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'riak', 'snappy'] Summary: There were 2 ERROR messages, returning a non-zero exit code. ====================================================================== INFO: FAIL: test_security (common.CommonCheckLayer) INFO: ---------------------------------------------------------------------- INFO: Traceback (most recent call last): File "/yocto/openembedded-core/scripts/lib/checklayer/cases/common.py", line 70, in test_security self.assertTrue(filename, msg="Layer doesn't contain a SECURITY.md file.") AssertionError: None is not true : Layer doesn't contain a SECURITY.md file. INFO: ====================================================================== INFO: FAIL: test_world_inherit_class (common.CommonCheckLayer) INFO: ---------------------------------------------------------------------- INFO: Traceback (most recent call last): File "/yocto/openembedded-core/scripts/lib/checklayer/cases/common.py", line 105, in test_world_inherit_class self.fail('\n'.join(msg)) AssertionError: Layer meta-erlang failed additional checks from yocto-check-layer.bbclass See below log for specific recipe parsing errors: Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities. Command: BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS BB_SIGNATURE_HANDLER" BB_SIGNATURE_HANDLER="OEBasicHash" BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS INHERIT" INHERIT="yocto-check-layer" bitbake -S lockedsigs world Output: NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection (#1)... (09:55:57.798989) Loading cache...done. Loaded 2051 entries from dependency cache. NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'snappy' (but /yocto/meta-erlang/recipes-database/riak/riak_3.2.5.bb, /yocto/meta-erlang/recipes-connectivity/vernemq/vernemq_1.13.0.bb DEPENDS on or otherwise requires it) ERROR: Required build target 'meta-world-pkgdata' has no buildable providers. Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'riak', 'snappy'] Summary: There were 2 ERROR messages, returning a non-zero exit code. ---------------------------------------------------------------------- INFO: Ran 9 tests in 45.415s INFO: FAILED INFO: (failures=2, errors=1, skipped=2) INFO: INFO: Summary of results: INFO: INFO: meta-erlang ... FAIL 103262 2 operations 2025-11-13 01:43:13 +0000 Complete- sending to advocacy