Look, you can be a PITA all you want. I am now facing a personal issue back home due to a death in my family. So I would appreciate it if you would back off. My world does not revolve around your inability to resolve the issue on your own. I stated I would do the needful once I am able. So, please, back off or learn how to resolve the issue on your own until I have a chance.
Search Criteria
Package Details: wsjtx-improved 3.2.0.260908-1
Package Actions
| 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) |
Dependencies (17)
- boost-libs
- fftw (fftw-amdAUR)
- hamlib (hamlib-gitAUR, hamlib-noindi-gitAUR)
- libusb (libusb-gitAUR)
- portaudio
- qt5-base (qt5-base-gitAUR, qt5-base-headlessAUR)
- qt5-multimedia
- qt5-serialport (qt5-serialport-gitAUR)
- qt5-tools
- qt5-websocketsAUR (qt5-websockets-gitAUR)
- readline (readline-gitAUR)
- asciidoc (asciidoc-gitAUR) (make)
- asciidoctor (make)
- boost (boost-gitAUR) (make)
- cmake (cmake3AUR, cmake-gitAUR) (make)
- gcc-fortran (gcc-fortran-gitAUR, gcc-fortran-snapshotAUR) (make)
- texinfo (texinfo-gitAUR) (make)
Required by (3)
- openwebrx-plus (requires wsjtx) (optional)
- openwebrx-plus-git (requires wsjtx) (optional)
- sparksdr-bin (requires wsjtx) (optional)
Sources (1)
KF5U commented on 2026-05-13 15:36 (UTC)
lycanananas commented on 2026-05-13 08:22 (UTC)
I will be pain in the ass. But I am still waiting for proper release.
KF5U commented on 2026-05-05 13:50 (UTC)
They aren't workarounds; they are solutions to resolve your issue. You are definitely a funny person. As stated, I am out of town, so I guess you have to wait until I can get back to resolve this to YOUR liking for YOU. I will take care of this when I have a chance once I am back in town.
lycanananas commented on 2026-05-04 20:54 (UTC)
I am not looking for workaround. I looking into solution.
KF5U commented on 2026-05-04 19:37 (UTC)
I am out of town on a business trip. Once I get back in town, I can address. Have you tried any of the suggestions I made below?
lycanananas commented on 2026-05-04 15:16 (UTC)
Any news? I still cannot upgrade this package on my another computer because of broken package version.
KF5U commented on 2026-04-30 15:50 (UTC)
And I already stated that I will address the versioning issue you are pointing out. I am not in a physical place to take care of it at this time...my process is typically automated, but this would be something I need to address manually until I have time to change my pipeline. Once I am able, I can address it.
KF5U commented on 2026-04-30 15:45 (UTC) (edited on 2026-04-30 15:53 (UTC) by KF5U)
So running yay -S wsjtx-improved --cleanbuild or removing the package cache does not work for you? My personal laptops worked with both options mentioned when I was recreating the issue.
lycanananas commented on 2026-04-30 15:34 (UTC)
Issue is still present it didn't disappear. On my another PC yay still do not sees new version of PKGBUILD because there are three versions with numer 3.1.0-260418.
From those commits: * Demote -Werror=format-security to warning for clean-install builds * Add boost-libs to depends (fix libboost_log_setup.so runtime error on clean i... KF5U * Update wsjtx-improved to version 3.1.0-260418
https://wiki.archlinux.org/title/PKGBUILD#pkgrel
pkgrel
The release number. This is usually a positive integer number that allows to differentiate between consecutive builds of the same version of a package. As fixes and additional features are added to the PKGBUILD that influence the resulting package, the pkgrel should be incremented by 1. When a new version of the software is released, this value must be reset to 1. In exceptional cases other formats can be found in use, such as major.minor.
It would be fine if those three commits would be version * 3.1.0-26041803 * 3.1.0-26041802 * 3.1.0-26041801
Please look for example for webkit2gtkpackage. It had multiple releases in last days due to packing problems. Every new change is new PKGREL so package managers like yay can see that there was change.
KF5U commented on 2026-04-30 15:14 (UTC)
When I have time, I will work to introduce the requested versioning change functions into my pipeline. However, I am also not going to continue sitting here and arguing the point. I appreciate the suggestions and will address them in future builds if a similar issue arises. Thanks!
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].