#linuxcnc-devel Logs

Jul 27 2017

07:48 AM jepler: Tom_L: in this case there will probably be an iso
07:49 AM jepler: Tom_L: but I do NOT plan to update the iso every time there's a new linuxcnc release in general
07:49 AM jepler: .. in general, we expect users to install LinuxCNC to their hard drive and then use the usual Debian way of updating packages after that.
07:51 AM Tom_L: right
09:49 AM seb_kuzminsky: what a great reply from nicokid :-)
03:05 PM andypugh: I can’t push to githib.
03:05 PM andypugh: Permission denied (publickey).
03:09 PM jepler: andypugh: you can add your specific machine's key via github's web ui https://github.com/settings/keys
03:10 PM andypugh: Yes, thanks, I have been looking at their docs for that
03:10 PM jepler: OK
03:10 PM jepler: if you haven't specifically set up that machine to push to github before, it is no surprise that you got that error
03:11 PM jepler: as linuxcnc project administrators, we can only add your github user as someone who is permitted to push. but we can't add the key(s) you had on git.linuxcnc.org, you have to add the keys.
03:11 PM andypugh: Indeed. I guess that Github hasn’t inherited the keys from glo
03:11 PM jepler: exactly, and it is perhaps my fault for not mentioning that fact
03:12 PM jepler: I didn't even think about it to be honest, because I have my github ssh keys set up to push to all sorts of projects on github already
03:21 PM jepler: andypugh: welcome to github
03:21 PM andypugh: Do you need to type the passphrase every commit? That’s new to me.
03:21 PM Tom_L: just curious why the move?
03:22 PM jepler: this is the mailing list post where I originally made the case for the move: (In reply to comment #5)
03:22 PM jepler: however, the neutral_srfc flag is not available in new_polygon, so we can't test it :-/
03:22 PM jepler: errr
03:22 PM jepler: https://sourceforge.net/p/emc/mailman/message/35845586/
03:23 PM Tom_L: thanks
03:23 PM jepler: andypugh: did you configure a passphrase on your ssh key before now, or did you do it at the suggestion of github instructions?
03:23 PM andypugh: I can’t remember, it was years ago.
03:24 PM jepler: I wouldn't expect it to change just because you were connecting to github
03:24 PM andypugh: I just added my existing .ssh key to github
03:24 PM andypugh: It’s not a big deal, luckily I remembered it
03:37 PM seb_kuzminsky: i use ssh-agent, so i unlock and add my keys once at the start of a session and then never type any passwords after that
05:15 PM linuxcnc-build: build #5055 of 1202.rip-lucid-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1202.rip-lucid-amd64/builds/5055 blamelist: andypugh <andy@bodgesoc.org>
05:15 PM andypugh: Oh
05:15 PM andypugh: :-(
05:16 PM seb_kuzminsky: not your fault
05:16 PM seb_kuzminsky: task: main loop took 5.516587 seconds
05:16 PM andypugh: Good :-)
05:16 PM seb_kuzminsky: timeout waiting for joint 0 to stop at -1.000 (pos=0.000, vel=0.000)
05:16 PM seb_kuzminsky: it's the flaky buildbot causing trouble again
05:17 PM seb_kuzminsky: linuxcnc-build: force build --branch=2.7 0000.checkin
05:17 PM linuxcnc-build: The build has been queued, I'll give a shout when it starts
05:17 PM seb_kuzminsky: i'm not sure how to fix that problem. sometimes the hypervisor just doesn't run the VMs for a while
05:18 PM seb_kuzminsky: i could try blindly upgrading my hypervisor, since the problem seems to only happen on the older hypervisor machine
05:19 PM andypugh: It’s not likely to make it worse, I guess.
05:20 PM seb_kuzminsky: probably not
05:38 PM jepler: ooh look at n. k. snark at someone who doesn't give a good enough explanation of whatever problem they're encountering
05:43 PM andypugh: I think there was a single-chracter answer to his problem - $
06:59 PM linuxcnc-build: build #5075 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/5075 blamelist: andypugh <andy@bodgesoc.org>
06:59 PM linuxcnc-build: build forced [ETA 2h02m34s]
06:59 PM linuxcnc-build: I'll give a shout when the build finishes
08:37 PM linuxcnc-build: Hey! build 0000.checkin #5076 is complete: Success [3build successful]
08:37 PM linuxcnc-build: Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/5076