For future maintainers of the PyPi entry I created this docker file:

Dockerfile
```
FROM debian:trixie

RUN apt-get update && \
  apt-get install -y pandoc \
  git \
  autoconf \
  gcc \
  build-essential \
  swig \
  python3 \
  python3-dev \
  python3-setuptools \
  python3-build \
  python3.13-venv \
  libgpgme-dev \
  gpg \
  twine

WORKDIR /opt/
RUN git clone https://dev.gnupg.org/source/gpgmepy.git gpgmepy

WORKDIR /opt/gpgmepy

# Set to latest release or commit
RUN git checkout 66e8a5e43d0482394b4733cad94924f7e1169c21

RUN ./autogen.sh

RUN mkdir build && cd build && ../configure --enable-maintainer-mode && make && python3 -m build

WORKDIR /opt/gpgmepy/build/dist

# How to obtain the token: https://pypi.org/help/#apitoken
ENV TWINE_USERNAME=__token__
ENV TWINE_PASSWORD=pypi-please-set-me

# Now you can run `twine upload *.tar.gz`
CMD ["/bin/bash"]
```

With this you can run `docker build -t gpgmepy .` and `docker run -it gpgmepy`. If you set the API token from PyPi, you can then run 
`twine upload *.tar.gz` to upload the gpgmepy bindings to PyPi.