I terms of additional eyeballs, the Debian package has brought Petter
and myself already before it was uploaded to the distribution :o) . I am
not aware of anyone else to have surfaced on github because it. From my
perspective, the package at the moment is still finding out how it can
use Debian's infrastructure (which also has build bots, many hardware
platforms).
Debian gives us an opportunity to think beyond the software that
constitutes LinuxCNC. FreeCAD comes to mind. Support for 3D mice. CAM.
ROS is in Debian. This seems like quite a nice basis for some story telling.
I do not see the LinuxCNC buildbot in conflict with the Debian-upload of
LinuxCNC. Ideally one would add the buildbot repository to the Debian
repository and then decides what version to install - and one could go
back to the earlier version with no hassle. So, I am with Ron. All the
releases and point-releases should be uploaded to the distribution.
Backports as we see fit.
Best,
Steffen
Am 05.09.2022 um 01:00 schrieb Rod Webster:
Buildbot is not really useful in terms of testing the Debian build until
such times as it can build it on the target OS platform. If that's a
requirement, then the focus should be on buildbot upgrades.
I think back and we had a stretch distro well before stretch was the stable
debian release. It's really been disappointing not to have a Bullseye image
as it has left many users floundering.
There should not be any more work after the next version is hived off
master. The debian release should coincide with the release of the next
production version.
Look at V 2.8, it's only been upgraded 3 times since its release to 2.8.3
now. That's all that should be going to Debian.
I do think however that syncing with the Debian release cycle might require
a different mindset... But I think that would be a good thing.
I think Andy is on the right track. Draw a line, focus on bug fixes and no
new features and get in step with Debian sooner than later so the workload
is not increased.
Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au
On Mon, 5 Sept 2022 at 08:34, Chris Morley <chrisinnana...@hotmail.com>
wrote:
I'm not sure you could say it adds _no_ value - the code is compiled and
tested by the buildbot.
Just not on the target you wish yet. - not perfect but still lots of
goodness.
I personally don't see how we could have a good release candidate anywhere
soon (depends what you mean soon of course - Andy implied weeks or the end
of the year recently)
I got basically no response on my discussion on it here on the maillist
and I see no action towards it.
We have run out of developers/developers time I think.
But I was more wondering if anyone had thought through the logistics of
dealing with another parallel release and potentially many(?) more users.
I may be making a big deal out of nothing but I thought I'd ask others
thoughts.
Chris
________________________________
From: Rod Webster <r...@vehiclemods.net.au>
Sent: September 4, 2022 9:27 PM
To: EMC developers <emc-developers@lists.sourceforge.net>
Subject: Re: [Emc-developers] Debian package - what is the future?
What has been overlooked so far is that there is still no buildbot version
for 2.9 on Bullseye so its increasingly difficult to deploy Linuxcnc on
newer hardware that requires say 5.10 kernel and higher. Buildbot is a long
way behind current kernel versions.
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
