Arch Linux User Repository

@belkka It is probably an upstream bug. Since the original project is now archived, it may be patched by ourselves if the problem can be addressed.

I cannot install the package despite my system being up-to-date. Tail of yay logs:

==> Starting build()...
yarn install v1.22.22
[1/4] Resolving packages...
warning Resolution field "yargs-parser@15.0.1" is incompatible with requested version "yargs-parser@^14.0.0"
warning Resolution field "nth-check@2.0.1" is incompatible with requested version "nth-check@~1.0.1"
warning Resolution field "js-yaml@3.13.1" is incompatible with requested version "js-yaml@~3.1.0"
warning Lockfile has incorrect entry for "ssri@^8.0.1". Ignoring it.
(node:38509) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
warning Resolution field "ejs@3.1.7" is incompatible with requested version "ejs@^2.6.1"
warning Resolution field "node-forge@1.3.0" is incompatible with requested version "node-forge@^0.10.0"
warning Lockfile has incorrect entry for "ansi-regex@^2.0.0". Ignoring it.
warning Resolution field "nth-check@2.0.1" is incompatible with requested version "nth-check@^1.0.2"
warning Resolution field "yargs-parser@13.1.2" is incompatible with requested version "yargs-parser@^4.2.0"
warning Resolution field "ansi-regex@5.0.1" is incompatible with requested version "ansi-regex@^2.0.0"
warning Resolution field "ansi-regex@5.0.1" is incompatible with requested version "ansi-regex@^3.0.0"
[2/4] Fetching packages...
error @achrinza/node-ipc@9.2.2: The engine "node" is incompatible with this module. Expected version "8 || 10 || 12 || 14 || 16 || 17". Got "21.7.3"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: raven-reader-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
raven-reader - exit status 4

The git tag v1.0.80 of raven-reader is currently pointed to the same commit of v1.0.79, which results in source code build failure.

Are gtk2 packages really necessary?

@MithicSpirit You are right. A merge to raven-reader-bin seems ok to me. How about other maintainers?

This package is a misnomer since it utilizes prebuilt binaries rather than building them from source, which requires the -bin suffix according to the AUR Rules of submission:

Packages that use prebuilt deliverables, when the sources are available, must use the -bin suffix. An exception to this is with Java. The AUR should not contain the binary tarball created by makepkg, nor should it contain the filelist.

I have created a PKGBUILD for this raven reader that builds from source, but I cannot upload it currently due to this name already being taken.

EDIT: oh lol I just noticed raven-reader-bin already exists, which is effectively just a dupe of this package since both essentially just extract the appimage and install the files to the correct locations. Maybe this package should just be merged into that one and the maintainers added as co-maintainers (though it would probably be good to talk to @wrenby, the current maintainer of raven-reader-bin first).

The latest version v1.0.60 now crashes on my side.

The latest version since 1.0.61 has started working on my machine.

If your raven-reader crashes like mine, there is one temporary solution.

• backup the "~/.config/Raven\ Reader/config.json"
• and then, delete "~/.config/Raven\ Reader/config.json"
• relaunch raven-reader

This will lose your application preference, but it will make raven-reader work again

@zoorat The new version works fine on my machine. Anyway, I think it's fine to wait until figuring out the problems.

new version v1.0.58 have some problem so don't update it, issue link: https://github.com/hello-efficiency-inc/raven-reader/issues/579