💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2021-01-09.txt captured on 2024-05-26 at 16:19:35.
⬅️ Previous capture (2021-12-17)
-=-=-=-=-=-=-
2021-01-09T02:59:32 #kisslinux <midfavila1> any of you guys ever messed around with heirloom m4? 2021-01-09T03:13:38 #kisslinux <acheam> Building the new versions of firefox, rust, llvm right now for repo-bin 2021-01-09T03:13:55 #kisslinux <midfavila1> Based 2021-01-09T09:01:02 #kisslinux <sad_plan> is there any trick to downgrading packages? im trying to build torbrowser, but to configure it, it require autoconf-2.13. autoconf exists in the repo, but its v2.69. its beyond me why torbrowser demands a release from '96, but thats not the issue. if I download the tar.gz file myself, unpack and build/install, i still get the same error. if I fork 2021-01-09T09:01:02 #kisslinux <sad_plan> autoconf, and edit the files to correspond with v2.13, it says it downloads v2.13, but when installing, and listing installed apps, it still says v2.69. what gives? 2021-01-09T09:02:34 #kisslinux <midfavila> I just uninstall whatever modern version I'm using and install 2.13 afterward 2021-01-09T09:07:46 #kisslinux <sad_plan> i did that, I installed 2.69 in the assumtion it worked anyway, but threw the error, so iI fetched the 2.13 tar, and installed it, afer uninstalling 2.69, but still gave me the same error, so I figured id let kiss install it instead, but for whatever reason, it installs 2.69, even though it says it downloads 2.13. im also in the autoconf dir, where 2021-01-09T09:07:46 #kisslinux <sad_plan> 2.13 is specified, so im bypassing $kiss_path to be sure 2021-01-09T09:15:57 #kisslinux <testuser[m]_> sad_plan just build autoconf2.13 inside the torbrowser build dir, then add it at the start of your PATH 2021-01-09T09:16:08 #kisslinux <testuser[m]_> PATH=$PWD/junk/bin:$PATH 2021-01-09T09:23:43 #kisslinux <sad_plan> just the files, or the whole folder? autoconf is built already. does it make any difference if its cleaned? just to be sure. 2021-01-09T09:23:55 #kisslinux <sad_plan> putting the folder into build dir gave same error 2021-01-09T09:24:46 #kisslinux <sad_plan> ah, I just noticed, and autoconf dir already exiist. overwrite it, yes? 2021-01-09T09:40:08 #kisslinux <sad_plan> i overwrote it, and it worked, however, theres an issue I dunno if we can bypass 2021-01-09T09:40:24 #kisslinux <sad_plan> ERROR: Don't know how to translate x86_64-unknown-linux-gnulibc1 for rustc 2021-01-09T09:40:47 #kisslinux <sad_plan> shouldnt the rust patch fix that, or does the patch do other things instead? 2021-01-09T09:46:13 #kisslinux <testuser[m]_> the rust patch is to upgrade packed_simd to compile on newer versions of rust 2021-01-09T09:47:25 #kisslinux <sad_plan> alright, so.. can this be fixed at all, or is there no way around? I mean, that isnt an immens amount of work and troubleshooting 2021-01-09T09:48:25 #kisslinux <testuser[m]_> normal firefox builds fine so i guess tor is using some globc specific stuff 2021-01-09T09:48:26 #kisslinux <testuser[m]_> glibc 2021-01-09T09:50:28 #kisslinux <sad_plan> probaly. how did you guys fix it with firefox? 2021-01-09T09:53:03 #kisslinux <testuser[m]_> firefox doesn't need fixes for musl now 2021-01-09T09:53:22 #kisslinux <testuser[m]_> i said tor might be using glibc specific things cuz it adds a lot over normal firefox 2021-01-09T09:54:02 #kisslinux <sad_plan> my bad. any suggestions? other than ditching it and going for chroot/vm 2021-01-09T10:11:31 #kisslinux <testuser[m]_> nope, no ideas 2021-01-09T10:11:31 #kisslinux <testuser[m]_> Maybe playing with the configure flags would help but i doubt it 2021-01-09T10:12:22 #kisslinux <sad_plan> ok. 2021-01-09T10:13:19 #kisslinux <sad_plan> playing with the config flags is way beyond me, so someone else has to look at that, in any case. ill post the error on github, and leave it open for some time, if in any case someone else got the urge to find a solution to this. 2021-01-09T10:13:26 #kisslinux <sad_plan> thanks anyway C: 2021-01-09T13:35:15 #kisslinux <kiedtl> Has dylan been seen yet? 2021-01-09T13:35:24 #kisslinux <kiedtl> Also, has anyone had any luck with the message on Dylan's site? 2021-01-09T13:36:18 #kisslinux <testuser[m]_> no and no 2021-01-09T13:36:50 #kisslinux <testuser[m]_> i dont think the message means anything 2021-01-09T15:00:44 #kisslinux <mahmutov> kiedtl, message is "A camel is a horse.." ? 2021-01-09T15:02:15 #kisslinux <testuser[m]_> https://dylan.k1ss.org/ 2021-01-09T15:02:17 #kisslinux <testuser[m]_> @freenode_mahmutov:matrix.org 2021-01-09T15:05:34 #kisslinux <mahmutov> ah ok 2021-01-09T16:40:04 #kisslinux <jaafard> Is there a way to install K1SS Linux on a virtual machine? 2021-01-09T16:45:53 #kisslinux <testuser[m]_> yes why not 2021-01-09T16:46:05 #kisslinux <testuser[m]_> you'd do it just like any other distro 2021-01-09T16:47:17 #kisslinux <jaafard> i don't think so 2021-01-09T16:48:02 #kisslinux <jaafard> because kiss linux is installed with tarballs, the installation expects you to already have an os, this won't work in a vm 2021-01-09T16:52:55 #kisslinux <Rio6> ...just mount your virtual drive in whatever and do the same thing 2021-01-09T16:54:28 #kisslinux <jaafard> I don't know how to do that in QEMU. 2021-01-09T16:58:30 #kisslinux <aarng> do you just want to try kiss? 2021-01-09T16:58:37 #kisslinux <jaafard> yes 2021-01-09T16:58:47 #kisslinux <aarng> just try it in a chroot 2021-01-09T17:01:11 #kisslinux <aarng> X should work too and if you like the install, you can always just write it to an actual disk 2021-01-09T17:01:46 #kisslinux <jaafard> alright, that seems cool 2021-01-09T17:02:19 #kisslinux <jaafard> I will totally daily-drive this if I ever get the courage to do the kernel stuff.