From: | Bernardo Generoso <generoso(dot)bernardoapple(at)gmail(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Christoph Berg <myon(at)debian(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-release(at)postgresql(dot)org, pgsql-www(at)postgresql(dot)org |
Subject: | Re: PG 15 downloads |
Date: | 2022-10-17 12:46:44 |
Message-ID: | 02FBC942-3AD4-43D4-8351-0038AC1DCDD2@gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Why I’m receiving the this emails?
On 17 Oct 2022, at 13:08, Dave Page <dpage(at)pgadmin(dot)org> wrote:
On Mon, 17 Oct 2022 at 13:02, Christoph Berg <myon(at)debian(dot)org> wrote:
Re: Dave Page
> > I've been asking for some way to be able to stop syncing the apt repo
> > from the repository master host so I can prepare the release, and then
> > have the release people grab it from there. But that was never
> > implemented, so things still rely on me being available to
> > synchronously do the required steps, which is obviously not optimal.
> >
>
> Yeah, unfortunately that's not entirely straightforward to implement.
I haven't seen the sync cronjob, but I assume it's something like
rsync over ssh, so wouldn't just prepending something like this work?
ssh atalia test -f /srv/apt/SYNC && rsync ...
I'd then remove the SYNC file during release time.
Unfortunately not (entirely). It pulls from atalia and a number of other boxes, performs a little magic, and then asynchronously pushes everything to the frontends.
--
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2022-10-17 12:56:52 | Re: PG 15 downloads |
Previous Message | Dave Page | 2022-10-17 12:07:59 | Re: PG 15 downloads |