Re: [Emc-developers] Bookworm

2023-06-09 Thread Rod Webster
Well tomorrow is the day! Debian Bookworm will retire Bullseye and become
Debian stable!
This article says the first point release will be released in about a month.
https://lists.debian.org/debian-devel-announce/2023/06/msg0.html
It would be great if Linuxcnc v 2.9 is sitting in Debian testing waiting
for that point release
Please guys put that date in your diary.

Rod Webster
1300 896 832
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au

Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au


On Fri, 9 Jun 2023 at 08:26, Alec Ari via Emc-developers <
emc-developers@lists.sourceforge.net> wrote:

> Thank you!!
>
> Alec
>
> On Wednesday, June 7, 2023 at 11:38:14 PM UTC, Sebastian Kuzminsky <
> s...@highlab.com> wrote:
>
>
>
>
>
> On 6/7/23 14:29, Alec Ari via Emc-developers wrote:
>
> > 2.9 branch is still missing any recent Clang fixes, just throwing that
> out there as a reminder.
> >
> > https://github.com/LinuxCNC/linuxcnc/pull/2214/commits
>
>
> Too bad that was merged into master - our published policy is to merge
> fixes into the oldest active stable branch.
>
> <
> http://linuxcnc.org/docs/2.9/html/code/contributing-to-linuxcnc.html#_use_of_git_in_the_linuxcnc_project
> >
>
> I'll backport it to 2.9.
>
>
> --
> Sebastian Kuzminsky
>
>
>
> ___
> 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


Re: [Emc-developers] Bookworm

2023-06-08 Thread Alec Ari via Emc-developers
Thank you!!

Alec

On Wednesday, June 7, 2023 at 11:38:14 PM UTC, Sebastian Kuzminsky 
 wrote: 





On 6/7/23 14:29, Alec Ari via Emc-developers wrote:

> 2.9 branch is still missing any recent Clang fixes, just throwing that out 
> there as a reminder.
> 
> https://github.com/LinuxCNC/linuxcnc/pull/2214/commits


Too bad that was merged into master - our published policy is to merge 
fixes into the oldest active stable branch.



I'll backport it to 2.9.


-- 
Sebastian Kuzminsky



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


Re: [Emc-developers] Bookworm

2023-06-08 Thread Hans Unzner



Am 07.06.23 um 17:26 schrieb Sebastian Kuzminsky:

On 6/7/23 06:48, andy pugh wrote:

Is it a problem that we haven't actually released 2.9 and that it is
due to be in Bookworm, which is due to be released very soon indeed?


IMO it would have been better if we released 2.9.0 and got it into 
Bookworm, just because the version number 
(`2.9.0~pre1+git20230208.f1270d6ed7`) looks a bit goofy and 
unprofessional.  Even just `2.9.0~pre2` would have been preferable.


Based on my reading of 
, now that 
Bookworm is in "Full Freeze" we should not upload a new upstream 
release, so i think we're stuck with the big goofy version.


Any bugs we want to fix in the debian.org package will need to be 
fixed in that version of our source code - i assume we'll fix it in 
the "real" 2.9 and cherrypick/backport the fix to a "bookworm" branch 
in our gbp repo (

Re: [Emc-developers] Bookworm

2023-06-07 Thread andy pugh
On Wed, 7 Jun 2023 at 23:59, Chad Woitas  wrote:

> Currently M5 by default stops spindle 0, but not any others.

>   1.  Stop all of them  https://github.com/LinuxCNC/linuxcnc/pull/2438
>   2.  Allow for enabling a default spindle or -1 for all spindles. 
> https://github.com/LinuxCNC/linuxcnc/pull/2437
>
> I’d prefer the second option as more configuration, with safe defaults is 
> nice. I’m not opposed to the first option

I prefer the first option, and I am fairly sure that is what I
intended when I first included multiple spindles.

(In fact I had been planning to make the change, but lost track of the
issue amongst several others)

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


Re: [Emc-developers] Bookworm

2023-06-07 Thread Sebastian Kuzminsky

On 6/7/23 14:29, Alec Ari via Emc-developers wrote:

2.9 branch is still missing any recent Clang fixes, just throwing that out 
there as a reminder.

https://github.com/LinuxCNC/linuxcnc/pull/2214/commits


Too bad that was merged into master - our published policy is to merge 
fixes into the oldest active stable branch.




I'll backport it to 2.9.


--
Sebastian Kuzminsky


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


Re: [Emc-developers] Bookworm

2023-06-07 Thread Chad Woitas

Another candidate to be included:

Currently M5 by default stops spindle 0, but not any others.

I have two PR’s for two different options:

  1.  Stop all of them  https://github.com/LinuxCNC/linuxcnc/pull/2438
  2.  Allow for enabling a default spindle or -1 for all spindles. 
https://github.com/LinuxCNC/linuxcnc/pull/2437

I’d prefer the second option as more configuration, with safe defaults is nice. 
I’m not opposed to the first option

The current code almost caused mayhem.

  *   This gantry has a 5 axis spindle, and hotwire cutter on side of the 
gantry on a Y axis
  *   A planer on the back side of the gantry on a separate Y axis
  *   Program runs 1 tool after the other, but didn’t stop the hotwire or 
planer as they’re mapped to spindle inputs.
  *   On the other hand maybe this is too many tools on one machine

Chad Woitas | Automation Developer
[cid:image001.png@01D7F7D7.6E1AFA10]

RMD Engineering Inc.<http://www.rmd-engineering.com/> | Saskatoon Machine Works 
Ltd.<http://www.smw.sk.ca/> | Scientific Instrumentation 
Ltd.<http://www.sil.sk.ca/>


From: Rod Webster<mailto:r...@vehiclemods.net.au>
Sent: June 7, 2023 1:39 PM
To: EMC developers<mailto:emc-developers@lists.sourceforge.net>
Subject: Re: [Emc-developers] Bookworm

Bookworm will be released in 2 days time on 10 June.
I am waiting until then to finalise the Bookworm URL in my
getting-linuxcnc docs. https://github.com/LinuxCNC/linuxcnc/pull/2496
Hopefully, one of you guys can push it soon after.
Now there is a buildbot building the Bookworm debs, perhaps we could
use that doc to instruct the user (including me) how to configure
sources.list to give preference to that version over the Debian
package.
I don't know how to do that but if one of you guys could tell me how
to do it, I'll include it.

I might be wrong but I thought Stefan indicated Debian might be able
to be sweet talked into including 2.9 after the release.

Rod Webster
1300 896 832
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au<http://www.vehiclemods.net.au>

Rod Webster
1300 896 832
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au<http://www.vehiclemods.net.au>


On Thu, 8 Jun 2023 at 01:27, Sebastian Kuzminsky  wrote:
>
> On 6/7/23 06:48, andy pugh wrote:
> > Is it a problem that we haven't actually released 2.9 and that it is
> > due to be in Bookworm, which is due to be released very soon indeed?
>
> IMO it would have been better if we released 2.9.0 and got it into
> Bookworm, just because the version number
> (`2.9.0~pre1+git20230208.f1270d6ed7`) looks a bit goofy and
> unprofessional.  Even just `2.9.0~pre2` would have been preferable.
>
> Based on my reading of
> <https://release.debian.org/testing/freeze_policy.html>, now that
> Bookworm is in "Full Freeze" we should not upload a new upstream
> release, so i think we're stuck with the big goofy version.
>
> Any bugs we want to fix in the debian.org package will need to be fixed
> in that version of our source code - i assume we'll fix it in the "real"
> 2.9 and cherrypick/backport the fix to a "bookworm" branch in our gbp
> repo (<https://github.com/LinuxCNC/linuxcnc-gbp).
>
> I think that's ok.  ¯\_(ツ)_/¯
>
>
> --
> Sebastian Kuzminsky
>
>
> ___
> 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


Re: [Emc-developers] Bookworm

2023-06-07 Thread Alec Ari via Emc-developers
2.9 branch is still missing any recent Clang fixes, just throwing that out 
there as a reminder.

https://github.com/LinuxCNC/linuxcnc/pull/2214/commits

Alec


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


Re: [Emc-developers] Bookworm

2023-06-07 Thread Rod Webster
Bookworm will be released in 2 days time on 10 June.
I am waiting until then to finalise the Bookworm URL in my
getting-linuxcnc docs. https://github.com/LinuxCNC/linuxcnc/pull/2496
Hopefully, one of you guys can push it soon after.
Now there is a buildbot building the Bookworm debs, perhaps we could
use that doc to instruct the user (including me) how to configure
sources.list to give preference to that version over the Debian
package.
I don't know how to do that but if one of you guys could tell me how
to do it, I'll include it.

I might be wrong but I thought Stefan indicated Debian might be able
to be sweet talked into including 2.9 after the release.

Rod Webster
1300 896 832
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au

Rod Webster
1300 896 832
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au


On Thu, 8 Jun 2023 at 01:27, Sebastian Kuzminsky  wrote:
>
> On 6/7/23 06:48, andy pugh wrote:
> > Is it a problem that we haven't actually released 2.9 and that it is
> > due to be in Bookworm, which is due to be released very soon indeed?
>
> IMO it would have been better if we released 2.9.0 and got it into
> Bookworm, just because the version number
> (`2.9.0~pre1+git20230208.f1270d6ed7`) looks a bit goofy and
> unprofessional.  Even just `2.9.0~pre2` would have been preferable.
>
> Based on my reading of
> , now that
> Bookworm is in "Full Freeze" we should not upload a new upstream
> release, so i think we're stuck with the big goofy version.
>
> Any bugs we want to fix in the debian.org package will need to be fixed
> in that version of our source code - i assume we'll fix it in the "real"
> 2.9 and cherrypick/backport the fix to a "bookworm" branch in our gbp
> repo (
> I think that's ok.  ¯\_(ツ)_/¯
>
>
> --
> Sebastian Kuzminsky
>
>
> ___
> 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


Re: [Emc-developers] Bookworm

2023-06-07 Thread Sebastian Kuzminsky

On 6/7/23 06:48, andy pugh wrote:

Is it a problem that we haven't actually released 2.9 and that it is
due to be in Bookworm, which is due to be released very soon indeed?


IMO it would have been better if we released 2.9.0 and got it into 
Bookworm, just because the version number 
(`2.9.0~pre1+git20230208.f1270d6ed7`) looks a bit goofy and 
unprofessional.  Even just `2.9.0~pre2` would have been preferable.


Based on my reading of 
, now that 
Bookworm is in "Full Freeze" we should not upload a new upstream 
release, so i think we're stuck with the big goofy version.


Any bugs we want to fix in the debian.org package will need to be fixed 
in that version of our source code - i assume we'll fix it in the "real" 
2.9 and cherrypick/backport the fix to a "bookworm" branch in our gbp 
repo (

Re: [Emc-developers] Bookworm

2023-06-07 Thread Hans Unzner
Yeah we really should build actual deb packages from the current 2.9 branch
and upload them to debian. Even though not all "2.9 must fix" issues are
resolved, the current 2.9 is much better than that what is currently in
debian. Much better in this case means that the majority of sample configs
resp. GUIs are running which is not the case with the current version of
LinuxCNC in debian.

Am Mittwoch, 7. Juni 2023 schrieb andy pugh :
> Is it a problem that we haven't actually released 2.9 and that it is
> due to be in Bookworm, which is due to be released very soon indeed?
>
> --
> atp
> "A motorcycle is a bicycle with a pandemonium attachment and is
> designed for the especial use of mechanical geniuses, daredevils and
> lunatics."
> — George Fitch, Atlanta Constitution Newspaper, 1912
>
>
> ___
> 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] Bookworm

2023-06-07 Thread andy pugh
Is it a problem that we haven't actually released 2.9 and that it is
due to be in Bookworm, which is due to be released very soon indeed?

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers


[Emc-developers] Bookworm Release Anounced

2023-04-29 Thread Rod Webster
Just a heads up that Debian Bookworm will be released on June 10
Bookworm Release Candidate 2 was released on April 28
https://www.debian.org/devel/debian-installer/

It would be really nice if we could have a V 2.9 release by June 10 so
we can sync our packages with Debian.

Rod Webster


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers