You are not logged in.
A while ago someone raised an issue on my github project regarding a bug when compiled for Archlinux. They'd created an AUR for it (here https://aur.archlinux.org/packages/webdav-daemon/ ).
In the AUR the'd already added a patch to correct another bug which wasn't reported but has since been fixed. So now the AUR will simply not build because the patch can't be applied.
Since someone's already put the effort into creating the AUR I'd like to ensure it actually builds, but as an Archlinux newby I don't see any obvious way for me to modify the AUR. That is, I know what the fix is, but don't have any access to correct the AUR.
Offline
If you don't own the PKGBUILD, or co-maintain it, you cannot. Try leaving a comment or directly emailing the maintainer.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
If the maintainer does not react to email or comment, then you can send an orphan request and take over maintainership.
By the way, the package has the wrong name, it should have a -git suffix since it builds from a git branch. That means one of you should upload the package with the corrected name and then request a merge/delete of the old package.
Last edited by progandy (2021-06-07 10:36:32)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Online
If you don't own the PKGBUILD, or co-maintain it, you cannot. Try leaving a comment or directly emailing the maintainer.
I'll do that. Thanks.
Preemptively I'll also ask if there's no administrative recourse should the maintainer fail to respond? It would be a shame if users could block packages from being in AUR (under their own name) by simply creating broken AURs.
Offline
If the maintainer does not react to email or comment, then you can send an orphan request and take over maintainership.
By the way, the package has the wrong name, it should have a -git suffix since it builds from a git branch. That means one of you should upload the package with the corrected name and then request a merge/delete of the old package.
Ah Thanks. That answers my question.
Offline
I suggest flagging the package as 'out-of-date'
Offline
No, "out of date" is for packages that are, as the name suggests, out of date - not for buggy packages.
Offline
Yes, "out of date" is for packages that are, as the name suggests, out of date - like git packages building from git master, which no longer build because the current PKGBUILD used to be correct, but isn't correct anymore after new upstream commits.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline