pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Check that we have a working tar before trying to use it
Date: Wed, 08 Dec 2021 12:05:24 -0500
Message-ID: <3660797.1638983124@sss.pgh.pa.us> (raw)
In-Reply-To: <b179201e-8451-6a5e-e9be-9c755a13be7f@dunslane.net>
References: <E1muynv-0006GS-R4@gemulon.postgresql.org>
	<3655283.1638977975@sss.pgh.pa.us>
	<2e118a11-6936-21ec-6782-e9dbb20972c2@dunslane.net>
	<3657697.1638980149@sss.pgh.pa.us>
	<b179201e-8451-6a5e-e9be-9c755a13be7f@dunslane.net>

Andrew Dunstan <andrew@dunslane.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?

			regards, tom lane





view thread (25+ messages)  latest in thread

Message-ID: <3660797.1638983124@sss.pgh.pa.us>
Permalink:  ../3660797.1638983124@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3660797.1638983124@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Check that we have a working tar before trying to use it
  In-Reply-To: <3660797.1638983124@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox