From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: Re: [ptxdist] git ptx-patches fails
Date: Tue, 1 Apr 2014 10:24:41 +0200 [thread overview]
Message-ID: <20140401082441.GC6045@pengutronix.de> (raw)
In-Reply-To: <2910384.0cJodDoVy1@kongar>
On Mon, Mar 31, 2014 at 07:08:53PM +0200, Alexander Stein wrote:
> On Saturday 29 March 2014, 10:28:54 wrote Michael Olbrich:
> > On Thu, Mar 27, 2014 at 08:16:15AM +0100, Alexander Stein wrote:
> > > I tried to use git ptx-patches fromwithin a package and noticed it doesn't work.
> > > I could track down the problem to this command (from scripts/git-ptx-patches):
> > > > man git-format-patch | grep -q -e --notes
> > >
> > > Executing this command manually results in this error message:
> > > > Error executing formatting or display command.
> > > > System command (cd "/usr/share/man" && (echo ".pl 11i"; /bin/bzip2 -c -d '/usr/share/man/man1/git-format-patch.1.bz2') | /usr/bin/gtbl | /usr/bin/nroff -mandoc | less) exited with status 141.
> > > > No manual entry for git-format-patch
> > >
> > > Interestingly executing
> > > > (cd "/usr/share/man" && (echo ".pl 11i"; /bin/bzip2 -c -d '/usr/share/man/man1/git-format-patch.1.bz2') | /usr/bin/gtbl | /usr/bin/nroff -mandoc | less) | grep -q -e --notes
> > > works as expected. I have no idea what's wrong here.
> >
> > Maybe this is caused by some aliases or interactive/non-ineractive magic.
> > Does it help to replace "man git-format-patch" with "git format-patch
> > --help" or "man -P cat git-format-patch"?
>
> Unfortunately no :(
>
> git format-patch --help | grep -q -e --notes
> Error executing formatting or display command.
> System command (cd "/usr/share/man" && (echo ".pl 11i"; /bin/bzip2 -c -d '/usr/share/man/man1/git-format-patch.1.bz2') | /usr/bin/gtbl | /usr/bin/nroff -mandoc | /usr/bin/less) exited with status 141.
> No manual entry for git-format-patch
>
> $ man -P cat git-format-patch | grep -q -e --notes
> Error executing formatting or display command.
> System command (cd "/usr/share/man" && (echo ".pl 11i"; /bin/bzip2 -c -d '/usr/share/man/man1/git-format-patch.1.bz2') | /usr/bin/gtbl | /usr/bin/nroff -mandoc | cat) exited with status 141.
> No manual entry for git-format-patch
Do you have git-format-patch's manpage, i.e. does
man git-format-patch
work? On bash, what happens on:
$ man -P cat git-format-patch | grep -q -e --notes
$ echo ${PIPESTATUS[@]}
Does
strace -f -o /tmp/lala man -P cat git-format-patch | grep -q -e --notes
give any insights (e.g. where does the 141 come from?)
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-04-01 8:24 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 [this message]
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
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=20140401082441.GC6045@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@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