Package Details: teensyduino 1.57-1

Git Clone URL: https://aur.archlinux.org/teensyduino.git (read-only, click to copy)
Package Base: teensyduino
Description: Arduino SDK with Teensyduino
Upstream URL: http://www.pjrc.com/teensy/teensyduino.html
Keywords: arduino pjrc teensy
Licenses: GPL, custom, LGPL
Conflicts: arduino, teensy-loader, teensy-loader-cli, teensy-loader-cli-git
Provides: arduino, teensy-loader, teensy-loader-cli
Submitter: Koromix
Maintainer: fabian-ang
Last Packager: fabian-ang
Votes: 25
Popularity: 0.147532
First Submitted: 2013-12-17 03:33 (UTC)
Last Updated: 2022-08-05 10:10 (UTC)

Dependencies (9)

Required by (12)

Sources (7)

Latest Comments

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

n0tty commented on 2018-10-26 15:44 (UTC) (edited on 2018-10-26 15:47 (UTC) by n0tty)

Apparently, yes there is this issue. Starting build()... -> Running Teensyduino installer (takes around 50 seconds) TeensyduinoInstall.linux64: no process found X I/O error

However, on further investigating it, it seems to be the error in "teensyduino.sh" script. Specifically this part, killall $(basename $1) >/dev/null || exit 1 [ -d $2/hardware/teensy ] || exit 1

This bit of error (TeensyduinoInstall.linux64: no process found) comes here (killall $(basename $1) >/dev/null)

afaik this also needs some changes in xdotool function being utilized. Here was my quick fix on xdotool in teensyduino.sh, however, the build() still fails - https://gist.github.com/n0tty/5349fc0a974936ee3eb637db75c95e72 SHA256 checksum - c57dc1d48a21a0af59a7566cd48e97044cdf811c5a745a2954747606b1ba7aa6

Here is what I get,

-> Running Teensyduino installer (takes around 50 seconds)

/home/.../.cache/pacaur/teensyduino/PKGBUILD: line 49: 2473 Killed xvfb-run ./teensyduino.sh "./TeensyduinoInstall.linux${_bits}" "${srcdir}/arduino-${_arduino}"

==> ERROR: A failure occurred in build().

Aborting...

faultylee commented on 2018-10-17 08:15 (UTC)

Hi, is anyone else getting this error? ==> Starting build()... -> Running Teensyduino installer (takes around 50 seconds) TeensyduinoInstall.linux64: no process found X I/O error

Files are there, and when I run TeensyduinoInstall.linux64 by hand it works. I suspect it's failing at xvfb-run. Not sure why.

sogaiu commented on 2018-09-10 09:50 (UTC)

An updated PKGBUILD for version 1.43 can be found at: https://pastebin.com/4jstYtjH

ptb commented on 2018-05-03 20:53 (UTC)

A updated PKGBUILD for version 1.41 can be found at https://pastebin.com/QtSDUk6g

kingstondude commented on 2018-01-19 11:46 (UTC)

Can we please get the PKGBUILD updated with the new checksum for 49-teensy.rules..

Maybe instructions for how to install this broken package would be a second best option.

I'm not sure how to go about changing the PKGBUILD myself..

Franek commented on 2017-09-10 16:45 (UTC)

The source file 49-teensy.rules fails its checksum, it must have been changed upstream. Everything works fine after updating the checksum in the PKGBUILD. 031de0b26991b5a3b19c497d9c0a17f86c40c55d925b9d07d19ab89f2286469d

mh00h commented on 2017-01-14 20:30 (UTC)

When this package has been installed, I see the following stderr with each yaourt installation. error: file owned by 'arduino-builder' and 'teensyduino': 'usr/share/arduino/hardware/platform.keys.rewrite.txt' error: file owned by 'arduino-builder' and 'teensyduino': 'usr/share/arduino/hardware/platform.txt'

parkerlreed commented on 2016-12-15 23:04 (UTC) (edited on 2016-12-15 23:05 (UTC) by parkerlreed)

There has got to be a better way to automatically run the Teensyduino installer than sending it keystrokes... I'll dig into this and see if I come up with something.

mh00h commented on 2016-11-06 16:55 (UTC)

Looks like the md5 for 49-teensy.rules has changed, breaking the PKGBUILD.

lmat commented on 2016-10-17 22:53 (UTC)

hv15 Excellent work! I can't imagine what kind of research would have led to this correct correction! I have the same error. I made the change you suggested, and of course, you also have to modify PKGBUILD:35 from that long hash to SKIP (or, of course, you can create a new hash for it...).