pitillo changed the topic of #crux-arm to: CRUX-ARM 3.8 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-8 | Logs: https://libera.irclog.whitequark.org/crux-arm/
_whitelogger has joined #crux-arm
aardo has quit [Ping timeout: 252 seconds]
ardo has joined #crux-arm
<beerman> bummer for the power otages, but nice .)
<cruxbridge> <jloc0> If I modify the PORTS_BLACKLIST do I just need to redo stage1 and finish it off again?
<cruxbridge> <jloc0> A rootfs is great, but I have no kernel, firmware or anything to ya know… boot it
<cruxbridge> <pitillo (@pitillo:crux.nu)> jloc0: You can tweak the process to avoid rebuilding everything in stage1
<cruxbridge> <pitillo (@pitillo:crux.nu)> Adjust blacklisted ports and delete stage1/packages.done file (this file is a flag used to “mark” the stage as done, same for stage0)
<cruxbridge> <jloc0> Ahh ok that’s why I’m failing
<cruxbridge> <pitillo (@pitillo:crux.nu)> BTW, keep a copy of packages as a backup
<cruxbridge> <jloc0> I probably have it all built I should just pull it off my vm, that would speed me up considerably heh
<cruxbridge> <pitillo (@pitillo:crux.nu)> So the stage1/ports.list will be rebuilt with non blacklisted ports and all built ports are not need to be rebuilt
<cruxbridge> <jloc0> Ok great
<cruxbridge> <pitillo (@pitillo:crux.nu)> All built ports (stage0 or stage1 packages) shouldn’t be deleted, but to be sure to avoid rebuilding them (just they got deleted) a backup is a good practice (just in case)
<cruxbridge> <jloc0> It seems to name the files bad, ends up “crux-.rootfs.xz” seems to miss the -arm-raspberrypi5 bit
<cruxbridge> <pitillo (@pitillo:crux.nu)> (Morning btw, my English probably sucks more at this time… I just woke up)
<cruxbridge> <jloc0> Ahh no matter it’s late for me, so proper grammar is out the door already ;)
<cruxbridge> <pitillo (@pitillo:crux.nu)> jloc0: Ummmmm we need to recheck that for the dockerized version, probably we are missing passing the variables to the dockerized script
<cruxbridge> <jloc0> Ok I think I’m seeing that it builds what’s in core but it doesn’t pull in the rest of the ports from the rpi5 repo, does it only build what core contains? I see it built the rpi5 ports package, and wpa_supplicant but not the rest… can I add them to its build list?
<cruxbridge> <jloc0> If I add to ports.list will it?
<cruxbridge> <pitillo (@pitillo:crux.nu)> Ports.list is regenerated
<cruxbridge> <pitillo (@pitillo:crux.nu)> It must contain any non blacklisted port in the device.mk file
<cruxbridge> <pitillo (@pitillo:crux.nu)> Did you remove from there?
<cruxbridge> <jloc0> Yeah removed them from the mk file
<cruxbridge> <jloc0> It’s completely skipping them but it did do all the ones that also exist in core
<cruxbridge> <pitillo (@pitillo:crux.nu)> Ummmm then may be we need to check again the logic regarding ports collection, but I’m pretty sure that it was adding all ports from overlays
<cruxbridge> <pitillo (@pitillo:crux.nu)> If they weren’t blacklisted in the device.mk file
<cruxbridge> <pitillo (@pitillo:crux.nu)> Stage0/ports.list must be a “closed” list with a group of base ports but stage1/ports.list must be filled with all ports from device overlay, core-arm64 and core ports
<cruxbridge> <jloc0> Ahhh I think o got it common.mk has BASE_PORTS I likely need to add them to
<cruxbridge> <jloc0> Heh nope skipped again, F
<cruxbridge> <pitillo (@pitillo:crux.nu)> Those base ports are only used on stage0
<cruxbridge> <jloc0> Ahh well it was worth a shot lol
<cruxbridge> <jloc0> Iirc pkgadd has a —root flag, I can do it the manual way and just add them to the system
<cruxbridge> <jloc0> Once I write it
hermit_crab has joined #crux-arm
<hermit_crab> Hello, somebody know a repo with pre-compiled core packages up-to-date? I can't compile binutils;cmake;gcc;python3 on my poor raspi 3b+
<r0ni> heh I haven't done a 3.8 repo like i did for 3.7, but I probably have packages
<r0ni> they are not optimized for rpi3, just reg -O2
<hermit_crab> this is a problem?
<r0ni> nah just standard optimization is all
<r0ni> gimme a few mins, I'll upload them for ya
<r0ni> hermit_crab: are you using arm64 builds on it?
<hermit_crab> yeah
<r0ni> ok just wanted to ensure that first
<cruxbridge> <pitillo (@pitillo:crux.nu)> Are you using 3.8 and looking for updated packages since the release?
<cruxbridge> <jloc0> Ooh yeah can get the big tarball from the rootfs
<hermit_crab> yeah pitillo
<cruxbridge> <pitillo (@pitillo:crux.nu)> Ummmm I should check crux-rootfs artifacts….
<cruxbridge> <pitillo (@pitillo:crux.nu)> I think we aren’t packaging stage1 packages
<r0ni> hermit_crab: here ya go: https://lngn.net/crux/arm64-3.8/
<hermit_crab> oh, thanks r0ni!
<r0ni> it's like 140mb all in
<r0ni> i don't think i've ever checked the logs on the packages i put up, no idea if it was a worthwhile idea
<hermit_crab> again, thanks r0ni!
<r0ni> hermit_crab: your welcome!
<hermit_crab> I will go to bed. Bye everybody.
hermit_crab has quit [Quit: hermit_crab]
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ core-arm64/3.8 ]: util-linux: update to 2.41.1
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ core-arm/3.8 ]: util-linux: update to 2.41.1
crux-arm-bot has left #crux-arm [#crux-arm]
frinnst has quit [Quit: welcome to IRC: where the men are men, the women are men, and the little girls are FBI agents]