02:18 <fishe> hey there

02:18 <fishe> trying crux again, and upon running efibootmgr i get "EFI Variables are not supported on this system"

02:19 <fishe> efivarfs is modprobe'd and i specified x86_64-efi when installing grub

03:15 <fishe> Took a bit, but i figured it out! just running `modprove efivarfs` does not work, but `mount -t efivarfs none /sys/firmware/efi/efivars` works fine

03:15 <fishe> modprobe*

03:30 <jaeger> Glad you got it sorted :)

10:56 <ppetrov^> guys, may I ask what are the plans about the upcoming 3.7 release, time-wise? I don't want to be _that guy_, asking "are we there yet", but I am certainly curious whether we should expect in a month or so...?

11:04 <SiFuh> Yesterday, jaeger had said that he will push 3.7 to iso.git soon and do a test build.

11:05 <SiFuh> I am awaiting OpenBSD 7.1 which should be launched soon.

11:07 <ppetrov^> cool, thanks! I am considering to migrate another PC to CRUX, so I would rather wait for 3.7

11:07 <ppetrov^> SiFuh, how easy is it to create ports on OpenBSD?

11:08 <SiFuh> Depends, some are quite easy, but most are heavily patched

11:22 <SiFuh> ppetrov^: When you learn the variables it is pretty easy. It compiles just like any other program and then you have to sign the port.

11:23 <SiFuh> The ports are in a tree, and the Makefiles are configured to be aware of every port or Makefile below it.

11:25 <SiFuh> Void Linux has a similar setup but they treat it is a source tree

11:34 <farkuhar> The OpenBSD release cycle is quite regular: every six months you can download a new stable release. You can follow the -CURRENT branch, but even the stable branch gets security patches in between the semiannual releases.

11:40 <farkuhar> The choice between a "rolling release" and semiannual updates is something you can approximate in CRUX. Use ports -u; prt-get sysup for the "rolling release" model, or just download the unofficial ISO every six months and reinstall from that, if you prefer moving at a slower pace. The only downside of the latter choice is that you have to apply security patches manually.

11:55 <ppetrov^> why would i apply security pacthes manually, if I am using the updated ISO?

11:57 <ppetrov^> btw, i kinda prefer to prt-get sysup regularly, because in this way I 'gradually' fix things that break with my own ports. If I wait for 6 months, I will probably have much many things to fix all at once

12:00 <farkuhar> Never touching the ports tree in between installations from the updated iso (i.e., never running ports -u), you would not have knowledge about security fixes in your ports tree.

12:01 <ppetrov^> i have no knowledge of security fixes in my ports tree even now

12:01 <ppetrov^> i just update them every now

12:01 <ppetrov^> and then

12:02 <farkuhar> I meant that by running ports -u, you propagate into your ports tree the information about available updates. If you only took snapshots of the ports tree every six months, then you have to keep up with those CVE notifications some other way.

12:03 <ppetrov^> yes, and if i make a new install every 6 months, I install updated ports

12:04 <ppetrov^> sorry, i feel stupid, i obvious misunderstand something

12:05 <farkuhar> OpenBSD has a mechanism for distributing critical security patches separately from "bleeding edge" software. In CRUX we lump all those updates together, forcing users to effectively follow a "rolling release" model if they want the latest security patches, even if they wish CRUX updates came at a slower pace.

12:08 <ppetrov^> ah, you mean that in the time between two fresh installs (for thos who want slower cycle), there will be no security updates

12:08 <farkuhar> Yes, that's the point I was trying to make. Sorry for the confusing description.

12:08 <ppetrov^> yes of course...

12:08 <ppetrov^> it's kinda obvious, but not for me... as teens say "duuh"

12:09 <ppetrov^> or did they say this some 10 years ago?

12:09 <farkuhar> No idea, maybe you'd better ask stenur (for an official amerikandeutsch perspective)

12:12 <ppetrov^> :D

12:13 <ppetrov^> so when 3.7 comes out, i am advised to install it in chroot environment and test my ports there?

12:14 <ppetrov^> i found this: https://crux.nu/Wiki/ChrootTesting

12:14 <ppetrov^> we'll see how it goes...

16:06 <fishe> might have brought this up a few weeks ago, but im back on crux and rust-bin is compiled against an old version of llvm

16:07 <fishe> im also pretty sure qtile is what was causing audio problems

16:16 <SiFuh> :-P

18:36 <fishe> got through compiling all of rust just for there to be a footprint mismatch

18:36 <fishe> god fucking damn it

18:56 <farkuhar> fishe: the built package should still be present on your disk. If the footprint mismatch doesn't look too worrisome, you can just pkgadd the result of your compilation.

18:57 <fishe> where would those be stored?

19:43 <ppetrov^> what does PKGMK_PACKAGE_DIR=" in /etc/pkgmk.conf say?

23:57 <ichi> hi

23:57 <ichi> i installed crux and its all good so far but i try to install i3 and i3status and it gives me an error

23:57 <ichi> i enabled contrib