Package Details: wsjtx-improved 3.2.0.260908-1

Git Clone URL: https://aur.archlinux.org/wsjtx-improved.git (read-only, click to copy)
Package Base: wsjtx-improved
Description: Software for Amateur Radio Weak-Signal Communication (JT9 and JT65) - WSJT-X Improved by DG2YCB
Upstream URL: https://sourceforge.net/projects/wsjt-x-improved/
Keywords: hamradio wsjtx
Licenses: GPL-3.0-or-later
Conflicts: wsjtx
Provides: wsjtx
Submitter: KF5U
Maintainer: KF5U
Last Packager: KF5U
Votes: 6
Popularity: 0.87
First Submitted: 2023-10-19 07:42 (UTC)
Last Updated: 2026-09-08 18:45 (UTC)

Pinned Comments

KF5U commented on 2026-08-27 19:20 (UTC)

Note on qt5-websockets

Arch has removed qt5-websockets from the official repositories; it now exists only as an AUR package. yay/paru users are unaffected — the dependency resolves automatically. If you build with plain makepkg -s, install qt5-websockets from the AUR first.

If you don't specifically need Qt5, wsjtx-improved-qt6 (and its -al-qt6 / -widescreen-qt6 variants) build against Qt6, where every dependency is still in [extra].

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

lycanananas commented on 2026-04-30 14:52 (UTC)

@KF5U not bumping means many other cannot upgrade your package.. Unless they do clean install..

lycanananas commented on 2026-04-30 14:49 (UTC)

If you want to keep date you can use YYMMDDnn is build of day for example 2604301 and next release from same day cam be 26043002. This is common practice used in DNS zones.

KF5U commented on 2026-04-30 14:48 (UTC)

Understood, however, I am not going to bump the pkgrel. As I stated, I made the call to keep inline with upstream version. Thanks!

lycanananas commented on 2026-04-30 14:45 (UTC)

@KF5U

You are not correct. I am mainly maintainer of deb packages. PKGREL is same was -1 or -2 in Debian versioning for example 2.0.0-3. It is used when:

  1. You fix package by adding patch.
  2. You are genaraly fixing package.

You can use it as you want. But if you keep PKGVER you MUST increase PKGREL by one and regenerate .SRCINFO to let know yay and other managers that package is updated. They use .SRCINFO to check they do not do git pull on AUR to check if new package is available.. it would be veeery slow and painful.

As @itslemonchan said. Changing building flags results in different binary and overall package!!

Please comply to Arch Linux policy.

itslemonchan commented on 2026-04-29 19:55 (UTC)

Still, it should be increased because "As fixes and additional features are added to the PKGBUILD that influence the resulting package, the pkgrel should be incremented by 1." (https://wiki.archlinux.org/title/PKGBUILD#pkgrel)

KF5U commented on 2026-04-29 13:22 (UTC)

You would be correct. To maintain version/package consistency with upstream versioning, this was intentional. Thanks.

lycanananas commented on 2026-04-29 11:19 (UTC)

@KF5U

I think this happend because you commited new PKGBUILD without PKGREL bump and .SRCINFO recreate.

KF5U commented on 2026-04-28 21:13 (UTC)

Thanks for clarifying.

lycanananas commented on 2026-04-28 19:08 (UTC)

Some how yay on three separate Arch install sticked to old commit..

itslemonchan commented on 2026-04-28 14:29 (UTC)

I built this package on a clean environment with the official Docker image (base-20260419.0.517065), so pretty much using a stock makepkg.conf. The PKGBUILD compiles just fine.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »