I opened a support ticket with DO (Ticket #10402365) since I was able to repro on their command line.
It’s either something in their DNS resolution, or there’s some new packaging requirements that yunohost isn’t satisfying as a vendor with github for this (and other) apps.
Anyway, I’ll post an update when I hear back - thanks!
Following the link that DO sent, I disabled ipv6 in the node’s netplan and now I am forcing all traffic through ipv4, the peertube installation went without a problem.
Summarize:
Edit /etc/netplan/50-cloud-init.yaml
Look for:
network->ethernets->eth0->addresses
And in this block, comment-out the IPv6 address:
I have also had the same issue on one of my servers. Strangely, this is the first time it happened for this server that is online since more than 6 months.
Anyway, I used another hack. Since yunohost update uses wget, I have created a “.bash_aliases” file in “/root” in which I have added alias wget="wget --inet4-only". This forced wget to use ipv4 and fixed the issue immediately.
Yeah - I couldn’t depend on wget being the only exposure to the problem so, for me, the solution is to fix at the system level and then just wait for the techno-wonks to work-out a long-term solution.