Steffan thanks for clarifying. It's been a while since I've used stable (Bullseye) but I don't think there would be anything that prevents the current unstable (bookworm) packages from building on Bullseye. Maybe they could be uploaded to stable and see what happens? That would fill the gap on the stable build that currently exists. I don't think you could upload v 2.8 to oldstable because the copyright would not be compliant.
I am willing to lean on my hosting provider to see if he will agree to donate a server instance to act as a buildbot with a Debian focus building just the approved debian packages (eg. 2.9 and master). This would give a best practice enterprise class redundant hardware platform as a foundation. I'll let you know how I go during the week. Rod Webster *1300 896 832* +61 435 765 611 Vehicle Modifications Network www.vehiclemods.net.au On Sun, 13 Nov 2022 at 09:36, Steffen Möller <steffen_moel...@gmx.de> wrote: > > > > Gesendet: Samstag, 12. November 2022 um 23:37 Uhr > > Von: "Rod Webster" <r...@vehiclemods.net.au> > > An: "EMC developers" <emc-developers@lists.sourceforge.net> > > Betreff: Re: [Emc-developers] 2.9 Release Manager Required. > > > > John, I wonder if any buildbot could be based on the debian > > buildd infrastructure? > > The Debian Build Demons can be inspected on > https://buildd.debian.org/status/package.php?p=linuxcnc but only work > with the packages for unstable. So, we can use them but would not get the > insights for the older distributions that I learned LinuxCNC to be used a > lot with. > > > Maybe Steffen could help point the way? > > https://www.debian.org/devel/buildd/ > > What is it you want to know? > > > It kind of makes sense if the future is debian. > > The future for the automated builds? That could be a plan. Problems with > that is that to test if a package works on a distribution you need to > upload to that distribution. And if there then was a problem, you will only > find that after package was uploaded. For unstable that is not too bad, but > for backports to stable, the current buildbot situation may be preferable > prior to an upload. We have the Github autobuilds that help. > > We could upload backports of LinuxCNC to Debian stable and see how this > works. > > Best, > Steffen > > > > On Sun, 13 Nov 2022 at 02:14, John Thornton <j...@gnipsel.com> wrote: > > > > > Andy, > > > > > > Thanks for everything you have done. > > > > > > I'm like you and don't have the keys or know the process either... > > > > > > Now that I have unlimited Internet access I could setup a buildbot but > > > like you I lack the expertise or know of a tutorial. It might be > > > something for me to attempt in between adding features and fixing bugs > > > with mesact. > > > > > > JT > > > > > > On 11/11/2022 7:05 PM, andy pugh wrote: > > > > I can't do it. > > > > > > > > Previously the buildbot was integral to the process, but the buildbot > > > only > > > > builds for Buster- and I have no control over it. > > > > > > > > LinuxCNC is being built into Debian Bookworm, but I have no > involvement > > > in > > > > this process, and no access rights. > > > > > > > > Debian Bullseye would be the logical release platform for 2.9. I > could > > > set > > > > up my own build-farm (I have enough hardware) but that would be a > lot of > > > > work in an area in which I have no expertise. > > > > > > > > I have asked what the release platform should be, and there wasn't a > > > single > > > > reply. > > > > > > > > I will continue as a user and I will continue to offer my support on > > > > the forum and mailing lists, I am not going anywhere, but I am both > > > > ignorant of what the release policy should be and incapable of > > > performing > > > > the release manager role with the accesses and expertise that I have. > > > > > > > > > > > > > _______________________________________________ > > > 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 > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
