I try my best to always follow all of the Arch package guidelines.
If you think I've missed something or have suggestions, you can:
- Submit a PR or create an issue in my PKGBUILDs repo
- Drop a comment here
- Email me
Search Criteria
Package Details: wootility-appimage 5.0.6-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/wootility-appimage.git (read-only, click to copy) |
|---|---|
| Package Base: | wootility-appimage |
| Description: | Utility for configuring Wooting keyboards |
| Upstream URL: | https://wooting.io/wootility |
| Keywords: | configuration keyboards wootility wooting |
| Licenses: | unknown |
| Conflicts: | wootility |
| Provides: | wootility |
| Submitter: | Freso |
| Maintainer: | AlphaLynx |
| Last Packager: | AlphaLynx |
| Votes: | 19 |
| Popularity: | 1.70 |
| First Submitted: | 2018-07-14 18:07 (UTC) |
| Last Updated: | 2025-07-15 20:49 (UTC) |
Dependencies (3)
Required by (0)
Sources (2)
AlphaLynx commented on 2025-06-29 03:27 (UTC) (edited on 2025-06-29 03:50 (UTC) by AlphaLynx)
AlphaLynx commented on 2025-06-29 00:06 (UTC) (edited on 2025-06-29 00:06 (UTC) by AlphaLynx)
@Quokka after this was orphaned (this request), I've adopted and updated it to the latest v5, and I'll continue to update it going forwards. I think we should now merge wootilty5-appimage into this package
shaybox commented on 2025-03-07 11:23 (UTC)
Please create and merge this to wootility4-appimage so wootility5-appimage can be merged into this package.
Quokka commented on 2025-02-20 23:24 (UTC)
Hi! v5.0.0 Stable was released yesterday. Are you planning on updating this package to v5.0.0 and upwards?
Quokka commented on 2025-02-08 09:55 (UTC)
Thanks for the info @atomo, I just updated the package to the latest version!
atomo commented on 2025-02-08 04:40 (UTC)
New update 5.0.0-beta.8 is released
Quokka commented on 2025-01-26 10:44 (UTC)
Thanks for the info @gpsolo, I just updated the package to the latest version!
gpsolo commented on 2025-01-26 05:51 (UTC)
New beta update 5.0.0-beta.6 just released
BigBrainAFK commented on 2024-07-15 12:13 (UTC)
@Freso We don't actually return a 403 Forbidden anywhere in the route handlers for that api. We also have no blocklist of Tor nodes or other such things. The best I can imagine is that DigitalOcean has some IPs blocked that may also be Tor Nodes which we can't influence.
Pinned Comments
AlphaLynx commented on 2025-06-29 03:27 (UTC) (edited on 2025-06-29 03:50 (UTC) by AlphaLynx)
I try my best to always follow all of the Arch package guidelines.
If you think I've missed something or have suggestions, you can: