#linuxcnc-devel Logs

Sep 04 2022

09:25 AM linuxcnc-build: build #6975 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/6975 blamelist: Hans Unzner <hansunzner@gmail.com>
09:32 AM linuxcnc-build: build #7299 of 1400.rip-wheezy-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/7299 blamelist: Hans Unzner <hansunzner@gmail.com>
11:03 AM roguish[m]: pere: good morning here. probably good evening where you are.. The mail list announces a new linuxcnc version was accepted in Debian. 2.9.0~pre0+git20220903.c8c4c539b1-1. is there any where to see what changes are included in it? Also, how often are packages submitted to Debian? day? week? month? thanks.
11:03 AM roguish[m]: silopolis: please add in if you can. thanks.
11:04 AM pere: roguish[m]: hi.
11:04 AM pere: roguish[m]: I use git to see what went in. the c8c4c539b part is a git id
11:04 AM pere: git commit id.
11:05 AM pere: roguish[m]: you can find the git commit ids of uploads to debian/changelog
11:06 AM roguish[m]: pere: thanks. I just found this from last week posted here by JT. https://tracker.debian.org/pkg/linuxcnc
11:07 AM pere: roguish[m]: yeah, it is my go-to page for debian status. sadly the 'news' section is broken at the moment, but I have been told someone is trying to fix it. it is broken for all packages in debian.
11:08 AM pere: the autopkgtest scripts are still broken, but I fail to understand why.
11:09 AM roguish[m]: pere: the reason I am asking is I'm still working with Cmorley on some minor bugs in qtvcp python3 for bookworm. he made changes last weekend. But I did not see any update in synaptic yesterday. with that new release there should be. i'll check on my system in a few hours.
11:22 AM pere: roguish[m]: did you figure out how to get the list of commits uploadeD?
11:23 AM roguish[m]: no
11:23 AM roguish[m]: tried and failed.
11:24 AM roguish[m]: do you have a direct link?
11:24 AM roguish[m]: please
11:25 AM pere: roguish[m]: do you have a git clone of the linuxcnc repo?
11:27 AM roguish[m]: ah, no. can do one in a while.
11:28 AM roguish[m]: pere: hey, thanks. I have to go for a while. I'll be back later. THANKS
11:28 AM pere: ok
11:48 AM linuxcnc-build: build #2768 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/2768 blamelist: Hans Unzner <hansunzner@gmail.com>
11:48 AM linuxcnc-build: build #9166 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9166 blamelist: Hans Unzner <hansunzner@gmail.com>
12:05 PM pere: roguish[m]: I just discoverd that my proposal to find commit ids in debian/copyright is not going to work.
12:08 PM seb_kuzminsky: i think you meant debian/changelog, not d/copyright
12:09 PM seb_kuzminsky: there are three different things one might mean by "version number":
12:09 PM seb_kuzminsky: 1. the version of the linuxcnc software itself
12:09 PM seb_kuzminsky: 2. the version of the linuxcnc deb built by buildbot.linuxcnc.org
12:09 PM seb_kuzminsky: 3. the version of the linuxcnc deb in debian.org
12:11 PM seb_kuzminsky: 1 is made by `scripts/get-version-from-git`
12:11 PM seb_kuzminsky: 2 is 1, prefixed with an epoch number ("1:")
12:12 PM pere: seb_kuzminsky: I sure did.
12:12 PM seb_kuzminsky: 3 is a scheme made up by smoe, which ultimately also comes from our release tags (where get-version-from-git gets it), but with a date stamp and git commit id added (and NO epoch number)
12:15 PM seb_kuzminsky: so debian.org debs have the "upstream" linuxcnc.org commit id in the version number (so in d/changelog), but there's also a "debian patch" which i'm tracking in a git-buildpackage repo here: https://github.com/sebkuzminsky/linuxcnc-gbp
12:16 PM seb_kuzminsky: so from a debian.org deb you can go from the debian package version number to the tag in the gbp repo for the dsc, or you can go from the git sha in the package version number to the commit in the "upstream" linuxcnc repo
12:16 PM seb_kuzminsky: does that make sense?
12:17 PM seb_kuzminsky: it's confusing because linuxcnc isn't a "pure upstream" project, by which i mean that we have our own debian/ directory in our repo, and we use it extensively in our own parallel package distribution system
12:30 PM roguish[m]: seb_kuzminsky: thanks for adding in. I see the new release in Debian is in the 'unstable' according to the debian tracker. is there a repository for 'unstable'? if so, would you be so kind and share it? i have been looking and can't find it.... thanks.
12:37 PM seb_kuzminsky: "unstable" is kind of like a debian release, like "buster" or "bullseye"
12:38 PM seb_kuzminsky: unstable is where all/most new packages go, and eventually it'll be released as a new debian stable release
12:38 PM seb_kuzminsky: debs from unstable often won't install in older releases, because the older releases have older versions of the dependencies
12:39 PM seb_kuzminsky: for example, the linuxcnc debs in unstable won't unstall on buster
12:40 PM seb_kuzminsky: so you generally need to upgrade your distro to unstable (or, slightly less drastically, to "testing") to use the debian.org linuxcnc debs
12:40 PM seb_kuzminsky: some info here: https://www.debian.org/releases/
12:40 PM roguish[m]: seb_kuzminsky: I
12:43 PM roguish[m]: I'm running bookworm. found on the tracker the 'link' to get the release. it says use 'dget' but I don't even seem to be able to install that. I just added bullseye-backport to my repository list.
12:44 PM roguish[m]: I get the whole testing, stable, unstable thing.....
12:47 PM roguish[m]: ok is the unstable branch considered 'sid' ???
12:50 PM roguish[m]: installing devscripts now. think it contains dget
12:55 PM roguish[m]: and it did contain dget.
12:55 PM roguish[m]: downloaded from the link,
12:56 PM roguish[m]: now where the heck did the .deb go?
12:56 PM roguish[m]: or was that only the source?
12:58 PM pere: the packages are uploaded to unstable/sid and propagate automatically to testing (currently bookworm) if the automatic checks clear out in the time holding time requored in unstable.
12:59 PM pere: roguish[m]: you can find the binaries in debian/unstable by selecting a link on the left side of the tracking page.
01:00 PM roguish[m]: I FOUND IT. at least where to download it...
01:01 PM roguish[m]: yeah, what you said. had to go to the bottom of the page.....
01:01 PM roguish[m]: it's a learning thing
01:01 PM pere: seb_kuzminsky: the linuxcnc package relationships are rather complex, but I suspect it would be good to ensure linuxcnc.org releases and debian releases mix well with the git branch snapshots. the epoc used with snapshots and linuxcnc.org releases (?) make it hard.
01:02 PM pere: roguish[m]: the statement "Too young, only 0 of 5 days old" tell you how long the holding time is for linuxcnc in unstable. I expect all tests to clear this time, and the package to migrate in 5 days.
01:02 PM pere: if we could get a working autopkgtest in debian/tests/, the holding time would go down to 2 days.
01:02 PM seb_kuzminsky: yeah, the epoch breaks everything. i wish we could have kept the epoch in the debian.org packages, but that ship has sailed
01:03 PM seb_kuzminsky: the next best option is probably to drop the epoch from the buildbot debs, and just deal with the fallout of our version numbers moving backwards this one time :-/
01:03 PM pere: seb_kuzminsky: it is not sailed. it just need to be debated on debian-devel@ first.
01:08 PM roguish[m]: THANKS you guys. I know you'all are working it. i've made my own problem here by going to bookworm.
01:10 PM seb_kuzminsky: i think bookworm/testing is a reasonable distro to use if you want to play with the debian.org debs of linuxcnc
01:10 PM seb_kuzminsky: pere: interesting, thanks - i didn't know it was still an option
01:11 PM pere: seb_kuzminsky: existing packages can get a epoc when needed, but only after discussing it on debian-devel@.
01:12 PM roguish[m]: seb_kuzminsky: i'll figure out how to add the repo. probably ask JT. he's pretty savy
01:13 PM roguish[m]: seb_kuzminsky: also, Chris M had an interesting email in the devel section
01:13 PM roguish[m]: cmorley
02:00 PM roguish[m]: THANKS AGAIN...... got it all downloaded and installed........
06:06 PM linuxcnc-build: build #2111 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/2111 blamelist: Hans Unzner <hansunzner@gmail.com>
06:48 PM linuxcnc-build: build #2004 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/2004 blamelist: Hans Unzner <hansunzner@gmail.com>