Re: [COMMITTERS] pgsql: Second try committing the path changes.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [COMMITTERS] pgsql: Second try committing the path changes.
Дата
Msg-id 21827.1157046650@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Second try committing the path changes.  (Chris Browne <cbbrowne@acm.org>)
Ответы Re: [COMMITTERS] pgsql: Second try committing the path
Список pgsql-hackers
Chris Browne <cbbrowne@acm.org> writes:
> tgl@sss.pgh.pa.us (Tom Lane) writes:
>> No, because those derived files are not in CVS at all.  What you
>> are describing sounds to me like a clock skew problem.  Is your
>> machine's system clock showing the correct date?

> Odd, odd.  NOT a clock problem.  The .c files were sitting in my
> buildfarm's CVS repository for HEAD.  And yes, indeed, the derived
> files shouldn't have been there at all.  I'm not quite sure how they
> got there in the first place.

> At any rate, after comprehensively looking for yacc-derived files,
> that clears this problem, as well as regression failures with last
> night's commit of COPY (SELECT) TO, which is no bad thing.

I'll bet the way they got there is you did a build in the CVS repository
tree, and then cleaned up with "make distclean" not "make maintainer-clean".

The buildfarm script is supposed to complain about unexpected files in
the repository --- I wonder if it is fooled by the .cvsignore entries
for these files?
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Magnus Hagander"
Дата:
Сообщение: Re: gBorg status?
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: Prepared statements considered harmful