jaeger changed the topic of #crux-arm to: CRUX-ARM 3.6 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-6 | Logs: https://libera.irclog.whitequark.org/crux-arm/
<jaeger> interestingly the magic sysrq key combos still worked in that state
<jaeger> Unfortunately the filesystem on the uSD card got corrupted so I'll have to see if I can fix it tomorrow... if not, rebuild it
<beerman> ouch
<r0ni> i had finally got rust 1.73 to build, had to move to another drive to do it, but it worked
<beerman> Neat:)
<jaeger> Interesting... it also hangs on an external USB SSD with usb_storage hung timeout kernel messages
<jaeger> Wonder if NFS will be better
<jaeger> I can't remember if this came up before, is this the wrong key? https://github.com/crux-arm/crux-ports-raspberrypi3-arm64/blob/3.7/ports/raspberrypi3-arm64.pub
<jaeger> "raspberrypi3-arm" vs. "raspberrypi3-arm64"
<beerman> this caught my curious eye much more
<beerman> i can't answer the question about the key, i had one at some point but i guess i had deleted it when i gave up on the pi3 and sold it
<beerman> or was it the 32 bit repository.. 🤔
<jaeger> I kinda thought it had come up but my log search-fu is apparently weak today
<jaeger> On the plus side my rpi3 hasn't locked up (YET) using NFS for /usr/ports instead of uSD or USB SSD
<beerman> heh :)
<beerman> i don't have anything in my history. I recently had to change the irc bridge so i pretty much dumped the old server logs i had along with the software
<jaeger> always fun
<beerman> aye.. i used the official matrix bridge which was closed due to a security flaw they weren't able to fix fast, so they just closed it :D
<jaeger> I remember seeing something about that on tech news sites
<jaeger> found a circular dependency... jsoncpp depends on ninja which depends on jsoncpp
<jaeger> ninja's not listed as a dep for jsoncpp so it's not made obvious by prt-get
<jaeger> Probably doesn't really matter if you're not doing container update shenanigans like I am
<beerman> ouch, yeah, mh
<jaeger> Worked around it by bootstrapping a standalone ninja executable