Package Details: anki-git r11208.b7cb0c0d0-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: hhttps://apps.ankiweb.net/
Keywords: anki memorise memory study
Licenses: AGPL3
Conflicts: anki, anki-official-binary-bundle, anki20
Provides: anki
Submitter: degeberg
Maintainer: DarkShadow44
Last Packager: DarkShadow44
Votes: 25
Popularity: 0.000469
First Submitted: 2017-02-12 11:51 (UTC)
Last Updated: 2024-08-29 18:32 (UTC)

Latest Comments

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

ghorshy commented on 2021-09-02 14:36 (UTC)

Tried to update anki for few days but this error comes up:

ERROR: Cannot install anki 2.1.46 (from /home/manjaro/.cache/yay/anki-git/src/anki-git/bazel-bin/pylib/anki/anki-2.1.46-cp38-abi3-manylinux2014_x86_64.whl) and anki 2.1.47 (from /home/manjaro/.cache/yay/anki-git/src/anki-git/bazel-bin/pylib/anki/anki-2.1.47-cp38-abi3-manylinux2014_x86_64.whl) because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested anki 2.1.46 (from /home/manjaro/.cache/yay/anki-git/src/anki-git/bazel-bin/pylib/anki/anki-2.1.46-cp38-abi3-manylinux2014_x86_64.whl)
    The user requested anki 2.1.47 (from /home/manjaro/.cache/yay/anki-git/src/anki-git/bazel-bin/pylib/anki/anki-2.1.47-cp38-abi3-manylinux2014_x86_64.whl)

I tried to -Rns in yay but now I can't install this package at all.

MartinX3 commented on 2021-09-02 11:03 (UTC)

@ivs_er If it's new, please open an issue ticket.

Or you need maybe java 16?

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