jaeger changed the topic of #crux to: CRUX 3.7 | Homepage: https://crux.nu/ | Ports: https://crux.nu/portdb/ https://crux.ninja/portdb/ | Logs: https://libera.irclog.whitequark.org/crux/
zorz has quit [Quit: leaving]
tilman has quit [Ping timeout: 252 seconds]
tilman has joined #crux
rever_4192 has quit [Ping timeout: 248 seconds]
<uwumeowmoewnyaa> Oh no, there is a problem with deleting ports that are no longer needed too...
rever_4192 has joined #crux
uwumeowmoewnyaa has quit [Remote host closed the connection]
<cruxbot> [contrib/3.7]: p5-business-issn: 1.006 -> 1.007
<cruxbot> [contrib/3.7]: pnpm: 9.15.2 -> 9.15.3
_moth_ has quit [Ping timeout: 265 seconds]
uwumeowmeownyaa has joined #crux
rever_4192 has quit [Ping timeout: 252 seconds]
uwumeowmeownyaa has quit [Quit: ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.4)]
lavaball has joined #crux
zorz has joined #crux
ivandi has quit [Quit: WeeChat 4.5.1]
ivandi has joined #crux
rever_4192 has joined #crux
rever_4192 has quit [Ping timeout: 276 seconds]
_moth_ has joined #crux
lavaball has quit [Remote host closed the connection]
lavaball has joined #crux
serpente has joined #crux
_whitelogger has joined #crux
<frinnst> woah, sysup'iung crux to core/3.8 broke pam in an interesting way
<frinnst> sudo broken, unable to login as root :D
<frinnst> hopefully my sudo'ed prt-get sysup will fix it.
<frinnst> don't try this at home, kids! listen to uncle jaeger and use the iso :D
<frinnst> ah libcrypt.so.1 -> libcrypt.so.2
<jaeger> :D
<frinnst> if I wasnt an idiot i'd had started a root shell before i began but alas
<frinnst> hopefully everyting will rebuild ok :D
<jaeger> Worst case you can fix it with the ISO if needed
<frinnst> I dont have a 3.8 iso written to stick so i'm kinda screwed. will need to revert my btrfs rootfs to a snapshot
<cruxbridge> <tim> boot into single user mode and just rebuild sudo there?
<frinnst> yeah but whats the fun in that? :)
<cruxbridge> <tim> well, if you put it like that :p
<frinnst> I dont think i've upgraded with an iso on this box ever.. maybe once or twice with my original x86_64 iso
<cruxbridge> <tim> I usually do the same here :)
kh1b has joined #crux
<cruxbridge> <tim> btw, one gotcha in opt that I should add on the TODO list as done is this topic here https://discourse.gnome.org/t/dealing-with-glib-and-gobject-introspection-circular-dependency/18701
<cruxbridge> <tim> there is glib-introspection in opt now for that reason, this might be easy to miss
<frinnst> cheers
<frinnst> ah right, I have "addcommand sudo pkgadd" in my prt-get.conf so all my installs fail
<frinnst> :D
<frinnst> im such a tool
<jaeger> oops
serpente has quit [Remote host closed the connection]
kh1b has quit [Ping timeout: 240 seconds]
<jaeger> If you have some other livecd or network boot or whatever you could use that instead of the 3.8 ISO
<jaeger> Just something temporary so you wouldn't have to revert your rootfs entirely
<ivandi> well, i tried it at home, but in a chroot, so it wasn't that bad :)
<ivandi> btw, python3-setuptools failed to build after python3 upgrade :(
<frinnst> booted an 3.7 iso
<frinnst> python3 took like 30mins running tests? gave up and fetched the rc iso and pkgadded. linux-pam depends on it
<cruxbridge> <tim> ivandi: bootstrapping a working setuptools from pip is the only thing that worked for me now that they start to deprecate it
<cruxbridge> <tim> frinnst: I enabled pgo for python, hence its running tests, but it comes back more optimized. Since python isn't updated to often it's not too bad imho, but surely adds up
<cruxbridge> <tim> ivandi: didn't you report the runtime level switching issue a while ago? It should be fixed now too
lavaball has quit [Remote host closed the connection]
<frinnst> when I tried building it in a 3.7 install chroot it failed a lot of tests and took aaaaaaages
<frinnst> after booting up, it builds fine again
<frinnst> yay ruby sucks: /tmp/ruby-3.4.1-1-work/src/ruby-3.4.1/ruby: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
<frinnst> builds a broken bin
<cruxbridge> <tim> sounds like you got something else stuck on an older openssl lib, it builds fine for me in a container
<cruxbridge> <tim> do you need a package for that?
<frinnst> nah just cleaning up
<frinnst> starting a rebuild of everything
<frinnst> only ruby in revdep so I guess I assumed wrong
<frinnst> revdep isnt as powerful today as it was, say, 10+ years or so ago
<frinnst> python is everywhere now and hard to detect broken stuff i guess
<cruxbridge> <tim> there is pip3 check which can help, but it just lists whatever a python module has specified in its buildfile
<cruxbridge> <tim> do you have that rather long pipe command to check for packages to rebuild that link against that old libcrypt.so.1?
rever_4192 has joined #crux