15683 2024-12-06 17:26:46 +0000 go-vendor.bbclass: avoid QA errors with absolute paths 2026-03-12 15:16:47 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 5.3 All Multiple RESOLVED FIXED Medium minor 5.2 1 pokylinux thomas meta.mr.watcher meta.watcher randy.macleod richard.purdie thomas yoann.congal --- --- Don't know oldest_to_newest 100377 0 pokylinux 2024-12-06 17:26:46 +0000 100378 1 pokylinux 2024-12-06 17:32:43 +0000 https://lists.openembedded.org/g/openembedded-core/message/208434 100379 2 pokylinux 2024-12-06 17:33:32 +0000 https://patchwork.yoctoproject.org/project/oe-core/patch/20241206173119.12422-1-Robert.Berger@ReliableEmbeddedSystems.com/ 100384 3 pokylinux 2024-12-08 22:52:55 +0000 Example which fails without my patch: https://gitlab.com/meta-layers/meta-yocto-training/-/tree/master/recipes-training/golang-helloworld?ref_type=heads Error: ERROR: github.com-robertberger-golangexample-1.0+git-r0 do_populate_sysroot: sstate found an absolute path symlink /workdir/build/multi-v7-ml-debug-training-master/tmp/work/armv7at2hf-neon-resy-linux-gnueabi/github.com-robertberger-golangexample/1.0+git/sysroot-destdir/usr/lib/go/src/github.com/robertberger/golangexample/vendor pointing at /workdir/build/multi-v7-ml-debug-training-master/tmp/work/armv7at2hf-neon-resy-linux-gnueabi/github.com-robertberger-golangexample/1.0+git/git/src/import/vendor. Please replace this with a relative link. 100422 4 randy.macleod 2024-12-12 15:36:34 +0000 Ricahard says that it's better to avoid creating the incorrect symlinks rather than creating them and then fixing them afterwards. 100437 5 pokylinux 2024-12-12 20:07:05 +0000 https://bugzilla.yoctoproject.org/show_bug.cgi?id=15683#c3 should explain it, plus my test case. Please note, that except for the selftests I seem to be the only one using this class in my example: $ grep --include \*.bb --include \*.inc --include \*.bbclass -r go-vendor . ./meta-yocto-training/recipes-training/golang-helloworld/github.com-robertberger-golangexample_git.bb:inherit go-vendor Besides, I am not sure how the selftest does not show this issue. Maybe the test case needs to be improved? "It's better to avoid creating the incorrect symlinks rather than creating them and then fixing them afterwards" Yes sure. The question is who creates them? ;) 100550 6 richard.purdie 2025-01-07 22:23:26 +0000 I've sent a patch to the list which changes go-vendor to create relative symlinks in the first place. 100652 7 pokylinux 2025-01-15 14:19:48 +0000 Just for completeness, here is the patch: https://git.yoctoproject.org/poky/commit/meta/classes/go-vendor.bbclass?id=c323d56244644964d68e012e688b3339492e50c4 102172 8 randy.macleod 2025-06-05 21:06:13 +0000 https://git.openembedded.org/openembedded-core/commit/?id=fc4f589cc7a8e5feba7940ccb244a74bd5f96371 104191 9 thomas 2026-02-07 20:10:09 +0000 Is this patch planned to be applied to the scarthgap branch as well? I ran into the same issue after creating a basic Go recipe using 'recipetool create'. I was about to file a bug for this problem, but I noticed that an existing report already addresses it and that it has been fixed upstream. 104206 10 randy.macleod 2026-02-09 19:20:02 +0000 Hi Thomas, If you think this makes sense as a backport, will you please test it and send an email: https://docs.yoctoproject.org/contributor-guide/submit-changes.html#submitting-changes-to-stable-release-branches If so, please change the status of this defect. Thanks. CC-ing Yoann who maintains the stable branches. 104307 11 thomas 2026-02-14 16:13:05 +0000 Hello Randy, I have submitted the patch after test and validation: https://patchwork.yoctoproject.org/project/oe-core/patch/20260214160806.3043158-1-thomas@bootzero.one/ 104611 12 randy.macleod 2026-03-12 15:16:47 +0000 Fixed by: https://git.openembedded.org/openembedded-core/commit/?h=scarthgap&id=2ef214747b64