Package Details: wsjtx-improved 3.1.0-260522

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: GPL3
Conflicts: wsjtx
Provides: wsjtx
Submitter: KF5U
Maintainer: KF5U
Last Packager: KF5U
Votes: 5
Popularity: 0.005244
First Submitted: 2023-10-19 07:42 (UTC)
Last Updated: 2026-05-22 15:02 (UTC)

Latest Comments

1 2 3 4 5 6 7 Next › Last »

KF5U commented on 2026-05-29 15:03 (UTC)

I guess you don't understand...the AUR team reviewed the package when you put in your cry for orphaning the package and stated all is well. I will just continue down my path until I have time to adjust my automation to address it AS I HAVE STATED MULTIPLE TIMES during your crying on here. Until I am done dealing with the now multiple deaths that have happened in my family, I will be leaving it as is until I have the time. Stop crying about it, I told you I would address it. Sad that you are letting this affect you so much. As I have stated, my time does not revolve around making you feel comfortable, good, warm, and fuzzy...so leave me the hell alone and I will address my automation once I have time.

lycanananas commented on 2026-05-29 10:07 (UTC)

You still do not understand what happened and what was the case of issue..

PKGVER is used for upstream version. PKGREL is used for PACKAGE revision. You made 3 different PKGBUILD files with same PKGREL so there where three different version of PKGBUILD with different commits. That means that SRCINFO stayed this same.So yay didn't saw update. My yay on different computers stayed on 2nd version. Yay do not use git to check if PKGBUILD changed it used AUR that uses SRCINFO.

Accorting to wiki

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.

src: https://wiki.archlinux.org/title/PKGBUILD#pkgrel

So when you change anything that results in different package you must increase by 1 PKGREL to notify package managers to download new package.

It is edge case only if you stuck with same PKGVER and PKGREL. Package managers do not see update. I came with exactly same issue in Debian years ago.

Now it is "solved" because PKGVER is updated. But if you release new PKGBUILD with same PKGVER and PKGREL for example 3.1.0-260522 as current. .SRCINFO will not regenerate so yay will not see update. Yay will see update if you release as 3.1.0-260523 because it is newer.

jefftheman commented on 2026-05-29 09:37 (UTC)

Thanks for this, it works great, unpacked and installed on the first try.

KF5U commented on 2026-05-26 15:49 (UTC)

And the fact that I have been maintaining this package for 3 years without any other person complaining about the pkgrel other than yourself and being reviewed by the AUR team, tells me that the package is just fine. It can continue down its path and will change once I have time to make said change.

KF5U commented on 2026-05-26 15:46 (UTC)

The package is not broken. It has been reviewed by the AUR team when you requested it to be orphaned because it does not follow the RECOMMENDATION of how to utilize pkgrel and not found to be in any broken/bad state. I told you that I would address this when I have time, and at this time, I do not have time. When I have time, I will fix this package to address YOUR concern, which is not a concern of the AUR team per their previous review. My personal life takes precedence over anything that would soothe your OCD.

lycanananas commented on 2026-05-26 13:23 (UTC)

if you are very proud maintainer and you are according to your qrz. then you need to follow PKG rules and you don't it.

If I would be PITA I would create wsjtx-improved2 package. You are maintaining package not for our self but for OTHERS. That means package cannot be broken, must be upgrade-able etc. If package install only with fresh install and upgrade do not work that means it is broken..

KF5U commented on 2026-05-26 13:19 (UTC)

First off, again, I shared the personal things going on on my side. The process is automated, and I will fix it when I have a chance. You seriously need to stop pestering me about this. The package works as it is done, and there is no requirement for me to address this. Were you able to update the package on your system? If so, then there is no problem, so please leave me be. You are being a complete PITA for ZERO reason. You have attempted to get the package orphaned for no reason and your attempt failed because the package is being updated. Drop it, I will handle this when I have time.

lycanananas commented on 2026-05-25 12:49 (UTC)

By issue I mean PKGREL that do not have serial number. If you need to stick to date it is fine. But add sequence number just like sysops uses for DNS for ages..

https://mxtoolbox.com/problem/dns/dns-soa-serial-number-format

lycanananas commented on 2026-05-25 12:45 (UTC)

I see new release with with same problem..

KF5U commented on 2026-05-13 15:41 (UTC)

The next release, which is coming soon, will automatically resolve your issue if I am unable to get to it in time due to my hectic world right now.

1 2 3 4 5 6 7 Next › Last »