Installing 2.10 master

I have decided to try another computer my plasma.
I tried to update to 2.10 on my old setup, but somehow failed.
Since my linux skills are so bad, I decided I should have a linux expert at my side with my newest attempt.
Problem is, I don't have the words to explain to them what exactly I need help with, so I'm asking for help I what directions I should give them.
First off, since it's a fresh install, am I better off installing linuxcnc 2.9.8 and then updating to 2.10, or just start with 2.10?
I assume I use the linuxcnc github to source the correct files?
Basically, what should I tell someone familiar with linux, but not linuxcnc, to get them started on the right path to helping me get linuxcnc 2.10?

In case your curious, I want to use 2.10 for some of the plasmac updates and so I can use pnccomf for my 7i97t.

Thanks in advance, I know there is a lot of information on how to do this on this forum, but when I tried, lunuxcnc would still open to the previous version. Hopefully with a little help, I'll get it this time.

There are installable artefacts in the GitHub actions, get a GitHub account, download those for your system, and install, I would reccomend to use a system for which the CI already builds, you'll have yourself way less headaches

2.10 is currently transitioning to the a new hal API, so mind that is still somewhat work in progress, there is no 2.10 finished release

bentiggin wrote:

I want to use 2.10 for some of the plasmac updates 

2.10 only partially supports Debian 13.
I can't check everything, but it looks like any qtvcp based gui won't work.
Changes in Python traditionally cause the problem.
A new version of numpy, but maybe something else too.
You can work around the problem by installing LinuxCNC on Debian 12, or downgrading some Python packages on Debian 13.
This is of course not a solution to the problem, the solution will be to repair the LinuxCNC sources, but so far no one wants to do that...

All qtvcp UI work on Debian 13, I'm not sure what python problem you are referring to, is this on the latest master?

grandixximo wrote:

All qtvcp UI work on Debian 13, I'm not sure what python problem you are referring to, is this on the latest master?
 

Tuxcnc had some python package version issues when using Debian 13.7 which was only released on 12 September. Just try upgrading debian and see if master branch  breaks now.

No, nothing breaks for me, I am on 13.7 I will investigate the other thread...

tuxcnc wrote: This is of course not a solution to the problem, the solution will be to repair the LinuxCNC sources, but so far no one wants to do that...

Already replied about the issue in your other post, as far as I can tell the issue is not with the LinuxCNC sources as Chris Morley tried to explain (maybe poorly) in the other thread... Anyhow, if you want the devs to take action on issues you find, you should post an issue in github, or mail the dev mailing list emc-users@lists.sourceforge.net if you'd rather do that, we are much more active there. This turn I think it is not a LinuxCNC issue, but next one might, so if you find anything you think is related to the LinuxCNC sources, please report to the channels where the devs are most active...

The matter became clear.
The problem I described was caused by installing the bcnc program.
So you can use LinuxCNC 2.10 with Debian 13.
At least until you install something that breaks Python's dependencies...

I managed to get 2.10 installed. I didn't get any help from a linux expert as I had planned, so who knows if I made any mistakes.
After transferring the config for my plasma table, everything seems to work, except I did have two problems.
This may be better suited to the plasmac category, but I figured I would ask here first before starting a new post there.
I often use the plasma to center spot holes for drilling on larger parts. I use sheetcam to generate the gcode.
On the old computer running linucnc 2.9.4? if I stop the program and use run from line to restart, it would treat everything as a spot, even what should be cuts.
My memory tells me that this was a bug and has been fixed in 2.10(my memory is often wrong).
On the new computer running 2.10, I am able to stop and run from line successfully. At least the first time or two. Eventually, I will get a pop up window that says

Operator Error:
g-code error in rfl.ngc
near line 0 of
/tmp/emcflt-yww9cryf.d/rfl.ngc
cannot use g53 incremental

I will get this message if I try to reload the gcode or even if I load old, known working gcode that doesn't even have spotting operations. The only solution seems to be to restart linuxcnc, but will happen again after stopping and run from line one or a few more times.
Is this a 2.10 thing or did I somehow mess up installing?
Unrelated, but I cannot use the arrow keys to make a cut after pressing f9/single cut. Torch fires. I can use the arrow keys to jog when I haven't pressed f9.
Whether it is 2.10 or if I made mistakes when installing, I don't know, but I wonder if it would be best going back to a stable version.
Any advice appreciated.