Back
[06:57:15] <jthornton> is there a 2.7 deb on buildbot? I don't see it on the list at buildbot.linuxcnc.org
[07:21:28] <Tom_itx> jthornton, you can check it out from master
[07:22:21] <jthornton> yea, I know you can get a checkout, I was wondering about a deb
[07:22:41] <Tom_itx> i don't think there is one yet
[07:23:08] <jthornton> I see 2.7 docs
[07:23:48] <jthornton> I'm just wondering if the buildbot page is not updated yet?
[07:25:02] <Tom_itx> couldn't say
[07:27:27] <jthornton> seb_kuzm1nsky, I just got some info from dgarr on moveoff and I'm thinking a new subdirectory off of docs/src. What's your thoughts on this?
[07:31:02] <Tom_itx> if anybody keeps track of it here, i added my mesa bitfile build instructions to the wiki the other day
[07:44:08] <jthornton> seb_kuzm1nsky, after some study I think it goes in config
[08:53:05] <seb_kuzm1nsky> jthornton: the buildbot does make 2.7 debs, but i've not added the info to the front page yet
[08:53:09] <seb_kuzm1nsky> hold on, i'll do it now
[09:00:50] <seb_kuzm1nsky> errrr, no i wont
[09:02:16] <seb_kuzminsky> the buildbot currently makes debs with the old names
[09:02:42] <seb_kuzminsky> 2.6 (and older) make "2.6-rt" for rtai and "2.6-sim" for sim
[09:02:58] <seb_kuzminsky> but 2.7 and newer need to make "2.7-rtai" for rtai and "2.7-uspace" for sim/rt-preempt
[09:03:16] <seb_kuzminsky> i've been meaning to teach the buildbot to do this new thing, but i haven't gotten to it yet
[09:03:47] <seb_kuzminsky> you can access the 2.7 debs via the old names, but i dont want to publicize that...
[09:04:05] <seb_kuzminsky> so 2.7-rt for rtai and 2.7-sim for uspace
[09:05:32] <seb_kuzminsky> the rename is a little tricky, since we want to "build rip and runtests" on three kernels (rtai, rt-preempt, and vanilla), but we only want to build debs on two (rtai and *either* rt-preempt or vanilla)
[09:06:00] <seb_kuzminsky> and the buildbot needs to support pre-2.7 branches as well as 2.7-and-later
[09:07:45] <seb_kuzminsky> jthornton: uhm, about the docs
[09:08:58] <seb_kuzminsky> i'd like to move towards a directory structure under docs/src that matches the "presentation layout" of our docs
[09:09:18] <seb_kuzminsky> so docs/src/getting-started, docs/src/user-manual, docs/src/integrator-manual, etc
[09:09:52] <JT-Shop> yea that makes sense
[09:10:03] <seb_kuzminsky> so far i've (nearly) done that reorg to the getting-started manual, but i've not finished it & pushed it to 2.7 yet
[09:11:11] <seb_kuzminsky> if you're adding moveoff docs (thanks!), that should probably go in docs/src/config for now, and if/when we reorganize the integrator manual we'll move it to the right place then (along with all the other documents that belong)
[09:11:36] <seb_kuzminsky> i should hurry up and push the getting-started docs reorg...
[09:12:00] <JT-Shop> ok, that is what I did this morning... I'm still checking the addition so I havn't pushed it yet
[09:16:08] <seb_kuzminsky> perfect
[09:16:29] <seb_kuzminsky> i'll wait for you to push your changes to 2.7, then i'll push my reorg changes to 2.7
[09:18:13] <JT-Shop> ok
[09:21:37] <KGB-linuxcnc> 03John Thornton 052.7 d734e64 06linuxcnc 10docs/src/Master_Integrator.txt 10docs/src/Submakefile 03docs/src/config/moveoff.txt 10docs/src/index.tmpl Docs: add moveoff * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=d734e64
[09:32:40] <seb_kuzminsky> wow, that was fast!
[09:38:50] <JT-Shop> if I could only get my work done that fast...
[09:44:10] <seb_kuzminsky> JT-Shop: i like that you (or dgarr?) called it "move while paused", to draw attention to the fact that it's not exactly jogging
[09:44:24] <seb_kuzminsky> (as opposed to calling it jog-while-paused)
[09:46:20] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.7 7bf57fe 06linuxcnc 10docs/src/index_es.tmpl docs: minor reorg in the Spanish html index * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7bf57fe
[09:46:27] <seb_kuzminsky> the translation mess in our docs is depressing
[09:47:34] <JT-Shop> yes it is
[09:48:13] <JT-Shop> that was dgarr words... I still need to format it a bit
[09:48:19] <seb_kuzminsky> ok
[09:48:34] <JT-Shop> I'm off to work now
[09:48:38] <seb_kuzminsky> i should be too
[09:51:37] <KGB-linuxcnc> 03Sebastian Kuzminsky 05seb/2.7/docs-reorg 81d3f82 06linuxcnc 10(81 files in 9 dirs) docs: reorg Getting Started (English) * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=81d3f82
[09:51:37] <KGB-linuxcnc> 03Sebastian Kuzminsky 05seb/2.7/docs-reorg 0df3342 06linuxcnc 10(76 files in 8 dirs) docs: reorg Getting Started (French) * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=0df3342
[09:51:37] <KGB-linuxcnc> 03Sebastian Kuzminsky 05seb/2.7/docs-reorg df737e8 06linuxcnc 10(21 files in 5 dirs) docs: reorg Getting Started (Spanish) * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=df737e8
[09:51:39] <KGB-linuxcnc> 03Sebastian Kuzminsky 05seb/2.7/docs-reorg 7583d89 06linuxcnc 10docs/src/getting-started/Getting-Started-with-LinuxCNC.contents-es.txt add FAQ to spanish * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7583d89
[09:52:55] <seb_kuzminsky> cradek: i just got this error while pushing the docs-reorg branch:
http://pastie.org/9774329
[09:53:45] <seb_kuzminsky> the buildbot did *not* get notified of the push, but the commits showed up in the git repo:
http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=shortlog;h=refs/heads/seb/2.7/docs-reorg
[09:53:58] <seb_kuzminsky> linuxcnc-build: force build --branch=seb/2.7/docs-reorg 0000.checkin
[09:54:04] <linuxcnc-build> The build has been queued, I'll give a shout when it starts
[09:54:08] <seb_kuzminsky> bbl
[09:55:02] <cradek> ok everyone hold still
[10:05:54] <cradek> :120000 100644 9b02a37... c7509ae... T docs/src/common/images/axis_25_fr.png
[10:06:08] <cradek> this is the line it's failing on - I think it expects the T to be one of M,A,D
[10:07:51] <cradek> T = "change in the type of the file"
[10:14:15] <cradek> I don't know what that means
[10:18:35] <jepler> I think it changed from a symlink to a file
[10:22:20] <jepler> this new sbc from hardkernel.com looks interesting. quad core 1.5GHz, 1GB RAM, gigabit ethernet, $35 (if shipped from s. korea; $37 at the US reseller). though by the time you finish adding accessories like a comfortably large eMMC module, you'll still hit $100 for the whole system.
[10:22:51] <jepler> .. there's a gigabit ethernet MAC in the SoC, so it might work with hm2-eth
[10:24:04] <cradek> well I added T to the regexp and now it's running ... and running ...
[10:24:08] <cradek> yeah it ran
[10:24:16] <cradek> I have no idea whether that's a right fix
[10:24:25] <cradek> this is code that is special to push -f
[10:24:28] <jepler> Amlogic S805 (Cortex-A5, Mali-450). perhaps CaptHindsight has an opinon about this SoC, he knows about so many of them
[10:24:51] <jepler> http://www.hardkernel.com/main/products/prdt_info.php?g_code=G141578608433&tab_idx=2
[10:24:55] <cradek> seems like push -f a "type" change was broken
[10:25:13] <CaptHindsight> jepler: spotted that a few days ago, looks good
[10:26:37] <CaptHindsight> also working on this
http://openlunchbox.com/ now that we found the source for the good keyboards we can make the whole laptop without much pain
[10:28:51] <seb_kuzminsky> cradek: thanks!
[10:29:21] <CaptHindsight> http://www.amlogic.com/product02.htm for more info on the S805 you have to contact U.S 2518 Mission College Blvd, Suite 120 Santa Clara, CA 95054, USA Tel: +1 408-850-9688
[10:31:04] <CaptHindsight> schematics and pinout
http://www.hardkernel.com/main/products/prdt_info.php?g_code=G141578608433&tab_idx=2
[10:32:16] <CaptHindsight> http://odroid.com/dokuwiki/doku.php?id=en:odroid-c1 no source trees yet for u-boot or kernels yet :(
[10:33:59] <CaptHindsight> http://www.cnx-software.com/2014/03/10/amlogic-gpl-source-code-release-kernel-3-10-u-boot-and-drivers-wi-fi-nand-tvin-mali-gpu/
[10:34:29] <CaptHindsight> http://openlinux.amlogic.com:8000/download/ARM/
[10:35:16] <CaptHindsight> http://www.cnx-software.com/2014/02/19/amlogic-s802-m802-android-4-4-sdk-documentation-and-reference-schematics-are-almost-available
[10:35:18] <KGB-linuxcnc> 03Dewey Garrett 052.7 3ff86cd 06linuxcnc 10configs/sim/touchy/ngcgui/pyngcgui_touchy_moveoff.ini 10scripts/moveoff_gui 10src/hal/components/moveoff.comp moveoff: update for manpage and touchscreen use * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3ff86cd
[10:35:19] <KGB-linuxcnc> 03Dewey Garrett 052.7 f05e53e 06linuxcnc 10scripts/moveoff_gui moveoff_gui: --help: show opts defaults better * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=f05e53e
[10:46:11] <KGB-linuxcnc> 03John Thornton 052.7 262b8af 06linuxcnc 10docs/src/config/moveoff.txt Docs: update moveoff to match man page * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=262b8af
[11:08:23] <Connor> seb_kuzminsky: What's in 2.8 vs 2.7 at this point ?
[11:14:38] <seb_kuzminsky> Connor: there's not much new in 2.8 (aka master) yet
[11:14:57] <Connor> but, is stuff from 2.7 going into it also?
[11:15:47] <seb_kuzminsky> yeah, hardly anything new in master
[11:15:48] <Connor> Now that we have 3 branches.. I'm finding it hard to know which one to use..
[11:16:10] <seb_kuzminsky> yes, everything that goes into any of the stable branches (2.5, 2.6, 2.7) gets merged into master
[11:16:44] <seb_kuzminsky> if you care mostly about stability and productivity, use the stable branch, 2.6
[11:17:00] <Connor> So why do we have a 2.8 while we have a 2.7 too ?
[11:17:21] <seb_kuzminsky> if you care about new features and want to help stabilize the *next* stable branch, use 2.7
[11:17:34] <seb_kuzminsky> if you want to develop new features, use master (aka 2.8)
[11:17:52] <Connor> I'm be using gmoccapy and looks like lots of fixes going on for it.
[11:19:12] <seb_kuzminsky> we have master (aka 2.8) and 2.7 because they are for different things
[11:19:48] <seb_kuzminsky> 2.7 is "frozen", meaning it's only getting bugfixes, no new features, so that it can become more stable in preparation for releasing 2.7.0
[11:20:18] <seb_kuzminsky> master (aka 2.8) is the new-development branch, where any new, potentially destabilizing features will be developed
[11:20:45] <Connor> ok. and 2.6 is most stable and your backporting fixed from 2.7 into it ?
[11:20:46] <Connor> or not ?
[11:21:32] <seb_kuzminsky> 2.6 is the current stable branch, but the normal workflow does not involve backporting things to it
[11:22:02] <seb_kuzminsky> Connor:
http://linuxcnc.org/docs/2.6/html/code/Contributing-to-LinuxCNC.html#_use_of_git_in_the_linuxcnc_project
[11:23:45] <Connor> Unless something major pops up and you need to push it down to 2.6 I guess..
[11:24:27] <cradek> oh hey the docs say just what I was going to say
[11:24:38] <Connor> So, where is the work going on for Jog while paused, or what ever we're calling it.
[11:25:07] <Connor> that in 2.8 I guess..
[11:25:15] <cradek> moveoff is going to be in 2.7
[11:25:27] <seb_kuzminsky> Connor: if there's a bug, the proper thing to do (as that document says) is to fix it in the oldest applicable branch, probably 2.6 at the moment
[11:25:43] <seb_kuzminsky> if someone accidentally puts the bugfix in a later branch, then yes i would backport it to 2.6
[11:25:56] <Connor> Okay...
[11:26:07] <Connor> I guess moveoff got in before the feature freeze..
[11:26:18] <cradek> these things really are answered in those first couple sentences at that docs url
[11:26:27] <seb_kuzminsky> moveoff (the interim jog-while-paused solution) was developed (by dgarr) in a feature branch, then cleaned up and merged into 2.7
[11:26:44] <seb_kuzminsky> i accepted it into 2.7 because it's a very isolated, low-risk change
[11:26:57] <seb_kuzminsky> again, as described in the doc i linked you
[11:27:33] <Connor> I'm looking it over. I use SVN.. closed source project.. not done a huge amount with GIT.
[11:27:34] <seb_kuzminsky> dgarr just merged moveoff into 2.7, it'll be in the next pre-release :-)
[11:27:43] <cradek> yay
[11:27:48] <seb_kuzminsky> yay :-)
[11:28:08] <seb_kuzminsky> yeah, the way branches and merges are supported is a big difference between svn and git
[11:28:10] <Connor> Somehow I ended up with 2.8 on my sim machine..
[11:28:30] <seb_kuzminsky> did you build from source or install debs from the buildbot?
[11:29:14] <seb_kuzminsky> Connor: it'd probably be worth your while to at least skim the git documentation linked here:
http://linuxcnc.org/docs/2.6/html/code/Contributing-to-LinuxCNC.html#_git_tutorials
[11:29:51] <Connor> In my application, I have a trunk and dev branch. I use a working copy as a beta for bug fixes and short term stuff, long term and other developers work in the dev branch..
[11:30:04] <Connor> having to merge down from trunk to dev sucks.
[11:30:31] <seb_kuzminsky> i also used to hate branches and merges
[11:30:36] <seb_kuzminsky> ... before i switched from svn to git ;-)
[11:31:02] <seb_kuzminsky> cradek: speaking of merges, i've been using git-imerge lately and it's awesome
[11:31:31] <Connor> how often do you have to go in and deal with conflicts ?
[11:31:36] <cradek> I see you keep saying that, but I haven't even googled it to see what it is
[11:31:53] <seb_kuzminsky> cradek:
https://www.youtube.com/watch?v=FMZ2_-Ny_zc
[11:32:03] <seb_kuzminsky> Connor: all the time, but git makes it easy
[11:33:06] <seb_kuzminsky> cradek: the elevator pitch is: it's just like git-merge and/or git-rebase, except you get smaller easier conflicts and you can checkpoint (and push!) the in-progress merge/rebase
[11:33:49] <cradek> that sounds nice
[11:33:52] <seb_kuzminsky> git-merge gives you a conflict between the two branch heads, git-rebase gives you conflicts between each commit on one branch and the head on the other branch
[11:34:18] <seb_kuzminsky> git-imerge gives you conflicts between commits on one branch and commits on the other branch, which sounds awful but turns out to be awesome
[11:57:17] <linuxcnc-build> build forced [ETA 1h19m54s]
[11:57:17] <linuxcnc-build> I'll give a shout when the build finishes
[12:11:30] <cradek> seb_kuzminsky: it looks like a great idea, although I couldn't make it through the video
[12:11:47] <cradek> I assume at the end it collapses all those little merges and looks like a normal merge?
[12:11:59] <linuxcnc-build> build #939 of 1405.rip-wheezy-armhf is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1405.rip-wheezy-armhf/builds/939
[12:31:28] <KGB-linuxcnc> 03Dewey Garrett 052.7 6d55eab 06linuxcnc 10configs/sim/hookup_moveoff.tcl 10docs/src/config/moveoff.txt 10scripts/moveoff_gui 10src/hal/components/moveoff.comp moveoff_gui: correct text errors for is connected * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=6d55eab
[12:32:30] <linuxcnc-build> build #2752 of 1200.rip-lucid-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1200.rip-lucid-i386/builds/2752
[12:39:02] <linuxcnc-build> build #2751 of 1300.rip-precise-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1300.rip-precise-i386/builds/2751
[12:39:48] <linuxcnc-build> build #2753 of 1306.rip-precise-amd64 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/2753
[12:42:37] <linuxcnc-build> build #1953 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/1953
[12:45:33] <seb_kuzminsky> cradek: at the end you can make it look like a merge or a rebase or a couple of other things that i dont care that much about
[12:48:53] <linuxcnc-build> build #909 of 1403.rip-wheezy-amd64 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1403.rip-wheezy-amd64/builds/909
[12:49:52] <seb_kuzminsky> those failures are a bug in the docs-reorg branch, i didn't move the Linux_FAQ*.txt files to getting-started/ correctly
[12:49:57] <seb_kuzminsky> i'll fix it tonight
[12:51:05] <linuxcnc-build> build #2752 of 1201.rip-lucid-rtai-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1201.rip-lucid-rtai-i386/builds/2752
[12:51:11] <linuxcnc-build> build #1100 of 1404.rip-wheezy-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1404.rip-wheezy-rtpreempt-amd64/builds/1100
[12:53:30] <linuxcnc-build> build #909 of 1400.rip-wheezy-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/909
[12:54:09] <linuxcnc-build> build #420 of 1402.rip-wheezy-rtpreempt-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1402.rip-wheezy-rtpreempt-i386/builds/420
[12:56:17] <linuxcnc-build> build #2752 of 1202.rip-lucid-amd64 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1202.rip-lucid-amd64/builds/2752
[12:57:31] <linuxcnc-build> build #567 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/567
[12:57:32] <linuxcnc-build> build #2763 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/2763
[13:02:25] <linuxcnc-build> build #2752 of 1300.rip-precise-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1300.rip-precise-i386/builds/2752 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz <micges@wp.pl>
[13:03:12] <linuxcnc-build> build #2754 of 1306.rip-precise-amd64 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/2754 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz <micges@wp.pl>
[13:03:13] <linuxcnc-build> build #1954 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/1954 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz
[13:03:13] <linuxcnc-build> <micges@wp.pl>
[13:03:34] <linuxcnc-build> build #2753 of 1200.rip-lucid-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1200.rip-lucid-i386/builds/2753 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz <micges@wp.pl>
[13:04:05] <linuxcnc-build> build #2753 of 1201.rip-lucid-rtai-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1201.rip-lucid-rtai-i386/builds/2753 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz <micges@wp.pl>
[13:05:05] <linuxcnc-build> build #2753 of 1202.rip-lucid-amd64 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1202.rip-lucid-amd64/builds/2753 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz <micges@wp.pl>
[13:05:49] <linuxcnc-build> build #910 of 1403.rip-wheezy-amd64 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1403.rip-wheezy-amd64/builds/910 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz <micges@wp.pl>
[13:06:04] <linuxcnc-build> build #1101 of 1404.rip-wheezy-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1404.rip-wheezy-rtpreempt-amd64/builds/1101 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz
[13:06:05] <linuxcnc-build> <micges@wp.pl>
[13:06:11] <linuxcnc-build> build #910 of 1400.rip-wheezy-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/910 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz <micges@wp.pl>
[13:06:30] <Connor> wow build bot.. way to spit out stuff.
[13:07:13] <linuxcnc-build> build #421 of 1402.rip-wheezy-rtpreempt-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1402.rip-wheezy-rtpreempt-i386/builds/421 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz
[13:07:13] <linuxcnc-build> <micges@wp.pl>
[13:07:22] <linuxcnc-build> build #568 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/568 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz <micges@wp.pl>
[13:11:47] <linuxcnc-build> build #940 of 1405.rip-wheezy-armhf is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1405.rip-wheezy-armhf/builds/940 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz <micges@wp.pl>
[13:20:04] <linuxcnc-build> build #2764 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/2764 blamelist: Dewey Garrett <dgarrett@panix.com>, dummy, Sebastian Kuzminsky <seb@highlab.com>, John Thornton <jthornton@gnipsel.com>, Michael Geszkiewicz <micges@wp.pl>
[14:02:04] <KGB-linuxcnc> 03John Thornton 052.7 c81f3db 06linuxcnc 10docs/src/config/moveoff.txt 10docs/src/index.tmpl Docs: formatting and other corrections * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c81f3db
[14:57:57] <seb_kuzminsky> bwaahaha
[14:58:33] <seb_kuzminsky> i'm looking at po4a (gettext for documentation), and i came across a package called 'gettext-lint', and i tried to run one of its checkers, and i got this error:
[14:58:36] <seb_kuzminsky> bash: /usr/bin/POFileClean: /usr/bin/python^M: bad interpreter: No such file or directory
[14:59:28] <seb_kuzminsky> po4a looks really promising, btw
[15:00:00] <seb_kuzminsky> you can feed it a master document and a localized document, and it'll spit out a .po file for the localization
[15:00:16] <seb_kuzminsky> then you can feed it the master document and the .po file, and it'll spit out a localized document
[15:00:33] <seb_kuzminsky> each paragraph in the asciidoc .txt files becomes one translatable string
[15:01:01] <seb_kuzminsky> the new version of po4a in jessie understands (supposedly) asciidoc markup so things like lists and tables should work right, but i haven't verified that yet
[15:01:26] <seb_kuzminsky> i'll push a branch tonight that shows how it works
[15:03:13] <seb_kuzminsky> there are gettext translators' tools in both gnome (gtranslate) and kde, and there's gettext modes for vim and emacs but i haven't played with them yet
[15:03:30] <seb_kuzminsky> and of course .po files are just flat text files that can be edited "by hand"
[16:36:37] <seb_kuzminsky> sigh, that POFileClean bug is known by debian.org, it was opened in 2011 and hasn't been fixed :-/
[16:36:40] <seb_kuzminsky> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627762
[18:30:42] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.7 34314f5 06linuxcnc 10docs/src/Master_Integrator.txt 10docs/src/Master_Integrator_es.txt 10docs/src/Master_Integrator_fr.txt docs: put the Linux FAQ in Getting Started only * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=34314f5
[20:17:30] <KGB-linuxcnc> 03Dewey Garrett 052.7 7b0a568 06linuxcnc 10configs/sim/hookup_moveoff.tcl hookup_moveoff.tcl: support twopass processing * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7b0a568
[22:51:01] <seb_kuzminsky> buildmaster's out of disk space again
[22:56:08] <KimK> Such a hard-working buildbot
[22:56:25] <skunkworks> what is the hardware?
[22:59:06] <KimK> Hi Sam. Speaking of hardware, do you have any suggestions for motherboards lately? I've heard Peter talk about his good results lately, I'll check with him too.
[23:02:37] <seb_kuzminsky> skunkworks: it's a kvm virtual machine on an old lucid server
[23:07:16] <seb_kuzminsky> plenty of room on the hypervisor host since i rm'd the xenomai buildslave images
[23:08:28] <skunkworks> KimK: what are you going to run with it? I have had good luck recently with gigabyte j1800, j1900 mother boards.
[23:09:04] <skunkworks> there was a xenomai build slave at some point?
[23:10:43] <skunkworks> the J1900 is a quad core celeron
[23:11:11] <skunkworks> The J1900 also has 1 pci slot
[23:11:42] <skunkworks> (I had it running a 5i25 + 7i80 (ethernet) at the same time.)
[23:11:57] <skunkworks> just testing
[23:12:38] <micges> skunkworks: you should add 7i90
[23:13:49] <skunkworks> for?
[23:14:01] <micges> J1900 has also EPP iirc
[23:14:04] <skunkworks> oh - sure - it does have a printer port too..
[23:14:34] <skunkworks> and dual nics - but I don't think 2 ethernet boards are supported yet..
[23:14:59] <micges> testing, you should be able to run 5i25 + 7i80 + 7i90 by lcnc without a problem
[23:15:14] <micges> not yet
[23:15:48] <skunkworks> it is unreal how much expansion you can do..
[23:16:07] <skunkworks> micges: what is the max i/o you have used
[23:16:08] <skunkworks> ?
[23:16:46] <micges> let see
[23:17:13] <micges> 5i25 + (7i77 + 7i84) + (7i76 + 7i71)
[23:17:48] <skunkworks> neat
[23:18:57] <micges> 96 outs and 96 in
[23:19:18] <KimK> Just a small (medium?) knee mill, 32" x 16", 3-axis servo (w/ optional Spindle? 4th? 5th? MPG? W/knee?) I don't have a true I/O count yet, but probably not a lot? No tool changer, though. It's currently a Milltronics, but the control is unrecoverable.
[23:19:22] <KimK> I gave up on Xenomai with the release of the recent LinuxCNC ISO. Is there a reason to stick with Xenomai?
[23:22:06] <KimK> The cabinet internals might make an out-the-back parallel port inconvenient, it may be better to stay inside the cabinet instead of going out and coming back in.
[23:25:47] <KimK> micges: Nice I/O count, any problems? Could you tell how much time was taken up (or left over) for the I/O cycle? And was this at a 1ms servo rate? Were you running base thread too, or no?
[23:27:29] <micges> skunkworks: KimK:
http://imagebin.ca/v/1kLScm2aB0uk
[23:27:42] <micges> KimK: no problems, just plug and play
[23:28:39] <micges> got only 1kHz servo cycle, as for time I didn't measure it but there were two sserial which takes 90us each
[23:29:20] <micges> so total was 5 sserial so up to 50% servo cycle was used
[23:42:40] <KimK> OK, thanks. And the 90us is a Mesa-determined speed? I have in mind a project which would use 8 now, maybe 16 eventually? So 720us now, 1440us later? (Clearly would have to go to 2ms.)
[23:53:33] <KimK> BTW, nice piggybacking on the 7i84 aux i/o and the 7i71 aux o, it took me a minute to look that up and see how that was done. And the primaries, 7i77 and 7i76, you needed both analog servos and steppers?