AUR (en) - anki

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: anki 24.11-1

Package Actions

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:	178
Popularity:	6.93
First Submitted:	2021-09-17 22:31 (UTC)
Last Updated:	2024-11-30 10:33 (UTC)

Dependencies (30)

python (python37^AUR, python311^AUR, python310^AUR)
python-beautifulsoup4
python-certifi
python-decorator
python-distro
python-flask-cors
python-jsonschema
python-markdown
python-orjson (python-orjson-git^AUR)
python-protobuf (python-protobuf-git^AUR)
python-pyqt6-webengine
python-pysocks
python-requests
python-send2trash
python-waitress
qt6-multimedia
qt6-svg
cargo (rustup-git^AUR, rust-nightly-bin^AUR, rust-git^AUR, rust-beta-bin^AUR, rustup-stub^AUR, rust, rustup) (make)
git (git-git^AUR, git-gl^AUR) (make)
mold (mold-git^AUR) (make)
ninja (ninja-kitware^AUR, ninja-mem^AUR, ninja-fuchsia-git^AUR, ninja-git^AUR, ninja-jobserver^AUR) (make)
nodejs (nodejs-lts-fermium^AUR, nodejs-git^AUR, python-nodejs-wheel^AUR, nodejs-lts-hydrogen, nodejs-lts-iron) (make)
python-installer (python-installer-git^AUR) (make)
python-wheel (make)
rsync (rsync-git^AUR, rsync-reflink^AUR, rsync-reflink-git^AUR) (make)
yarn (yarn-pnpm-corepack^AUR, corepacker^AUR, yarn-berry^AUR) (make)
lame (lame-svn^AUR, lame-altivec^AUR) (optional) – record sound
mplayer (mplayer-vaapi^AUR, mplayer-gui-svn^AUR) (optional) – play sound
mpv (mpv-light-pulse^AUR, mpv-amd-full-git^AUR, mpv-full-git^AUR, mpv-full^AUR, mpv-git^AUR, mpv-full-build-git^AUR, mpv-build-git^AUR) (optional) – play sound. prefered over mplayer
texlive-most (optional) – render LaTex in cards

Required by (2)

kindle2anki-git
subs2srs (optional)

Sources (7)

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 30 Next › Last »

<deleted-account> commented on 2023-05-05 13:35 (UTC)

Anyone else getting this errors?

/usr/bin/ld: final link failed: bad value
          collect2: error: ld returned 1 exit status

  = note: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
  = note: use the `-l` flag to specify native libraries to link
  = note: use the `cargo:rustc-link-lib` directive to specify the native 
libraries to link with Cargo (see https://doc.rustlang.org/cargo/reference/build-scripts.html#cargorustc-link-libkindname)

error: could not compile `archives` due to previous error

[9/76; 1 active; 65.690s] rslib/i18n
ninja: build stopped: subcommand failed.

Build failed. ==> ERROR: A failure occurred in build(). Aborting... error: failed to build 'anki-2.1.62-2': checking dependencies...

AlexBocken commented on 2023-05-04 15:55 (UTC)

@AutomaticUpdates good idea! As of my understanding, the anki devs have their own method for optimizing their build process which is enabled by calling ./tools/build. I'm not quite sure about this but I also couldn't find any further information on optimization on their github besides them recommending to act like this.

I played around with the build process but couldn't get it working by for example adding --release at the cargo build step (and adjusting appropriate further steps). At least to me it feels like significant patching would be required for it to work.

If you have a working PKGBUILD, patches or any ideas, please post them here, I'm glad to see what others can do to improve this package.

AutomaticUpdates commented on 2023-05-04 13:46 (UTC)

The cargo build command that is run results in a unoptimized debug binary. It would be great if it would build the binary in release mode

boarim commented on 2023-04-18 12:28 (UTC)

I got an error during the build phase with pyenv:

     Running `out/rust/debug/configure`
[16/76; 3 active; 388.493s] pyenv
FAILED: /home/remi/build/aur/anki/src/anki/out/pyenv/bin/python /home/remi/build/aur/anki/src/anki/out/pyenv/bin/pip /home/remi/build/aur/anki/src/anki/out/pyenv/bin/pip-compile /home/remi/build/aur/anki/src/anki/out/pyenv/bin/pip-sync /home/remi/build/aur/anki/src/anki/out/pyenv/bin/mypy /home/remi/build/aur/anki/src/anki/out/pyenv/bin/black /home/remi/build/aur/anki/src/anki/out/pyenv/bin/isort /home/remi/build/aur/anki/src/anki/out/pyenv/bin/pylint /home/remi/build/aur/anki/src/anki/out/pyenv/bin/pytest /home/remi/build/aur/anki/src/anki/out/pyenv/bin/protoc-gen-mypy 
/home/remi/build/aur/anki/src/anki/out/rust/debug/runner pyenv /home/remi/build/aur/anki/src/anki/out/extracted/python/bin/python3 /home/remi/build/aur/anki/src/anki/out/pyenv  python/requirements.base.txt python/requirements.dev.txt python/requirements.qt6_4.txt
Command failed:

Any idea why?

snpefk commented on 2023-04-12 09:36 (UTC)

Having trouble building cargo part:

error: unexpected argument '-f' found

  note: to pass '-f' as a value, use '-- -f'

Usage: runner build [ARGS]...

For more information, try '--help'.
    Finished dev [unoptimized + debuginfo] target(s) in 0.11s
     Running `out/rust/debug/configure`
    Finished dev [unoptimized + debuginfo] target(s) in 0.12s
error: unexpected argument '-f' found

  note: to pass '-f' as a value, use '-- -f'

Usage: runner build [ARGS]...

For more information, try '--help'.

Build failed.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: anki-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
anki - exit status 4

dough.mean commented on 2023-04-05 17:39 (UTC)

I had the same issue as @a-bostaurus, but apparently my /etc/resolv.conf was not correctly configured. This fixes it for me:

# ln -rsf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

More details in the wiki: https://wiki.archlinux.org/title/systemd-resolved#DNS

AlexBocken commented on 2023-04-03 12:06 (UTC)

@a-bostaurus Hmmm, should work with the default key server without any issues. Might be your gpg conf if it is peculiar.

a-bostaurus commented on 2023-04-03 10:46 (UTC)

@AlexBocken: The Problem is still existing. My terminal says: "gpg --receive-keys C0A351979B37E3B9 gpg: Empfangen vom Schlüsselserver fehlgeschlagen: Server zeigt einen unbestimmten Fehler an" (gpg: Receive from key server failed: server displays an unspecified error). Perhaps the keyserver is down.

AlexBocken commented on 2023-04-02 12:25 (UTC) (edited on 2023-05-13 10:29 (UTC) by AlexBocken)

If your build aborts due to "unknown public key" like this:

==> Verifying source file signatures with gpg...
    anki git repo ... FAILED (unknown public key C0A351979B37E3B9)
==> ERROR: One or more PGP signatures could not be verified!

Please manually import this key once via gpg --receive-keys <key-id> as below.

✖ 1 anki ❯❯❯ gpg --receive-keys 814EA4E90C34AF39A712DE703F5566A2D16899FB
gpg: key 3F5566A2D16899FB: public key "Anki Signatures <gpg@ankiweb.net>" imported
gpg: Total number processed: 1
gpg:               imported: 1

This is best practice for packages to ensure security.

AlexBocken commented on 2023-04-02 12:20 (UTC)

@tocic good point. I must have missed this when changing to the git sources instead of the tarballs. Might be a bit annoying to have to manually import this key on first install but the security implications are definitely valid. New PKGBUILD (did not bump pkgrel as resultant build should not change) includes the pgp signature as well as relying on the tag commit hashsum instead of the tag name to be more reliable. Thanks for commenting!