#linuxcnc-devel Logs

Nov 13 2022

04:53 AM JT-Cave: pcw--home, thanks
10:34 AM -!- #linuxcnc-devel mode set to +v by ChanServ
01:39 PM andypugh: Is the buildbot bot not here any more?
01:41 PM andypugh: I think that build 4040 needs killing, it’s been staled for 20 hiurs or so.
01:41 PM andypugh: seb_kuzminsky: It seems that resurecting the i386 Buster machine hasn’t worked.
02:29 PM CaptHindsight[m]: andypugh: what do you require access to for the next official release?
02:30 PM CaptHindsight[m]: Rob mentioned checking with his host provider to get a free node to run a buildbot
02:32 PM andypugh: The new release manager will have to decide what platforms need to be built for.
02:33 PM CaptHindsight[m]: I don't that will be a problem
02:34 PM CaptHindsight[m]: * I don't think that will
02:34 PM andypugh: pere: I am having trouble with hal_speaker and RTAI on 2.9. I have a real machine which I just cherry-picked your last commit to, and that builds fine, so I pushed it.
02:34 PM andypugh: Then I checked 2.9 put on a VM, and it doesnt build.
02:35 PM andypugh: (complaining about implicit declaration of ipoerm)
02:35 PM CaptHindsight[m]: choose a release manager from volunteers
02:37 PM CaptHindsight[m]: if Rod can't get a free VM then they are only a few $/mo to run a buildbot
02:38 PM CaptHindsight[m]: silopolis also mentioned some other free options
02:39 PM CaptHindsight[m]: "replace the buildbot with GitHub Actions, probably
02:39 PM CaptHindsight[m]: using Docker container actions to build on Debian and not Ubuntu, and then
02:39 PM CaptHindsight[m]: pushing packages to some artifact hosting service like
02:39 PM CaptHindsight[m]: https://packagecloud.io/l/apt-repository."
02:39 PM andypugh: We don’t have any real problem with the self-hosted repository.
02:40 PM andypugh: It’s just building all the debs to put there that needs new infrastructure.
02:40 PM CaptHindsight[m]: then maybe I missed what the problems are
02:40 PM CaptHindsight[m]: what are the problems wit the next official release?
02:40 PM andypugh: Building the debs
02:41 PM CaptHindsight[m]: for the current buildbot?
02:41 PM andypugh: For all the supported OSes. (Whatever those are)
02:41 PM CaptHindsight[m]: who has access to building the current build bot?
02:42 PM CaptHindsight[m]: I recall Seb having one, is the the one and the same build bot?
02:42 PM andypugh: But probably (Buster + Bullseye) * (AMD64 + Armhf (Arm64?)) * (RTAI + Preempt-RT)
02:43 PM andypugh: Yes, thats the one Buildbot.
02:43 PM CaptHindsight[m]: yeah, those are the main three
02:43 PM andypugh: So, even supporting only Buster + is 8 buildbots.
02:44 PM andypugh: buildbot.linuxcnc.org
02:44 PM CaptHindsight[m]: it shouldn't take much effort to decide if there should be any bother with Buster and just skip to Bullseye
02:44 PM andypugh: Supports Wheezt to Buster.
02:45 PM andypugh: Nobody decides anything. Nobody even answers such questions on the mailing list.
02:45 PM CaptHindsight[m]: they just need a nudge
02:47 PM CaptHindsight[m]: am i missing something here?
02:47 PM CaptHindsight[m]: Is it OK to talk about this?
02:48 PM andypugh: The (current) buildbot does actually build for Buster.
02:49 PM andypugh: (except not at the moment because the Buster / i386 worker seems to be stuck)
02:49 PM andypugh: Also, it doesn’t seem to be able to make 2.9 packages, but that might be a versioning error (and my fault)
02:51 PM CaptHindsight[m]: is the problem fixing the current buildbot?
02:52 PM andypugh: The problem is that there are no builders for Bullseye or Bookworm. Bookworm is being built by Debian, but I don’t think that they will do an RTAI version.
02:53 PM andypugh: Maybe the policy is to wait for Bookworm and stop self-hoting and nobody told me?
02:53 PM CaptHindsight[m]: RTAI users won't have a problem getting RTAI packages from Alec
02:54 PM andypugh: RTAI _LinuxCNC_ packages?
02:55 PM CaptHindsight[m]: that was my impression about LCNC, wait for Bookworm and stop self-hoting
02:55 PM CaptHindsight[m]: andypugh: yes, Alec said he'd maintain RTAI packages, even for Debian
02:55 PM andypugh: So, no 2.9 release until Bookworm?
02:56 PM CaptHindsight[m]: that was what I got from the little I heard, have everything on Debian
02:56 PM andypugh: I am still not clear if you mean the RTAI kernel package or the RTAI LinuxCNC package. And there is also the issue of archive signing keys etc.
02:56 PM CaptHindsight[m]: wait for releases to trickle down
02:58 PM andypugh: And in the meantime keep publishing a .ISO that installs Buster? Despite it being into LTS now?
02:58 PM CaptHindsight[m]: andypugh: he's out right now but I will clarify with him but I believe that he was getting a a LinuxCNC RTAI+uspace build,
02:59 PM andypugh: We already have RTAI + Uspace working, with a helper app and LXRT
03:00 PM andypugh: (ie if you install the RTAI kernel and the uspace LinuxCNC .deb, and also the linuxcnc-uspace-rtai .deb then you get a something that works (though it still doesn’t support hm2_eth)
03:00 PM CaptHindsight[m]: I don't think that there is a problem for him to maintain a RTAI kernel package or the RTAI LinuxCNC package
03:02 PM andypugh: I really would prefer to have the packages somewhere more public, to be honest. The current problem is largely that only Seb has any access to the buildbot.
03:02 PM CaptHindsight[m]: https://forum.linuxcnc.org/18-computer/39371-results-of-latency-test-list-of-computers-tested-for-use-with-linuxcnc?start=320#253800
03:02 PM CaptHindsight[m]: his RTAI Using LXRT realtime
03:03 PM CaptHindsight[m]: that is not a problem for RTAI
03:03 PM andypugh: Yes, I get similar resuts myself.
03:03 PM CaptHindsight[m]: well lets check with Rod in the next day or so
03:04 PM CaptHindsight[m]: he was asking for a free VM from his host or ISP
03:06 PM CaptHindsight[m]: people have already been hosting debs they build for Bullseye and Bookworm
03:07 PM CaptHindsight[m]: qtpyvcp devs have had to to keep development moving ahead
03:13 PM CaptHindsight[m]: https://repository.qtpyvcp.com/repo/linuxcnc_debs/
03:13 PM CaptHindsight[m]: maybe they have extra space for a buildbot, I'll ask them
03:21 PM pere: andypugh: sound like you do not have the latest patch.
03:22 PM andypugh: pere: I cherry-picked the latest patch earlier. Looking at the files it all looked fine.
03:22 PM andypugh: In the end I deleted the whole folder and re-cloned it, and then it worked fine. I have no idea what was going on, and no real incentive to work it out.
03:23 PM pere: wowo
03:23 PM pere: wow, I mean.
03:23 PM pere: got to run
04:45 PM Tom_L: is linuxcnc on bookworm being hosted by debian now?
04:47 PM CaptHindsight[m]: Tom_L https://packages.debian.org/search?suite=bookworm&keywords=linuxcnc-uspace
04:47 PM Tom_L: i thought it was
04:47 PM CaptHindsight[m]: nothing for Bullseye
04:47 PM Tom_L: buster and bullseye are the problem children
04:48 PM Tom_L: well, buster may be covered by the buildbot
04:48 PM CaptHindsight[m]: if people would just stop talking about bullseye the problem goes away
04:48 PM Tom_L: at least it's in the dist list
04:48 PM Tom_L: i'm for that
04:48 PM Tom_L: i'm running bookworm anyway
04:49 PM Tom_L: there was one around wheezy time that didn't get alot of mention either
04:55 PM Tom_L: by the time there is a solution for it bookworm will likely be released anyway
05:01 PM CaptHindsight[m]: I'm using Sid and Bookworm
05:01 PM CaptHindsight[m]: of the debians