Search Criteria
Package Details: ubiquity 0.4.0-4
Package Actions
Git Clone URL: | https://aur.archlinux.org/ubiquity.git (read-only, click to copy) |
---|---|
Package Base: | ubiquity |
Description: | An open-source, cross-platform markdown editor written in Rust using Tauri, Yew, Tailwind and DaisyUI. |
Upstream URL: | https://github.com/opensourcecheemsburgers/ubiquity |
Licenses: | GPL3 |
Submitter: | opensourcecheems |
Maintainer: | opensourcecheems |
Last Packager: | opensourcecheems |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2023-08-01 11:41 (UTC) |
Last Updated: | 2023-08-01 11:41 (UTC) |
Dependencies (5)
- libayatana-appindicator
- webkit2gtk (webkit2gtk-imgpasteAUR)
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
- pkgconf (pkgconf-gitAUR) (make)
- rustup (rustup-gitAUR) (make)
Latest Comments
alan1world commented on 2024-04-16 14:49 (UTC) (edited on 2024-04-16 14:52 (UTC) by alan1world)
The package isn't out-of-date - latest version of ubiquity is still 0.4.
There are dependencies in the chain which breaks the compilation.
There's several points where specific toolchains are pinned, e.g. in the PKGBUILD:
rustup update nightly-2023-07-07-x86_64-unknown-linux-gnu
rustup component add rust-src --toolchain nightly-2023-07-07-x86_64-unknown-linux-gnu
and in the rust-toolchain:
channel = "nightly-2023-07-07"
All of these I needed to change to simply "nightly" and use the current nightly toolchain. The 2023 set will no longer build.
In frontend's cargo.toml and Trunk.toml, it is locked to wasm-bindgen = "=0.2.86" but this gives an error of "versions that meet the requirements
^0.2.89
are: 0.2.92, 0.2.91, 0.2.90, 0.2.89"also
previously selected package
wasm-bindgen-futures v0.4.36
-> versions that meet the requirements^0.4.39
are: 0.4.42, 0.4.41, 0.4.40, 0.4.39Once all of these changes were made, I was able to compile.
Nice project!