Your keywords were dropped, readd them if you want
I cant get it working: # host-woods -l gentoo.org Invalid query name gentoo.org (dotted quad not allowed in listmode) syntax wrong?
HPPA done. Fixed one quoting issue. (In reply to comment #1) > I cant get it working: > > # host-woods -l gentoo.org > Invalid query name gentoo.org (dotted quad not allowed in listmode) Which arch? elmer ~ # host-woods -l gentoo.org !!! gentoo.org AXFR record query refused by udns1.ultradns.net !!! gentoo.org AXFR record query refused by udns2.ultradns.net No nameservers for gentoo.org responded elmer ~ # host-woods -l gmail.com !!! gmail.com AXFR record query refused by ns3.google.com !!! gmail.com AXFR record query refused by ns2.google.com !!! gmail.com AXFR record query refused by ns4.google.com !!! gmail.com AXFR record query refused by ns1.google.com elmer ~ # host-woods -l sco.de 216.250.130.1 (ns.calderasystems.com) host_res_read_anslen(): recv_sock(): error reading answer's length: Connection reset by peer elmer ~ # host-woods -l example.com !!! example.com AXFR record query refused by b.iana-servers.net !!! example.com AXFR record query refused by a.iana-servers.net No nameservers for example.com responded Seems to work fine (on hppa). :)
(In reply to comment #2) > > # host-woods -l gentoo.org > > Invalid query name gentoo.org (dotted quad not allowed in listmode) > > Which arch? ok. so this has issues on ppc64. amd64: you, too? if so, then this might be a 64bit problem.
(In reply to comment #3) > ok. so this has issues on ppc64. > amd64: you, too? if so, then this might be a 64bit problem. No, works fine here. In fact, this was the first arch on which it was (officially) tested before I submitted this new version. I rather suspect it is ppc or even ppc64 specific. This app comes with build instructions that have quite some notes on proper linking, with many special cases. Likely, there is something about ppc(64) that's causing this. You might try linking against some other resolver lib, if you really desire. In my experience, before it was fixed, it would always compile, however it would not resolve with complaints similar to that. Bear in mind that this is not the standard host, that one is a part of bind. This is a special version (forked looong time ago as I understand) with some extra functionality. It was primarily necessary for xtraceroute, now punted (likely because this host package was inoperational for some time). With xtraceroute gone I suspect there a re not that many users who really need it. I'd suggest that we only add keywrds for the arches where the app builds and works and not spend too much time on it otherwise. Instead let's leave it to users to request its keywording on the arches where it does not link properly. Then we can ask them to do the hard work - trying to link it against all the possible resolver libs and variants and checking which one actually works on that arch :) (sorry, I can only do it on amd6 and x86 myself and there it is already keyworded). George PS #67973 is the bug that dealt with update. I even forgot that this thing was almost fixed once then a new version came out that completely differently dealt with resolver :).
ok. :-) I'm not going to add ~ppc64 and leave it 'as is'.
Keyworded for ~ppc.
If mips team is too busy, feel free to remove yourself and close this bug. I do not perceive this as any kind of problem, as this is a rather low profile package, see my comment above (comment #4). Or I'll do so (close the bug) in another month if there is no more activity. George
No activity in more like 4 month, closing the bug. If users will want it on a particular non-covered arch, the'll ask.. George
