Arch Linux User Repository

The package can be successfully built when setting options=('!buildflags').

I found that hint in https://wiki.archlinux.org/title/Makepkg#Makepkg_fails,_but_make_succeeds

@shalzz That workaround does not work for me locally from a clean install. The non-AUR arch package is having similar issues for me. I'm looking for another Go package that has a working fix.

A workaround is to set export LDFLAGS="" in the build() and package() hooks

# git.sr.ht/~rjarry/aerc flag provided but not defined: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now

...

make: *** [Makefile:45: aerc] Error 2

==> ERROR: A failure occurred in build(). Aborting...

error: failed to build 'aerc-git-0.6.0.r21.gbc593ac-1':

error: packages failed to build: aerc-git-0.6.0.r21.gbc593ac-1

This is broke for 1-2 weeks.

Great! Thanks for doing that.

As lamarpavel points out, Drew DeVault switched to the rjarry fork for his Alpine packages, which is a good-enough endorsement for me. This fact, combined with the Arch community repo already using the rjarry fork, means there is enough trust in the fork to switch the AUR package over.

The necessary changes have been pushed to the PKGBUILD. Feel free to update.

ainola, you can't see any commits in my name because my original commits were in the aerc2-git AUR package. As the software renamed itself to aerc, the AUR repos were moved but the git history was not transferred to this repo.

Seeing as aerc in [community] is already using the rjarry fork, this should be moved over as well. gkbrk, I will reject the orphan request on the basis that you will change to the fork and maintain the package (I don't seem to see any prior commits in your name).

gkbrk, please also consider adding some co-maintainers so that you all can keep an eye and work together on improving the package.

The official package of aerc for alpine linux is maintained by Drew DeVault [1] and pulls in its APKBUILD from rjarrys fork [2].

I agree that an announcement on the mailing list or official site would be better but it does look like it's almost official.

[1] https://pkgs.alpinelinux.org/packages?name=aerc&branch=edge [2] https://git.alpinelinux.org/aports/tree/community/aerc/APKBUILD

Here's a quote from the official mailing list of aerc.

The basic idea is to give you a space in which you can develop the fork and earn the community's trust without having to necessarily provide a stranger with the legitimacy of being the official fork until they've earned that trust.

This was posted 48 days ago. As of today there is no indication on the aerc website or the ~sircmpwn/aerc sourcehut page of the rjarry fork being in any capacity official. https://aerc-mail.org/ still points to the official repo.

I will of course move the PKGBUILD to a fork if it is blessed as official on the website or the repository of the official repo. The current aerc repo still has code that works, and for an ancient protocol like email that doesn't require too much change, the last commit on the official repo is not too old.

I am sure in the future the situation will become more clear and there will be an obvious repo that should be moved to. But at this point in time I don't feel comfortable giving my email credentials to a repo who is very fresh. Give it time, this is not a web browser that needs the latest patches without any regard to where they come from. Who knows, there might be a more active fork later.