Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 714022 - www-apps/hugo-0.62 various "network is unreachable" errors
Summary: www-apps/hugo-0.62 various "network is unreachable" errors
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords: PullRequest
Depends on:
Blocks:
 
Reported: 2020-03-22 18:07 UTC by Dale Lukas Peterson
Modified: 2020-04-21 08:17 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info '=www-apps/hugo-0.62.0::gentoo' (emerge_info.txt,6.40 KB, text/plain)
2020-03-22 18:07 UTC, Dale Lukas Peterson
Details
emerge -pqv '=www-apps/hugo-0.62.0::gentoo' (emerge_pqv.txt,71 bytes, text/plain)
2020-03-22 18:07 UTC, Dale Lukas Peterson
Details
/var/tmp/portage/www-apps/hugo-0.62.0/temp/build.log (build.log,25.53 KB, text/x-log)
2020-03-22 18:08 UTC, Dale Lukas Peterson
Details
/var/tmp/portage/www-apps/hugo-0.62.0/temp/environment (environment,59.33 KB, text/plain)
2020-03-22 18:08 UTC, Dale Lukas Peterson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dale Lukas Peterson 2020-03-22 18:07:12 UTC
Created attachment 624536 [details]
emerge --info '=www-apps/hugo-0.62.0::gentoo'

A number of the hugo dependencies are failing to download, during emerge hugo, I see a lot of things like:

# get https://proxy.golang.org/github.com/spf13/cobra/@v/v0.0.4-0.20190321000552-67fc4837d267.mod                                                                                                                                 
# get https://proxy.golang.org/github.com/markbates/inflect/@v/v0.0.0-20171215194931-a12c3aec81a6.mod: Get "https://proxy.golang.org/github.com/markbates/inflect/@v/v0.0.0-20171215194931-a12c3aec81a6.mod": dial tcp: lookup pro
xy.golang.org on 192.168.50.8:53: dial udp 192.168.50.8:53: connect: network is unreachable                                                                                                                                       
# get https://proxy.golang.org/github.com/%21burnt%21sushi/toml/@v/v0.3.1.mod: Get "https://proxy.golang.org/github.com/%21burnt%21sushi/toml/@v/v0.3.1.mod": dial tcp: lookup proxy.golang.org on 192.168.50.8:53: dial udp 192.1
68.50.8:53: connect: network is unreachable
Comment 1 Dale Lukas Peterson 2020-03-22 18:07:58 UTC
Created attachment 624538 [details]
emerge -pqv '=www-apps/hugo-0.62.0::gentoo'
Comment 2 Dale Lukas Peterson 2020-03-22 18:08:21 UTC
Created attachment 624540 [details]
/var/tmp/portage/www-apps/hugo-0.62.0/temp/build.log
Comment 3 Dale Lukas Peterson 2020-03-22 18:08:43 UTC
Created attachment 624542 [details]
/var/tmp/portage/www-apps/hugo-0.62.0/temp/environment
Comment 4 Kai Krakow 2020-03-22 18:49:32 UTC
I can confirm... Sorting the log line alphabetically reveals that all dependencies are failing.
Comment 5 Kai Krakow 2020-03-22 18:50:42 UTC
(In reply to Kai Krakow from comment #4)
> I can confirm... Sorting the log line alphabetically reveals that all
> dependencies are failing.

Before finding this report, I found this which may be related (but older):
https://bugs.gentoo.org/693992
Comment 6 Dale Lukas Peterson 2020-03-24 04:10:39 UTC
Is there anything about the hugo .ebuild files that is fundamentally different about than other go packages that don't exhibit this issue? I took a look at a few and nothing stood out, but my search was by no means exhaustive. For what it is worth, manually downloading the same tar.gz file from github, extracting it, and running `mkdir bin && go build -o bin/hugo` succeeded without issue, notably it fetched all the packages that emerge fetch fails on.
Comment 7 Kai Krakow 2020-03-24 17:12:58 UTC
(In reply to Dale Lukas Peterson from comment #6)
> Is there anything about the hugo .ebuild files that is fundamentally
> different about than other go packages that don't exhibit this issue? I took
> a look at a few and nothing stood out, but my search was by no means
> exhaustive. For what it is worth, manually downloading the same tar.gz file
> from github, extracting it, and running `mkdir bin && go build -o bin/hugo`
> succeeded without issue, notably it fetched all the packages that emerge
> fetch fails on.

In my comment https://bugs.gentoo.org/693992#c8 I think that it could be a sandboxing issue...
Comment 8 Dale Lukas Peterson 2020-03-24 19:37:29 UTC
Yep, I saw that and suspect you are correct. Any idea how to go about resolving the issue, or know who might know how? It is weird to me that this issue doesn't manifest with other go packages -- or maybe it does?
Comment 9 Kai Krakow 2020-03-24 21:28:39 UTC
Actually, I've seen this with all go builds lately, then suddenly some of them worked, except hugo. Maybe the build system of hugo is just different?

Apparently, all elogs are already rotated out... So I cannot check back in for git logs in portage around that date.

But as an example, here's syncthing from emerge.log which worked, then failed (missing "Merging"), then worked again:

# cat /var/log/emerge.log | awk -F: '/(Cleaning|Merging|Compiling).*syncthing/ { ts=strftime("%F %H:%M:%S",$1); sub($1,""); print ts $0 }'

2020-02-14 09:47:20:  === (20 of 251) Cleaning (net-p2p/syncthing-1.3.4::/usr/portage/net-p2p/syncthing/syncthing-1.3.4.ebuild)
2020-02-14 09:47:21:  === (20 of 251) Compiling/Packaging (net-p2p/syncthing-1.3.4::/usr/portage/net-p2p/syncthing/syncthing-1.3.4.ebuild)
2020-02-14 09:47:46:  === (20 of 251) Merging (net-p2p/syncthing-1.3.4::/usr/portage/net-p2p/syncthing/syncthing-1.3.4.ebuild)
2020-02-14 09:47:57:  === (20 of 251) Post-Build Cleaning (net-p2p/syncthing-1.3.4::/usr/portage/net-p2p/syncthing/syncthing-1.3.4.ebuild)

2020-03-08 13:08:32:  === (6 of 19) Cleaning (net-p2p/syncthing-1.3.4::/usr/portage/net-p2p/syncthing/syncthing-1.3.4.ebuild)
2020-03-08 13:08:33:  === (6 of 19) Compiling/Packaging (net-p2p/syncthing-1.3.4::/usr/portage/net-p2p/syncthing/syncthing-1.3.4.ebuild)

2020-03-08 13:52:24:  === (1 of 3) Cleaning (net-p2p/syncthing-1.3.4::/usr/portage/net-p2p/syncthing/syncthing-1.3.4.ebuild)
2020-03-08 13:52:24:  === (1 of 3) Compiling/Packaging (net-p2p/syncthing-1.3.4::/usr/portage/net-p2p/syncthing/syncthing-1.3.4.ebuild)

2020-03-09 09:33:37:  === (3 of 9) Cleaning (net-p2p/syncthing-1.3.4::/usr/portage/net-p2p/syncthing/syncthing-1.3.4.ebuild)
2020-03-09 09:33:38:  === (3 of 9) Compiling/Packaging (net-p2p/syncthing-1.3.4::/usr/portage/net-p2p/syncthing/syncthing-1.3.4.ebuild)

2020-03-10 20:48:55:  === (2 of 16) Cleaning (net-p2p/syncthing-1.3.4-r1::/usr/portage/net-p2p/syncthing/syncthing-1.3.4-r1.ebuild)
2020-03-10 20:48:55:  === (2 of 16) Compiling/Packaging (net-p2p/syncthing-1.3.4-r1::/usr/portage/net-p2p/syncthing/syncthing-1.3.4-r1.ebuild)
2020-03-10 20:49:23:  === (2 of 16) Merging (net-p2p/syncthing-1.3.4-r1::/usr/portage/net-p2p/syncthing/syncthing-1.3.4-r1.ebuild)
2020-03-10 20:49:38:  === (2 of 16) Post-Build Cleaning (net-p2p/syncthing-1.3.4-r1::/usr/portage/net-p2p/syncthing/syncthing-1.3.4-r1.ebuild)

So, something was broken between the first two, and fixed between the last two, at least for syncthing.
Comment 10 Kai Krakow 2020-03-24 21:43:31 UTC
This bump to -r1 seems to have fixed syncthing for me:
https://github.com/gentoo/gentoo/commit/99a8cd3309a44c63837d5e62df67f78276836945

The news is "EGO_SUM" while it previously used "EGO_VENDOR".

BTW: hugo does use neither, so it's probably really a sandbox issue: Ebuilds should not download stuff, only portage is allowed to download build artifacts.

Let's cross-check:

# genlop portage
     Mon Mar  2 20:49:52 2020 >>> sys-apps/portage-2.3.89
     Wed Mar  4 22:00:38 2020 >>> sys-apps/portage-2.3.89-r1

Yep, portage bumped to -r1 between the first two syncthing merges from my log. So maybe it hardened the build environment to not download from network between those two?

But this was a simple bugfix and shouldn't have such an effect:
https://github.com/gentoo/gentoo/commit/4a96d5d727207cfd5ce35d9c897e59440ed3f1ce

I'm left somewhat clueless...
Comment 11 Larry the Git Cow gentoo-dev 2020-04-21 08:17:44 UTC
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(+)