Arch Linux User Repository

From the official page:

• master: Use this branch as stable/release version
• testing: Use this branch as testing/release canidate

The master branch is "stable" in the sense that works (partially) for older models, and we already had issues when the developer switched the main branch from master to testing and the package was not building anymore. I thought about it, and I believe we must adhere to the development model of OpenCorsairLink, not switch the branches back and forth.

As a consequence, I created opencorsairlink-testing-git.

Hi DanySK, I suggest to keep it simple and just to change it to testing (option 1) and not make any new packages. The issue is that there's nothing stable about the master branch so it would be disingenuous to call it that. OpenCorsairLink is not very mature and not that stable. However, testing branch is much more stable than the master and it's unfortunate that it's called "testing" since that means different things to different people. And testing also supports all the new AIOs that people are actually buying and installing today (master supports mostly old AIOs). As it is right now, binary produced by this package cannot control any of the latest AIOs.

Hi, Batou the problem is that the testing branch was not working, and I had to switch to master. I believe we could create two packages, and either:

• Switch this PKGBUILD to the testing branch, and create a new one for master as opencorsairlink-stable-git
• Keep this one as it is and create opencorsairlink-testing-git

Which one do you believe would work best? I'd be in favor of the second option.

source=(git+https://github.com/audiohacked/OpenCorsairLink#branch=master)

The author of opencorsairlink hasn't updated the master in over 3 months and all the work and patches have gone into the testing branch. Testing branch is the only one that supports majority of AIOs. Also, master branch is extremely buggy and doesn't even work. No one should be using master branch at this point... it's less stable than testing.

Maintainer of this package should switch the source to 'testing' until the author releases a stable version (which won't be anytime soon since he's busy).

Hi CyberShadow, to the best of my knowledge pkgver should automatically set the pkgver variable when makepkg is invoked. Is it possible that the git repo roll-backed some commits? Do you have any idea on how to solve the issue?

DanySK, ping.

Possibly related, but the pkgver is off. The pkgver in the metadata, and as seen here on aurweb, is 20180515-1, but pkgver returns 20180506-1, as that is the date of the last commit on master. As a result, AUR helpers keep thinking this package is newer than the installed one, and will always attempt to reinstall it when looking for updates.

Consider using #branch=master instead of invoking "git checkout".

Yup, works great - thanks!

Please test now if it's back working.

Hi, according to the official documentation the only requirements are libusb and pkg-config. I believe upstream made testing branch the main one. I'm now forcing master.