Update LinuxCNC 2.9.5 on debian 13

I don't know why there seems to be a dependency on an old Python3 version, I don't see that anywhere in the Debian config folder.

github.com/LinuxCNC/linuxcnc/blob/2.9/debian/control.top.in#L44

f355 wrote:

However, the debian package itself seems to have a broken python3 dependency. I'm on the latest Raspberry Pi OS Lite (which is basically trixie with a custom kernel and a few Pi-specific tools installed). Any particular reason for the arm64 package to want python3 < 3.12? amd64 one depends on 3.13, and so does linuxcnc-uspace 2.9.4 that comes with trixie.
 

It's possibly a consequence of the recent Pi .deb that I posted being built on Bookworm as I don't have a Pi running Trixie at the moment. 
The Debian package control files don't specify a version, but it is possible that a dependency is introduced by the configure step of the software build. 

I have a feeling that the package for the Pi in www.linuxcnc.org/dists/trixie might be the Bookworm package rather than one built on Pi/Trixie. I don't know how that happened at this point, I might just have been hoping that it would work and have now found out otherwise 
 

At the time, there was no way to build an image file that included custom software.
The image builder we created is based on a fork of  github.com/pyavitz/rpi-img-builder The original author gave us amazing support and advice. This repo builds the kernel from source and we had to patch the kernel to produce a PREEMPT_RT version. This proved tricky because the kernel version needed to match a version of the RT patch so we had to ensure we got the  Pi kernel code at a specific commit.
This is a cross compiler environment on amd64  as doing what we do would likely take days on a pi.

At the time, there was no LinuxCNC Deb file (linuxcnc-uspace) for the Pi so we had no choice but to build from source. I still don't believe we have a buildbot building for the Pi.

Today, you may be able to use the Debian build system we use for amd64 because the RT kernel and linuxcnc-uspace v 2.94 are in the debian repos. It uses a chroot, so it may permit building on amd64 but I have never seen settings for that. 

andypugh wrote:

f355 wrote:

I have a feeling that the package for the Pi in www.linuxcnc.org/dists/trixie might be the Bookworm package rather than one built on Pi/Trixie. I don't know how that happened at this point, I might just have been hoping that it would work and have now found out otherwise 


 

I think you would need to edit the release variable in the userdata.txt file but you'd also need to sync our repo to the upstream sources

I've been playing with pi-gen.....I think it is a little better, you get a more raspberry pi like experience. There's a link in my proposal thread. ATM the moment I've been building upto the "lite" stage burning & booting and installing the desktop,Xorg and the rest. Linuxcnc has been from the debian repo.....But I should be able to fine tune things.

Bookworm has been the target so far, Trixie shouldn't be an issue, but one thing I really need to know is the status of linuxcnc.org/docs/2.9/html/drivers/hal_gpio.html . I think there was an issue with the libgpiod library.
Bookworm version is 1.6.3-1
Trixie version is 2.2.1-2

You can burn to your boot device sing RPI-Imager and edit settings such via the imager.

There's realtime kernels available via the raspberry kernel repo. The Rpi4 4k page kernels run on the Rpi5.......so we may only need one image to cover both boards.

Your could just upgrade Bookworm  to Trixie with sudo apt dist-upgrade for testing