#linuxcnc-devel Logs

Aug 21 2020

#linuxcnc-devel Calendar

12:21 AM linuxcnc-build: build #7153 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/7153 blamelist: andypugh <andy@bodgesoc.org>
01:44 AM -!- #linuxcnc-devel mode set to +v by weber.freenode.net
04:05 AM linuxcnc-build: build #7155 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/7155 blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
12:12 PM linuxcnc-build: build #7157 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/7157 blamelist: andypugh <andy@bodgesoc.org>
12:37 PM satiowadahc: So I've been off working on our in house linuxcnc development for the better half of a year. And now with the lack of python2 I seem to be a bit behind. I see theres been a few issues created for python3 conversions, is there any where in particular that would be handy to start on that someone else isn't working on
02:48 PM Centurion-Dan2 is now known as Centurion_Dan
03:22 PM jepler: the "master" branch is supposed to be capable of running on python3, but some of the UIs have dependencies that are not available in python2 so they don't work. I believe axis works, but those based on gtk do not.
04:00 PM satiowadahc: I might make a virtual machine shortly and retry. Coming back into the project I went for gold on Ubuntu 20, with kernel 5.6RT, Python3... Suprisingly has a few issues but I'll revert to known U18.04,Kernel5.19
05:23 PM satiowadahc: Hmmm seems I'm stuck on install yapps... Can't find a python3 based version
05:29 PM satiowadahc: Looks like monday problems.. Might try again then
07:10 PM andypugh: Any groff experts? http://buildbot.linuxcnc.org/buildbot/builders/2000.docs/builds/5721/steps/compile/logs/warnings%20%28131%29
07:11 PM andypugh: Comparing man to man/es it _looks_ like the difference is a space after a comma. Does that, in any way, make sense? it seems odd.
08:01 PM jepler: anything in particular, or just all of it?
08:05 PM jepler: Missing backslash
08:05 PM jepler: -.IP \-n \-\-name\ <halname>
08:05 PM jepler: +.IP \-n\ \-\-name\ <halname>
08:06 PM jepler: the space after "-n" needs to be escaped, so that it all forms the "tag" part of the .IP macro's arguments
08:07 PM jepler: .IP "\-n \-\-name <halname>"
08:07 PM jepler: * .IP "\-n \-\-name <halname>"
08:08 PM jepler: huh this so called IRC client seems to be having trouble with things that have angle brackets, almost like it's a bad idea to use a web browser for chat.
08:09 PM jepler: anyway, apparently things can be quoted as well, though the "-" still need to be escaped because they should be the literal "-", not one of the typographic enhancements that man likes to do to things (turn them into en dashes, I think?)
08:11 PM jepler: No warnings: https://gist.github.com/502c8b41bcbe72fae95e3388f0b8725f
08:19 PM jepler: I fixed several other 'types' of error, most were due to inattention to whitespace. This doesn't fix all the diagnostics, just at least one of each "kind" https://github.com/jepler/linuxcnc/pull/new/es-manpage-fixes contains the accumulated fixes
08:19 PM jepler: https://github.com/LinuxCNC/linuxcnc/compare/andypugh/multilingual_comp...jepler:es-manpage-fixes?expand=1 more useful view
08:19 PM jepler: andypugh: enjoy
08:21 PM Tom_itx: the first / doesn't show because it's an irc client command
08:21 PM Tom_itx: i sometimes preface it with alt 255 to avoid that
09:17 PM Tom_itx is now known as Tom_L