Package: libsoup2.4-1 Version: 2.60.2-1 Severity: important File: libsoup Dear Maintainer,
* What led up to the situation? using .test as a local development machine domain TLD * What exactly did you do (or not do) that was effective (or ineffective)? i have to type http:// in front of every .test domain or i get a web search * What was the outcome of this action? typing http://blah.test works but so should blah.test * What outcome did you expect instead? that typing blah.test would work as well - i realize that typing http:// might not seem like a big deal, and in the grand scheme of things it isn't, but it gets *really* old really quick, and besides it *should* work as it is the recommended TLD to use for local development work etc -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libsoup2.4-1:amd64 depends on: ii glib-networking 2.54.1-1 ii libc6 2.25-3 ii libglib2.0-0 2.54.1-1 ii libgssapi-krb5-2 1.15.2-2 ii libsqlite3-0 3.21.0-1 ii libxml2 2.9.4+dfsg1-5.1 libsoup2.4-1:amd64 recommends no packages. libsoup2.4-1:amd64 suggests no packages. -- no debconf information