Package Details: bazecor-git 1.4.3.4439-1

Git Clone URL: https://aur.archlinux.org/bazecor-git.git (read-only, click to copy)
Package Base: bazecor-git
Description: Graphical configurator for Dygma Raise. Development branch
Upstream URL: https://github.com/Dygmalab/Bazecor
Licenses: GPL3
Conflicts: bazecor
Provides: bazecor
Submitter: TimQuelch
Maintainer: TimQuelch
Last Packager: TimQuelch
Votes: 5
Popularity: 0.000379
First Submitted: 2022-03-23 02:20 (UTC)
Last Updated: 2024-08-03 08:53 (UTC)

Dependencies (7)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

voidzero commented on 2025-04-29 13:16 (UTC)

Hi maintainer, bazecor-git requires npm 22 now, please update the nvm commands to reflect that. Thank you.

TimQuelch commented on 2024-08-03 07:12 (UTC)

Apologies for the delay. I've pushed some changes which should fix the build issues.

The package will now also install and own the udev rules so that you are not prompted by bazecor itself to install these on first run.

sammyF commented on 2024-04-17 10:53 (UTC)

any way to get bazecor to build, run and recognize the keyboard?

sagar794 commented on 2024-01-21 05:49 (UTC)

@TimQuelch I created a PR to resolve the mksquashfs error. Please feel free to leave any comments or feedback on the PR.

TimQuelch commented on 2024-01-12 00:10 (UTC)

I've fixed the build commands and versioning issues, however I'm still running into the mksquashfs issue mentioned by rethus.

I'm open to any suggestions or PRs at https://github.com/TimQuelch/bazecor-git-aur

coolapso commented on 2024-01-11 16:56 (UTC) 

==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: 1.3.10-rc.2.3305
 -> error making: bazecor-git-exit status 12
checking dependencies...

why is this out of date for so long? is the package maintainer out?

rethus commented on 2023-07-24 10:27 (UTC) (edited on 2023-07-24 10:36 (UTC) by rethus)

build faild with: 

error Command "build:linux" not found.

A short look into the git-repository shows, that they changed the command from build:linux to make-lin

https://github.com/Dygmalab/Bazecor/blob/development/package.json#L21C6-L21C14

But even if I change this in the PKGBUILD during installing the package, I got an additional error: 

[STARTED] Making a AppImage distributable for linux/x64
[FAILED] mksquashfs returned non-zero code: '1'
[FAILED] mksquashfs returned non-zero code: '1'

An unhandled rejection has occurred inside Forge:
Error: mksquashfs returned non-zero code: '1'
at EventEmitter.<anonymous> (/tmp/pamac-build-rethus/bazecor-git/src/bazecor-git/node_modules/@reforged/maker-appimage/src/main.ts:339:54)
    at Object.onceWrapper (node:events:628:26)
    at EventEmitter.emit (node:events:513:28)
    at EventEmitter.emit (node:domain:489:12)
    at ChildProcess.<anonymous> (/tmp/pamac-build-rethus/bazecor-git/src/bazecor-git/node_modules/@reforged/maker-appimage/src/utils.ts:197:49)
    at ChildProcess.emit (node:events:525:35)
    at ChildProcess.emit (node:domain:489:12)
    at maybeClose (node:internal/child_process:1100:16)
    at Socket.<anonymous> (node:internal/child_process:458:11)
    at Socket.emit (node:events:513:28)
    at Socket.emit (node:domain:489:12)
    at Pipe.<anonymous> (node:net:301:12)
error Command failed with exit code 1.

TimQuelch commented on 2022-11-07 23:03 (UTC)

I've updated the PKGBUILD with nvm to use node 16.

devgioele commented on 2022-10-24 17:20 (UTC) (edited on 2022-10-24 18:41 (UTC) by devgioele)

After some debugging, I understood that the Node.js version must be 16. Version 19 makes the prepare phase fail and version 18 makes the build phase fail.

A possible solution is to specify in the PKGBUILD file that the version of the nodejs package must be =16. I think it should be put in makedepends. This causes problems, because almost every other software requiring nodejs asks for the latest version.

The preferred solution is to add nvm, the Node version manager, in makedepends and use it to temporarily set the Node.js version to 16. Running nvm install 16 && nvm use 16 in the prepare phase, before running yarn, should do the job.

devgioele commented on 2022-10-23 16:35 (UTC) (edited on 2022-10-23 16:40 (UTC) by devgioele)

There is only a white screen when I open the application. Looking at the build logs, the command prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild outputs No prebuilt binaries found (target=18. with error code 127.

I am not sure the error is related, but there is a comment in issue 45 that mentions yarn rebuild to fix it.

Does anyone know a solution or have the same white screen?

1 2 Next › Last »