In commit 9626e8a2c8 ("libgpiod: update to v2.2"), "gpio-manager" user
and "gpio" group were added, add them to the static ID lists for the
reproducibility test.
Fixes this error from AB[0]:
2025-03-15 10:40:07,437 - oe-selftest - INFO - ERROR: Nothing RPROVIDES 'libgpiod-gpiosim' (but /srv/pokybuild/yocto-worker/reproducible-meta-oe/build/meta-openembedded/meta-python/recipes-devtools/python/python3-gpiod_2.3.0.bb RDEPENDS on or otherwise requires it)
2025-03-15 10:40:07,437 - oe-selftest - INFO - libgpiod RPROVIDES libgpiod-gpiosim but was skipped: Recipe libgpiod, package libgpiod-manager: system username "gpio-manager" does not have a static ID defined. Add gpio-manager to one of these files: /srv/pokybuild/yocto-worker/reproducible-meta-oe/build/build/build-st-meta-python/build-st/meta-selftest/files/static-passwd /srv/pokybuild/yocto-worker/reproducible-meta-oe/build/meta-openembedded/meta-oe/files/static-passwd-meta-oe
[0]: https://autobuilder.yoctoproject.org/valkyrie/#/builders/87/builds/36/steps/40/logs/stdio
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The influxdb group is used by the influxdb recipe and created by default
by the useradd command.
Also, align static passwd file to the USERADD_PARAM in the influxdb
recipe and add the missing newline at end of file.
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Current recipe does impose UID=GID=28 in the recipe code.
Change postgres static ID to match in order to avoid a warning in
reproducibility tests.
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
In order to pass reproducible tests, recipes that use the
useradd class must have static ids configured.
Signed-off-by: Fabien Thomas <fabien.thomas@smile.fr>
Reviewed-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The recipes that are using waf-samba were all
moved to meta-networking, so move the bbclass
and related cross-answers files as well.
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
--cross-execute uses qemu to run cross-compiled binaries,
it works fine for qemu supported targets, but it definitely
will fail if the target is not supported by qemu. So we need
to use the cross-answers option.
Added three methods and set 'answer' as default:
1. answers:
Only --cross-answers - try the cross-answers file, and if
there's no corresponding answer, add to the file and mark
the configure process as unfinished.
2. exec:
Only --cross-execute - get the answer from cross-execute,
an emulator (qemu) is used to run cross-compiled binaries.
3. both:
Try the cross-answers file first, and if there is no
corresponding answer, use cross-execute to get an answer,
and add that answer to the file.
The cross files in are all generated by qemu when the 'both'
mode is enabled, and are placed in a common directory
LAYERDIR/files/waf-cross-answers which is set as
WAF_CROSS_ANSWERS_PATH in layer.conf of meta-oe,
so that we don't have to put copies of them for each
package (there are 5 packages inerit waf-samba for now)
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
