anki: upgrade to latest release

[NilsIrl]

https://github.com/ankitects/anki/releases/tag/2.1.19

The structure of the project has changed in 2.1.17.

@oxij @the-kenny @Profpatsch @Enzime

[NilsIrl]

I've tried to do it but I was unable to do it correctly. Here is my attempt: master...NilsIrl:anki_2_1_19

All the changes made on this branch are in the right direction (from what I can tell) so it might be a nice starting point.

[Profpatsch]

Maybe we could start by adding a few tests first.

[nixos-discourse]

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/how-to-override-python-package-anki/8213/3

[bhipple]

A month ago I also gave it a stab and also was unsuccessful, but at least merged a couple PRs cleaning up cruft in the anki expression and getting us a little closer.

[Atemu]

I've been making progress writing a derivation for their new Rust stuff yesterday but am now stuck with a rogue build script trying to access things outside the sandbox.

Highly WIP progress so far: https://github.com/Atemu/nixpkgs/tree/anki-update

[Atemu]

Speaking of which, can I somehow get Rust to tell me which path it's getting "Permission denied" on? By default it only prints a cryptic error message that is incredibly unhelpful.

[Profpatsch]

Speaking of which, can I somehow get Rust to tell me which path it's

getting "Permission denied" on? By default it only prints a cryptic error message that is incredibly unhelpful. Unfortunately not by default, the `std::io::Error` cannot allocate anything on the heap, so it is not allowed to allocate a `PathBuf`. If users want to have better error messages, they have to wrap std::io::Error for these cases.

…

On Tue, Jul 21, 2020 at 9:08 PM Atemu ***@***.***> wrote: Speaking of which, can I somehow get Rust to tell me which path it's getting "Permission denied" on? By default it only prints a cryptic error message that is incredibly unhelpful. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#78449 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYB5ZVOAIVV4DFN45Y2FC3R4XRRLANCNFSM4KLNTASA> .

[Atemu]

I eventually found the culprits using lots of straceing and the rust parts build sucessfully now. I haven't been able to build the whole program to test their correctness yet however.

How would I go about wrapping it in case I encounter something like this in the future? Can I even touch the part which prints the file errors?

[Profpatsch]

How would I go about wrapping it in case I encounter something like this

in the future? Can I even touch the part which prints the file errors? No, this is the `Debug` or `Display` instance of `std::io::ErrorKind`. There has to be other rust users that have solved this problem to some satisfaction. My best guess is wrapping `std::io::Error` into a struct/enum that is constructed using the path when applicable. It’s a rather invasive change that has to be threaded through the application code however.

…

On Wed, Jul 29, 2020 at 5:32 PM Atemu ***@***.***> wrote: I eventually found the culprits using lots of straceing and the rust parts build sucessfully now. I haven't been able to build the whole program to test their correctness yet however. How would I go about wrapping it in case I encounter something like this in the future? Can I even touch the part which prints the file errors? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#78449 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYB5ZVHDQLMIAIES76KYALR6A6JVANCNFSM4KLNTASA> .

[martinetd]

I've been annoyed by that as well - have you made any progress @Atemu?
I'd be willing to spend some time kludging this around a bit more, but if you've already done stuff like building the rust part I'd rather not spend hours doing what you've already done; so even if you're stuck posting an incomplete commit or something would be great! :)
EDIT: I'm blind, just seen you posted a link to your anki-update branch, I'll try to pick it up a bit from there.

(Cc @cideM)

[Atemu]

Days my friend, days.

Pushed some additional stuff I had laying around. Take the commit message to heart though.

Also https://github.com/Atemu/anki/tree/wip-hacks-to-get-nix-build-working