Arch Linux User Repository

GPG signing has been enabled for this package. If you get an "unknown key" error, import the key and run makepkg again:

gpg --recv-keys E7729BFFBE85400FEEEE23B178D7DEFB9AD59AF1

See the following links for more information:
http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/
https://wiki.archlinux.org/index.php/Makepkg#Signature_checking
https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key

Thanks @arcanenibble - have pushed an updated PKGBUILD with your recommended changes.

I do not have an Ubuntu One account, and upstream responsiveness on bugs has been pretty lacking, but I will see about making a report at some point in the near future.

The upstream code declares an incompatibility with python-flit version 4:

==> Starting build()...
* Getting build dependencies for wheel...

ERROR Missing dependencies:
    flit_core<4,>=3.8
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: python-spf-engine-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
python-spf-engine - exit status 4

However, patching it out seems to work fine:

diff --git a/PKGBUILD b/PKGBUILD
index 45b15a6..6781c65 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -31,6 +31,7 @@ validpgpkeys=('E7729BFFBE85400FEEEE23B178D7DEFB9AD59AF1') # Donald Scott Kitterm

 build() {
   cd "${pkgname#*-}-${pkgver}"
+  sed -e 's/flit_core >=3.8,<4/flit_core >=3.8/' -i pyproject.toml
   python -m build --wheel --no-isolation
 }

Ideally this should be reported to upstream.

@ki9 please rebuild the python-pyspf dependency against python-3.12.

This package might be broken. Postfix was throwing some errors, so I ran policyd-spf and got ImportError: Module not found: spf, or something like that.

Thanks @Thaodan. I do not understand why the package needs to depend on an explicit Python version, though. Could you please give me a bit more context for why you need this particular customisation?

@morgenstern: makedepends=(python)

Then in build(): _version_major=$(python -c 'import sys;print(sys.version_info.major)') _version_micro=$(python -c 'import sys;print(sys.version_info.micro)')

_version_bad=${version_major}.$((version_micro+1)) _version_good=${version_major}.${version_micro}

Than in package(): depends+=("python>=${_version_good}" "python<${_version_bad}")

@Thaodan I'm not sure I follow - if you want to post an example of what you think the PKGBUILD should look like, I'd be happy to take it under advisement.

Can you make it so it depends on the python version used during build?

GPG signing has been enabled for this package. If you get an "unknown key" error, import the key and run makepkg again:

gpg --recv-keys E7729BFFBE85400FEEEE23B178D7DEFB9AD59AF1

See the following links for more information:
http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/
https://wiki.archlinux.org/index.php/Makepkg#Signature_checking
https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key