From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Christoph Berg <myon(at)debian(dot)org>, Dave Page <dpage(at)pgadmin(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:07:59 |
Message-ID: | CA+OCxozNoSHedSdd99g-9-yGvtZwt5N15JhQuZR1OF1B_0=uwQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Bernardo Generoso | 2022-10-17 12:46:44 | Re: PG 15 downloads |
Previous Message | Christoph Berg | 2022-10-17 12:02:40 | Re: PG 15 downloads |