| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Check that we have a working tar before trying to use it |
| Date: | 2021-12-08 17:53:29 |
| Message-ID: | b6782dc3-a7b0-ed56-175f-f8f54cb08d67@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 12/8/21 12:05, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Actually, I think it makes more sense to simply revert this. bowerbird,
>> like all buildfarm animals, has a working tar.
> Right, it doesn't seem like tar is the biggest lift when setting up
> a buildfarm critter.
>
>> It's just that this one
>> is apparently seriously confused by using paths with a drive spec.
> Hm, so how would this test have handled that anyway?
>
>
It would have passed the test and failed the invocation as before. It
turns out that the tar being used is from the (old) MsysGit
installation. So I'm rearranging the path so it finds the system tar
instead. That should take care of things. (testing first before I do
anything else). On my initial test the system tar handled paths with
drive specs just fine.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-12-08 21:50:23 | pgsql: Revert "Check that we have a working tar before trying to use it |
| Previous Message | Tom Lane | 2021-12-08 17:05:24 | Re: pgsql: Check that we have a working tar before trying to use it |