Paul Eggert <address@hidden> wrote:
> Jim Meyering <address@hidden> writes:
>
>> However, I can't reproduce that:
>>
>> $ git clone git://git.sv.gnu.org/coreutils.git cu \
>> && cd cu && ./bootstrap --gnulib-srcdir=/gnulib
>> ...
>> Creating ./._bootmp/lib/uniwidth/.gitignore
>> ...
>> ./bootstrap: done. Now you can run './configure'.
>>
>> Are you sure your copy of coreutils was up to date?
>
> Yes, I just now checked again; please see the transcript below.
> I notice that you bootstrapped from a private copy of gnulib; perhaps
> that's out of date on your host?
No. I reran the following in a brand-new account
on my system, as well as on another system altogether
(that claims to be Debian 4.0), just to be sure:
$ git clone git://git.sv.gnu.org/coreutils.git cu && cd cu && ./bootstrap
Both times, it succeeded.
However, the log showed differences from yours.
Your log has the following "overrides" lines, while mine don't:
> 505-penguin $ git clone git://git.sv.gnu.org/coreutils.git cu
...
> ./bootstrap: build-aux/.gitignore overrides ._bootmp/build-aux/.gitignore
...
> ./bootstrap: doc/.gitignore overrides ._bootmp/doc/.gitignore
...
> ./bootstrap: lib/.gitignore overrides ._bootmp/lib/.gitignore
That probably comes down to the use of version_controlled_file()
in bootstrap's slurp function, and makes me wonder if our differences
are due to your using a version of git for which "git-rm -n file"
doesn't do what version_controlled_file expects it to.
I've tested the following versions of git:
1.5.3.rc1.27.ga5e40
1.5.2.4
1.4.4.4
E.g., from a git-cloned coreutils work area,
"git-rm -n doc/.gitignore" should exit successfully.
Does that work for you?