Marius, I know your preference for the standard ISO. If you reread my suggestions you will see I was specifically referring to 2.8 just for you that might have solved your docs issue via a workaround.
Gene asked about Bookworm and I addressed some issues for him. But despite you sticking with linuxcnc 2.8 until it is depreciated, the operating system it's distributed on is well and truly depreciated.. There are many people who are forced to upgrade to a later OS due to lack of driver support or because they want features that are not available in 2.8. Whilst 2.9 is now supported in the ISO, that was not always the case. It was quite some time before 2.9/master became available on Buster following the move to Python 3.x. Some of us responded to that by abandoning the Buster ISO. Rod Webster *1300 896 832* +61 435 765 611 Vehicle Modifications Network www.vehiclemods.net.au On Mon, 14 Aug 2023 at 18:27, Marius <mar...@mastercut.co.za> wrote: > @Rod > > Most non-guru users make use of the ISO and that is still on buster. The > new process using bookworm requires a lot of intervention that is not > easy for most folks to do. The simplest way is using the current ISO and > then use Synaptic Package Manager to upgrade to master branch. I think > most users will stay with that until it is deprecated. > > On 2023/08/13 19:39, Rod Webster wrote: > > @marius, There is a new buildbot Seb has built > http://buildbot2.highlab.com/ > > One solution would be to download the docs you want and install with sudo > > dpkg -i > > Alternatively, you could edit your sources to use them with apt. This is > > described for Bookworm and 2.9 in the docs under heading #9 here. > > http://linuxcnc.org/docs/2.9/html/getting-started/getting-linuxcnc.html > > If you wanted to get for say buster and master, you would need to > change > > the echo statement to suit. I am not sure how the linuxcnc 2.8 iso does > > this, you might need to review and update files in /etc/apt/sources.list > > and /etc/apt/sources.list.d/ > > > > @gene, if you want to move forward to bookworm, the process is described > in > > the 2.9 docs per the second link > > The Raspberry pi is a bit of a problem as there is no new buildbot for > it. > > Today, you would be better off using 64 bit arm64 instead of armhf (on a > pi > > 4b). Installing on bookworm is also described in the docs above. The gpio > > was broken due to depreciation of the non standard method we used. I > think > > Andy has fixed that recently pending a new driver that uses the correct > > method. But there is no alternative but to build from source on the pi to > > obtain the latest versions as the bookworm image is locked by debian > > policies at an earlier version. I was hoping that the new buildbot would > > build Raspberry images using a cross compiler on AMD64 hardware as per > some > > links I shared on Issue #2349 > > https://github.com/LinuxCNC/linuxcnc/issues/2349 Currently the old > buildbot > > uses a pi to build everything which is not desirable moving forward. > > > > Rod Webster > > *1300 896 832* > > +61 435 765 611 > > Vehicle Modifications Network > > www.vehiclemods.net.au > > > > > > On Sun, 13 Aug 2023 at 23:05, gene heskett <ghesk...@shentel.net> wrote: > > > >> On 8/13/23 05:17, Steffen Mller wrote: > >>> Hello, > >>> > >>>> Gesendet: Freitag, 11. August 2023 um 09:38 Uhr > >>>> Von: "Marius" <mar...@mastercut.co.za> > >>>> > >>>> There seem to be a problem with the DOCS on the server. Upgrading is > not > >>>> possible if the docs are included as they just will not download at > all > >>>> or take many hours if they do download. > >>>> > >>>> I reported this before but it seems to be still ongoing issue. > >>> I'm a bit puzzled by the issue you've mentioned regarding the DOCS on > >> the server. I thought it might be connected to the online documentation > on > >> the web server, but it seems that part is working fine for the sections > I > >> checked. > >>> Could you provide more details about the problem? Is it related to a > >> Debian documentation package? If you have specific steps or commands to > >> recreate the error, please share them. > >>> If someone else on this list can already reproduce this issue, please > >> step forward :) > >>> Sorry for the delay in getting back to you. We're here to help, so the > >> more information you can give us, the better. With more details, I'm > sure > >> someone with expertise will come forward to address the issue. > >>> Many thanks! > >>> Steffen > >>> > >> I don't have the expertise, but I can report results. > >> > >> Because I have no interest in languages I don't speak and there is no > >> way to build just the English docs. I am locked out of any upgrades as > >> I'm running buster, I cannot even build linuxcnc on bullseye because > >> bullseye's python is too new. This has been reported several times on > >> this list. > >> > >> I normally, since I'm not a for profit shop, run master from the > >> buildbot, as a hobbiest I can afford to bleed occasionally, but the > >> buster in-release file has been removed from the buildbot for armhf, > >> disabling my access to the buildbot's output for buster master. > >> > >> So I'm back to running some scripts here that duplicate the buildbot, > >> including building install-able debs. But something has gone wrong and > >> the installed debs, which run just fine, now break apt, and the only > >> solution is to fix-broken, which will remove the debs my pi just spent > >> 40 minutes building and 3 minutes installing. > >> > >> I can after that, probably install bookworm and then install linuxcnc, > >> v2.9.0 from the bookworm repo's. > >> > >> But that is not the point Steffan, because I'm not a for profit user, > >> I've been playing canary in the coal mine, running master for almost 20 > >> years, reporting unseen bugs as I've encountered them, my contribution > >> to the stability of linuxcnc. These guy's are good, I've only reported > >> a failure twice in that time frame. OTOH my test is just to see if it > >> runs from a shell so I don't catch everything. > >> > >> So at present, I can't build the docs because my machine does not have > >> the resources installed to build all the languages that have been added > >> in the last 2 years. I could probably install them if I had a list of > >> what's needed. But its also time to install bookworm. A different kettle > >> of fish entirely. > >> > >> Lets assume I install bookworm, first on my wintel stuff. But is the > >> plan to lock up the buildbot now that linuxcnc is officially in debian? > >> IDK. If that is the case, my canary just died. > >> > >> And because the buster in-release file has been deleted, synaptic nor > >> apt will touch the buildbots output for armhf. > >> > >> I can still do a git pull and build linuxcnc, install and run it, but > >> that breaks apt, and now tha docs are locked away. So what do I do to > >> restore my access to the docs? > >> > >> I should also point out that my 3 wintel busters running on old Dell's > >> are still getting all 4 master updates from the buildbot as of this > >> morning, only the armhf build seems to be affected. > >> > >> Thank you, take care & stay well, Steffan. > >> > >>> > >>> _______________________________________________ > >>> Emc-developers mailing list > >>> Emc-developers@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/emc-developers > >>> . > >> Cheers, Gene Heskett. > >> -- > >> "There are four boxes to be used in defense of liberty: > >> soap, ballot, jury, and ammo. Please use in that order." > >> -Ed Howdershelt (Author, 1940) > >> If we desire respect for the law, we must first make the law > respectable. > >> - Louis D. Brandeis > >> Genes Web page <http://geneslinuxbox.net:6309/> > >> > >> > >> > >> _______________________________________________ > >> 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
