>>> Compiling source in /var/tmp/portage/www-apps/hugo-0.48/work/hugo-0.48 ... /var/tmp/portage/www-apps/hugo-0.48/work/hugo-0.48/src/github.com/gohugoio/hugo /var/tmp/portage/www-apps/hugo-0.48/work/hugo-0.48 go: github.com/BurntSushi/locker@v0.0.0-20171006230638-a6e239ea1c69: Get https://proxy.golang.org/github.com/%21burnt%21sushi/locker/@v/v0.0.0-20171006230638-a6e239ea1c69.mod: dial tcp: lookup proxy.golang.org on 127.0.0.1:53: read udp 127.0.0.1:33497->127.0.0.1:53: read: connection refused * ERROR: www-apps/hugo-0.48::gentoo failed (compile phase): * (no error message) * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-20190909-131515 ------------------------------------------------------------------- Please see the tracker bug for details. gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.13.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm repository timestamp: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Tue, 10 Sep 2019 17:26:09 +0000 emerge -qpvO www-apps/hugo [ebuild N ] www-apps/hugo-0.48 USE="sass"
Created attachment 589648 [details] emerge-info.txt
Created attachment 589650 [details] emerge-history.txt
Created attachment 589652 [details] environment
Created attachment 589654 [details] etc.portage.tbz2
Created attachment 589656 [details] www-apps:hugo-0.48:20190910-175807.log
I have been maintaining www-apps/hugo on my personal overlay for quite some time now, at https://github.com/NuLL3rr0r/gentoo-overlay and it does not have this issue. BTW, 0.48 is too old. You can find v0.58.3 and v0.59.1 there. In case you need a maintainer, I am willing to that.
https://github.com/NuLL3rr0r/gentoo-overlay/tree/master/www-apps/hugo
It's still any issue with 0.62 but the log looks different: mkdir: created directory 'bin' WORK=/var/tmp/portage/www-apps/hugo-0.62.0/temp/go-build914333060 # get https://proxy.golang.org/github.com/%21burnt%21sushi/locker/@v/v0.0.0-20171006230638-a6e239ea1c69.mod # get https://proxy.golang.org/github.com/disintegration/gift/@v/v1.2.1.mod # get https://proxy.golang.org/github.com/%21burnt%21sushi/toml/@v/v0.3.1.mod # get https://proxy.golang.org/github.com/fortytw2/leaktest/@v/v1.3.0.mod # get https://proxy.golang.org/github.com/mitchellh/hashstructure/@v/v1.0.0.mod # get https://proxy.golang.org/github.com/olekukonko/tablewriter/@v/v0.0.0-20180506121414-d4647c9c7a84.mod # get https://proxy.golang.org/google.golang.org/api/@v/v0.5.0.mod # get https://proxy.golang.org/github.com/fsnotify/fsnotify/@v/v1.4.7.mod # get https://proxy.golang.org/github.com/gohugoio/testmod%21builder/mods/@v/v0.0.0-20190520184928-c56af20f2e95.mod # get https://proxy.golang.org/github.com/mattn/go-isatty/@v/v0.0.8.mod # get https://proxy.golang.org/github.com/gohugoio/testmod%21builder/mods/@v/v0.0.0-20190520184928-c56af20f2e95.mod: Get https://proxy.golang.org/github.com/gohugoio/testmod%21builder/mods/@v/v0.0.0-20190520184928-c56af20f2e95.mod: dial tcp [2a00:1450:4001:814::2011]:443: connect: network is unreachable While it seems to work for some modules, it doesn't work for others. For all failing mods, the IP is always the same. I'm not sure if the error occurs locally or if this actually a result from the upstream proxy. But I can confirm that other go packages in portage had the same problem but they seem to be fixed now. This is the only package remaining for me. Testing the URL with curl actually show the URL is working: No error "network is unreachable". So maybe it's a portage sandbox issue? Also, it feels wrong that go packages download additional content during merging: It bypasses portage infrastructure to maintain package integrity, it probably should download these via SRC_URI and properly unpack them in the build directory. Ebuilds should never download stuff while bulding/merging. And that's probably the sandbox issue then?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=38f286fc749350296806ffa70841ab263d913e17 commit 38f286fc749350296806ffa70841ab263d913e17 Author: Kai Krakow <kai@kaishome.de> AuthorDate: 2020-04-19 12:07:46 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2020-04-21 08:17:20 +0000 www-apps/hugo: Bump to 0.69.0 Closes: https://bugs.gentoo.org/670470 Closes: https://bugs.gentoo.org/678980 Closes: https://bugs.gentoo.org/693992 Closes: https://bugs.gentoo.org/714022 Package-Manager: Portage-2.3.89, Repoman-2.3.20 Signed-off-by: Kai Krakow <kai@kaishome.de> Signed-off-by: Joonas Niilola <juippis@gentoo.org> www-apps/hugo/Manifest | 527 +++++++++++++++++++++++++++++++++++ www-apps/hugo/hugo-0.69.0.ebuild | 579 +++++++++++++++++++++++++++++++++++++++ 2 files changed, 1106 insertions(+)
