2020-12-18T02:30:35 #kisslinux it feels like the kernel is recompiling everything when all I did was changing one config :| 2020-12-18T02:39:44 #kisslinux i wonder if busybox diff complaining about unknown option -I causes it, or if kernel building just does that 2020-12-18T05:29:51 #kisslinux is xterm not in the repos? I swear I had it before 2020-12-18T09:54:39 #kisslinux Anyone had any issue with amd-vi being unable to read/write to iommu? I get the error upon boot, and its preventing me from booting kiss linux.. 2020-12-18T09:57:33 #kisslinux * sad_plan[m] uploaded an image: IMG_20201213_215849.jpg (37KiB) < https://matrix.org/_matrix/media/r0/download/privacytools.io/NZkemJyiiZHACvfHLNfdlbZO/IMG_20201213_215849.jpg > 2020-12-18T09:57:43 #kisslinux Theres the error if its of any case 2020-12-18T12:34:07 #kisslinux Any word on Dylan's whereabouts yet? 2020-12-18T12:34:38 #kisslinux Haven't visited this channel in ages, but I read from the logs and based on his lack of git activity that he seems to have gone off the grid. 2020-12-18T12:40:55 #kisslinux no word yet. 2020-12-18T12:47:29 #kisslinux ok, thanks. 2020-12-18T14:15:21 #kisslinux anybody know if the init framework's portability is meant to span BSDs as well? https://github.com/kisslinux/init/blob/master/lib/init/rc.boot#L103 the `-p` command is Linux specific 2020-12-18T15:41:18 #kisslinux I can't for the life of me figure out how to get the PARTUUID of my GUID partition using /just/ busybox tools installed. Anybody know if there's a way to get this from the kernel? I can't even get it from fdisk 2020-12-18T15:41:42 #kisslinux mdev doesn't mount /dev/disk/by-partuuid since it's seemingly not available? not sure 2020-12-18T15:42:33 #kisslinux I don't know of a way to get PARTUUID without actual util-linux 2020-12-18T15:42:59 #kisslinux but you can just build util-linux blkid and run it once, save the PARTUUID, and then not have to deal with util-linux again 2020-12-18T15:43:47 #kisslinux also I don't see a way that the sysctl command could be made portable to BSDs cuz they use -f for specifying file and linux sysctl doesn't have -f, although I guess the correct flag could be chosen based on uname? 2020-12-18T15:45:20 #kisslinux ah ok, thanks for confirming E5ten - I didn't want to spin my wheels any longer if there wasn't any actual way 2020-12-18T15:45:47 #kisslinux np 2020-12-18T16:33:32 #kisslinux onodera and sdssdsd1 i've merged your PRs (blender, icu/webkitgtk) in my fork of community since it looks like dylanaraps is busy 2020-12-18T16:39:17 #kisslinux figured out why my kiss manifest was broken 2020-12-18T16:39:26 #kisslinux micr0: nice 2020-12-18T16:39:28 #kisslinux kiss depends on busybox sh and does not work with bash 2020-12-18T16:40:06 #kisslinux any news on dylan yet tho? 2020-12-18T16:40:39 #kisslinux not that I've seen. I assume we will hear from him after the new year 2020-12-18T16:43:00 #kisslinux i've seen this in enough projects around a single person, so it will be a good test of the claim that the project has a bus factor of '0' not '1' because its understandable by a single person 2020-12-18T16:50:09 #kisslinux this really threw me for a loop: https://github.com/kisslinux/kiss/blob/master/kiss#L1277 -- post_install is hardcoded to run everytime but that's not how the hooks typically work 2020-12-18T16:50:16 #kisslinux unless, I'm misunderstanding something 2020-12-18T16:51:00 #kisslinux it's not enough to simply put a pre-build or whatever in the package repo, you need to use KISS_HOOK 2020-12-18T16:51:19 #kisslinux but you can get away with putting post-install in the package repo, because that line will execute it 2020-12-18T16:51:44 #kisslinux (you can also add additional post-install options in general with KISS_HOOK) 2020-12-18T16:53:22 #kisslinux micr0: what goes wrong with using bash to run kiss? afaik the intent is that kiss only uses POSIX shell features, so it should work with bash too 2020-12-18T16:56:10 #kisslinux E5ten try using `kiss owns` with /bin/sh set to bash using kiss alternatives 2020-12-18T16:56:32 #kisslinux I'm not on kiss lol, I'll need your output 2020-12-18T16:56:33 #kisslinux so, technically, it might not be 'kiss' the single script, but one of the "extensions" that ship with kiss 2020-12-18T16:56:39 #kisslinux output is nothing, -1 2020-12-18T16:57:29 #kisslinux i tried strace -e open but saw nothing out of the ordinary 2020-12-18T16:58:05 #kisslinux can you run it with -x and dump stdout and stderr to a file and then send that here? 2020-12-18T16:58:19 #kisslinux I guess ideally once with bash, and once with busybox sh, so I can compare 2020-12-18T16:59:33 #kisslinux E5ten set the shebang to #!/bin/sh -ex and redirect stderr to stdout and paste? 2020-12-18T17:00:52 #kisslinux I guess so yeah, maybe also change the line "$util" "$@" where it runs the other tools from to start with sh -x so those have xtrace enabled too? 2020-12-18T17:01:19 #kisslinux http://ix.io/2IA3 => busybox sh 2020-12-18T17:01:33 #kisslinux http://ix.io/2IA5 => bash sh 2020-12-18T17:04:19 #kisslinux ok I think I see the issue, but just to make sure I'm not wrong, what's the exact command you ran for these? 2020-12-18T17:05:55 #kisslinux kiss owns /usr/share/terminfo/b/bantam 2020-12-18T17:06:50 #kisslinux but in terms of what the problem seems to be, POSIX allows a leading // to be treated specially, and bash seems to do that, so when kiss-owns does `cd -P "$KISS_ROOT/${1%/*}"`, since $KISS_ROOT is / it does cd -P //path, and then in bash $PWD will also have the leading //, because it's special and doesn't get resolved to a single / like it would if it weren't leading 2020-12-18T17:07:43 #kisslinux did that message go through correctly? matrix did some formatting stuff with it and I know in the past when it's done that it's sometimes led to it not sending correctly 2020-12-18T17:07:55 #kisslinux yeah it is readable and good to me E5ten 2020-12-18T17:07:59 #kisslinux btw what client are you using for matrix? 2020-12-18T17:08:00 #kisslinux great 2020-12-18T17:08:06 #kisslinux element in browser 2020-12-18T17:08:09 #kisslinux cool 2020-12-18T17:08:51 #kisslinux but yeah I think the solution is to change the line in kiss-owns where it does cd -P "$KISS_ROOT/${1%/*}" to remove "trailing" slashes from $KISS_ROOT 2020-12-18T17:08:59 #kisslinux so that a double slash doesn't appear 2020-12-18T17:09:49 #kisslinux probably "${KISS_ROOT%${KISS_ROOT##*[!/]}}/${1%/*}" 2020-12-18T17:09:55 #kisslinux oh god that message probably got fucked up 2020-12-18T17:13:14 #kisslinux micr0: http://ix.io/2IA9 try this 2020-12-18T17:17:23 #kisslinux E5ten didnt fix it :( 2020-12-18T17:17:42 #kisslinux but probably a thing we want anyway, doubleslash is important 2020-12-18T17:18:46 #kisslinux but this isn't wanted double slash, this is double slash just because KISS_ROOT=/ but it's also having a trailing slash added 2020-12-18T17:19:15 #kisslinux could you send the xtrace output again with bash and that change? because I don't really understand how that's not fixing it 2020-12-18T17:20:39 #kisslinux oh wait a second, there's already code in kiss itself to ensure KISS_ROOT doesn't end with a slash, so I'm not sure how this is happening with kiss-owns 2020-12-18T17:21:54 #kisslinux E5ten its the same output as before 2020-12-18T17:22:05 #kisslinux http://ix.io/2IA5 2020-12-18T17:23:33 #kisslinux can you add a line above the cd -P that just echo's the part of the cd -P before the "/${1%/*}" to see what is getting put before the / between the vars? 2020-12-18T17:23:52 #kisslinux ohhhh wait a second 2020-12-18T17:24:13 #kisslinux ok change it back, and just remove the / between $KISS_ROOT and ${1%/*} 2020-12-18T17:24:31 #kisslinux or actually hmm, if there's only 1 slash in $1 that'll be an issue 2020-12-18T17:24:56 #kisslinux actually no it won't, because if there's only one slash then it'll be empty, so the / between them will just be a trailing slash 2020-12-18T17:25:12 #kisslinux http://ix.io/2IAe try this 2020-12-18T17:27:19 #kisslinux that works! 2020-12-18T17:27:35 #kisslinux tested on both busybox sh and bash sh 2020-12-18T17:27:38 #kisslinux nice 2020-12-18T17:27:49 #kisslinux gonna submit a PR for that? 2020-12-18T17:28:00 #kisslinux dylanaraps: http://ix.io/2IAe you should apply this, it's necessary for kiss-owns to work correctly with bash 2020-12-18T17:28:13 #kisslinux nah lol too lazy, just gonna hope dylan sees that eventually 2020-12-18T17:28:52 #kisslinux I added to https://github.com/kisslinux/kiss/issues/209 2020-12-18T17:28:52 #kisslinux thanks 2020-12-18T17:29:17 #kisslinux no problem 2020-12-18T17:35:07 #kisslinux i wonder if a similar change will be needed for my permissions issues 2020-12-18T17:35:58 #kisslinux what's the issue? 2020-12-18T17:48:49 #kisslinux when I install a repo (using kiss build repo-jedahan && kiss install repo-jedahan, as an example), even though /var/db/kiss/repos is set to my user permissions, when it merges the permissions are set to root:root 2020-12-18T17:48:53 #kisslinux instead of micr0:micr0 2020-12-18T17:49:09 #kisslinux and that only happens with bash? 2020-12-18T17:51:53 #kisslinux ahh nevermind, its for busybox or bash sh 2020-12-18T17:52:05 #kisslinux its just how kiss works, womp womp 2020-12-18T18:14:47 #kisslinux set a kiss hook to chown it? 2020-12-18T18:22:12 #kisslinux yeah i mean i can do that with post-install or manually but it seems really hacky 2020-12-18T18:22:48 #kisslinux I think generally kiss should preserve permissions when merging from a tarball 2020-12-18T18:22:55 #kisslinux to the filesystem 2020-12-18T18:39:53 #kisslinux neat. when bootstrapping rust 1.48, they reduced the compile time of llvm by 33% by switching to ninja. 2020-12-18T18:40:10 #kisslinux testing out now 2020-12-18T22:05:21 #kisslinux btw I packages noto-sans-jp so I can view japanese gemini content :) 2020-12-18T22:13:13 #kisslinux gemini the http replacement? 2020-12-18T22:21:19 #kisslinux ya