#linuxcnc-devel Logs

Aug 28 2022

12:08 AM pere: seb_kuzminsky: looking
12:24 AM pere: seb_kuzminsky: look good to me. what is the next step?
12:49 AM pere: seb_kuzminsky: do you want me to upload it to debian?
03:20 AM hansu: Hi
03:21 AM hansu: @pere: I have a question, let me know when you have a minute ;-)
03:22 AM pere: hansu: hi. :)
03:23 AM hansu: Nice, that was fast :)
03:26 AM pere: I just sat down with my computer. :)
03:28 AM hansu: In components.adoc I include a file that is generated during doc build. So it makes no sense to have this as an empty file in the repository. So I just wanted to "touch" it. But in the depending stage it already complains about that missing file:
03:28 AM hansu: Depending ../docs/src/hal/components.adoc
03:28 AM hansu: sed: can't read ../docs/src/hal/components_gen.adoc: No such file or directory
03:28 AM hansu: I am sure there is a simple solution for that.
03:28 AM hansu: Here is the regarding target and my tries:
03:28 AM hansu: https://github.com/LinuxCNC/linuxcnc/blob/5e4ecd899f6ed4a65c9ed885d6f19a84f7a92585/docs/src/Submakefile#L367
03:28 AM linuxcnc-build: build #2325 of 1660.rip-buster-python3 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1660.rip-buster-python3/builds/2325 blamelist: Hans Unzner <hansunzner@gmail.com>
03:29 AM pere: I have not studied the dependency system, and have no idea how it work.
03:29 AM pere: apart from it generating some files that can mess up things later if I remove a file.
03:30 AM hansu: You mean especially the linuxcnc dependency system?
03:35 AM pere: yeah, the stuff in the makefiles.
03:35 AM pere: perhaps it can be overridden for a single file?
03:40 AM hansu: I have no idea in general of depending systems :(
03:40 AM hansu: how to do that?
03:41 AM pere: there is most likely some instructions to generate make style relations file: dependency and stuff it in files included in the makefile system at startup.
03:41 AM pere: the 'Depending' line printed during build is probably involved.
03:46 AM hansu: Ah ok I think I have found the location ... I thought it would be something which makes "make" kind of automatically O:-)
03:46 AM hansu: Thanks :-)
03:48 AM pere: hansu: did you think some more on how we want weblate to be set up?
03:49 AM hansu: Ähm what in detail to set up?
03:53 AM pere: the topics I know about is automatic rebasing, allowing everyone to add languages and the sync procedure into master.
03:59 AM pere: another topic that need to be resolved is the adoc style guide
04:00 AM hansu: Not really yet. But it's the first weekend since I don't know where I have a bit time for linuxcnc :)
04:01 AM hansu: Yeah the style guide would be good as well, I agree
04:03 AM pere: I do not understand where we go from the pull request about it.
04:07 AM hansu: Do we have a pull requet about that? I only found an issue.
04:13 AM pere: hansu: <URL: https://github.com/LinuxCNC/linuxcnc/pull/1530 > is the one on my mind.
04:15 AM hansu: Ok
04:15 AM pere: if we manage to merge one more pull request, we get all the open ones on one page. :)
04:19 AM hansu: Yeah I am currently working to fix up another :-)
04:19 AM hansu: But also will open a new one to close an issue...
04:20 AM hansu: Its nice that we are below 30 already :-)
04:24 AM pere: :)
04:25 AM pere: I updated <URL: https://github.com/LinuxCNC/linuxcnc/pull/1822 > and hope it is closer to acceptable now.
04:26 AM pere: hansu: who was it that would look into #581? Have not seen summary from last meeting, guess it might be written there.
04:27 AM hansu: I'll have a look later, but let me first finish my currrent topic ;-)
04:28 AM hansu: I could have been René, but I am not sure
04:31 AM pere: did you see the meeting summary? I could not find it.
04:33 AM hansu: https://docs.google.com/document/d/1aWMxBY8IbCYXFLFvjgqUXZ09inZp5u0r-pZcjeb2bWk/edit
04:33 AM pere: not posted to the list yet?
04:35 AM pere: hansu: rene-dev5 it was, indeed. Added him as a reviewer and commented in github to document this.
04:36 AM hansu: :+1:
04:42 AM pere: andypugh: do you know what is next after seb_kuzminsky built the dsc for a new debian upload?
04:42 AM pere: who uploads, who tags, who do what when?
04:51 AM linuxcnc-build: build #2727 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/2727 blamelist: Hans Unzner <hansunzner@gmail.com>
05:37 AM linuxcnc-build: build #2486 of 1650.rip-buster-rtpreempt-rpi4 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1650.rip-buster-rtpreempt-rpi4/builds/2486 blamelist: Hans Unzner <hansunzner@gmail.com>
05:37 AM linuxcnc-build: build #9125 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9125 blamelist: Hans Unzner <hansunzner@gmail.com>
07:58 AM pere: hansu: did you get your patch working?
08:39 AM hansu: yes, I was thinking a bit to complex
08:46 AM pere: got a chance to look at my patch?
09:01 AM hansu: Yes. But I just noticed that my build fails due to some po4a issues: "sed: can't read ../docs/src/de/hal/components_gen.adoc: No such file or directory" :'(
09:01 AM hansu: You are talking about #1822, right?
09:07 AM pere: yes
09:20 AM seb_kuzminsky: pere: yes, please upload
09:20 AM seb_kuzminsky: we don't tag the linuxcnc git repo for debian packages, only for linuxcnc releases
09:26 AM pere: seb_kuzminsky: ok, uploading. why do you not tag debian releases?
09:27 AM seb_kuzminsky: should we?
09:27 AM pere: I find tagging releases make life easier when comparing old releases. :)
09:27 AM seb_kuzminsky: the debian package "release schedule" has so far been totally independent of the linuxcnc release schedule
09:27 AM seb_kuzminsky: i've got the orig tarballs in a gbp repo here: https://github.com/SebKuzminsky/linuxcnc-gbp
09:28 AM seb_kuzminsky: we do tag linuxcnc releases, up until you and smoe pushed us to get our software into debian it simply wasn't an issue :-)
09:30 AM pere: :)
09:30 AM pere: what about preparing an upload to exerimental with the new binary packages?
09:34 AM pere: seb_kuzminsky: the upload is going now.
09:34 AM pere: seb_kuzminsky: any chance you can have a look at some of <URL: https://github.com/LinuxCNC/linuxcnc/pulls >?
09:35 AM pere: only three pull requests older than 2021 left to process. :)
09:35 AM seb_kuzminsky: thanks for the upload pere!! :-)
09:35 AM pere: and I suspect #525 is a subset of #581.
09:37 AM seb_kuzminsky: if we make new binary packages and upload to experimental, they'll sit in the NEW queue until the ftp masters have time to look at them... while we wait for that, we can still upload new versions of the current packages to unstable?
09:37 AM pere: yes
09:37 AM seb_kuzminsky: ok, great
09:37 AM pere: so the experimental upload is a separate 'branch', and should probably be a git branch.
09:38 AM pere: we just need to be careful about the version number we use.
09:38 AM seb_kuzminsky: hmm, yeah...
09:40 AM seb_kuzminsky: in linuxcnc.git, short-lived branches always get version numbers that sort as "less than the most recent linuxcnc release", so they never preempt debs from the long-lived release branches (incl master)
09:40 AM seb_kuzminsky: what's the norm for debian/experimental version numbers?
09:42 AM pere: it is a bit up to us, but I suspect we want X in unstable < Y in experimental < Z later in unstable.
09:43 AM pere: so people testing the packages in experimental get their installed packages replaced with the ones from unstable, when we upload there after the new packages clear NEW.
09:44 AM pere: seb_kuzminsky: please check out #1916 and #1963 to see if you agree with the approaches.
09:45 AM pere: would also be nice to know if #1822 is an improvement or a confusing derailing.
10:37 AM roguish[m]: ok, simple question........ if I want to run 2.9.pre on bullseye, do I have to build it and RIP ???
10:38 AM roguish[m]: or is there a deb available somewhere....
10:48 AM Tom_itx is now known as Tom_L
04:25 PM Tom_dev: pere, i don't have qemu-debootstrap
04:27 PM Tom_dev: https://wiki.debian.org/EmDebian/CrossDebootstrap
05:04 PM Tom_dev: pere, vmdb2, the successor to vmdebootstrap
05:05 PM Tom_dev: https://vmdb2.liw.fi/
05:06 PM Tom_dev: http://raspi.debian.net/ those are the images i started to look at when i hit the wall
05:07 PM Tom_dev: bare bones
06:07 PM linuxcnc-build: build #1967 of 4042.deb-buster-rtpreempt-rpi4 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4042.deb-buster-rtpreempt-rpi4/builds/1967 blamelist: Hans Unzner <hansunzner@gmail.com>
06:14 PM linuxcnc-build: build #2074 of 4041.deb-buster-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4041.deb-buster-rtpreempt-amd64/builds/2074 blamelist: Hans Unzner <hansunzner@gmail.com>
08:52 PM linuxcnc-build: build #2075 of 4041.deb-buster-rtpreempt-amd64 is complete: Failure [4failed shell_3 shell_4] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4041.deb-buster-rtpreempt-amd64/builds/2075 blamelist: Steffen Moeller <moeller@debian.org>, CMorley <chrisinnanaimo@hotmail.com>, Petter Reinholdtsen <pere@hungry.com>, Hans Unzner
08:52 PM linuxcnc-build: <hansunzner@gmail.com>
09:36 PM linuxcnc-build: build #1968 of 4042.deb-buster-rtpreempt-rpi4 is complete: Failure [4failed shell_3 shell_4] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4042.deb-buster-rtpreempt-rpi4/builds/1968 blamelist: Steffen Moeller <moeller@debian.org>, CMorley <chrisinnanaimo@hotmail.com>, Petter Reinholdtsen <pere@hungry.com>, Hans Unzner
09:36 PM linuxcnc-build: <hansunzner@gmail.com>
11:06 PM Tom_L: pere, http://tom-itx.no-ip.biz:81/~webpage/cnc/live-build/build.log
11:07 PM pere: thanks
11:09 PM pere: found this which seem relevant: W: skipping /usr/lib/live/build/binary_syslinux, foreign architecture(s).
11:36 PM pere: Tom_L: just found <URL: https://github.com/simonpoole1/raspbian-live-build/blob/master/Makefile > which contain some live-build options to build rpi images.
11:38 PM pere: Tom_L: I suspect the HDD_IMAGE_BUILD_OPTIONS options might be key to get the boot working.