jaeger changed the topic of #crux to: CRUX 3.6 | Homepage: https://crux.nu/ | Ports: https://crux.nu/portdb/ https://crux.ninja/portdb/ | Logs: https://libera.irclog.whitequark.org/crux/
fishe has quit [Quit: Connection closed for inactivity]
fishe has joined #crux
<fishe> @SiFuh: Even after a full reinstall I'm still getting 404's on packages from your repo
<fishe> It looks like it's only the ones that download from sourceforge which is weird
<SiFuh> Sourceforge is a pain
<SiFuh> It does a lot of redirects
<SiFuh> Which ports?
<fishe> All of the ones that use sourceforge have the issue for me
<fishe> sox, eigen3-plugins, etc
<SiFuh> I don't have those in my repo
<SiFuh> Sure they are not a dependency from another repo?
<fishe> Oh, those are in contrib
<fishe> facepalm
<fishe> libdv uses sourceforge to get the tarball from but it downloads fine
<fishe> But then there are the ports like sox that point somewhere wrong
ocb has quit [Remote host closed the connection]
ocb has joined #crux
SiFuh has quit [Ping timeout: 240 seconds]
SiFuh has joined #crux
fishe has quit [Quit: Connection closed for inactivity]
fishe has joined #crux
ocb has quit [Remote host closed the connection]
ocb has joined #crux
ppetrov^ has joined #crux
fishe has quit [Quit: Connection closed for inactivity]
guido_rokepo has quit [Quit: guido_rokepo]
guido_rokepo has joined #crux
guido_rokepo has quit [Client Quit]
ocb has quit [Remote host closed the connection]
ocb has joined #crux
_moth_ has quit [Ping timeout: 250 seconds]
ardo has quit [Ping timeout: 256 seconds]
ardo has joined #crux
guido_rokepo has joined #crux
fishe has joined #crux
ocb has quit [*.net *.split]
Romster has quit [Ping timeout: 246 seconds]
ocb has joined #crux
Romster has joined #crux
Romster has quit [Ping timeout: 248 seconds]
<fishe> Regarding the Sox port, I've gotten it to download correctly by using "https://sourceforge.net/code-snapshots/git/s/so/$name/code.git/$xtarget.zip"
<fishe> instead of "https://sourceforge.net/code-snapshots/git/s/so/${name}/code.git/\${xtarget}.zip"
<fishe> Can anyone check if sox in contrib builds properly for them? Entirely plausible that something is wrong with my install
Romster has joined #crux
<farkuhar> fishe: =======> Building '/usr/pkgmk/packages/sox#20211029-1.pkg.tar.xz' succeeded.
<fishe> So something is broken on my end
<fishe> I have no clue why, but it 404s a lot of sourceforge links
<fishe> Just tried it again and I have no clue why but now it's working
<fishe> What should I do when there's a signature mismatch?
<fishe> "MISMATCH signify"
<SiFuh> sourceforge.net/code-snapshots/git/s/so/sox/code.git/sox-code-42b3557e13e0fe01a83465b672d89faddbe65f49.zip
<SiFuh> I just tested the URL and it downloaded fine
<jaeger> what actually got downloaded? Is it a zip file or something else?
<SiFuh> fishe: ^
<fishe> im not actually sure what was downloaded, it kinda just started working
<fishe> ladspa is giving me ssl cert errors when I try to install it though
_moth_ has joined #crux
stoffepojken has quit [Quit: ZNC 1.8.2 - https://znc.in]
<fishe> i reinstalled so i wouldn't break things again and i seem to already have broken things
<jaeger> Are you able to install ANY ports or is it only sourceforge downloads breaking?
<fishe> Most sf ports
<jaeger> Can you run 'file' on one of the downloads?
<jaeger> ladspa.org has something wrong with their SSL cert, that's on their end
<jaeger> You could grab the ladspa source via HTTP or from one of the distfile mirrors in the meantime
stoffepojken has joined #crux
<fishe> @jaeger: It didn't download a file when it was 404'ing because it couldn't reach the page
<fishe> I have no clue what changed but it looks like sf mirrors are working now
<stenur> SiFuh: OpenBSD 7.1 released, April 21, 2022
<stenur> Unfortunately limit excessed, i have to wait a week. 7.1 i will do again. Nice artwork fish!
fishe38 has joined #crux
<jaeger> Obviously if there's a 404 there's no download but what about the other times? I'm confused, it sounds like you're describing multiple issues at the same time
<stenur> sox URL works for sure
<fishe> I'm not entirely sure what the issue was itself because now it's not happening
<fishe> But a lot of sourceforge links would return 404
fishe38 has quit [Client Quit]
<stenur> for "dig sourceforge.net" i get 104.18.34.243 and 172.64.153.13
<SiFuh> stenur: not sure. I actually do not use the apm feature on laptops.
ty3r0x has joined #crux
jue has joined #crux
jue has joined #crux
<_moth_> hi all. on my old hardware with intel GMA X3500(Gen4) graphics i got this error in mpv player:
<_moth_> libEGL warning: MESA-LOADER: failed to open crocus: /usr/lib/dri/crocus_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
jue has quit [Ping timeout: 240 seconds]
<_moth_> if i understand correctly this changes affect chipsets with intel GMA Gen3-4 graphics (Gen4) and intel CPU with HD Graphics <= 5200 (Gen5-7)...so no hardware acceleration on all of this devices if crocus driver not enabled at build time since mesa 22.0
<_moth_> fixed mesa Pkgfile with enabled crocus driver support -> http://ix.io/3VJi
<_moth_> Crux 3.6
<fishe> @SiFuh: gtest port in your repo is giving me a 404, is that just my system
Torr has joined #crux
Torr has left #crux [#crux]
ty3r0x has quit [Quit: Konversation terminated!]
SiFuh has quit [Ping timeout: 240 seconds]
<jaeger> Looks like the tag part of the URL (v1.11.0) should be replaced with "release-1.11.0"
<farkuhar> _moth_: nice find regarding mesa 22.0. The official release notes for 22.0.0 clearly indicated that users who wanted stability should wait for 22.0.1, but in light of your phoronix thread the users of older hardware have even more reason to stick with the 21.3 branch for a while.
<farkuhar> webkitgtk returned errors for me after the upgrade to mesa 22.0 ("cannot create EGL context" IIRC), but only on Wayland (X11 worked fine). I thought that error would disappear after the 22.0.1 ("bug fix") release, but no luck.
<farkuhar> so for now I've locked mesa to its last good 21.3 version, but your Pkgfile gives me hope that a clever set of compilation options might bring the 22.0 branch to feature-parity with 21.3
<_moth_> farkuhar: thx for info. it may be preferable to create two packages(mesa-21, and current) to prevent future problem?
<farkuhar> _moth_: good idea. There's already a precedent for that: witness the side-by-side installations of ffmpeg4 and ffmpeg (version 5).
ppetrov^ has quit [Quit: Leaving]
_moth_ has quit [Quit: _moth_]
_moth_ has joined #crux
_moth_ has quit [Client Quit]
groovy2shoes has quit [Quit: Leaving]
groovy2shoes has joined #crux
tilman has quit [Ping timeout: 240 seconds]
tilman has joined #crux