From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] inetutils-whois simply just doesn't work
Date: Tue, 21 Jan 2020 15:48:39 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18445@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
New issue by shahab-vahedi on void-packages repository
https://github.com/void-linux/void-packages/issues/18445
Description:
### System
* xuname:
Void 5.4.12_1 x86_64 GenuineIntel notuptodate rFF
* package:
inetutils-whois-1.9.4_10
iana-etc-20190504_1
### Expected behavior
```
> whois 4.2.2.4
...
NetRange: 4.0.0.0 - 4.127.255.255
CIDR: 4.0.0.0/9
...
```
### Actual behavior
```
> whois 4.2.2.4
getaddrinfo: Servname not supported for ai_socktype
```
### Steps to reproduce the behavior
Have `inetutils-whois` and `iana-etc` installed just the way they are, and you will bump into the error message shown in *Actual behavior*.
### How I fixed it for myself
By adding the following lines into my `/etc/services`:
```
whois 43/tcp
whois 43/udp
```
### Note
I am not sure in which package this fix should end up, `inetutils-whois` or `iana-etc`. I think latter is the case. I wanted to submit a patch but then I noticed that `iana-etc` uses an `update.sh` to fetch its `protocols` and `services`. Is it OK if I change `update.sh` to add those lines to `services` if they are not there?
next reply other threads:[~2020-01-21 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 14:48 voidlinux-github [this message]
2020-01-21 15:14 ` voidlinux-github
2020-01-25 12:09 ` [ISSUE] [CLOSED] " voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18445@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).