Description of problem:
autopoint fails if the GREP_OPTIONS environment variable contains the -n (prefix each line of output with line number) option.
This happens because autopoint assumes that grep outputs lines of the source file in an unmodified form, which is not always true.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. cd to a directory with a configure.ac file which contains the AM_GNU_GETTEXT_VERSION macro
2. run "GREP_OPTIONS=-n autopoint --force"
autopoint: *** Missing version: please specify in configure.ac through a line 'AM_GNU_GETTEXT_VERSION(x.yy.zz)' the gettext version the package is using
autopoint: *** Stop.
autoreconf: autopoint failed with exit status: 1
autopoint succeeds as if the -n grep option was not set.
I see - thanks for the report.
So do you suggest that autopoint unsets (ignores) GREP_OPTIONS?
Do you have to export GREP_OPTIONS ?
The variable has to be set in the environment from which autopoint is started, so yes, probably.
For the record, I had the "export GREP_OPTIONS=-n" line in my .bash_profile when I noticed the bug.
(In reply to comment #3)
> For the record, I had the "export GREP_OPTIONS=-n" line in my .bash_profile
> when I noticed the bug.
That was my question: do you really need to export it?
Yes, I want the line numbers in grep output (and no, it doesn't work without exporting the variable).
BTW, there are several gzip invocations in autopoint - gzip uses $GZIP for default options, it should probably be handled as well.
Ok, probably we should ask gettext upstream about GREP_OPTIONS,
but I suppose autopoint could be patched to unset it.
In the meantime perhaps you could make a ~/bin/autopoint
wrapper script to handle it.
http://lists.gnu.org/archive/html/bug-gettext/2012-07/msg00005.html was my post - no follows yet to date.
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
I guess this is fixed in F21+?
gettext-0.18.3.2-5.fc20 has been submitted as an update for Fedora 20.
gettext-0.18.3.2-5.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.