From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] No man page for traceroute?
Date: Sun, 06 Nov 2011 23:38:37 +0100 [thread overview]
Message-ID: <4EB70C6D.7050806@binarywings.net> (raw)
In-Reply-To: <201111061907.39004.michaelkintzios@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Am 06.11.2011 20:07, schrieb Mick:
> On Sunday 06 Nov 2011 16:52:02 Alex Schuster wrote:
>> Florian Philipp writes:
>>> Am 06.11.2011 14:13, schrieb Mick:
>>>> Why would there be no traceroute(8) man page on my laptop?
>>>>
>>>> An older x86 box has it and displays it without fuss.
>>>
>>> It seems that the man page has been dropped from the package. Only the
>>> old 2.0.3 version from sourceforge still contains it. I couldn't find
>>> any mention on on bugs.g.o or traceroute-devel.
>>
>> I have traceroute-2.0.18 installed, and I do have the man page.
>
> I am getting confused. x86 box has traceroute-2.0.15 with man page, while
> amd_64 box has same version and no man page.
>
I bet the man-page disappears when you re-emerge traceroute. According
to changelog, the patch I mentioned in a different message was
introduced without changing the revision number (it doesn't have to
because it just fixes a build problem). If you emerged traceroute-2.0.15
before the patch was applied, you got the man-page. Afterwards, it is lost.
Regards,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-11-06 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 13:13 [gentoo-user] No man page for traceroute? Mick
2011-11-06 16:08 ` Florian Philipp
2011-11-06 16:52 ` Alex Schuster
2011-11-06 18:11 ` Florian Philipp
2011-11-06 19:07 ` Mick
2011-11-06 19:23 ` Dale
2011-11-06 22:38 ` Florian Philipp [this message]
2011-11-06 22:52 ` Érico Porto
2011-11-06 22:59 ` Mick
2011-11-06 17:01 ` Mick
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=4EB70C6D.7050806@binarywings.net \
--to=lists@binarywings.net \
--cc=gentoo-user@lists.gentoo.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