5a788a6249
* Since release 2.1.55, upstream has changed the build system to a homebrew solution written in Rust, which generates the files for ninja(1) and then uses the latter also for building. As a result, quite a number of patches, that revolved around the Bazel build system, can now be removed and the Makefile can also be slimmed down considerably. By environment variables recognized by the build system, some required binaries (e.g. Python, Node.js, etc.) for the build can be directly defined instead downloading the binary tarballs from the official repositories, which saving quite a bit of patches at the end. In order to be able to build Anki successfully on FreeBSD, a few more environment variables have been introduced via custom patches. With this it's possible to use an offline cache for Node.js as well as a native Python environment instead of a venv. * Belatedly add devel/py-orjson as a fixed runtime dependency and although it's still optional in the code, the question is how long this will be the case. Thus update NOT_FOR_ARCH_REASON accordingly and keep ONLY_FOR_ARCH unchanged for now. Changelogs since 2.1.54: https://changes.ankiweb.net/changes/2.1.60-69.html https://changes.ankiweb.net/changes/2.1.50-59.html MFH: No (feature release)
38 lines
1.4 KiB
Text
38 lines
1.4 KiB
Text
[
|
|
{ type: upgrade
|
|
maximum_version: 2.1.54
|
|
message: <<EOD
|
|
The V1 scheduler is no longer supported. If you have not yet updated to V2 or
|
|
V3, you will be prompted to update when you attempt to review cards in 2.1.50+.
|
|
EOD
|
|
}
|
|
{ type: upgrade
|
|
maximum_version: 2.1.62
|
|
message: <<EOD
|
|
The 2.1.58 release fixes an issue in 2.1.57 that caused cards and deck
|
|
presets to be reset to the default ease, if you exported a .colpkg with
|
|
compatibility with older clients enabled, or used the downgrade and quit
|
|
option, then opened the collection again.
|
|
|
|
For the former issue, this occurred to the collection you were exporting
|
|
from, and not just the .colpkg file. If you were affected by this, running
|
|
the following in the debug console after updating should restore your cards
|
|
to the ease they were at when you last reviewed them, if they were not
|
|
reviewed after the problem occurred. Please make a backup before proceeding.
|
|
|
|
updated = 0
|
|
for cid, old, new in mw.col.db.all("select id, factor, (select factor from revlog where cid=cards.id order by id desc limit 1) as factor2 from cards where type=2"):
|
|
if new and old != new:
|
|
card = mw.col.get_card(cid)
|
|
card.factor = new
|
|
mw.col.update_card(card)
|
|
updated += 1
|
|
print("updated", updated)
|
|
|
|
It will print the number of updated cards. Instructions how to use the debug
|
|
console can be found here:
|
|
|
|
https://docs.ankiweb.net/misc.html#debug-console
|
|
EOD
|
|
}
|
|
]
|