-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AUR package FTBFS (failed to build from source) #52
Comments
Thank you for the bug report, it seems like newer versions of GCC are flagging this and raising a warning, which is treated as an error due to the |
Thanks! 🙏 🎉 👏 I've been able to recompile from latest |
Thank you. I'm no longer using Arch - would you be interested in maintaining the PKGBUILD on AUR? |
Sure! I'm currently using Manjaro on my daily driver PC, and am able to maintain the P.S.: I should clarify... I have the knowledge, expertise, and capability to maintain I assume that you would be willing to sponsor me? |
Ah, I'm not a "Trusted User"/Package maintainer on Arch, but I did add you as a co-maintainer for the libx52 repo on AUR. My understanding was that anybody could contribute to AUR, though you'd have to be a trusted user to contribute to the main repository. |
Oh, that makes sense! I must have been misunderstanding the Wiki.
🙏 Thanks! I'm happy to help out with this Should I now be able to update the Also, it looks like the
My testing pre-release If I'm going to update to latest |
I believe you should be able to push to the AUR repo, but I've never done this before, do let me know if I need to do something else. The release workflow runs when a new tag is pushed to the repo. I'll do so once I'm back home. |
While the actions that the release workflow have been deprecated, they still work (for now). I've created release v0.3.1, so you should be able to update the PKGBUILD to use that new version. |
Ok, thanks! I just tried doing a version bump and running the command to update sha256 checksums for the I checked into what's going on, and it looks like the release URL has a version mismatch for the release version and version in filename:
I figured that it's probably a bug or release errata since it looks like the |
D'oh! Thanks for catching it... That's what I get when I'm trying to make a release when I really should be in bed. Please use v0.3.2 instead. |
Ok, great! I've found some time to do this today. |
Describe the bug
The
PKGBUILD
currently on AUR failed to build with compilation errors inpinelog.c
.To Reproduce
Steps to reproduce the behavior:
yay -Sy libx52
Expected behavior
Package should build and install successfully.
Screenshots/Logs
Build log error:
Full
yay -Sy libx52
LogEnvironment (please complete the following information):
Output of
x52bugreport
:N/A
- could not build, so this utility is not installedgcc --version
:Additional context
N/A
The text was updated successfully, but these errors were encountered: