mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-27 08:41:13 -07:00
ScottW514
cf7b51fb32
The lock held meta-openglow at dd8f74c, three commits behind the pushed scarthgap head, so a build from this repository resolved the old BSP and none of the component pins just bumped there. Moves that one entry to 31c5205. poky, meta-openembedded, meta-freescale and meta-freescale-distro keep their commits: the platform is deliberately unchanged, so the build exercises the pins and nothing else. Proven: bitbake -c fetch and -c populate_lic over forgectrl, grblhal-glowforge, gfcloud, gfhome, python3-ffmachine, python3-gfhardware, python3-gfutilities and kernel-module-glowforge all succeed - the four LIC_FILES_CHKSUM values written ahead of their pins now match the fetched license text. A full bitbake forgefirm-image forgefirm-image-dev run completed, 5841 tasks, no errors, and the release rootfs manifest carries forgectrl 0.1.26, grblhal-glowforge 0.1.18, kernel-module-glowforge 0.0.6, python3-gfutilities 0.9.19+git0+0a93ebf30b and gfcloud/gfhome/python3-ffmachine 0.1.30+git0+6cc4f45d31. Release rootfs 125 MiB, inside the 195 MiB gate.
15 lines
416 B
YAML
15 lines
416 B
YAML
header:
|
|
version: 14
|
|
overrides:
|
|
repos:
|
|
poky:
|
|
commit: 70ed6f677234d32198371a030178d2f272cf2d94
|
|
meta-openembedded:
|
|
commit: b0c2c648a1af89e7a8dd4c2ec841f3bc0ed0ccb9
|
|
meta-freescale:
|
|
commit: b699d026506a6fc402e03afb432dcabd3d81c7ab
|
|
meta-freescale-distro:
|
|
commit: b9d6a5d9931922558046d230c1f5f4ef6ee72345
|
|
meta-openglow:
|
|
commit: 31c52050bc70776c4ecdb5fcaa096a69b9c08e3b
|