Arch Linux User Repository

Changed 2026-08-18:
- The chirp-next mirror on my GitHub page includes both the source tarball and the .AppImage of the current release and of past releases back to 20260814, along with SHA1SUMS (upstream published checksums) and checksums.txt (upstream SHA1 published checksums plus my locally generated SHA256 checksums of the release assets).
- I have also created a chirp-next-bin AUR package that installs the upstream .AppImage binary to provide quicker installation. This package also remains available for those who prefer to watch gcc at work.

@GaryScottMartin All fair points, I hope upstream does indeed at least add sha256sums.

@jsimon0, I understand your argument. However, SHA1 hashes are now considered cryptographically broken, as they are subject to practical collision attacks. Please see this December 15, 2022 advisory from the US National Institute of Standards and Technology (NIST): NIST Retires SHA-1 Cryptographic Algorithm. I have written to the upstream developers of chirp-next and asked them to convert to the use of SHA256 hashes.

If you wish to continue personally assuring the provenance of the package that I am currently mirroring (entirely reasonable, I certainly take no offense), then I suggest that you inspect checksums.txt from the mirror, either here (mirror repo home page), or here (actual release artifact). You can then directly compare the SHA256 hash from checksums.txt with the value computed by and directly reported by GitHub for the source tarball and the SHA256 hash contained in the PKGBUILD.

Alternatively, if you wish to be assured only that the source tarball SHA1 hash matches the upstream SHA1 hash, you can clone the package from the AUR and edit the PKGBUILD yourself to change sha256sums in line 27 to sha1sums, then run updpkgsums from the command line in your cloned AUR directory. It will update the PKGBUILD with the calculated SHA1SUM of the mirrored package. You can then compare that hash against the published hash at the chirp archive.

Just be aware that, since SHA1 is no longer a secure means of assurance, matching SHA1 hashes don't prove that the mirrored package, or I, myself, am trustworthy.

@GaryScottMartin Thanks for taking over the package. I encourage you to continue using SHA1 checksums for these files to make it easier to cross reference against the SHA1SUM file posted by the CHIRP project. As an example, in the prior version of this package's PKGBUILD, I could pull the SHA1 checksum right out of the PKGBUILD and compare to the file on CHIRP's site so, even if the tarballs came from a mirror, the checksums had to match and in front of my eyes. To be clear, I'm not suggesting that you aren't trustworthy, but I'm sure you can imagine people why want to be able to validate the checksums themselves against the checksums of record provided by the upstream project.

Changed 2026-08-18:
- The chirp-next mirror on my GitHub page includes both the source tarball and the .AppImage of the current release and of past releases back to 20260814, along with SHA1SUMS (upstream published checksums) and checksums.txt (upstream SHA1 published checksums plus my locally generated SHA256 checksums of the release assets).
- I have also created a chirp-next-bin AUR package that installs the upstream .AppImage binary to provide quicker installation. This package also remains available for those who prefer to watch gcc at work.

Download link does not work (404). It does work with pkgver=20260807. But why does it not use https://archive.chirpmyradio.com/chirp_next/next-20260807/chirp-20260807.tar.gz ?

chirp-next-1:20260522-1 will build just fine, but I cannot run it. When running from console, I get:

ModuleNotFoundError: No module named 'yattag'.

On 2024-12-28 I see this should be fixed with python-yattag-1.16.1-1, but this is already installed. I tried re-installing it, but this also did not work.

Is there a newer version of python-yattag to be pulled in now? Or is it something to do with virtualenv/venv that Python cannot find it? (Python is a bit out of my wheelhouse, I don't know how to look deeper sorry). Thanks!

EDIT: I removed chirp-next and dependencies, cleaned the build directories, rebuilt, re-installed them and now it runs.

Quick fix. If you have the package and the makepkg script (snapshot) from here, edit the PKGBUILD file to:

# Maintainer: WT5A <K5TRP[at]onlyhams[dot]ca>
# Maintainer: Helmut Stult <hst[at]e-mail[dot]de>
# Thanks to the maintainer(s) of chirp-daily

pkgname=chirp-next
pkgver=20260130
pkgrel=1
epoch=1
pkgdesc="GUI tool for programming ham radios (Local Source Build)"
arch=('any')
url="https://chirpmyradio.com/projects/chirp/wiki/Home"
license=('GPL-3.0-or-later')
depends=('python-pyserial' 'python-requests' 'python-suds'
         'python-yattag' 'python-wxpython' 'python-lark-parser')
optdepends=('hamradio-menus: XDG menus for ham radio software')
makedepends=('python-build' 'python-installer' 'python-wheel' 'python-setuptools')
options=(!emptydirs)
conflicts=('chirp' 'chirp-daily')
provides=(chirp)
install=$pkgname.install

# Pointing to the local file in the base directory
source=("chirp-${pkgver}.tar.gz")

# Since you have the file, we use 'SKIP' or the specific hash.
# I kept your hash here to ensure the file you have is the correct one.
sha1sums=('9b62a2aaedd1d9f54ca21be99761bf0ef91f791e')

build() {
    cd "chirp-${pkgver}"
    python -m build --wheel --no-isolation
}

package() {
  _site_packages=$(python -c "import site; print(site.getsitepackages()[0])")
  cd "chirp-$pkgver"
  python -m installer --destdir="${pkgdir}" dist/*.whl

  install -D -m644 "chirp/share/chirpw.1" "${pkgdir}/usr/share/man/man1/chirp.1"
  install -D -m644 "chirp/share/chirp.desktop" "${pkgdir}/usr/share/applications/chirp.desktop"
  install -D -m644 "chirp/share/chirp.png" "${pkgdir}/usr/share/pixmaps/chirp.png"

  # Ensure locale directory exists and copy
  mkdir -p "${pkgdir}${_site_packages}/chirp"
  cp -dr --preserve=mode,timestamp "chirp/locale/" "${pkgdir}${_site_packages}/chirp/locale"
}

Then makepkg -si as normal.

Given the cloudflare issue it might be better to build directly from git (I have not seen recent tags but if the release cycle is merely weekly (as it seems to be), it shouldn't be too hard to track it).

AFAIK this is the official repo https://github.com/kk7ds/chirp