I can make sure RTAI works with LinuxCNC myself, no need for Seb's stuff or
anyone's VMs for that matter. Adding back in RTAI support though to the
LinuxCNC Debian configure script would be helpful. I started on it but it's not
finished.
https://github.com/LinuxCNC/linuxcnc/issues/2052
In case
On 2022-11-14 15:54, Sebastian Kuzminsky wrote:
In order to support testing LinuxCNC on RTAI the buildbot uses custom
VMs which i created a long time ago and maintain poorly. It all runs
on hardware in my house, on my local network, so I am reluctant to
open it up to a more collaborative mode o
https://www.mail-archive.com/emc-developers@lists.sourceforge.net/msg23329.html
full link in case it gets truncated and you get a 404
On 11/14/22 18:55, Alec Ari via Emc-developers wrote:
I don't mind building LinuxCNC RTAI packages but the problem is actually a
license problem. LinuxCNC keeps
I don't mind building LinuxCNC RTAI packages but the problem is actually a
license problem. LinuxCNC keeps complaining after the ./configure about how
it's a non-distributable build, but that flag has to be set due to the readline
GPL-v2/LGPL starting with Debian Bullseye, otherwise the configur
I'll just wait until you guys decide on a way forward and iff the offer we
have is required.
Perhaps the Github actions could be extended to build the 2.9 branch?
If that were possible, maybe the VM here does the RTAI build?
I'm not sure git will host the resulting debs but it might be worth
ment
On 11/14/22 15:54, Sebastian Kuzminsky wrote:
The difficulty with building and testing LinuxCNC in docker containers
or in off-the-shelf VMs (as in Github Actions) is that our 'RTAI'
configuration needs a special kernel, and needs to load and unload
kernel modules to run & test LinuxCNC.
(
On 11/14/22 13:37, Jérémie Tarot wrote:
Could someone explain me how relocating the buildbot on someone's
machine can be better for the project than migrating it to GitHub
Actions, build farm and package hoster ?
Don't get me wrong John and Rod, I very much appreciate your proposal
and investmen
This sounds like a good long term solution if it's free.
In the mean time I'm trying to at least get some debs uploaded to
http://linuxcnc.org/dists/ as soon as I get my ssh key sorted out.
JT
On 11/14/2022 2:37 PM, Jérémie Tarot wrote:
Le dim. 13 nov. 2022 à 18:39, Jérémie Tarot a écrit :
Ooops Python 3.9
Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au
On Tue, 15 Nov 2022 at 06:53, Rod Webster wrote:
> I think some of those features on github might incurr a cost. I'm sure we
> have more than 500 mb of code.
> You could also consid
I think some of those features on github might incurr a cost. I'm sure we
have more than 500 mb of code.
You could also consider this free openbuild servce
https://build.opensuse.org/
The etherlab guys use it to build debs as per the sticky I put in our
ethercat forum.
They have a connector from gi
On Mon, 14 Nov 2022 at 20:42, Jérémie Tarot wrote:
> Could someone explain me how relocating the buildbot on someone's
> machine can be better for the project than migrating it to GitHub
> Actions, build farm and package hoster ?
What would the user install instructions look like in that scenari
Le dim. 13 nov. 2022 à 18:39, Jérémie Tarot a écrit :
>
> Hello Andy,
>
Well, at least you're not alone to feel ignored sometimes...
Could someone explain me how relocating the buildbot on someone's
machine can be better for the project than migrating it to GitHub
Actions, build farm and package
On Mon, 14 Nov 2022 at 14:26, Steffen Möller wrote:
>
> If all the dependencies of the RTAI version are in Debian then I see no
> reason why only the RTAI version should be built.
The main dependency of the RTAI version is the RTAI kernel.
And that isn't in Debian.
--
atp
"A motorcycle is a bi
On Mon, 14 Nov 2022 at 14:53, Steffen Möller wrote:
> I am tempted to suggest that the LiveCD may run with bookworm. My line of
> thought is that when we release, bookworm will already be "frozen", such that
> the parts of Debian we are using are unlikely to see much of a change until
> the re
If someone can supply me with the credentials for
http://linuxcnc.org/dists/ I can build debs and upload them via sftp for
the ones that the current buildbot does not create.
JT
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
h
> Gesendet: Montag, 14. November 2022 um 10:28 Uhr
> Von: "andy pugh"
> An: "EMC developers"
> Betreff: Re: [Emc-developers] Plans for the USB sticks anyone?
>
> On Mon, 14 Nov 2022 at 08:52, Steffen Möller wrote:
>
> > b) the Live USB stick with LinuxCNC (and other useful or eye candy bits)
If all the dependencies of the RTAI version are in Debian then I see no reason
why only the RTAI version should be built.
Python3 is in all versions of Debian
https://tracker.debian.org/pkg/python3-defaults.
Best,
Steffen
> Gesendet: Montag, 14. November 2022 um 13:44 Uhr
> Von: "Rod Webster"
OK,
I wonder if we could organise a Google meet to discuss this before I go
back to Damien so I understand requirements. Also it would be good if
somebody could find out memory requirements for a buildbot.
I am GMT +10 so off to bed now.
Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifica
On Mon, 14 Nov 2022 at 10:18, Rod Webster wrote:
>
> Do we really need a Bullseye release?
I think so. I have the impression that the 2.9 release is already
considered "late" and our LiveCD is currently based on Buster (which
is out of date, though still supported as oldstable, I think?)
Bookw
Do we really need a Bullseye release?
If the Debian release freeze starts In January and we've always had to
build from source on Bullseye, aren't we going backwards and doubling the
maintenance?
Can it be done in a chroot environment? I thought that's what buildbots did.
I can ask nicely, but do
On Mon, 14 Nov 2022 at 08:52, Steffen Möller wrote:
> b) the Live USB stick with LinuxCNC (and other useful or eye candy bits) on it
>
> Is there any "production team" for b) already? I would like to discuss what
> is missing and/or should be updated.
It uses live-build and is controlled by:
ht
On Mon, 14 Nov 2022 at 08:34, Steffen Möller wrote:
> The primary challenge for the build bots may be to place the resulting .debs
> in a location from where they can then be installed with apt. I have no idea
> how the current system does it.
Semi-manually. There are some scripts:
https://git
Dear all,
I keep thinking that we are releasing two different things together
a) LinuxCNC
b) the Live USB stick with LinuxCNC (and other useful or eye candy bits) on it
Is there any "production team" for b) already? I would like to discuss what is
missing and/or should be updated.
Best,
Steffen
I have not yet fully understood what is happening but I like all the vibes you
are sending.
> Gesendet: Sonntag, 13. November 2022 um 22:50 Uhr
> Von: "John Thornton"
>
> I've been putzing around with buildbot and just now have it showing
> changes in a scratch github repo. Now to make it build
24 matches
Mail list logo
