Package Details: graphite-editor-git r2430.d6c06da-1

Git Clone URL: https://aur.archlinux.org/graphite-editor-git.git (read-only, click to copy)
Package Base: graphite-editor-git
Description: raster & vector editor with a modern node-based, non-destructive, procedural workflow
Upstream URL: https://github.com/GraphiteEditor/Graphite
Licenses: Apache-2.0
Conflicts: graphite-editor
Provides: graphite-editor
Submitter: alerque
Maintainer: alerque
Last Packager: alerque
Votes: 3
Popularity: 0.47
First Submitted: 2024-03-29 23:19 (UTC)
Last Updated: 2025-12-09 23:08 (UTC)

Latest Comments

alerque commented on 2025-12-09 23:06 (UTC)

Thanks to this major contribution the GUI is back and working again in this build! I think there is some cleanup that could be done, but it's definitely working to play around in again now.

alerque commented on 2025-07-09 13:36 (UTC)

I've made only partial progress on this. I'm about to post an update that builds again, but only the CLI is working, the Tauri based desktop UI is not here. If anybody figures out the right incantation to get that to build and which pieces to package as well I'm open to suggestions or PRs to this repo.

alerque commented on 2025-07-03 15:56 (UTC)

Yes the shape of the build system has changed a bit, I'm trying to work out the best incantation for the current shape of things.

andykluger commented on 2025-06-09 20:06 (UTC) 

==> Starting build()...
error: invalid value 'app' for '--bundles [<BUNDLES>...]'
  [possible values: deb, rpm, appimage]

  tip: a similar value exists: 'appimage'

wallabra commented on 2025-01-19 02:22 (UTC)

Their Contributor guide refers to a different command to initiate a release build. In PKGBUILD's build() this could be done as:

pushd frontend
mold-run npm run build # the build command indicated by Graphite
popd

In the end, however, in the current Git version, this also crashes because of some cryptic, non-verbose cargo-about related issue:

Generating license information for Rust code

cargo-about failed null 
Could not run `cargo about`, which is required to generate license information.
To install cargo-about on your system, you can run `cargo install cargo-about`.
License information is required in production builds. Aborting.

This whole situation is very strange and, frankly, does not reflect very well on their project setup tenacity.

wallabra commented on 2025-01-19 01:40 (UTC) (edited on 2025-01-19 01:40 (UTC) by wallabra)

I'm getting a different error.

==> Starting build()...
     Running beforeBuildCommand `npm run tauri:build-wasm`
npm error Missing script: "tauri:build-wasm"
npm error
npm error To see a list of scripts, run:
npm error   npm run
npm error A complete log of this run can be found in: /home/gustavo/.npm/_logs/2025-01-19T01_39_48_168Z-debug-0.log
       Error beforeBuildCommand `npm run tauri:build-wasm` failed with exit code 1
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat 'target/release/graphite-cli': No such file or directory
install: cannot stat 'target/release/graphite-desktop': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...
error: failed to build 'graphite-editor-git-r1409.46a9fc0-1':

(there is nothing after the colon at the end, curiously)

That1Calculator commented on 2024-05-12 20:45 (UTC)

Getting the same error as @maderios

maderios commented on 2024-04-19 11:13 (UTC)

I get this error


[INFO]: ✨   Done in 9m 55s
[INFO]: 📦   Your wasm pkg is ready to publish at ./wasm/pkg.
       Error Unable to find your web assets, did you forget to build your web app? Your distDir is set to ""../dist"".
==> Starting check()...
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat 'target/release/graphite-cli': No such file or directory
install: cannot stat 'target/release/graphite-desktop': No such file or directory