From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kris Jurka <books(at)ejurka(dot)com>, pgsql-hackers(at)postgresql(dot)org, Michael Meskes <meskes(at)postgresql(dot)org> |
Subject: | Re: CVS corruption/mistagging? |
Date: | 2007-08-14 23:34:31 |
Message-ID: | 46C23C07.4010007@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> In the meantime, though, it's not quite clear why this would lead to
> a buildfarm failure --- it should just mean a lot of extraneous files
> appearing in a fresh checkout. (Looks a bit harder ... Oh, it looks
> like btree_gist has some files that used to be autogenerated and are
> now in CVS, so the bogusly new versions from CVS are suppressing the
> desired generation from the old btree_num.c file.)
>
>
>
Looking at the Committers mail, it looks like there have only been two
very small commits since Michael's series of commits around 12 to 13.5
hours ago, and before that nothing since around 28 hours ago. Do we have
a backup snapshot of the repo taken during that time that we can roll
back to? That might be simpler than doing surgery on the repo.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2007-08-14 23:58:27 | Re: Index Tuple Compression Approach? |
Previous Message | Tom Lane | 2007-08-14 23:03:55 | Re: CVS corruption/mistagging? |