Package Details: anki-git r11894.f927aa578-1

Git Clone URL: https://aur.archlinux.org/anki-git.git (read-only, click to copy)
Package Base: anki-git
Description: Helps you remember facts (like words/phrases in a foreign language) efficiently
Upstream URL: https://github.com/ankitects/anki
Keywords: anki memorise memory study
Licenses: AGPL-3.0-or-later
Conflicts: anki, anki-bin, anki-official-binary-bundle, anki20
Provides: anki
Submitter: degeberg
Maintainer: blackthorne
Last Packager: blackthorne
Votes: 25
Popularity: 0.000000
First Submitted: 2017-02-12 11:51 (UTC)
Last Updated: 2025-07-07 06:18 (UTC)

Pinned Comments

blackthorne commented on 2025-05-09 19:48 (UTC)

the PKGBUILD should be compiling now. if not, please let me know. i'll try and clean up the PKGBUILD soon, try and get rid of the AUR dependency, compiler optimization flags, etc.

@hmry thanks for the rust-clang-linking fix.

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 Next › Last »

ivs_er commented on 2021-09-02 10:57 (UTC)

Getting a bazel error while building the latest version, stack trace:

Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make java.lang.String(byte[],byte) accessible: module java.base does not "opens java.lang" to unnamed module @9353778
    at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:357)
    at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
    at java.base/java.lang.reflect.Constructor.checkCanSetAccessible(Constructor.java:188)
    at java.base/java.lang.reflect.Constructor.setAccessible(Constructor.java:181)
    at com.google.devtools.build.lib.unsafe.StringUnsafe.<init>(StringUnsafe.java:75)
    at com.google.devtools.build.lib.unsafe.StringUnsafe.initInstance(StringUnsafe.java:56)
    at com.google.devtools.build.lib.unsafe.StringUnsafe.<clinit>(StringUnsafe.java:37)
    ... 19 more

MartinX3 commented on 2021-08-31 20:36 (UTC)

@DarkShadow44 Yes, exactly, I thought the version variable would be useless and the aur helper would anyway generate the correct version, instead of showing you the static version.

DarkShadow44 commented on 2021-08-31 20:33 (UTC)

Yes, now it doesn't show it as changed. But you went back to the old versioning scheme, right?

MartinX3 commented on 2021-08-31 17:51 (UTC)

@DarkShadow44 Hmmm, i thought the default pkgver variable is useless, if I use the pgkver() function. Does it work now?

DarkShadow44 commented on 2021-08-31 16:37 (UTC) (edited on 2021-08-31 16:37 (UTC) by DarkShadow44)

Sorry, I don't really understand how the helper(s) do that. I just know that yay isn't the only one to flag anki-git as changed, despite it not being changed.

MartinX3 commented on 2021-08-31 11:09 (UTC) (edited on 2021-08-31 11:09 (UTC) by MartinX3)

@DarkShadow44 I just switched the dummy version of this package to the real anki version to not get confused with package updates.

But the real version of this package should be generated by the "pkgver()" function in the PKGBUILD and be used by your AUR helper.

Or did I read the wiki wrong? VCS_package_guidelines#The_pkgver()_function

DarkShadow44 commented on 2021-08-30 22:26 (UTC)

Hey, stupid question, but yay always shows this package as changed: r8319.ab20f215b-1 -> 2.1.47-1 Any idea why that is? It used to work before.

MartinX3 commented on 2021-08-30 16:59 (UTC)

@DarkShadow44 you're welcome :)

Probably a basel bug not removing the old version, since it's both aqt, just with different minor versions. O.o

DarkShadow44 commented on 2021-08-30 16:28 (UTC) (edited on 2021-08-30 16:28 (UTC) by DarkShadow44)

Thanks! Just a small heads up, I got a strange issue when building, like

Processing ./bazel-bin/qt/aqt/aqt-2.1.48-py3-none-any.whl
ERROR: Cannot install aqt 2.1.47 (from /var/cache/yay/anki-git/src/anki-git/bazel-bin/qt/aqt/aqt-2.1.47-py3-none-any.whl) and aqt 2.1.48 (from /var/cache/yay/anki-git/src/anki-git/bazel-bin/qt/aqt/aqt-2.1.48-py3-none-any.whl) because these package versions have conflicting dependencies.

I solved it by deleting ~/.cache/bazel

Just in case someone has the same problem...

MartinX3 commented on 2021-08-29 23:01 (UTC) (edited on 2021-08-29 23:05 (UTC) by MartinX3)

@DarkShadow44 Thank you I must be blind

I updated the package now, thank you :)