Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: inetutils: fix the missing port number for whois
Date: Sat, 25 Jan 2020 08:49:36 +0100	[thread overview]
Message-ID: <20200125074936.AWKTd7rNyBsm3CkyxdorI0bNraNN_rOFlPmkztBIFn8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18520@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 910 bytes --]

There's a merged pull request on the void-packages repository

inetutils: fix the missing port number for whois
https://github.com/void-linux/void-packages/pull/18520

Description:
Fixes issue 18445:
#18445

inetutils-whois consults the /etc/services provided by IANA to
determine the port number for the "whois" service. However, the
"whois" service is not listed in that file and when you run whois
you will end up with the following error:

> whois 4.2.2.4
  getaddrinfo: Servname not supported for ai_socktype

This patch makes use of "nicname" port which is the same number
(43) as a "whois" port and is listed in /etc/services.
Moreover, changing the whois/whois.c leads to invocation of
help2man. This is unnecessary, because no option has changed and
launching help2man during the cross compilation fails.

This fix wouldn't be possible without the help of great folks
at #voidlinux.

      parent reply	other threads:[~2020-01-25  7:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 21:53 [PR PATCH] " voidlinux-github
2020-01-24 22:43 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-24 22:46 ` voidlinux-github
2020-01-25  7:49 ` voidlinux-github [this message]

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=20200125074936.AWKTd7rNyBsm3CkyxdorI0bNraNN_rOFlPmkztBIFn8@z \
    --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).