doh-proxy 0.9.6 deb package incompatible with latest Debian libc6 about doh-server HOT 5 CLOSED

It's for the system it's built on. I guess since the last time you installed it, GitHub updated the Ubuntu version (ubuntu-latest).

Do the .tar.bz2 files work on your system?

from doh-server.

Thanks for this suggestion. Yes, the static binary provided in the bz2 archive indeed works fine.

Is there a reason for the debian package containing a different (and dynamically linked) executable? Do you consider shipping the same static build in the debian package as well? This would make the deb package actually work on Debian without breaking it for other distributions.

Binary from doh-proxy_0.9.6_linux-x86_64.tar.bz2:

# ldd doh-proxy 
        not a dynamic executable

Binary from doh-proxy_0.9.6_amd64.deb:

# ldd doh-proxy 
        linux-vdso.so.1 (0x00007ffca99eb000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f16d9a7d000)
        libm.so.6 => /usr/lib/libm.so.6 (0x00007f16d9995000)
        libc.so.6 => /usr/lib/libc.so.6 (0x00007f16d97ae000)
        /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f16d9da3000)

from doh-server.

The cargo zigbuild command produces an executable for any target (even without dependencies). This is easy to use and what is used for the tarballs.

The cargo deb command produces an executable and creates a Debian package.

But there's no command that combines these two commands, so finding the proper incantation was not easy.

from doh-server.

I see, thank you for looking into it.

from doh-server.

Debian packages for x86_64 and aarch64 have been added to the current release. Thanks!

from doh-server.