Package Details: betaflight-configurator 10.10.0-1

Git Clone URL: https://aur.archlinux.org/betaflight-configurator.git (read-only, click to copy)
Package Base: betaflight-configurator
Description: Crossplatform configuration tool for the Betaflight flight control system
Upstream URL: https://github.com/betaflight/betaflight-configurator
Licenses: GPL3
Submitter: FryDay
Maintainer: Jake
Last Packager: Jake
Votes: 18
Popularity: 0.000309
First Submitted: 2018-01-24 18:06 (UTC)
Last Updated: 2024-05-16 21:40 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

andrej commented on 2019-03-24 03:34 (UTC)

Thanks for maintaining this. It would be helpful to pass command-line arguments in the launcher script. I tried to run multiple instances of the configurator, for which you have to set --user-data-dir, and it didn't work at all, as described on GitHub. :-)

Jake commented on 2018-09-06 13:37 (UTC)

Sure, done.

btreecat commented on 2018-09-05 17:11 (UTC)

Can the workaround be included in the mean time so the package is not broken?

Jake commented on 2018-08-21 20:19 (UTC)

Ahh yes, that makes sense, it builds from the release zip, which does not contain the git info... Another workaround is to build inside the AUR package git repo, so it picks the commit hash from there, that is what i always do, so i didn't notice this error. A fix would be to clone the whole repo and it would obviously need git as makedepend then.

I tracked it down to this pull request/commit: https://github.com/betaflight/betaflight-configurator/pull/1154 hoping for an answer and better solution from the developers.

jhalfmoon commented on 2018-08-21 06:36 (UTC) (edited on 2018-08-21 07:31 (UTC) by jhalfmoon)

"Not sure why, but I can't build the latest version..."

+1 ; I was just about to report the exact same thing. This fix / workaround worked for me:

build() {
    cd $pkgname-$pkgver
    git init
    git add .
    git commit -m 'ThereIfixedIt'
    yarn install
    ./node_modules/.bin/gulp dist --linux64
}

Tahvok commented on 2018-08-21 06:11 (UTC) (edited on 2018-08-21 06:23 (UTC) by Tahvok)

Not sure why, but I can't build the latest version:

added 7 packages from 6 contributors and audited 7540 packages in 8.083s
found 8 vulnerabilities (2 low, 5 moderate, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details
[09:10:55] Finished 'dist_src' after 8.73 s
[09:10:55] Starting 'dist_locale'...
[09:10:55] Finished 'dist_locale' after 20 ms
[09:10:55] Starting 'dist_libraries'...
[09:10:55] Finished 'dist_libraries' after 22 ms
[09:10:55] Starting 'dist_resources'...
[09:10:55] Finished 'dist_resources' after 60 ms
[09:10:55] Starting 'getChangesetId'...
[09:10:55] 'getChangesetId' errored after 7.13 ms
[09:10:55] Error: Command failed: git log -1 --format="%h"
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

    at ChildProcess.exithandler (child_process.js:289:12)
    at ChildProcess.emit (events.js:182:13)
    at ChildProcess.EventEmitter.emit (domain.js:460:23)
    at maybeClose (internal/child_process.js:961:16)
    at Socket.stream.socket.on (internal/child_process.js:380:11)
    at Socket.emit (events.js:182:13)
    at Socket.EventEmitter.emit (domain.js:460:23)
    at Pipe._handle.close (net.js:599:12)
[09:10:55] 'dist' errored after 8.86 s
==> ERROR: A failure occurred in build().
    Aborting...

Jake commented on 2018-07-07 22:46 (UTC) (edited on 2018-07-07 22:46 (UTC) by Jake)

Yes, thanks, i forgot that npm is only a optional dependency from node. It is added now (also in the blackbox-explorer package).

kbabioch commented on 2018-07-07 22:13 (UTC)

npm should be added as makedependency, since the build failed for me:

[4/4] Building fresh packages... success Saved lockfile. $ npm run _postinstall /bin/sh: npm: Kommando nicht gefunden. error Command failed with exit code 127.

FryDay commented on 2018-07-06 14:32 (UTC)

Done https://lists.archlinux.org/pipermail/aur-requests/2018-July/025219.html

Jake commented on 2018-07-06 10:06 (UTC)

You can't cancel it through the web interface, but you could reply to the mailing list message to explain the changed situation. https://lists.archlinux.org/pipermail/aur-requests/2018-June/025125.html