Thanks for reopening. Assigning hostname to localhost is indeed logical,
unless the hostname is already assigned an address --
which is the whole point of the bug.
--
network-admin aliases hostname to 127.0.0.1 unconditionally
https://launchpad.net/bugs/24874
--
desktop-bugs mailing list
desktop
Quoting my comment #10 of a year ago:
> I have lost personal interest in this bug, and can no longer test it
easily.
This is still the case.
--
[network-admin] aliases hostname to 127.0.0.1 unconditionally
https://bugs.launchpad.net/bugs/24874
You received this bug notification because you are
I have lost personal interest in this bug, and can no longer test it
easily. I have not learned any more Perl, but examination of the routine
mentioned above (gst_network_ensure_loopback_statichost) in a modern
version seems to show that the bug is still present (both code paths
alias hostname to l
Oh, scratch my earlier comment. I've now seen what's been going on with
the new system-tool-backends on freedesktop.org. If this bug is still
valid, it probably belongs in a different package now.
--
[network-admin] aliases hostname to 127.0.0.1 unconditionally
https://bugs.launchpad.net/bugs/248
No, I meant that I had found a version of an old network.pl in my system
and had thought it was modern.
I've taken another short look at system-tool-backends, and found
ensure_loopback_statichost in line 329 of Network/hosts.pm. If that
function is called with the hostname, it still does what this
