Closed misterhsp closed 2 years ago
Looks like a dns issue.
curl: (6) Could not resolve host: raw.githubusercontent.com
it resolves ok here.
$ ping -c5 raw.githubusercontent.com
PING raw.githubusercontent.com (185.199.108.133) 56(84) bytes of data.
64 bytes from cdn-185-199-108-133.github.com (185.199.108.133): icmp_seq=1 ttl=57 time=37.7 ms
64 bytes from cdn-185-199-108-133.github.com (185.199.108.133): icmp_seq=2 ttl=57 time=38.2 ms
64 bytes from cdn-185-199-108-133.github.com (185.199.108.133): icmp_seq=3 ttl=57 time=45.5 ms
64 bytes from cdn-185-199-108-133.github.com (185.199.108.133): icmp_seq=4 ttl=57 time=55.8 ms
64 bytes from cdn-185-199-108-133.github.com (185.199.108.133): icmp_seq=5 ttl=57 time=36.7 ms
--- raw.githubusercontent.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 36.680/42.769/55.845/7.242 ms
Is not a dns issue
wget https://raw.githubusercontent.com/jstasiak/python-zeroconf --2021-10-13 22:19:52-- https://raw.githubusercontent.com/jstasiak/python-zeroconf SSL_INIT Auflösen des Hostnamens raw.githubusercontent.com (raw.githubusercontent.com)… 185.199.110.133, 185.199.108.133, 185.199.109.133, ... Verbindungsaufbau zu raw.githubusercontent.com (raw.githubusercontent.com)|185.199.110.133|:443 … verbunden. HTTP-Anforderung gesendet, auf Antwort wird gewartet … 400 Bad Request 2021-10-13 22:19:53 FEHLER 400: Bad Request.
Is always Bad Request, curl same Problem
If you're building in a sandbox or chroot, maybe you need to give it internet access? Or just follow the recommendation and disable that step in your build. You can install python3-zeroconf instead. If you're not comfortable editing the debian/rules file you could simply change the default in the meson_options.txt file for bundle-zeroconf
.
It looks like 0.36.4 is available on sid, which should work, though I can't guarantee this, as that module is heavily developed and they haven't been averse to breaking things in the past. This is the prime reason that a specific version is downloaded, one that warpinator was fully tested on.
You could also use pip3 to install the specific .29 version, though I generally think mixing pip with apt packages should be avoided if possible.
I can't build warpinator under Debian SID