Re: pgarchives & pglister: bookworm migration

On Fri, May 3, 2024 at 10:10 AM Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>
wrote:

> > Oh, we're all on bullseye by now so the EOL of buster should not be
> relevant. All the standard packages on bullseye (except django itself,
> which has to be loaded in a virtualenv) should work. Actually, I think we
> also load django-markwhat into our virtualenv, but I don't think any of
> those apps actually use it.
>
> Thanks!
>
> Additional questions:
> - Is there a place where the currently supported platform(s) is listed?
>

Unfortunately, no,not really :/ The only real way is to track the pgweb git
history which will have an entry for the compatibility. Probably enough to
just track the requirements.txt

> - What issues can arise if trying to run the applications (pglister and
> pgarchives) with higher Debian versions, as long as the Django version is
> supported? Specific postgresql queries?
>

No, the issue is likely to be with non-django dependencies, the one that we
use debian packages for. There aren't many in pgarchives and pglister --
we've got a lot more in pgeu-system and there have been some
incompatibilities reported there. (We use the same runtime env for them all
on pginfra, which is why that matters)

It might very well be that for just pglister and pgarchives, there are
actually no such dependencies. And as long as there aren't, it should just
work.

(The exim integration might break if there are output incompatibilities
there, but that's not a mandatory component)

I don't think either of those have any advanced SQL in them, so they should
work on all supported postgres I believe. And there definitely shouldn't be
a problem using a *newer* postgres. (FWIW, all the pginfra production
systems of these systems are on postgres 15 at this time).

//Magnus