Hey Iyán, > I think the issue is that in the past I commited a large patch file (by > mistake) instead of including the url in the sources array (that's commit > ef079835), and somehow the remote didn't complain back then but it does now. > > I have removed that patch and replace it with the upstream url, but I can't > push a new version. This is what I'm trying to commit: > > https://github.com/iyanmv/PKGBUILDs/commit/5e642048f438b3857007621d8b778689776244f3
Yes that indeed seems to be the issue here. If you compare the history of the PKGBUILD on GitHub[0] and on the aur[1] seems that the problematic commit is currently not in the aur and would only be added once your push goes through. You could try to remove the patch file from the problematic commits[2][3] and re-publish using aurpublish. Another solution which is maybe more easily doable is to directly clone the aur repo of python-tweedledum, re-apply and push the fixed changes (so without the big patch) and re-import the package into your GitHub repository. There is currently no need to rewrite the git history on the AUR, so you should be able to do this without TU support :) cheers, chris [0] https://github.com/iyanmv/PKGBUILDs/commits/main/python-tweedledum/PKGBUILD [1] https://aur.archlinux.org/cgit/aur.git/log/?h=python-tweedledum [2] https://github.com/iyanmv/PKGBUILDs/commit/03f29bc9219ecc3c35e969011dc810484b25584e [3] https://github.com/iyanmv/PKGBUILDs/commit/5e642048f438b3857007621d8b778689776244f3
signature.asc
Description: PGP signature
