Arch Linux User Repository

Note on getting the git signing public key. Any of the following:

1) Get fresh copy of the package (on this page Package Actions Download Snapshot) Unpack tar file and the key will be in keys/pgp:

gpg --import < keys/pgp/*.asc

2) Available on github (same account as the package source): https://github.com/gene-git/blog/tree/master/git-keys

3) From authors website : https://www.sapience.com/tech

4) via WKD curl $(gpg-wks-client --print-wkd-url arch@sapience.com) | gpg --import

Thank you and very happy to help:)

Thanks, that's the best help an AUR package maintainer has ever given me!

Right - sorry about that - fair comment:

Edit the PKGBUILD file and change the line :

depends=('python>=3.13'

to be

depends=('python>=3.11'

and then build it by running the command

makepkg

Then this creates the package to install. As of now that would be

dmarc_report-4.12.5-1-any.pkg.tar.zst

So you then install using:

 sudo pacman -U ./dmarc_report-4.12.5-1-any.pkg.tar.zst

Or run as root and without sudo. Let me know if I can help further

I love the way y'all say "simply edit the PKGBUILD", like it's obvious to an end user how to do that.

@politas - it shouldn't be a problem for now to simply edit and change the PKGBUILD depends array to use 3.12 and then install.

I am a bit surprised however, since I thought manjaro tracked arch (stable and testing) and since arch has had 3.13 for a while in core (stable), is manjaro stable not also on 3.13? Some things like tensorflow are lagging behind so some folks may want to hang back - but if were me i'd update and find a way to deal with tensorflow and old versions.

Anyway, even if manjaro is on 3.11/3.12, it should be easy to install - but I don't use manjaro so cannot test - let me know if you have any more trouble.

I see. It will work on 3.11, but we can't install it with 3.11 or 3.12, since they don't meet the requirements. Thanks. Guess I'll just have to deal with it until Manjaro upgrades Python, then.

@politas thanks for pointing that out. I am the upstream author as well as the packager. As of now, it will currently work fine on 3.11.

I chose to bump the Arch PKGBUILD to 3.13 since its the current core version of python and I simply forgot to change the README :). To minimize maintenance going forward I typically drop support for older versions at some point.

Thanks and I should make the arch version dependency and the upstream readme file consistent as well as the pyproject.toml.

Might be a useful little project for me to build a new tool to add to my release workflow toolkit to ensure that deps are consistent everywhere.

thanks for letting me know.

Can I ask why this package has been set as python>=3.13 when the github readme says "Require python version 3.11 or later"?

@politas good catch - however I have no control over what is on the web page.

This seems to be a "quirk" with aurweb which seems to append any python it finds in the aur regardless of the PKGBUILD dependencies.

The correct dependencies are the ones in the PKGBUILD.

Aurweb does this for every python package in the AUR not just this one.

This issue may be relevant:

https://gitlab.archlinux.org/archlinux/aurweb/-/issues/163

Dependency of "python>=3.13". Seems contradictory to the (python37AUR, python311AUR, python310AUR) listed above.