jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
jue has joined #crux-devel
<jue> beerman: that's my fault, I've committed a fix at 2023-09-22 but didn't raise the release. Please try if the latest mariadb.rc works for you.
<beerman> Will do in a bit :) thanks!
<jue> thank you for the report ;)
<beerman> of course :)
<beerman> jue jaeger any objections to pull in python 3.12 for 3.8? I looked at it over the weekend, and will need to do a bit more testing, but i have only identified >10 ports that don't play nice with it yet - it should be fine until we are ready to release 3.8
<jue> no objections, will be a lot of work to update all the footprints, though
<beerman> already done 🫠
<beerman> not comitted and pushed though
<beerman> https://dpaste.com/CKGMHTUMQ it's not stupid if it works
<beerman> https://dpaste.com/27VZPCLYH footprints for opt
<jue> ok :)
<beerman> i'll commit what i have later tonight then, if jaeger has no objections
<beerman> we'll need to look into setuptools, https://docs.python.org/3/whatsnew/3.12.html distutils has been removed. building setuptools fails
<beerman> i hacked around it by using ensurepip which we have in core/python3
<beerman> certainly not the correct way, but i am unsure if that means we will need build, wheel and installer in core or so..
SiFuh has quit [Quit: leaving]
SiFuh has joined #crux-devel
<jaeger> No objection here
<beerman> cool, will commit later. The setuptools bootstrap might be the way after all, I did some more reading during the day. But probably exchanging them for build, wheel and installer might be a lot better. Of course, this would require for not only the footprint to change but all the ports that use setuptools to build the package will need to adapt to the new syntax.
<beerman> and build, wheel and installer will need to be bootstrapped the same way. First imagination says that instead of setuptools we would need pip, build, wheel, installer in core. Then at least we only bootstrap pip once, instead later on again in opt
<beerman> i am stopped right at the beginning where nftables requires setuptools, so nevermind
<jaeger> Sounds like a bit of a mess
<beerman> https://dpaste.com/6W6AXHQD7 i guess sticking to setuptools will be the best option right now until dust settles
<beerman> the diff doesn't look too bad once its applied :)
<jaeger> ok
braewoods has quit [Read error: Connection reset by peer]
braewoods has joined #crux-devel
braewoods_ has joined #crux-devel
braewoods has quit [Ping timeout: 260 seconds]
braewoods_ has quit [Read error: Connection reset by peer]
braewoods_ has joined #crux-devel
braewoods_ has quit [Remote host closed the connection]
braewoods_ has joined #crux-devel
braewoods_ has quit [Remote host closed the connection]
braewoods_ has joined #crux-devel
braewoods_ has quit [Remote host closed the connection]
braewoods_ has joined #crux-devel
braewoods_ has quit [Read error: Connection reset by peer]
braewoods has joined #crux-devel
braewoods has quit [Ping timeout: 248 seconds]
sajcho has joined #crux-devel
<sajcho> beerman: I used this pip build path and it works fine https://github.com/sajcho/core-x86_64/blob/main/python3-pip/Pkgfile
sajcho has quit [Quit: Client closed]
braewoods has joined #crux-devel
<beerman> but why when there is ensure pip included in our python3 install?
braewoods has quit [Remote host closed the connection]
braewoods has joined #crux-devel
sajcho has joined #crux-devel
<sajcho> be independent of the supplied version of pip in the python source
sajcho has quit [Client Quit]
jue has quit [Ping timeout: 240 seconds]
<beerman> i am not sure why though? ensurepip is fine enough to bootstrap a proper pip from the pip source? Why would an external script be any better?
sajcho has joined #crux-devel
<sajcho> you're right, sorry, it was just a shout in the dark, forget it
sajcho has quit [Client Quit]
<beerman> mh