https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-games/aseprite-1.3.5 fails to compile. Discovered on: amd64 (internal ref: tinderbox_musl) System: MUSL-SYSTEM (https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#MUSL) Info about the issue: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CF0014
Created attachment 896954 [details] build.log build log and emerge --info
Error(s) that match a know pattern in addition to what has been reported in the summary: FAILED: clone_strings-populate-prefix/src/clone_strings-populate-stamp/clone_strings-populate-download /var/tmp/portage/dev-games/aseprite-1.3.5/work/aseprite-1.3.5_build/_deps/clone_strings-subbuild/clone_strings-populate-prefix/src/clone_strings-populate-stamp/clone_strings-populate-download fatal: unable to access 'https://github.com/aseprite/strings.git/': Could not resolve host: github.com
Try disable network-sandbox (FEATURES="-network-sandbox in make.conf) It is work for me
(In reply to kurosuminowa from comment #3) > Try disable network-sandbox (FEATURES="-network-sandbox in make.conf) > It is work for me Please dont disable the network-sandbox globally. If you **have to** use package.env and do it per package. Even so the upstream solution is in the linked issue. Either -DFETCHCONTENT_FULLY_DISCONNECTED:BOOL=ON or https://github.com/aseprite/aseprite/commit/064ddef1901b69c45a40a396b7444769e7fbb4c4
Created attachment 899330 [details, diff] Patch to avoid the clone strings issue Thanks Alfred!
Comment on attachment 899330 [details, diff] Patch to avoid the clone strings issue Firstable, let me express my apologies because of my poor English. Thanks to Alfred Wingate, I was be able to make an ebuild patch in order to avoid the compilation issue. Just download the patch file and save it into (if the directories path doesn't exists, just create it): /etc/portage/patches/dev-games/aseprite-1.3.5/
Thanks @Strong1983, this worked!
Yes, this patch works. I don't know why the clone fails as the repo is there, maybe it should be part of the SRC_URI?