John Morris

@cerna I've been taking a little break from this, but will get back to it shortly and think about this harder. First thoughts reading this latest post: - Assumptions/prerequisites agree...

Not too important, but for the sake of interest, the history of the CI was as follows. We initially built packages on a buildbot in my shop. The ARM builds...

> Do you have any idea how much traffic the Machinekit project needs? Packagecloud gives 25 GB of storage and 250 GB traffic (currently the watermark is at about 10...

> I have just downloaded `pyzmq` (source for `python-zmq`), `yapps2` (source for `python-yapps`) and `pyftpdlib` (source for `python-pyftpdlib`) through `pip(3)` command. Given that there are official Python alternatives, why these...

> 1. Distribute problematic APT packages in special repository The MK project has been known to do that in the past. The Jessie repo has (had?) kernel, ZMQ-related and other...

I started taking a look at the Bullseye deps. I suspect it'll take a full python3 upgrade to support Bullseye, and that will probably take some real rework. Some issues...

> > (...)and that will probably take some real rework(...) > > Well, Python2 was EOL for few months and the situation will be worsening with packages going missing left...

Since merging #282 (see #267), the `halshow` program isn't in the `machinekit-hal` repo anymore. It is still available, and works fine, in the LinuxCNC tree that will soon be promoted...

I'm sorry I wasn't following the multicore work, and don't understand v2 components or the issue at hand, but I can explain the `cpuset` feature. In my experiments, I was...

Thinking about this one: > 2. Find a way of being able to tell what type of component is loaded and control the loading. I think the component type could...