algernon [1] filed a deletion request for chrysalis [2]:

I am the upstream maintainer and primary developer of Chrysalis, and I
am requesting the deletion of the `chrysalis` package in that
capacity.

The major reason for the request is that the way this package is made
completely breaks Chrysalis. Running with an external Electron is
unsupported upstream to begin with, and results in Chrysalis not
finding some of its static assets, such as the firmware files it is
supposed to flash. This already breaks an important capability of the
application.

On top of that, the packaging upgrades Electron from version 17 to 19.
This breaks pretty much every functionality of the package, because of
breaking changes within Electron. We have intentionally stayed on
Electron 17 upstream due to this reason. Anything higher introduces
subtle bugs that simply do not exist with Electron 17. We will upgrade
Electron once we verified that the regressions have been fixed, or if
we figure out how to work them around.

Due to these issues, and after numerous reports on our Discord by
frustrated Arch users, we added a sanity check at startup, that
verifies Chrysalis is running in a sane environment. For the past two
releases, when installed via the `chrysalis` package in AUR, the
application displays this screen on start:

https://user-
images.githubusercontent.com/17243/193005865-46313413-5ae7-46d4-b52b-8438c7ced2a0.png

Running Chrysalis with an external Electron, one that is TWO MAJOR
VERSIONS HIGHER than what is officially supported is never, ever going
to work.

Please remove the package, so it doesn't cause more confusion and
frustration among Chrysalis users that happen to use Arch.

If you need more information, you can email me at
[email protected].

Thanks in advance!

[1] https://aur.archlinux.org/account/algernon/
[2] https://aur.archlinux.org/pkgbase/chrysalis/

Reply via email to