#linuxcnc-devel Logs

Oct 02 2021

10:15 AM -!- #linuxcnc-devel mode set to +v by ChanServ
10:21 AM -!- #linuxcnc-devel mode set to +v by ChanServ
10:55 AM Eric_ is now known as unterhausen
12:47 PM seb_kuzminsky: Tom_L: that's for wheezy and forward, and precise and forward
12:48 PM seb_kuzminsky: debs on wlo now
01:08 PM Tom_L: ahh ok thanks
01:21 PM seb_kuzminsky: we decided to do the Debian unstable upload a different way, that lets us still keep supporting old distros for now
01:21 PM Tom_L: is that on github?
01:22 PM seb_kuzminsky: the mesaflash 3.4.0 release is on github here: https://github.com/LinuxCNC/mesaflash/releases/tag/release%2F3.4.0
01:22 PM Tom_L: thanks
01:22 PM seb_kuzminsky: our debs are on wlo as usual (http://www.linuxcnc.org/dists/)
01:25 PM Tom_L: wasn't sure what wlo was :)
01:45 PM JT-Shop: seb_kuzminsky, is mesaflash master the same as the latest release?
02:09 PM JT-Shop: ah that is master
04:33 PM -!- #linuxcnc-devel mode set to +v by ChanServ
06:10 PM seb_kuzminsky: JT-Shop: sounds like you figured it out but just to confirm, yes, the mesaflash `master` branch is where we've been making 3.4 pre-releases from, and it's where i made the 3.4.0 release just now
06:10 PM JT-Shop: thank seb_kuzminsky
06:10 PM JT-Shop: s
06:10 PM JT-Shop: thanks even
06:11 PM seb_kuzminsky: given how development on mesaflash works, i think we probably don't need to worry about maintaining old stable release branches at this point - i think more of a "rolling release" model would be appropriate, with releases made from master like we have been
06:11 PM JT-Shop: I'm so glad we have mesaflash in our repository now
06:11 PM JT-Shop: I agree
06:12 PM Tom_L: does that github mesaflash build as 64bit only?
06:12 PM JT-Shop: you can build either
06:12 PM seb_kuzminsky: we build both i386 (32-bin) and amd64 (64-bit) debs
06:13 PM JT-Shop: I used to build both an include them with the 7i96 configuration tool but now I just check to see if they have it installed
06:13 PM seb_kuzminsky: i don't have the automation set up to build arm binaries, but it'd probably make sense to add that
06:14 PM Tom_L: i just tried compiling it with make and got a bunch of 64bit errors
06:14 PM Tom_L: didn't know if i need to change something there
06:14 PM seb_kuzminsky: hmm, can you paste the errors somewhere?
06:14 PM JT-Shop: iirc I built mesaflash on my rpi4 32 bit
06:14 PM Tom_L: lemme boot in linux
06:14 PM JT-Shop: chow time here
06:14 PM seb_kuzminsky: Tom_L: were you building it on something other than linux?
06:15 PM JT-Shop: see you guys later
06:15 PM seb_kuzminsky: see you later :-)
06:15 PM Tom_L: iirc it's debian buster
06:15 PM Tom_L: either buster or stretch
06:15 PM seb_kuzminsky: ah, that should work
06:15 PM seb_kuzminsky: both should work
06:15 PM seb_kuzminsky: i just published mesaflash debs for everything between wheezy and sid, inclusive
06:18 PM Tom_L: i just ran it from terminal and it says mesaflash version 3.4.0-pre1
06:18 PM Tom_L: so maybe it built?
06:18 PM seb_kuzminsky: maybe, or maybe you have the debian package installed? what does `which mesaflash` say?
06:19 PM Tom_L: /usr/bin/mesaflash
06:19 PM seb_kuzminsky: ok, so that's the one from the deb
06:19 PM seb_kuzminsky: the old 3.4.0~pre1 deb, not the new 3.4.0 deb
06:19 PM Tom_L: make said there's nothing to do as well
06:19 PM Tom_L: i'll try it again
06:19 PM seb_kuzminsky: sounds like make thinks it succeeded at building it
06:20 PM Tom_L: maybe since the old one is there?
06:20 PM seb_kuzminsky: what happens if you run `./mesaflash` in the build directory?
06:20 PM Tom_L: 3.4.0
06:20 PM Tom_L: so it's not in the bin directory
06:21 PM Tom_L: but it must have built
06:23 PM seb_kuzminsky: sounds like it build successfully, that's good
06:23 PM seb_kuzminsky: the build by default doesn't install it anywhere
06:23 PM Tom_L: ok
06:24 PM seb_kuzminsky: if you want the new version installed in /usr/bin so it's accessible from anywhere by anyone on your computer, the easiest way is to install the debian package from www.linuxcnc.org
06:24 PM Tom_L: yeah
06:24 PM seb_kuzminsky: which is probably where you got the old 3.4.0~pre1 version that's there now, i'm guessing?
06:24 PM Tom_L: i'm sure it was
06:24 PM seb_kuzminsky: you should be able to run `apt-get update` and then `apt-get install mesaflash`
06:24 PM Tom_L: it's a test pc so i'm sure i installed the debs
06:25 PM Tom_L: says newest version is installed already
06:25 PM Tom_L: (pre1)
06:26 PM Tom_L: (pre1-1)
06:27 PM seb_kuzminsky: even after `apt-get update`? hmm
06:27 PM seb_kuzminsky: maybe that computer doesn't have the wlo archive listed in its apt sources list for some reason?
06:28 PM -!- #linuxcnc-devel mode set to +v by ChanServ
06:28 PM Tom_dev: http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
06:28 PM Tom_L: that's probably it
06:29 PM seb_kuzminsky: it should say something about fetching frmo linuxcnc.org
06:30 PM Tom_dev: Get:3 http://ftp.us.debian.org/debian buster InRelease [122 kB]
06:30 PM Tom_dev: Hit:4 http://buildbot.linuxcnc.org buster InRelease
06:30 PM Tom_dev: Hit:2 https://s3.amazonaws.com/apt.matrix.one/raspbian buster InRelease
06:30 PM Tom_dev: Get:5 https://packages.riot.im/debian buster InRelease [2,911 B]
06:30 PM Tom_dev: Err:5 https://packages.riot.im/debian buster InRelease
06:30 PM Tom_dev: The following signatures were invalid: EXPKEYSIG C2850B265AC085BD riot.im packages <packages@riot.im>
06:31 PM seb_kuzminsky: it's got the buildbot, but it's missing the main wlo debs
06:31 PM Tom_dev: it's not a big deal on this pc. it's just for test anyway
06:31 PM seb_kuzminsky: if you want to add those, create a new file named `/etc/apt/sources.list.d/linuxcnc.list`, containing this line:
06:32 PM seb_kuzminsky: deb http://linuxcnc.org buster base
06:34 PM Tom_dev: ok
06:36 PM Tom_dev: GPG error: http://linuxcnc.org buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3CB9FD148F374FEF
06:44 PM seb_kuzminsky: oh, right!
06:45 PM Tom_dev: how do i add that??
06:45 PM seb_kuzminsky: to use the deb archive on linuxcnc.org you have to tell apt the key
06:45 PM seb_kuzminsky: try this:
06:45 PM Tom_dev: apt-key add?
06:45 PM seb_kuzminsky: sudo apt-key adv --keyserver keys.openpgp.org --recv-key 3CB9FD148F374FEF
06:46 PM Tom_dev: i think it added 1
06:46 PM Tom_dev: same error
06:47 PM Tom_dev: NO_PUBKEY 3CB9FD148F374FEF
06:47 PM seb_kuzminsky: hmm, what was the output from the apt-key command i wrote above?
06:48 PM Tom_dev: Executing: /tmp/apt-key-gpghome.MJGcOBMavo/gpg.1.sh --keyserver keys.openpgp.org --recv-key 3CB9FD148F374FEF
06:48 PM Tom_dev: gpg: key 3CB9FD148F374FEF: new key but contains no user ID - skipped
06:48 PM Tom_dev: gpg: Total number processed: 1
06:48 PM Tom_dev: gpg: w/o user IDs: 1
06:48 PM seb_kuzminsky: hmm, skipped, that's not good
06:48 PM Tom_dev: heh
06:48 PM seb_kuzminsky: try using the ubuntu keyserver instead:
06:48 PM seb_kuzminsky: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-key 3CB9FD148F374FEF
06:49 PM Tom_dev: imported
06:49 PM seb_kuzminsky: the openpgp key infrastructure is in some wierd stat of flux, and pretty flaky these days
06:50 PM Tom_dev: E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
06:50 PM Tom_dev: N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
06:50 PM Tom_dev: now what about that error?
06:50 PM seb_kuzminsky: hmm, there's an apt flag for that i think, let me look...
06:50 PM Tom_dev: i appreciate your help
06:51 PM Tom_dev: i can stumble thru a few things...
06:51 PM seb_kuzminsky: yeah, try this:
06:51 PM seb_kuzminsky: sudo apt-get update --allow-releaseinfo-change
06:52 PM Tom_dev: thanks
06:52 PM Tom_dev: that seemed to work
06:52 PM seb_kuzminsky: it's pretty unfortunate that the debian "aging" process introduces this hickup with old distros
06:53 PM Tom_dev: seems some process changes nearly every release
06:54 PM Tom_dev: and was able to install mesaflash
06:54 PM Tom_dev: thanks
06:54 PM Tom_dev: Mesaflash version 3.4.0
08:12 PM seb_kuzminsky: great!
08:12 PM Tom_L: :)
08:13 PM roguish[m]1: seb_kuzminsky: it's very nice to see you back, if not but for a visit
08:52 PM seb_kuzminsky: i'm back (temporarily?) to work with Steffen Möller from debian.org to get linuxcnc and mesaflash into the real debian. This will make our software super accessible to lots more people.
09:57 PM Tom_L: that's great