From: | James Coleman <jtc331(at)gmail(dot)com> |
---|---|
To: | Christoph Berg <myon(at)debian(dot)org> |
Cc: | pgsql-pkg-debian(at)lists(dot)postgresql(dot)org |
Subject: | Re: Postgres 15.2 packages missing |
Date: | 2023-05-17 19:15:49 |
Message-ID: | CAAaqYe-bK5FXXx8_eD-z7SVfOUYBy=wre7wjg7fPhRZAgyTa+g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-debian |
On Wed, May 17, 2023 at 11:14 AM Christoph Berg <myon(at)debian(dot)org> wrote:
>
> Re: James Coleman
> > Thanks. I had a vague memory of something like that, but then when I
> > saw the 15.0 and 15.1 packages I assumed I'd remembered incorrectly.
> >
> > What's the reasoning for maintaining only the newest point release in the repo?
>
> Mostly that reprepro that doesn't support it, unfortunately. It's
> still the best repo managing software around. We might have a look at
> "aptly", but its command line interface is somewhat weird and possibly
> not an improvement.
>
> Thanks for spotting the inconsistency, I managed to clean up the
> debris in there. The extra packages in there were mostly from old
> packages built while the distribution in question was still in
> development itself, so this wasn't even usable as a general wayback
> machine.
>
> apt-archive.postgresql.org is automatically kept up to date and
> receives all packages with a delay of one day.
Ah, that helps. Thanks for maintaining the repo.
I'm probably misunderstanding something here still, but is reprepro
_not_ used to manage the archive repo such that we don't have that
problem there?
Thanks,
James
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2023-05-17 19:21:06 | Re: Postgres 15.2 packages missing |
Previous Message | Christoph Berg | 2023-05-17 15:14:14 | Re: Postgres 15.2 packages missing |