From: fosslinux <fosslinux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: WIP: anki: update to 2.1.26
Date: Wed, 23 Dec 2020 02:33:21 +0100 [thread overview]
Message-ID: <20201223013321.X3mnaxS8A3_CqhefI-7W2lEYva-ie0dmcO4WhjJR4Rw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22219@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1831 bytes --]
There's a closed pull request on the void-packages repository
WIP: anki: update to 2.1.26
https://github.com/void-linux/void-packages/pull/22219
Description:
This has a wide variety of changes as if you have heard my ranting in #xbps it has turned into a Bad Build System - there is rust, nodejs, python, etc etc, no proper install target...
A few things to note:
- python3-mypy is updated as mypy-protobuf needs the new version, otherwise the build failed.
- same thing with python-protobuf, but for anki and at runtime
- maturin is some weird build system at the intersection of rust and python.
- mypy-protobuf-python is what anki uses for binding python and rust together, partly.
- mypy-protobuf-go is the go implementation of mypy-protobuf-python that I thought should be packaged anywway.
- python-stringcase is a new dependency.
- anki is an archd package (not nocross), because the rust code is obviously platform specific.
Still todo:
- [x] Apply archlinux's aqt_build patch, which stops it from polluting /usr directly (:vomiting_face:)
- [x] Update python3-protobuf - hopefully will fix `AttributeError: module 'google.protobuf.descriptor' has no attribute '_internal_create_key'`.
- [x] Look into travis musl error. https://github.com/rust-lang/rust/issues/40174. Hopefully, using rust 1.44 as the rust version *should* fix this. What a PITA. I understand that this is because it works when I cross-compile to x86_64-musl from x86_64 but we need it to work native build from x86_64-musl for the builders...
- [x] Get off rustup and onto rust stable. Needs either a) pyo3 to work on stable or b) anki to be patched for rust-cpython.
- [x] Blocked by rust 1.44. Blocked by #22739
- [ ] Travis wth on i686?
- [x] Make it open.
- [x] More extensive runtime testing.
- [ ] Runtime test on musl.
next prev parent reply other threads:[~2020-12-23 1:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 6:18 [PR PATCH] " fosslinux
2020-05-23 7:07 ` [PR PATCH] [Updated] " fosslinux
2020-05-24 5:37 ` fosslinux
2020-05-24 5:39 ` fosslinux
2020-05-28 7:38 ` [PR PATCH] [Updated] " fosslinux
2020-05-30 1:53 ` fosslinux
2020-06-01 9:58 ` fosslinux
2020-06-01 9:59 ` fosslinux
2020-06-01 10:05 ` [PR PATCH] [Updated] " fosslinux
2020-06-01 10:28 ` fosslinux
2020-06-01 12:05 ` stpx
2020-12-23 1:33 ` fosslinux [this message]
2021-05-19 14:54 ` ericonr
2021-05-19 16:12 ` sgn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201223013321.X3mnaxS8A3_CqhefI-7W2lEYva-ie0dmcO4WhjJR4Rw@z \
--to=fosslinux@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).