[Bug 375459] [NEW] Can't resolve host
gregor herrmann
gregor+debian at comodo.priv.at
Tue May 12 17:53:34 UTC 2009
On Tue, 12 May 2009 14:11:07 -0000, arky wrote:
> Public bug reported:
> Binary package hint: bti
Hi,
I'm the maintainer of bti in Debian.
> Doesn't post , looks like a network error but the connection is ok.
Thanks for the detailed bug report!
> $ bti --debug
[..]
> bti: main: host = 2
[..]
> * getaddrinfo(3) failed for tweeter:80
> * Couldn't resolve host 'tweeter'
> $ cat .bti
[..]
> host=tweeter
[..]
You've set "host=tweeter" in your .bti file.
bti supports three kind of hosts: [0]
for twitter.com: "twitter"
for identi.ca: "identica"
for a custom laconi.ca instance: the hostname you want (since version 22)
Since you are neither using "twitter" nor "identica" bti assumes that
you want to use a host called 'tweeter' [1] and tries to connect to
that host (with curl); that fails in your case because the hostname
'tweeter' doesn't resolve on your machine.
I'm not sure what you want to do:
* If you want to use twitter, put 'twitter' instead of 'tweeter' in
your .bti file.
* If you want to use some service called tweeter either put the whole
hostname into .bti or make sure in some other way that your machine
can resolve 'tweeter' (/etc/hosts or some DNS stuff) -- and check
with `host tweeter' that the name resolution actually works.
In any case the issue of your machine not being able to resolve a
hostname called 'tweeter' is not a bug in bti.
Cheers,
gregor
[0]
cf. `man bti', at least for the first two options
[1]
from your log: host = 2
from bti.c:
enum host {
HOST_TWITTER = 0,
HOST_IDENTICA = 1,
HOST_CUSTOM = 2
};
[..]
session->host = HOST_CUSTOM;
[..]
dbg("host = %d\n", session->host);
--
.''`. Home: http://info.comodo.priv.at/{,blog/} / GPG Key ID: 0x00F3CFE4
: :' : Debian GNU/Linux user, admin, & developer - http://www.debian.org/
`. `' Member of VIBE!AT, SPI Inc., fellow of FSFE | http://got.to/quote/
`- NP: Queen: 39
--
Can't resolve host
https://bugs.launchpad.net/bugs/375459
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
More information about the universe-bugs
mailing list