Resolving wdl1.pcfg.cache.wpscdn.com... failed: Temporary failure in name resolution. wget: unable to resolve host address wdl1.pcfg.cache.wpscdn.com’ * Fetch failed for 'app-office/wps-office-11.1.0.10976', Log file: * '/var/log/portage/app-office:wps-office-11.1.0.10976:20220609-071651.log' !!! Couldn't download 'wps-office_11.1.0.10976.XA_amd64.deb'. Aborting. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-j4-20220607-150005 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-12.1.1 * clang/llvm (if any): clang version 14.0.4 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/14/bin /usr/lib/llvm/14 14.0.4 Python 3.9.13 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.61.0 [2] rust-1.61.0 * The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: [1] php8.1 * HEAD of ::gentoo commit 4fccf78e426e22791969ad22b18a062a74f304eb Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Thu Jun 9 06:48:03 2022 +0000 2022-06-09 06:48:02 UTC emerge -qpvO app-office/wps-office [ebuild N ] app-office/wps-office-11.1.0.10976
Created attachment 783728 [details] emerge-info.txt
Created attachment 783731 [details] app-office:wps-office-11.1.0.10976:20220609-071651.log
Created attachment 783734 [details] emerge-history.txt
Created attachment 783737 [details] etc.portage.tar.bz2
it works for me now
(In reply to Pacho Ramos from comment #5) > it works for me now yep, a rare case, where DNS seems not to work for a particular hosts at the tinderbox: dig wdl1.pcfg.cache.wpscdn.com ;; connection timed out; no servers could be reached Anyway, not a bug.
FWIW that FQDN seems to be messed wrt to DNSSEC: https://dnsviz.net/d/wdl1.pcfg.cache.wpscdn.com/dnssec/
The package is hosted at a domain with a malformed working DNS: Whilst the DNS resolution works from most locations there are network segments from where a DNS request seems to be blocked: https://github.com/NLnetLabs/unbound/issues/694#issuecomment-1156343925
Personally I still don't understand what unbound does differently than the other DNS servers. It works fine with Google, Cloudfare, Orange, Movistar, Vodafone... well... I still couldn't see other service failing. Also we are using exactly the same address as used by Slackware, Arch or FreeBSD without issues :/ Personally I would switch to other DNS... also, at least in my setup, I set multiple DNSs to fallback in the case of issues
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=74f499a18b521c684273875f15c4e0c3ffdb5df3 commit 74f499a18b521c684273875f15c4e0c3ffdb5df3 Author: Pacho Ramos <pacho@gentoo.org> AuthorDate: 2022-10-28 14:57:29 +0000 Commit: Pacho Ramos <pacho@gentoo.org> CommitDate: 2022-10-28 15:15:24 +0000 app-office/wps-office: Fix crash due to glibc version conflict Also drop file requiring systemd (#813138) as gentoo-zh overlay is doing Try a differrent SRC_URI (same as gentoo-zh overlay) as current one fails for some DNS resolvers Closes: https://bugs.gentoo.org/813138 Bug: https://bugs.gentoo.org/850727 Closes: https://bugs.gentoo.org/878451 Signed-off-by: Pacho Ramos <pacho@gentoo.org> app-office/wps-office/Manifest | 1 + .../wps-office/wps-office-11.1.0.11664-r2.ebuild | 102 +++++++++++++++++++++ 2 files changed, 103 insertions(+)
it seems current SRC-URI is more reliable, right?