Search Criteria
Package Details: chirp-next 1:20251212-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/chirp-next.git (read-only, click to copy) |
|---|---|
| Package Base: | chirp-next |
| Description: | GUI tool for programming ham radios |
| Upstream URL: | https://chirpmyradio.com/projects/chirp/wiki/Home |
| Keywords: | ham radio |
| Licenses: | GPL-3.0-or-later |
| Conflicts: | chirp, chirp-daily |
| Provides: | chirp |
| Submitter: | WT5A |
| Maintainer: | WT5A (schinfo) |
| Last Packager: | schinfo |
| Votes: | 83 |
| Popularity: | 0.50 |
| First Submitted: | 2023-01-22 22:04 (UTC) |
| Last Updated: | 2025-12-12 22:14 (UTC) |
Dependencies (11)
- python-lark-parser
- python-pyserial (python-pyserial-labgrid-gitAUR)
- python-requests
- python-suds
- python-wxpython (python-wxpython-gitAUR)
- python-yattagAUR
- python-build (make)
- python-installer (make)
- python-setuptools (make)
- python-wheel (make)
- hamradio-menusAUR (optional) – XDG menus for ham radio software
Latest Comments
1 2 3 4 5 6 .. 16 Next › Last »
Omar007 commented on 2025-12-02 17:40 (UTC) (edited on 2025-12-02 17:47 (UTC) by Omar007)
Once the epoch has been set, it should not be removed again. Any release without the epoch set to 1 (or larger if needed) will be regarded as an older version.
EDIT: To provide some more context; you generally only ever need to use the epoch when the versioning scheme that the software uses is changed or if it has no stable versioning number (and you can't use a commit count or something).
Once the epoch is set, any package without it or a lower number will be regarded as outdated, a higher number is always more recent. If the epoch is equal, normal version matching is done (pkgver and pkgrel).
That means, you can really never ever remove it again, only keep the value set or increase it at some point in the future.
In most, if not all other cases, bumping the pkgrel is the way to go to trigger/force a rebuild if the software version(ing scheme) has otherwise stayed the same but things like the packaging have changed.
loacker commented on 2025-11-01 06:13 (UTC)
@schinfo I think you may eliminate the epoch parameters with the upcoming update cycle.
schinfo commented on 2025-09-21 12:43 (UTC)
Problem is fixed with "epoch"
loacker commented on 2025-09-20 18:46 (UTC)
@schinfo Have you tried using the PKGBUILD's "epoch" feature?
phonemic commented on 2025-09-20 00:42 (UTC)
You should be able to do an interactive rebase and drop the last commit.
git rebase -i HEAD~1
schinfo commented on 2025-09-19 17:18 (UTC)
Sorry, the acute build does not work because there is no 20250919. It was my mistake - the auto-built crap ;-) Unfortunately, I didn't find a way for AUR to go back to version 20250912.
FunctionalHacker commented on 2025-09-19 14:50 (UTC) (edited on 2025-09-19 14:56 (UTC) by FunctionalHacker)
Looks like the checksum is not correct for the latest package
Actually the downloaded file seems like a HTML document. Might be because the newest release available from the upstream is https://archive.chirpmyradio.com/chirp_next/next-20250912/chirp-20250912.tar.gz so no 20250919 is available.
SIGPIG commented on 2025-08-05 17:14 (UTC) (edited on 2025-08-05 17:14 (UTC) by SIGPIG)
any time @schinfo. upgrade went well here, for what that's worth. take it easy. thanks for maintaining!
schinfo commented on 2025-08-05 16:43 (UTC)
@SIGPIG: Thank's for the info. It's fixed!
1 2 3 4 5 6 .. 16 Next › Last »