Re: Keeping up with security fixes

From: "Karl O(dot) Pinc" <kop(at)karlpinc(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: pgadmin-support(at)lists(dot)postgresql(dot)org
Subject: Re: Keeping up with security fixes
Date: 2023-10-23 19:00:32
Message-ID: 20231023140032.76840cdb@slate.karlpinc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On Mon, 23 Oct 2023 10:43:05 +0100
Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Wed, 18 Oct 2023 at 23:07, Karl O. Pinc <kop(at)karlpinc(dot)com> wrote:
>
> > What is the expected method for keeping PgAdmin4 up-to-date?
> >
>
> It depends on the platform and where you get your packages from.

Thank you very much for your through reply.

I decided to not use the OS-level packages because, at
least for my platform, the package requires apache. That
overly constrains me.

So I used pypi.org with Python packaging and virtual environments.

I test for updates by comparing the installed package version
with the version available at pypi. Basically (korn shell):

[ "$(curl -s https://pypi.org/pypi/pgadmin4/json \
| jq --raw-output .info.version)" \
= "$(/srv/venvs/pgadmin4/bin/pip list \
| awk '{if ($1 == "pgadmin4") print $2;}')" ]

If you see any flaws in this approach I'd appreciate your comments.
(I'm not entirely sure how the pypi API deals with reporting development
versions. And there might be other problems as well.)

Thanks again for the help.

Regards,

Karl <kop(at)karlpinc(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Tim Quinn 2023-10-24 01:47:00 Never asked to set Master Password
Previous Message Dave Page 2023-10-23 09:43:05 Re: Keeping up with security fixes