I wanted to try the current high watermark, 2.3, or wings. There is contained in the Makefile for the wings project two (2) git clone statements to dependency projects: https://github.com/tonyrog/cl.git and https://github.com/dgud/libigl.git Gentoo's sandbox which prevents lower level fetches causes the git clones to fail. Reference: https://devmanual.gentoo.org/general-concepts/sandbox/index.html Otherwise, I was able to stage the project and successfully compile it on my own by adding dev-util/rebar. Installing wings is not critical for me (as I can do so outside of portage), but I thought I would document what lies ahead for whoever takes up the maintenance of this package, if at all. Reproducible: Always Steps to Reproduce: 1. emerge media-gfx/wings-2.3 Actual Results: make[1]: Entering directory '/var/tmp/portage/media-gfx/wings-2.3/work/wings-2.3' git -c advice.detachedHead=false clone --depth 1 -b 3.3.7 https://github.com/eigenteam/eigen-git-mirror.git _deps/eigen Cloning into '_deps/eigen'... fatal: unable to access 'https://github.com/eigenteam/eigen-git-mirror.git/': Could not resolve host: github.com make[1]: *** [Makefile:150: _deps/eigen] Error 128 make[1]: Leaving directory '/var/tmp/portage/media-gfx/wings-2.3/work/wings-2.3' make[3]: Nothing to be done for 'common'. make[1]: *** Waiting for unfinished jobs.... make[1]: Entering directory '/var/tmp/portage/media-gfx/wings-2.3/work/wings-2.3' git -c advice.detachedHead=false clone --depth 1 -b master https://github.com/dgud/libigl.git _deps/libigl Cloning into '_deps/libigl'... fatal: unable to access 'https://github.com/dgud/libigl.git/': Could not resolve host: github.com make[1]: *** [Makefile:144: _deps/libigl] Error 128 make[1]: Leaving directory '/var/tmp/portage/media-gfx/wings-2.3/work/wings-2.3' make: *** [Makefile:27: opt] Error 2 [31;01m*[0m ERROR: media-gfx/wings-2.3::local failed (compile phase): [31;01m*[0m emake failed Expected Results: successful build. Here are the relevent lines from the Makefile[1]: jlpoole@ryzdesk /usr/local/src/wings $ cat -n Makefile |grep clone 128 GIT_FLAGS = -c advice.detachedHead=false clone --depth 1 jlpoole@ryzdesk /usr/local/src/wings $ cat -n Makefile |grep git 89 git archive --format=tar \ 119 CL_REPO = https://github.com/tonyrog/cl.git 120 IGL_REPO = https://github.com/dgud/libigl.git 121 EIGEN_REPO = https://github.com/eigenteam/eigen-git-mirror.git 138 git $(GIT_FLAGS) -b $(CL_VER) $(CL_REPO) _deps/cl 144 git $(GIT_FLAGS) -b $(IGL_VER) $(IGL_REPO) _deps/libigl 150 git $(GIT_FLAGS) -b $(EIGEN_VER) $(EIGEN_REPO) _deps/eigen jlpoole@ryzdesk /usr/local/src/wings $ Here's my custom ebuild diff: ryzdesk /var/db/repos/local/media-gfx/wings # diff wings-2.2.6.1.ebuild wings-2.3.ebuild 14c14,21 < --- > # > # 3/16/24 jlpoole: rebar3 per Unix build instructions > # added sci-libs/libigl because that package is a dependency > # on something wings brings in and the command it "git clone" > # which fails for lack of authentication. So we'll bring th > # package in the Gentoo way so there should not be a need > # for installing a dependency. > # 20a28,29 > >=dev-util/rebar-3 > 23a33 > sci-libs/libigl ryzdesk /var/db/repos/local/media-gfx/wings #
Created attachment 888002 [details] Build log
ebuilds must not fetch sources themselves unless PROPERTIES="live" is set
(In reply to Mike Gilbert from comment #2) > ebuilds must not fetch sources themselves unless PROPERTIES="live" is set I don't think it's INVALID as a bug? It's a heads-up for a bump which ahsn't happened yet.
(In reply to Sam James from comment #3) > (In reply to Mike Gilbert from comment #2) > > ebuilds must not fetch sources themselves unless PROPERTIES="live" is set > > I don't think it's INVALID as a bug? It's a heads-up for a bump which ahsn't > happened yet. Sam is correct. Although there currently is not a maintainer, I just wanted to lay the groundwork in Bug to help whomever might assume the role. Probably, the upstream owner should be contacted and persuaded not to pull in other repositories in his Makefile. Thanks Sam.
> Probably, the upstream owner should be contacted and persuaded not to pull in other repositories in his Makefile. Thanks Sam. Actually the makefile can just be patched by the ebuild in order to remove the repositories from the Makefile, and then specific commits or tagged commits of those repositories could be added to the Portage SRC_URI as tar.gz.
(In reply to benoit.dufour from comment #5) > > Probably, the upstream owner should be contacted and persuaded not to pull in other repositories in his Makefile. Thanks Sam. > Actually the makefile can just be patched by the ebuild in order to remove > the repositories from the Makefile, and then specific commits or tagged > commits of those repositories could be added to the Portage SRC_URI as > tar.gz. Well, yeah. There's a lot of different options in theory, but what John said is still right. They should be persuaded to not do that.
