From: Alexander Stein <alexander.stein@systec-electronic.com>
To: ptxdist@pengutronix.de
Cc: "Michael Olbrich" <m.olbrich@pengutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [ptxdist] git ptx-patches fails
Date: Tue, 01 Apr 2014 15:53:09 +0200 [thread overview]
Message-ID: <2661265.18rvLUC2Oa@ws-stein> (raw)
In-Reply-To: <16825117.7fFJm0Hm9F@ws-stein>
On Tuesday 01 April 2014 15:07:19, Alexander Stein wrote:
> Hello Uwe,
>
> On Tuesday 01 April 2014 14:30:30, Uwe Kleine-König wrote:
> > > I don't think this is related to man (what's man-db BTW?) at all.
> > man-db is the package that provides /usr/bin/man on Debian. Also man-db
> > from Debian unstable (i.e. 2.6.6) is unaffected.
> >
> > > I think the versions of cat and grep behave differently. I have
> > At least my grep also closes its input with -q and makes cat unhappy:
> >
> > $ { seq 1 2000 | cat; echo >&2 $?; } | grep -q 1
> > 141
> > $ { seq 1 2000 | cat; echo >&2 $?; } | grep 1 > /dev/null
> > 0
>
> Both commands work well here:
> $ { seq 1 2000 | cat; echo >&2 $?; } | grep -q 1
> 0
> $ { seq 1 2000 | cat; echo >&2 $?; } | grep 1 > /dev/null
> 0
>
> > So I still think it's a man problem. Reading the output of
> >
> > strace -o /tmp/tralala man git-format-patch | grep -q -e --notes
> >
> > "my" man doesn't use system to render the manpage. At least it doesn't
> > do any execvp and it opens /usr/share/man/man1/git-format-patch.1.gz
> > itself.
>
> You might be missing the -f option? My strace shows several execve. One of
them is
> > execve("/bin/sh", ["sh", "-c", "/bin/bzip2 -c -d /usr/share/man/"...], [/*
120 vars */]) = 0
>
> > So again, what is your man version?
> >
> > > installed grep-2.16 and coreutils-8.21 (current Gentoo stable
> > > versions).
> > For completeness although I think its proven to be unrelated:
> > grep 2.12-2 + coreutils 8.13-3.5 (i.e. Debian stable)
>
> I have man-1.6g
Mh, those numbers made me wonder. I checked the sources of this version and
found this snippet:
> There is a very different man program, also derived from
> John Eaton's original version (by Graeme W. Wilford)
> distributed under the name man_db, with version numbers
> like man_db-2.3.10. Do not confuse the two, they are
> mutually incompatible, although they perform nearly the same job.
It seems that the default (? dunno why this variant was installed though) of
man behaves differently. I now installed man-db-2.6.6 and it works now \o/
Thanks for the hint
Alexander
--
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
Am Windrad 2
08468 Heinsdorfergrund
Tel.: 03765 38600-1156
Fax: 03765 38600-4100
Email: alexander.stein@systec-electronic.com
Website: www.systec-electronic.com
Managing Director: Dipl.-Phys. Siegmar Schmidt
Commercial registry: Amtsgericht Chemnitz, HRB 28082
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-04-01 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 7:16 Alexander Stein
2014-03-29 9:28 ` Michael Olbrich
2014-03-31 17:08 ` Alexander Stein
2014-04-01 8:24 ` Uwe Kleine-König
2014-04-01 9:24 ` Alexander Stein
2014-04-01 9:37 ` Uwe Kleine-König
2014-04-01 9:59 ` Alexander Stein
2014-04-01 10:55 ` Michael Olbrich
2014-04-01 12:30 ` Uwe Kleine-König
2014-04-01 13:07 ` Alexander Stein
2014-04-01 13:53 ` Alexander Stein [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=2661265.18rvLUC2Oa@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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