Package Details: goose-desktop 1.46.0-1

Git Clone URL: https://aur.archlinux.org/goose-desktop.git (read-only, click to copy)
Package Base: goose-desktop
Description: Goose Desktop (built from source) - an open source, extensible AI agent that goes beyond code suggestions - install, execute, edit, and test with any LLM
Upstream URL: https://github.com/aaif-goose/goose
Keywords: goose
Licenses: Apache-2.0
Conflicts: goose-desktop-bin
Provides: goose-desktop
Submitter: dbirks
Maintainer: sheikhlimon
Last Packager: sheikhlimon
Votes: 9
Popularity: 0.137516
First Submitted: 2025-04-16 04:56 (UTC)
Last Updated: 2026-08-12 16:12 (UTC)

Latest Comments

1 2 3 Next › Last »

sheikhlimon commented on 2026-07-27 22:19 (UTC) (edited on 2026-07-27 22:21 (UTC) by sheikhlimon)

@chadsr good catch, thanks! fixed in -2

chadsr commented on 2026-07-27 11:41 (UTC)

This fails on 1.44.0 with error: package(s) 'goose-server' not found in workspace.

It seems goose-server no longer exists and the generated files it used to produce (crates/goose/acp-schema.json, crates/goose/acp-meta.json) are already committed in the release tarball, so regeneration isn't needed during packaging.

Removing cargo run -p goose-server --bin generate_schema from the PKGBUILD seems to work fine.

thelooter commented on 2026-07-09 20:49 (UTC)

Broken with pnpm 11 (current extra/pnpm). pnpm install/pnpm run package fail with ERR_PNPM_EXOTIC_SUBDEP, ERR_PNPM_IGNORED_BUILDS, then electron-forge's "node-linker must be hoisted" preflight. Cause: pnpm 11 no longer reads package.json#pnpm or ui/.npmrc's node-linker, and renamed onlyBuiltDependencies -> allowBuilds.

Fix — migrate the settings into ui/pnpm-workspace.yaml in prepare():

cat >> ui/pnpm-workspace.yaml <<'YAML'

allowBuilds: '@modelcontextprotocol/ext-apps': true electron: true electron-winstaller: true esbuild: true overrides: react: ^19.2.4 react-dom: ^19.2.4 blockExoticSubdeps: false nodeLinker: hoisted YAML

Builds cleanly after this (tested on 1.41.0).

sheikhlimon commented on 2026-05-17 14:51 (UTC)

Hey, thanks for reporting this. I haven't been able to reproduce the hang locally pnpm run package completes fine for me on Node 24.10.0.

Could you share a bit more about your build environment?

  • node --version and pnpm --version
  • The full build log(ideally with makepkg -L or extra-x86_64-build if you're using devtools)
  • Whether this happens in a clean chroot or only in your local environment

I'm wondering if it could be something environment-specific, missing lib, display server interaction, or something in the build context that differs from a standard setup.

esdaniel commented on 2026-05-15 07:00 (UTC)

My install hangs at this stage: ◼ Running postPackage hook

On exiting via CTRL-C I get the following:

(node:247495) [DEP0205] DeprecationWarning: module.register() is deprecated. Use module.registerHooks() instead. (Use node --trace-deprecation ... to show where the warning was created) [me@host]$  ELIFECYCLE  Command failed.

sheikhlimon commented on 2026-05-08 19:48 (UTC)

Replaced npx with pnpm run package and added --frozen-lockfile — no npm dependency needed anymore. Let me know if you still hit issues.

rifrif commented on 2026-05-07 03:41 (UTC)

Please update the package, it still requires npm to build correctly.

sheikhlimon commented on 2026-03-31 06:25 (UTC)

The package previously used npm, but since migrating to pnpm, it may no longer be required - nodejs should provide npx which might be sufficient. However, clang is indeed needed.

Gimmeapill commented on 2026-03-22 11:01 (UTC)

npm as well, otherwise it doesn't build in a clean chroot with extra-x86_64-build

Gimmeapill commented on 2026-03-22 08:26 (UTC)

clang should as well be added to makedepends

1 2 3 Next › Last »