#linuxcnc-devel | Logs for 2014-12-01

[00:14:17] <seb_kuzminsky> micges: i'm uncertain about commit 37068c76 in 2.6
[00:15:05] <seb_kuzminsky> i bet it's right, but it seems wrong to change the default parallel port address in 2.6
[00:15:24] <seb_kuzminsky> i'd prefer to see 2.6 restored to it's previous behavior, and this change go into 2.7
[00:19:01] <seb_kuzminsky> wow, well there's the debian fork over the systemd issue: https://devuan.org/
[00:19:12] <seb_kuzminsky> that's enough open source for me for tonight
[04:23:57] <atom1> seb_kuzminsky, tom@atom1:~/linuxcnc-dev$ dpkg-checkbuilddeps
[04:23:59] <atom1> dpkg-checkbuilddeps: error: cannot read debian/control: No such file or directory
[04:24:21] <atom1> i'm getting all sorts of other errors after that as well
[04:24:36] <atom1> configure: error: GTK2 missing. Install it or specify --disable-gtk to skip the parts of LinuxCNC that depend on GTK
[04:24:40] <atom1> for one
[04:25:56] <atom1> configure: error: tk lib not found
[04:26:47] <Tom_itx> i'm calling it on this one for now.
[06:25:57] <jthornton> what are you trying to install?
[06:33:19] <Tom_itx> 2.7 on a wheezy iso install
[06:34:06] <Tom_itx> it worked ok on ubuntu 10.04
[06:34:26] <Tom_itx> so i pulled out the ssd to try it on wheezy and had nothing but trouble
[06:37:15] <jthornton> yea me too, I tried dgarr/moveoff branch on wheezy with nothing but problems
[06:37:47] <Tom_itx> i'm pretty sure they strip it down for efficiency but...
[06:37:54] <Tom_itx> all sorts of packages missing
[06:38:01] <Tom_itx> alot of gnome stuff
[06:38:06] <Tom_itx> seemed like
[06:39:20] <Tom_itx> seb_kuzminsky's suggestions got it further along though
[06:39:56] <Tom_itx> 17°F
[06:40:29] <Tom_itx> from 60+ a couple days ago
[06:42:06] <jthornton> I just tested moveoff in hardy and it works YEA
[06:42:13] <Tom_itx> nice
[06:42:23] <Tom_itx> i've been waiting for that
[06:46:34] <Tom_itx> that and the TP sound like a couple nice improvements
[06:55:01] <jthornton> I finally found the output for Z it's mv.plusoffset-2
[07:05:28] <jthornton> nice when you have an offset the pause button has a red slash and won't unpause
[07:06:14] <Tom_itx> how do you return it to it's original point?
[07:06:47] <jthornton> a dialog pops up and you can use + or - buttons to move the axis and when your close hit the zero button
[07:07:21] <Tom_itx> multiple axis?
[07:07:47] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/moveoff 88ad4dc 06linuxcnc 10configs/sim/axis/moveoff/moveoff.hal 10src/hal/components/moveoff.comp moveoff.comp: fix name for pos-plusoffset-M * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=88ad4dc
[07:07:47] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/moveoff 578176f 06linuxcnc 10scripts/moveoff_gui moveoff_gui detect waypoint_limit and show * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=578176f
[07:09:04] <Tom_itx> even as we speak!
[07:09:13] <Tom_itx> later...
[08:48:24] <seb_kuzminsky> Tom_itx: so you *dont* have the build dependencies installed, just like the configure script says
[08:48:44] <seb_kuzminsky> the live CD is optimized for users, not developers
[08:49:01] <seb_kuzminsky> users need to install the build dependencies before they can do non-user things like build different branches
[08:49:54] <seb_kuzminsky> Tom_itx: did you see the instructions i linked above? http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Installing_LinuxCNC#Resolving_outstanding_build_dependencies
[08:50:42] <seb_kuzminsky> jthornton: awesome!
[09:06:50] <seb_kuzminsky> JT-Shop: did you get dgarr's moveoff built successfully? or are you still running into problems?
[09:09:23] <JT-Shop> seb_kuzminsky, I tested it on 10.04 this morning but have not tested it on wheezy since the other day
[09:10:10] <seb_kuzminsky> cool
[09:10:36] <JT-Shop> last time I tried to do a RIP on wheezy it gave me errors
[09:10:53] <seb_kuzminsky> was it the same kind of configure-time missing-dependency problems that Tom_itx was having?
[09:11:22] <JT-Shop> IIRC I resolved that
[09:11:27] <seb_kuzminsky> oh good
[09:12:16] <JT-Shop> checking for library containing Tcl_Init... no
[09:12:16] <JT-Shop> configure: error: tcl lib not found
[09:12:25] <JT-Shop> this is where I'm at now
[09:12:46] <seb_kuzminsky> sounds like a missing tclNumber.Number-dev
[09:13:08] <seb_kuzminsky> that dpkg-checkbuilddeps trick i linked Tom_itx above should fix it, if so
[09:15:16] <JT-Shop> logger[mah], log
[09:15:16] <logger[mah]> JT-Shop: Log stored at http://linuxcnc.mah.priv.at/irc/%23linuxcnc-devel/2014-12-01.html
[09:51:58] <seb_kuzminsky> linuxcnc-build_: force build --branch=2.6
[09:51:58] <linuxcnc-build_> you must provide a Builder, try 'force build [--branch=BRANCH] [--revision=REVISION] [--props=PROP1=VAL1,PROP2=VAL2...] <WHICH> <REASON>'
[09:52:02] <seb_kuzminsky> linuxcnc-build_: force build --branch=2.6 0000.checkin
[09:52:03] <linuxcnc-build_> build forced [ETA 1h13m21s]
[09:52:03] <linuxcnc-build_> I'll give a shout when the build finishes
[09:52:14] <cradek> https://lists.dyne.org/lurker/message/20141127.212941.f55acc3a.en.html
[09:55:06] <pcw_home> seb_kuzminsky the paralle port issue is not serious but the second default address of 0x3F8 is totaly bogus (thats a COM1 port address)
[10:01:40] <skunkworks> Think we are leaning towards retro on the mazak.
[10:02:11] <skunkworks> But things work 'enough' that I think we can figure out how things work.
[10:02:40] <skunkworks> The one issue is - it looks like X and Y have resolvers - spindle has an encoder.
[10:02:42] <pcw_home> (you can only get the bogus address used if you include 2 firmwares but no port addresses or various typos that confuse the config line parser)
[10:03:55] <skunkworks> Hope to reuse the spindle vfd - (spindle does jog)
[10:05:00] <skunkworks> pcw_home, I suppose the resolver interface doesn't have any encoder counters?
[10:05:52] <pcw_home> Nope but you can of course ass a dauightercard that has encoders
[10:06:00] <skunkworks> sure
[10:06:13] <pcw_home> sorry . _add_ a daughtercard
[10:06:16] <skunkworks> heh
[10:06:46] <pcw_home> fingers not awake
[10:06:48] <skunkworks> looks from the documentation that they have been chasing a X axis issue.
[10:07:42] <skunkworks> lots of pot turning it seems which makes me think there was an issue they where missing. (even looks like they replaced the resolver and leadscre...)
[10:07:45] <pcw_home> you can hope that is issue is above the drives/resolvers
[10:08:31] <pcw_home> are these DC drives?
[10:08:34] <skunkworks> we will probably replace the drives - we have a bunch of amc's
[10:08:47] <skunkworks> yes - brushed servo.
[10:08:58] <skunkworks> 1kw I think is the Z
[10:09:05] <skunkworks> X is less.
[10:11:40] <pcw_home> If you are replacing drives there's not much left to cause trouble
[10:15:53] <PetefromTn_> skunkworks Man that sounds like a big project. Sorry to hear the mazak is not going to work as you bought it. BUt at least you can make it possibly even better now ;)
[10:19:07] <skunkworks> we got it for 2K - we never assumed the original control was going to stay...
[10:19:24] <skunkworks> Plus having all the machines running linuxcnc helps dad.
[10:19:25] <PetefromTn_> sounds like my Cincinatti heh
[10:20:48] <skunkworks> The turret rotates.. spindle jogs.. axis moves..
[10:21:03] <PetefromTn_> sweet,
[10:21:05] <skunkworks> All the stuff we need seems to work.
[10:21:22] <PetefromTn_> my machine actually worked when I got it after I reset the firmware
[10:21:38] <PetefromTn_> but then it started blowing expensive boards so I bailed on the original electronics
[10:24:42] <seb_kuzminsky> pcw_home: i realize the bogosity of second default parport address
[10:25:10] <seb_kuzminsky> it's very unlikely that anyone is using it and having it work
[10:26:27] <seb_kuzminsky> but even so i dont want to change defaults in the middle of a stable branch
[10:26:40] <seb_kuzminsky> the change is welcome in 2.7
[10:27:13] <seb_kuzminsky> i can move it or micges can if you prefer
[10:34:44] <pcw_home> On a PC its is impossible for 0x3F8 to ever have worked, so its a bug
[10:36:23] <pcw_home> (though a very difficult to invoke and easy to work around bug)
[10:43:38] <linuxcnc-build_> Hey! build 0000.checkin #2729 is complete: Success [3build successful]
[10:43:38] <linuxcnc-build_> Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/2729
[10:51:41] <seb_kuzminsky> linuxcnc-build_: force build --branch=2.6 0000.checkin
[10:51:44] <linuxcnc-build_> build forced [ETA 1h02m28s]
[10:51:44] <linuxcnc-build_> I'll give a shout when the build finishes
[10:52:49] <seb_kuzminsky> pcw_home: on a pc with 2 parallel ports and 0 serial ports, i think 0x3f8 could be used for a parport, no?
[10:53:56] <jepler> Today it might be best to say 0,1
[10:54:04] <jepler> linux parport numbers, not I/O port numbers
[10:55:25] <seb_kuzminsky> hmm
[10:56:30] <kwallace2> The motherboard parallel port address can usually be set to one of the common defaults in BIOS?
[10:56:35] <seb_kuzminsky> jepler: the 7i43 driver does ins and outs by hand, using the ioaddr the user supplies (or the default)
[10:56:46] <seb_kuzminsky> it does not go through a linux driver
[10:58:03] <pcw_home> seb_kuzminsky 0x3F8 is never used for parallel ports
[10:59:02] <pcw_home> Motherboard ports are 0x378, 0x278, 0x3BC, PCI can be anywhere buts is almost always above 0x1000
[11:00:31] <kwallace2> Ah 3F8 = serial port
[11:01:22] <jepler> seb_kuzminsky: if you pass hal_parport_get a 'base' address < 16, it finds the base'th linux parport and claims it. it populates the 'port' out argument with linux's actual base address; additionally, if the base_hi parameter is 0, it populates port->base_hi with linux's idea of the port's high I/O address too
[11:02:11] <jepler> seb_kuzminsky: so as long as hm2_7i43 takes care to use port.base and port.base_hi, it should work in rtai and uspace to use linux port numbering rather than I/O addresses
[11:02:55] <jepler> this should go for all drivers that use hal_parport APIs, which is all the in-tree ones
[11:04:48] <seb_kuzminsky> ok, i see
[11:06:53] <jepler> now the problem that might arise if you did use 0,1 is: hal_parport_get will return -errno if there's no port 1, making hm2_7i43_setup return -errno, causing the whole driver to not load
[11:07:08] <jepler> ah but you'd only hit that if you had two config strings defined
[11:31:10] <JT-Shop> seb_kuzminsky, got moveoff working on wheezy
[11:34:45] <seb_kuzminsky> oh good
[11:55:09] <cradek> http://www.phoronix.com/scan.php?page=news_item&px=MTg1MTM
[11:55:23] <cradek> I really should try coreboot on something
[11:55:44] <cradek> fwiw, I see this board has pci slots and a parport
[12:00:01] <pcw_home> thats a LGA775 MB?
[12:02:09] <pcw_home> No I see its LGA1155 MB
[12:08:43] <seb_kuzminsky> cradek: that looks pretty sweet
[12:09:30] <seb_kuzminsky> matt shaver initially had trouble with that board, but i think he got it working with lucid/rtai: http://thread.gmane.org/gmane.linux.distributions.emc.devel/9246
[12:11:02] <seb_kuzminsky> has anyone heard from matt lately? i haven't...
[12:14:30] <pcw_home> intel desktop pinout chronology is something like 775, 1155, 1150, 2011 (dont know if 2011 is only for high end chips)
[12:14:32] <pcw_home> I havent heard from Matt for several months
[12:23:11] <linuxcnc-build_> Hey! build 0000.checkin #2730 is complete: Success [3build successful]
[12:23:11] <linuxcnc-build_> Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/2730
[13:11:09] <seb_kuzminsky> linuxcnc-build: force build --branch=2.6 2000.docs
[13:11:11] <linuxcnc-build> build #2207 forced
[13:11:11] <linuxcnc-build> I'll give a shout when the build finishes
[13:20:02] <linuxcnc-build> Hey! build 2000.docs #2207 is complete: Warnings [8warnings compile]
[13:20:02] <linuxcnc-build> Build details are at http://buildbot.linuxcnc.org/buildbot/builders/2000.docs/builds/2207
[13:23:54] <seb_kuzminsky> linuxcnc-build: force build --branch=2.6 2000.docs
[13:23:54] <linuxcnc-build> build #2208 forced
[13:23:55] <linuxcnc-build> I'll give a shout when the build finishes
[13:32:18] <linuxcnc-build> Hey! build 2000.docs #2208 is complete: Warnings [8warnings compile]
[13:32:19] <linuxcnc-build> Build details are at http://buildbot.linuxcnc.org/buildbot/builders/2000.docs/builds/2208
[13:36:49] <seb_kuzminsky> ok whew
[13:37:22] <seb_kuzminsky> the buildmaster resets its umask to 002, which messes up the permissions on all the files and directories it creates
[13:38:04] <seb_kuzminsky> such as the docs dirs at http://buildbot.linuxcnc.org/doc
[13:38:31] <seb_kuzminsky> i guess it's not that often that a buildmaster creates files, that's usually done by the slaves
[13:38:45] <seb_kuzminsky> and buildbot lets you control the umask the slaves use, but not the master
[14:14:32] <skunkworks> If I have the 7i80 - how could i hook up the 7i74 easy?
[14:16:01] <skunkworks> I am thinking of replacing the resolvers with encoders.. (sorry andy...) so that means the 7i48.
[14:17:27] <micges> skunkworks: you must have 7i80HD to connect 7i48 and 7i80DB to connect 7i74
[14:17:47] <skunkworks> I have the HD.
[14:19:01] <micges> so directly 7i48 and 7i74 through HD-DB ADAPTER
[14:19:19] <micges> and custom firmware
[14:20:33] <skunkworks> or a 7i44...
[14:20:53] <micges> yes
[14:24:14] <skunkworks> wow - mesa has a lot of boards..
[14:26:21] <micges> what do you need?
[14:26:44] <CaptHindsight> I wonder how they sell them without having cute names like cape, shield, trenchcoat, etc etc?
[14:29:57] <skunkworks> I have the 7i80hd. I need atleast 3 analog outputs - 6 would be better. (hence the 7i48). I would like to use most of the other to plugs for opto22 boards. (and also use the 7i73 some how)
[14:31:09] <skunkworks> (so 48ish i/o - we have the 24 plug opto22 boards and like how they work)
[14:32:20] <skunkworks> We like to stay with the HD style 50 pin setup because that is what is in the K&T for trouble shooting
[14:36:17] <skunkworks> I could use one plug for the 7i44 I suppose.. (that would be alot of expantion..) I don't think 24 pins of I/O will be enough..
[14:37:23] <micges> use 7i84 for io
[14:38:08] <micges> 7i80->7i74->7i84,7i73
[14:38:17] <micges> and 7i48 on second hd
[14:46:35] <skunkworks> hmm the 7i69 would work to..
[14:47:33] <skunkworks> and they are in stock..
[14:52:25] <skunkworks> wow - that is inexpensive for what you get..
[14:58:49] <cradek> oh hell, we're going to argue about goto again
[14:59:52] <skunkworks> heh
[15:13:50] <seb_kuzminsky> maybe we'll get lucky & they'll argue about turtle graphics instead
[15:14:45] <cradek> I'm going to argue strongly that it's wrong to have strong feelings about whether or not gcode has goto
[15:15:33] <cradek> oh gross, then there's stuart
[15:16:06] <skunkworks> /me shakes his head....
[15:16:10] <skunkworks> heh
[15:22:46] <bjmorel_work> Anything to distract me from buying something I don't need because of these damn cyber Monday deals.
[15:30:25] <seb_kuzminsky> i want to buy one of those coreboot/maybe-linuxcnc motherboards cradek linked...
[15:36:44] <CaptHindsight> I don't know what comments they leave in the intel coreboot code but unless the dev tweaked the settings performance with RTAI might be worse with coreboot
[15:37:10] <CaptHindsight> with AMD you can get most of the register docs
[15:52:20] <seb_kuzminsky> huh, if you miss when you type "git" you get "fur"
[15:53:02] <Tom_itx> or hoy
[15:53:13] <seb_kuzminsky> heh
[15:53:24] <Tom_itx> i'm gonna work on that this evening
[15:53:43] <CaptHindsight> I guess i should learn to type one of these days (and other words)
[15:53:54] <seb_kuzminsky> Tom_itx: your 2.7 build on wheezy?
[15:53:59] <Tom_itx> yes
[15:54:07] <Tom_itx> i saw the link.. going thru it
[15:54:23] <Tom_itx> it's more just an exercise
[15:54:24] <seb_kuzminsky> cool, i bet it's something simple, we know it works fine in the buildbot and on other peoples' machines
[15:54:37] <Tom_itx> i realize the iso is crippled..
[16:03:50] <seb_kuzminsky> Tom_itx: i disagree, it's optimized for a different use case than what you are doing
[16:03:59] <seb_kuzminsky> it's well suited to that use case
[16:05:55] <PCW> skunkworks: a 7I90 will work for OPTO-22 expansion (like a 3 connector 7I69)
[16:06:41] <Tom_itx> seb_kuzminsky i realize that
[16:18:38] <Tom_itx> seb_kuzminsky, that's kinda what i meant to say :)
[16:21:37] <PCW> this little script works for me for building master on a virgin ISO:
[16:21:39] <PCW> http://pastecode.org/index.php/view/87690064
[16:21:40] <PCW> (well for uspace)
[16:23:37] <seb_kuzminsky> PCW: that looks about like what i do
[16:24:02] <seb_kuzminsky> you shouldn't need to apt-get libudev-dev, that should be in the build-dep list for linuxcnc (unless we forgot to add it)
[16:24:20] <seb_kuzminsky> also, right after 'git clone', the 'git pull' is not necessary
[16:25:26] <PCW> Yeah nor checkout master
[16:25:27] <PCW> the udev stuff was needed and missing at one time
[16:25:35] <Tom_itx> PCW is that for wheezy?
[16:25:42] <PCW> Yes
[16:26:05] <seb_kuzminsky> it should be the same on wheezy, lucid, and precise
[16:28:10] <PCW> (Other than the kernel, I assume the preemt-RT kernel is Wheezy only)
[16:29:03] <PCW> probably also needs some grub foo to add the new kernel to the list
[16:29:25] <PCW> (unless install does that)
[16:32:36] <seb_kuzminsky> yeah, good point, the rt-preempt kernel is only available on wheezy
[16:35:31] <Tom_itx> i may start again with the iso just to clear any mess i made along the way
[16:36:05] <Tom_itx> it's going on a spare drive anyway
[16:41:39] <Tom_itx> PCW what does the --with-realtime=uspace do ?
[16:42:42] <Connor> Tom_itx: makes it so that you can run it on a non-realtime kernel I think.
[16:44:23] <seb_kuzminsky> Connor: that's right
[16:44:30] <Tom_itx> thanks
[16:44:35] <Connor> WooT I got something right! :)
[16:44:40] <Tom_itx> heh
[16:44:57] <seb_kuzminsky> it configures linuxcnc to build so it can run on an rt-preempt kernel or a "vanilla" kernel without any realtime extensions
[16:54:15] <skunkworks> logger[psha]:
[16:54:16] <logger[psha]> skunkworks: Log stored at http://psha.org.ru/irc/%23linuxcnc-devel/2014-12-01.html
[17:08:36] <skunkworks> PCW, Oh - the 7i90 could be setup as a smart serial device?
[17:23:20] <skunkworks> I don't know if I need all the i/o. Just a feeling. the 6i69 seems cool because I could have opto22 panels in 2 different locations. I doubt if I need more than 72 i/o...
[17:24:15] <skunkworks> (on 50 pin on the 7i80 and 2 on the 6i90
[17:24:20] <PCW> Yeah the 7I90 has 4 modes
[17:24:56] <PCW> EPP/SPI/Serial/SSerial-remote)
[17:25:26] <skunkworks> *7i69
[17:26:25] <PCW> the 7I69 has somewhat smarter firmware that the 7I90 in ssremote mode and allows bit reversed OPTO 22 I/O to match the IO module rack numbering
[17:28:13] <PCW> I may add that feature to the 7I90 if I develop enough ambition
[17:28:29] <skunkworks> neat
[17:29:46] <PCW> probably have to add bitreverse hardware or instruction
[17:30:04] <skunkworks> we will look - but it may be just as easy to swap to encoder.. (even though I like resolvers) The spindle has an encoder and the 2 axis have resolvers.
[17:31:17] <skunkworks> Plus then we have another 7i48 for troubleshooting
[17:33:12] <PCW> if you plan to use OPTO-22 I/O and 2 connectors (48 I/O) is enough then just use the 7I80 I/O directly
[17:33:32] <PCW> (assuming you change to encoders)
[17:37:33] <skunkworks> I wanted to use the remote panel.. which is 422..
[17:38:18] <skunkworks> 7i74
[17:38:26] <skunkworks> so I need some way to do smart serial
[17:40:02] <skunkworks> so the 7i44 takes up one connector
[17:41:10] <skunkworks> so - 7i44 -> 7i74
[17:41:11] <skunkworks> |-> 7i69
[17:46:59] <skunkworks> if that makes sense
[18:40:34] <seb_kuzminsky> PCW: can you advise on this bug? https://sourceforge.net/p/emc/bugs/407/
[19:15:10] <Connor> PCW Is just my imagination, or does the picture of th 7i69 on the website have green wire fixes (red wire in this case)
[19:16:01] <Connor> 7i70 picture has one too. :)
[19:24:23] <PCW> Yeah photos are often of protos
[19:28:56] <PCW> seb_kuzminsky: I think that's bogus (or maybe an old version) Jepler looked and said the current ini files had lower case
[19:34:39] <Tom_itx> seb_kuzminsky, PCW, thanks for your help!
[19:34:44] <Tom_itx> got it to compile finally
[20:30:01] <seb_kuzminsky> PCW: ok thanks
[22:04:25] <KimK> On Sourceforge here ( http://sourceforge.net/projects/emc/support?source=navbar ) it says, "Best Way to Get Help - LinuxCNC (formerly EMC) says the best way to get help with its software is by visiting http://www.linuxcnc.org/content/view/4/8/lang,en/ " Which turns out to be a dead link, 404 Not Found.
[22:09:09] <KimK> Maybe Sourceforge itself is a dead end anymore? Anyway, now you know, FWIW.
[22:24:05] <seb_kuzminsky> KimK: thanks for the bug report!
[22:24:14] <seb_kuzminsky> i wonder if i have enough SF credentials to fix it...
[22:25:21] <KimK> Hi Seb. Yes, after I thought about it a bit, I wondered how much we even use Sourceforge anymore, but there you go.
[22:27:25] <KimK> I guess if we're still running our bug tickets out of there, we're still using it. Isn't there a git bug ticket app? Maybe we should be doing our own bug tickets?
[22:27:41] <seb_kuzminsky> i'm only a Developer and bug-admin on SF, and i can't find any way to edit our Support page there
[22:27:51] <seb_kuzminsky> one of the guys with Admin access should look at it
[22:28:30] <seb_kuzminsky> eh, that's alex_joni, cradek, jepler_, and some others that we dont see much any more
[22:28:48] <KimK> OK Seb, hey, thanks for trying.
[22:28:48] <seb_kuzminsky> including, amusingly(?), Mr. Weeabo
[22:29:06] <cradek> oh don't start
[22:29:12] <seb_kuzminsky> we still use SF for mailing lists and bug tracking
[22:29:24] <seb_kuzminsky> well maybe he shouldnt have admin access to the sf project any more...
[22:29:33] <seb_kuzminsky> https://sourceforge.net/p/emc/_members/
[22:30:05] <seb_kuzminsky> did anyone try to repro eslavko's streamer bug? https://sourceforge.net/p/emc/bugs/405/
[22:31:08] <cradek> there, uh, I pointed it at the mailing lists
[22:31:15] <seb_kuzminsky> thanks
[22:31:21] * cradek shrugs
[22:31:53] <KimK> Thanks Chris, the 404 did look kind of bad
[22:32:06] <skunkworks> who is Weeabo?
[22:32:20] <skunkworks> inside joke?
[22:32:32] <seb_kuzminsky> pawl coroner
[22:32:48] <skunkworks> ah..
[22:34:10] <skunkworks> his site is still up - but no new posts since 08
[22:38:10] <skunkworks> pcw_home: when do you think you will get some 7i73's in stock?
[22:44:48] <pcw_home> Couple weeks, we are way behind...
[22:45:22] <KimK> I found them: ticgit & ticgitweb, they're in the repos. But ticgit is now unmaintained and deprecated, now see ticgit-ng instead. Mostly written in Ruby, if that makes a difference. Maybe here now?: https://github.com/schacon/ticgit/tree/master/lib/ticgit-ng
[22:46:15] <KimK> "ticgit is an issue tracking system based in the Git revision control system. Tickets are stored in a separate branch called “ticgit” within a Git repository that can be made available on a public server along with the project’s source code. The idea is to keep tickets close to a project without touching its source tree. "
[22:55:50] <KimK> So then, http://ticgit.linuxcnc.org/ ? That would be pretty cool.
[23:03:54] <KimK> More info: "Note: the original TicGit author has pulled all the TicGit-ng changes into his repository, creating a potentially confusing situation. The schacon TicGit repo, this one, is not consistently maintained. For up to date TicGit-ng info and code, check the canonical TicGit-ng repository at https://github.com/jeffWelling/ticgit "
[23:23:26] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/moveoff c5f3d9f 06linuxcnc 10scripts/moveoff_gui moveoff_gui: option for -noentry * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c5f3d9f
[23:23:27] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/moveoff 0744f5c 06linuxcnc 10configs/sim/axis/moveoff/moveoff.halshow 10scripts/moveoff_gui 10src/hal/components/moveoff.comp moveoff.comp: provide waypoint-percent-used pin * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=0744f5c
[23:23:27] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/moveoff 8e4b227 06linuxcnc 10scripts/moveoff_gui 10src/hal/components/moveoff.comp moveoff_gui: replace zero button with per axis 0 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=8e4b227