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> Hrmm, I find I still have raspberrypi4-arm.sec... maybe I never had one for 64, only 32?
<jaeger> Going to make a new one for 64, though
<jaeger> Guess I don't need to update the httpup REPO since there's a github workflow doing that... would just be duplicate work
<jaeger> ok, crux-ports-raspberrypi4-arm64 has a 3.7 branch now
mnkydeth has quit [Quit: leaving]
<jaeger> Going to sleep soon but finished a stage1 build for the rpi4 without errors. I'll test the packages on the rpi4 itself tomorrow
mnkydeth has joined #crux-arm
<beerman> exciting progress you three are pushing through with :) can't wait to get my hand on a pi 4 64 bit image 8-)
<pitillo> great jaeger !
<pitillo> let's see how can we manage it
<pitillo> the pine64 is on the aim too beerman 8)
<beerman> perfect :D I want to get to this
<pitillo> sepen was managing yesterday make targets/objectives on crux-arm-release just to prepare an inprovement to stages
<beerman> sounds very cool :) i haven't even looked closely yet but it sounds fantastic
<beerman> with the pi4 images AND the pine64 one I might be able to setup a working environment for the pinephone in a breeze
<pitillo> let's see how performance goes on the rpi4
<beerman> pi4 should be fine, I haven't been grumpy about "having to use 32bit" with it, so 64bit should feel just a tad better. at least thats what I expect from it
<beerman> I am more interested in finding out what I can build on it 8-)
<beerman> there have been a few ports I had troubles with but I didn't spend too much time with it either
<pitillo> probably anything
<pitillo> if you find problems, share them, may be they are reproducible on other devices too
<beerman> pi4 can be a great desktop replacement again, now that energy prices are surging
<beerman> i will
<beerman> i have two pis to setup, and one can run as a clean build env and/or distcc member
<beerman> so
<beerman> I should be able to maintain a few ports in our overlay, finally
<pitillo> that's true... probably depends on desktop usages... but it can fit as desktop for many purposes
<pitillo> sounds great
<beerman> up until 2 weeks ago or so I had used the pi4 for homeassistant with their own sd card image. I moved that to a x86_64 server on my network so now the pi4 is unused and in need of a new purpose 8-)
<pitillo> that sounds like a plan xD
<beerman> and for the other pi, I used to run kodi on it and for that I used a 32bit install of CRUX.. but I don't do that anymore so no need to hold onto it. Right now it just fetches and sorts my mail etc
<beerman> the pi is not satisfying for kodi if it runs on a 4k panel :D
<pitillo> jajajjaa not enought for 4k
<beerman> not for all forms of 4k
<beerman> if you have really high quality file it won't display at all
<pitillo> well, I'm done. Docker "snapshot" done with current work... so it's time to let my kid put me on the street, and not the oposite xD
<beerman> sound will run, but not the video xD
<beerman> i forgot what it was... i think the high bandwith of color spectrum type of feature
<beerman> hahaha
<beerman> have fun, enjoy your sunday :)
<pitillo> it's a powerful device really, but with video I believe there are other details as codecs or what you said, file specs
<pitillo> yeah!!! same there@~||@|@@#
<beerman> indeed, integrated amdgpu is more than enough for kodi on ryzen cpus :D
<beerman> thanks :D
<jaeger> pitillo: what's the intent behind these lines? https://github.com/crux-arm/crux-arm-release/blob/main/Makefile#L275-L278
<jaeger> Wouldn't we want the proper pkgmk.conf and prt-get.conf from the device overlay in the rootfs instead?
<jaeger> hrmm, something is also weird with the github httpup REPO update workflow
<jaeger> does not exist in https://github.com/crux-arm/crux-ports-raspberrypi4-arm64/blob/3.7/REPO after the update workflow
<jaeger> near the end, after the httpup-repgen run, "nothing to commit, working tree clean"
<jaeger> oh, maybe that's a red herring... I see 'git add REPO' earlier in the log