#linuxcnc-devel Logs

Jul 14 2022

#linuxcnc-devel Calendar

01:15 AM -!- #linuxcnc-devel mode set to +v by ChanServ
02:18 AM pere: hi
05:18 AM pere: is building on anything older than debian/buster currently supported?
06:07 AM rmu: pere: I don't know if it is "supported", but I regularly use linuxcnc on ubuntu LTS releases for simulation purposes
06:12 AM pere: rmu: I talk about building the git master branch.
06:12 AM pere: rmu: which version of debhelper are you building with?
06:18 AM rmu: pere: yes i'm running git master branch on ubuntu 20.4 lts in a "run in place" configuration
06:19 AM rmu: debhelper is the version from KDE Neon project 13.3.3ubuntu3+p20.04+trelease+git20210331.1428
06:20 AM pere: I take it you do not know the version number. Can you run 'dpkg -l debhelper'?
06:21 AM rmu: I just posted the version numbner, dpkg -l debhelper says the same.
06:21 AM pere: ah, I took that as the KDE Noen version number.
06:22 AM pere: it is newer than debian buster, which provides debhelper 10.
06:23 AM pere: the build rules seem to claim that debhelper 9 is working, but I could not get compat level 9 to work at all, and started to wonder if this is a false claim.
06:25 AM rmu: sorry i can't help, no idea about debian packaging stuff. and my system is pretty "polluted" with kde neon and all other sorts of PPAs
06:25 AM pere: you really helped to have another data point, so nothing to be sorry for.
06:33 AM rmu: on the real machine i have debhelper 11.1.6ubuntu2, ubuntu 18.04.6 lts, running linuxcnc master from 3 days ago or so
06:36 AM pere: On my real machine I run debian/testing/bookworm.
08:27 AM pere: just learned that po4a 0.67 with even better asciidoc support was just released. :)
08:28 AM pere: <URL: https://github.com/mquinson/po4a/releases/tag/v0.67 >
09:22 AM pere: I hope <URL: https://github.com/LinuxCNC/linuxcnc/pull/1835 > can make life easier for the project and its deb package maintainers.
10:02 AM pere: should we move to the latest po4a as a requirement, to get better handling of line breaks in asciidoc?
11:27 AM silopolis[m]: <pere> "should we move to the latest..." <- In master definitely!
11:29 AM silopolis[m]: And, still for master, we shouldn't worry about packages versions older than current stable... My personnal opinion being that master should be based on testing
11:32 AM pere: silopolis[m]: only way for that to happen is for the distribution CD to be updated to testing too. apparently several users run directly from git on old debian and ubuntu installations.
11:41 AM silopolis[m]: No, we keep cd and official support on stable
11:44 AM pere: good luck with that approach.
11:48 AM silopolis[m]: Building from sources should not be considered a supported way of running "in production" and not for Jo user
11:49 AM pere: silopolis[m]: you do not have to convince me, I am not the decision maker here. I am just telling you that the way this project is managed, it is, and you need to take it into account.
01:28 PM pere: I discovered that by translating a few key header strings, I can get a significant amount of manual pages translated. :)
01:29 PM pere: a very small man page was suddenly more than 60% translated thanks to generic terms and strings shared across many man pages.
02:15 PM Tom_L: that's great
05:36 PM pere: Is <URL: https://github.com/LinuxCNC/linuxcnc/pull/98 > still interesting to merge?