Arch Linux User Repository

So, I discovered the package nekoray-mahdi-zarei-bin, first submitted in February 2025 (when the original project's authors had not yet officially announced its discontinuation), which uses the fork's repository.

To avoid duplicating identical packages and causing division among the 'fans' of the original, I decided to roll back the version to use the original repository instead, removing broken additional dependencies and adding a version conflict with the newer nekoray-mahdi-zarei-bin.

I’m also dropping support for this package, as maintaining a package for a project that has reached EOL (End of Life) seems pointless.

In turn, I advise following the original project author’s recommendation and finding an alternative client.

For those interested, Mahdi-zarei/Nekoray is currently continuing development under the name Throne (throne-bin), and can be installed alongside MatsuriDayo/nekoray.

So, I discovered the package nekoray-mahdi-zarei-bin, first submitted in February 2025 (when the original project's authors had not yet officially announced its discontinuation), which uses the fork's repository.

To avoid duplicating identical packages and causing division among the 'fans' of the original, I decided to roll back the version to use the original repository instead, removing broken additional dependencies and adding a version conflict with the newer nekoray-mahdi-zarei-bin.

I’m also dropping support for this package, as maintaining a package for a project that has reached EOL (End of Life) seems pointless.

In turn, I advise following the original project author’s recommendation and finding an alternative client.

@Adrian.Carver I perfectly understand the difference between a fork and the original. But apparently, you still haven't grasped what happened to the original project. The 'About' section of the original repository now states: 不再维护，自寻替代品。 - "No longer maintained, find your own replacement." This means there will be no more updates, bug fixes, or vulnerability patches for the original. And yes, it still works for now, but over time — on top of everything else — even its compatibility with the SignBox core server may degrade.

So in this case, manually rolling back and freezing updates won’t affect the "die-hard users" at all — simply because there will be no more updates for the original.

@labaman, you really can't see the difference between the latest version of the original repository and its fork with the same name by a different author? It makes no difference whether the original repository was archived or not - a fork is a fork. In this case, it's unstable and stripped down.

As a result of your “update”, a fair number of users have had to roll back the version or manually install the latest version from the original author and block the package update, which is not good. The question about the expediency of your intervention in this case remains open.

@labaman That was probably a me problem, I should've tried restarting Plasma before writing the comment. Oh well, I'm on the non-bin version now so hopefully everything is fine for everyone else.

@legalize_nukes but why? Everything is included in the package. The desktop file is created by the post_install script and removed by post_rm. The icon used is part of the package.

@Adrian.Carver Because the original developers have stopped working on the project. Since March of this year, all repositories have been archived. There will be no more improvements or fixes for the "old" version. The fork by Mahdi-zarei is currently the only repository where development is still ongoing.

@labaman, and why would you do that? They are different versions from different developers. They're different repositories. What was the purpose of making the changes?

The old version is stable. The new ones are not. Why would it be necessary to mess with something that works? Were you itching?

Could you please add back the icons and the .desktop file?

@ali.molaei my bad. I thought the source of package is https://github.com/Mahdi-zarei/nekoray