Package Details: anki 24.04.1-2

Git Clone URL: https://aur.archlinux.org/anki.git (read-only, click to copy)
Package Base: anki
Description: Helps you remember facts (like words/phrases in a foreign language) efficiently
Upstream URL: https://apps.ankiweb.net/
Keywords: anki languages learning vocabulary
Licenses: AGPL3
Conflicts: anki-bin, anki-git, anki-qt5
Submitter: demize
Maintainer: AlexBocken
Last Packager: AlexBocken
Votes: 158
Popularity: 7.54
First Submitted: 2021-09-17 22:31 (UTC)
Last Updated: 2024-04-28 10:07 (UTC)

Required by (2)

Sources (7)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 28 Next › Last »

patenteng commented on 2024-03-25 06:46 (UTC)

RAM use when compiling is very high. It went to 10+ GB on my system.

Spixmaster commented on 2024-03-24 21:28 (UTC) (edited on 2024-03-24 21:28 (UTC) by Spixmaster)

@AlexBocken I monitored the RAM usage particularly know. You seem to be right and I hope that that is the reason. Thank you very much!

AlexBocken commented on 2024-03-24 20:08 (UTC) (edited on 2024-03-24 22:06 (UTC) by AlexBocken)

@Spixmaster Thanks for the report! sccache: Compile terminated by signal 9 could indicate that this could be a RAM issue. Could you verify that you still have available memory when this signal is sent?

If not so, consider reducing the parallel compile threads in your /etc/makepkg.conf (MAKEFLAGS=-j<number-of_threads). Of course maybe also try closing memory-hogging applications like a browser during compilation. Using a swap partition could maybe also solve this.

Spixmaster commented on 2024-03-24 17:13 (UTC) (edited on 2024-03-24 17:17 (UTC) by Spixmaster)

The package does not build for me. I tried it twice with the second time with cleaned cache, rm -r .cache/paru/clone/anki/.

[63/65; 1 active; 657.560s] /home/matheus/.cache/paru/clone/anki/src/anki-23.12.1/out/rust/release/runner run cargo build --profile release-lto  --locked -p rsbridge --features rustls
FAILED: /home/matheus/.cache/paru/clone/anki/src/anki-23.12.1/out/rust/release-lto/librsbridge.so
/home/matheus/.cache/paru/clone/anki/src/anki-23.12.1/out/rust/release/runner run cargo build --profile release-lto  --locked -p rsbridge --features rustls
   Compiling syn v2.0.39
   Compiling libc v0.2.150
   Compiling autocfg v1.1.0
   Compiling serde v1.0.193
   Compiling version_check v0.9.4
   Compiling scopeguard v1.2.0
   Compiling once_cell v1.18.0
...
   Compiling rustls-webpki v0.101.7
   Compiling tokio-rustls v0.24.1
   Compiling hyper-rustls v0.24.2
   Compiling reqwest v0.11.22
warning: field `0` is never read
  --> rslib/src/config/bool.rs:57:79
   |
57 | struct BoolLike(#[serde(deserialize_with = "deserialize_bool_from_anything")] bool);
   |        -------- field in this struct                                          ^^^^
   |
   = note: `#[warn(dead_code)]` on by default
help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field
   |
57 | struct BoolLike(#[serde(deserialize_with = "deserialize_bool_from_anything")] ());
   |                                                                               ~~

warning: `anki` (lib) generated 1 warning
sccache: Compile terminated by signal 9
error: could not compile `rsbridge` (lib)
Failed with code Some(101): cargo build --profile release-lto --locked -p rsbridge --features rustls
ninja: build stopped: subcommand failed.

Build failed.
==> FEHLER: Ein Fehler geschah in build().
    Breche ab...
Fehler: ‚anki-23.12.1-2‘ konnte nicht erstellt werden:

AlexBocken commented on 2024-03-24 09:34 (UTC)

Thanks for the feedback. I've bumped the pkgrel to ensure this will be fine for others as well.

Finally figured out how to get rid of mold and still have LTO. This has also been changed. If anki does not build in your environment anymore please comment here or shoot me an email.

0ion9 commented on 2024-03-23 23:01 (UTC)

Rebuild worked this time, so maybe I didn't do it correctly before.

0ion9 commented on 2024-03-23 22:15 (UTC)

Yes, I have tried clean rebuilding before I tried symlinking. Theoretically that is what you would expect when there's an outdated link-time dependency, but rebuilding doesn't seem to have any effect.

I didn't symlink to the old version; anki is looking for the old version, which doesn't exist, so I made a symlink with the name of the old version pointing at the NEW version. Hope that clarifies.

Currently trying another clean rebuild after removing the symlink, just to be absolutely sure.

AlexBocken commented on 2024-03-23 09:24 (UTC) (edited on 2024-03-23 09:54 (UTC) by AlexBocken)

Thanks for the report! Are you sure you are rebuilding properly? I'm struggling to reproduce this issue with svt-av1 2.0.0-1 installed. Could you confirm whether a rebuild of anki would fix this issue for you instead of symlinking to the old version? If so I could bump the pkgver to fix this issue for all users. Otherwise further triage might be needed.

You can do this by either downloading the above listed git repo (git clone https://aur.archlinux.org/anki.git) and doing a makepkg -si in it. Alternatively, if you're using a AUR helper, clear it's cache (e.g. paru -Scc or rm -rf ~/.cache/paru/clone/anki) and reinstall via something like paru -S anki

Thanks for your help

0ion9 commented on 2024-03-23 08:39 (UTC)

Upstream issue maybe? But there is currently an issue where this package looks for libSvtAv1Enc.so.1:

[...]
  File "/usr/lib/python3.11/site-packages/aqt/qt/qt6.py", line 19, in <module>
    from PyQt6.QtWebEngineCore import *
ImportError: libSvtAv1Enc.so.1: cannot open shared object file: No such file or directory

, but svt-av1 provides only libSvtAv1Enc.so{,.2,.2.0.0} (so Anki fails to start). Rebuilding does not help (so maybe upstream is specifically trying to reference that version?)

I symlinked 1 to 2.0.0, and that is enough to get Anki to start, but it's obviously not correct. Hopefully as long as I don't need to deal with AV1 files it will work enough.

The first known version of svt-av1 where this problem occurs is 2.0.0-1 (built 19 Mar 2024)

sloker commented on 2024-02-27 08:53 (UTC)

In ~/.cargo/config I added:

[net]
git-fetch-with-cli = true

And it worked.

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 28 Next › Last »