mrg swiper These are the packages that would be merged, in reverse order: Calculating dependencies ... done! [ebuild R ~] app-emacs/swiper-20200503.1102 >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-emacs/swiper-20200503.1102::melpa >>> Failed to emerge app-emacs/swiper-20200503.1102, Log file: >>> '/var/log/portage/app-emacs:swiper-20200503.1102:20200727-114415.log' >>> Jobs: 0 of 1 complete, 1 failed Load avg: 3.23, 3.22, 2.99 * Package: app-emacs/swiper-20200503.1102 * Repository: melpa * Maintainer: jauhien@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox * Emacs version: 26.3 >>> Unpacking source... --2020-07-27 14:44:16-- http://melpa.org/packages/swiper-20200503.1102.el Resolving melpa.org... failed: Temporary failure in name resolution. wget: unable to resolve host address 'melpa.org' * ERROR: app-emacs/swiper-20200503.1102::melpa failed (unpack phase): * (no error message) * * Call stack: * ebuild.sh, line 125: Called src_unpack * environment, line 1076: Called gs-elpa_src_unpack * environment, line 1028: Called g-sorcery_src_unpack * environment, line 994: Called g-sorcery_fetch * environment, line 987: Called die * The specific snippet of code: * $GSORCERY_FETCH_CMD ${REPO_URI}${SOURCEFILE} || die; * * If you need support, post the output of `emerge --info '=app-emacs/swiper-20200503.1102::melpa'`, * the complete build log and the output of `emerge -pqv '=app-emacs/swiper-20200503.1102::melpa'`. * The complete build log is located at '/var/log/portage/app-emacs:swiper-20200503.1102:20200727-114415.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-emacs/swiper-20200503.1102/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emacs/swiper-20200503.1102/temp/environment'. * Working directory: '/var/cache/distfiles' * S: '/var/tmp/portage/app-emacs/swiper-20200503.1102/work/swiper-20200503.1102' amd64 ~ # FEATURES=-network-sandbox mrg swiper These are the packages that would be merged, in reverse order: Calculating dependencies .... done! [ebuild R ~] app-emacs/swiper-20200503.1102 >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-emacs/swiper-20200503.1102::melpa >>> Installing (1 of 1) app-emacs/swiper-20200503.1102::melpa >>> Jobs: 1 of 1 complete Load avg: 3.69, 3.35, 3.05 >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. * IMPORTANT: 34 config files in '/etc' need updating. * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS * sections of the emerge man page to learn how to update config files. Reproducible: Always
Created attachment 650954 [details] failed build log
Please include emerge --info too.
To be honest, I doubt we can do anything about auto-detecting and disabling network-sandbox when needed. Especially since the network-sandbox is default for security reasons. If there is an alternative to disabling the network-sandbox for gs-elpa generated ebuilds, I am open to suggestions.
Created attachment 651054 [details] emerge --info
(In reply to Brian Dolbec from comment #3) > To be honest, I doubt we can do anything about auto-detecting and disabling > network-sandbox when needed. Especially since the network-sandbox is > default for security reasons. > > If there is an alternative to disabling the network-sandbox for gs-elpa > generated ebuilds, I am open to suggestions. From a user point of view, network-sandbox cancelling requirement is rather new [6 to 8 months IIRC). Maybe this is linked to network-sandbox switch to default. Don't how old this is. Thks 4 ur attention, interest & support.
(In reply to Brian Dolbec from comment #3) > To be honest, I doubt we can do anything about auto-detecting and disabling > network-sandbox when needed. Especially since the network-sandbox is > default for security reasons. > > If there is an alternative to disabling the network-sandbox for gs-elpa > generated ebuilds, I am open to suggestions. Indeed, network-sandbox must be disabled for src_unpack(). Presumably this should be done in g-sorcery.eclass. I'll take a look into it.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/g-sorcery.git/commit/?id=13e68826557ccc22b6968814066f5442ccf67b3c commit 13e68826557ccc22b6968814066f5442ccf67b3c Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2021-05-03 21:24:39 +0000 Commit: Ulrich Müller <ulm@gentoo.org> CommitDate: 2021-05-04 15:48:09 +0000 g-sorcery.eclass: Add live property This will disable the network-sandbox during the unpack phase. Bug: https://bugs.gentoo.org/734080 Signed-off-by: Ulrich Müller <ulm@gentoo.org> g_sorcery/data/g-sorcery.eclass | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6cc2528773c80050f10b73d2e118851ef4a1394b commit 6cc2528773c80050f10b73d2e118851ef4a1394b Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2021-05-04 16:28:26 +0000 Commit: Ulrich Müller <ulm@gentoo.org> CommitDate: 2021-05-04 17:26:03 +0000 app-portage/g-sorcery: Version bump to 0.2.2 Closes: https://bugs.gentoo.org/734080 Package-Manager: Portage-3.0.18, Repoman-3.0.3 Signed-off-by: Ulrich Müller <ulm@gentoo.org> app-portage/g-sorcery/Manifest | 1 + app-portage/g-sorcery/g-sorcery-0.2.2.ebuild | 47 ++++++++++++++++++++++++++++ 2 files changed, 48 insertions(+)
