Package Details: anki 24.06.3-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: 169
Popularity: 4.50
First Submitted: 2021-09-17 22:31 (UTC)
Last Updated: 2024-08-02 10:08 (UTC)

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 Next › Last »

Navrxz commented on 2021-11-23 03:26 (UTC)

This package spits out some errors during makepkg -s . Try anki-official-binary-bundle 2.1.49-1 package , It is working well .

ddavo commented on 2021-11-21 09:20 (UTC)

Anki fails to open. Trying to run it from the terminal, I get the following error

anki
Traceback (most recent call last):
  File "/usr/bin/anki", line 16, in <module>
    import aqt
  File "/usr/lib/python3.9/site-packages/aqt/__init__.py", line 15, in <module>
    import anki.lang
  File "/usr/lib/python3.9/site-packages/anki/lang.py", line 12, in <module>
    import anki._backend
  File "/usr/lib/python3.9/site-packages/anki/_backend/__init__.py", line 11, in <module>
    from markdown import markdown
  File "/usr/lib/python3.9/site-packages/markdown/__init__.py", line 29, in <module>
    from .core import Markdown, markdown, markdownFromFile  # noqa: E402
  File "/usr/lib/python3.9/site-packages/markdown/core.py", line 26, in <module>
    from . import util
  File "/usr/lib/python3.9/site-packages/markdown/util.py", line 88, in <module>
    INSTALLED_EXTENSIONS = metadata.entry_points(group='markdown.extensions')
TypeError: entry_points() got an unexpected keyword argument 'group'

Maybe it's a dependency error?

AlexBocken commented on 2021-10-27 10:38 (UTC) (edited on 2021-10-27 10:38 (UTC) by AlexBocken)

Thanks for the help from @pawggers and @Nocifer. I've added a check in prepare to delete ts/node_modules if present.

Nocifer commented on 2021-10-27 10:18 (UTC)

I can't say for certain about the lot of them but in the case of the two I have used in recent years, yay & paru, the default is to just ask you if you want to do a clean build, and if you don't explicitly say so then they keep the build dir intact as cache for future builds (this can also be evidenced by @pawgerr's log). Perhaps a more sure-fire solution would be to proactively look for and delete the ts/node_modules folder in prepare().

AlexBocken commented on 2021-10-26 22:04 (UTC)

Ah awesome, thanks for that info. So can this only occur if one has a previously messed up build and forgot to add -C to makepkg? I seriously doubt that the most common AUR helpers do not use makepkg -C, right?

pawggers commented on 2021-10-26 21:39 (UTC)

Here's the build output of mine as requested

https://pastebin.com/2C3zvhCK

I haven't found a solution yet

Nocifer commented on 2021-10-26 21:05 (UTC)

Nevermind, I just tried to update and failed, saw the error output and remembered the solution: you need to delete the src/anki-x.x.xx/ts/node_modules folder. That's where the problem actually resides (node_modules is generally a pain in the a$$) but Bazel links to src/anki-x.x.xx from within its labyrinthine cache folder, and so it seems as if the problem is inside .cache/bazel when it's really not.

AlexBocken commented on 2021-10-26 20:40 (UTC)

Ah I should've saved the outputs during the failing builds. I can't reproduce it now. I'll sticky my other comment with the request to post the error message here if encountered.

Nocifer commented on 2021-10-26 20:22 (UTC)

I encountered this issue a couple of months ago and solved it, but I can't remember exactly how. Can you post the error message?

AlexBocken commented on 2021-10-26 19:53 (UTC) (edited on 2021-10-26 20:41 (UTC) by AlexBocken)

If you have issues with compiling anki (There seems to be this "missing modules" error for some typescript stuff) and can find a method of fixing it that does not involve doing sudo rm -rf ~/.cache/bazel and trying to reinstall multiple times let me know how you fixed it. Bazel really is a mystery to me at times.

If you have this error, please post the build output here, even if you haven't found a solution yourself