Deprecation of Python 3.6 and 3.7 in Barman 3.14

[Martin Marques]

Hello,

This message is just to inform that as of version 3.14 of Barman we are officially deprecating Python 3.6 and 3.7, so you'll need to run with python 3.8 or newer.

PGDG packages for rpm are already built against python 3.12, and Debian/Ubuntu distributions are already using newer versions of python by default. For this reason anyone using packages is completely covered and won't have to worry about the deprecation.

Kind regards, Martín

[Sebastiaan Maas]

Barman got updated from the official PGDG repo to 3.14.0 when we ran updates on our RHEL 9 install last Tuesday. Python 3.12 was automatically installed, however it caused barman to fail, because with Python 3.12 distutils is no longer available. It threw me this

ModuleNotFoundError: No module named 'distutils' error. I had to fix it by installing Python 3.12 setuptools. After that, barman was working again.

sudo yum install python3.12-setuptools

Kind regards,

Sebastiaan

Op vrijdag 23 mei 2025 om 17:48:29 UTC+2 schreef Martin Marques:

[Martin Marques]

You need to report that to the pgsql-...@postgresql.org list (you
don't have to be subscribed to write to that list AFAIU). In any case,
I'll point Devrim (the rpm maintainer) to this issue

> --
> --
> You received this message because you are subscribed to the "Barman for PostgreSQL" group.
> To post to this group, send email to pgba...@googlegroups.com
> To unsubscribe from this group, send email to
> pgbarman+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/pgbarman?hl=en?hl=en-GB
>
> ---
> You received this message because you are subscribed to the Google Groups "Barman, Backup and Recovery Manager for PostgreSQL" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pgbarman+u...@googlegroups.com.
> To view this discussion, visit https://groups.google.com/d/msgid/pgbarman/5081762f-2eb9-4660-8160-b862dbaf004fn%40googlegroups.com.

[Martin Marques]

Devrim just mentioned that this has already been fixed here:
https://git.postgresql.org/gitweb/?p=pgrpms.git;a=commitdiff;h=0c91c44ba2abb17b312e442fc58eb16d0e76e46a