**** BEGIN LOGGING AT Fri Oct 30 02:59:57 2020
Oct 30 06:40:16 <mihai> morning
Oct 30 07:41:37 <LetoThe2nd> yo dudX
Oct 30 07:43:07 <mckoan> good morning
Oct 30 07:55:11 <LetoThe2nd> the final good morning coffee in virtual dublin is taking place at https://www.twitch.tv/theyoctojester in 5 minutes!
Oct 30 08:54:44 <mk4953> Hello again.
Oct 30 08:55:01 <mk4953> My question is about sofware configuration
Oct 30 08:57:12 <mk4953> I have an assignment where we have to show how to disable software
Oct 30 09:01:10 <LetoThe2nd> and disabling software means?
Oct 30 09:03:29 <LetoThe2nd> mk4953: just not including it in the resulting image?
Oct 30 09:07:45 <mk4953> 2 sec
Oct 30 09:08:29 <mk4953> This is question from my assignment
Oct 30 09:08:33 <mk4953> "Describe how to add "standard" software, ie. sw, which is part of the Yocto Project"
Oct 30 09:09:18 <mk4953> And the other
Oct 30 09:09:20 <mk4953> "Describe how to exclude software"
Oct 30 09:09:47 <LetoThe2nd> the answer is always the same. "create a custom image that includes what you wnat"
Oct 30 09:10:15 <mk4953> Hmm
Oct 30 09:11:02 <LetoThe2nd> see me doing it here: https://youtu.be/nqHylLP2NmA
Oct 30 09:11:13 <LetoThe2nd> it is really exactly that.
Oct 30 09:12:36 <mk4953> Ok. så i need to see that again (i have seen most of your videos. :))
Oct 30 09:12:55 <mk4953> It makes sense :)
Oct 30 09:13:07 <mk4953> Very useful..
Oct 30 09:14:05 <mk4953> But my problem is that i cannot find issues very quickly i looking for always.
Oct 30 09:14:40 <mk4953> Is this ok, if i ask question from video, if you have time later?
Oct 30 09:16:50 <LetoThe2nd> just ask here, there is always somebody around. and creating a custom image is no magic at all. if you prefer written words/slides, find some good stuff here: https://docs.google.com/presentation/d/1wfuA_SrPEH-kFLhTgkp2VPD6bsULAMJ84ODtnKSarbY/edit#slide=id.p4
Oct 30 10:17:33 <mihai> is anyone else seeing issues with read only permissions on files under workdir and "permission denied" when cleaning?
Oct 30 10:18:51 <mihai> might be related to using go.bbclass, not sure
Oct 30 10:28:57 <RobertBerger> @ j
Oct 30 10:29:03 <RobertBerger> @mihai: yes ;)
Oct 30 10:29:16 <RobertBerger> @mihai: if you use master this goes away
Oct 30 10:29:38 <RobertBerger> @mihai: it's related to pseudo
Oct 30 10:32:10 <mihai> oh ok, thanks, RobertBerger
Oct 30 10:35:17 <LetoThe2nd> hum, i would rather said, it is being reduced probably. it can be triggered by reuse of tmp, and wiping tmp before the build substantially seems to reduce the problem, but it is not completely solved. however as RobertBerger said, on current master the behaviour changes to abort if corruption is detected, and includes information in how to aid debugging.
Oct 30 11:23:41 <dl9pf> darknighte: ping
Oct 30 11:25:43 <dl9pf> bluelightning: ping
Oct 30 11:25:50 <dl9pf> are you up ?
Oct 30 11:26:05 <bluelightning> dl9pf: hey - I am indeed
Oct 30 11:26:17 <dl9pf> cool
Oct 30 12:02:55 <eduardas> hello, I get No rule to make target 'arch/arm64/boot/dts/ipq6018-cp01-c1.dtb' while compiling latest kernel 5.10-rc1 and having set KERNEL_DEVICETREE = "ipq6018-cp01-c1.dtb" in my machine config
Oct 30 12:04:04 <eduardas> the path is wrong since it should be /arch/arm64/boot/dts/qcom/ipq6018-cp01-c1.dtb
Oct 30 12:04:14 <eduardas> the qcom part is missing in path
Oct 30 12:04:45 <eduardas> can anyone explain why this happens?
Oct 30 12:05:11 <eduardas> this is on yocto 3.2 gatesgarth
Oct 30 12:11:36 <RP> eduardas: very hard to speculate without looking at what is going on :/
Oct 30 12:12:16 <zeddii> I'm still a few days away from shaking out day0 issues with 5.10 myself, ELCe sort of sucked up all my time.
Oct 30 12:13:40 <zeddii> I did check the the devicetree .bbclass doesn't care about the path, it just uses the base '<foo>.dtb', so that issue is within the kernel build (some new input requirement, etc).
Oct 30 12:23:04 <eduardas> RP: setting KERNEL_DEVICETREE = "qcom/ipq6018-cp01-c1.dtb" seems to solve it, but I have never seen this happen before
Oct 30 12:46:15 <eduardas> can I configure a 32-bit u-boot build, but a 64-bit kernel/userpsace build for same machine?
Oct 30 13:27:07 <sgw> RP, JPEW: I just send WIP RFC for the qmp work.  I am stuck with the monitor_dump not running inside the ssh cmd processing correctly.
Oct 30 13:27:23 <sgw> maybe some other eyes on it, it's close.
Oct 30 13:30:08 <RP> sgw: at a quick glance that code looks horribly racy with the socket number :/
Oct 30 13:31:03 <RP> sgw: hardcoded 4444 too? :/
Oct 30 13:34:27 <sgw> RP: the hardcoded 4444 was for the human interface for test only remember my WIP!
Oct 30 13:35:50 <sgw> The generated socket number is supposed to be the way to do that according to my google searches.  I am more concerned about the monitor_dump() not working as I expect in the ssh _run() code
Oct 30 13:54:05 <RP> sgw: the trouble is that as soon as you close that socket number, another process can take it and race?
Oct 30 13:54:21 <RP> sgw: fair enough on 4444
Oct 30 13:54:32 <RP> sgw: you didn't mention it in the commit messages ;-)
Oct 30 13:58:24 <sgw> RP: WIP and early moning excuses!
Oct 30 14:01:53 <JPEW> sgw: I think you have erronouse quotes in the command
Oct 30 14:02:13 <JPEW> The single quotes in testimage_dump_monitor() should not be there
Oct 30 14:02:17 <JPEW> I think?
Oct 30 14:04:10 <sgw> JPEW: It's not even printing the debug message from the monitor_dump when I call it in _run.  The one time I did see output correctly, it's quoted correctly (I think also because of the \n)
Oct 30 15:03:12 <eduardas> is it just me or is do_fetch for binutils-cross-aarch64 extremely slow? this is always the case for me on an entirely clean build without downloads
Oct 30 15:09:00 <eduardas> though it could be much faster using ftp and tarball download, I suspect it is not done in poky for CI reasons?
Oct 30 15:22:05 <prabhakarlad> Hi All,
Oct 30 15:22:34 <prabhakarlad> What is the proper solution to check if file exists in  a bb file ?
Oct 30 15:27:55 <eduardas> prabhakarlad: is this file in metadata or work directory?
Oct 30 15:28:25 <eduardas> prabhakarlad: if it's ir WORKDIR, I'd probably append a shell script to a task
Oct 30 15:28:44 <prabhakarlad> eduardas: its in work dir downloaded as part of SRC_URI
Oct 30 15:29:50 <eduardas> prabhakarlad: if you're using poky, I think there is a check that will not allow you to build the recipe if a SRC_URI file is missing
Oct 30 15:30:51 <eduardas> ERROR: musl-1.2.1+gitAUTOINC+a5aff1972c-r0 do_package_qa: QA Issue: musl package is not obeying usrmerge distro feature. /lib should be relocated to /usr. [usrmerge]
Oct 30 15:31:09 <prabhakarlad> eduardas: SRC_URI file is Linux repo, I am trying to build tools (pcitest) which is only present in 4.19+ kernels
Oct 30 15:31:12 <eduardas> I musl even known to work with usrmerge?
Oct 30 15:32:15 <prabhakarlad> eduardas: builds below 4.19 are failing
Oct 30 15:32:56 <eduardas> prabhakarlad: you should build the tools only for machines and images that have 4.19+
Oct 30 15:33:41 <eduardas> prabhakarlad: don't you have different image recipes for systems that run different kernel versions?
Oct 30 15:34:02 <eduardas> prabhakarlad: assuming you have different kernel versions to support different platforms
Oct 30 15:34:51 <eduardas> prabhakarlad: because why not use a single kernel recipe if platforms are similar enough?
Oct 30 15:35:09 <prabhakarlad> eduardas: unfortunately no :(  we have same recipe to build different kernel version.
Oct 30 15:38:37 <eduardas> prabhakarlad: https://www.yoctoproject.org/docs/3.1.3/ref-manual/ref-manual.html#var-MACHINE_EXTRA_RDEPENDS
Oct 30 15:39:26 <eduardas> prabhakarlad: I'd have different machine configs for different kernel versions and do MACHINE_EXTRA_RDEPENDS for a separate pcitests package
Oct 30 15:40:06 <eduardas> prabhakarlad: MACHINE_EXTRA_RDEPENDS goes into machine configuration files
Oct 30 15:41:12 <eduardas> prabhakarlad: not really sure how to go about pcitests themselves. Do you have a separate recipe for them using the same SRC_URI as kernel recipe?
Oct 30 15:41:53 <eduardas> prabhakarlad: because I assume these are binaries that work on the target and are supposed to be shipped with the rootfs?
Oct 30 15:41:54 <prabhakarlad> eduardas: I am using the staging dir to get to pcitest.c
Oct 30 15:42:42 <prabhakarlad> Yes it should be shipped with rootfs.
Oct 30 15:43:25 <zeddii> so you are explictly launching the build for it in your do_compile ?
Oct 30 15:45:34 <prabhakarlad> Yep that's wight.
Oct 30 15:45:42 <prabhakarlad> right
Oct 30 15:46:05 <zeddii> so just test for the file, and only build if its there. do_compile is just shell.
Oct 30 15:48:05 <prabhakarlad> Ah good point -F test <path> ?
Oct 30 15:48:37 <zeddii> whatever you prefer.  if [ -f <foood> ]; then <do your build stuff>; fi
Oct 30 15:49:32 <eduardas> prabhakarlad: just curiosity: what package does the binary belong to after it gets installed into rootfs and packaged?
Oct 30 15:52:27 <prabhakarlad> zeddii: Thanks
Oct 30 15:52:35 <eduardas> prabhakarlad: Arago project packages this binary separately: http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-extras/recipes-kernel/pcitest/pcitest_5.4.bb;hb=master
Oct 30 15:53:06 <eduardas> though the approach mentioned earlier should also work
Oct 30 15:53:21 <prabhakarlad> eduardas: we have a sperate recipe which builds all the required tools kernel-test.bb
Oct 30 15:54:39 <eduardas> prabhakarlad: I'd personally still do a separate pcitest recipe and use MACHINE_EXTRA_RDEPENDS or add the package per image recipe
Oct 30 15:55:16 <eduardas> prabhakarlad: but there are different ways to do the same thing
Oct 30 15:56:54 <eduardas> prabhakarlad: the advantage for separate recipe is that COMPATIBLE_MACHINE can be used as an additional sanity check
Oct 30 15:57:46 <eduardas> prabhakarlad: i.e. it can be made not to build for machines that use older kernels even if the BSP user mistakenly does "bitbake pcitests"
Oct 30 15:58:16 <prabhakarlad> eduardas: agreed that would give fine grain control. Thank you for the pointers :)
Oct 30 15:59:58 <eduardas> prabhakarlad: well, hopefully I can be helpful to people at least occasionally... I am usually get to ask for advice rather than give it to other people :D
Oct 30 16:02:49 <prabhakarlad> :)
Oct 30 16:04:15 <eduardas> does anyone know if the usrmerge distro feature broken under musl?
Oct 30 16:04:30 <eduardas> or is it just my weird distro configuration
Oct 30 16:04:59 <eduardas> is anyone even building/testing with usrmerge enabled?
Oct 30 17:40:10 <RP> kanavin_home: thanks for the patches. I've started moving master forwards again
Oct 30 17:43:04 <kanavin_home> RP: cheers, I do think me running the builds takes quite a bit of friction out
Oct 30 17:43:23 * kanavin_home is a mini-ross
Oct 30 17:43:41 <moto-timo> kanavin_home is a tornado of patch bomb goodness
Oct 30 17:45:29 <RP> kanavin_home: it helps massively!
Oct 30 17:45:42 <RP> kanavin_home: I miss ross doing this, it is a huge help!
Oct 30 17:46:18 <RP> rburton: you're being deprecated ;-)
Oct 30 17:46:36 <moto-timo> rburton 2.0
Oct 30 18:16:15 <RP> JPEW: How do you handle the two recipe problem with your prebuilt setup?
Oct 30 18:22:24 <JPEW> RP: j/s I'm pushing up my code :)
Oct 30 18:34:30 <JPEW> RP: https://github.com/JoshuaWatt/prebuilt-recipes-example
Oct 30 18:34:48 <JPEW> I think I sufficiently sanitized that :)
Oct 30 18:35:04 <khem> RP: we have quite a few prebuilts too, and a bit of organizing helps, but we are producer and more consumer of them, someone who is building SDKs might have more different usecases
Oct 30 18:35:34 <khem> ah same think what JPEW is doing :)
Oct 30 18:36:04 <JPEW> It works well enough.... if we had to do it more than once I probably would have made it better
Oct 30 18:36:19 <JPEW> I think you could combine them into a single recipe with BBCLASSEXTEND or somethinmg
Oct 30 18:37:24 <khem> yeah, I am always paranoid avoid sharing wrong ones :)
Oct 30 18:38:05 <JPEW> My favorite part of this is the do_publish() task in the source recipe.... it's not often you write a task that modifies a recipe :)
Oct 30 18:38:17 <RP> JPEW: its interesting but very specific use case. I still think one recipe switching between two inc files would probably look better to most end users
Oct 30 18:39:30 <JPEW> RP: Right. To be clear, I'm fine with one recipe & inc files; I just don't want the selection of the inc files to be tied to what layers are present
Oct 30 18:40:16 <RP> JPEW: how do you want the selection?
Oct 30 18:40:28 <RP> JPEW: the hard part is most people don't want to share the source recipe
Oct 30 18:40:54 <RP> JPEW: would BBMASK work for you?
Oct 30 18:41:21 <RP> or BBPATH modification more likely
Oct 30 18:41:29 <khem> RP: right, thats why its in a different layer and has virtual/xxx
Oct 30 18:43:19 <JPEW> Ah, I guess if they want to hide the source recipe that's another story
Oct 30 18:43:31 <JPEW> I wasn't thinking about that
Oct 30 18:43:55 <JPEW> Our recipes are just side by side in the same layer because we don't care about that
Oct 30 18:44:09 <moto-timo> ++
Oct 30 18:44:09 <RP> JPEW: right, hiding this is key for some which is why the layer selection piece
Oct 30 18:44:18 <moto-timo> --
Oct 30 18:44:29 <RP> I'm not saying that is a good thing, just a hard requirement I keep hearing
Oct 30 18:44:34 <moto-timo> I know
Oct 30 18:44:38 <moto-timo> just don't like it
Oct 30 18:44:41 <moto-timo> :)
Oct 30 18:44:56 <RP> I don't like prebuilts full stop ;-)
Oct 30 18:44:58 <moto-timo> I fundamentally don't think it's the right business model
Oct 30 18:45:00 <moto-timo> lol
Oct 30 18:45:09 <JPEW> Ours is entirely a legal thing; they want to know who has to go to a deposition because they could see the source if we get sued
Oct 30 18:45:25 <moto-timo> ahh, the lawyers
Oct 30 18:45:29 <moto-timo> hello
Oct 30 18:48:22 <armpit> postbuilts ?
Oct 30 21:33:28 <opennandra> hello, I'm trying to bump python on rocko (need to stay ar poky rocko but need 3.7.x python). I just took brute force method to copy recipe from some later release but seems it's not right way as I'm getting errors like: NOTE: Resolving any missing task queue dependencies
Oct 30 21:33:28 <opennandra> NOTE: preferred version 3.7.6 of python3 not available (for item python3-subprocess)
Oct 30 21:33:28 <opennandra> NOTE: versions of python3 available: 3.5.3
Oct 30 21:33:28 <opennandra> NOTE: preferred version 3.7.6 of python3 not available (for item python3-textutils)
Oct 30 21:33:29 <opennandra> NOTE: versions of python3 available: 3.5.3
Oct 30 21:33:31 <opennandra> NOTE: preferred version 3.7.6 of python3 not available (for item python3-reprlib)
Oct 30 21:33:33 <opennandra> NOTE: versions of python3 available: 3.5.3
Oct 30 21:33:36 <opennandra> it is even possible?
Oct 30 21:37:28 <RP> kanavin_home: still around?
Oct 30 21:47:23 <kanavin_home> RP: yes, just got the email
Oct 30 21:48:01 <RP> kanavin_home: I'm puzzled why this suddenly appeared :/
Oct 30 21:48:40 <kanavin_home> RP: I guess json-glib generates a file with build paths in it
Oct 30 21:48:58 <RP> kanavin_home: looks like it, but why suddenly in master-next
Oct 30 21:50:17 <kanavin_home> RP: I'll run a local build and see what happens
Oct 30 21:51:17 <kanavin_home> RP: is it probable that json-glib previously wasn;t a part of reproducibility tests, and now something in -next pulls it in?
Oct 30 21:53:35 <RP> kanavin_home: ah, yes, that could well be
Oct 30 21:53:44 <RP> kanavin_home: I think rburton may have seen this before
Oct 30 21:56:46 <kanavin_home> RP:
Oct 30 21:56:46 <kanavin_home> commit 642fde647f9f69ccbf67babd5c86a0779b25166c
Oct 30 21:56:46 <kanavin_home> Author: Jose Quaresma <quaresma.jose@gmail.com>
Oct 30 21:56:46 <kanavin_home> Date:   Thu Oct 29 14:28:00 2020 +0000
Oct 30 21:56:46 <kanavin_home>     gst-examples: upgrade to version 1.18.0
Oct 30 21:56:47 <kanavin_home>      
Oct 30 21:56:47 <kanavin_home>     DEPENDS:
Oct 30 21:56:48 <kanavin_home>      - Upstream now depends on libsoup-2.4 and json-glib
Oct 30 21:56:49 <kanavin_home> could be this?
Oct 30 21:57:05 <RP> kanavin_home: yes, that would explain it. So its probably never been reproducible :/
Oct 30 21:57:11 <kanavin_home> meta/recipes-sato/packagegroups/packagegroup-core-x11-sato.bb:GSTEXAMPLES ?= "gst-examples"
Oct 30 21:57:14 <RP> kanavin_home: sorry, I was getting distracted by the upgrade
Oct 30 21:57:50 <kanavin_home> RP: I'm running a build, I vaguely remember I have seen - and fixed - something like that
Oct 30 21:58:06 <RP> kanavin_home: right, it does look familiar
Oct 30 22:05:26 <RP> kanavin_home: similar to http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ead43a4168cc8682e7440c3c5ac0da54f0af6f85 ?
Oct 30 22:07:45 <kanavin_home> RP: YES
Oct 30 22:20:34 <kanavin_home> RP: patch sent
Oct 30 22:21:01 <kanavin_home> RP: grrr, discard
Oct 30 22:21:10 <kanavin_home> will fix the right one in a second
Oct 30 22:21:16 <kanavin_home> I'm really falling asleep :)
Oct 30 22:21:55 <RP> kanavin_home: no problem, its getting late and its somehow really tiring watching/listening to all this
Oct 30 22:22:21 <RP> kanavin_home: I'm much happier now I know what is wrong, I'll just hold this set until we get this fixed
Oct 30 22:26:30 <kanavin_home> RP: sent again
Oct 30 22:26:34 <kanavin_home> RP: and now, afk
Oct 30 22:26:55 <RP> kanavin_home: thanks!
Oct 30 22:55:16 * zeddii sees the story RP was mentioning https://www.bbc.com/news/health-54750775
Oct 30 22:59:34 <RP> zeddii: not looking good. Although the North East is the one area in the country where they think growth rates may be slowing
Oct 30 23:00:09 <RP> I'm still not sure what a "reasonable worst case scenario" is
Oct 30 23:01:02 * paulg returns to Ottawa tomorrow - which is AFAIK still in "Stage2" as a "red zone".   :-/
Oct 30 23:01:37 <zeddii> they are talking about letting stuff open again. fingers crossed.
Oct 30 23:03:24 <paulg> thought it was a hard four weeks starting Oct 9th... so another week and a bit minimum.
Oct 30 23:04:11 <zeddii> with the latest numbers, they were talking about ways to ease. Might just wait the week, but they have at least acknowledged their 'choices
Oct 30 23:04:14 <zeddii> were shit
Oct 30 23:04:21 <zeddii> and based on no numbers.
Oct 30 23:06:53 <RP> I don't think they really know...
Oct 30 23:07:17 <zeddii> they released some decent ones here on Wednesday. As much as they know. But our scale is far less then most places.
Oct 31 00:27:25 <RP> gah, can't sleep :(
Oct 31 00:27:40 <zeddii> moto-timo: is still on the zoom call! :D
Oct 31 00:27:53 <moto-timo> zeddii: yep
Oct 31 00:32:33 <RP> moto-timo: I was tiring ages ago sadly
Oct 31 00:33:13 <RP> kanavin_home: fix looks like its worked, thanks again!
Oct 31 00:36:18 <moto-timo> RP: me too about 11am my time I was #done
Oct 31 00:36:31 <moto-timo> RP: zeddii: but I caught me second or third wind and this point
Oct 31 00:37:19 <zeddii> indeed. I decided to keep myself awake by finishing 5.10 kernel work, and ended up porting aufs to it, and have now booted / fixed all architectures. Assuming ppc finishes and boots.
Oct 31 00:37:38 <zeddii> and now, I want to see if it works .. so I'm getting tired while I watch it build.
Oct 31 00:37:43 <moto-timo> Friday night lights!
Oct 31 00:38:02 <denix> you all are crazy!
Oct 31 00:38:06 <zeddii> that and I want to finish the cloud-init effort that moto-timo goaded me into :D
Oct 31 00:38:09 <moto-timo> I certainly am
Oct 31 00:38:11 <zeddii> but not tonight for that.
Oct 31 00:38:35 <moto-timo> zeddii: thank you for cloud-init whether it happens soon or not
Oct 31 00:39:10 <zeddii> I have it "done", but the config for it is *crazy*, so I'm trying to sort that out. got lost in the docs, will let it mull a bit and finish it next week.
Oct 31 00:39:37 <zeddii> it's worse now, then when I did it the first time .. years ago now.
Oct 31 00:42:19 * RP has managed to get master moving forward again, lots of upgrades
Oct 31 00:42:37 <RP> with any luck the next batch of patches might turn out ok this time
Oct 31 00:44:15 * RP reads another update-alternatives patch and things we need a new mechanism for this mess
Oct 31 00:44:20 <RP> thinks
Oct 31 00:48:17 <moto-timo> zeddii: can't talk on the zoom neener neener
Oct 31 00:48:30 <zeddii> back to my cursed mac
Oct 31 00:53:12 <moto-timo> `too bad zeddi can't tell us what he told me about meta-python in San Diego in 2016
Oct 31 00:53:25 * zeddii starts meta-c
Oct 31 00:53:37 * moto-timo starts meta-cobol
Oct 31 00:53:58 <zeddii> the most important thing about an application, is the language it is written in!!!!!
Oct 31 00:59:56 <moto-timo> zeddii: meta-dual-carbuerator-tuning
Oct 31 01:00:14 <RP> moto-timo: only dual?!
Oct 31 01:00:38 <moto-timo> meta-quad-carbuerator-tuning-v2
Oct 31 01:00:58 <RP> moto-timo: but my four carbs are on a v4? :)
Oct 31 01:01:49 <moto-timo> meta-one-am-why-cannot-i-sleep
Oct 31 01:02:17 <RP> moto-timo: the photos of motorcycle on facebook really are off a v4 with four carbs I'll need to balance
Oct 31 01:02:59 <moto-timo> RP: :) good times... I remember attempting to balance the carbs on my VW camper van
Oct 31 01:03:45 <moto-timo> california law required us to strip off the centrifugal advance distributor and the single carbuerator and replace it with the much less efficient original equipment
Oct 31 01:03:59 <moto-timo> "for pollution reasons"
Oct 31 01:04:06 <moto-timo> ? more polution?
Oct 31 01:05:10 <RP> moto-timo: conversely, fixing my re-imported ex-Californian MGB started by removing most of the pollution stuff that was already half disconnected or falling apart
Oct 31 01:05:38 <RP> sadly that car isn't well now :(
Oct 31 01:12:14 <moto-timo> Elvis has left the building and the zoom call is over
Oct 31 01:12:36 <moto-timo> RP: you still have an MGB?
Oct 31 01:12:50 <moto-timo> RP: I'll come visit and redo the entire electrical system
Oct 31 01:13:14 <RP> moto-timo: technically. The electrical system isn't the problem, that, I fixed as a 13 year old ;-)
Oct 31 01:13:27 <moto-timo> RP: I once had my Dad's MGB up on two wheels ...
Oct 31 01:13:37 <moto-timo> RP: lol
Oct 31 01:14:09 <moto-timo> RP: I was transporting the (now illegal in California) vehicle to Nevada but the belt on the generator was loose
Oct 31 01:14:21 <moto-timo> RP: so battery only power gets you... > this < far
Oct 31 01:15:04 <RP> Not sure I've had the MGB off the ground. Which is odd as I've managed all the wheels on I think every other vehicle I've owned
Oct 31 01:15:08 <moto-timo> RP: mind you it had expired tags and I'm not even sure it was insured so being on the road with the station chief of the highway patrol behind you as a teenager
Oct 31 01:15:19 <moto-timo> ... not a great life experience I want to repeat
Oct 31 01:15:31 <RP> moto-timo: character building? :)
Oct 31 01:15:38 <moto-timo> RP: indeed
Oct 31 01:16:04 <moto-timo> RP: reasons why my headset not working 30 seconds before my talk on Thursday is not stressful
Oct 31 01:16:16 <moto-timo> #2020 what else you got
**** ENDING LOGGING AT Sat Oct 31 02:59:57 2020