Hi @iyanmv
The release should be stable now, someone has made a PR to improve the stability, I apologize for the non-consistent behavior so far.
The release should always be on the latest early-adopter now, hopefully.
| Git Clone URL: | https://aur.archlinux.org/burpsuite.git (read-only, click to copy) |
|---|---|
| Package Base: | burpsuite |
| Description: | An integrated platform for performing security testing of web applications (free edition) |
| Upstream URL: | https://portswigger.net/burp/ |
| Licenses: | custom |
| Submitter: | daronin |
| Maintainer: | tux268 (dkasak, AkechiShiro) |
| Last Packager: | AkechiShiro |
| Votes: | 123 |
| Popularity: | 0.27 |
| First Submitted: | 2008-02-14 18:49 (UTC) |
| Last Updated: | 2026-02-24 23:26 (UTC) |
Hi @iyanmv
The release should be stable now, someone has made a PR to improve the stability, I apologize for the non-consistent behavior so far.
The release should always be on the latest early-adopter now, hopefully.
Hi @MrColdboot,
I just saw your comment, sorry for the delay
Any PR onto the current automation work would be gladly welcome if you're able to improve and stabilize the versioning, AFAIK this package should always follow Early Adopter.
The Stable version creeping up is due to the way I get the latest version, there might be some tweaks that could fix it (more grep/sed).
Regarding the Update to vX.X.X commit message, I wanted to add the version number but I failed and then I left it as it is currently.
Unfortunately I'm no longer using ArchLinux but I can review and merge improvements PR, they are more than welcome.
I'd be willing to help if you don't have the time.
You seem to be going back and forth between the Stable and Early Adopter versions, breaking the package updates. Also, the package version in PKGBUILD doesn't always match the version actually installed. For example, the version I currently have built is reported 2025.5(-1), but the burpsuite version is 2025.5.1.
Aside from that, the commit messages are just a long list of Update to, with no version or other information.
Can we decide on whether this is going to follow the stable or early adopter releases and fix some of these issues?
And you have done it again... "upgrade" from 2025.5.1-1 to 2025.4.4-1 without any explanation or epoch bump. If by mistake you update the PKGBUILD to an early adopter release and you want to go back the stable series, simply increase the epoch.
You should not downgrade the pkgver (2025.2.1-1 -> 2025.1.3-1) without increasing epoch.
I've tried to automatically script the update of Burpsuite on this repo : https://github.com/AkechiShiro/aur-burpsuite
Feel free to let me know any improvements, the CI runs every Monday at 10 A.M. UTC, this should help keep the package up to the latest early adopter release every week.
EDIT : 2025-12-23
The release should be stable now, someone has made a PR to improve the stability, I apologize for the non-consistent behavior so far.
PR: https://github.com/AkechiShiro/aur-burpsuite/pull/5
The release should always be on the latest early-adopter now, hopefully.
The right sha256 for the jar file is: 07b055873c5e8955695c3cd41515763352a285c410939b25b4b8050f7c876a90 As reported in https://portswigger.net/burp/releases
For some reason the integrity check is failing, it seems that the upstream package was changed (or somehting else).
requires java 21
Pinned Comments
AkechiShiro commented on 2024-07-20 14:13 (UTC) (edited on 2025-12-23 15:21 (UTC) by AkechiShiro)
I've tried to automatically script the update of Burpsuite on this repo : https://github.com/AkechiShiro/aur-burpsuite
Feel free to let me know any improvements, the CI runs every Monday at 10 A.M. UTC, this should help keep the package up to the latest early adopter release every week.
EDIT : 2025-12-23
The release should be stable now, someone has made a PR to improve the stability, I apologize for the non-consistent behavior so far.
PR: https://github.com/AkechiShiro/aur-burpsuite/pull/5
The release should always be on the latest early-adopter now, hopefully.