Arch Linux User Repository

Hi! GitButler team member chiming in.

There is a slight misconfiguration in this PKGBUILD, as surfaced in this issue: https://github.com/gitbutlerapp/gitbutler/issues/13732#issuecomment-4475055438

The environment variable CHANNEL should be set to "release" when building a release build. As that is not set in the build environment here, the build falls back on development settings for certain details, such as where global cache, data and logs are stored. It also apparently in the above case affected login flow. While the latter is being fixed for the upcoming release, it would still be more correct to set CHANNEL=release to prevent issues like this in the future. Edit: I misunderstood the "fix", without CHANNEL=release the build is now assuming a dev login flow, meaning that CHANNEL must be set for the build to behave properly.

There is a pretty significant side effect to setting CHANNEL, however: all global user data will be lost, most notably forge integrations and projects. Note that for the latter, no VCS data is lost; GitButler will just "forget" where the projects are located and you need to add them again. But for the builds to behave properly, it needs to be done.

Checksum failing again. The gitbutler-bin package still works though.

Upstream re-tagged this after the initial release. See background story here: https://github.com/gitbutlerapp/gitbutler/issues/11525#issuecomment-3657412658

I've updated the checksum in this package, but because it is not just the same code with a new checksum it is actually 6 or 7 new commits, I also bumped the pkgrel so that people with -1 will be prompted to rebuild. This will be an ongoing fiasco because now all the people that built it already have to do so again, but if they have the original tag downloaded in their pkgsrc cache they will need to clear that and force a new download to get a checksum match and the actual current code.

I'm experiencing the same md5sum mismatch as @miwig. The gitbutler-bin package works though.

==> Validating source files with sha256sums... gitbutler-release-0.14.35.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check!

Hey @alerque,

This package needs more hacks to actually build it correctly :) As packaged, it is basically non-functional because the frontend part is not built at all.

Please take a look and apply: https://0x0.st/8pKP.mbox

Edit: sent you a PR.

Just built this package (with yay). I can't start it correctly. I get:

jespera@thinkit ~> gitbutler-tauri
2025-03-19T10:25:09.159540Z  INFO crates/gitbutler-tauri/src/main.rs:64: system git executable for fetch/push: "git"
2025-03-19T10:25:09.159590Z  INFO crates/gitbutler-tauri/src/main.rs:104: starting app version=0.0.0 name=GitButler Dev
[2025-03-19][10:25:09][tauri::manager][ERROR] AssetNotFound("index.html")

A window is opened but in the "main contents" of the window it states:

asset not found: index.html

I'm guessing there is something I'm doing wrong. Any pointers to where I can start looking?

can't install since the checksum is wrong

sha256sum gitbutler-release-0.14.4.tar.gz
f646cf82e4dafd4dcc275a40a1125e1ce7cac22f44ac77f250552619f1826b48  gitbutler-release-0.14.4.tar.gz

Chiming in as a GitButler team member here. The PKGBUILD looks alright, except for that the build cmd should be tauri build, as that also triggers the sveltekit build and packages in the FE. cargo build only does the backend.

So basically: pnpm exec tauri build --config crates/gitbutler-tauri/tauri.conf.release.json

Just installed this version of gitbutler. When I run it, it shows "asset not found: index.html"