04:31 <cruxbot> [opt.git/3.6]: nvidia: updated to version 510.60.02

04:31 <cruxbot> [compat-32.git/3.6]: nvidia-32: updated to version 510.60.02

08:40 <GazL> Morning all. Is there a problem with the mailing-list archive on crux.nu? Last update was March 15th.

09:12 <SiFuh> Probably fine, since it is still there :-)

09:19 <GazL> Not much use without any recent messages though.

09:27 <dbrooke> It's a low traffic list, I don't think the archive is missing anything.

09:34 <SiFuh> Very low, and the last CRUX digest was on the 6th March

13:28 <fishe_> https://www.irccloud.com/pastebin/YYd63vOD

13:29 <fishe_> error was too long to send as a normal message, but this happens any time I try to install something with cargo

14:16 <farkuhar> fishe_: Are you using rust-bin instead of rust?

14:16 <fishe_> Yes

14:19 <farkuhar> If you can spare the CPU cycles, I'd suggest replacing rust-bin with rust.

14:21 <fishe_> Alright, thanks

14:41 <fishe_> So many things are just inexplicably broken, I don't understand

14:42 <fishe_> I installed crux the right way but 50% of things are just broken

14:42 <fishe_> bash prompt is weirdly fucked up, lib files missing, nothing compiles

14:47 <farkuhar> fishe_: upstream source code is changing so fast, it's a miracle that crux maintainers are able to keep it all in sync. Your experience of widespread breakage is not unusual, due to the difficulty of tracking so many moving targets.

14:48 <farkuhar> Or as SiFuh put it several weeks ago, port quality isn't what it used to be.

14:48 <fishe_> it just leaves me a little confused because i was able to use crux fine for months a little while ago

14:48 <fishe_> and then when i try it again nothing works

14:50 <farkuhar> now I'm curious to know: did you install from the 3.6.1 iso or the latest unofficial iso?

14:52 <farkuhar> due to how long it's been since 3.6.1 was released, running `prt-get sysup` on a fresh install might lead to more breakage than if you'd been updating periodically since 3.6.1 was released.

14:54 <fishe_> I used 3.6.1, I didn't know there were unofficial isos that are newer

14:54 <fishe_> I did run sysup as well; could that have caused a partial upgrade?

14:54 <fishe_> The lib errors cargo gave were from it trying to look for out of date libs

14:55 <farkuhar> If you try to sysup from the original 3.6.1 packages, you might need to run the command several times to resolve all the newer dependencies. Also be sure to run revdep.

14:58 <fishe_> What does revdep do?

14:59 <farkuhar> It checks for incompatibilities in the binaries owned by each installed port. So if a program is linked against an older version of a shared library, revdep will report it, and you can rebuild those ports.

14:59 <ppetrov^^> last i used the unofficial iso, the system would not boot, no idea why

15:00 <fishe_> Also, I've tried running sysup multiple times and though there are packages that are outdated, there are constant errors when compiling. It would be easier to reinstall from an unofficial iso

15:00 <SiFuh> farkuhar: :-P guess I am stuck with that for a long time

15:00 <fishe_> I completely forgot revdep existed, gonna need to start using it

15:03 <farkuhar> One of the other cases that demands manual intervention is when a port is renamed, as happened in the transition wayland-egl to egl-wayland. You can identify such cases by running prtorphan.

15:04 <farkuhar> But of course, you're not likely to have any orphaned ports if you install from the latest unofficial iso.

15:05 <fishe_> dd is flashing, time to try this again

15:05 <fishe_> Third time's the charm?

18:10 <fishe_> Installed from a newer ISO, things are going good so far

18:10 <fishe_> sysup worked fully instead of leaving a broken mess

18:11 <fishe_> Not entirely sure, but I think rust-bin links against an old version of LLVM so if it's updated things stop working

18:45 <fishe_> compiled all of rust just for there to be a footprint mismatch... fml

19:15 <cruxbot> [contrib.git/3.6]: [notify] docker: updated to version 20.10.14

20:15 <fishe_> what do y'all do when there's signature/md5/footprint mismatches? i usually just ignore them

20:22 <farkuhar> fishe_: what kind of footprint mismatch? It's usually safe to ignore "new files", but not "missing files".

20:22 <fishe_> just about always new files

20:22 <fishe_> sucks when they happen because then everything has to recompile

20:24 <farkuhar> Uncomment the line PKGMK_IGNORE_NEW="yes" in /etc/pkgmk.conf, and you should be spared the expense of rebuilding.

20:25 <farkuhar> These days almost nobody is using md5sums, but if you get a signature mismatch, you can report it to the maintainer (in this channel, or #crux-devel, or by email).

20:28 <fishe_> done, ty

21:08 <dbrooke> IIRC the package is still present despite the fottprint mismatches, just not installed, so if they're only new files you can pkgadd it without recompiling

21:36 <fishe> Alacritty wants to use outdated LLVM libs that don't exist on my install anymore, and even after recompiling it's still looking for libLLVM-13

22:20 <farkuhar> fishe: do you have sccache installed? I'm wondering if your previous build attempt left some rust crates hanging around, and the latest attempt is not bothering to check whether these artifacts are for the right version of LLVM.

22:41 <fishe90> farkuhar I don't have sccache installed