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" <j...@gnipsel.com>
>
> I've been putzing around with buildbot and just now have it showing
> changes in a scratch github repo. Now to make it build a deb...

The .deb-building I suggest to copy from the ci.yml file 
(https://github.com/LinuxCNC/linuxcnc/blob/master/.github/workflows/ci.yml):

        eatmydata apt-get --yes --quiet build-dep --arch-only .
        eatmydata debuild -us -uc --build=any

The debuild (or dpkg-buildpackage) is executed from within the source tree.

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.

Best,
Steffen

>
> JT
>
> On 11/13/2022 3:43 PM, andy pugh wrote:
> > On Sun, 13 Nov 2022 at 21:15, Bari <bari00...@gmail.com> wrote:
> >
> >> Rod,
> >>
> >> Have  you had a chance to check with your web host on getting a free VM?
> >>
> >> How much VM do we need to host a new buildbot?
> >
> > The existing buildbot (should) work for Buster and previous OSes.
> >
> > And Debian will be building Bookworm + uspace
> >
> > So I think we would need
> >
> > Bullseye amd64 uspace
> > Bullseye amd64 RTAI
> > Bullseye arm64 uspace
> > Bookworm amd64 RTAI
> >
>
>
> _______________________________________________
> 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

Reply via email to