💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2020-10-09.txt captured on 2023-01-29 at 04:00:09.
⬅️ Previous capture (2021-12-17)
-=-=-=-=-=-=-
2020-10-09T04:46:51 #kisslinux <dylanaraps> E5ten: Fixed, thanks
2020-10-09T04:46:56 #kisslinux <dylanaraps> dilynm: Added prompt back
2020-10-09T04:47:44 #kisslinux <dylanaraps> Also fixed xcb-proto
2020-10-09T04:56:25 #kisslinux <dylanaraps> rust 1.47 is compiling (:
2020-10-09T05:09:55 #kisslinux <dylanaraps> Rust 1.47.0 is giving me some pain. Pushed it to testing repository for now. Working on fix.
2020-10-09T05:12:12 #kisslinux <dylanaraps> See: https://github.com/kisslinux/repo/issues/228
2020-10-09T05:18:05 #kisslinux <dylanaraps> onodera: Send a log of the package manager output?
2020-10-09T05:18:57 #kisslinux <dylanaraps> dilynm: You too if possible
2020-10-09T06:08:38 #kisslinux <konimex> dylan: unfortunately I can't reproduce the problem
2020-10-09T06:09:34 #kisslinux <konimex> now let's see if the build would suddenly fail on stage 1
2020-10-09T06:09:59 #kisslinux <dylanaraps> The build fails just after the bootstrap part.
2020-10-09T06:10:04 #kisslinux <dylanaraps> When it compiles the libc crate.
2020-10-09T06:10:16 #kisslinux <dylanaraps> Build passes this stage if I disable our musl patch.
2020-10-09T06:10:30 #kisslinux <dylanaraps> Currently 30~ minutes into build without the patch.
2020-10-09T06:12:11 #kisslinux <dylanaraps> We'll see how this goes.
2020-10-09T06:12:43 #kisslinux <dylanaraps> The only related change I can see if rust + the libc crate is that it now supports static linking with glibc.
2020-10-09T06:12:52 #kisslinux <dylanaraps> ie, code around crt-static changed
2020-10-09T06:13:03 #kisslinux <dylanaraps> s/if/in/
2020-10-09T06:13:22 #kisslinux <konimex> where did you get that patch from? the only patch I applied to wyverkiss is llvm-clang, libressl, and one little sed to make sure crt-static is disabled by default
2020-10-09T06:13:47 #kisslinux <dylanaraps> We've had this patch for upwards of a year now.
2020-10-09T06:14:07 #kisslinux <dylanaraps> It was submitted by the ataraxia linux developer.
2020-10-09T06:14:18 #kisslinux <dylanaraps> It replaced an even larger patch we were using.
2020-10-09T06:14:52 #kisslinux <dylanaraps> This is why I've disabled the patch for this build. Need to know if the issue is on our side or in rust.
2020-10-09T06:15:24 #kisslinux <dylanaraps> I may need to add back the crt-static default change though (what you use a sed call for)
2020-10-09T06:21:11 #kisslinux <kinkinkijkin> does kiss support btrfs or only ext/dosfs/xfs?
2020-10-09T06:21:27 #kisslinux <kinkinkijkin> if the latter ill make an issue to request btrfs
2020-10-09T06:22:26 #kisslinux <dylanaraps> btrfs-progs is in community
2020-10-09T06:22:41 #kisslinux <dylanaraps> It's not a matter of "does kiss support"
2020-10-09T06:23:01 #kisslinux <kinkinkijkin> yesyes i know
2020-10-09T06:23:16 #kisslinux <dylanaraps> It's just a matter of; is the software packaged and does it work?
2020-10-09T06:23:24 #kisslinux <kinkinkijkin> it's a common wording for that
2020-10-09T06:24:03 #kisslinux <dylanaraps> You can use 'kiss s <query>' to search for packages. Globbing is supported so you could do: 'kiss s *btrfs*'
2020-10-09T06:24:33 #kisslinux <dylanaraps> Also handy is: 'cd $(kiss s pkg)'
2020-10-09T06:25:02 #kisslinux <kinkinkijkin> also the kiss install page says support so i was just using the word in there as im leafing through it right now as i set up a kiss chroot inside of fedora for the purpose of porting packages using my dev environ instead of my laptop with kiss on it
2020-10-09T06:25:48 #kisslinux <dylanaraps> Yeah
2020-10-09T06:49:03 #kisslinux <claudia02> morning
2020-10-09T06:49:55 #kisslinux <claudia02> I have found a bugreport about my issue "Cpu frequenzy not scaling up since kernel 5.8". With no solution yet though.
2020-10-09T06:49:57 #kisslinux <claudia02> https://bugzilla.kernel.org/show_bug.cgi?id=209069
2020-10-09T11:38:55 #kisslinux <cemkeylan> Finally, C version of sysmgr works
2020-10-09T14:09:05 #kisslinux <kinkinkijkin> kiss installs real fast considering it's source-based
2020-10-09T14:25:00 #kisslinux <dilyn> dylanaraps: re kiss u failure; there isn't anything really printed to stdout besides what onodera reported
2020-10-09T14:25:58 #kisslinux <dilyn> I did `kiss u` and >2 packages were ready to update (from a fresh 9-2 chroot) and it built the first one with no problems, and then it said 'pkg (second package) has not been built' and exits
2020-10-09T14:26:07 #kisslinux <dilyn> it repeated this for the remainder of packages
2020-10-09T14:29:32 #kisslinux <dilyn> steps to reproduce: download latest chroot tarball, clone kisslinux/repo; export KISS_PATH=repo/testing:repo/core:repo/extra:repo/xorg; kiss u && kiss u. should build & install binutils, and report an error for bison
2020-10-09T14:41:11 #kisslinux <konimex> dylan: can you reproduce this building firefox with rust 1.47.0? https://termbin.com/zsr5 (look for E0425)
2020-10-09T16:50:55 #kisslinux <E5ten> dylanaraps: while the guy in the shebang thread of pure-bash-bible is maybe being a bit rude lol, I do think his reasoning seems sound
2020-10-09T16:51:22 #kisslinux <E5ten> Like someone being able to set PATH to somewhere with a compromised version of bash seems like a security risk
2020-10-09T16:51:39 #kisslinux <E5ten> Hardcoding #!/bin/bash seems better than that
2020-10-09T18:18:46 #kisslinux <kinkinkijkin> konimex I was told to ask here, installing kiss+wyverkiss and getting a lot of c compiler cannot create executables
2020-10-09T18:18:58 #kisslinux <kinkinkijkin> I just did this process on my desktop and never got this so I'm confused
2020-10-09T18:22:36 #kisslinux <kinkinkijkin> actually nevermind, I had a typo in my global profile
2020-10-09T18:35:06 #kisslinux <merakor> E5ten: someone being able to install a compromised bash and change my user's PATH implies bigger security issues than not using hardcoded paths
2020-10-09T18:36:21 #kisslinux <merakor> At that point your system is already compromised what difference does it make to hardcode bash
2020-10-09T20:13:19 #kisslinux <dilyn> dylanaraps: the prompt is in fact back but seems a little bugged
2020-10-09T20:13:56 #kisslinux <dilyn> I just built automake and kiss went and built autoconf+perl as deps. They got installed as deps, and then after it built automake it prompted me to install all three packages
2020-10-09T20:14:31 #kisslinux <dilyn> and then after I pressed 'enter' on the prompt, at the end (after installing automake in this example), it prints "successfully built all packages" (:
2020-10-09T20:16:35 #kisslinux <dilyn> it looks like this basically
2020-10-09T20:16:46 #kisslinux <dilyn> http://ix.io/2AeZ
2020-10-09T20:18:01 #kisslinux <sh4rm4^bnc> -> Using '/usr/bin/sls' (to become root)
2020-10-09T20:18:06 #kisslinux <sh4rm4^bnc> what's sls ?
2020-10-09T20:18:17 #kisslinux <dilyn> i believe illiliti made it?
2020-10-09T20:18:25 #kisslinux <dilyn> it's a doas/sudo replacement
2020-10-09T20:19:09 #kisslinux <dilyn> it's basically like if your sudo/doas conf just said don't prompt for password
2020-10-09T20:19:18 #kisslinux <sh4rm4^bnc> do you need to enter you root password there? or does kiss switch to some non-root user to build packages?
2020-10-09T20:19:31 #kisslinux <sh4rm4^bnc> ah
2020-10-09T20:24:32 #kisslinux <kinkinkijkin> can't switch to a non-root user automatically when the distro doesn't come with users
2020-10-09T20:26:42 #kisslinux <sh4rm4^bnc> that's the main reason i didnt implement root-less package installs on sabotage
2020-10-09T20:27:09 #kisslinux <sh4rm4^bnc> it seems like too much of a hassle to expect users to create some build user before using the package manager
2020-10-09T20:38:47 #kisslinux <sh4rm4^bnc> so sls is basically a su without password prompt? i.e. anyone can become root?
2020-10-09T20:55:31 #kisslinux <dilyn> anyone who's in the right group
2020-10-09T20:55:51 #kisslinux <dilyn> mine is for instance root:dilyn so only me/people in the dilyn group
2020-10-09T20:55:57 #kisslinux <dilyn> could be wheel or even floppy...
2020-10-09T21:16:46 #kisslinux <E5ten> dylanaraps: in k's str.h, str_from allocates the return value of snprintf, but I think it should be allocating that + 1, because that's the length param used in the following snprintf call
2020-10-09T21:18:59 #kisslinux <E5ten> also, in msg() and die(), the puts() call sends a newline to stdout, but fprintf call is to stderr, shouldn't that puts("") be fputc('n', stderr)?
2020-10-09T21:21:56 #kisslinux <E5ten> also, the getline man page says that the buffer it allocates should be freed even when getline fails, so the if (err == -1) condition should free "ver" before it returns NULL
2020-10-09T22:34:56 #kisslinux <dilyn> https://abetterinternet.org/post/memory-safe-curl
2020-10-09T22:35:30 #kisslinux <dilyn> they're implmenting a rust backend for curl
2020-10-09T23:38:10 #kisslinux <sh4rm4^bnc> effing rustards
2020-10-09T23:40:41 #kisslinux <dilyn> when in doubt, rust it out