[2021-09-10T00:26:18Z] anybody else having a problem installing binaries as setuid with kiss? just had an issue reinstalling opendoas [2021-09-10T00:29:20Z] oh, curious...?? [2021-09-10T01:08:08Z] i recently packaged a setuid program and it was fine [2021-09-10T01:15:40Z] the opendoas package doesn't seem to make itself setuid [2021-09-10T01:16:16Z] -rwsr-xr-x 1 root root 112072 Sep 9 20:13 /usr/bin/doas [2021-09-10T01:25:00Z] orly... [2021-09-10T01:25:11Z] then this is a me problem. hmhmhm [2021-09-10T02:28:18Z] dilyn: unfortunately that tic part of yours don't work in my build [2021-09-10T02:36:51Z] ...and now my rebuilt netbsd-curses is broken [2021-09-10T03:01:05Z] https://github.com/kiss-community/community/pull/675/files [2021-09-10T03:01:09Z] this looks awfully familiar... [2021-09-10T03:02:59Z] just some casual MIT license violations, nothing to see here [2021-09-10T03:03:35Z] oof and phoebos found an issue in it [2021-09-10T03:03:35Z] lol, my repo doesn't even have a license [2021-09-10T03:03:46Z] then its just some causal IP violations [2021-09-10T03:03:58Z] maybe i should add one to screw with people [2021-09-10T03:04:27Z] $ cat LICENSE [2021-09-10T03:04:45Z] nah, i meant that the packaging was pulled straight from my personal repo [2021-09-10T03:05:00Z] > by using this software, the user forfeits the right to their PC to nihal jere [2021-09-10T03:05:08Z] noocsharp: ik, you interupted my really bad joke [2021-09-10T03:06:08Z] i wonder if a court would enforce that [2021-09-10T03:06:47Z] probably not [2021-09-10T03:07:24Z] its unlikely, but at least somewhat possible that they could have written that themselves, and it just happened to be the same as yours [2021-09-10T03:07:31Z] given that its a fairly straightforward build file [2021-09-10T03:08:05Z] or the court might just not see it as property after explaining for 20 minutes what a build file actually is [2021-09-10T03:08:25Z] but I Am Not A Lawyer(tm) [2021-09-10T03:08:31Z] but only i'm stupid enough to pull raw source files straight from cgit [2021-09-10T03:08:46Z] instead of downloading the tarball or using git [2021-09-10T03:09:16Z] i would have added it to community, but i thought it was a stupid hack to package it [2021-09-10T03:11:50Z] yeah why did you do that? [2021-09-10T03:12:03Z] oh because its in a big repo? [2021-09-10T03:14:19Z] yeah, and it hasn't been updated in several years [2021-09-10T03:14:40Z] actually, i could have just copied the files into a files subdirectory... thats what i did with bsdfmt [2021-09-10T03:29:15Z] TIL you can control monitor settings from your computer [2021-09-10T03:29:22Z] https://www.ddcutil.com/ [2021-09-10T03:34:48Z] Hi [2021-09-10T03:40:49Z] hello [2021-09-10T03:41:45Z] i2c over hdmi? vga? [2021-09-10T03:45:09Z] indeed [2021-09-10T04:26:02Z] noocsharp: wdym? [2021-09-10T04:46:23Z] konimex: interesante. how doesn't it work? [2021-09-10T04:46:30Z] I know it was finicky but I've forgotten [2021-09-10T04:47:09Z] a lot of my builds are seemingly broken; for instance, freetype's pkgconfig file reports the wrong version! lmao [2021-09-10T05:00:14Z] Can someone on a regular kiss system build automake [2021-09-10T05:06:59Z] dilyn: netbsd-curses still fails to find foot terminfo from my end [2021-09-10T05:07:19Z] and when I rebuilt netbsd-curses suddenly TERM=linux no longer works so there's that [2021-09-10T05:07:29Z] hhhmmmmm [2021-09-10T05:07:50Z] I *think* i had this same problem, at some point when I was doing stuff a couple weeks ago... [2021-09-10T05:11:26Z] i haven't checked in any of my env stuff in a long while so if I WERE using a TERM variable I don't recall it :X [2021-09-10T05:17:45Z] testuser: nop; help2man complaint? [2021-09-10T05:18:11Z] yeah [2021-09-10T05:18:14Z] it works fine for me but no one else [2021-09-10T05:18:44Z] :thinking: [2021-09-10T05:19:03Z] this is just some vanilla kiss chroot i keep around so you must've done something special? [2021-09-10T05:19:18Z] no i tried on my default chroot too [2021-09-10T05:19:33Z] i guess its sorta out of date but all related packages to automake should be up to date [2021-09-10T05:19:36Z] ill try with a new one [2021-09-10T05:21:22Z] lmfao [2021-09-10T05:21:37Z] open up the ChangeLog for automake and peep that update from 2012-04-12 [2021-09-10T05:21:48Z] might be a regression of some kind [2021-09-10T05:22:07Z] 2012 ? [2021-09-10T05:22:12Z] yeah [2021-09-10T05:22:30Z] just checked with -j1/2/3/4, it doesn't seem to be [2021-09-10T05:24:13Z] but it's been building fine since 1 year [2021-09-10T05:24:18Z] https://github.com/kisslinux/repo/blob/6dfff99f4cbb79b3ec378a2e501452c01c4127ed/core/grub/files/help2man i guess i could try this [2021-09-10T05:25:24Z] that would be suitable probably considering the problematic file is doc/help2man [2021-09-10T05:28:06Z] tried it, then it complains about 'cannot get --help' from aclocal [2021-09-10T05:28:07Z] hmhm [2021-09-10T05:28:31Z] i forgor 💀 [2021-09-10T05:28:33Z] the issue is that [2021-09-10T05:28:36Z] automake doesnt work [2021-09-10T05:28:50Z] complains about some signal stuff [2021-09-10T05:28:58Z] 1 sec [2021-09-10T05:29:12Z] mfw [2021-09-10T05:29:50Z] https://libera.irclog.whitequark.org/kisslinux/2021-09-04#30790284; [2021-09-10T05:32:29Z] https://libera.irclog.whitequark.org/kisslinux/2021-09-04#30790404; they get it [2021-09-10T05:32:54Z] guess i'll check on wyverkiss as well just for sanity [2021-09-10T05:34:25Z] love having to build three packages just to build a single package that allows me to *checks notes* insanely build packages [2021-09-10T05:35:08Z] uuuhhh [2021-09-10T05:35:11Z] automake builds fine for me [2021-09-10T05:35:16Z] on wyverkiss [2021-09-10T05:35:19Z] kekw :V :V :V [2021-09-10T05:35:57Z] rebuild perl [2021-09-10T05:35:58Z] then it wont [2021-09-10T05:36:21Z] so perl broke somehow due to external factors [2021-09-10T05:37:14Z] my working binary was built on july 11 [2021-09-10T05:37:15Z] oh god if this perl reinstall breaks this chromium build smh [2021-09-10T05:38:02Z] i'll install it in a safe place :V [2021-09-10T05:39:14Z] maybe its gcc 11 ? it was updated on july 28 [2021-09-10T05:39:54Z] i guess we could just patch automake to not register handlers for SIGHUP but idk what that would break [2021-09-10T05:40:08Z] yeah rebuilt perl and it's fine [2021-09-10T05:40:25Z] so... [2021-09-10T05:40:31Z] but galaxynova on wyverkiss couldnt build it so it cant be a gcc issue either [2021-09-10T05:40:32Z] i have no idea what the common denominator might be here [2021-09-10T05:41:01Z] maybe automake is trying super hard to get gpl software on my machine so it's bending the rules of reality to function properly [2021-09-10T05:43:50Z] ok so all signal handling is broken [2021-09-10T08:37:49Z] Hello there! [2021-09-10T08:38:10Z] I'm having a problem which may or may not have to do something with KISS Linux but with the wayland adoption. [2021-09-10T08:38:29Z] What is it [2021-09-10T08:38:45Z] When running command "wal -i wall/wall0.jpg", I get error "FileNotFoundError: [Errno 2] No such file or directory" [2021-09-10T08:38:56Z] When running command "wal -i wall/wall0.jpg", I get error "FileNotFoundError: [Errno 2] No such file or directory: 'swaymsg'" [2021-09-10T08:39:09Z] So would I have to build swaymsg? [2021-09-10T08:39:40Z] swaymsg is provided by sway, and this "wal" program seems to talk to swaymsg to set the backgroun [2021-09-10T08:39:52Z] oh wal is pywal ? [2021-09-10T08:40:16Z] yes, pywal [2021-09-10T08:40:38Z] I have the sway-tiny package currently installed, is that a problem? [2021-09-10T08:41:26Z] so /usr/bin/swaymsg doesnt exist ? [2021-09-10T08:42:16Z] "find: /usr/bin/swaymsg: No such file or directory" :( [2021-09-10T08:42:39Z] build regular sway i guess, dylan might've removed swaymsg from the tiny fork [2021-09-10T08:43:14Z] Building regular sway package will break my current installation [2021-09-10T08:43:22Z] why [2021-09-10T08:43:34Z] Because I don't have any cron daemon or something [2021-09-10T08:43:43Z] And configuring all that the tty only is a pain [2021-09-10T08:44:09Z] i guess you could tell pywal to use another wallpaper setter [2021-09-10T08:44:09Z] Instead, is it possible to disable the wallpaper setting thing? [2021-09-10T08:44:48Z] Wait.. I found it! [2021-09-10T08:45:03Z] Yep. It worked! [2021-09-10T08:45:09Z] Thanks! [2021-09-10T08:45:24Z] nice [2021-09-10T08:46:41Z] Time for playing with pywal [2021-09-10T08:47:26Z] BTW, have you tested waybar on KISS Linux? [2021-09-10T08:47:50Z] no [2021-09-10T08:47:57Z] ok [2021-09-10T08:50:12Z] Dang gtkmm is not in KISS Linux repo [2021-09-10T08:51:12Z] gtk2 isnt there so how would gtkmm be there [2021-09-10T08:51:16Z] those are gtk2 bindings right [2021-09-10T08:51:37Z] Its not good for a package like Waybar to use gtk2 [2021-09-10T08:51:46Z] Testing bemenu.. [2021-09-10T08:57:10Z] bemenu also doesn't work [2021-09-10T08:57:23Z] is there a status bar that actually works? [2021-09-10T09:00:15Z] bemenu works [2021-09-10T09:00:37Z] `bemenu-run` [2021-09-10T09:00:44Z] its not a status bar its a launcher [2021-09-10T09:00:48Z] How? [2021-09-10T09:01:06Z] I tried doing "bemenu" and it shows.. nothing. [2021-09-10T09:01:11Z] oooooooh [2021-09-10T09:03:18Z] Yes! It works [2021-09-10T09:03:20Z] Great [2021-09-10T09:04:59Z] Now its time for a status bar [2021-09-10T09:17:18Z] Waybar doesn't compile due to gtkmm, nwg-panel also doesn't compile too [2021-09-10T09:17:30Z] Is mercurial present in the KISS repository [2021-09-10T09:17:33Z] or the community one? [2021-09-10T09:18:06Z] Or how can I clone a package from hg.sr.ht? [2021-09-10T09:19:06Z] pip install mercurial [2021-09-10T09:19:17Z] OK [2021-09-10T09:19:23Z] Lets see [2021-09-10T09:19:27Z] or this outdated package https://github.com/kiss-community/graveyard/tree/main/community/mercurial [2021-09-10T09:20:00Z] naaaaaaaaaaaaaaah [2021-09-10T09:20:07Z] no outdated packges allowed [2021-09-10T09:20:40Z] P.S. i hope libwayland-dev, libgtk-3-dev pkg-config and meson are also present [2021-09-10T09:23:41Z] isn't meson already in kiss main? [2021-09-10T09:24:41Z] yep it is [2021-09-10T09:24:49Z] but what about the libraries [2021-09-10T09:25:09Z] if the libraries didnt exist then your sway wouldnt have built [2021-09-10T09:25:24Z] OOOH [2021-09-10T09:25:45Z] "FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/share/man/man1'" when building wofi [2021-09-10T09:27:59Z] oops [2021-09-10T09:28:04Z] I'm building the wrong thing sorry [2021-09-10T09:31:12Z] there's no yaml [2021-09-10T10:08:13Z] Hello again! [2021-09-10T10:08:26Z] I want to have information about how to change the border thickness and color in sway? [2021-09-10T10:08:35Z] I'm asking this question because the man pages in sway-tiny are missing [2021-09-10T10:11:16Z] Also when using mold as the system linker, grim fails the compile [2021-09-10T10:11:40Z] I haven't used sway-tiny, but I reckon it's the same as sway. [2021-09-10T10:11:46Z] It says "clang-12: error: argument unused during compilation: '--ld-path=/usr/bin/mold' [2021-09-10T10:12:07Z] x4n: man page online https://www.mankier.com/5/sway [2021-09-10T10:15:11Z] soliwilos I don't know how to do it [2021-09-10T10:15:54Z] no information about how to change color :( [2021-09-10T10:18:16Z] Look at the client.background section. [2021-09-10T10:19:21Z] client.focused for focused windows and others for other states. [2021-09-10T10:19:51Z] border color is done with those. [2021-09-10T10:19:56Z] oh [2021-09-10T10:19:57Z] nice [2021-09-10T10:20:42Z] wait [2021-09-10T10:20:58Z] in which format is the color supposed to provided? [2021-09-10T10:21:04Z] hex? rgb? [2021-09-10T10:21:31Z] hex, prefixed with #. [2021-09-10T10:22:01Z] #000000 and the like. [2021-09-10T10:22:02Z] alright [2021-09-10T10:22:35Z] The defaults are given in the manpage there. [2021-09-10T10:24:56Z] So will I have to do like "client.focused #000000"? [2021-09-10T10:29:02Z] plz help [2021-09-10T10:44:45Z] Sorry, was busy. [2021-09-10T10:45:11Z] As far as I rerember you need to specify all the colors. [2021-09-10T10:45:34Z] s/rerember/remember/ [2021-09-10T10:45:34Z] As far as I remember you need to specify all the colors. [2021-09-10T10:46:03Z] So "client.focused #4c7899 #285577 #ffffff #2e9ef4 #285577" [2021-09-10T10:46:36Z] Where the first color given is for the border. [2021-09-10T10:58:37Z] So in the commit https://github.com/wyvertux/wyverkiss/commit/20033f4085a97d3a3b17c22beabd4030585761b9 [2021-09-10T10:58:48Z] Konimex mentioned to set the $TERM value [2021-09-10T10:59:01Z] put even when having the variable in the /etc/profile.d/ [2021-09-10T10:59:14Z] I still don't have the value set to xterm-256color [2021-09-10T10:59:28Z] I tried sourcing it but it only becomes valid for the current terminal session [2021-09-10T11:00:40Z] x4n: relogin [2021-09-10T11:01:00Z] Also the mold failure can be fixed by removing adding `-Wno-error` to build flags [2021-09-10T11:01:21Z] Devs like to enforce Werror for some reason, it's not good since compilers are free to warn for anything [2021-09-10T11:01:42Z] `-Werror=somecriticalwarning` should be used [2021-09-10T11:01:42Z] by removing adding? [2021-09-10T11:01:54Z] Add -Wno-error to cflags [2021-09-10T11:01:59Z] oh [2021-09-10T11:02:00Z] ok [2021-09-10T11:02:03Z] how did you add --ld-path=/usr/bin/mold there? [2021-09-10T11:02:23Z] I have it in my CFLAGS and CXXFLAGS environment variable [2021-09-10T11:02:26Z] just use the alternatives system [2021-09-10T11:02:36Z] I have used the alternatives system [2021-09-10T11:02:49Z] It just warns since there's no linking involved in just compiling c files [2021-09-10T11:02:55Z] You sure the guide didnt mentiond LDFLAGS ? [2021-09-10T11:03:03Z] if the alternative system is used then don't even bother with --ld-path [2021-09-10T11:03:14Z] it didn't mentioned LDFLAGS [2021-09-10T11:03:31Z] it had the alternative system AND the export CFLAGS in the steps [2021-09-10T11:03:32Z] since /bin/ld will be searched first anyway [2021-09-10T11:03:33Z] so I did both [2021-09-10T11:03:52Z] what steps? [2021-09-10T11:04:02Z] In https://kisslinux.org/wiki/pkg/mold [2021-09-10T11:04:28Z] time to open an issue to dylan then [2021-09-10T11:04:47Z] a'ight [2021-09-10T11:04:53Z] I'll close mine then [2021-09-10T11:05:33Z] no no, don't close it [2021-09-10T11:05:41Z] and what may I do for $TERM variable? [2021-09-10T11:05:53Z] Alright. [2021-09-10T11:05:57Z] just set it in your .profile [2021-09-10T11:06:00Z] and restart your computer [2021-09-10T11:06:12Z] or logout and log back in [2021-09-10T11:06:50Z] Alright [2021-09-10T11:11:37Z] well, I have "export TERM=xterm-256color" and "TERM=xterm-256color" in my ~/.profile but the environment variable is not exported [2021-09-10T11:12:43Z] what sh are you using? [2021-09-10T11:12:47Z] sh [2021-09-10T11:12:57Z] yeah, what sh? [2021-09-10T11:13:06Z] bash? dash? zsh? [2021-09-10T11:13:21Z] sh [2021-09-10T11:13:23Z] pure sh [2021-09-10T11:13:42Z] aka busybox sh aka POSIX shell aka ash [2021-09-10T11:17:36Z] ah yes, it seems foot overrides $TERM [2021-09-10T11:18:05Z] and ash doesn't have .ashrc it seems [2021-09-10T11:18:40Z] yee [2021-09-10T11:20:59Z] I'd recommend bash (since I personally do use it) but it'd be ironic to have a gnu-free distro using bash [2021-09-10T11:21:17Z] but I'll come up with something [2021-09-10T11:21:40Z] oke [2021-09-10T11:22:05Z] There is always OpenBSD's KSH :-) [2021-09-10T11:22:19Z] SOrry if I sound like a fanboi everytime I open my mouth :-( [2021-09-10T11:22:48Z] bountyht: open an issue on dylan's kiss, maybe he'll include it in his repos (and in turn, wyverkiss will follow) [2021-09-10T11:23:34Z] oksh is in the community repo [2021-09-10T11:23:37Z] but not in the kiss main repo [2021-09-10T11:23:46Z] konimex: I am still playing with kiss in a chroot and deciding which computer I place it in for testing [2021-09-10T11:24:00Z] and its from ibara [2021-09-10T11:24:16Z] who also made portable m4 that KISS uses [2021-09-10T11:24:16Z] x4n: yeah, and the solution I'm trying to make should be in line with kiss main repo, so no oksh at all [2021-09-10T11:24:48Z] yep [2021-09-10T11:24:55Z] also oksh depends on ncurses so.. [2021-09-10T11:25:11Z] i guess it won't work out of the box in wyverkiss [2021-09-10T11:25:42Z] a temporary solution, of course, is invoking `TERM=linux vim` [2021-09-10T11:25:56Z] or `TERM=linux alsamixer` [2021-09-10T11:26:25Z] And so will "alias vim="TERM=linux vim" and "alias alsamixer=TERM=linux alsamixer"! [2021-09-10T11:26:33Z] wtf, does it depend on ncurses? [2021-09-10T11:26:37Z] that should also work [2021-09-10T11:26:38Z] * bountyht ldds ksh [2021-09-10T11:26:46Z] yep [2021-09-10T11:26:57Z] it depends on ncurses, mentioned in the depends file [2021-09-10T11:27:31Z] yee the alias works! [2021-09-10T11:28:26Z] P.S. why the git clone of vim is so big?? [2021-09-10T11:28:36Z] it exceeds 50Mb+ [2021-09-10T11:32:46Z] dylan uses git clones instead of tarballs since they bump the version every commit [2021-09-10T11:33:07Z] as for why is it big, perhaps because of the git commit itself [2021-09-10T11:33:30Z] I've done the clone manually with --depth 1 and the size is 15.10Mb [2021-09-10T11:33:46Z] Is is possible for this --depth parameter to be inserted in the kiss git clone command? [2021-09-10T11:35:43Z] you may want to open an issue in kisslinux/kiss since the current command is invoked from the package manager itself [2021-09-10T11:36:12Z] Alright, i'm doing it. [2021-09-10T11:39:22Z] Done. [2021-09-10T11:40:28Z] Also, why vim compiles with an unrecognized option "--disable-gmp"? [2021-09-10T11:42:13Z] gmp? are you sure? since there's no --disable-gmp in the kiss vim buildfile [2021-09-10T11:42:36Z] Hold up [2021-09-10T11:42:58Z] Maybe because of this symlink "../../kiss-repo/extra/vim/build" [2021-09-10T11:43:36Z] You can see it here "https://github.com/kisslinux/repo/blob/8c3548d0bdfb5f9b1152dc064f8563a75b47b58a/extra/vim/build" [2021-09-10T11:44:53Z] I've compiled vim manually and created an issue in the kiss linux repo [2021-09-10T11:45:00Z] sorry the kiss package manager repo [2021-09-10T12:05:45Z] Alright, the optimizations made will be 1) shallow clones 2) Tag management [2021-09-10T12:05:58Z] according to dylan [2021-09-10T12:57:37Z] Does kiss-community/bin packages work in Wyverkiss? [2021-09-10T12:57:45Z] Asking because of Firefox [2021-09-10T12:57:47Z] and Rust [2021-09-10T12:58:53Z] They would if they were built with static libgcc and stdc but i don't think they are [2021-09-10T12:59:23Z] And they also require libepoxy that is not present in Wyverkiss, nice.. [2021-09-10T12:59:46Z] And I can't use ccache because it instead slows down the building process of Wyverkiss.. [2021-09-10T13:00:03Z] Anyways, I'm trying it. [2021-09-10T13:01:22Z] ccache will do literally nothing for firefox or rust [2021-09-10T13:05:10Z] Yes, you are right. [2021-09-10T13:05:24Z] It takes hours for me to compile it. [2021-09-10T13:05:33Z] Even now I have rust update pending. [2021-09-10T13:15:41Z] what? I don't think firefox or rust require any libepoxy [2021-09-10T13:17:12Z] can tmux byobu or screen be built in wyverkiss? [2021-09-10T13:34:31Z] https://github.com/epilys/buke < full text manpage search, neat [2021-09-10T13:41:47Z] sorry for not noticing konimex [2021-09-10T13:41:50Z] I got disconnected [2021-09-10T13:42:04Z] But I was talking about the binary packages in kiss-community/bin [2021-09-10T15:58:29Z] made progress since yesterday but now I'm up to a kernel panic-- it says "VFS: Cannot open root device "PARTUUID=..." or unknown-block(0, 0): error -6"; "Please append a correct "root=" boot option; here are the available partitions:" then goes on to list UUIDs I don't recognize from blkid [2021-09-10T15:59:07Z] I suspected it might be a missing SATA or AHCI driver based on googling the issue but it seems like I've enabled the relevant settings for an Intel controller (what lspci says I have) so I'm unsure what i could be missing [2021-09-10T16:12:49Z] Have you enabled the filesystem you're using in the kernel? [2021-09-10T16:13:37Z] let me check [2021-09-10T16:14:21Z] ext4 seems to be enabled yeah [2021-09-10T16:14:28Z] Did you also try using root=/dev/sdXY instead of uuid? [2021-09-10T16:14:50Z] worth a try, ill give that a spin [2021-09-10T16:24:23Z] one of the UUID things only works if you have an initramfs that handles it with userland stuff, I forget which [2021-09-10T16:24:30Z] the other I believe the kernel can do on it's own? [2021-09-10T16:25:18Z] I am under the impression efistub with no initramfs should be possible-- I've avoided allowing any kernel modules and baked in the microcode and graphics drivers [2021-09-10T16:28:05Z] ah efistub, that's fun stuff; I am doing the same at work alas I never could get it to do the right thing without an initramfs; which I bake into the kernel for now but have plans to not to once efibootmgr works like it should; sorry I should say that what I am doing is not actually kisslinux related, it's a custom embedded-ish thing [2021-09-10T16:28:25Z] I see [2021-09-10T16:28:44Z] I've never tried any custom stuff, always got stuck when trying to do LFS lol [2021-09-10T16:28:54Z] figures given it's taken me a full day already to get back to this point with KISS [2021-09-10T16:30:57Z] figuring out how the darn kernel wants to continue booting can be quite confusing, especially when you try EFI; but I figured "hey, no bootloader needed, one less moving part" so I went there as well [2021-09-10T16:31:40Z] for me it's more just frustration with the fact that GRUB seems to manage to always erase my windows 10 install that's on a *separate disk* somehow [2021-09-10T16:32:21Z] hoping this doesn't have the same issue (though last install also got wiped since i only started trying efistub after another failed grub attempt x_x) [2021-09-10T16:36:30Z] boots now :) [2021-09-10T16:37:33Z] js "I want range(99)" jv "we have range(99) at home" range(99) at home "[...Array(99).keys()]" [2021-09-10T16:38:08Z] lmao [2021-09-10T16:38:52Z] amazing how everything runs on a language that can't figure out what lexical scope is [2021-09-10T16:39:48Z] o/ [2021-09-10T16:40:01Z] hi [2021-09-10T16:40:10Z] Hi [2021-09-10T16:44:02Z] davidgarland: congrats! [2021-09-10T16:44:23Z] thanks for the help [2021-09-10T16:44:58Z] davidgarland: so did PARTUUID work or did the "classic" path for the partition work? [2021-09-10T16:46:02Z] I ended up getting PARTUUID working, but I'm not entirely sure which kernel option specifically was responosible for getting it working [2021-09-10T16:46:49Z] that's how it goes [2021-09-10T16:47:03Z] one day, go through and randomly delete kernel options until it breaks [2021-09-10T16:47:07Z] lol [2021-09-10T16:47:16Z] then you will know [2021-09-10T16:47:21Z] yeah [2021-09-10T17:07:34Z] Do this instead https://ldpreload.com/blog/git-bisect-run [2021-09-10T17:26:10Z] probably a dumb question but how do I get dhcpcd to stop printing things over the console [2021-09-10T17:29:04Z] am using the default busybox init [2021-09-10T17:38:03Z] ..just edited the run file manually, guess that works [2021-09-10T18:12:56Z] hi guys [2021-09-10T18:13:22Z] have any openjdk repo that works? [2021-09-10T18:29:18Z] if you're merely concerned with getting one onto your machine, you could use https://adoptium.net/ to grab prebuilt ones-- if that's not what you want, then disregard [2021-09-10T18:44:10Z] will test [2021-09-10T18:44:24Z] why the problem in build? [2021-09-10T19:31:15Z] i think landlock could be a lighter weight way to verify that dependencies are correct than chroot [2021-09-10T19:31:59Z] by allowing access only to files owned by particular dependencies, and if a file outside of that is accessed, then you know that it's missing something [2021-09-10T21:31:37Z] Hello [2021-09-10T21:31:49Z] I'm trying out hexchat [2021-09-10T21:31:59Z] hi [2021-09-10T22:49:53Z] decided i wanted to play around with dylan's new take on baseinit and also get smdev sorted [2021-09-10T22:50:13Z] forgot that baseinit by default is fscked with toybox, so had to handle constant exits [2021-09-10T22:50:31Z] been troubleshooting a 'cannot fork - try again' for a couple hours now [2021-09-10T22:50:49Z] realized it's because my chromium script is self-referring, not because something during init indefinitely blocks >.< [2021-09-10T23:05:00Z] uhhh [2021-09-10T23:05:07Z] you launch chromium on boot? [2021-09-10T23:05:40Z] no, it's just one of the first things i launch after wayfire [2021-09-10T23:05:53Z] then why did you think it was an init issue? [2021-09-10T23:05:55Z] which is why it was so confusing (yet should have been obvious) -- wayfire launched fine [2021-09-10T23:06:04Z] because I'm a mooran [2021-09-10T23:06:09Z] ah but wayfire launches chromium? [2021-09-10T23:06:21Z] no it's just muscle memory to hit meta+w at this point [2021-09-10T23:06:33Z] meta+enter; meta+w, twerktwerktwerk [2021-09-10T23:07:14Z] interestingly, with toybox mount, baseinit nonfatally errors saying that /dev is not in /proc/mounts when trying to mount devtmpfs... [2021-09-10T23:07:51Z] but toybox mount is complete, and sufficient in this case. so that's weird