13:09:29 <nsITobin> so funny story, spectrum has determined once again its my router with the issue.. So I did a test.. I changed the mac address of the router to something assigned to a long dead early linksys router? .. full speed. and it wasn't just the reboot cause I rebooted stuff before I changed it to rule that out as a "fix"
13:09:36 <nsITobin> they.. are screwing with me
13:10:17 <nsITobin> because I won't give them 7 bucks to have their hacked openwrt with all features removed cheap router assuming direct control over my network
13:12:20 <nsITobin> frankly my router does better than the average reported for this model on getting extremely close to full gigabit
13:12:37 <nsITobin> likely cause it isn't overtaxed with the wifi
13:13:40 <nsITobin> I looked at a new router .. they are as far as hardwired connections conserned functionally no more advanced than what I already have they just have magical versioned wifi upgrades
13:14:36 <nsITobin> and an app
13:14:40 <nsITobin> :P
13:47:43 <frg_Away> just what you need. A router configurable over the internet
13:48:22 <nsITobin> well my router IS configurable over the internet I just have it disabled cause well you know me.. I am almost always here
13:49:00 <frg_Away> nsITobin yes mine too. Standard fritz box
13:51:36 <nsITobin> My router's deficiencies are that as a wifi router it isn't that great but it hardly matters and its ipv6 support is irritating enough I disabled it.. otherwise its been a solid piece of equipment despite its tendancy to cosplay as other router brands
13:53:53 <nsITobin> well frg_Away I have been lulled into a false sense of security by a lifetime dealing with comcast and its aquired predicesors.. spectrum is a whole different animal it seems and they are into some not-so-clean tactics
13:56:12 <nsITobin> with comcast it was just a friendly game of gotcha here's a promo to make up for it.. with spectrum it is an actual fight to get them to do anything
13:57:46 <nsITobin> anyway how do I test this quad zero thing?
13:59:05 <frg_Away> nsITobin I entered the address in the url bar and got a different error depending on pref under Windows
14:00:55 <nsITobin> I'll get the queue going on my chroot into Rocky VIII and a-test.
14:01:22 <nsITobin> suddenly want some 80s music for some reason...
14:58:01 <CaptainTobin> Turn off NETGEAR logo LED
14:59:06 <nsITobin> always clean up any instantiated xpcom interfaces
17:20:56 <nsITobin> finally build kicked off
17:35:16 <nsITobin> frg_Away: with pref false its Failed to Connect with pref true it is Address Not Found
17:35:19 <nsITobin> on Linux
17:35:27 <nsITobin> WIP Patch Queue
17:37:23 <frg_Away> nsITobin sounds about right
17:37:38 <frg_Away> so no change needed?
17:37:51 <nsITobin> doesn't look like it
17:39:18 <nsITobin> sorry it took so long BUT setting up did go smoothly and I got the start of a rocky 8 kickstart file out of it i can refine over time
17:42:58 <frg_Away> gitlab wip updated. Sync with 2.53
17:58:28 <nsITobin> re-applying updated patchqueue
18:11:38 <nsITobin> frg_Away: I am getting a Could not detect environment shell exception
18:15:52 <frg_Away> nsITobin did you nuke the old object dir?
18:16:00 <nsITobin> yes
18:17:24 <frg_Away> Linux or Windows?
18:17:30 <nsITobin> linux
18:17:59 <nsITobin> rocky 8 chroot env the same one I just built from minutes previously before I swapped the patches out for the updated queue
18:18:03 <nsITobin> wip
18:18:03 <frg_Away> seems shell is not defined then.
18:19:00 <nsITobin> yes
18:19:02 <nsITobin> i agree
18:19:53 <nsITobin> did SHELL=/bin/bash got through configure but telemetry mozbuild is complaining about unsorted SOURCES
18:20:13 <nsITobin> SHELL=/bin/bash ./mach configure
18:20:16 <nsITobin> is what I did
18:21:14 <nsITobin> 0:24.37     ['UnsortedError: An attempt was made to add an unsorted sequence to a list. The incoming list is unsorted starting at element 0. We expected "core/ipc/TelemetryIPC.cpp" but got "HangReports.cpp"\n']
18:21:46 <nsITobin> never did figure out how to RIP THAT OUT ONCE AND FOR ALL lol
18:32:06 <frg_Away> HangReports.cpp is gone. I don't see any reference left
18:47:29 <nsITobin> frg_Away: maybe the patches goofed up i popped em all and reappling
18:47:57 <nsITobin> it's not a perfect system but a useful one from all i have read on mq
19:06:46 <nsITobin> frg_Away: what patch file removed it?
19:08:36 <frg> nsITobin 1722225-1-killtelemetry-bhr-2539.patch
19:17:10 <nsITobin> frg_Away: the queue stops at 1619555-PARTIAL-76a1.patch on the mozilla side this file does not exist the kill telemetry patches are after that point
19:18:28 <nsITobin> maybe just not added to the index?
19:18:35 <nsITobin> in git
19:23:38 <therube> Pref off HTTP/2 push
19:23:40 <therube> https://bugzilla.mozilla.org/show_bug.cgi?id=1915848
19:26:22 <nsITobin> after the web takes over our desktop and http catches up to usb and wifi and processor generations you will find it so much more streamline when you have to decide to get the new Technology 14 (Version 2025-first half)
19:27:18 <nsITobin> therube: tell me technology hasn't went from innovation for existing problems to spring and fall fasion wear
19:29:11 <nsITobin> frg_Away: case senstive filesystems are case senstive
19:30:25 <nsITobin> an additional note: I dislike case senstive file systems.
19:30:58 <frg_Away> nsITobin might have goofed will fix
19:31:25 <nsITobin> let me make sure I didn't
19:31:53 <nsITobin> applying 1619555-PARTIAL-76a1.patch
19:31:53 <nsITobin> unable to read 1619555-PARTIAL-76a1.patch
19:32:00 <nsITobin> 1619555-partial-76a1.patch
19:32:09 <nsITobin> yep case senstive filesystems are indeed case senstive
19:32:12 <frg_Away> yeahh goofed
19:32:35 <nsITobin> easy mistake.. I dislike case senstive file systems for this very reason
19:35:11 <nsITobin> I honestly cannot think of a usecase for a filesystem with case senstivity
19:35:24 <nsITobin> it just makes typing filenames harder
19:36:52 <nsITobin> mkfs.xfs -f -n version=ci /dev/sda
19:37:00 <nsITobin> good to know for the future
19:38:33 <frg_Away> fixed
19:38:56 <nsITobin> did you rename the file or the entry in series file
19:40:23 <frg_Away> The file. All the others are uppercase
19:41:06 <frg_Away> and its patchday :)
19:41:59 <nsITobin> ok stopped at ipdl-start
19:42:03 <nsITobin> let's try again
19:43:13 <nsITobin> kicked off estimated time to built ~10 minutes
19:43:38 <nsITobin> yes it builds FAST on here
19:47:18 <nsITobin> best turn the fan on.. getting a bit warm under the desk
19:47:33 <nsITobin> this is deff a winter pc
19:47:48 <nsITobin> not so well suited to southern us heat
19:56:06 <nsITobin> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0 SeaMonkey/2.53.20
19:56:06 <nsITobin> Build identifier: 20240910144147
20:04:57 <grey_gandalf> hi fellows...
20:05:06 <nsITobin> grey_gandalf: hello
20:05:15 <grey_gandalf> somebody around? trying to setup seamonkey to build on my MacBook with 10.9 and macports
20:05:24 <grey_gandalf> I have some ptyhon setup issues
20:06:17 <nsITobin> I dunno if I can provide much help but what issue are you having?
20:06:23 <grey_gandalf> I usually hack quite well, but python is not my thing
20:06:47 <frg_Away> grey_gandalf currently native building is broken. Only cross compiles work. Needs some more backports.
20:07:11 <frg_Away> 10.9 is no longer supported too
20:07:23 <frg_Away> code taken out
20:08:08 <grey_gandalf> I will try to reinstantiate it
20:08:27 <grey_gandalf> it is a good niche for SeaMonkey... a pity it was taken out btw
20:08:33 <nsITobin> grey_gandalf: is there a reason you can't update OS X to something higher?
20:09:00 <grey_gandalf> sure, apple doesn't like older MacBooks :)
20:09:11 <grey_gandalf> anyway, I think my issue is much earlier. I do run
20:09:13 <grey_gandalf> MACH_USE_SYSTEM_PYTHON=1 ./mach build
20:09:17 <nsITobin> Latest release	10.9.5 (Build 13F1911) / July 18, 2016; 8 years ago
20:09:20 <frg_Away> as far as I know anything which can runn10.9 an update to 10.11
20:09:31 <frg_Away> ^can update
20:09:59 <grey_gandalf> but also 10.9 isn't that worse than 10.11, so shoudl be easy to patch... I maintanin ArcticFox for 10.6 :)
20:10:06 <grey_gandalf> I get
20:10:08 <grey_gandalf> ModuleNotFoundError: No module named 'imp'
20:10:27 <grey_gandalf> python3 is supplied by MacPorts on my setup
20:10:42 <nsITobin> ArticFox is based on Tycho originally from Mozilla 38
20:10:48 <grey_gandalf> is "imp" some seamonkey module or a module I should install?
20:11:27 <nsITobin> and Pale Moon 24-26's frontend
20:11:39 <grey_gandalf> ArcticFox is current to about Mozilla 48/49 - I am the maintainer/developer... the fork is long ago and I mostly mozilla-ed it and obsoleted tycho
20:11:43 <nsITobin> that was largely contemporary to 10.9
20:11:51 <frg_Away> Its known broken. I need to fix it but didn't find the time and was/is dependent on having a later llvm. Now that we have a Rocky 8 builder I can finally tackle it but not tomorrow
20:11:55 <grey_gandalf> yes lovely frontend, but it is only single-browser
20:12:37 <grey_gandalf> I always loved seamonkey... since ages, use it on all my systems and especially on mac it has a wonderful look!
20:13:04 <grey_gandalf> so since I got 10.9 to built ArcticFox I want seamonkey too :) I have a 10.11 machine... I don't have modern macs, too expensive
20:13:11 <grey_gandalf> (and also ugly)
20:13:13 <nsITobin> grey_gandalf: you're rmottola?
20:13:20 <grey_gandalf> nsITobin:  yes
20:13:22 <nsITobin> sup
20:13:33 <frg_Away> It needs Bug 1516228 among other for this to work again
20:13:38 <grey_gandalf> it is broken in what regards?
20:14:10 <grey_gandalf> I see... that build is much later... my issue is with python I suppse, it dies instantly
20:14:29 <grey_gandalf> maybe I can just install some python port from macports, but I don't know about "Imp"
20:14:49 <frg_Away> yes build system is half baked and needs more backports
20:15:07 <grey_gandalf> ArcticFox still uses python 2.7... (something I'd like to fix, but I don't know python.. so it sticks a little bit in mozilla 45 for now)
20:15:13 <grey_gandalf> build system is a headache
20:15:43 <frg_Away> 2.7 is gone too. Needs 3.7 at least
20:15:53 <grey_gandalf> I have python 3.12
20:16:01 <nsITobin> too new
20:16:06 <grey_gandalf> ahahah
20:16:08 <frg_Away> and this is too new :)
20:16:08 <grey_gandalf> darn
20:16:23 <grey_gandalf> wait macports has several pythons and I can select them ..
20:16:34 <nsITobin> grey_gandalf: one of a couple of us will get the build system settled
20:16:48 <frg_Away> porting for 3.12 is underway but no eta
20:18:20 <grey_gandalf> 3.11 ?
20:18:24 <nsITobin> I just dunno if older os targets are gonna get much if any attention when current versions need a lot of it.. gtk3 windows 10 + 1 etc
20:18:28 <nsITobin> and setuptools
20:19:41 <grey_gandalf> sure... not much use. 10.11 is already nice it was "reinstantiated"... the latest that runs on my Macbook. but got another one to test 10.9..
20:20:05 <grey_gandalf> and love it, since it still has removable battery :) easy "fix"
20:20:43 <grey_gandalf> what is latest python I can use? I have 2.7, 3.11 and 3.12
20:20:46 <nsITobin> well dedicate yourself to the fight to keep x11 and user choice alive on the linux front rather than play with ancient macos
20:21:05 <grey_gandalf> but I think I can coerce some older python
20:21:18 <nsITobin> 3.11 with setuptools will work fine
20:21:25 <grey_gandalf> ok
20:21:34 <nsITobin> but you will have to bootstrap from esr115
20:21:37 <nsITobin> for deps
20:21:53 <nsITobin> and i dunno if mozilla does native mac building anymore
20:22:51 <frg_Away> They still support it but I think either 10.15 or 11 is minimum now with central
20:22:55 <grey_gandalf> mozilla.. sorry for offending, but really goes a terrible route for Firefox... I dislike mozilla and all choices in past years
20:23:04 <frg_Away> thanks to rust too
20:23:07 <grey_gandalf> still faithful to it and will eat dust before using chrome
20:23:26 <nsITobin> grey_gandalf: half the issues with supporting old macs is apple keeps piling on arbitrary changes chanegs back removals new stuff to make it literally not worth supporting anything but the current version.. same with windows 10 from the pandemic on and most linux distros .. its industry wide
20:23:41 <grey_gandalf> .. but tested.. chromium works on 10.7 mac... supports almost anything.
20:23:51 <grey_gandalf> works and is compatible....
20:24:05 <grey_gandalf> I just hate the interface, the idea and google... stick to mozilal with my heard
20:24:23 <nsITobin> last I checked chromium isn't mozilla.. tho you may have been told otherwise and the webapp design of firefox on central doesn't help
20:24:24 <grey_gandalf> but esr 115 is so ugly... I hate the UI with all my guts
20:25:04 <nsITobin> 115 is JUST to get build dependancies as a service while they still exist
20:25:05 <grey_gandalf> I do know it is not mozilla.. jsut drawing comparisons.. firefox is getting worse though. I wurstion a lot of things by  mozilla
20:25:15 <grey_gandalf> yet at lest seamonkey has a decent UI
20:25:21 <nsITobin> and feel free to share ~/.mozbuild/toolchains/*
20:25:29 <grey_gandalf> but obsolete engine, we know
20:26:10 <nsITobin> umm how is it obsolete?
20:26:24 <nsITobin> it merely does not YET support every google and microsoft mandated web shiney yet
20:26:32 <grey_gandalf> well.. it is mostly gecko 60, right?
20:26:35 <nsITobin> you work on a Pale Moon fork.. come on y0
20:26:42 <grey_gandalf> well... try to use one important website: github. It won't work
20:26:42 <nsITobin> you know better
20:27:08 <grey_gandalf> I know, the palemoon fork is hopeless too :)
20:27:28 <grey_gandalf> actually it has so little palemoon left, that it is a PM-ized firefox fork.
20:28:33 <nsITobin> the very existance of a strata40 style firefox UI on 38 was a product of me. vNext Reserch Part 1
20:29:27 <nsITobin> grey_gandalf: I'd strongly consider doing linux on your macs instead of using old macosx
20:30:13 <nsITobin> i mean after PowerPC they just became largely overpriced laptop parts taped on an LCD monitor
20:30:23 <nsITobin> they ain't special no more
20:30:42 <grey_gandalf> I know... but well I do like older MacOS, so that's it...
20:31:29 <grey_gandalf> ArcticFox used to work on PPC LInux too.. but somehow I broke it. Works on NetBSD/PPC though
20:31:59 <grey_gandalf> so you are mattatobin?
20:33:27 <grey_gandalf> ok with python3.11 things are very different
20:33:52 <nsITobin> grey_gandalf: Yeah sorry I wasn't able to help you any on github i was shadowbanned forever
20:34:47 <grey_gandalf> oh, no longer github?
20:35:45 <grey_gandalf> ok, with python3.11 I have a crash inside tooolchain
20:35:58 <grey_gandalf> I wonder if my .mozconfig is correct? amy good examples for mac?
20:36:04 <grey_gandalf> I use the one I have on FreeBSD
20:38:20 <nsITobin> pastebin your mozconfig
20:38:45 <grey_gandalf> https://pastebin.com/qXDDQhwJ
20:39:23 <frg_Away> grey_gandalf its borken believe me. Needs more ports
20:39:48 <grey_gandalf> frg_Away: sure, but you get a failure much much later... I don't start building yet
20:40:02 <nsITobin> i think it needs more removals
20:40:11 <grey_gandalf> that was my error, this is my config
20:40:13 <grey_gandalf> https://pastebin.com/z2i98hHD
20:40:55 <nsITobin> not too insane actually
20:41:03 <nsITobin> i think you are out of luck
20:42:35 <grey_gandalf> it worked on freebsd 13 with 2.53.18
20:42:37 <grey_gandalf> should update now
20:42:51 <nsITobin> my evaulation of the seamonkey build system currently is: "It's a wonder it works at all" it does need more backports or severe cleanup likely both
20:43:11 <grey_gandalf> of course, system compiler might bea in issue, but that would
20:43:15 <grey_gandalf> bail out later
20:43:28 <nsITobin> you ain't even near a compiler were that errored out lol
20:43:33 <grey_gandalf> exactly...
20:43:37 <frg_Away> I know that native building is broken beucase I tried it on my mini mac some trime ago. I identified a few backports but these were blocked by our old clang CentOS 7 builder
20:44:03 <grey_gandalf> let me try on FreeBSD, I need to update there anyway
20:44:39 <frg_Away> FreeBSD should work. It was a macOS issue only
20:44:50 <grey_gandalf> I also use seamonkey on Gentoo... it was patched for build recently.. but IRC is long broken
20:45:09 <nsITobin> UNIX_BUT_NOT_MAC ;)
20:45:55 <nsITobin> chatzilla is busted why grey_gandalf
20:45:55 <grey_gandalf> wellseveral years ago I could do without firefox, just seamonkey.. these were times! :)
20:46:29 <grey_gandalf> nsITobin: works on windows, freebsd... but on Gentoo it doesn't install even if I enable it as port option. If I isntall the addon, it doesn't load
20:47:20 <nsITobin> speaking of I need to get back to my extensions-as-components work..
20:47:32 <nsITobin> i actually think I lost those patches
20:47:36 <nsITobin> have to do em again
20:50:06 <nsITobin> well grey_gandalf since you are obviously an experienced builder when the codebase isn't busted for your target would you be willing to help me determine current build requirements and build proceedures for various targets like the BSDs and gentoo cause I am gonna be revising the build page that has instructions and it would be nice if it was up to date and more detailed like the ones I wrote for Pale Moon's developer site
20:50:55 <grey_gandalf> I can do... I build from packages on gentoo, but could run ab build from source if needed
20:51:13 <grey_gandalf> my freebsd setup is nothing special, but I can share it
20:51:28 <grey_gandalf> I also need to see OpenBSD... and attempt an i386 build
20:52:03 <grey_gandalf> just because offical packages were removed from FreeBSD and OpenBSD - 2 years ago SeaMonley was long unbuildable
20:52:35 <grey_gandalf> I'm not so experienced as you think though - build system is a mystery for me as is the UI
20:52:37 <nsITobin> that's a shame.. u'd figure they'd fix them no matter what
20:53:03 <grey_gandalf> is it expected that auto-update on windows doesn't work?
20:53:15 <grey_gandalf> typing from there right now... and update get sinternal server error
20:53:26 <nsITobin> huh
20:56:41 <nsITobin> frg_Away: I ALMOST have this figured out
20:56:49 <frg_Away> something for ewong maybe
20:56:52 <nsITobin> how to instruct mach to get anything I want at 115
20:57:33 <nsITobin> $ ./mach artifact toolchain --artifact-manifest ../beer.text --from-build linux64-nasm
20:57:33 <nsITobin>  0:02.85 Setting up artifact nasm.tar.zst
20:57:33 <nsITobin>  0:02.85 Using artifact from local cache: /root/.mozbuild/toolchains/c0560725ae23de0d-nasm.tar.zst
20:57:33 <nsITobin>  0:02.85 rm tree: /mozdev/mozilla-esr115/nasm
20:57:33 <nsITobin>  0:02.86 untarring "/mozdev/mozilla-esr115/nasm.tar.zst"
20:57:43 <grey_gandalf> Internal server error (500)
20:57:50 <nsITobin> grey_gandalf: where?
20:58:02 <grey_gandalf> in the update panel when I check for updates
20:58:19 <nsITobin> Error Console or Browser Console clear and run again
20:58:23 <grey_gandalf> I do that on windows 7 only, of course. On FreeBSD I do build myself, gentoo comes from ports...
20:59:09 <grey_gandalf> Timestamp: 9/10/2024, 10:57:43 PM
20:59:11 <grey_gandalf> Error: XML Parsing Error: syntax error
20:59:12 <grey_gandalf> Location: https://updates.seamonkey-project.org/update/3/SeaMonkey/2.53.18.2/20240318103520/WINNT_x86_64-msvc-x64/en-US/release/Windows_NT%206.1.1.0.7601%20(x64)/ISET:SSE3,MEM:8047,JAWS:0/default/default/update.xml?force=1
20:59:14 <grey_gandalf> Line Number 1, Column 55:
20:59:15 <grey_gandalf> Source File: https://updates.seamonkey-project.org/update/3/SeaMonkey/2.53.18.2/20240318103520/WINNT_x86_64-msvc-x64/en-US/release/Windows_NT%206.1.1.0.7601%20(x64)/ISET:SSE3,MEM:8047,JAWS:0/default/default/update.xml?force=1
20:59:17 <grey_gandalf> Line: 1, Column: 55
20:59:18 <grey_gandalf> Source Code:
20:59:20 <grey_gandalf> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
20:59:23 <nsITobin> pastebin
20:59:24 <nsITobin> dude
20:59:29 <grey_gandalf> sorry for the strange paste... darn
20:59:54 <grey_gandalf> SeaMonkey IRC is funky with multiline :)
21:00:05 <nsITobin> no its just too many lines
21:00:07 <grey_gandalf> https://pastebin.com/vAfm0htv
21:01:05 <nsITobin> yeah i see it
21:01:28 <nsITobin> something is messed up on the server side it isn't an instantload and yeah
21:11:40 <nsITobin> SO mozilla-esr115 ./mach artifact toolchain --no-unpack --from-build linux64-clang linux64-rust linux64-nasm .. etc
21:11:51 <grey_gandalf> and broken... but last version it did update
21:12:07 <nsITobin> I just need the right OS-package combo to get ANYTHING from taskcluster applicable to 115
21:12:28 <nsITobin> grey_gandalf: there IS something going on with the sm aus
21:12:37 <grey_gandalf> test: on FreeBSD that said mozconfig started compilation! will take like 2 hours on my workstation with super-slow clang, but.. still a step forward compared to Mac
21:13:30 <grey_gandalf> GCC on FreeBSD builds happily, but fails to run :-P some linking issues
21:15:10 <nsITobin> well don't expect a magical resolution there are still bigger fish to fry but knowing current state is important too from beyond windows and linux
21:28:42 <grey_gandalf> I can't build on linux I guess... msvc and all that stuff
21:28:59 <nsITobin> you don't need msvc to build on linux
21:29:00 <grey_gandalf> freebsd is continuing... so basic setup is there, need to wait... going to bed then
21:29:08 <nsITobin> i am on linux its fine
21:29:52 <grey_gandalf> nsITobin: in theory mingw, but they dropped windows7 and so stopped updating and I don't have all the required stuff. Wanted to use it for ArcticFox too
21:30:47 <nsITobin> cross-compiling on pre-quantum codebases is not supported by anyone and experimenal research into it yielded issues largely cause of nsis..
21:30:59 <nsITobin> here we go.. finally..
21:31:13 <nsITobin> https://xref.palemoon.org/firefox-esr115/source/taskcluster/ci/build/
21:31:51 <nsITobin> these yaml files have lists of things I can put on the commandline to GRAB all the 115 toolchain artifacts so when they drop off taskcluster i will have em up on the server
21:32:14 <nsITobin> yeah dunno why I am on Pale Moon's cross-reference but doesn't matter
21:34:34 <grey_gandalf> I don't know yaml files
21:35:25 <grey_gandalf> but for today, my brain is full
21:35:26 <nsITobin> sorry grey_gandalf i was doing both thinking about what you are doing and working on one of my tasks which is to preserve these artifacts then rig up something so seamonkey users don't need to go fetch a bunch of extra stuff
21:35:51 <grey_gandalf> check building another time. FOr today I get that macos build is broken
21:36:03 <nsITobin> now that I have the command and all the package names I can grab em all
21:36:04 <grey_gandalf> tomorrow I'll see if freebsd compiled, let's hope! I can report setup in case
21:36:06 <grey_gandalf> goot dnight
21:39:12 <nsITobin> rest well
21:39:32 <nsITobin> for six months I been trying to work this bs out and I finally did it
21:40:01 <nsITobin> just came to me after seeing three related things in rapid succession
21:40:34 <nsITobin> ./mach artifact toolchain --no-unpack --artifact-manifest ../beer.text --from-build linux64-clang linux64-rust linux64-rust-size linux64-cbindgen linux64-dump_syms linux64-sccache linux64-nasm linux64-node linux64-pkgconf sysroot-x86_64-linux-gnu sysroot-wasm32-wasi
23:10:25 <nsITobin> seems vs is protected by some other mechnism from getting it manually not that it matters
23:40:08 <nsITobin> I need a better way to consume these yaml files