#linuxcnc-devel Logs

Nov 23 2022

01:58 PM seb_kuzminsky: andypugh: i'm actively working on bullseye & bookworm debs from the buildbot, yes
02:05 PM andypugh: Great, thanks Seb.
02:05 PM andypugh: I am thinking that I might try for a trial bullseye ISO this weekend.
02:05 PM pere: seb_kuzminsky: hi.
02:05 PM seb_kuzminsky: like you, i am trying to fit this work in around other things going on in my life, so i'm making no promises as to the schedule :-/
02:05 PM seb_kuzminsky: andypugh: cool!
02:05 PM seb_kuzminsky: pere: hi :-)
02:05 PM seb_kuzminsky: pere: i will continue to ignore dxf2gcode until the current set of linuxcnc fires are all put out
02:05 PM pere: seb_kuzminsky: ok. is it still used?
02:05 PM seb_kuzminsky: not by me, i switched to https://github.com/sebkuzminsky/svg2gcode
02:05 PM pere: aha. just noticed it on the removal list in debian and decided to have a look.
02:06 PM andypugh: https://www.bodgesoc.org/newfile_script.svg?12
02:06 PM andypugh: (change the number at the end to see a different slice.
02:06 PM seb_kuzminsky: andypugh: did you make those "VALVE 0", "VALVE 1", ... wire labels in the last picture? it looks very professional
02:07 PM andypugh: seb_kuzminsky: Dymo do heat-shrink printable tube.
02:08 PM seb_kuzminsky: 👍
02:09 PM andypugh: https://www.amazon.co.uk/gp/product/B07BPHKRRW
02:12 PM seb_kuzminsky: i'm too embarrassed to show you the wiring job we did in petter's mazak
02:13 PM pere: I thought you liked spagetti? :P
02:50 PM Tom_L: point A to point B and what's inbetween is a secret
03:26 PM cradek: whoa, printing on tube it would never unwind and fall off
03:38 PM JT-Shop22 is now known as JT-Shop2
03:39 PM seb_kuzminsky: hi cradek :-)
04:00 PM linuxcnc-build2: Build [#1](http://buildmaster-2.local:8010/#builders/9/builds/1) of `0000.checkin` 6stopped with exception.
04:41 PM cradek: hi!
04:45 PM linuxcnc-build2: Build [#1](http://buildmaster-2.local:8010/#builders/13/builds/1) of `00-checkin` 6stopped with exception.
04:54 PM linuxcnc-build2: Build [#2](http://buildmaster-2.local:8010/#builders/6/builds/2) of `00-checkin` 6stopped with exception.
04:57 PM seb_kuzminsky: linuxcnc-build2: force build --branch=new-buildbot 00-checkin
04:57 PM linuxcnc-build2: Force build successfully requested.
04:58 PM rene-dev53 is now known as rene-dev5
04:58 PM linuxcnc-build2: Build [#3](http://buildmaster-2.local:8010/#builders/2/builds/3) of `01-rip.debian-09-stretch-rtpreempt-i386` 3completed successfully.
04:58 PM linuxcnc-build2: Build [#3](http://buildmaster-2.local:8010/#builders/1/builds/3) of `01-rip.debian-08-jessie-i386` 3completed successfully.
04:58 PM linuxcnc-build2: Build [#3](http://buildmaster-2.local:8010/#builders/7/builds/3) of `01-rip.debian-12-bookworm-rtpreempt-amd64` 3completed successfully.
04:58 PM linuxcnc-build2: Build [#3](http://buildmaster-2.local:8010/#builders/5/builds/3) of `01-rip.ubuntu-12-04-precise-rtai-i386` 3completed successfully.
05:22 PM linuxcnc-build2: Build [#3](http://buildmaster-2.local:8010/#builders/3/builds/3) of `01-rip.debian-10-buster-rtpreempt-amd64` 8completed with warnings.
05:24 PM linuxcnc-build2: Build [#3](http://buildmaster-2.local:8010/#builders/8/builds/3) of `01-rip.debian-11-bullseye-rtpreempt-amd64` 8completed with warnings.
05:46 PM linuxcnc-build2: Build [#4](http://buildmaster-2.local:8010/#builders/4/builds/4) of `01-rip.debian-07-wheezy-amd64` 3completed successfully.
05:55 PM -!- #linuxcnc-devel mode set to +v by ChanServ
05:56 PM linuxcnc-build2: Worker `checkin` is missing. It was seen last on Wed Nov 23 15:55:01 2022.
06:11 PM linuxcnc-build2: Build [#4](http://buildmaster-2.local:8010/#builders/6/builds/4) of `00-checkin` 3completed successfully.
06:16 PM linuxcnc-build: build #4857 of 4017.deb-wheezy-amd64 is complete: Failure [4failed shell_1] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.deb-wheezy-amd64/builds/4857 blamelist: adamlouis <adamlouis@users.noreply.github.com>, andypugh <andy@bodgesoc.org>
06:17 PM andypugh: seb_kuzminsky: Still here? I don’t understand that error log
06:18 PM seb_kuzminsky: i'll look
06:22 PM linuxcnc-build: build #4854 of 4016.deb-wheezy-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4016.deb-wheezy-i386/builds/4854 blamelist: adamlouis <adamlouis@users.noreply.github.com>, andypugh <andy@bodgesoc.org>
06:23 PM linuxcnc-build: build #3510 of 4021.deb-jessie-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4021.deb-jessie-i386/builds/3510 blamelist: adamlouis <adamlouis@users.noreply.github.com>, andypugh <andy@bodgesoc.org>
06:23 PM seb_kuzminsky: that's weird, it triggered the deb build before the dsc build was done uploading the dsc
06:24 PM linuxcnc-build: build #3506 of 4022.deb-jessie-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4022.deb-jessie-amd64/builds/3506 blamelist: adamlouis <adamlouis@users.noreply.github.com>, andypugh <andy@bodgesoc.org>
06:28 PM seb_kuzminsky: no, it was a misconfiguration - i broke it when i added the 2.9 branch to the newer buildbot workers
06:28 PM seb_kuzminsky: fixing it now
06:31 PM seb_kuzminsky: wheezy-i386 failed because the key debian uses to sign the ancient wheezy package archive expired :-(
06:31 PM seb_kuzminsky: same with the jessie builders
06:47 PM linuxcnc-build: build #4123 of 4014.deb-wheezy-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4014.deb-wheezy-rtpreempt-i386/builds/4123 blamelist: adamlouis <adamlouis@users.noreply.github.com>, andypugh <andy@bodgesoc.org>
06:48 PM linuxcnc-build: build #4148 of 4015.deb-wheezy-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4015.deb-wheezy-rtpreempt-amd64/builds/4148 blamelist: adamlouis <adamlouis@users.noreply.github.com>, andypugh <andy@bodgesoc.org>
06:49 PM linuxcnc-build: build #4544 of 4018.deb-wheezy-rtai-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4018.deb-wheezy-rtai-i386/builds/4544 blamelist: adamlouis <adamlouis@users.noreply.github.com>, andypugh <andy@bodgesoc.org>
06:49 PM andypugh: Maybe time to retire Jessie?
06:49 PM seb_kuzminsky: the wheezy keys published by the debian ftp-masters at https://ftp-master.debian.org/keys.html are expired
06:50 PM seb_kuzminsky: retiring jessie would still leave us with wheezy not building
06:50 PM linuxcnc-build: build #3396 of 4020.deb-jessie-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4020.deb-jessie-rtpreempt-amd64/builds/3396 blamelist: adamlouis <adamlouis@users.noreply.github.com>, andypugh <andy@bodgesoc.org>
06:51 PM seb_kuzminsky: which means we'd be without rtai debs for 2.8 (until we add newer rtai builders to the buildbot)
06:51 PM linuxcnc-build: build #3397 of 4019.deb-jessie-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4019.deb-jessie-rtpreempt-i386/builds/3397 blamelist: adamlouis <adamlouis@users.noreply.github.com>, andypugh <andy@bodgesoc.org>
06:51 PM seb_kuzminsky: pere: do you have any advise for how to deal with debian's expired keys for wheezy and jessie?
06:53 PM andypugh: We have 2.8.4 Buster RTAI debs. https://www.linuxcnc.org/dists/buster/2.8-rt/binary-amd64/linuxcnc_2.8.4_amd64.deb
06:55 PM andypugh: I am a bit concerned that I don’t know where they came from as tha obvious explanation is that I probabl hand-built them.
06:59 PM seb_kuzminsky: yes, i think you (or someone) hand-built them
07:18 PM linuxcnc-build2: Worker `checkin` is missing. It was seen last on Wed Nov 23 17:16:50 2022.
07:19 PM seb_kuzminsky: looks like `apt-get --yes --force-yes` will accept the debs, even though the key that signed the archive is expired
07:19 PM seb_kuzminsky: it's probably not the right way to solve this but i don't know what the right way is
07:32 PM andypugh: At this point. for those distros. I wou;d say what works is good enough. It’s not like anyone using them is going to complain about certificates, if they cared at all about security theoy wouldn;t be using thoe distros.
07:33 PM seb_kuzminsky: good point
07:37 PM seb_kuzminsky: i'll enable this for the distros with expired keys (wheezy and jessie), and leave package signature authentication enabled for all the other distros
07:38 PM andypugh: Sounds pragmatic
07:51 PM seb_kuzminsky: this is the kind of buildbot maintenance work that won't go away if we hire someone else to run the buildbot
07:51 PM seb_kuzminsky: i hear people talking about this option, but i don't see it saving us much time
08:28 PM Tom_L: seb_kuzminsky, you use buildbot gitCommit and gitPush to put the debs back up?
08:28 PM Tom_L: i can't seem to find the right combination of those for my test repo
09:02 PM -!- #linuxcnc-devel mode set to +v by ChanServ
09:03 PM seb_kuzminsky: linuxcnc-build: force build --branch=2.8 0000.checkin
09:04 PM linuxcnc-build: The build has been queued, I'll give a shout when it starts
09:05 PM seb_kuzminsky: Tom_L: I use DirectoryUpload to send the packages from the worker to the buildmaster
09:08 PM Tom_L: is that a part of buildbot?
09:09 PM Tom_L: don't have access to the help atm.. setting up a new ssd
09:09 PM seb_kuzminsky: yes, it's a standard build step in buildbot 0.8
09:09 PM Tom_L: thanks
09:10 PM Tom_L: will that send back to a git repo?
09:10 PM seb_kuzminsky: and in 3.4
09:10 PM Tom_L: using 3.6 i think
09:10 PM seb_kuzminsky: no, it just transfers files, like scp or rsync would
09:10 PM seb_kuzminsky: it's in 3.6 too
09:11 PM seb_kuzminsky: are you trying to commit debs to a git repo?
09:11 PM Tom_L: yes
09:11 PM Tom_L: i get success until i try using gitcommit and gitpush
09:11 PM Tom_L: can't seem to find the right combination
09:12 PM seb_kuzminsky: what error do you get frmo gitcommit?
09:13 PM Tom_L: Build [#39](http://localhost:8010/#builders/1/builds/39) of `buildtests` failed.
09:13 PM Tom_L: <messenger> Build [#38](http://localhost:8010/#builders/2/builds/38) of `runtests`
09:13 PM Tom_L: also failed.
09:13 PM Tom_L: the deb gets built locally
09:14 PM Tom_L: on the worker
09:14 PM Tom_L: i don't have access to the master.cfg right now.. setting things up on a different ssd
09:16 PM seb_kuzminsky: do you have the www interface set up? that's the best way i've found to see how the build is going, and what all the errors are
09:16 PM Tom_L: localhost?
09:16 PM Tom_L: yes
09:16 PM Tom_L: i think so
09:16 PM Tom_L: i've been watching the logs
09:17 PM seb_kuzminsky: ok cool, yeah those logs are what i was talking about
09:17 PM seb_kuzminsky: just the error message in irc doesn't shed much light
09:17 PM Tom_L: yeah
09:20 PM -!- #linuxcnc-devel mode set to +v by ChanServ
09:30 PM Tom_dev: seb_kuzminsky, you see anything that stands out? http://paste.debian.net/1261653/
09:30 PM Tom_L: i'm really too new to know what i don't know :)
09:31 PM Tom_L: that's the commit & push parts i found
09:33 PM seb_kuzminsky: that looks like the buildmaster log
09:33 PM Tom_L: you want the worker?
09:34 PM Tom_dev: http://paste.debian.net/1261654/
09:35 PM Tom_dev: meh, i skipped the commit part
09:36 PM seb_kuzminsky: the logs from the buildbot processes are useful, but that's not what i meant either
09:36 PM Tom_L: oh
09:36 PM seb_kuzminsky: i mean the logs that the buildbot collects of what it runs and what the output of those commands was
09:37 PM seb_kuzminsky: like the stdio logs
09:38 PM Tom_dev: not sure where to find those
09:38 PM seb_kuzminsky: like this: http://highlab.com/~seb/linuxcnc/Screenshot%20from%202022-11-23%2020-35-35.png
09:38 PM Tom_dev: ok
09:38 PM seb_kuzminsky: like if you click on the link that your buildmaster posted in irc, it should take you there
09:39 PM Tom_dev: yeah i found it
09:44 PM linuxcnc-build: build #2220 of 4042.deb-buster-rtpreempt-rpi4 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4042.deb-buster-rtpreempt-rpi4/builds/2220 blamelist: adamlouis <adamlouis@users.noreply.github.com>, Phillip Carter <phillcarter54@gmail.com>
09:46 PM seb_kuzminsky: ugh
09:47 PM Tom_dev: email required?
09:47 PM Tom_dev: maybe that is it..
09:49 PM Tom_dev: http://tom-itx.no-ip.biz:81/~webpage/cnc/JT-SHOP/mesact/buildbot_errorlist.png
09:49 PM seb_kuzminsky: you shouldn't need email set up for the www interface to work
09:49 PM seb_kuzminsky: oh i see, in your git log
09:49 PM seb_kuzminsky: yes, that looks like it
09:50 PM Tom_dev: :)
09:50 PM seb_kuzminsky: your buildbot is trying to `git commit`, but it doesn't have a .gitconfig with its identity in it
09:50 PM seb_kuzminsky: it's so easy when you can see the logs :-)
09:50 PM Tom_dev: ok
09:50 PM Tom_dev: i saw that but forgot what file those are in
09:50 PM Tom_dev: is that part of the worker or master?
09:52 PM Tom_dev: found it i think
09:52 PM linuxcnc-build: build #2327 of 4041.deb-buster-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4041.deb-buster-rtpreempt-amd64/builds/2327 blamelist: adamlouis <adamlouis@users.noreply.github.com>, Phillip Carter <phillcarter54@gmail.com>
09:53 PM seb_kuzminsky: the web interface is part of the master
09:53 PM seb_kuzminsky: c['www']
09:53 PM Tom_dev: the email goes in the master.cfg file?
09:54 PM seb_kuzminsky: the email for the git identity? no, i'd expect that to go in the normal git place, ~/.gitconfig for whatever user is running git
09:54 PM Tom_dev: ok, well at least i have a direction now
09:54 PM Tom_dev: thanks
09:58 PM seb_kuzminsky: ah, or you can pass it in via the GitCommit `env` argument, as GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_COMMITTER_NAME, and GIT_COMMITTER_EMAIL (see the git-commit-tree manpage)
09:58 PM seb_kuzminsky: that might be easier than trying to mess with stuff in the buildbot's homedir, plus you get to revision-track it with the rest of the master.cfg
10:03 PM Tom_dev: thanks
10:12 PM Tom_L: i don't see mention of those in the 3.6 docs but i'll try them
10:35 PM linuxcnc-build: build #2221 of 4042.deb-buster-rtpreempt-rpi4 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4042.deb-buster-rtpreempt-rpi4/builds/2221 blamelist: adamlouis <adamlouis@users.noreply.github.com>, CMorley <chrisinnanaimo@hotmail.com>, Phillip Carter <phillcarter54@gmail.com>, andypugh
10:35 PM linuxcnc-build: <andy@bodgesoc.org>
10:44 PM seb_kuzminsky: Tom_L: GitCommit is here: https://docs.buildbot.net/3.6.0/manual/configuration/steps/gitcommit.html
10:44 PM seb_kuzminsky: including the `env` argument
10:44 PM seb_kuzminsky: that's a dict that you fill with the environment variables you want to have when running the command
10:44 PM seb_kuzminsky: the env vars are in the git-commit-tree manpage
10:46 PM Tom_L: yeah i've been looking at that
10:48 PM Tom_L: not finding that manpage..
10:52 PM seb_kuzminsky: https://www.man7.org/linux/man-pages/man1/git-commit-tree.1.html
10:52 PM Tom_L: thanks
10:52 PM seb_kuzminsky: hmm, but that version doesn't mention the env vars
10:53 PM Tom_L: nope
10:53 PM seb_kuzminsky: ah, it moved to the git-commit manpage sometime between 2.30 (what i have on bullseye) and 2.33 (what's on man7)
10:53 PM seb_kuzminsky: https://www.man7.org/linux/man-pages/man1/git-commit.1.html
10:55 PM Tom_L: --author?
10:56 PM seb_kuzminsky: set the environment variables described here: https://www.man7.org/linux/man-pages/man1/git-commit.1.html#COMMIT_INFORMATION
10:56 PM seb_kuzminsky: make them into a dict and pass them as the `env` argument to buildbot's GitCommit
10:57 PM Tom_L: i get errors when trying that
10:58 PM Tom_dev: SyntaxError: invalid syntax. Maybe you meant '==' or ':=' instead of '='?
10:58 PM Tom_dev: env=[GIT_AUTHOR_NAME='tlight9']
10:59 PM seb_kuzminsky: env = { 'GIT_AUTHOR_NAME': 'tlight9' }
10:59 PM seb_kuzminsky: it's a dict, not a list
10:59 PM Tom_L: new to python too :/
11:00 PM seb_kuzminsky: it's a good language to learn :-)
11:00 PM Tom_L: i'm an ole dos phart
11:00 PM seb_kuzminsky: dos makes me all nostalgic :-)
11:00 PM seb_kuzminsky: aah, simpler days
11:00 PM Tom_L: heh
11:01 PM Tom_L: none of this oops stuff
11:01 PM Tom_L: or objects containers.....
11:02 PM Tom_L: comma separated inside the {}?
11:02 PM seb_kuzminsky: yep
11:02 PM seb_kuzminsky: {'a': 1, 'b': 2}
11:03 PM Tom_L: checkconfig says 'ok'
11:03 PM seb_kuzminsky: yay!
11:03 PM Tom_L: just name and email are the required ones ?
11:04 PM seb_kuzminsky: i think so, but i think you have to set both GIT_COMMITTER_* and GIT_AUTHOR_*
11:04 PM Tom_L: ok
11:07 PM linuxcnc-build: build #2328 of 4041.deb-buster-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4041.deb-buster-rtpreempt-amd64/builds/2328 blamelist: adamlouis <adamlouis@users.noreply.github.com>, CMorley <chrisinnanaimo@hotmail.com>, Phillip Carter <phillcarter54@gmail.com>, andypugh
11:07 PM linuxcnc-build: <andy@bodgesoc.org>
11:12 PM linuxcnc-build: build #6286 of 4007.deb-precise-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4007.deb-precise-i386/builds/6286
11:13 PM linuxcnc-build: build #6286 of 4008.deb-precise-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4008.deb-precise-amd64/builds/6286
11:22 PM linuxcnc-build: build #5118 of 4009.deb-precise-rtai-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4009.deb-precise-rtai-i386/builds/5118
11:23 PM linuxcnc-build: build #4149 of 4015.deb-wheezy-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4015.deb-wheezy-rtpreempt-amd64/builds/4149
11:24 PM linuxcnc-build: build #4124 of 4014.deb-wheezy-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4014.deb-wheezy-rtpreempt-i386/builds/4124
11:24 PM linuxcnc-build: build #4855 of 4016.deb-wheezy-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4016.deb-wheezy-i386/builds/4855
11:25 PM linuxcnc-build: build #4858 of 4017.deb-wheezy-amd64 is complete: Failure [4failed shell_2] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4017.deb-wheezy-amd64/builds/4858
11:25 PM Tom_dev: fatal: could not read Username for 'https://github.com': No such device or address
11:26 PM Tom_dev: that's on the GitPush commmand using the same env= string
11:28 PM linuxcnc-build: build #4545 of 4018.deb-wheezy-rtai-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4018.deb-wheezy-rtai-i386/builds/4545
11:30 PM seb_kuzminsky: the push doesn't need those two, but it will need some way to authenticate your push to github
11:31 PM Tom_L: yeah, i'm not sure where to add that. i put the user etc in the www section
11:31 PM Tom_L: digging some more...
11:32 PM Tom_L: the commit works now !
11:33 PM Tom_L: sshHostKey maybe?
11:33 PM seb_kuzminsky: do you normally authenticate to github using ssh, with a key?
11:33 PM Tom_L: i set a key up for it yes
11:33 PM seb_kuzminsky: does your key have a passphrase?
11:34 PM Tom_L: also new to that... i'm not sure but i think so
11:35 PM seb_kuzminsky: it'll probably be awkward to use an ssh key with a passphrase for automated pushing from buildbot
11:36 PM seb_kuzminsky: because you need to type in the passphrase to use the key, but i dont think GitPush has a convenient way to do that
11:36 PM Tom_L: ok
11:36 PM seb_kuzminsky: there may be a way and i just don't know about it
11:37 PM Tom_L: np, you've already spent enough time helping...
11:37 PM Tom_L: at least i have a direction to go
11:37 PM linuxcnc-build: build #3397 of 4020.deb-jessie-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4020.deb-jessie-rtpreempt-amd64/builds/3397
11:38 PM linuxcnc-build: build #3398 of 4019.deb-jessie-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4019.deb-jessie-rtpreempt-i386/builds/3398
11:39 PM linuxcnc-build: build #2295 of 4030.deb-stretch-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4030.deb-stretch-rtpreempt-i386/builds/2295
11:40 PM linuxcnc-build: build #2294 of 4031.deb-stretch-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4031.deb-stretch-rtpreempt-amd64/builds/2294
11:41 PM linuxcnc-build: build #3511 of 4021.deb-jessie-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4021.deb-jessie-i386/builds/3511
11:41 PM seb_kuzminsky: what a mess
11:41 PM linuxcnc-build: build #3507 of 4022.deb-jessie-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4022.deb-jessie-amd64/builds/3507
11:42 PM seb_kuzminsky: Tom_L: the "tried and true" way to do automatic git push is to make an ssh key without a passphrase, and let your buildbot use that
11:42 PM Tom_L: i may have done that, i just don't know enough about it.
11:42 PM seb_kuzminsky: this would be a new, single-purpose ssh key that you'd use only for git push to this github repo
11:42 PM Tom_L: i _can_ use git gui without a login
11:43 PM Tom_L: and push changes with it
11:43 PM seb_kuzminsky: git gui is local, doesn't talk to github
11:43 PM linuxcnc-build: build #2222 of 4042.deb-buster-rtpreempt-rpi4 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4042.deb-buster-rtpreempt-rpi4/builds/2222
11:43 PM seb_kuzminsky: oh you can push! that's promising
11:43 PM Tom_L: i push changes with it to my repo
11:43 PM Tom_L: so i know i have a key of some sort
11:43 PM seb_kuzminsky: does your ssh key show up if you run `ssh-add -l`
11:43 PM seb_kuzminsky: ?
11:44 PM Tom_L: yes
11:44 PM Tom_L: SHA256 xxxx
11:44 PM seb_kuzminsky: ok, that means you have loaded the key into your ssh agent
11:44 PM seb_kuzminsky: try this:
11:46 PM seb_kuzminsky: well first, where's your key stored? usually it's ~/.ssh/id_rsa
11:46 PM Tom_dev: i was about to ask you that
11:46 PM Tom_dev: yes
11:46 PM Tom_dev: it's there
11:47 PM seb_kuzminsky: ok, run `ssh-add -d ~/.ssh/id_rsa` to remove the key from your ssh-agent (it will still be in that file in .ssh/, but it won't be "ready to use" until you add it back)
11:48 PM Tom_dev: http://tom-itx.no-ip.biz:81/~webpage/cnc/JT-SHOP/mesact/ssh_id.png
11:48 PM seb_kuzminsky: ah ok, it's called id_ed25519, that's fine
11:49 PM seb_kuzminsky: so `ssh-add -d ~/.ssh/id_ed25519`, then `ssh-add -l` to verify that it got removed
11:50 PM seb_kuzminsky: linuxcnc-build: force build --branch=2.8 0000.checkin
11:50 PM Tom_dev: ould not remove identity "/home/tom/.ssh/id_ed25519": agent refused operation
11:50 PM linuxcnc-build: The build has been queued, I'll give a shout when it starts
11:51 PM seb_kuzminsky: Tom_dev: odd
11:52 PM seb_kuzminsky: well you could just try to use it
11:52 PM Tom_dev: with sshPrivateKey?
11:53 PM seb_kuzminsky: yeah
11:53 PM Tom_dev: point to the file ?
11:53 PM seb_kuzminsky: right, sshPrivateKey points to your id_ed25519 file
11:53 PM Tom_dev: ok
11:54 PM seb_kuzminsky: and the `repourl` has to be a git+ssh url, something like `git@github.com:tom/repo.git`
11:54 PM Tom_dev: ok
11:54 PM seb_kuzminsky: you can find the ssh url for your repo on the github repo page
11:54 PM Tom_dev: instead of the https one
11:54 PM Tom_dev: i've had to use it before...
11:54 PM Tom_dev: setting up git gui i think
11:55 PM seb_kuzminsky: http://highlab.com/~seb/linuxcnc/Screenshot%20from%202022-11-23%2022-53-12.png
11:58 PM Tom_dev: still get the username error
11:58 PM Tom_dev: fatal: could not read Username for 'https://github.com': No such device or address
11:58 PM Tom_dev: woops forgot to edit the https..