linuxmint / warpinator

Share files across the LAN
GNU General Public License v3.0
1.18k stars 80 forks source link

buid-error on debian SID #108

Closed misterhsp closed 2 years ago

misterhsp commented 2 years ago

I can't build warpinator under Debian SID

Running custom install script '/usr/bin/python3 /build/warpinator-1.2.4/install-scripts/meson_update_icon_cache.py'
Running custom install script '/bin/sh /build/warpinator-1.2.4/install-scripts/meson_install_bin_script.sh'
Running custom install script '/usr/bin/python3 /build/warpinator-1.2.4/install-scripts/download_zeroconf.py'
--- stdout ---

Downloading and packaging zeroconf 0.29.0 in libexec/warpinator/zeroconf_
Package url: https://raw.githubusercontent.com/jstasiak/python-zeroconf/0.29.0/zeroconf/__init__.py

Could not download zeroconf. If you wish skip this and install it via package manager, set the 'use-zeroconf' build option to false. See the README.

--- stderr ---
curl: (6) Could not resolve host: raw.githubusercontent.com

FAILED: install script '/usr/bin/python3 /build/warpinator-1.2.4/install-scripts/download_zeroconf.py' exit code 1, stopped
FAILED: meson-install 
/usr/bin/meson install --no-rebuild
ninja: build stopped: subcommand failed.
dh_auto_install: error: cd obj-x86_64-linux-gnu && DESTDIR=/build/warpinator-1.2.4/debian/warpinator LC_ALL=C.UTF-8 ninja install returned exit code 1
make: *** [debian/rules:4: binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2
I: copying local configuration
E: Failed autobuilding of package
I: unmounting dev/ptmx filesystem
I: unmounting dev/pts filesystem
I: unmounting dev/shm filesystem
I: unmounting proc filesystem
I: unmounting sys filesystem
I: cleaning the build env 
I: removing directory /var/cache/pbuilder/build/345621 and its subdirectories
leigh123linux commented 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
misterhsp commented 2 years ago

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

mtwebster commented 2 years ago

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.