Arch Linux User Repository

Hi there,

1.35.0 has been out there for a week and while an updated PKGBUILD builds, bruno only displays its error screen when I try to test it. I haven't found why yet.

I also have very limited time to work on this issue for now so if you're interested in the 1.35.0, do not hesitate to try and have a go at it.

edit: just tried with 1.36.1 and the issue persists.

edit (2025, 9th of january): issue still persists with 1.38.1.

@D3vil0p3r Did you edit the PKGBUILD? I just cloned the PKGBUILD in a chrooted environment and it built successfully.

edit: since you have a similar issue for the bruno-git PKGBUILD, not related to husky but to rollup for that one, I believe the issue is in your build process/environment: both husky and rollup are installed via npm in the node_modules/.bin/ folder, a path added to $PATH when invoked through the npm command. They should be available for every npm run ... command if the dependencies are correctly installed (done in the prepare function of the PKGBUILD). If you edited the PKGBUILD, make sure this is still done.

Build fails:

Now using node v20.9.0 (npm v10.1.0)
Creating default alias: default -> v20.9.0
npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.

> prepare
> husky install

sh: line 1: husky: command not found
npm notice 
npm notice New minor version of npm available! 10.1.0 -> 10.9.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.0
npm notice Run npm install -g npm@10.9.0 to update!
npm notice 
npm ERR! code 127
npm ERR! path /tmp/makepkg/bruno/src/bruno-1.32.0
npm ERR! command failed
npm ERR! command sh -c husky install

npm ERR! A complete log of this run can be found in: /tmp/makepkg/bruno/src/npm-cache/_logs/2024-10-09T18_51_48_610Z-debug-0.log
==> ERROR: A failure occurred in prepare().
    Aborting...

Hi there,

For reason unknown, the package for version > 1.24 build correctly but bruno does not start correctly. Please kindly wait while I try to fix it on my free time.

Cheers

edit: Found the issue. It's been fixed.

Hi there,

I just updated to 1.22.0. Enjoy the updated electron dependency to electron31. No need anymore to fetch an old electron version from the AUR.

** On the reasons under the nvm makedepend.

From @lumac0:

Making nvm a required dependency is a little intrusive if the system is using a different version manager like asdf. Requiring a specific version of node (or just node) may simplify the build.

nvm (as a make dependency) is needed if we want to build bruno with the same node version used by the upstream, which is what's aimed here: same node version, same electron version, etc. This node version will never be used nor stored outside of the packaging directory (please see line 34 in the previous link) and therefore won't contaminate you host with unneeded nodejs versions.

You can find the .nvmrc in the upstream repository here and the requirement for the electron version there.

Please see the related documentation on archlinux's wiki on using nvm in packaging here.

For those interested, same thing about how to build against the system's electron here.

Please note that if you don't want the hassle of building this application, you can use the binary release from github directly from the PKGBUILD under the name bruno-bin.

edit: formatting then using this post to pin some information.

Making nvm a required dependency is a little intrusive if the system is using a different version manager like asdf. Requiring a specific version of node (or just node) may simplify the build.

Thank you!

Sorry for the delay, 1.8.0 is now packaged.